3 ms·
Ask HN: What License for New “Open Source” Project? Commons Clause?
I am currently working on a project which I want to "Open Source" soon. I write it in quotes because I am also thinking about adding Common Clause to it which even though the code would still be open and free to use and for 99.99999% of the people it should make no difference it would not be allowed to be called Open Source anymore.
The reason I want to apply Commons Clause[1] is simple. On the one hand, do I want that everybody no matter if a private person or big company can use it totally free for themselves. On the other hand, do I not want that another company commercializes it and at the same time does not do anything to further the project. If the chance really arrises, I would prefer to commercialize it myself and so fund improving the project and giving part of the profit to other Open Source projects which are important for mine. I think that this would be in the end in the interest of everybody (obviously except for the cloud providers).
So would love to hear what you all think about it. Especially if it would cause anybody not to use or contribute to a project with uses Common Clause or other concerns you would have.
Thanks!
[1] https://commonsclause.com/
- mindcrime 8y agoIf the chance really arrises, I would prefer to commercialize it myself FWIW, there's no hard rule that says only one firm can commercialize a project. How many vendors, for example, offer commercial Linux distributions?
- n8n-io 8y agoAh yes, you are right. It does not mean it would be impossible but for sure would make it much harder when a big cloud provider can offer it earlier and cheaper.
- mindcrime 8y ago"Cheaper" probably yeah, because they could presumably subsidize the thing with profits from their other services. Not sure about "earlier" though. I mean, if you're the one building it, by definition you have at least the opportunity to move first. Considering how slow big companies usually are, due to all the various committees, bureaucracy, hand-offs, approvals, etc., I think you'd have a very good chance to be earlier than those guys. And, perhaps ironically, you could build a business around your "thing" by using a public cloud provider. Look at the Netflix / Amazon relationship, for example. They are direct competitors in terms of streaming video, but yet Netflix builds on AWS. Yes, that's a different kind of thing, but my point is that, in real life, things aren't always so "black and white" as "Oh, big cloud provider came along, commercialized my thing, GAME OVER." Consider too that many (most? all?) markets can be segmented in ways that support multiple vendors. For all the talk about monopolies that is the rage today, ask yourself how many products you can think of that literally have ONE and ONLY ONE provider. I doubt it's very many. There might be one dominant vendor and a constellation of smaller ones, but maybe it's OK to be one of those smaller firms that fills a specific niche. Heck, find enough of those niches and maybe you can use the old Komatsu "encircle Caterpillar"[1][2] strategy. [1]: https://dilipnaidu.wordpress.com/2010/05/06/strategic-intent/ https://dilipnaidu.wordpress.com/2010/05/06/strategic-intent... [2]: https://hbr.org/2005/07/strategic-intent https://hbr.org/2005/07/strategic-intent
- n8n-io 8y agoThanks a lot. I will have to give it a read! About the earlier. Yes, it would be for sure possible to be the first. The problem is just that it would take a considerable amount of time which in the end would be kind of "harmful" for the project itself. Because instead of fixing bugs or adding important features I would spend my time on creating a hosted version which would not really further the project itself. Unless of course, the hosted version would help the project by growing the community as it would be easier for people to use because they do not have to set it up themselves. Also, could it help to fund further development early on. So maybe should really think about a hosted version earlier than planned.
- mindcrime 8y agoBecause instead of fixing bugs or adding important features I would spend my time on creating a hosted version which would not really further the project itself. That's a fair point. Maybe you could partner with somebody who wants to focus on that side of things, while you focus on the core project, and work out some kind of revenue sharing agreement or something?