> The whole point is not if the work is nice we all agree that > it is and > we thank you for the work the point is that we want more commitors if > we do > that it means more people can at on any random day change 30 > classes as > part of cleanup. That itself is again not a problem unless they all > do it at the same time and they are all done at the high > level of work > you did. The MMC for that reason has to have 'some' idea of what is > going on. This > is the reason why there is a cleanup project and a simple > email to the > projectmanager with a general note of 'i want to make changes on the > whole code > base for imports, scoop etc etc fo the next few days) would have been > enough. This limits the changes over overlapping work of very unlucky > timing and it > also means that lesser commitors (since we want to have more > commitors) > don't get the feeling you can do whatever you like.
What is the reason to have more committors then we have now? There are a lot of people who have the right to commit, but only a few have used it in the last months. This last year does contradict with the remark you make. Some people who were willing to become a committor were denied, because they did not contribute enough as a known mmbase developer. The above is not very pragmatic and realistic. I did the changes in the present where only a few commitors are active on the repository. I don't understand why I should take possible future situations into account in my current actions. I will deal with it when it is there. The timimg of mine was okay I think. Not a lot of new functionality projects are running and one big step in the cleanup project was just finished, And to be very pragrmatic, most of the changes (if not all) would easily be merged by CVS into changed code. > Im sorry but if such simple email to the projectmanager is > too much you > should not work in a opensource community or any other team. You have > to see that in order > to at least have some safeguards at least some communication > is needed > this has nothing to do with your work but a general comment. > MMBase is > a lot more open then for example linux or other big opensource > projects. Last sunday, I chose a different communication approach then, I guess, most prefer. I chose to do the changes first and then inform the community of what I did. I believed it was okay to take this approach, because the repository seemed to be in a quiet state and the timeframe I used between checkout and checkin was very short. Maybe my perception on what a committor is allowed to do on the HEAD is much more loose then it should be. I will keep that in mind next time. > If you feel i am too hard then well lets have a developers meeting on > topics like this since i know the mmc has been having a hard time on > how to handle these issues and how to make them so that we get more > developers get the feeling they are welcome and respected for their > work if you see this as a attack on yourself then something is very > wrong and we need to talk about it as a group. > > Lets not forget the mmc also puts in alot of their private time and > they are not out to get you, like you they want to have a big happy > family of developers, Why do we need more developers? For what do we need them? What issue is the community trying to solve with mmbase at the moment? Mmbase already solved the issue to store content. It is a content toolkit which can be used to build many types of systems. I think it is good to talk about these topics, but not (only) on a developers meeting. This list is viewed by more people then there will be people at meetings. Another advantage to discuss it on the list is that people can respond when they have the time to respond and not when the meeting is held. Nico _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
