Re: [DISCUSS] State of the project: Culture and governance

2018-05-08 Thread Kenneth Knowles
On Tue, Jan 23, 2018 at 8:44 AM Ismaël Mejía wrote: > - Clear guidelines for the criteria to earn commitership/PMC status. > The PMC discussed this quite a bit and we have now added this to the web site: https://beam.apache.org/contribute/become-a-committer/ Kenn

Re: [DISCUSS] State of the project: Culture and governance

2018-02-04 Thread Ted Yu
bq. 1. Propose a pull request to their fix branch. This is my favorite and I've mentioned it. Everything is straightforward and explicit. The above makes sense. When the contributor merges the reviewer's pull request, it signifies their willingness to adopt the suggestion, making the combined

Re: [DISCUSS] State of the project: Culture and governance

2018-02-04 Thread Romain Manni-Bucau
Le 4 févr. 2018 19:53, "Kenneth Knowles" a écrit : On Wed, Jan 31, 2018 at 1:11 AM, Ismaël Mejía wrote: > > For example if a > first-time contributor fixes some error and has the expected quality > we should accept it quickly, not being picky about some

Re: [DISCUSS] State of the project: Culture and governance

2018-02-04 Thread Kenneth Knowles
On Wed, Jan 31, 2018 at 1:11 AM, Ismaël Mejía wrote: > > For example if a > first-time contributor fixes some error and has the expected quality > we should accept it quickly, not being picky about some other part > that can be improved that was discovered during the review,

Re: [DISCUSS] State of the project: Culture and governance

2018-01-31 Thread Jean-Baptiste Onofré
Sorry, but I fail to see the difference between Beam and other Apache project. It's not a github project: Beam follows the rules defined by the Apache Software Foundation. Beam website/contribution guide or whatever should just point to Apache website resources. It's clearly explained and

Re: [DISCUSS] State of the project: Culture and governance

2018-01-31 Thread Ismaël Mejía
Some extra comments inlined: JB, > 1. The Apache Beam website contains a link to the Apache Code of Conduct (on > the dropdown menu under the feather icon ;)). Maybe we can also add a link to > the contribution guide as it's really important, especially for people who > target the

Re: [DISCUSS] State of the project: Culture and governance

2018-01-30 Thread Lukasz Cwik
I have to -1 reductions in the code review quality bar as this leads to test problems, which leads to CI issues, which leads to gaps in coverage and then to delayed, bad and broken releases. +1 on converting Google docs to either markdown or including them on the website since it is a valuable

Re: [DISCUSS] State of the project: Culture and governance

2018-01-29 Thread Ismaël Mejía
Hello again, Some comments inlined: JB, > 1. The code of conduct is the one from Apache. Yes I am not necessarily saying that we need a new one, I am just saying that we need to make this explicit, not sure everybody is aware of it https://www.apache.org/foundation/policies/conduct.html > 2.

Re: [DISCUSS] State of the project: Culture and governance

2018-01-23 Thread Robert Bradshaw
On Tue, Jan 23, 2018 at 9:29 AM, Romain Manni-Bucau wrote: > Hi Ismael, > > More you add policies and rules around a project more you need energy to > make it respected and enforced. At that stage you need to ask yourself if it > does worth it? +1. I also agree with JB

Re: [DISCUSS] State of the project: Culture and governance

2018-01-23 Thread Kenneth Knowles
Great starting points! I agree w/ JB's point that some of this should be private@ discussion. I am keeping my comments to things that I think everyone on dev@ should be part of. For all mentions of ASF policy: we should have our own link to the relevant policy. It is hard enough for us to find

Re: [DISCUSS] State of the project: Culture and governance

2018-01-23 Thread Romain Manni-Bucau
Hi Ismael, More you add policies and rules around a project more you need energy to make it respected and enforced. At that stage you need to ask yourself if it does worth it? I'm not sure it does for Beam and even if sometimes on PR you can find some comments "picky" (and guess me I thought it

Re: [DISCUSS] State of the project: Culture and governance

2018-01-23 Thread Jean-Baptiste Onofré
Hi, I would like to remind: we are an Apache project, not an isolated one. As an Apache member, it's really important to me. 1. The code of conduct is the one from Apache. 2. If it's not happen on the mailing list, it doesn't exist. That's the Apache rule. We already discussed about that in the

[DISCUSS] State of the project: Culture and governance

2018-01-23 Thread Ismaël Mejía
This is a sub-thread of the state of the project one initiated by Davor. Since this subject can be part of the community issues I would like to focus on the state of the project for its contributors so we don’t mix the discussion with the end-user thread. I hope other members of the community