I don't think it will be easy and actually it may be unfeasible but I see some good reasons for hope:
* the general discussion/vote would involve all committers and not only PMC members: everyone would be involved in the decision and in the responsibilities/consequences around it * our committers group is made of clever persons that know we are all playing on top of a system that is bigger than us, that is very complex and has been built thanks to the visions and great ideas/skills of others; we have to make sure we do not ruin what we are asked to maintain and improve and, with such a big and complex beast, working together as a group is the only responsible way of achieving this difficult task... on the other hand continuing to think as individuals with our own personal goals and ideas will make a mess of this project soon Jacopo On Mar 1, 2012, at 3:47 PM, Adrian Crum wrote: > You are a lot more optimistic than I am. Despite the best efforts of PMC > members to provide advice/guidance/suggestions, committers still do what they > please. It's worth a try, but I don't have much hope for success. > > -Adrian > > On 3/1/2012 1:48 PM, Jacopo Cappellato wrote: >> On Mar 1, 2012, at 11:39 AM, Adrian Crum wrote: >> >>> I understand the workflow you are suggesting - cut down the size of the >>> existing framework and then switch to something else. In an ideal world we >>> could do that. Unfortunately, we have a lot of committers who believe more >>> is better, so while we're cutting down in one area, someone else will be >>> adding code in another area. >> Yes, I know what you mean: I still think that, if the goal is clear and the >> strategy makes sense (e.g. "simplify/standardize the tools used, for example >> migrate everything from bsh to groovy, and then slim down the current >> framework to the bare minimum technologies used by the official applications >> in order to simplify and renew the code base") we could try to work to get a >> majority approval and a shared strategy and then everyone will have to stick >> to the plan and help to implement it... i.e. working as a community rather >> than as individual with commit rights and different visions. >> >> Jacopo
