GovernanceIssues

This is a list of open Mozilla community governance issues that Gerv may be attempting to resolve.

Here's a first cut. scan bugzilla Mark's message in .governance Current status for each Recommended next step Link to most relevant bug/thread -> wiki

Monday Meeting

Clarify the purpose of the meeting, and determine whether the current timing is optimal.

Commit Access Policies

Mitchell drove through the main part of the policy, but work remains to be done on dormant accounts.

Code Review Policies

Which policies apply to which repositories? Do we want to harmonise?

Non-Code Modules

Define what the modules are, and find owners for them. Work out what makes a good module, and who makes a good module owner. Mark says: make sure it's not just a mirror of Mozilla staffing structure, and not just an addition to a job title. Examples: SFX, mozilla.org (content vs. technical?).

Also contains the question of whether we need to separate policy creation and implementation.

Bug Triage

Go through open governance bugs and attempt to resolve - either immediately, or via this list.

Module Owners List

Make it hackable, parseable, easier to maintain and therefore more accurate.

Stale Reviews

Review requests remain open and unloved in Bugzilla. This is bad for the (often new) contributors who make patches and see them ignored. Fixing the Module Owners List and mapping it to Bugzilla components allows us to nag module owners about their reviews - cancel, do or delegate.

Committer's Agreement=

Finish the transition to the new agreement by nagging those who have not signed and eventually disabling accounts.

Discussion Forums

There are several issues with the current technical implementation - the unresponsiveness of Google re: Google Groups and so on. Need to look at whether to take the web interface part back in house, and/or put in place other anti-spam measures.