{"action":"created","comment":{"url":"https://api.github.com/repos/amethyst/rfcs/pulls/comments/231617232","pull_request_review_id":172577108,"id":231617232,"node_id":"MDI0OlB1bGxSZXF1ZXN0UmV2aWV3Q29tbWVudDIzMTYxNzIzMg==","diff_hunk":"@@ -1,8 +1,304 @@\n-# RFC\n+# Amethyst RFCs\n+[Amethyst RFCs]: #amethyst-rfcs\n \n-This is the repository where we work and keep track of the all RFC documents related to Amethyst.\n-Having this repository allows people to participate in decision making by opening a pull request with a new document.\n+- [Discussing RFCs](https://github.com/amethyst/rfcs/pulls)\n+- [Accepted RFCs](https://github.com/amethyst/rfcs/tree/master)\n+- [RFCs Awaiting Implementation](https://github.com/amethyst/rfcs/issues?utf8=✓&q=label%3A%22RFC%3A+Accepted%22+-label%3A%22Status%3A+Working%22+)\n \n-## Creating a new RFC\n+## Opening\n+[Opening]: #opening\n \n-The specifics of the RFC process are not yet discussed, but will be documented in the first RFC.\n+Many changes, including bug fixes and documentation improvements can be\n+implemented and reviewed via the normal GitHub pull request workflow.\n+\n+Some changes though are \"substantial\", and we ask that these be put through a\n+bit of a design process and produce a consensus among the Amethyst community and\n+the [sub-team]s.\n+\n+The \"Request for Comments\" (RFC) process is intended to provide a consistent\n+and controlled path for new features to enter the engine and associated\n+libraries, so that all stakeholders can be confident about the direction in which\n+the engine is evolving.\n+\n+You may join our Discord here: https://discord.gg/dqe9UYE and the Amethyst Community Forum here: https://community.amethyst-engine.org.\n+\n+## Table of Contents\n+[Table of Contents]: #table-of-contents\n+\n+- [Opening]\n+- [Table of Contents](#table-of-contents)\n+- [When you need to follow this process](#when-you-need-to-follow-this-process)\n+  - [Sub-team Specific Guidelines](#sub-team-specific-guidelines)\n+- [Before creating an RFC](#before-creating-an-rfc)\n+- [What the process is](#what-the-process-is)\n+- [Tracking Issues](#tracking-issues)\n+  - [Labels and Tags](#labels-tags)\n+- [The RFC life-cycle](#the-rfc-life-cycle)\n+  - [Reviewing RFCs](#reviewing-rfcs)\n+  - [Implementing an RFC](#implementing-an-rfc)\n+  - [RFC Postponement](#rfc-postponement)\n+- [Help this is all too informal!](#help-this-is-all-too-informal)\n+- [License](#license)\n+\n+## When you need to follow this process\n+[When you need to follow this process]: #when-you-need-to-follow-this-process\n+\n+You need to follow this process if you intend to make \"substantial\" changes to\n+Amethyst, its component crates, or the RFC process itself. The definition of substantial\n+is somewhat fluid, and to an extent set by the community. Some examples might include:\n+\n+- A change to a different crate used for physics calculations\n+- Changes to how the editor communicates with the engine\n+- Significant protocol changes to the networking library\n+- Anything that has the potential to produce a substantial negative impact on users\n+\n+Some changes do not require an RFC:\n+\n+- Rephrasing, reorganizing, refactoring, or otherwise \"changing shape does\n+  not change meaning\".\n+- Additions that strictly improve objective, numerical quality criteria\n+  (warning removal, speedup, better platform coverage, more parallelism, trap\n+  more errors, etc.)\n+- Additions only likely to be _noticed by_ other developers-of-amethyst,\n+  invisible to users-of-amethyst.\n+- More tests and benchmarks\n+\n+If you submit a pull request that ends up being generating a lot of discussion or\n+pushback, you may be asked to submit an RFC. What seems to be a minor change can\n+have unintended consequences other teams might see.\n+\n+### Sub-team specific guidelines\n+[Sub-team specific guidelines]: #sub-team-specific-guidelines\n+\n+For more details on when an RFC is required for the following areas, please see \n+the Amethyst community's [sub-team] specific guidelines for:\n+\n+- [Networking changes](net_changes.md)\n+- [Renderer changes](rend_changes.md)\n+- [Engine changes](engine_changes.md)\n+- [Web changes](web_changes.md)\n+\n+## Before creating an RFC\n+[Before creating an RFC]: #before-creating-an-rfc\n+\n+A hastily-proposed RFC can hurt its chances of acceptance. Low quality\n+proposals, proposals for previously-rejected features, or those that don't fit\n+into the near-term roadmap, may be quickly rejected, which can be demotivating\n+for the unprepared contributor. Laying some groundwork ahead of the RFC can\n+make the process smoother.\n+\n+Although there is no single way to prepare for submitting an RFC, it is\n+generally a good idea to pursue feedback from other project developers\n+beforehand, to ascertain that the RFC may be desirable; having a consistent\n+impact on the project requires concerted effort toward consensus-building.\n+\n+The most common preparations for writing and submitting an RFC include talking\n+the idea over on the [Discord channel](https://discord.gg/dqe9UYE), specifically\n+with the applicable sub-team and discussing it on our [Amethyst Community Forums](https://community.amethyst-engine.org)\n+\n+We welcome all ideas and strive to provide kind but useful feedback. While not\n+every proposal will make it through, that should in no way discourage anyone\n+from continuing to make proposals in the future.\n+\n+If the proposal is promising and someone is new to the RFC process, we will\n+do our best to find someone to mentor them through the process.\n+\n+## What the process is\n+[What the process is]: #what-the-process-is\n+\n+In short, to get a major feature added to Amethyst, one must first get the RFC\n+merged into the RFC repository as a markdown file. At that point the RFC is\n+approved and may be implemented with the goal of eventual inclusion into Amethyst.\n+\n+- Fork the RFC repo [RFC repository]\n+- Copy `0000-template.md` to `text/0000-my-feature.md` (where \"my-feature\" is\n+  descriptive. Don't assign an RFC number yet).\n+- Fill in the RFC. Put care into the details: RFCs that do not present\n+  convincing motivation, demonstrate understanding of the impact of the\n+  design, or are disingenuous about the drawbacks or alternatives tend to be\n+  poorly-received.\n+- Submit a pull request. As a pull request the RFC will receive design\n+  feedback from the larger community, and the author should be prepared to\n+  revise it in response.\n+- Each pull request will be labeled with the most relevant [sub-team], which\n+  will lead to its being triaged by that team in a future meeting and assigned\n+  to a member of the subteam.\n+- Build consensus and integrate feedback. RFCs that have broad support are\n+  much more likely to make progress than those that don't receive any\n+  comments. Feel free to reach out to the RFC assignee in particular to get\n+  help identifying stakeholders and obstacles.\n+- The sub-team will discuss the RFC pull request, as much as possible in the\n+  comment thread of the pull request itself. Offline discussion will be\n+  summarized on the pull request comment thread.\n+- RFCs rarely go through this process unchanged, especially as alternatives\n+  and drawbacks are shown. You can make edits, big and small, to the RFC to\n+  clarify or change the design, but make changes as new commits to the pull\n+  request, and leave a comment on the pull request explaining your changes.\n+  *Specifically, do not squash or rebase commits after they are visible on the\n+  pull request.*\n+- At some point, a member of the subteam will propose a \"motion for final\n+  comment period\" (FCP), along with a *disposition* for the RFC (merge, close,\n+  or postpone).\n+  - This step is taken when enough of the tradeoffs have been discussed that\n+  the subteam is in a position to make a decision. That does not require\n+  consensus amongst all participants in the RFC thread (which is usually\n+  impossible). However, the argument supporting the disposition on the RFC\n+  needs to have already been clearly articulated, and there should not be a\n+  strong consensus *against* that position outside of the subteam. Subteam\n+  members use their best judgment in taking this step, and the FCP itself\n+  ensures there is ample time and notification for stakeholders to push back\n+  if it is made prematurely.\n+  - For RFCs with lengthy discussion, the motion to FCP is usually preceded by\n+    a *summary comment* trying to lay out the current state of the discussion\n+    and major tradeoffs/points of disagreement.\n+  - Before actually entering FCP, *all* members of the subteam must sign off;\n+  this is often the point at which many subteam members first review the RFC\n+  in full depth.\n+- The FCP lasts ten calendar days, so that it is open for at least 5 business\n+  days. It is also advertised widely,\n+  e.g. in [This Week in Amethyst](https://amethyst.rs/). This way all\n+  stakeholders have a chance to lodge any final objections before a decision\n+  is reached.\n+- In most cases, the FCP period is quiet, and the RFC is either merged or\n+  closed. However, sometimes substantial new arguments or ideas are raised,\n+  the FCP is canceled, and the RFC goes back into development mode.\n+\n+## Tracking Issues\n+[tracking-issues]: #tracking-issues\n+These are issues created on GitHub that track the implementation progress of the RFC.\n+They link to related issues, have checkboxes, or other structures that make them more\n+of a meta-issue than an issue for adding a specific feature or fixing a bug.\n+\n+This issue is one the sub-team will create, not one you need to create.\n+\n+## Labels and Tags\n+[labels-tags]: #labels-tags\n+\n+We use the following tags for RFC tracking issues:\n+\n+- RFC: Proposed\n+- RFC: Accepted\n+- RFC: Declined\n+- RFC: Complete\n+- RFC: Postponed\n+\n+See the life-cycle section below for details on what these mean.\n+\n+## The RFC life-cycle\n+[The RFC life-cycle]: #the-rfc-life-cycle\n+\n+When an RFC is first created, a tracking issue is created and given the label\n+\"RFC: Proposed\".\n+\n+Once an RFC becomes approved, the tracking issue will be tagged with the label\n+\"RFC: Accepted\". Authors may implement it and submit the feature as a pull\n+request to the Amethyst repo. Being approved is not a rubber stamp, and in\n+particular still does not mean the feature will ultimately be merged; it\n+does mean that in principle all the major stakeholders have agreed to the\n+feature and are amenable to merging it.\n+\n+Furthermore, the fact that a given RFC has been accepted and is approved\n+implies nothing about what priority is assigned to its implementation, nor does\n+it imply anything about whether an Amethyst developer has been assigned the task of\n+implementing the feature. While it is not *necessary* that the author of the\n+RFC also write the implementation, it is by far the most effective way to see\n+an RFC through to completion: authors should not expect that other project\n+developers will take on responsibility for implementing their accepted feature.\n+\n+Modifications to approved RFCs can be done in follow-up pull requests. In\n+order for a PR that deviates from the RFC standard, a new RFC that follows\n+the accepted guidelines should be written and contain a link to the prior version.\n+\n+We strive to write each RFC in a manner that it will reflect the final design of\n+the feature; but the nature of the process means that we cannot expect every\n+merged RFC to actually reflect what the end result will be at the time of the\n+next major release.\n+\n+In general, once accepted, RFCs should not be substantially changed. They should\n+be as detailed as possible so that only very minor changes are needed as amendments.\n+More substantial changes should be new RFCs, with a note added to the original RFC.\n+Exactly what counts as a \"very minor change\" is up to the sub-team to decide; check\n+[Sub-team specific guidelines] for more details.\n+\n+### Reviewing RFCs\n+[Reviewing RFCs]: #reviewing-rfcs\n+\n+While the RFC pull request is up, the sub-team may schedule meetings with the\n+author and/or relevant stakeholders to discuss the issues in greater detail,\n+and in some cases the topic may be discussed at a sub-team meeting. In either\n+case a summary from the meeting will be posted back to the RFC pull request.\n+\n+A sub-team makes final decisions about RFCs after the benefits and drawbacks\n+are well understood. These decisions can be made at any time, but the sub-team\n+will regularly issue decisions. When a decision is made, the RFC pull request\n+will either be merged or closed. In either case, if the reasoning is not clear\n+from the discussion in thread, the sub-team will add a comment describing the\n+rationale for the decision. In the case of the RFC being closed, the tag\n+\"RFC: Declined\" will be added to the tracking issue. If it is merged, it will\n+receive the tag \"RFC: Accepted\".\n+\n+### Implementing an RFC\n+[Implementing an RFC]: #implementing-an-rfc\n+\n+Some accepted RFCs represent vital features that need to be implemented right\n+away. Other accepted RFCs can represent features that can wait until some\n+arbitrary developer feels like doing the work. Every accepted RFC has an\n+associated issue tracking its implementation in the Amethyst repository; thus that\n+associated issue can be assigned a priority via the triage process that the\n+team uses for all issues in the Amethyst repository.\n+\n+The author of an RFC is not obligated to implement it. Of course, the RFC\n+author (like any other developer) is welcome to post an implementation for\n+review after the RFC has been accepted. A prototype or other supporting\n+materials (data flow diagrams, architecture diagrams, aggregations of\n+posts from the community) can all help demonstrate the need and the\n+priority of the RFC.\n+\n+If you are interested in working on the implementation for an approved RFC, but\n+cannot determine if someone else is already working on it, feel free to ask\n+(e.g. by leaving a comment on the associated issue).\n+\n+Once an RFC has been implemented, the tracking issue will be closed and given\n+the label \"RFC: Complete\".\n+\n+### RFC Postponement\n+[RFC Postponement]: #rfc-postponement\n+\n+Some RFC pull requests are tagged with the \"RFC: Postponed\" label when they are\n+closed (as part of the rejection process). An RFC closed with \"RFC: Postponed\" is\n+marked as such because we want neither to think about evaluating the proposal\n+nor about implementing the described feature until some time in the future, and\n+we believe that we can afford to wait until then to do so. Postponed pull\n+requests may be re-opened when the time is right. We don't have any formal\n+process for that, you should ask members of the relevant sub-team.\n+\n+Usually an RFC pull request marked as \"RFC: Postponed\" has already passed an\n+informal first round of evaluation, namely the round of \"do we think we would\n+ever possibly consider making this change, as outlined in the RFC pull request,\n+or some semi-obvious variation of it.\" (When the answer to the latter question\n+is \"no\", then the appropriate response is to close the RFC, not postpone it.)\n+\n+### Help! This is all too informal","path":"README.md","position":286,"original_position":286,"commit_id":"dfa3acf7626cd2339136b0a30ebd17d398694660","original_commit_id":"dfa3acf7626cd2339136b0a30ebd17d398694660","user":{"login":"Xaeroxe","id":6182002,"node_id":"MDQ6VXNlcjYxODIwMDI=","avatar_url":"https://avatars3.githubusercontent.com/u/6182002?v=4","gravatar_id":"","url":"https://api.github.com/users/Xaeroxe","html_url":"https://github.com/Xaeroxe","followers_url":"https://api.github.com/users/Xaeroxe/followers","following_url":"https://api.github.com/users/Xaeroxe/following{/other_user}","gists_url":"https://api.github.com/users/Xaeroxe/gists{/gist_id}","starred_url":"https://api.github.com/users/Xaeroxe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Xaeroxe/subscriptions","organizations_url":"https://api.github.com/users/Xaeroxe/orgs","repos_url":"https://api.github.com/users/Xaeroxe/repos","events_url":"https://api.github.com/users/Xaeroxe/events{/privacy}","received_events_url":"https://api.github.com/users/Xaeroxe/received_events","type":"User","site_admin":false},"body":"I never really liked this section in the rust-lang RFC process.  It's excessively formal in my opinion.  That doesn't mean it's bad, but there is a lot more ceremony involved in this process compared to what we've done previously.","created_at":"2018-11-07T18:06:53Z","updated_at":"2018-11-07T18:08:55Z","html_url":"https://github.com/amethyst/rfcs/pull/2#discussion_r231617232","pull_request_url":"https://api.github.com/repos/amethyst/rfcs/pulls/2","author_association":"MEMBER","_links":{"self":{"href":"https://api.github.com/repos/amethyst/rfcs/pulls/comments/231617232"},"html":{"href":"https://github.com/amethyst/rfcs/pull/2#discussion_r231617232"},"pull_request":{"href":"https://api.github.com/repos/amethyst/rfcs/pulls/2"}}},"pull_request":{"url":"https://api.github.com/repos/amethyst/rfcs/pulls/2","id":226659402,"node_id":"MDExOlB1bGxSZXF1ZXN0MjI2NjU5NDAy","html_url":"https://github.com/amethyst/rfcs/pull/2","diff_url":"https://github.com/amethyst/rfcs/pull/2.diff","patch_url":"https://github.com/amethyst/rfcs/pull/2.patch","issue_url":"https://api.github.com/repos/amethyst/rfcs/issues/2","number":2,"state":"open","locked":false,"title":"Initial ideas on a process. Ripped shamelessly from the Rust process.","user":{"login":"fhaynes","id":4388373,"node_id":"MDQ6VXNlcjQzODgzNzM=","avatar_url":"https://avatars2.githubusercontent.com/u/4388373?v=4","gravatar_id":"","url":"https://api.github.com/users/fhaynes","html_url":"https://github.com/fhaynes","followers_url":"https://api.github.com/users/fhaynes/followers","following_url":"https://api.github.com/users/fhaynes/following{/other_user}","gists_url":"https://api.github.com/users/fhaynes/gists{/gist_id}","starred_url":"https://api.github.com/users/fhaynes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fhaynes/subscriptions","organizations_url":"https://api.github.com/users/fhaynes/orgs","repos_url":"https://api.github.com/users/fhaynes/repos","events_url":"https://api.github.com/users/fhaynes/events{/privacy}","received_events_url":"https://api.github.com/users/fhaynes/received_events","type":"User","site_admin":false},"body":"","created_at":"2018-10-29T18:01:31Z","updated_at":"2018-11-07T18:08:55Z","closed_at":null,"merged_at":null,"merge_commit_sha":"96ca670bcd30712805cb9ebb814a78f18bea8934","assignee":null,"assignees":[],"requested_reviewers":[],"requested_teams":[],"labels":[],"milestone":null,"commits_url":"https://api.github.com/repos/amethyst/rfcs/pulls/2/commits","review_comments_url":"https://api.github.com/repos/amethyst/rfcs/pulls/2/comments","review_comment_url":"https://api.github.com/repos/amethyst/rfcs/pulls/comments{/number}","comments_url":"https://api.github.com/repos/amethyst/rfcs/issues/2/comments","statuses_url":"https://api.github.com/repos/amethyst/rfcs/statuses/dfa3acf7626cd2339136b0a30ebd17d398694660","head":{"label":"fhaynes:master","ref":"master","sha":"dfa3acf7626cd2339136b0a30ebd17d398694660","user":{"login":"fhaynes","id":4388373,"node_id":"MDQ6VXNlcjQzODgzNzM=","avatar_url":"https://avatars2.githubusercontent.com/u/4388373?v=4","gravatar_id":"","url":"https://api.github.com/users/fhaynes","html_url":"https://github.com/fhaynes","followers_url":"https://api.github.com/users/fhaynes/followers","following_url":"https://api.github.com/users/fhaynes/following{/other_user}","gists_url":"https://api.github.com/users/fhaynes/gists{/gist_id}","starred_url":"https://api.github.com/users/fhaynes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fhaynes/subscriptions","organizations_url":"https://api.github.com/users/fhaynes/orgs","repos_url":"https://api.github.com/users/fhaynes/repos","events_url":"https://api.github.com/users/fhaynes/events{/privacy}","received_events_url":"https://api.github.com/users/fhaynes/received_events","type":"User","site_admin":false},"repo":{"id":154991206,"node_id":"MDEwOlJlcG9zaXRvcnkxNTQ5OTEyMDY=","name":"rfcs","full_name":"fhaynes/rfcs","private":false,"owner":{"login":"fhaynes","id":4388373,"node_id":"MDQ6VXNlcjQzODgzNzM=","avatar_url":"https://avatars2.githubusercontent.com/u/4388373?v=4","gravatar_id":"","url":"https://api.github.com/users/fhaynes","html_url":"https://github.com/fhaynes","followers_url":"https://api.github.com/users/fhaynes/followers","following_url":"https://api.github.com/users/fhaynes/following{/other_user}","gists_url":"https://api.github.com/users/fhaynes/gists{/gist_id}","starred_url":"https://api.github.com/users/fhaynes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fhaynes/subscriptions","organizations_url":"https://api.github.com/users/fhaynes/orgs","repos_url":"https://api.github.com/users/fhaynes/repos","events_url":"https://api.github.com/users/fhaynes/events{/privacy}","received_events_url":"https://api.github.com/users/fhaynes/received_events","type":"User","site_admin":false},"html_url":"https://github.com/fhaynes/rfcs","description":"RFCs are documents that contain major plans and decisions for the engine","fork":true,"url":"https://api.github.com/repos/fhaynes/rfcs","forks_url":"https://api.github.com/repos/fhaynes/rfcs/forks","keys_url":"https://api.github.com/repos/fhaynes/rfcs/keys{/key_id}","collaborators_url":"https://api.github.com/repos/fhaynes/rfcs/collaborators{/collaborator}","teams_url":"https://api.github.com/repos/fhaynes/rfcs/teams","hooks_url":"https://api.github.com/repos/fhaynes/rfcs/hooks","issue_events_url":"https://api.github.com/repos/fhaynes/rfcs/issues/events{/number}","events_url":"https://api.github.com/repos/fhaynes/rfcs/events","assignees_url":"https://api.github.com/repos/fhaynes/rfcs/assignees{/user}","branches_url":"https://api.github.com/repos/fhaynes/rfcs/branches{/branch}","tags_url":"https://api.github.com/repos/fhaynes/rfcs/tags","blobs_url":"https://api.github.com/repos/fhaynes/rfcs/git/blobs{/sha}","git_tags_url":"https://api.github.com/repos/fhaynes/rfcs/git/tags{/sha}","git_refs_url":"https://api.github.com/repos/fhaynes/rfcs/git/refs{/sha}","trees_url":"https://api.github.com/repos/fhaynes/rfcs/git/trees{/sha}","statuses_url":"https://api.github.com/repos/fhaynes/rfcs/statuses/{sha}","languages_url":"https://api.github.com/repos/fhaynes/rfcs/languages","stargazers_url":"https://api.github.com/repos/fhaynes/rfcs/stargazers","contributors_url":"https://api.github.com/repos/fhaynes/rfcs/contributors","subscribers_url":"https://api.github.com/repos/fhaynes/rfcs/subscribers","subscription_url":"https://api.github.com/repos/fhaynes/rfcs/subscription","commits_url":"https://api.github.com/repos/fhaynes/rfcs/commits{/sha}","git_commits_url":"https://api.github.com/repos/fhaynes/rfcs/git/commits{/sha}","comments_url":"https://api.github.com/repos/fhaynes/rfcs/comments{/number}","issue_comment_url":"https://api.github.com/repos/fhaynes/rfcs/issues/comments{/number}","contents_url":"https://api.github.com/repos/fhaynes/rfcs/contents/{+path}","compare_url":"https://api.github.com/repos/fhaynes/rfcs/compare/{base}...{head}","merges_url":"https://api.github.com/repos/fhaynes/rfcs/merges","archive_url":"https://api.github.com/repos/fhaynes/rfcs/{archive_format}{/ref}","downloads_url":"https://api.github.com/repos/fhaynes/rfcs/downloads","issues_url":"https://api.github.com/repos/fhaynes/rfcs/issues{/number}","pulls_url":"https://api.github.com/repos/fhaynes/rfcs/pulls{/number}","milestones_url":"https://api.github.com/repos/fhaynes/rfcs/milestones{/number}","notifications_url":"https://api.github.com/repos/fhaynes/rfcs/notifications{?since,all,participating}","labels_url":"https://api.github.com/repos/fhaynes/rfcs/labels{/name}","releases_url":"https://api.github.com/repos/fhaynes/rfcs/releases{/id}","deployments_url":"https://api.github.com/repos/fhaynes/rfcs/deployments","created_at":"2018-10-27T17:30:02Z","updated_at":"2018-11-07T15:19:03Z","pushed_at":"2018-11-07T15:19:00Z","git_url":"git://github.com/fhaynes/rfcs.git","ssh_url":"git@github.com:fhaynes/rfcs.git","clone_url":"https://github.com/fhaynes/rfcs.git","svn_url":"https://github.com/fhaynes/rfcs","homepage":null,"size":85,"stargazers_count":0,"watchers_count":0,"language":null,"has_issues":false,"has_projects":true,"has_downloads":true,"has_wiki":false,"has_pages":false,"forks_count":0,"mirror_url":null,"archived":false,"open_issues_count":0,"license":{"key":"other","name":"Other","spdx_id":"NOASSERTION","url":null,"node_id":"MDc6TGljZW5zZTA="},"forks":0,"open_issues":0,"watchers":0,"default_branch":"master"}},"base":{"label":"amethyst:master","ref":"master","sha":"34e3133f7caab2a5a795bd5da434c2f48ada7e09","user":{"login":"amethyst","id":17814736,"node_id":"MDEyOk9yZ2FuaXphdGlvbjE3ODE0NzM2","avatar_url":"https://avatars1.githubusercontent.com/u/17814736?v=4","gravatar_id":"","url":"https://api.github.com/users/amethyst","html_url":"https://github.com/amethyst","followers_url":"https://api.github.com/users/amethyst/followers","following_url":"https://api.github.com/users/amethyst/following{/other_user}","gists_url":"https://api.github.com/users/amethyst/gists{/gist_id}","starred_url":"https://api.github.com/users/amethyst/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/amethyst/subscriptions","organizations_url":"https://api.github.com/users/amethyst/orgs","repos_url":"https://api.github.com/users/amethyst/repos","events_url":"https://api.github.com/users/amethyst/events{/privacy}","received_events_url":"https://api.github.com/users/amethyst/received_events","type":"Organization","site_admin":false},"repo":{"id":154931504,"node_id":"MDEwOlJlcG9zaXRvcnkxNTQ5MzE1MDQ=","name":"rfcs","full_name":"amethyst/rfcs","private":false,"owner":{"login":"amethyst","id":17814736,"node_id":"MDEyOk9yZ2FuaXphdGlvbjE3ODE0NzM2","avatar_url":"https://avatars1.githubusercontent.com/u/17814736?v=4","gravatar_id":"","url":"https://api.github.com/users/amethyst","html_url":"https://github.com/amethyst","followers_url":"https://api.github.com/users/amethyst/followers","following_url":"https://api.github.com/users/amethyst/following{/other_user}","gists_url":"https://api.github.com/users/amethyst/gists{/gist_id}","starred_url":"https://api.github.com/users/amethyst/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/amethyst/subscriptions","organizations_url":"https://api.github.com/users/amethyst/orgs","repos_url":"https://api.github.com/users/amethyst/repos","events_url":"https://api.github.com/users/amethyst/events{/privacy}","received_events_url":"https://api.github.com/users/amethyst/received_events","type":"Organization","site_admin":false},"html_url":"https://github.com/amethyst/rfcs","description":"RFCs are documents that contain major plans and decisions for the engine","fork":false,"url":"https://api.github.com/repos/amethyst/rfcs","forks_url":"https://api.github.com/repos/amethyst/rfcs/forks","keys_url":"https://api.github.com/repos/amethyst/rfcs/keys{/key_id}","collaborators_url":"https://api.github.com/repos/amethyst/rfcs/collaborators{/collaborator}","teams_url":"https://api.github.com/repos/amethyst/rfcs/teams","hooks_url":"https://api.github.com/repos/amethyst/rfcs/hooks","issue_events_url":"https://api.github.com/repos/amethyst/rfcs/issues/events{/number}","events_url":"https://api.github.com/repos/amethyst/rfcs/events","assignees_url":"https://api.github.com/repos/amethyst/rfcs/assignees{/user}","branches_url":"https://api.github.com/repos/amethyst/rfcs/branches{/branch}","tags_url":"https://api.github.com/repos/amethyst/rfcs/tags","blobs_url":"https://api.github.com/repos/amethyst/rfcs/git/blobs{/sha}","git_tags_url":"https://api.github.com/repos/amethyst/rfcs/git/tags{/sha}","git_refs_url":"https://api.github.com/repos/amethyst/rfcs/git/refs{/sha}","trees_url":"https://api.github.com/repos/amethyst/rfcs/git/trees{/sha}","statuses_url":"https://api.github.com/repos/amethyst/rfcs/statuses/{sha}","languages_url":"https://api.github.com/repos/amethyst/rfcs/languages","stargazers_url":"https://api.github.com/repos/amethyst/rfcs/stargazers","contributors_url":"https://api.github.com/repos/amethyst/rfcs/contributors","subscribers_url":"https://api.github.com/repos/amethyst/rfcs/subscribers","subscription_url":"https://api.github.com/repos/amethyst/rfcs/subscription","commits_url":"https://api.github.com/repos/amethyst/rfcs/commits{/sha}","git_commits_url":"https://api.github.com/repos/amethyst/rfcs/git/commits{/sha}","comments_url":"https://api.github.com/repos/amethyst/rfcs/comments{/number}","issue_comment_url":"https://api.github.com/repos/amethyst/rfcs/issues/comments{/number}","contents_url":"https://api.github.com/repos/amethyst/rfcs/contents/{+path}","compare_url":"https://api.github.com/repos/amethyst/rfcs/compare/{base}...{head}","merges_url":"https://api.github.com/repos/amethyst/rfcs/merges","archive_url":"https://api.github.com/repos/amethyst/rfcs/{archive_format}{/ref}","downloads_url":"https://api.github.com/repos/amethyst/rfcs/downloads","issues_url":"https://api.github.com/repos/amethyst/rfcs/issues{/number}","pulls_url":"https://api.github.com/repos/amethyst/rfcs/pulls{/number}","milestones_url":"https://api.github.com/repos/amethyst/rfcs/milestones{/number}","notifications_url":"https://api.github.com/repos/amethyst/rfcs/notifications{?since,all,participating}","labels_url":"https://api.github.com/repos/amethyst/rfcs/labels{/name}","releases_url":"https://api.github.com/repos/amethyst/rfcs/releases{/id}","deployments_url":"https://api.github.com/repos/amethyst/rfcs/deployments","created_at":"2018-10-27T05:58:47Z","updated_at":"2018-11-06T18:34:30Z","pushed_at":"2018-11-07T15:19:02Z","git_url":"git://github.com/amethyst/rfcs.git","ssh_url":"git@github.com:amethyst/rfcs.git","clone_url":"https://github.com/amethyst/rfcs.git","svn_url":"https://github.com/amethyst/rfcs","homepage":null,"size":2,"stargazers_count":4,"watchers_count":4,"language":null,"has_issues":true,"has_projects":false,"has_downloads":true,"has_wiki":false,"has_pages":false,"forks_count":2,"mirror_url":null,"archived":false,"open_issues_count":2,"license":null,"forks":2,"open_issues":2,"watchers":4,"default_branch":"master"}},"_links":{"self":{"href":"https://api.github.com/repos/amethyst/rfcs/pulls/2"},"html":{"href":"https://github.com/amethyst/rfcs/pull/2"},"issue":{"href":"https://api.github.com/repos/amethyst/rfcs/issues/2"},"comments":{"href":"https://api.github.com/repos/amethyst/rfcs/issues/2/comments"},"review_comments":{"href":"https://api.github.com/repos/amethyst/rfcs/pulls/2/comments"},"review_comment":{"href":"https://api.github.com/repos/amethyst/rfcs/pulls/comments{/number}"},"commits":{"href":"https://api.github.com/repos/amethyst/rfcs/pulls/2/commits"},"statuses":{"href":"https://api.github.com/repos/amethyst/rfcs/statuses/dfa3acf7626cd2339136b0a30ebd17d398694660"}},"author_association":"MEMBER"}}
{"actor":{"display_login":"Xaeroxe"}}