Here's where I think we are.
We have a community that's growing quickly. The volunteers are growing and the employees are growing. As a project we've grown so much that the old way of "everybody scratches their own itch" and we do some coordination is not enough. Also, we're in a very complex and fast-paced competitive space.
My sense is that *all* our decision-making processes are under stress. The module ownership system answers some questions about decisions re particular pieces of code, and some other activities. It doesn't yet answer questions of whole product decisions, of priorities, etc.
We are developing some news ways to integrate the work, and eventually decision-making, of volunteers and employees. (and btw, it's not the case that every employee participates in any given strategy decision. There's too much going on each day for that.) ReMo is one example. Nukeador has made a number of suggestions on this list, and we worked on some at MozCamp.
At MozCamp I also mentioned my goal that some part of the ReMo Council begin providing input to the Boards and management. That's means working with me to figure out what input is the most important, preparing a presentation and supporting materials, and being comfortable to answer questions and have a discussion.
These are all starting points. I don't know what the next "stable state" (meaning a system that needs only tune-up but no major changes) will look like. I don't think there's anything that exists today; we will make something new.
Mitchell _______________________________________________ governance mailing list [email protected] https://lists.mozilla.org/listinfo/governance
