-
Notifications
You must be signed in to change notification settings - Fork 130
NodeBug.me for io.js #253
Comments
The nodebug.me site is actually linked from the the official io.js FAQ. I haven't dug into this site. It seems @chrisdickinson has contributed to both projects (io.js site and nodebug.me). Perhaps he can provide more context. |
I'm open to us further promoting tools like this or even helping give them a bump if they want to gain more structure as a WG initiative. Giving it a more official URL is okay too but would probably happen through the context of another team managing that initiative. |
I think this is far less important for io.js -- the main motivator was to have a way to somewhat sanely filter through node's gazillion issues. However, this may become worthwhile in the future. For now core's still mostly under control, I think. |
@Fishrock123 I talked to Mikeal not too long after I posted this, and he felt similarly. He told me one reason NodeBug.me worked was because there was such a huge number of open issues on the Node repo, whereas the maintainers of io.js have handled them pretty well, taking care of everything that can be taken care of. Closing, as it seems now isn't quite the right time for ioBug.me. The idea of a tool like this that creates further engagement is definitely something to keep on the table, but this incarnation isn't the right one at present. |
It probably isn't worthwhile to write our own tool for that. There's lots of tools that hook into github. |
Sorry, I didn't mean to suggest we write our own tool for anything related to GitHub. I just meant the idea of an engagement tool that further involves the community in WGs in a more accessible way is something to keep in mind. Pretty much along the lines of nodejs/evangelism#26 |
I just found http://nodebug.me on roadmap/#3, and was completely blown away. It's available on GitHub. I'd like to get input from @iojs/website on feasibility, and if that returns positive I'm going bring it to @iojs/evangelism to discuss anything that might be needed from it.
What are your thoughts on putting a version of NodeBug.me on a subdomain of iojs.org, like bugs.iojs.org or help.iojs.org/bugs?
The text was updated successfully, but these errors were encountered: