diff options
| author | Brian Grant <bgrant0607@users.noreply.github.com> | 2017-08-11 07:17:54 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-08-11 07:17:54 -0700 |
| commit | 5a2bf2e3cc93877875745e62e8e50ebb47e62767 (patch) | |
| tree | 9748ac14b6455645c860a14ea644b8a488ae11cc | |
| parent | c45dd1ff571c517e9c15037367683e68bf2de3e4 (diff) | |
Expand backlog with items from Bootstrap meetings
| -rw-r--r-- | committee-steering/backlog.md | 20 |
1 files changed, 19 insertions, 1 deletions
diff --git a/committee-steering/backlog.md b/committee-steering/backlog.md index cbf54879..19b2c95f 100644 --- a/committee-steering/backlog.md +++ b/committee-steering/backlog.md @@ -6,5 +6,23 @@ This is a backlog of items that the steering committee needs to either handle or ## Backlog Items - Check the governance documents into the community repo -- Use the latest version of Code of Conduct Committee and documenting enforcement +- Update the Code of Conduct Committee to a more recent version, documenting enforcement, broaden coverage + beyond maintainers and committers, coding activities, and project/public spaces, specify our own reporting + path, clarify the policy on employer notification and who else may be involved, decide what should + be shared with the accused - Document resources that the community has and make sure they have a home: releases, twitter handles, etc +- Find homes for unowned areas of the project, such as the build system +- SIG charter template, including suggested governance and minimum required intra-SIG governance, its scope + (topics, subsystems, code repos and directories), responsibilities, areas of authority, how members and roles + of authority/leadership are selected/granted, how decisions are made, and how conflicts are resolved +- Formalize the concept of subprojects +- Decide how/whether ecosystem subprojects (e.g., kops, helm) are governed differently +- Resolve the disconnect between code organization (OWNERS, maintainers) and people organization (SIGs) +- Update incubator process to explain new GitHub organization strategy +- Explicitly delegate areas to SIGs +- Escalation process +- Fund-requesting and budget processes +- Committee decision-making process (e.g., modified lazy consensus) and quorum requirement +- Improve/expand definition of members of standing +- Identify who is responsible for evolving the governance going forward and how changes will be approved +- Do we need user groups? |