On Monday 03 August 2009 17:47:52 Joshua J. Kugler wrote: > On Sunday 02 August 2009, Kern Sibbald said something like: > > A developer's git repository has been created on github, and this is > > where, in the beginning, developers will make their commits. It > > exists, but we still need to document its usage, so it will be > > sometime next week when we can hook developers upto a git repository > > for making commits (actually pushes). If you are a developer and > > want to commit, please let me know. > > Just a clarifying question/suggestion. > > The usual work flow on github seems to be that of a developer creating > their own fork on github, and then requesting that the parent project > pull from their fork. Buildbot, for example, does this. This may work > better than giving several people direct commit access to the main > bacula git repo.
We have planned to give all developers write access to the bacula github repository. By all developers, I mean the ones that have write permission to the SVN. > Senior developers, obviously, would have direct commit > access, but random/occasional contributors would create their own fork, > etc. Just a suggestion. I would like to have the github bacula repository as open as possible to all Bacula developers. On the other hand, the Source Forge repository will have write access only by the most senior Bacula developers. Any other user who develops code for Bacula can either create their own github repository or send us a patch. If they contribute regularly and their submissions conform to our programming standards, ... then we will be happy to give them write access to the github bacula repository. I think the above corresponds to what you are suggesting. Git has many advantages over SVN that I will not go into, but it does have at least three disadvanges: 1. It is far more complex than SVN 2. It (as you mention below) is all or nothing. You cannot checkout (clone) a partial git repository. 3. It is *way* too easy for a developer to "rewrite" the repository history. Despite the above disadvantages, I am totally convinced that there are so many advantages of git, that it will significantly improve the way Bacula developers work together. > > > where xxx is the directory you want to be created. Once it is done, > > you will find that directory contains four subdirectories: > > .git > > bacula > > regress > > gui > > The main code and regression tests make sense to keep together. Might it > be better to break the gui out into its own repo? The "git way" (for > whatever value of "git way" you might find) seems to be breaking things > down as small as possible. One reason for that being git doesn't allow > you to clone just parts of a project. It's all or nothing. So, if I > wanted to just hack on the gui, I'd have to pull down all the bacula > director/sd/client and regress code. > For the moment, our primary requirement is to have all the source code on Source Forge (though I am very unhappy with SF). As such, we must either keep the gui code in the SVN or in the git repository. Since it makes up part of our "source" code, and it is actively being worked on, we want to keep it with the rest of the source code. As you point out, one of the disadvantages of git is that it is all or nothing, and Source Forge only permits one git repository, so for the moment we do not plan to change the current split of code between SVN and git. At some time in the future if we decide to host all our code on github (a possibility for later discussion), we may re-organize what parts are in what git repos since on github we can have multiple git repositories. Regards, Kern ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
