> I'm not very familiar with the Gnome team, but isn't this just a resource problem?
How much time that is spent on packaging, documenting existing features, building communication systems, and doing cool new features is indeed hard resource questions for a project manager. Then there is policy questions which effect resources.
Python demands PEPs to be written before changes is considered. That demand for PEPs is less a resource question, and more a policy question. It forces developer to write down in words what they try to accomplish with a change, and also write down what effect it has on users.
In my opinion, the community reaction to gnome3 is not very surprising. Its a result of "less restrictive" developer process and few efforts into mitigation of community outrage. I can only hope they will find some insight from other projects, and start to handle feature changes with more user awareness.
How much time that is spent on packaging, documenting existing features, building communication systems, and doing cool new features is indeed hard resource questions for a project manager. Then there is policy questions which effect resources.
Python demands PEPs to be written before changes is considered. That demand for PEPs is less a resource question, and more a policy question. It forces developer to write down in words what they try to accomplish with a change, and also write down what effect it has on users.
In my opinion, the community reaction to gnome3 is not very surprising. Its a result of "less restrictive" developer process and few efforts into mitigation of community outrage. I can only hope they will find some insight from other projects, and start to handle feature changes with more user awareness.