BradNeuberg proposed that we should have "stewards" - persons who are skilled in certain project-wide coding issues and help developers improve their code.
Of course, this is all voluntary. Nobody needs to let a steward look into his code and give comments. But I hope people will accept the stewards' help as one way of quality assurance - and after all, that's what we want to create: a high quality product. :-)
So here's a first list:
|ThreadSafetySteward (ensures that code is thread-safe)||
StefanReich (I don't have complete theoretical knowledge about this subject, but intend to do some recherche/research and maybe write a "meta test program" [if there is none])
|InternationalizationSteward (ensures that code is internationalizable)||StefanBorg|
|JavaBeansSteward (ensures that classes are reusable as JavaBeans)||StefanBorg|
|ExtensibilitySteward (ensures that interfaces are open enough to be extended in later releases)||BorneMace|
|PRSteward see PRIssues|
|WebSteward In charge of web site maintenance|
In the same vein as the above, I would like to propose a ProjectSteward.
This is a call for volunteers.
- IainLowe 19 Jan 99
Last summary 7-Feb-1999, by MarkAMeyer. You can have a look at the original page at OldStewards.