|
|
|
|
|
by was_boring
2984 days ago
|
|
This seems like a weak argument for not open sourcing. Just because it is open source doesn't mean you need to accept any community suggestions, and it doesn't mean you can't make radical changes because you want to. Even by doing this, you're still giving back because people can learn from it -- kind of like how a patent gives back. You are the project owner after all, and if someone doesn't like the way you are going they can just fork it and continue on their own. |
|
You're right tho that they could do everything you describe, i.e. publish the source code and not actually participate in any 'open source' community projects that might spring up around the code. I'm guessing that's not really that attractive to Stripe, or lots of other people. It's work just to remember to push commits to the public repo, even if you're otherwise ignoring all public communications about the project. (And ignoring all the public communications, e.g. blog posts complaining about the company not collaborating with the community, is work too.)