{"action":"created","issue":{"url":"https://api.github.com/repos/coredns/coredns/issues/2112","repository_url":"https://api.github.com/repos/coredns/coredns","labels_url":"https://api.github.com/repos/coredns/coredns/issues/2112/labels{/name}","comments_url":"https://api.github.com/repos/coredns/coredns/issues/2112/comments","events_url":"https://api.github.com/repos/coredns/coredns/issues/2112/events","html_url":"https://github.com/coredns/coredns/pull/2112","id":362245517,"node_id":"MDExOlB1bGxSZXF1ZXN0MjE3MDE3NTEx","number":2112,"title":"initiate a project  Governance document","user":{"login":"fturib","id":19315664,"node_id":"MDQ6VXNlcjE5MzE1NjY0","avatar_url":"https://avatars1.githubusercontent.com/u/19315664?v=4","gravatar_id":"","url":"https://api.github.com/users/fturib","html_url":"https://github.com/fturib","followers_url":"https://api.github.com/users/fturib/followers","following_url":"https://api.github.com/users/fturib/following{/other_user}","gists_url":"https://api.github.com/users/fturib/gists{/gist_id}","starred_url":"https://api.github.com/users/fturib/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fturib/subscriptions","organizations_url":"https://api.github.com/users/fturib/orgs","repos_url":"https://api.github.com/users/fturib/repos","events_url":"https://api.github.com/users/fturib/events{/privacy}","received_events_url":"https://api.github.com/users/fturib/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2018-09-20T15:35:59Z","updated_at":"2018-09-24T14:49:38Z","closed_at":null,"author_association":"MEMBER","pull_request":{"url":"https://api.github.com/repos/coredns/coredns/pulls/2112","html_url":"https://github.com/coredns/coredns/pull/2112","diff_url":"https://github.com/coredns/coredns/pull/2112.diff","patch_url":"https://github.com/coredns/coredns/pull/2112.patch"},"body":"<!--\r\nThank you for contributing to CoreDNS!\r\nPlease provide the following information to help us make the most of your pull request:\r\n-->\r\n\r\n### Why is this pull request needed and what does it do?\r\nIn order to graduate on last level inside CNCF organization, we need to clarify our GOVERNANCE rules.\r\n\r\n### Description\r\n\r\nOn advise of @caniszczyk , I started with a copy of the [governance doc from fluentd](https://github.com/fluent/fluentd/blob/master/GOVERNANCE.md), which, itself is extracted from [Kubernetes' governance doc](https://github.com/kubernetes/community/blob/master/governance.md).\r\nThen I tuned the text to adapt to CoreDNS project.\r\n\r\n**Please pay attention to these points:**\r\n\r\n1- MAINTAINERS are defined as the individuals assigned to the team 'maintainers' (from Github project). It is not the same as Reviewers or Approvers defined into OWNER.md\r\n\r\n2- VOTE is defined by Organization + individual maintainers. This vote would be used to agree on a direction to the project. I am not sure, so far, it was used formerly. We may want to be able to have a 2/3 majority when it comes to vote. Which means a limited number of MAINTAINERS that are really focus on CoreDNS project. (as of today we have  2 Orgs + 2 individuals).\r\n\r\n3- I made up the content of the paragraph \"Projects\". We may want to tune that description. \r\n\r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/coredns/coredns/issues/comments/424002031","html_url":"https://github.com/coredns/coredns/pull/2112#issuecomment-424002031","issue_url":"https://api.github.com/repos/coredns/coredns/issues/2112","id":424002031,"node_id":"MDEyOklzc3VlQ29tbWVudDQyNDAwMjAzMQ==","user":{"login":"fturib","id":19315664,"node_id":"MDQ6VXNlcjE5MzE1NjY0","avatar_url":"https://avatars1.githubusercontent.com/u/19315664?v=4","gravatar_id":"","url":"https://api.github.com/users/fturib","html_url":"https://github.com/fturib","followers_url":"https://api.github.com/users/fturib/followers","following_url":"https://api.github.com/users/fturib/following{/other_user}","gists_url":"https://api.github.com/users/fturib/gists{/gist_id}","starred_url":"https://api.github.com/users/fturib/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fturib/subscriptions","organizations_url":"https://api.github.com/users/fturib/orgs","repos_url":"https://api.github.com/users/fturib/repos","events_url":"https://api.github.com/users/fturib/events{/privacy}","received_events_url":"https://api.github.com/users/fturib/received_events","type":"User","site_admin":false},"created_at":"2018-09-24T14:49:38Z","updated_at":"2018-09-24T14:49:38Z","author_association":"MEMBER","body":"for MAINTAINERS, looks like we may need here to be more clear on the process, and have a way to step-up and step-down for the MAINTAINERS that avoid friction whenever possible. Which means knowing in advance the responsibilities and the rules to keep a good list of active MAINTAINERS \r\n\r\n\r\n## MAINTAINERS change triggered by PRs and votes\r\nThere is a specific file MAINTAINERS.md that we need to modify each time there is a change in the list of maintainers. Most likely there will need a vote for approval before merging.\r\n\r\n## MAINTAINERS responsibilities\r\n* participate to the votes. On each call to vote, the MAINTAINER cannot remain silent. It either vote YES, either vote NO, either provide a comment for no decision. A vote is open for 2 weeks, unless it reaches an agreement before that delay.\r\n\r\n* have a significant involvement in the project, measured by 'activity'.\r\n\r\n## NEW MAINTAINERS\r\n- Any reviewer that have the required level activity, that make the request can be elected as MAINTAINERS if it get the needed  2/3 vote of existing maintainers\r\n- a former MAINTAINER can also asked to re-added to the list with the same process as for a reviewer\r\n\r\n## STEPPING DOWN MAINTAINER\r\n- Volunteering (no more personal time to involve in the project). Need a PR, but no need for vote.\r\n- After an evaluation of activity, Maintainers below the level are automatically proposed for removing from maintainers. Need vote. And vote can be refused if other maintainer wills it after the failing maintainers is providing explanations.\r\n- specific divergence in directions in the project. Need vote.\r\n\r\nWhatever the reason, a former maintainer is always part of the list of 'emeritus maintainers'.\r\nHowever he is removed from the Gihub 'maintainers' list, and lost its 'owner' privilege on the github project.\r\n\r\n## MEASURING ACTIVITY\r\n- **Voting** : it is important that every MAINTAINERS participate actively to the votes. \r\n=> MAINTAINERS should not miss more than 2 votes in a row (or 2 votes since last evaluation of activity ?)\r\n- **Project activity**: I guess we can get an easy measure from Github stats (need to be easy to collect and neutral statistic). We need an average of XX events per month.\r\n\r\n_NOTE: for instance, k8s just provided a minimum of 50 event of activity on the repo during the last year to have the right to vote for the steering committee._\r\n\r\n## TRIGGERING EVALUATION OF ACTIVITY\r\n- by default evaluation happen every 3 months.\r\n- an evaluation should be trigger when we do not reach to get enough total votes. When a PR with vote  as not enough feedback to take a decision.\r\n\r\nNOTE: Change in measuring activity and decisions can still be made, using a PR with vote on the \"GOVERNANCE.md\" file.\r\n\r\n\r\n\r\n"}}
{"actor":{"display_login":"fturib"}}