I suggest a trusting-by-default policy for gaining push access to main repo on cho:
- anybody who has contributed accepted patches to wxhaskell - and who requests it (or says yes to a "would you like commit access") The basic rule for using this access is - use good judgement: only push if you have some confidence in what's going in Using a DVCS means we can afford to relax a little. The worst case is a reset and a message to wxhaskell mailing lists asking folks to reset their own branches Darcsden/Patch-tag forks are great, but it may help for synchronisation to have a single focal point that moves forward quickly. Review is great, but it be more effective to make it a social norm than a technical stumbling block. Comments? -- Eric Kow <http://erickow.com> ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
