Bug#231591: [Savane-dev] Re: Bug#231591: RFP: savane -- a Web-based Free Software hosting system.
Tobias Toedter <t.toedter@gmx.net> tapota :
> Hello Mathieu,
>
> On Sunday 08 February 2004 15:17, Mathieu Roy wrote:
>> Welcome!
>
> Thanks a lot.
>
>> > I'd be grateful for pointers.
>>
>> Apart from saying that there ideally should be a package for the
>> fronted, one for the backend, and one handling database, there not
>> much to say right now, but I'll reply to any question you may have.
>
> It's no problem to split savane up into different packages. Concerning your
> debian directory, I would suggest to remove it from the savane source code.
> The reason is that it would be a "Debian-native" package otherwise, which in
> my opinion does not apply to savane.
Hum, I clearly prefer having the debian directory managed by CVS, and by
the project cvs is better than anywhere.
The fact that it makes the package "Debian-native" does not sound
really problematic to me -- I never really understood the problem with
that.
If I had rpm specs, I would put them directly in the CVS in the same
way. It is important for someone that download the tarball to be able
to build a debian package if he want to. If we can provide that, why
not doing it?
But maybe there are reasons I'm not aware of.
I have another project called pdbv, it's debian-native while it is not
debian specifically oriented, but nobody ever complained about
that. :)
> Again, that's really nitpicking, and it's probably too early to do so.
>
> [German translation]
>> I understand that, but unless I forgot something nobody ever proposed
>> to do the german translation. The only translation that is almost
>> complete is the French one.
>
> Surprise, surprise! ;-)
>
>> German translation would be a great addition.
>
> OK, I'll start that then.
Great.
>
> By the way: I already stumbled across a few bugs, should I submit them in the
> savane project page?
Yes, that would be good.
If they are trivial and you know a way to fix them, you can commit on
the CVS directly.
Before commiting, I'd like you to read first:
http://cvs.gna.org/viewcvs/savane/savane/doc/devel/CODING_STYLE?rev=1.4&content-type=text/vnd.viewcvs-markup
http://cvs.gna.org/viewcvs/savane/savane/doc/devel/CVS_USAGE?rev=1.1&content-type=text/vnd.viewcvs-markup
> Well, for the moment I can think of one last question: What does GNA! stand
> for? Probably "GNA!'s not american!", but is that right?
Hum, no.
GNA is not american but it is open to anybody from america :)
The name come from "Gna is Not Axis", Axis being a company where Loic
Dachary was working when he founded the association GNA, which became
later the FSF France.
However, apart from the name and the fact that FSF France made Gna!
possible, there is not so much in common.
Someone suggested "Gna is Not an Acronym", I like this version.
--
Mathieu Roy
+---------------------------------------------------------------------+
| General Homepage: http://yeupou.coleumes.org/ |
| Computing Homepage: http://alberich.coleumes.org/ |
| Not a native english speaker: |
| http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english |
+---------------------------------------------------------------------+
Reply to: