IOW I don't want to wait for approval for something I believe does not have any major impact. I am not going to wait a couple of days before I am allowed to do it. The moment has passed and I probably will spend my time in some other way.
The point is that, as a member in an open source community, you are expected to communicate changes. Minor changes are generally fine, except if you do them on a large scale, when it may impact (or conflict with) code of others. In that case, you should communicate in advance if possible, so people know of the change.
I have no issues with the changes, but it did take me a good amount of time to review them. And yes, I have to review them. And yes, I found issues, or at least I had questions regarding changes.
Committers in MMBase get a certain amount of trust. But we also expect a certain amount of responsibility. This means a willingness to communicate with others on changes and ideas. None of this is required to take long or get into details. But if you are a part of a community, your are expected to interact, and sometimes that leads to discussions or delay, which is unfortunate, but a part of the process.
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Anything worth doing is worth overdoing." _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
