A few observations I have found by looking through the Apache wiki for all the
projects is:
That several of them do separate the two roles.
The discussions about committers happens in the dev@ list while discussions for
PMC happen on the private@ list.
Some projects projects treat PMC as a promot
It sounds like the consensus is: don’t change [the current questionable uses of
getMessage] unless willing go a step further and provide a detailed,
informative message, which may include the exception’s toString.
Thanks.
-Owen
> On May 28, 2019, at 3:32 PM, Nabarun Nag wrote:
>
> Looking at
I don’t see a compelling reason for Geode to make a distinction between
committer and PMC member.
If you have the power to merge PRs, you are a steward of the codebase;
we need to be able to trust that you have Geode’s best interests at heart and
will adhere to our practices.
PMC membership c
My two cents...
1) What is our criteria for becoming a committer and PMC member?
I don't have anything particularly enlightening to say here, and I think I
am just reinforcing what we already do, but here goes...
I think this piece from the ASF notes is key for measuring candidacy for
committer/P
I think it’s time to re-establish consensus around two things:
1) What is our criteria for becoming a committer and PMC member?
2) Do we have separate criteria for committers and PMC members (and thus should
elect them separately)?
The ASF notes that projects are free to chose the approach that
