You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
plantarum
changed the title
Community May Not
Community May Not Coalesce, Open Source Code
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.
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.
The text was updated successfully, but these errors were encountered: