GovernanceIssues: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 1: Line 1:
__NOTOC__
__NOTOC__
This is a list of open Mozilla community governance issues that Gerv is working on.
This is a list of open Mozilla community governance issues.


We have a page listing [http://www.mozilla.org/about/policies/ existing policies] (may need updating).
We also have a page listing [http://www.mozilla.org/about/policies/ existing policies].


==Open Issues==
==Open Issues==
Line 57: Line 57:
===Monday Meeting===
===Monday Meeting===


Issue: Clarify the purpose of the meeting, and determine whether the current timing is optimal.  
Issue: the Monday meeting is having an identity crisis. Clarify the purpose and most useful content of the meeting, and determine whether the current timing is optimal.  


* [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/68685672ffb76f6b/37cf986d3962a47 thread in mozilla.dev.planning on moving the meeting time]
* [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/68685672ffb76f6b/37cf986d3962a47 thread in mozilla.dev.planning on moving the meeting time]
Line 63: Line 63:
* [http://groups.google.com/group/mozilla.dev.planning/msg/89fa03e13375ae9f dria's summary of the meeting's purpose]
* [http://groups.google.com/group/mozilla.dev.planning/msg/89fa03e13375ae9f dria's summary of the meeting's purpose]


So Far: Timing has been moved. Gerv has had discussions with surman and beltzner about possible improvements to content and format.
So Far: Timing has been changed. Gerv has had discussions with surman and beltzner about possible improvements to content and format.


Next Steps: Gerv is working on a proposal for change.
Next Steps: Gerv is working on a proposal for change.
Line 103: Line 103:
Issue: Mozilla runs a large number of mailing lists, as well as our public [http://www.mozilla.org/community/developer-forums.html discussion forums]. We should audit that list to make sure no project discussion is private when it should be (at least) read-only public.
Issue: Mozilla runs a large number of mailing lists, as well as our public [http://www.mozilla.org/community/developer-forums.html discussion forums]. We should audit that list to make sure no project discussion is private when it should be (at least) read-only public.


So Far:  
So Far: Gerv wrote a small script to extract a list of possibly-concerning mailing lists from mailman. He has had several iterations of the list from mzeier, refining the script each time.
 
Next Steps: contact the owners of possibly-concerning lists, and ask them politely about the purpose of their list and whether public would be a better option.


==Proposed==
==Proposed==
Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925

edits

Navigation menu