2010/5/11 Jeff Mitchell <[email protected]>: [snip] > At this point, if I had to pick a solution for us, I'd say Gitolite + > Redmine, with migration of our Bugzilla over to Redmine. I think this > provides a pretty nice capability, allowing each project to have its own > issues, wiki, news, repository, and so on yet still be a part of the KDE > whole. Clean separation, yet still unity. We could even still throw cgit > on top, allowing for multiple ways of browsing code depending on > individuals' preferences.
An important basic feature of Gitorious is the ability to create team and private repos on-the-fly without help from an administrator. Given how Git works, if KDE doesn't provide this itself we will find people using github and gitorious and we fail the "keep the community together" test. I'm guessing it might be possible with Gitolite's more advanced ACL to do things like allow the creation and deletion of remote branches without allowing force pushes in the master branch (disabling force pushes in at least master is needed for revertabliity). These remote branches could perform the duty that clones and forks provide in gitorious and github. It would be a bit messy since remote branches are a flat list, but having multiple repos for the same project is also messy so its just a tradeoff. This is just a requirement that we took for granted with Gitorious that we have to think about. I can't think of any others, there might be some. Ian _______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
