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

Community May Not Coalesce, Open Source Code #61

Open
plantarum opened this issue Dec 4, 2017 · 1 comment
Open

Community May Not Coalesce, Open Source Code #61

plantarum opened this issue Dec 4, 2017 · 1 comment
Assignees

Comments

@plantarum
Copy link
Contributor

plantarum commented Dec 4, 2017

Every OSS project does not need to be the Linux kernel. We don't need to have long-term support and ongoing development in every case. Suggesting that releasing a program open source will necessarily incur the long-term burden of developing and maintaining a community is unreasonable, and will introduce prejudice against small projects for which this is unnecessary.

@plantarum plantarum changed the title Community May Not Community May Not Coalesce, Open Source Code Dec 4, 2017
@smellems
Copy link
Member

smellems commented Dec 4, 2017

It probably depends on what your goals are when publishing code as OSS. Maybe you just want/need to put code out there (to make it accessible to others or just to work in the open) and are not actively looking for contributions to keep it going. In other cases you may want to create a new community and would like to see it continue to exist without the GC being the main contributor..

But your right, we don't want to say that you must actively build a community around your OSS.

@gcharest gcharest self-assigned this May 25, 2018
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