{"action":"created","issue":{"url":"https://api.github.com/repos/ethereum/EIPs/issues/148","repository_url":"https://api.github.com/repos/ethereum/EIPs","labels_url":"https://api.github.com/repos/ethereum/EIPs/issues/148/labels{/name}","comments_url":"https://api.github.com/repos/ethereum/EIPs/issues/148/comments","events_url":"https://api.github.com/repos/ethereum/EIPs/issues/148/events","html_url":"https://github.com/ethereum/EIPs/issues/148","id":176516249,"number":148,"title":"EIP/ERC process improvement","user":{"login":"axic","id":20340,"avatar_url":"https://avatars.githubusercontent.com/u/20340?v=3","gravatar_id":"","url":"https://api.github.com/users/axic","html_url":"https://github.com/axic","followers_url":"https://api.github.com/users/axic/followers","following_url":"https://api.github.com/users/axic/following{/other_user}","gists_url":"https://api.github.com/users/axic/gists{/gist_id}","starred_url":"https://api.github.com/users/axic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/axic/subscriptions","organizations_url":"https://api.github.com/users/axic/orgs","repos_url":"https://api.github.com/users/axic/repos","events_url":"https://api.github.com/users/axic/events{/privacy}","received_events_url":"https://api.github.com/users/axic/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/ethereum/EIPs/labels/meta","name":"meta","color":"bfd4f2"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2016-09-13T00:09:42Z","updated_at":"2016-10-26T06:54:07Z","closed_at":null,"body":"I think this is happening de facto already, but can we codify that:\r\n- proposals can be referred to as `ERC<n>` where `n` refers to the issue number\r\n- final EIP numbers are allocated when an ERC is *accepted*\r\n\r\nAdditionally, can we also introduce the following Github labels?\r\n- `scheduled` (for discussion in the next *core dev meeting*)\r\n- `concept accepted` / `prototyping` (design is accepted, need to/should be prototyped in multiple clients)\r\n- `rejected`\r\n- `accepted` (it must become an EIP, where changes are allowed)\r\n\r\nAlternatively we could also just follow the process described in EIP0 😃 "},"comment":{"url":"https://api.github.com/repos/ethereum/EIPs/issues/comments/256264299","html_url":"https://github.com/ethereum/EIPs/issues/148#issuecomment-256264299","issue_url":"https://api.github.com/repos/ethereum/EIPs/issues/148","id":256264299,"user":{"login":"Arachnid","id":17865,"avatar_url":"https://avatars.githubusercontent.com/u/17865?v=3","gravatar_id":"","url":"https://api.github.com/users/Arachnid","html_url":"https://github.com/Arachnid","followers_url":"https://api.github.com/users/Arachnid/followers","following_url":"https://api.github.com/users/Arachnid/following{/other_user}","gists_url":"https://api.github.com/users/Arachnid/gists{/gist_id}","starred_url":"https://api.github.com/users/Arachnid/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Arachnid/subscriptions","organizations_url":"https://api.github.com/users/Arachnid/orgs","repos_url":"https://api.github.com/users/Arachnid/repos","events_url":"https://api.github.com/users/Arachnid/events{/privacy}","received_events_url":"https://api.github.com/users/Arachnid/received_events","type":"User","site_admin":false},"created_at":"2016-10-26T06:54:07Z","updated_at":"2016-10-26T06:54:07Z","body":"> As Github goes, the current layout is easy enough to navigate, and the history of modifications to each EIP file is clear.\r\n\r\nUnless I'm missing something, there's no way to see what revisions have been made to an issue; can you elaborate?\r\n\r\n> I'm not clear how things would look and be navigated in this new PR scheme - but it sounds more complicated.\r\n\r\nExactly as described in EIP0: New EIPs are submitted as pull requests, and are discussed in the pull request. This seems simpler, to me, than starting off in an issue and then migrating to a file in the repository, and also allows amendments to EIPs to be discussed independently of the EIP itself."}}
{"actor":{"display_login":"Arachnid"}}