Nick Burrett wrote: > People will contribute to a project if they like the software > but would like to see a enhancement to fulfill their needs. Some will > make the time and take the effort to do this, while others may simply > put requests onto the mailing lists.
Well, suppose I want to contribute to FreeVSD. Where do I begin ? How is FreeVSD structured ? Which file has which purpose ? Not a single of those questions is answered in the documentation. I do want to contribute, and I'm quite capable of contributing with good code. But if I have to look it all up myself, I don't think it's worth the trouble, so I'd rather submit my requests. So suppose I request 10 things. 5 of those are needed by 80% of FreeVSD users and 5 of those are needed by 10% of FreeVSD users. The 5 needed by 80% will be implemented in, let's say, about 6-12 months. The other 5 won't be implemented at all. If I knew how FreeVSD worked, I'd implement all 10 of them and submit my code to GPL. That way, everyone's happy : other people are happy because they get more features and I'm happy because I get my features PLUS I get comments on my code, which will result in code improvements. Additionally, other people will come up with new ideas, based on my implementations, and this will again result in new code. I hope this clarifies what I mean : if you want to get more programmers working on a project, you need to make sure the code is not only GPL, but it's easy to learn how the project works. If you don't do that, you'll just get tons of requests, but no code. And you're missing out on a great opportunity to make the project grow. Greetings, Wim ------------------------- The freeVSD Support List -------------------------- Subscribe: mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support Archives: http://freevsd.org/support/mail-archives/freevsd-support -----------------------------------------------------------------------------
