Mathias Bauer wrote: > Frank Schönheit - Sun Microsystems Germany wrote: > > > I'd say we need a set of highly proficient and highly respected > > architects, whose opinion should, at least, be weighted high. > > No, please not! > Hi Mathias,
FWICT Frank was joking here. ;) > Of course (as for every code change) you should do that accountably and > talk to other developers that will be influenced by your changes and you > should try to make your changes in a way that the potential work of > others is minimized. > > But please no processes, not gate keeper etc. Let things evolve and > assume that all participants in the development process act reasonably. > A bad API change should be treated as any other code change or patch > that we have nowadays: if you see a problem with it, raise your concerns > and discuss. > Hm. I'm totally with you regarding the dislike of processes. But in contrast to normal code changes, which usually happen on the sole discretion of a single dev, API changes should *require* discussion. Cheers, -- Thorsten --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
