The submitter must acquire the skills to transmit reliable write-ups to
draw the attention of consumers.
On Nov 2, 2018 10:43 PM, "Dmitriy Pavlov" wrote:
> Hi Craig,
>
> Ignite dev list is now quite busy-list. GitHub comments are not forwarded
> (for the main repository, it is only forwarded for
Hi Craig,
Ignite dev list is now quite busy-list. GitHub comments are not forwarded
(for the main repository, it is only forwarded for an additional GitBox
repository, and probably we need to disable it as well or create
notifications list). Forwarding comments may create additional pressure to
co
+1 to what Myrle says.
I especially like the idea of engaging the submitter to discuss a pull request.
Even if it's to say "Thanks for this. It looks perfect as is". But often, there
will be a bit of back and forth.
One potential problem is the work flow using the github tools, which can have
+1 on everything Chris says here.
If anyone on the PMC is uncomfortable with making someone a committer
because of their uncommunicativeness, I'd be inclined to give it a little
more time. A "no" now, doesn't mean a "no" forever. Maybe ask that person
a few questions about their PR's on the list
Pada 2 Nov 2018 20:49, "Rafael Weingärtner"
menulis:
Hey Christofer, you just said what I was going to comment.
How is it possible for someone to contribute code (opening a PR, and so on)
without engaging with the community? I mean, don’t you have a reviewing
process to accept/merge code?
We ha
I agree that it's hard to be a critical and crucial part of a community without
being *IN* the community.
More than anything, the PMC is the entity within the ASF that is the community
representative for a project. They "run" the project for the community with the
understanding that they unders
Pada 2 Nov 2018 20:49, "Bertrand Delacretaz"
menulis:
On Fri, Nov 2, 2018 at 1:43 PM Christofer Dutz
wrote:
> ...I think these contributions would just be uncommented code-drops...
Code speaks louder than words sometimes ;-)
But in general I agree with you.
-Bertrand
---
On Fri, Nov 2, 2018 at 1:43 PM Christofer Dutz
wrote:
> ...I think these contributions would just be uncommented code-drops...
Code speaks louder than words sometimes ;-)
But in general I agree with you.
-Bertrand
-
To unsubsc
Hey Christofer, you just said what I was going to comment.
How is it possible for someone to contribute code (opening a PR, and so on)
without engaging with the community? I mean, don’t you have a reviewing
process to accept/merge code?
We had this situation in the past in CloudStack, and you sti
Hi Dimitriy,
well I guess I simply forgot about the option the PMC != Committers ;-)
So I agree, in some cases I could probably support someone not able to
communicate because of such reasons a committer, but definitely not to become a
PMC.
But if it's just laziness or unwillingness (for whatev
Dear ASF Fellows,
I strongly appreciate all your replies. I believe there is no just one
correct answer. Which is why I need opinions of folks from other projects.
Myrle, Apache Ignite has 26 PMC members and 38 committers, so PMCs is a
subset of committers set.
About collaboration: I guess these
Hi Dmitriy,
Is Ignite a PMC = committer community or a PMC ⊂ committer community?
You may have different requirements for communication level depending on
which of these your community is. But I don't believe it is possible to
write very good code without being willing to talk with others about
On Fri, Nov 2, 2018 at 10:22 AM Christofer Dutz
wrote:
>... So if someone is an awesome coder, but doesn't communicate, I would not
>invite him or vote for inviting...
I agree with that when it comes to inviting people on a PMC.
I think it's fine to accept code contributions from people who are
Have to admit it was the title which triggered me ... but I guess it was
intentionally ;-)
Well for me it is clear:
Communication == Community
Code == Code
And: Community over Code.
So if someone is an awesome coder, but doesn't communicate, I would not invite
him or vote for inviting.
In th
I cannot see how someone could be a an effective community member without
joining the community's communication channel. That just seems a practical
necessity. Especially if someone is to be given the keys, to become a
committer. They need to be there to respond, e.g. if they were to break thing
Dear ASF Fellows,
I am PMC member of Apache Ignite, but I joined PMC relatively recently. I
need help from you again in regarding the Apache Way.
Question is related to comittership for community members,
- who are not visible on dev/user list, have a couple of threads they
participated
- but c
16 matches
Mail list logo
