{"action":"created","comment":{"url":"https://api.github.com/repos/rust-lang/rfcs/pulls/comments/28932265","id":28932265,"diff_hunk":"@@ -0,0 +1,728 @@\n+- Feature Name: not applicable\n+- Start Date: 2015-02-27\n+- RFC PR: (leave this empty)\n+- Rust Issue: (leave this empty)\n+\n+# Summary\n+\n+This RFC proposes to expand, and make more explicit, Rust's governance\n+structure. It seeks to supplement today's core team with several\n+*subteams* that are more narrowly focused on specific areas of\n+interest.\n+\n+*Thanks to Nick Cameron, Manish Goregaokar, Yehuda Katz, Niko Matsakis and Dave\n+ Herman for many suggestions and discussions along the way.*\n+\n+# Motivation\n+\n+Rust's governance has evolved over time, perhaps most dramatically\n+with the introduction of the RFC system -- which has itself been\n+tweaked many times. RFCs have been a major boon for improving design\n+quality and fostering deep, productive discussion. It's something we\n+all take pride in.\n+\n+That said, as Rust has matured, a few growing pains have emerged.\n+\n+We'll start with a brief review of today's governance and process,\n+then discuss what needs to be improved.\n+\n+## Background: today's governance structure\n+\n+Rust is governed by a\n+[core team](https://github.com/rust-lang/rust-wiki-backup/blob/master/Note-core-team.md),\n+which is ultimately responsible for all decision-making in the\n+project. Specifically, the core team:\n+\n+* Sets the overall direction and vision for the project;\n+* Sets the priorities and release schedule;\n+* Makes final decisions on RFCs.\n+\n+The core team currently has 8 members, including some people working\n+full-time on Rust, some volunteers, and some production users.\n+\n+Most technical decisions are decided through the\n+[RFC process](https://github.com/rust-lang/rfcs#what-the-process-is).\n+RFCs are submitted for essentially all changes to the language,\n+most changes to the standard library, and\n+[a few other topics](https://github.com/rust-lang/rfcs#when-you-need-to-follow-this-process).\n+RFCs are either closed immediately (if they are clearly not viable),\n+or else assigned a *shepherd* who is responsible for keeping the\n+discussion moving and ensuring all concerns are responded to.\n+\n+The final decision to accept or reject an RFC is made by the core\n+team. In many cases this decision follows after many rounds of\n+consensus-building among all stakeholders for the RFC. In the end,\n+though, most decisions are about weighting various tradeoffs, and the\n+job of the core team is to make the final decision about such\n+weightings in light of the overall direction of the language.\n+\n+## What needs improvement\n+\n+At a high level, we need to improve:\n+\n+* Process scalability.\n+* Stakeholder involvement.\n+* Clarity/transparency.\n+* Moderation processes.\n+\n+Below, each of these bullets is expanded into a more detailed analysis\n+of the problems. These are the problems this RFC is trying to\n+solve. The \"Detailed Design\" section then gives the actual proposal.\n+\n+### Scalability: RFC process\n+\n+In some ways, the RFC process is a victim of its own success: as the\n+volume and depth of RFCs has increased, it's harder for the entire\n+core team to stay educated and involved in every RFC. The\n+[shepherding process](https://github.com/rust-lang/rfcs#the-role-of-the-shepherd)\n+has helped make sure that RFCs don't fall through the cracks, but even\n+there it's been hard for the relatively small number of shepherds to\n+keep up (on top of the other work that they do).\n+\n+Part of the problem, of course, is due to the current push toward 1.0,\n+which has both increased RFC volume and takes up a great deal of\n+attention from the core team. But after 1.0 is released, the community\n+is likely to grow significantly, and feature requests will only\n+increase.\n+\n+Growing the core team over time has helped, but there's a practical\n+limit to the number of people who are jointly making decisions and\n+setting direction.\n+\n+A distinct problem in the other direction has also emerged recently: we've\n+slowly been requiring RFCs for increasingly minor changes. While it's important\n+that user-facing changes and commitments be vetted, the process has started to\n+feel heavyweight (especially for newcomers), so a recalibration may be in order.\n+\n+We need a way to scale up the RFC process that:\n+\n+* Ensures each RFC is thoroughly reviewed by several people with\n+  interest and expertise in the area, but with different perspectives\n+  and concerns.\n+\n+* Ensures each RFC continues moving through the pipeline at a\n+  reasonable pace.\n+\n+* Ensures that accepted RFCs are well-aligned with the values, goals,\n+  and direction of the project, and with other RFCs (past, present,\n+  and future).\n+\n+* Ensures that simple, uncontentious changes can be made quickly, without undue\n+  process burden.\n+\n+### Scalability: areas of focus\n+\n+In addition, there are increasingly areas of important work that are\n+only loosely connected with decisions in the core language or APIs:\n+tooling, documentation, infrastructure, for example. These areas all\n+need leadership, but it's not clear that they require the same degree\n+of global coordination that more \"core\" areas do.\n+\n+These areas are only going to increase in number and importance, so we\n+should remove obstacles holding them back.\n+\n+### Stakeholder involvement\n+\n+RFC shepherds are intended to reach out to \"stakeholders\" in an RFC,\n+to solicit their feedback. But that is different from the stakeholders\n+having a direct role in decision making.\n+\n+To the extent practical, we should include a diverse range of\n+perspectives in both design and decision-making, and especially\n+include people who are most directly affected by decisions: users.\n+\n+We have taken some steps in this direction by diversifying the core\n+team itself, but (1) members of the core team by definition need to\n+take a balanced, global view of things and (2) the core team should\n+not grow too large. So some other way of including more stakeholders\n+in decisions would be preferable.\n+\n+### Clarity and transparency\n+\n+Despite many steps toward increasing the clarity and openness of\n+Rust's processes, there is still room for improvement:\n+\n+* The priorities and values set by the core team are not always\n+  clearly communicated today. This in turn can make the RFC process\n+  seem opaque, since RFCs move along at different speeds (or are even\n+  closed as postponed) according to these priorities.\n+\n+  At a large scale, there should be more systematic communication\n+  about high-level priorities. It should be clear whether a given RFC\n+  topic would be considered in the near term, long term, or\n+  never. Recent blog posts about the 1.0 release and stabilization\n+  have made a big step in this direction. After 1.0, as part of the\n+  regular release process, we'll want to find some regular cadence for\n+  setting and communicating priorities.\n+\n+  At a smaller scale, it is still the case that RFCs fall through the\n+  cracks or have unclear statuses (see Scalability problems\n+  above). Clearer, public tracking of the RFC pipeline would be a\n+  significant improvement.\n+\n+* The decision-making process can still be opaque: it's not always\n+  clear to an RFC author exactly when and how a decision on the RFC\n+  will be made, and how best to work with the team for a favorable\n+  decision. We strive to make core team meetings as *uninteresting* as\n+  possible (that is, all interesting debate should happen in public\n+  online communication), but there is still room for being more\n+  explicit and public.\n+\n+### Community norms and the Code of Conduct\n+\n+Rust's design process and community norms are closely intertwined. The\n+RFC process is a joint exploration of design space and tradeoffs, and\n+requires consensus-building. The process -- and the Rust community --\n+is at its best when all participants recognize that\n+\n+> ... people have differences of opinion and that every design or\n+> implementation choice carries a trade-off and numerous costs. There\n+> is seldom a right answer.\n+\n+This and other important values and norms are recorded in the\n+[project code of conduct (CoC)](http://www.rust-lang.org/conduct.html),\n+which also includes language about harassment and marginalized groups.\n+\n+Rust's community has long upheld a high standard of conduct, and has\n+earned a reputation for doing so.\n+\n+However, as the community grows, as people come and go, we must\n+continually work to maintain this standard. Usually, it suffices to\n+lead by example, or to gently explain the kind of mutual respect that\n+Rust's community practices. Sometimes, though, that's not enough, and\n+explicit moderation is needed.\n+\n+One problem that has emerged with the CoC is the lack of clarity about\n+the mechanics of moderation:\n+\n+* Who is responsible for moderation?\n+* What about conflicts of interest? Are decision-makers also moderators?\n+* How are moderation decisions reached? When are they unilateral?\n+* When does moderation begin, and how quickly should it occur?\n+* Does moderation take into account past history?\n+* What venues does moderation apply to?\n+\n+Answering these questions, and generally clarifying how the CoC is viewed and\n+enforced, is an important step toward scaling up the Rust community.\n+\n+# Detailed design\n+\n+The basic idea is to supplement the core team with several \"subteams\". Each\n+subteam is focused on a specific area, e.g., language design or libraries. Most\n+of the RFC review process will take place within the relevant subteam, scaling\n+up our ability to make decisions while involving a larger group of people in\n+that process.\n+\n+To ensure global coordination and a strong, coherent vision for the project as a\n+whole, **each subteam is led by a member of the core team**.\n+\n+## Subteams\n+\n+**The primary roles of each subteam are**:\n+\n+* Shepherding RFCs for the subteam area. As always, that means (1) ensuring that\n+  stakeholders are aware of the RFC, (2) working to tease out various design\n+  tradeoffs and alternatives, and (3) helping build consensus.\n+\n+* Accepting or rejecting RFCs in the subteam area.\n+\n+* Setting policy on what changes in the subteam area require RFCs, and reviewing\n+  direct PRs for changes that do not require an RFC.\n+\n+* Delegating *reviewer rights* for the subteam area. The ability to `r+` is not\n+  limited to team members, and in fact earning `r+` rights is a good stepping\n+  stone toward team membership. Each team should set reviewing policy, manage\n+  reviewing rights, and ensure that reviews take place in a timely manner.\n+  (Thanks to Nick Cameron for this suggestion.)\n+\n+Subteams make it possible to involve a larger, more diverse group in the\n+decision-making process. In particular, **they should involve a mix of**:\n+\n+* Rust project leadership, in the form of at least one core team member (the\n+  leader of the subteam).\n+\n+* Area experts: people who have a lot of interest and expertise in the subteam\n+  area, but who may be far less engaged with other areas of the project.\n+\n+* Stakeholders: people who are strongly affected by decisions in the\n+  subteam area, but who may not be experts in the design or\n+  implementation of that area. *It is crucial that some people heavily\n+  using Rust for applications/libraries have a seat at the table, to\n+  make sure we are actually addressing real-world needs.*\n+\n+Members should have demonstrated a good sense for design and dealing with\n+tradeoffs, an ability to work within a framework of consensus, and of course\n+sufficient knowledge about or experience with the subteam area. Leaders should\n+in addition have demonstrated exceptional communication, design, and people\n+skills. They must be able to work with a diverse group of people and help lead\n+it toward consensus and execution.\n+\n+Each subteam is led by a member of the core team. **The leader is responsible for**:\n+\n+* Setting up the subteam:\n+\n+    * Deciding on the initial membership of the subteam (in consultation with\n+      the core team). Once the subteam is up and running.\n+\n+    * Working with subteam members to determine and publish subteam policies and\n+      mechanics, including the way that subteam members join or leave the team\n+      (which should be based on subteam consensus).\n+\n+* Communicating core team vision downward to the subteam.\n+\n+* Alerting the core team to subteam RFCs that need global, cross-cutting\n+  attention, and to RFCs that have entered the \"final comment period\" (see below).\n+\n+* Ensuring that RFCs and PRs are progressing at a reasonable rate, re-assigning\n+  shepherds/reviewers as needed.\n+\n+* Making final decisions in cases of contentious RFCs that are unable to reach\n+  consensus otherwise (should be rare).\n+\n+The way that subteams communicate internally and externally is left to each\n+subteam to decide, but:\n+\n+* Technical discussion should take place as much as possible on public forums,\n+  ideally on RFC/PR threads and tagged discuss posts.\n+\n+* Each subteam will have a dedicated\n+  [discuss forum](http://internals.rust-lang.org/) tag.\n+\n+* Subteams should actively seek out discussion and input from stakeholders who\n+  are not members of the team.\n+\n+* Subteams should have some kind of regular meeting or other way of making\n+  decisions. The content of this meeting should be summarized with the rationale\n+  for each decision -- and, as explained below, decisions should generally be\n+  about weighting a set of already-known tradeoffs, not discussing or\n+  discovering new rationale.","path":"text/0000-rust-governance.md","position":298,"original_position":298,"commit_id":"c3f9fda5f1c2f284760c7bd150801eeeb2373708","original_commit_id":"c3f9fda5f1c2f284760c7bd150801eeeb2373708","user":{"login":"nrc","id":762626,"avatar_url":"https://avatars.githubusercontent.com/u/762626?v=3","gravatar_id":"","url":"https://api.github.com/users/nrc","html_url":"https://github.com/nrc","followers_url":"https://api.github.com/users/nrc/followers","following_url":"https://api.github.com/users/nrc/following{/other_user}","gists_url":"https://api.github.com/users/nrc/gists{/gist_id}","starred_url":"https://api.github.com/users/nrc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nrc/subscriptions","organizations_url":"https://api.github.com/users/nrc/orgs","repos_url":"https://api.github.com/users/nrc/repos","events_url":"https://api.github.com/users/nrc/events{/privacy}","received_events_url":"https://api.github.com/users/nrc/received_events","type":"User","site_admin":false},"body":"I think we are more or less in agreement, with perhaps some difference of opinion about where to draw the line in the details.\r\n\r\nI hope that having the subteams will make things easier. Rather than bouncing ideas off a specific person, we have a small group of people to ask if they're interested in the 'idea bouncing stage', and that group of people at least can know which ideas are bouncing around.","created_at":"2015-04-23T02:25:29Z","updated_at":"2015-04-23T02:25:29Z","html_url":"https://github.com/rust-lang/rfcs/pull/1068#discussion_r28932265","pull_request_url":"https://api.github.com/repos/rust-lang/rfcs/pulls/1068","_links":{"self":{"href":"https://api.github.com/repos/rust-lang/rfcs/pulls/comments/28932265"},"html":{"href":"https://github.com/rust-lang/rfcs/pull/1068#discussion_r28932265"},"pull_request":{"href":"https://api.github.com/repos/rust-lang/rfcs/pulls/1068"}}},"pull_request":{"url":"https://api.github.com/repos/rust-lang/rfcs/pulls/1068","id":33576749,"html_url":"https://github.com/rust-lang/rfcs/pull/1068","diff_url":"https://github.com/rust-lang/rfcs/pull/1068.diff","patch_url":"https://github.com/rust-lang/rfcs/pull/1068.patch","issue_url":"https://api.github.com/repos/rust-lang/rfcs/issues/1068","number":1068,"state":"open","locked":false,"title":"RFC: Scaling Rust's Governance","user":{"login":"aturon","id":709807,"avatar_url":"https://avatars.githubusercontent.com/u/709807?v=3","gravatar_id":"","url":"https://api.github.com/users/aturon","html_url":"https://github.com/aturon","followers_url":"https://api.github.com/users/aturon/followers","following_url":"https://api.github.com/users/aturon/following{/other_user}","gists_url":"https://api.github.com/users/aturon/gists{/gist_id}","starred_url":"https://api.github.com/users/aturon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aturon/subscriptions","organizations_url":"https://api.github.com/users/aturon/orgs","repos_url":"https://api.github.com/users/aturon/repos","events_url":"https://api.github.com/users/aturon/events{/privacy}","received_events_url":"https://api.github.com/users/aturon/received_events","type":"User","site_admin":false},"body":"This RFC proposes to expand, and make more explicit, Rust's governance\r\nstructure. It seeks to supplement today's core team with several\r\n*subteams* that are more narrowly focused on specific areas of\r\ninterest.\r\n\r\n*Thanks to Nick Cameron, Manish Goregaokar, Yehuda Katz, Niko Matsakis\r\nand Dave Herman for many suggestions and discussions along the way.*\r\n\r\n[Rendered](https://github.com/aturon/rfcs/blob/rust-governance/text/0000-rust-governance.md)","created_at":"2015-04-17T19:56:19Z","updated_at":"2015-04-23T02:25:30Z","closed_at":null,"merged_at":null,"merge_commit_sha":"cede1d1e86f1b90cde1e6e0e9a3bea3d30ab7ce3","assignee":{"login":"aturon","id":709807,"avatar_url":"https://avatars.githubusercontent.com/u/709807?v=3","gravatar_id":"","url":"https://api.github.com/users/aturon","html_url":"https://github.com/aturon","followers_url":"https://api.github.com/users/aturon/followers","following_url":"https://api.github.com/users/aturon/following{/other_user}","gists_url":"https://api.github.com/users/aturon/gists{/gist_id}","starred_url":"https://api.github.com/users/aturon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aturon/subscriptions","organizations_url":"https://api.github.com/users/aturon/orgs","repos_url":"https://api.github.com/users/aturon/repos","events_url":"https://api.github.com/users/aturon/events{/privacy}","received_events_url":"https://api.github.com/users/aturon/received_events","type":"User","site_admin":false},"milestone":null,"commits_url":"https://api.github.com/repos/rust-lang/rfcs/pulls/1068/commits","review_comments_url":"https://api.github.com/repos/rust-lang/rfcs/pulls/1068/comments","review_comment_url":"https://api.github.com/repos/rust-lang/rfcs/pulls/comments{/number}","comments_url":"https://api.github.com/repos/rust-lang/rfcs/issues/1068/comments","statuses_url":"https://api.github.com/repos/rust-lang/rfcs/statuses/c3f9fda5f1c2f284760c7bd150801eeeb2373708","head":{"label":"aturon:rust-governance","ref":"rust-governance","sha":"c3f9fda5f1c2f284760c7bd150801eeeb2373708","user":{"login":"aturon","id":709807,"avatar_url":"https://avatars.githubusercontent.com/u/709807?v=3","gravatar_id":"","url":"https://api.github.com/users/aturon","html_url":"https://github.com/aturon","followers_url":"https://api.github.com/users/aturon/followers","following_url":"https://api.github.com/users/aturon/following{/other_user}","gists_url":"https://api.github.com/users/aturon/gists{/gist_id}","starred_url":"https://api.github.com/users/aturon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aturon/subscriptions","organizations_url":"https://api.github.com/users/aturon/orgs","repos_url":"https://api.github.com/users/aturon/repos","events_url":"https://api.github.com/users/aturon/events{/privacy}","received_events_url":"https://api.github.com/users/aturon/received_events","type":"User","site_admin":false},"repo":{"id":20423396,"name":"rfcs","full_name":"aturon/rfcs","owner":{"login":"aturon","id":709807,"avatar_url":"https://avatars.githubusercontent.com/u/709807?v=3","gravatar_id":"","url":"https://api.github.com/users/aturon","html_url":"https://github.com/aturon","followers_url":"https://api.github.com/users/aturon/followers","following_url":"https://api.github.com/users/aturon/following{/other_user}","gists_url":"https://api.github.com/users/aturon/gists{/gist_id}","starred_url":"https://api.github.com/users/aturon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aturon/subscriptions","organizations_url":"https://api.github.com/users/aturon/orgs","repos_url":"https://api.github.com/users/aturon/repos","events_url":"https://api.github.com/users/aturon/events{/privacy}","received_events_url":"https://api.github.com/users/aturon/received_events","type":"User","site_admin":false},"private":false,"html_url":"https://github.com/aturon/rfcs","description":"RFCs for changes to Rust","fork":true,"url":"https://api.github.com/repos/aturon/rfcs","forks_url":"https://api.github.com/repos/aturon/rfcs/forks","keys_url":"https://api.github.com/repos/aturon/rfcs/keys{/key_id}","collaborators_url":"https://api.github.com/repos/aturon/rfcs/collaborators{/collaborator}","teams_url":"https://api.github.com/repos/aturon/rfcs/teams","hooks_url":"https://api.github.com/repos/aturon/rfcs/hooks","issue_events_url":"https://api.github.com/repos/aturon/rfcs/issues/events{/number}","events_url":"https://api.github.com/repos/aturon/rfcs/events","assignees_url":"https://api.github.com/repos/aturon/rfcs/assignees{/user}","branches_url":"https://api.github.com/repos/aturon/rfcs/branches{/branch}","tags_url":"https://api.github.com/repos/aturon/rfcs/tags","blobs_url":"https://api.github.com/repos/aturon/rfcs/git/blobs{/sha}","git_tags_url":"https://api.github.com/repos/aturon/rfcs/git/tags{/sha}","git_refs_url":"https://api.github.com/repos/aturon/rfcs/git/refs{/sha}","trees_url":"https://api.github.com/repos/aturon/rfcs/git/trees{/sha}","statuses_url":"https://api.github.com/repos/aturon/rfcs/statuses/{sha}","languages_url":"https://api.github.com/repos/aturon/rfcs/languages","stargazers_url":"https://api.github.com/repos/aturon/rfcs/stargazers","contributors_url":"https://api.github.com/repos/aturon/rfcs/contributors","subscribers_url":"https://api.github.com/repos/aturon/rfcs/subscribers","subscription_url":"https://api.github.com/repos/aturon/rfcs/subscription","commits_url":"https://api.github.com/repos/aturon/rfcs/commits{/sha}","git_commits_url":"https://api.github.com/repos/aturon/rfcs/git/commits{/sha}","comments_url":"https://api.github.com/repos/aturon/rfcs/comments{/number}","issue_comment_url":"https://api.github.com/repos/aturon/rfcs/issues/comments{/number}","contents_url":"https://api.github.com/repos/aturon/rfcs/contents/{+path}","compare_url":"https://api.github.com/repos/aturon/rfcs/compare/{base}...{head}","merges_url":"https://api.github.com/repos/aturon/rfcs/merges","archive_url":"https://api.github.com/repos/aturon/rfcs/{archive_format}{/ref}","downloads_url":"https://api.github.com/repos/aturon/rfcs/downloads","issues_url":"https://api.github.com/repos/aturon/rfcs/issues{/number}","pulls_url":"https://api.github.com/repos/aturon/rfcs/pulls{/number}","milestones_url":"https://api.github.com/repos/aturon/rfcs/milestones{/number}","notifications_url":"https://api.github.com/repos/aturon/rfcs/notifications{?since,all,participating}","labels_url":"https://api.github.com/repos/aturon/rfcs/labels{/name}","releases_url":"https://api.github.com/repos/aturon/rfcs/releases{/id}","created_at":"2014-06-02T23:35:56Z","updated_at":"2015-01-17T17:42:40Z","pushed_at":"2015-04-23T00:12:13Z","git_url":"git://github.com/aturon/rfcs.git","ssh_url":"git@github.com:aturon/rfcs.git","clone_url":"https://github.com/aturon/rfcs.git","svn_url":"https://github.com/aturon/rfcs","homepage":"","size":2813,"stargazers_count":4,"watchers_count":4,"language":null,"has_issues":false,"has_downloads":true,"has_wiki":true,"has_pages":false,"forks_count":0,"mirror_url":null,"open_issues_count":0,"forks":0,"open_issues":0,"watchers":4,"default_branch":"master"}},"base":{"label":"rust-lang:master","ref":"master","sha":"a19c1d2c0e8cf5a0ea85c6e684422956a59af0cd","user":{"login":"rust-lang","id":5430905,"avatar_url":"https://avatars.githubusercontent.com/u/5430905?v=3","gravatar_id":"","url":"https://api.github.com/users/rust-lang","html_url":"https://github.com/rust-lang","followers_url":"https://api.github.com/users/rust-lang/followers","following_url":"https://api.github.com/users/rust-lang/following{/other_user}","gists_url":"https://api.github.com/users/rust-lang/gists{/gist_id}","starred_url":"https://api.github.com/users/rust-lang/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rust-lang/subscriptions","organizations_url":"https://api.github.com/users/rust-lang/orgs","repos_url":"https://api.github.com/users/rust-lang/repos","events_url":"https://api.github.com/users/rust-lang/events{/privacy}","received_events_url":"https://api.github.com/users/rust-lang/received_events","type":"Organization","site_admin":false},"repo":{"id":17527989,"name":"rfcs","full_name":"rust-lang/rfcs","owner":{"login":"rust-lang","id":5430905,"avatar_url":"https://avatars.githubusercontent.com/u/5430905?v=3","gravatar_id":"","url":"https://api.github.com/users/rust-lang","html_url":"https://github.com/rust-lang","followers_url":"https://api.github.com/users/rust-lang/followers","following_url":"https://api.github.com/users/rust-lang/following{/other_user}","gists_url":"https://api.github.com/users/rust-lang/gists{/gist_id}","starred_url":"https://api.github.com/users/rust-lang/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rust-lang/subscriptions","organizations_url":"https://api.github.com/users/rust-lang/orgs","repos_url":"https://api.github.com/users/rust-lang/repos","events_url":"https://api.github.com/users/rust-lang/events{/privacy}","received_events_url":"https://api.github.com/users/rust-lang/received_events","type":"Organization","site_admin":false},"private":false,"html_url":"https://github.com/rust-lang/rfcs","description":"RFCs for changes to Rust","fork":false,"url":"https://api.github.com/repos/rust-lang/rfcs","forks_url":"https://api.github.com/repos/rust-lang/rfcs/forks","keys_url":"https://api.github.com/repos/rust-lang/rfcs/keys{/key_id}","collaborators_url":"https://api.github.com/repos/rust-lang/rfcs/collaborators{/collaborator}","teams_url":"https://api.github.com/repos/rust-lang/rfcs/teams","hooks_url":"https://api.github.com/repos/rust-lang/rfcs/hooks","issue_events_url":"https://api.github.com/repos/rust-lang/rfcs/issues/events{/number}","events_url":"https://api.github.com/repos/rust-lang/rfcs/events","assignees_url":"https://api.github.com/repos/rust-lang/rfcs/assignees{/user}","branches_url":"https://api.github.com/repos/rust-lang/rfcs/branches{/branch}","tags_url":"https://api.github.com/repos/rust-lang/rfcs/tags","blobs_url":"https://api.github.com/repos/rust-lang/rfcs/git/blobs{/sha}","git_tags_url":"https://api.github.com/repos/rust-lang/rfcs/git/tags{/sha}","git_refs_url":"https://api.github.com/repos/rust-lang/rfcs/git/refs{/sha}","trees_url":"https://api.github.com/repos/rust-lang/rfcs/git/trees{/sha}","statuses_url":"https://api.github.com/repos/rust-lang/rfcs/statuses/{sha}","languages_url":"https://api.github.com/repos/rust-lang/rfcs/languages","stargazers_url":"https://api.github.com/repos/rust-lang/rfcs/stargazers","contributors_url":"https://api.github.com/repos/rust-lang/rfcs/contributors","subscribers_url":"https://api.github.com/repos/rust-lang/rfcs/subscribers","subscription_url":"https://api.github.com/repos/rust-lang/rfcs/subscription","commits_url":"https://api.github.com/repos/rust-lang/rfcs/commits{/sha}","git_commits_url":"https://api.github.com/repos/rust-lang/rfcs/git/commits{/sha}","comments_url":"https://api.github.com/repos/rust-lang/rfcs/comments{/number}","issue_comment_url":"https://api.github.com/repos/rust-lang/rfcs/issues/comments{/number}","contents_url":"https://api.github.com/repos/rust-lang/rfcs/contents/{+path}","compare_url":"https://api.github.com/repos/rust-lang/rfcs/compare/{base}...{head}","merges_url":"https://api.github.com/repos/rust-lang/rfcs/merges","archive_url":"https://api.github.com/repos/rust-lang/rfcs/{archive_format}{/ref}","downloads_url":"https://api.github.com/repos/rust-lang/rfcs/downloads","issues_url":"https://api.github.com/repos/rust-lang/rfcs/issues{/number}","pulls_url":"https://api.github.com/repos/rust-lang/rfcs/pulls{/number}","milestones_url":"https://api.github.com/repos/rust-lang/rfcs/milestones{/number}","notifications_url":"https://api.github.com/repos/rust-lang/rfcs/notifications{?since,all,participating}","labels_url":"https://api.github.com/repos/rust-lang/rfcs/labels{/name}","releases_url":"https://api.github.com/repos/rust-lang/rfcs/releases{/id}","created_at":"2014-03-07T21:29:00Z","updated_at":"2015-04-20T21:49:10Z","pushed_at":"2015-04-23T00:56:45Z","git_url":"git://github.com/rust-lang/rfcs.git","ssh_url":"git@github.com:rust-lang/rfcs.git","clone_url":"https://github.com/rust-lang/rfcs.git","svn_url":"https://github.com/rust-lang/rfcs","homepage":"","size":11793,"stargazers_count":318,"watchers_count":318,"language":null,"has_issues":true,"has_downloads":true,"has_wiki":true,"has_pages":false,"forks_count":191,"mirror_url":null,"open_issues_count":494,"forks":191,"open_issues":494,"watchers":318,"default_branch":"master"}},"_links":{"self":{"href":"https://api.github.com/repos/rust-lang/rfcs/pulls/1068"},"html":{"href":"https://github.com/rust-lang/rfcs/pull/1068"},"issue":{"href":"https://api.github.com/repos/rust-lang/rfcs/issues/1068"},"comments":{"href":"https://api.github.com/repos/rust-lang/rfcs/issues/1068/comments"},"review_comments":{"href":"https://api.github.com/repos/rust-lang/rfcs/pulls/1068/comments"},"review_comment":{"href":"https://api.github.com/repos/rust-lang/rfcs/pulls/comments{/number}"},"commits":{"href":"https://api.github.com/repos/rust-lang/rfcs/pulls/1068/commits"},"statuses":{"href":"https://api.github.com/repos/rust-lang/rfcs/statuses/c3f9fda5f1c2f284760c7bd150801eeeb2373708"}}}}