{"action":"created","issue":{"url":"https://api.github.com/repos/nodejs/TSC/issues/59","repository_url":"https://api.github.com/repos/nodejs/TSC","labels_url":"https://api.github.com/repos/nodejs/TSC/issues/59/labels{/name}","comments_url":"https://api.github.com/repos/nodejs/TSC/issues/59/comments","events_url":"https://api.github.com/repos/nodejs/TSC/issues/59/events","html_url":"https://github.com/nodejs/TSC/pull/59","id":139137860,"number":59,"title":"Flatten project, scope TSC, big changes to structure.","user":{"login":"mikeal","id":579,"avatar_url":"https://avatars.githubusercontent.com/u/579?v=3","gravatar_id":"","url":"https://api.github.com/users/mikeal","html_url":"https://github.com/mikeal","followers_url":"https://api.github.com/users/mikeal/followers","following_url":"https://api.github.com/users/mikeal/following{/other_user}","gists_url":"https://api.github.com/users/mikeal/gists{/gist_id}","starred_url":"https://api.github.com/users/mikeal/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mikeal/subscriptions","organizations_url":"https://api.github.com/users/mikeal/orgs","repos_url":"https://api.github.com/users/mikeal/repos","events_url":"https://api.github.com/users/mikeal/events{/privacy}","received_events_url":"https://api.github.com/users/mikeal/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/nodejs/TSC/labels/ctc-agenda","name":"ctc-agenda","color":"5319e7"},{"url":"https://api.github.com/repos/nodejs/TSC/labels/tsc-agenda","name":"tsc-agenda","color":"fbca04"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":23,"created_at":"2016-03-08T00:34:20Z","updated_at":"2016-03-17T01:04:17Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/nodejs/TSC/pulls/59","html_url":"https://github.com/nodejs/TSC/pull/59","diff_url":"https://github.com/nodejs/TSC/pull/59.diff","patch_url":"https://github.com/nodejs/TSC/pull/59.patch"},"body":"Based on the recent TSC meeting and some of the feedback I've gotten on recent issues I've logged I created this initial draft of a new structure.\r\n\r\nThis does a few critical things:\r\n\r\n* Sets the boundary for \"long term project hosting\" under the TSC to projects that are connected to Core development. However, it makes it clear that projects that are connected to Core development may stretch far beyond the needs of Core (evangelism, website, documentation).\r\n* Renames the \"Incubator\" to \"Mentorship\" in order to reduce many false assumptions from Apache's Incubator. This still reserves the ability for the TSC to intervene in projects outside of the above scope, like Express, without assuming the TSC will host them long term. The issue of where to host these projects long term is a question for another day -- there are many options we can explore.\r\n* Flattens all projects and Working Groups under the TSC. The line between what should and should not be under the CTC was always a bit difficult to draw. Flattening makes autonomy more clear and allows the TSC to focus on improving communication and collaboration between the different parts (which the CTC has never done much of because it's so focused on the needs of direct Core development).\r\n\r\nThere's some very good things this accomplishes.\r\n*  It solves the \"blessing projects\" problem. By not hosting projects next to Core we can avoid making them \"official.\"\r\n* It makes the TSC focus on some core problems we're experiencing at scale.\r\n * Automating reporting, communication and transparency for projects and working groups.\r\n * Creating and promoting contribution and governance policies for use both within the TSC and **in the ecosystem**.\r\n * Creating measurements and tools for evaluating project health. First for use within the Foundation but conceptually for use outside it later on.\r\n\r\nThe good thing about flattening this stuff and staying away from a hierarchy is that we do a better and more explicit job of groups being service providers. This allows group to be more effective in this role within the project but also with the broader community.\r\n\r\nWhat is not yet resolved is the question of who is on the TSC. Proportional representation is difficult, anything as simple as \"one rep per project\" ignores the disparity in contributors and scope between projects.\r\n\r\nThis document also isn't enough, there's a lot of other process points in other now irrelevant documents.\r\n\r\nAnd finally, because this is a huge change that effects every group and project it's going to need to reach a consensus among all the sub projects. @nodejs/tsc @nodejs/ctc \r\n\r\n"},"comment":{"url":"https://api.github.com/repos/nodejs/TSC/issues/comments/197629431","html_url":"https://github.com/nodejs/TSC/pull/59#issuecomment-197629431","issue_url":"https://api.github.com/repos/nodejs/TSC/issues/59","id":197629431,"user":{"login":"nebrius","id":1141386,"avatar_url":"https://avatars.githubusercontent.com/u/1141386?v=3","gravatar_id":"","url":"https://api.github.com/users/nebrius","html_url":"https://github.com/nebrius","followers_url":"https://api.github.com/users/nebrius/followers","following_url":"https://api.github.com/users/nebrius/following{/other_user}","gists_url":"https://api.github.com/users/nebrius/gists{/gist_id}","starred_url":"https://api.github.com/users/nebrius/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nebrius/subscriptions","organizations_url":"https://api.github.com/users/nebrius/orgs","repos_url":"https://api.github.com/users/nebrius/repos","events_url":"https://api.github.com/users/nebrius/events{/privacy}","received_events_url":"https://api.github.com/users/nebrius/received_events","type":"User","site_admin":false},"created_at":"2016-03-17T01:04:17Z","updated_at":"2016-03-17T01:04:17Z","body":"Do I remember correctly that intl does website work as well? If so, should they be top level?"}}