{"action":"created","issue":{"url":"https://api.github.com/repos/ngbp/ngbp/issues/347","labels_url":"https://api.github.com/repos/ngbp/ngbp/issues/347/labels{/name}","comments_url":"https://api.github.com/repos/ngbp/ngbp/issues/347/comments","events_url":"https://api.github.com/repos/ngbp/ngbp/issues/347/events","html_url":"https://github.com/ngbp/ngbp/issues/347","id":53191201,"number":347,"title":"RFC: Boilerplate is abandoned","user":{"login":"saibotsivad","id":91254,"avatar_url":"https://avatars.githubusercontent.com/u/91254?v=3","gravatar_id":"","url":"https://api.github.com/users/saibotsivad","html_url":"https://github.com/saibotsivad","followers_url":"https://api.github.com/users/saibotsivad/followers","following_url":"https://api.github.com/users/saibotsivad/following{/other_user}","gists_url":"https://api.github.com/users/saibotsivad/gists{/gist_id}","starred_url":"https://api.github.com/users/saibotsivad/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/saibotsivad/subscriptions","organizations_url":"https://api.github.com/users/saibotsivad/orgs","repos_url":"https://api.github.com/users/saibotsivad/repos","events_url":"https://api.github.com/users/saibotsivad/events{/privacy}","received_events_url":"https://api.github.com/users/saibotsivad/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/ngbp/ngbp/labels/more+info+needed","name":"more info needed","color":"fef2c0"},{"url":"https://api.github.com/repos/ngbp/ngbp/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2014-12-31T16:27:59Z","updated_at":"2015-01-07T15:57:33Z","closed_at":null,"body":"This is not meant as a criticism, it is an open request for comments from the developers and the community:\r\n\r\n* It looks like the [last commit]() was a while ago (25 days currently).\r\n* There are [52 open pull requests](https://github.com/ngbp/ngbp/pulls), some of them very old.\r\n* Even trivial-but-important PRs, like [this one](https://github.com/ngbp/ngbp/pull/337), have been sitting for a month and a half.\r\n\r\nOn the one hand, I could fork boilerplate myself and merge a bunch of pull requests, but a few months down the road it would be sitting in the same position: I would have lost interest, and the code would get stagnant. I don't want to maintain even a cool project like this forever!\r\n\r\nOne potential solution I would suggest, that Rod Vagg uses in [levelup](https://github.com/rvagg/node-levelup) is making people contributors. (See his [working manifesto](https://github.com/rvagg/node-levelup/blob/master/CONTRIBUTING.md) as an example.) In practice what this means is that anyone who contributes \"reasonably significant\" code is nearly automatically made a contributor.\r\n\r\nThis solves the problem of a lack of people with admin power being able to merge pull requests.\r\n\r\nComments? Critiques? Suggestions?"},"comment":{"url":"https://api.github.com/repos/ngbp/ngbp/issues/comments/69042144","html_url":"https://github.com/ngbp/ngbp/issues/347#issuecomment-69042144","issue_url":"https://api.github.com/repos/ngbp/ngbp/issues/347","id":69042144,"user":{"login":"saibotsivad","id":91254,"avatar_url":"https://avatars.githubusercontent.com/u/91254?v=3","gravatar_id":"","url":"https://api.github.com/users/saibotsivad","html_url":"https://github.com/saibotsivad","followers_url":"https://api.github.com/users/saibotsivad/followers","following_url":"https://api.github.com/users/saibotsivad/following{/other_user}","gists_url":"https://api.github.com/users/saibotsivad/gists{/gist_id}","starred_url":"https://api.github.com/users/saibotsivad/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/saibotsivad/subscriptions","organizations_url":"https://api.github.com/users/saibotsivad/orgs","repos_url":"https://api.github.com/users/saibotsivad/repos","events_url":"https://api.github.com/users/saibotsivad/events{/privacy}","received_events_url":"https://api.github.com/users/saibotsivad/received_events","type":"User","site_admin":false},"created_at":"2015-01-07T15:57:32Z","updated_at":"2015-01-07T15:57:32Z","body":"@joshdmiller I'm glad you're still around! Sorry for the length of the text below. :)\r\n\r\nI saw in the ngbp organization that there were four other contributors, but based on the lack of activity it appears that the four of you don't have enough free time to devote to maintaining the project.\r\n\r\nFor example, on the first page of pull requests, only 8/25 seem to have comments from contributors. Of the ones that are commented on by contributors, a number of them seem to indicate that the pull request is ready to be merged, but they have been sitting open for months.\r\n\r\nIf this is a case of people not making good pull requests (always a possibility) than there would be more comments on the pull requests to indicate what should be changed, ideally a link to some \"code style guide\" or perhaps a \"guiding philosophy\" document. (Semi-relatedly, the links in the [wiki](https://github.com/ngbp/ngbp/wiki) go to the old repo, so none of those documents are reachable.)\r\n\r\nAgain, this isn't meant as a criticism, but due to lack of activity it certainly seems that this project has been abandoned.\r\n\r\nCorrect me if I'm wrong, but based on you moving the boilerplate from your personal repo to the ngbp, it appears that you intended this project to become less personal and more community driven?\r\n\r\nIf that's the case, I think that a reasonable solution to keeping ngbp updated and alive is threefold:\r\n\r\n### 1. Cast a vision\r\n\r\nFor other people to volunteer their time, you'll want to say \"*this* is the goal\". This might be as simple as writing up a \"design philosophy\" page in the wiki.\r\n\r\n### 2. Lower the bar for adding contributors.\r\n\r\nThis seems to be the approach of [Rod Vagg](https://github.com/rvagg) (of levelup fame). In practice what this looks like is that anyone who contributes some arbitrarily long/reasonable code is automatically added as a contributor. (They can remove themselves if they don't want to be.)\r\n\r\nThe advantage of this is:\r\n\r\n* It encourages community involvement. Giving people responsibility makes them want to be more involved.\r\n* Less personal work required. Other people can address issues and merge pull requests, meaning that you don't have to do as much work.\r\n\r\n### 3. Lower the bar for pull requests.\r\n\r\n(I don't know if this is actually necessary, if you have enough active contributors.)\r\n\r\nIf pull requests don't have comments in the commits, or other such things, maybe they can still be merged if they are not important (e.g. slight wording change, fix links, etc.).\r\n\r\n---\r\n\r\nAll this to say: I really appreciate all the work that's gone into this project, it's been an indispensable help in learning grunt and angular! I'd love to help mature this project and make it more community-driven."}}