Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
mstdn.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A general-purpose Mastodon server with a 500 character limit. All languages are welcome.

Administered by:

Server stats:

17K
active users

mstdn.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.3

#licensing

9 posts9 participants0 posts today
Public
VM (Vicky) Brasseur

Well, this is worrying.

“If the appellate court upholds that decision, which endorsed database maker Neo4j's right to amend the GNU Affero General Public License, version 3, governing the use of its software with new binding terms, current assumptions about the enforceability of copyleft licenses will no longer apply.”

theregister.com/2025/02/27/adv

The Register · FYI: An appeals court may kill a GNU GPL software licenseBy Thomas Claburn
#OpenSource#FreeSoftware#Licensing
Public
FErki

Many projects mix code and non-code content. Some of them use a single license to cover them all, some decide to apply different licenses to different type of content.

I wonder, how commonly projects use different licenses for their code and non-code content?

If you know examples of this, please consider sharing a link in replies.

Happy to learn about your related experience and insights in replies too.

Please consider boosting for wider reach, if you find it interesting.

· 3 people ·
#licensing
Public
Dan Brown

Came across this questionable legal workaround in a (GPL + Commercial licensed) project today:

>> All contributions to this repository are made under the MIT License

>> If you make a PR, the PR code is licensed as MIT. As soon as I copy (merge) the code into this repository it is then made available under the GPLv3 as part of <project>

Anyone seen something like this before? Seems sketchy and less honest than a required CLA. Just wondering if it's done elsewhere...

#OpenSource#licensing
Public *
Ross A. Baker

I had given up GitHub for non-work use, but I'm coming back with a project under an explicitly non-AI license. It will be fun to see which tools respect it and which don't.

github.com/rossabaker/goodbye-

It will also be fun to dust off my Scheme enough to make the program less trivial and more obviously copyrightable. Pull requests welcome, but only under the MIT NON-AI License!

You wouldn't train on unlicensed code, would you? Contribute to rossabaker/goodbye-ai development by creating an account on GitHub.
GitHubGitHub - rossabaker/goodbye-ai: You wouldn't train on unlicensed code, would you?You wouldn't train on unlicensed code, would you? Contribute to rossabaker/goodbye-ai development by creating an account on GitHub.
#AI#Licensing#Scheme
ExploreLive feeds
About