@WhyJiffie@sh.itjust.works @technology@lemmy.worldPossibly. 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 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, 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).