Given that Cloudstack (and Apache) considers "committer" status to be a
permanent status and that an emeritus committer can reactivate
unilaterally, it does not seems necessary (or even reasonable) to
restrict their access, unless they request it.
Main points from the Cloudstack example:
1) rules are explicit and PMC decisions are recorded in the bylaws
2) clear recognition of past contribution (and perhaps remaining but
passive interest in the project) while keeping the "active" list
accurately reflecting the people who are currently contributing in an
on-going basis.
Ron
On 21/04/2016 1:49 AM, Sharan-F wrote:
Hi Jacques
I thought that the discussion Ron raised was more about communication rather
than actually disabling access. I agree with you in the sense that I think
it could turn out to be considerably more work than we would want to manage.
Thanks
Sharan
--
View this message in context:
http://ofbiz.135035.n4.nabble.com/Fwd-Re-Managing-Emeritus-Committers-tp4679835p4679850.html
Sent from the OFBiz - Dev mailing list archive at Nabble.com.
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
