Peter Donald wrote: > Thats nice for some codebases but not appropriate for all. For instance the > Ant codebase has got to have at least 10-15 different styles (probably way > way way more) because 70% of code is not written by the committers but by > members of community who have their own particular tastes. It is is largely > up to the committers to decide whether to restyle the files and that really > has not greatly impacted the quality of ant. However other codebases have > much more rigourous conventions that are followed precisely. Its up to the > developers what they want to do.
Agreed. I'm simply saying that, moving forward, the Ant PMC member should encourage the subproject to stick to the default convention, or declare one of their own. If we had been more careful about this sooner, then perhaps the Ant codebase would not be host to so many diverse styles. I agree that any change has to be made by a Committer to the subproject, but reserve our right to nag. If the Committers want to ignore us they can, but that doesn't mean we should go quietly into the night. I personally believe these things don't happen because people are bloody-minded, they happen because people are unaware, and we haven't been watching each other's back. In the meantime, I do suggest we go with rule #1 - Adhere to the style of the original. -- Ted Husted, Husted dot Com, Fairport NY USA. -- Building Java web applications with Struts. -- Tel +1 585 737-3463. -- Web http://www.husted.com/struts/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
