Hi
I'm not sure that we have any separate project bylaws (it sounds like
something legal :-) but I know that we do document and implement
proposals based on community feedback (e.g regarding filing ICLA's).
It sounds like essentially the idea is that if a committer wants become
emeritus then they need to email the PMC to let them know. And if they
want to change back then they do the same thing. This puts the
responsibility on the committer to communicate it.
The term 'inactive' may mean different things to different people.
People do have valid reasons why they are not active for certain periods
(e.g studying, working on an intense project, or just taking a break).
In each of examples people may seem to be inactive but with the
intention to return after the break. I suppose sometimes people dont
really know how long they will be away (and sometimes it happens
unintentionally) so I think giving the committer the choice to become
emeritus or not, will be a good thing.
BTW I see we already have an emeritus PMC section. I would suggest that
only have one emeritus section that includes PMC and Committers (as PMC
are committers by default anyway) and a column could be added to
indicate PMC or not if required. Also the people we have on the current
inactive list – have they actually said that they would be inactive? (if
so then they could be on emeritus list...)
Thanks
Sharan
On 20/04/16 00:04, Jacques Le Roux wrote:
That sounds indeed better than what we have now... If the committers
play the game... (I mean if they do care)
https://cwiki.apache.org/confluence/display/OFBADMIN/Apache+OFBiz+PMC+Members+and+Committers#ApacheOFBizPMCMembersandCommitters-InactiveCommiters
Jacques
Le 19/04/2016 23:55, Ron Wheeler a écrit :
There may be some merit in this idea from the Cloudstack team.
Ron
-------- Forwarded Message --------
All,
As I am sure many have observed, we have a large number of committers
[1] who are no longer active. Currently, we no status that continues
to recognize someone’s committer merit while allowing them to declare
inactive in the project. To address this gap, I am proposed amending
our project bylaws [2] as follows:
2.3.4 A committer is considered "emeritus" by sending their
declaration to
priv...@cloudstack.apache.org<mailto:priv...@cloudstack.apache.org>.
An emeritus committer may return to "active" status by sending
their declaration to
priv...@cloudstack.apache.org<mailto:priv...@cloudstack.apache.org>.
No vote is required for a committer change from “emeritus" to
“active" status.
2.3.5 "Active committters" are all non-emeritus committers.
These clauses were inspired by the Apache Cocoon [3] bylaws [4]. To
be clear, a committer never loses their merit, and only a committer
can decide to go emeritus. Since merit is never lost, a emeritus
committer may return to active status at anytime by simply informing
the PMC of their intention to be active again. No one can require
that committer change to emeritus status.
On the website, we would place emeritus committers in a separate
section — allowing users to more easily identify those that are
actively participating in the project.
Thoughts?
-John
[1]: http://cloudstack.apache.org/who.html
[2]: https://cloudstack.apache.org/bylaws.html
[3]: http://cocoon.apache.org/
[4]:
http://code.metager.de/source/xref/apache/cocoon/commons/bylaws/bylaws.txt#14
Regards,
John Burwell
john.burw...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London VA WC2N 4HSUK
@shapeblue
