Re: retiring/removal of committers

Jakob/John/Suneel: Thanks for the perspective. Its important for the community to understand the philosophy of how Apache operates, which your notes have done - at least for me. —Tom > On Nov 29, 2017, at 8:57 PM, Jakob Homan wrote: > > This was

Re: retiring/removal of committers

This was an explanation I had previously sent to another podling I mentor: (Merit never expiring) is not a bug. As ASF sees it, this is a feature: https://www.apache.org/dev/committers.html (search for Merit Never Expires, an ASF axiom). As a volunteer organization, we cannot require anyone

Re: retiring/removal of committers

There is one out. When a podling graduates, its customary to keep everyone on. However, if there are people who are no longer interested in the project and the project chooses to not include them, its not uncommon that they be left off the graduation. They would still be open to be included

Re: retiring/removal of committers

I think that is why we were having it - no one knew about Apache’s rules around this. That seems to settle the matter: once you are in, you are in. —Tom > On Nov 29, 2017, at 3:42 PM, Suneel Marthi wrote: > > Fyi... committership never expires in

Re: retiring/removal of committers

Fyi... committership never expires in ASF, unless the committer chooses to go Emeritus. So not sure if this discussion is needed. On Wed, Nov 29, 2017 at 3:23 PM, Thomas Nadeau wrote: > > One action I took from the last grooming meeting was to > investigate with

retiring/removal of committers

One action I took from the last grooming meeting was to investigate with the community, what process and policies we want to use around the retirement and/or removal of Committers on the project. As our mentors have told us before, the community here is empowered to decide the criteria