[kepler-dev] Proposal: Allow members to give apprenticeship (cvs write access) to trusted colleagues

[Matt Jones]

Chad and other Kepler members:

I've modified the text on the management page to accomodate your request 
for sponsored cvs accounts.

    http://kepler-project.org/Wiki.jsp?page=KeplerManagement

This essentially lets us give CVS write access to people before they 
have become full project members.

Please let me know if this captures the essence of your request.  If it 
does, then we can put the practice into effect.  Lets give people one 
more week (until Fri Dec 17) to voice any disagreement with the policy, 
and then we can put the policy in place if there aren't any 
disagreements.  Cheers,

Matt

Chad Berkley wrote:

> I would like to make a proposal for a rule change to the Kepler 
> project group rules.  Our current system of giving CVS write access to 
> only group members makes it cumbersome to get a (possibly) future 
> member to contribute code to the repository.  Right now, a current 
> member has to check code in for another individual until they are 
> voted into the group.  This is a major hassle, especially if the 
> person you are helping is not working in your office.  I think what 
> most of us do is give our password to a contributor, which is an 
> unnecessary security risk.
>
> To fix these problems I propose the following:  A current member would 
> ask for an apprenticeship account for the contributor.  This account 
> would have write access to CVS.  The member who asks for the account 
> is solely responsible for everything and anything that the contributor 
> submits/changes.  When the apprentice has shown that he/she will 
> continue contributing, the member can then propose a vote for 
> membership.  The important part of this is that the member is totally 
> responsible for whatever the apprentice contributes.   I think this 
> will keep members from requesting an apprentice account for anyone 
> they don't trust.
>
> Before I propose a vote for this proposal, I'd like to hear any 
> feedback.  I'm open to modifying this if something thinks it's necessary.
>
> Thanks,
> chad
> _______________________________________________
> kepler-dev mailing list
> kepler-dev at ecoinformatics.org
> http://www.ecoinformatics.org/mailman/listinfo/kepler-dev