Le 17/09/2012 16:10, Galen Charlton a écrit :
Yes. The way it works in Evergreen is that there's a working repository [1] separate from the main Evergreen repository. Anybody who has an SSH key registered with the Gitolite installation managing Evergreen's Git server can push branches to the working repo. It's currently configured so that a person could push a branch starting with user/$username and have exclusive access to push to that branch, or push to a branch starting with collab/$username to allow anybody to also push to that branch.
I really love the idea of having something where everybody can push, but it can't be adopted "as is": * where would ppl signoff patches ? (ie: in which branch ?) * how would patches be pushed ? through a merge ? For signing-off, there are many possibilities: * the patch to signoff is pushed to collab/bug_NNNN, and, when it's signed-off, the signoffer does a push -f ? * the patch to signoff is pushed to collab/$patchauthor/bug_NNNN, the signed-off patch is pushed to a specific signed-off branch (like collab/signed_off/bug_NNNN) Having a separate repo for wip is also a good way to have an official repo without zillions of branches: koha.git would become koha_wip.git (with all branches) and a new koha.git repo is created, from koha_wip, but only with released & master branches (Is it also time to speak again of putting languages in a specific repo ?) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08