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

[Ilkay Altintas]

I think this is a great idea. Maybe we can have a time out limit for 
the apprentice accounts. 6 months maybe?..

-Ilkay

On Oct 27, 2004, at 1:44 PM, Shawn Bowers wrote:

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