{"action":"opened","issue":{"url":"https://api.github.com/repos/alexyans/collabhub/issues/6","labels_url":"https://api.github.com/repos/alexyans/collabhub/issues/6/labels{/name}","comments_url":"https://api.github.com/repos/alexyans/collabhub/issues/6/comments","events_url":"https://api.github.com/repos/alexyans/collabhub/issues/6/events","html_url":"https://github.com/alexyans/collabhub/issues/6","id":95375540,"number":6,"title":"Idea for first project breakdown","user":{"login":"saske505","id":5356951,"avatar_url":"https://avatars.githubusercontent.com/u/5356951?v=3","gravatar_id":"","url":"https://api.github.com/users/saske505","html_url":"https://github.com/saske505","followers_url":"https://api.github.com/users/saske505/followers","following_url":"https://api.github.com/users/saske505/following{/other_user}","gists_url":"https://api.github.com/users/saske505/gists{/gist_id}","starred_url":"https://api.github.com/users/saske505/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/saske505/subscriptions","organizations_url":"https://api.github.com/users/saske505/orgs","repos_url":"https://api.github.com/users/saske505/repos","events_url":"https://api.github.com/users/saske505/events{/privacy}","received_events_url":"https://api.github.com/users/saske505/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-07-16T08:03:21Z","updated_at":"2015-07-16T08:03:21Z","closed_at":null,"body":"#1 track the number of bugs idea\r\n\r\nFor this one I was thinking of getting users of the service to point out which packages to follow. That is, say you go to the page and you want to know the status of bugs for some npm package. Instead of tracking every package that is out there, or only those over some number of downloads, track packages on demand.\r\n\r\nUsually, users leave stack traces on github issues and that is more than enough to get an idea of how many bugs are out there, which dependencies are affected and if has also happened for other package.\r\n\r\n#1 The problems with this one are:\r\n\r\nit would be very difficult to get package versions out of pasted stack traces\r\nit would be necessary to properly discard/scan stack traces so things can get interesting\r\nthe language learning idea\r\n\r\nThis is way more complex on how things can be developed just because is way more complex.\r\n\r\nThe basic idea is to acknowledge that languages can't be thoroughly learned on a short period and if you really want to learn you have to spend time on your normal day. You don't have to do it every day, but you have to if you want to learn something.\r\n\r\nFilling gaps on written sentences or learning grammar means nothing. Grammar is there for when you have doubts, and the basic principles of the language."}}