GovernanceIssues: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 14: Line 14:
* [http://groups.google.com/group/mozilla.governance/browse_thread/thread/7d418189694b88d1# mozilla.governance thread on mailing list spam]
* [http://groups.google.com/group/mozilla.governance/browse_thread/thread/7d418189694b88d1# mozilla.governance thread on mailing list spam]


Status: [[Discussion_Forums/Proposal|Plan written]], [https://bugzilla.mozilla.org/show_bug.cgi?id=598060 bug filed]. We now have 10 or 12 groups switched over, and a contact with Google, but we aren't quite there yet - there are unresolved problems with how the moderation is working.  
Status: [[Discussion_Forums/Proposal|Plan written]], [https://bugzilla.mozilla.org/show_bug.cgi?id=598060 bug filed]. We now have 10 or 12 groups switched over, and a contact with Google, but we aren't quite there yet - there are unresolved problems with how the moderation is working. rbryce in IT is actively working on improving the situation.


Next Steps: Gerv to discuss with justdave at the All Hands.
Next Steps: wait for rbryce to report back.


===Mozilla Code Not In Our Repos===
===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
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?


Next Steps: [https://bugzilla.mozilla.org/show_bug.cgi?id=619576 Bug filed] with legal. Email exchange with mitchell and sayrer. Possibility of discussion at next All Hands.
Next Steps: None planned at the moment.


===Triage Stale Reviews===
===Triage Stale Reviews===
Line 30: Line 30:
* [http://spreadsheets.google.com/ccc?key=pcR-hFir9x0Pn-TxV3j2Zbg Spreadsheet mapping Bugzilla components to modules], prepared by Dirkjan Ochtman.
* [http://spreadsheets.google.com/ccc?key=pcR-hFir9x0Pn-TxV3j2Zbg Spreadsheet mapping Bugzilla components to modules], prepared by Dirkjan Ochtman.


Status: Bugzilla modules have been added to the Module Owners List. But we need to fix that list to be more complete before we can start hassling people.
Status: Bugzilla now whines about outstanding requests on a weekly basis, and data is being captured to see if this has significant effect on the queue.
 
Next Steps: Write scripts to parse module owners list, and use the information to find out the size and scope of the problem.


===Change Bugzilla Workflow===
===Change Bugzilla Workflow===
Line 44: Line 42:
Other suggestions: open up EXPIRED, or collapse EXPIRED, WONTFIX and INVALID into INACTIVE or some other word.
Other suggestions: open up EXPIRED, or collapse EXPIRED, WONTFIX and INVALID into INACTIVE or some other word.


Status: shaver wants a wider discussion than we have had so far; Gerv to find out what that means in practice.
Status: there are two proposals - a [[BMO/Workflow_Proposal|safe-ish one]] and a [[BMO/Workflow_Proposal_2|more radical one]]. Just waiting for Gerv to have time to push this.


===Shouldn't-Be-Private Mailing Lists===
===Shouldn't-Be-Private Mailing Lists===
Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925

edits