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
