GovernanceIssues: Difference between revisions

GovernanceIssues (view source)

Revision as of 01:14, 14 July 2010

312 bytes added , 14 July 2010

no edit summary

Gerv

Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti

4,925

edits

@@ Line 7: / Line 7: @@
 ==Open Issues==
-===Harmonize and Simplify Commit Access Policy===
-Issue: Our commit access policies are currently very diverse. We should harmonize them and make them consistent, understandable and easy to implement.
-* [[Commit Policy:Current Procedures|reed's long list of what happens now]]
-Status: [http://www.mozilla.org/hacking/commit-access-policy/ new Commit Access Policy] written and implemented, and infrastructure updated to match. However, discussion has been reopened on whether it could be made even simpler.
 ===Improve Module Owners List===
@@ Line 45: / Line 37: @@
 ==Proposed==
+===Mozilla Code Not In Our Repos===
+Issue: recently, Mozilla community members have been storing Mozilla code in repos other than ours (e.g. github, Google Code). Is this a concern from a community, technical or a legal point of view? Possible issues include worrying about stuff being hosted in the cloud, worrying about
+Next Steps: Mitchell to talk to senior engineers about the issue.
 ===Change Bugzilla Workflow===
@@ Line 61: / Line 59: @@
 ==Resolved==
+===Harmonize and Simplify Commit Access Policy===
+Issue: Our commit access policies are currently very diverse. We should harmonize them and make them consistent, understandable and easy to implement.
+* [[Commit Policy:Current Procedures|reed's long list of what happens now]]
+Status: [http://www.mozilla.org/hacking/commit-access-policy/ new Commit Access Policy] written and implemented, and infrastructure updated to match.
 ===Switch To New Committer's Agreement===