Complete.Org: Mailing Lists: Archives: freeciv-dev: December 2001:
[Freeciv-Dev] Re: Documentation, Usability and Development
Home

[Freeciv-Dev] Re: Documentation, Usability and Development

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Freeciv developers <freeciv-dev@xxxxxxxxxxx>
Subject: [Freeciv-Dev] Re: Documentation, Usability and Development
From: Petr Baudis <pasky@xxxxxxxxxxx>
Date: Tue, 4 Dec 2001 16:03:52 +0100

Dear diary, on Tue, Dec 04, 2001 at 01:50:30PM CET, I got a letter,
where Reinier Post <rp@xxxxxxxxxx> told me, that...
> OK, assuming we're going to have a development branch, here are some
> practical questions.
Questionable if answers will be good for anything (I would still prefer
one branch with a little more development-open CVS, though), but anyway...
> 
> 1 Where to put the CVS tree?
> 
>   1a same repository, different branch?
>      i don't know of any specific advantages - are there any?
I.e. easy merges
>   1b different CVS repository on cvs.freeciv.org?
>      better from a sysadmin point of view, but you'd still be
>      having the same sysadmins (and they read this list)
>   1c CVS repository on sourceforge or berlios?
>      that way, you'd stick with whatever facilities/policies they offer
For now I'm happy with my private development branch hosted on localhost (tm)
:-). However I think 1a should be best.
> 
> 2 What to seed it with?
> 
>   1a current Freeciv code
>   1b nothing
Uh? 1a obviously, I thought we made clear rewrite from scratch is unneeded.
>   
> 3 Where to put the documentation?
>   1a in a dedicated corner on www.freeciv.org
>   1b sourceforge/etc
Documentation of what?
> 
> 4 What does the documentation look like?
>   Which tools to use to maintain it?
Ditto. Code? Then 1a, kernel-doc/javadoc would do IMHO this job fine.
> 
> 5 Who gets CVS write access?
>   5a function-related accounts
>   5b personal accounts
5b. Much more easy to track actions of different ppl etc.
> 
> 6 Which system for bug reporting / patch tracking will be used?
>   6a Freeciv's
>   6b sourceforge/etc
6a. It's still same project, not different one. Keeping as much things as 
possible
common is good thing.

-- 

                                Petr "Pasky" Baudis

UN*X programmer, UN*X administrator, hobbies = IPv6, IRC, FreeCiv hacking
.
  "A common mistake that people make, when trying to design
   something completely foolproof is to underestimate the
   ingenuity of complete fools."
     -- Douglas Adams in Mostly Harmless
.
Public PGP key, geekcode and stuff: http://pasky.ji.cz/~pasky/


[Prev in Thread] Current Thread [Next in Thread]