Infrastructure for Mozart development

[Boriss Mejias]

Hi Guido,

I'm surprised that your message didn't get any reactions yet, so I'm 
going to start commenting some of your points.

Guido Tack wrote:
> Dear hackers,
> 
[...]
> 
> Our concrete proposal consists of four steps:
> 
> Step 1 - The news server.
> We would like to switch off our news server, as it is used for mirroring
> mailing lists only. Our proposal would be to use a free service like
> gmane.org for mirroring. As this is not such a big issue, we want to do
> that in the very near future if no one objects.
> 
> Step 2 - The CVS.
> The source code repository should be moved. I would suggest to use a service
> like sourceforge or savannah, and to maybe move to subversion (just
> personal taste, though). That way, the developers (or the board) can give
> write access to the CVS as needed, and you get a bugtracker and release
> management system on top of it.

Kevin was looking at Sourceforge and Savannah sometime in the past, but 
I just remember that his conclusion was that we were going to lose the 
history of CVS. I don't know if that is the case if we first port the 
repository to SVN, and then we put it at Sourceforge. Savannah does not 
support SVN yet. I haven't used SVN very much yet, but according to the 
basic advantages that it presents, I also think we should switch to that.

> Step 3 - Mail.
> Currently, we are hosting two services: email addresses for developers, and
> the mailing lists. The mailing lists could be hosted at sourceforge or
> savannah, too.
> For the mail aliases for developers, it would be enough to register the MX
> record for the mozart-oz.org domain somewhere where you can easily define
> forwarders (e.g. for gecode.org, we've used namecheap.com).
> 
> Step 4 - The web pages.
> The Mozart web site, as nice as it may look on the surface, is a weird
> mixture of Mozart scripts that we don't have any source code of, php, perl
> hacks and some html. It is a nightmare to maintain, and we were more than
> lucky that it survived our server migration last year. The bugtracker,
> jitterbug, is a discontinued project - no updates, no support.
> All in all, the web site will need the most work, definitively.

Is it necessary to keep the website with the layout that it has now? I 
think that everything could be done using the support provided by 
Sourceforge or Savannah, except for the documentation. But documentation 
is generated from the repository, and those pages are static once they 
are built, so no problem keeping that as it is now, and keeping it 
updated once changes are committed to the repository.

> 
> Of course, we will try to help out where we can during the transition - and
> until an optimal solution is found, we will fully continue hosting and
> support for Mozart. I am sure, in the end this will push Mozart much more
> in the direction of a community product.

thanks for offering help, and I agree that this migration would be very 
convenient

cheers
Boriss

> 
> Cheers,
>         Guido
>