this post was submitted on 23 Feb 2026
92 points (77.4% liked)
Technology
81869 readers
4659 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
you mean the DCOs? those are nothing like NDAs. if not, which ones you mean?
@WhyJiffie@sh.itjust.works @technology@lemmy.world
Possibly. I don't know the specific acronym they use, but regardless of the acronym: to me, it smells and looks like NDAs insofar it's some kind of analogous version of a "secretive initiation ritual" for a developer who's just trying to help an open-source community. It's an agreement where the developer accepts that anything they contribute free-of-charge is going to be used for enterprise (paid) purposes and any contribution is subject to be altered or removed as the management pleases, sometimes it also involves literal NDA if private (often "enterprise/premium edition") repos are intertwined with the open-source ("community edition") repos.
The ideal open-source, at least to me, would require a developer, any developer no matter who they are or how long their experience is, whenever they wanted to contribute with their coding skills, to simply do a PR or fork a repo, with no bureaucratic or "selling the soul to the Great Corporate" requirements for doing so.
Developing is already mentally demanding for a developer, and adding licensing shenanigans to the equation only complicates things, because now the developer, who's used to talk the language of computers, would need to become knowledgeable about ambiguous social cues, corporate legalese and the differences between a "MIT" and a "GPL" (that's one of the main reasons why I'm quite fond of WTFNMFPL licensing: no legalese).