On Mon, 2010-09-20 at 02:05 +0300, Andrew wrote: > 20.09.2010 00:17, Mike Noyes пишет: > > Andrew, > > I was referring to LEAF project members. We have over 80. Most of whom, > > aren't code contributers. They help with support, documentation, etc. > > The current access is: > > > > leaf/CVSROOT/avail > > # Selective access for teams, etc. > > avail|arneb, dorus, espakman, hejl, hun, lfcorreia, nangel, > > nitr0man|src/bering-uclibc4 > > > I think that anybody of them who will want to bring something new/fix > something old&broken into LEAF tree (like davidMbrooke) should do this > without long-time coordination with all members - at least until this is > not global changes (IMHO all global changes are now in past - except > possible pre-release kernel upgrading to latest stable version). How > it'll be done better - let you decide, to grant access on demand to > members that request it,
Andrew, This is how we've handled write access in the past. It works well when one of our project admins makes timely modifications to 'CVSROOT/avail' on request. > or to grant access for all contributors by > default, or even to grant access to all project members. -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ leaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-devel
