{"action":"created","issue":{"url":"https://api.github.com/repos/processwire/processwire-issues/issues/1","repository_url":"https://api.github.com/repos/processwire/processwire-issues","labels_url":"https://api.github.com/repos/processwire/processwire-issues/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/processwire/processwire-issues/issues/1/comments","events_url":"https://api.github.com/repos/processwire/processwire-issues/issues/1/events","html_url":"https://github.com/processwire/processwire-issues/issues/1","id":178904449,"number":1,"title":"What to do with issues from old repository?","user":{"login":"isellsoap","id":477474,"avatar_url":"https://avatars.githubusercontent.com/u/477474?v=3","gravatar_id":"","url":"https://api.github.com/users/isellsoap","html_url":"https://github.com/isellsoap","followers_url":"https://api.github.com/users/isellsoap/followers","following_url":"https://api.github.com/users/isellsoap/following{/other_user}","gists_url":"https://api.github.com/users/isellsoap/gists{/gist_id}","starred_url":"https://api.github.com/users/isellsoap/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/isellsoap/subscriptions","organizations_url":"https://api.github.com/users/isellsoap/orgs","repos_url":"https://api.github.com/users/isellsoap/repos","events_url":"https://api.github.com/users/isellsoap/events{/privacy}","received_events_url":"https://api.github.com/users/isellsoap/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/processwire/processwire-issues/labels/meta","name":"meta","color":"5319e7"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-09-23T15:20:00Z","updated_at":"2016-09-23T20:19:47Z","closed_at":null,"body":"How should we handle still open issues in the [\"old\" ProcessWire repository](https://github.com/ryancramerdesign/ProcessWire/issues)? Should be migrate them step-by-step into this one? Any suggestions?\r\n\r\n@ryancramerdesign I think it would be also good to add a _READ THIS BEFORE SUBMITTING ISSUE REPORTS_ issue ([like you did here](https://github.com/processwire/processwire/issues/8)) in the old repository."},"comment":{"url":"https://api.github.com/repos/processwire/processwire-issues/issues/comments/249292464","html_url":"https://github.com/processwire/processwire-issues/issues/1#issuecomment-249292464","issue_url":"https://api.github.com/repos/processwire/processwire-issues/issues/1","id":249292464,"user":{"login":"teppokoivula","id":1252021,"avatar_url":"https://avatars.githubusercontent.com/u/1252021?v=3","gravatar_id":"","url":"https://api.github.com/users/teppokoivula","html_url":"https://github.com/teppokoivula","followers_url":"https://api.github.com/users/teppokoivula/followers","following_url":"https://api.github.com/users/teppokoivula/following{/other_user}","gists_url":"https://api.github.com/users/teppokoivula/gists{/gist_id}","starred_url":"https://api.github.com/users/teppokoivula/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/teppokoivula/subscriptions","organizations_url":"https://api.github.com/users/teppokoivula/orgs","repos_url":"https://api.github.com/users/teppokoivula/repos","events_url":"https://api.github.com/users/teppokoivula/events{/privacy}","received_events_url":"https://api.github.com/users/teppokoivula/received_events","type":"User","site_admin":false},"created_at":"2016-09-23T20:19:47Z","updated_at":"2016-09-23T20:19:47Z","body":"> If some old issue still exists in 3.x and needs attention, I'm not aware of any, but no doubt it'll resurface here on its own.\r\n\r\nI'm a bit confused by this particular observation, considering that even I have opened a couple of issues myself that are still waiting for some kind of reaction from you. Take a look at [#966](https://github.com/ryancramerdesign/ProcessWire/issues/966), for an example, if you don't believe me. You probably get too many notices from GitHub to react to them all, but trust me: there most definitely *are* open issues.\r\n\r\nPlease note that I'm not trying to blame anyone here, just stating how this looks to me: I'm afraid that you, Ryan, have piled too much responsibility on your own shoulders, and at some point that's bound to cause problems. I'm hopeful that officially having more people take care of issues helps with this particular bottleneck. Wise decision indeed :)\r\n\r\nThat being said, if you do decide that migrating issues here makes sense (in my opinion it would), I for one would be happy to help with going through old issues. Either way I'm going to go through my own open issues and re-post those that still make sense here."}}
{"actor":{"display_login":"teppokoivula"}}