I think this list accurately reflects the people that own the code behind the various web pages but we also need to capture the product owners and content owners for it to be accurate.
For example, mozilla.org. Paul McLanahan does an awesome job of coding and maintaining Mozilla.org. If you see a technical issue or see a way you could improve the site, you'd talk to Paul. If you want to add "Mozilla is a nonprofit" to every page on Mozilla.org, you would talk to Jennifer Bertsch, the Mozilla.org product manager. Assuming she thought your proposal had merit she would pull in all the stakeholders, have the discussion and make the decision about whether or not to put "Mozilla is a nonprofit" on every page. If she decides the idea is a good one and we should move forward, she'd work with Paul (and others) to figure out how and when to implement it. So if the module system is supposed to reflect ownership and help guide people to the right people to talk to, I think it would be incomplete to list Paul without listing Jennifer. Stormy On Thu, Apr 11, 2013 at 1:11 PM, <[email protected]> wrote: > Ahoy! > > We have quite a few major web products, properties or services that have > not been properly documented as modules. See list below: > > https://docs.google.com/spreadsheet/ccc?key=0AhiX365xacl1dE5sRzhDUjVRaFEyWElLZlAzWWJ2aUE&usp=sharing > > This has created confusion at times around: > 1. who owns what > 2. how does someone contribute > 3. who do you talk to about issues or suggestions > 4. where is the code? where do I send my pull request? > > As a part of our effort to move toward HA (high-availability) for > multiple pieces of our infrastructure, we've had to clear a lot of this up > so any future "run books" (incident response procedures for a NOC) clearly > outline who is responsible for the health, operation and maintenance of a > particular web property. Since we had to do all of this anyway, many of us > saw this as an opportunity to clean up how module ownership for these web > projects is documented. > > On the bright side, most of the proposed modules have: > 1. owners responsible for them who already fill the role > 2. github repositories, many already with outside contribution (PR's and > forks) > 3. a way to contribute (https://wiki.mozilla.org/Webdev/GetInvolved) > 4. their own bugzilla product or component > 5. ample documentation > > The list includes only important/critical web projects and (hopefully!) > these should not be a surprise. If you have questions or comments I'd like > to discuss! > > Thanks for your time, > Mike > > _______________________________________________ > governance mailing list > [email protected] > https://lists.mozilla.org/listinfo/governance > _______________________________________________ governance mailing list [email protected] https://lists.mozilla.org/listinfo/governance
