Thorsten Behrens wrote:
Mathias Bauer wrote:
>
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.
No problem with that. If in the past someone made an internal C++ API
change I assume that discussions have happened also in many cases. Of
course we can make prior announcements and discussions mandatory for UNO
API or language binding changes. Detecting such changes is easy (we
already do it for UNO APIs) and so changes without discussion shouldn't
come unnoticed.
But I don't want to have any kind of voting/judgement and so forth. For
me API changes are not different to other code changes in this regard:
if we trust developers that have commit rights, we should also trust
them to act reasonably when it comes to API changes. If developers
repeatedly act against the "common sense" of the whole group (either
when making API changes or otherwise), they risk to lose their commit
rights. Until then we should be able to work together without too much
procedural overhead.
Regards,
Mathias
--
Mathias Bauer (mba) - Project Lead OpenOffice.org Writer
OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS
Please don't reply to "nospamfor...@gmx.de".
I use it for the OOo lists and only rarely read other mails sent to it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org
For additional commands, e-mail: dev-h...@api.openoffice.org
