[Gecode] Moving the CVS

[Christian Schulte]

Good idea, maybe I can add some more comments:
 - The root is good
 - For the web I propose the module www as directory
 - For the system I propose gecode
 - Then we should move stuff such as benchmarks and doc out of the gecode
directory
 - The upload to the webserver should be done by a script only (going to
grizzly, doing the cvs up, and also the proper permissions). The idea is
that nobody ever goes there but the script.
 - All webpages should be done using php from the start
 - The webpages hsould clearly reflect general information and version
specific information (one of the mistakes we did with Mozart)

Cheers
Christian

--
Christian Schulte, http://www.imit.kth.se/~schulte/ 

-----Original Message-----
From: gecode-bounces at ps.uni-sb.de [mailto:gecode-bounces at ps.uni-sb.de] On
Behalf Of Guido Tack
Sent: Monday, July 26, 2004 3:59 PM
To: 'Technical discussions about Gecode'
Subject: [Gecode] Moving the CVS


Hi everyone.

I would suggest moving our CVS from /services/ps/CVS to
/services/gecode/CVS. 
This will give us better permission control and a nicer directory structure.

And, in addition, we can use cvs.gecode.org:/services/gecode/CVS as the 
root ;-)

For the web server, Christian suggested to put all the web pages into CVS,
so 
that we just have to do a CVS update to "upload" any changes. I think this
is 
a good idea, and I would propose to add another toplevel module gecode-web. 
Would it make sense to have a shell script that is, say, "suid tack", which 
updates the CVS in apache's html root? That way, all directories and files 
would automatically get coherent permissions.

Guido

-- 
Guido Tack
Programming Systems Lab
http://www.ps.uni-sb.de/~tack
_______________________________________________
Gecode mailing list
Gecode at ps.uni-sb.de http://www.ps.uni-sb.de/mailman/listinfo/gecode