Dear mozart hackers,
(Warning, long email, but reactions are needed)
We had a great time attending FOSDEM on the past weekend. Interesting talks
and people, and good beer :) One of the things we realized was that many
projects are hosted at github, so we are going to follow Steward's suggestion
and we will migrate Mozart's repository to github. Unless, of course, the
Mozart Board disagrees with this idea.
But there are a bunch of things we have to decide first. It is not only code
what is being hosted at the UCL/GForge, so here you have several suggestions
for the work we have to do now. If you disagree with any of the following
points, please speak soon:
- History: we will try to keep the history of changes in the move from svn to
git (Yves and I are investigating on this), but if this is too complicated, we
will simply create a snapshot of the current mozart state, and start a new git
repository from it. In other words, keeping history is not a priority. Anyone
interested in the history can have a look at the svn repository hosted at
UCL/GForge.
- Bug tracker: It was quite time consuming to migrate the previous bug tracker
to the current one at UCL/GForge. Since we are not advancing in fixing bugs, I
suggest we keep the tracker where it is. At least for now. We might decide on
something different later on.
- Wikipages: Since the wiki support at UCL/GForge is far from great, we might
migrate it some day, but again, not yet. Suggestions and discussions can
follow on a separate thread.
- Clean up: This is probably one of the most important points. This is an
opportunity to clean up a bit the repository and get rid of many directories
and branches that are no longer under development. They won't be lost because
they will remain available in the current svn repository. Here is a proposal:
Tags: There are 38 tags. I would only keep:
mozart-1-2-5
mozart-1-3-2
mozart-1-4-0
Branches: 24 branches. I'd only keep:
mozart-1-3-0-fixes
mozart-1-4-0
mozart-gecode
Trunk: There are 12 directories, and here we need to be more exhaustive about
what to do with them.
To be kept (3):
mozart
mozart-stdlib
meps
I don't know, but probably keep (1):
mogul
I don't know, but probably forget (4):
gtk-canvas
mozart-contrib
mozart-gtk
mozart-site
To be forgotten (4):
contrib
CVSROOT
NSST-Satisfiability
portage
Now, from the directories to be kept, 3 or 4, we would like to make a
different git project for each of them.
Feedback needed before we take any decision you might regret.
cheers
Boriss
_________________________________________________________________________________
mozart-users mailing list
[email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
