From: Francisco R. <li...@na...> - 2002-04-09 21:09:44
|
On Tue, 9 Apr 2002, Dan Wilson wrote: > I may have mis-understood what you were requesting. Probably I didn't explain it well either. >Were you wanting to simply read documentation on the new version, Not documentation but whatever thoughts, emails, plans there are. >or did you want developer access to the cvs? No. > If it's the documentation, we can't help you... there isn't much information > regaurding the new version other than some emails intersperced in the -devel > mailing list. So does that mean that the new version is not actively been worked on? What I had hoped for was to join the analysis phase of the new version and be involved in the planning. > If you want developer access to the cvs, then I would hope that all projects > require some type of evidence that you are a capable developer before allowing > access into the cvs. Of course. > This is a completely normal and sane requirement prior > to allowing developer access. Agree. >I don't think I've ever been part of an open- >source project where some type of contribution to the product was the key to >being granted access into the code. I think we had a communication problem. I totally agree with your stance on access to CVS. However, I was not referring to that. > If you have something to contribute to the project or have a list of other > projects in which you have been involved, then we would be happy to have you > aboard. But until we know that, there is no real point. I don't particularly want/care about CVS access. If I have something to contribute I will post it on the list or on a web page. If and when I produce so much code that it is too much work for others to commit it then I will probably be given CVS access whether I want it or not. :-) I guess I should join the development list. How about creating a statement of what is desired of a new version? |