Repository navigation
Discussions #94
Description
There are many GitHub issues about the future of io.js (governance, logo, community, etc). However these create a noise in this repository. I think only code related issues should be discussed here (similarly to joyent/node). I suggest to create a "discuss" repository and move these discussions there.
Activity
mikeal commentedon Dec 6, 2014
Issues about core, even conversational ones, should happen here or in the roadmap repo (if they relate to a future roadmap)
Issues about the ecosystem or node in general can happen on https://github.com/node-forward/discussions/
The reason issues about core need to be here is so that they can be tagged for the TC agenda if necessary.
gergoerdosi commentedon Dec 6, 2014
Well, the way I see is that iojs/io.js is just a repository for code. It doesn't represent the whole project. The GitHub site (iojs.github.io), the build infrastructure, etc. is also part of the project. In my opinion issues that are about the whole project should be discussed somewhere else. For example: #94, #37, #52, #51.
The reason is simple. I'm interested in changes and discussions in the core (iojs/io.js). However I receive too many emails that are not related to the core (eg. logo) and it takes a lot of time to remove this "noise" from my inbox.
mikeal commentedon Dec 6, 2014
@gergoerdosi most of that "noise" is just because the project is new, these issues will all get posted over the next week or so and you can just unsubscribe from the ones that aren't relevant. After that I would expect all the issues to be more code related.
kenperkins commentedon Dec 6, 2014
@gergoerdosi One tip: I always unsubscribe from issues I'm not fully vested in, i.e. #37. Lets me keep my inbox clearer... ymmv
gergoerdosi commentedon Dec 6, 2014
@mikeal @kenperkins Thanks for the tip, the unsubscribe button solves my problem indeed. I'm closing this issue then.