{"action":"created","issue":{"url":"https://api.github.com/repos/scikit-learn/scikit-learn/issues/4333","labels_url":"https://api.github.com/repos/scikit-learn/scikit-learn/issues/4333/labels{/name}","comments_url":"https://api.github.com/repos/scikit-learn/scikit-learn/issues/4333/comments","events_url":"https://api.github.com/repos/scikit-learn/scikit-learn/issues/4333/events","html_url":"https://github.com/scikit-learn/scikit-learn/issues/4333","id":59777562,"number":4333,"title":"How to find issues that no one is working on?","user":{"login":"martin0258","id":1118615,"avatar_url":"https://avatars.githubusercontent.com/u/1118615?v=3","gravatar_id":"","url":"https://api.github.com/users/martin0258","html_url":"https://github.com/martin0258","followers_url":"https://api.github.com/users/martin0258/followers","following_url":"https://api.github.com/users/martin0258/following{/other_user}","gists_url":"https://api.github.com/users/martin0258/gists{/gist_id}","starred_url":"https://api.github.com/users/martin0258/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/martin0258/subscriptions","organizations_url":"https://api.github.com/users/martin0258/orgs","repos_url":"https://api.github.com/users/martin0258/repos","events_url":"https://api.github.com/users/martin0258/events{/privacy}","received_events_url":"https://api.github.com/users/martin0258/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-03-04T10:25:10Z","updated_at":"2015-03-04T11:10:42Z","closed_at":"2015-03-04T11:10:42Z","body":"As title, how do I find issues that no one is working on?\r\nI'd like to contribute to issues that no one is working on.\r\nI spent much time browsing open issues to find them.\r\n\r\nMy best approach is: Find [open issues with least comments](https://github.com/scikit-learn/scikit-learn/issues?q=is%3Aissue+is%3Aopen+sort%3Acomments-asc). However, it also failed in some cases like `#1854` (at this point, it is open without comment, but someone is working on it with a pull request to it). Is there any better approach? Probably with convention of issue title, assignee, or label?\r\n\r\nSorry if it is a stupid question......I'm a new contributor."},"comment":{"url":"https://api.github.com/repos/scikit-learn/scikit-learn/issues/comments/77139776","html_url":"https://github.com/scikit-learn/scikit-learn/issues/4333#issuecomment-77139776","issue_url":"https://api.github.com/repos/scikit-learn/scikit-learn/issues/4333","id":77139776,"user":{"login":"jnothman","id":78827,"avatar_url":"https://avatars.githubusercontent.com/u/78827?v=3","gravatar_id":"","url":"https://api.github.com/users/jnothman","html_url":"https://github.com/jnothman","followers_url":"https://api.github.com/users/jnothman/followers","following_url":"https://api.github.com/users/jnothman/following{/other_user}","gists_url":"https://api.github.com/users/jnothman/gists{/gist_id}","starred_url":"https://api.github.com/users/jnothman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jnothman/subscriptions","organizations_url":"https://api.github.com/users/jnothman/orgs","repos_url":"https://api.github.com/users/jnothman/repos","events_url":"https://api.github.com/users/jnothman/events{/privacy}","received_events_url":"https://api.github.com/users/jnothman/received_events","type":"User","site_admin":false},"created_at":"2015-03-04T11:10:42Z","updated_at":"2015-03-04T11:10:42Z","body":"It's not a stupid question, but questions aren't issues, so this will be closed.\r\n\r\nIt is also a question that we attempt to answer [here](http://scikit-learn.org/dev/faq.html#how-can-i-contribute-to-scikit-learn) and hence [here](http://scikit-learn.org/dev/developers/index.html#easy-issues) (although I think @ragv is [trying to have this written more clearly](https://github.com/scikit-learn/scikit-learn/issues/3912#issuecomment-73424168)).\r\n\r\nAt this time of year, a lot of the easier/smaller issues have been taken by people trying to get ready for GSoC applications, so \"easy\" issues may not be as available as at other times of year."}}