Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discussions #94

Closed
gergoerdosi opened this issue Dec 6, 2014 · 5 comments
Closed

Discussions #94

gergoerdosi opened this issue Dec 6, 2014 · 5 comments

Comments

@gergoerdosi
Copy link

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.

@mikeal
Copy link
Contributor

mikeal commented 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
Copy link
Author

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
Copy link
Contributor

mikeal commented 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
Copy link
Contributor

@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
Copy link
Author

@mikeal @kenperkins Thanks for the tip, the unsubscribe button solves my problem indeed. I'm closing this issue then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants