[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [glob2-devel] general updating in CVS
From: |
Stéphane Magnenat |
Subject: |
Re: [glob2-devel] general updating in CVS |
Date: |
Mon, 28 Nov 2005 10:20:34 +0100 |
User-agent: |
Mozilla Thunderbird 1.0.7 (Windows/20050923) |
Hi,
TODO file needs updating, and those links are wrong, you have to take
out the SID= part in the links. Also, please rewrite that into english :)
change the [no-spam] in the AUTHORS file to [at] and [dot]com instead of
.com, etc
Should we put the TODO on the Wiki instead of on the source? I think
that the roadmap concept is good because it show clearly the state of
the project. So I suggest moving things from TODO in the CVS into
roadmap on the Wiki.
And we should really make backups of the Wiki, otherwise we have the
risk to forget everything !
does TODO.Eli need to be in there?
I do not think so. Eli, any objection?
remove DONE
remove NEWS
INSTALL needs to be updated properly
so does README and README.cvs
Agreed.
what is Doxyfile doing in there if we don't use doxygen?
Doxygen is already partially used, please let it there. I plan to make
scripts on www.globulation2.org that create doc on a regular basis. By
the way, is cron working for users?
can we have the base set of maps and data kept in cvs? I personally
would prefer that over having to make sure I run ./syncdata &&
./syncmaps every time. I don't see what the big deal is there.
Well, why not, but we have to know that CVS is really not efficient for
binary files.
please make metaserver work! I would love for it to be able to compile
since it hasn't been able to yet. What I really want to see happen is a
linking of metaservers, one on each continent, so if one fails we still
have backups to connect to, and they can be chosen in game.
What is the problem? The last time I tried it was working perfectly!
By the way, it's good to plan backups, and we have to keep them in mind,
but as we are small, it's better to have a metaserver well integrated
with the Wiki using a unified login than a 100% uptime.
Steph