{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/community/issues/28","repository_url":"https://api.github.com/repos/kubernetes/community","labels_url":"https://api.github.com/repos/kubernetes/community/issues/28/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/community/issues/28/comments","events_url":"https://api.github.com/repos/kubernetes/community/issues/28/events","html_url":"https://github.com/kubernetes/community/issues/28","id":165582488,"number":28,"title":"Kubernetes Elders Council - proposal","user":{"login":"sarahnovotny","id":127370,"avatar_url":"https://avatars.githubusercontent.com/u/127370?v=3","gravatar_id":"","url":"https://api.github.com/users/sarahnovotny","html_url":"https://github.com/sarahnovotny","followers_url":"https://api.github.com/users/sarahnovotny/followers","following_url":"https://api.github.com/users/sarahnovotny/following{/other_user}","gists_url":"https://api.github.com/users/sarahnovotny/gists{/gist_id}","starred_url":"https://api.github.com/users/sarahnovotny/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sarahnovotny/subscriptions","organizations_url":"https://api.github.com/users/sarahnovotny/orgs","repos_url":"https://api.github.com/users/sarahnovotny/repos","events_url":"https://api.github.com/users/sarahnovotny/events{/privacy}","received_events_url":"https://api.github.com/users/sarahnovotny/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":{"login":"sarahnovotny","id":127370,"avatar_url":"https://avatars.githubusercontent.com/u/127370?v=3","gravatar_id":"","url":"https://api.github.com/users/sarahnovotny","html_url":"https://github.com/sarahnovotny","followers_url":"https://api.github.com/users/sarahnovotny/followers","following_url":"https://api.github.com/users/sarahnovotny/following{/other_user}","gists_url":"https://api.github.com/users/sarahnovotny/gists{/gist_id}","starred_url":"https://api.github.com/users/sarahnovotny/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sarahnovotny/subscriptions","organizations_url":"https://api.github.com/users/sarahnovotny/orgs","repos_url":"https://api.github.com/users/sarahnovotny/repos","events_url":"https://api.github.com/users/sarahnovotny/events{/privacy}","received_events_url":"https://api.github.com/users/sarahnovotny/received_events","type":"User","site_admin":false},"assignees":[{"login":"sarahnovotny","id":127370,"avatar_url":"https://avatars.githubusercontent.com/u/127370?v=3","gravatar_id":"","url":"https://api.github.com/users/sarahnovotny","html_url":"https://github.com/sarahnovotny","followers_url":"https://api.github.com/users/sarahnovotny/followers","following_url":"https://api.github.com/users/sarahnovotny/following{/other_user}","gists_url":"https://api.github.com/users/sarahnovotny/gists{/gist_id}","starred_url":"https://api.github.com/users/sarahnovotny/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sarahnovotny/subscriptions","organizations_url":"https://api.github.com/users/sarahnovotny/orgs","repos_url":"https://api.github.com/users/sarahnovotny/repos","events_url":"https://api.github.com/users/sarahnovotny/events{/privacy}","received_events_url":"https://api.github.com/users/sarahnovotny/received_events","type":"User","site_admin":false}],"milestone":null,"comments":5,"created_at":"2016-07-14T14:58:12Z","updated_at":"2016-07-14T16:39:31Z","closed_at":null,"body":"**Problem**:  As the Kubernetes project has pivoted from a Company run open source project to a Foundation owned and community inclusive project, there have been growing pains.  The perceptions of Googler who have more structure and visibility into most of the operational aspects of the projects differ greatly from the perspectives of most of the community members - particularly new project contributors and interested project contributors.  Google intentionally chose not to have a BDFL for all the down sides that has, but a confused “power vacuum” has evolved.  The organic structure appears to a newcomer to be opaque, relationship based and full of cronyism.  There is no clear starting point progression in the project or escalation for conflict resolution etc.  Long standing (primarily Google employed) contributors feel that newcomers are all focused on specific features and aren’t stepping up to contribute to the more material and growing backlog of housekeeping, management, and organizational health tasks.\r\n\r\n**Goals** :  Establish clear cultural, technical, and team leadership as well as act as an escalation point with a “last say” on any contentious issues.   \r\n\r\n**Requirements**: This group should have a long standing history with the project,  good people management skills, strong technical vision for the project and empathy for the user and FOSS developer perspective.  \r\n\r\n**Instantiation**:   The first seed incarnation of the Elders will be voted in as a slate of 3 Elders with a 2 year term (ending August 2018) through the Community Meeting and on the mailing list kubernetes-dev@.  During the first year, the Elders will add 2 members (with a term ending August 2017) to their group for a total of 5 members.\r\n\r\n**Refreshes**:  In August each year subsequent the community will vote on the seats which term out.  All positions voted on will have a 2 year term.  The voting will be handled using Condorcet voting and a service such as [CIVS](http://civs.cs.cornell.edu/).  Voter eligibility must be defined, and will require registration during a public registration period.  Nominations for candidates will be accepted for one week prior to the voting period.   \r\n\r\n**Resignations**:  In the event that an elder resigns, the remaining elders will appoint a successor to serve until the next scheduled vote.\r\n\r\n**Known Issues**:  Elder nomination process. Voter eligibility.\r\n"},"comment":{"url":"https://api.github.com/repos/kubernetes/community/issues/comments/232721057","html_url":"https://github.com/kubernetes/community/issues/28#issuecomment-232721057","issue_url":"https://api.github.com/repos/kubernetes/community/issues/28","id":232721057,"user":{"login":"philips","id":33544,"avatar_url":"https://avatars.githubusercontent.com/u/33544?v=3","gravatar_id":"","url":"https://api.github.com/users/philips","html_url":"https://github.com/philips","followers_url":"https://api.github.com/users/philips/followers","following_url":"https://api.github.com/users/philips/following{/other_user}","gists_url":"https://api.github.com/users/philips/gists{/gist_id}","starred_url":"https://api.github.com/users/philips/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/philips/subscriptions","organizations_url":"https://api.github.com/users/philips/orgs","repos_url":"https://api.github.com/users/philips/repos","events_url":"https://api.github.com/users/philips/events{/privacy}","received_events_url":"https://api.github.com/users/philips/received_events","type":"User","site_admin":false},"created_at":"2016-07-14T16:39:30Z","updated_at":"2016-07-14T16:39:30Z","body":"@sarahnovotny thanks for putting this together. Seems like a great start and we do need to sort something out as our alternative to BFDL.\r\n\r\nOne anti-pattern I want to avoid is the \"detached leader\" who shows up just during critical moments but doesn't have the confidence of the community as they aren't regularly engaged. A few ideas on how we might do that:\r\n\r\n1. Ask elders to rotate through planning and managing a major release. This likely looks like the role that @mike-saparov and @idvoretskyi took in the v1.3. Essentially, report to the community hangout feature progress, keep tabs on super critical issues, and do all they can to keep velocity up on the 3 or so super critical items for that release.\r\n2. Ensure that elders remain engaged in the community through Kubernetes community projects, code, mailing list participation, or running of community meetings. By Kubernetes community projects I mean really wide stuff from kubernetes.git to stuff like Brendan's ksql.\r\n3. Make themselves available through office hours on a twice monthly basis to discuss  issues with contributors and maintainers and try and work through tricky core issues in real time."}}
{"actor":{"display_login":"philips"}}