Help a lot. Thank's. Em qui, 4 de out de 2018 às 13:30, Luciano Resende <luckbr1...@gmail.com> escreveu:
> “The Apache Way” values “community over code” and is meritocracy driven, so > any kind of contributions, code or non-code can be used to suggest a > contributor as committer. > > Having said that, Marvin is now an Apache project, and all what we do is > open. We also have a say that “if it didn’t happen on the mailing list, it > didn’t happen”.... and the list is publicly and archived. While, to certain > extent, we are ok with chat applications, final decisions and communication > needs to happen on the mailing list which is open to all (but i believe > slack is also open to all) > > In reality, a coommitter is a contributor, that based on trust from > previous contributions, was given write access to the repo. > > And to finalize, after the initial list of committers that came with Marvin > proposal, new committers need to be elected by PPMC. > > Hope this helps... > > > On Thu, Oct 4, 2018 at 16:09 Lucas Bonatto Miguel <lucasb...@apache.org> > wrote: > > > Hi, > > > > This is a question for the mentors or any other person with more > experience > > in the Apache process than me. > > > > Should stakeholders be listed as committers as well? In this context > > stakeholders are people who are involved with the project, make non-code > > contributions, but help with architectural discussions, product design, > > etc. It is important for those people to have access to our Slack and > most > > resources that committers have. > > > > I am not sure if I used the right terms, but I didn't find much online > > about this subject. > > > > - Lucas > > > -- > Sent from my Mobile device >
