The decisions are made by the volunteers who write the code. As the code is submitted to the repository, the changes are submitted to the development list for peer review. If someone sees a better way to write the code, the best thing is to submit a patch demonstrating the change. In an Apache project, all development conversations do happen on the mailing list. If you follow the mailing list, including the commit list, then you are privy to all the development decisions.
The important thing is to offer concrete suggestions in code, preferably in the form of a patch. The volunteers are usually very busy people who work the usual 40+ hours a week and then contribute to open source projects after hours. If you want to get a volunteer's attention, it's important to show that *you* are paying attention, and that you are doing everything you can to make the best use of the volunteer's time. Volunteers are freely sharing their work, and it's important to show that you are willing to share your best effort in return. -Ted. On 9/14/05, Paranj, Bala <[EMAIL PROTECTED]> wrote: > I have seen code in open source projects like Commons Chain which does > not use some of the good design principles like command-query > separation. Are decisions like these made without any justifications? If > yes, then it needs to be documented. It is overwhelming to someone who > is new to open source development to do the documentation. Looks like > this requires lot of search in the email archives. Any thoughts on this? > > Bala > http://groups.yahoo.com/group/OOAD_UML --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
