Hacker News
Should your developer company go open source?
oxag3n
|next
[-]
Even before AI ElasticSearch got smashed by Amazon with their own product.
Now with AI "translation", they don't even care about license.
Agres
|next
|previous
[-]
0xbadcafebee
|next
|previous
[-]
I know some people want to ban AI posts, but I want the opposite: ban any post until AI has looked over it and adds its own two cents based on the consensus of the entire internet & books it's trained on.
CactusBlue
|next
|previous
[-]
Didn't Airbyte rugpull their license to ELv2?
benrutter
|root
|parent
|next
[-]
In reality, since about 1 year into the project, it's operated with a mix of open and "less open" licenses for different parts of the codebase, in a way that would make it difficult to just use the MIT licensed bit.
I think that kinda proves the point you were going for.
[0] https://github.com/airbytehq/airbyte/commits/master/LICENSE
iberator
|next
|previous
[-]
kaicianflone
|next
|previous
[-]
With consensus.tools we split things intentionally. The OSS CLI solves the single user case. You can run local "consensus boards" and experiment with policies and agent coordination without asking anyone for permission.
Anything involving teams, staking, hosted infra, or governance sits outside that core.
Open source for us is the entry point and trust layer, not the whole business. Still early, but the federation vs stadium framing is useful.
spacebanana7
|next
|previous
[-]
If your developer company gets popular you’ll be rich enough anyway. You might need to choose between screwing over your VCs by not monetising or screwing over your customers by messing around with licences.
But yourself as a founder will likely be okay as long as the tool is popular.
metadata
|root
|parent
[-]
Startups die for a variety of reasons, even if products are popular and loved.
Joel_Mckay
|next
|previous
[-]
Community efforts should almost always be kept separate from commercial works.
The one exception occurs during product deprecation, as there is no longer commercial interest in the investors property or curatorship. =3
figmert
|previous
[-]
carefulfungi
|root
|parent
|next
[-]
Having first hand experience with building multiple open source and open core dev infra companies, the advice in this article is spot on. If it is AI slop, it's still good advice.
I'd prefer comments focused on content vs. trying to Turing-test AI generated text.
benatkin
|root
|parent
|next
|previous
[-]
figmert
|root
|parent
[-]
> The only question that matters is this: Does open-source structurally help this product win?
> A hard filter first: Only technical users are emotionally sensitive to open-source.
> Important framing shift: OSS is not the product. OSS is the entry point.
> Open-source is powerful. But only when it is deliberate.
Finally, the random bolded bits of text.
This article is literally copy pasted directly from some LLM, and I'm fairly sure it's ChatGPT.