That's fine with me. I think all you need to do is to register on savannah
and to join the project. At that point you should have CVS writing
permissions (probably *after* I approve you, but I promise you I will
:-)). Of course that holds for everyone else interested in using the CVS.
I think we are all (well, you are all) very capable people, so I have no
intention to put any restrictions on people that want to have writing
access to the CVS of the project, provided that they partecipate actively
to the mailing list or that at least they send a couple of reasonable
patches. That as a future policy, of course. And that's my point of view:
any other opinion is very welcome.
I also suggets we make a doc directory on savannah to collect
everything we can gather :-) , and start writing a formal spec of the
part's we know how to do, also over algoriths we intend to use and data
structures, this since I find it a major flaw of gcc that this kind of
info is hard to find and access.
That's a good idea. I have pushed towards having some official things
written even before starting to write a single line of code. I think that
a project that is just starting needs a clear design right from the
beginning. That will attract new develepers, who otherwise will be just
put off by the lack of clear documentation. Or am I too much a bureaucrat
and too bad as a developer? :-)
Perhaps it's time to contact our webmaster and to sum up what we want
on the page ?
Of course. They are both here, and they are probably reading this e-mail
as well (Richard and Guy, can you confirm?)
I suggest that any specific question/question addressed to them be
contained in a message with the world "webmasters" clearly marked in the
subject.
Biagio