> > So what is your point? >> >> - that we need a whole lot more people working on this. We already know, > > either people will volunteer or they won't. > > - that you don't know how to help. You said you can see problems. Tell us > > you are going to fix those problems. Then do it. > >Well, now that I consider it more, I have to say that I guess I am just >used to a "corporate" way of developing software that has a definite >administrative structure and plan of action with people assigned specific >tasks. Since I've never worked on an Open Source project, it justs seems >sort of anarchistic to me. Maybe it'll be fun -- it justs seems like a >lot of code, documentation, and examples to just jump into.
There is some introductory guidance on this, exempli gratia: <URL: http://www.advogato.org/article/429.html > <URL: http://www.linuxdoc.org/HOWTO/Software-Release-Practice-HOWTO/ > <URL: http://www.kbasic.org/1/join.php3 > <URL: http://www.newsforge.com/article.pl?sid=01/07/11/185221 > <URL: http://www.mozilla.org/hacking/ > Though Mozilla is more organised and disciplined than a lot of OS developers prefer <URL: http://www.tuxedo.org/~esr/faqs/hacker-howto.html > This may be a bit too general. <URL: http://www2.abisource.com/mailinglists/abiword-dev/99/December/0264.html > This contains the single best description of how not to look out of place on an OS project, really the OS Initiative <URL: http://www.opensource.org/ > ought to be invited to get the authors permission <Paul Rohr ([EMAIL PROTECTED]) > and place a version of it somewhere on their site. Ben. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
