Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925
edits
GovernanceIssues: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
Next Steps: discuss with Mitchell. | Next Steps: discuss with Mitchell. | ||
"Create modules when there is a specific level of responsibility, authority and decision making that it would be helpful to invest in a person." - Mitchell | |||
"Makes modules to unambiguously place things in the arena of stuff which we apply open source and transparent principles to." - Gerv | |||
Module owner for transparency? | |||
What are the policies about acceptance or rejection of extensions? How are they determined? Where can the community find them? How might they change? | |||
Mitchell to talk to Nick | |||
Module owner for monitoring/tracking community involvement across activities. Define the metrics. Asa and Daniel? | |||
Mitchell to drive | |||
No actions for Gerv | |||
===Commit Access Policies: Dormant Accounts=== | ===Commit Access Policies: Dormant Accounts=== | ||
| Line 24: | Line 38: | ||
Next Steps: get updated list of active accounts from IT; disable inactive accounts. | Next Steps: get updated list of active accounts from IT; disable inactive accounts. | ||
Blog a warning; this is what you do if you have problems with your account. Refined a few times, but there are edge cases. | |||
Beginning of a work day | |||
===Commit Access Policies: Harmonization=== | ===Commit Access Policies: Harmonization=== | ||
| Line 34: | Line 52: | ||
Next Steps: public review (ongoing). | Next Steps: public review (ongoing). | ||
Ascher: simple enough? | |||
===Committer's Agreement=== | ===Committer's Agreement=== | ||
| Line 130: | Line 150: | ||
Resolution: mconnor updated the super-review policy. | Resolution: mconnor updated the super-review policy. | ||
*** API project debrief; what's good, what was difficult, how can I be more effective. | |||