@geerlingguy

So in a nut shell - the #GPLv2 says if #RedHat give you the binaries, they must also give you the source code (if you want it).

But if you do something they don't like (e.g. break their EULA) they can refuse to give you more/future binaries, and without those binaries you're not entitled to more/future source code either.

And it's always been this way, but it's not been strictly enforced before now.

@elecharny @jimjag @linkedin this says recipients can freely distribute the source:

“6. Each time you redistribute the Program…, the recipient automatically receives a license from the original licensor to copy, distribute or modify [it] subject to these terms and conditions. *You may not impose any further restrictions* on the recipients' exercise of the rights granted…"

https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html

#GPLv2 #RedHat

Recommended watch: GPLv3 vs GPLv2, according to Linus Torvald (and why Linux is GPLv2 only)
➡️ https://www.youtube.com/watch?v=PaKIZ7gJlRU

I'd love to see (A)GPLv3 everywhere, but it's very interesting to watch. I do agree that it should have been another license.

#AGPLv3Everywhere #FreeAndOpenSource #FreeAsInFreedom #GNU #GPLv2 #GPLv3 #Freedom #Software #License

Recommended watch: GPLv3 vs GPLv2, according to Linus Torvald
https://www.youtube.com/watch?v=PaKIZ7gJlRU
Personally, I'm actually siding with Richard Stallman's view, but it surely is interesting to watch. #AGPLv3Everywhere #FreeAndOpenSource #FreeAsInFreedom #GNU #GPLv2 #GPLv3 #Freedom #Software #License

Recommended watch: GPLv3 vs GPLv2, according to Linus Torvald
https://www.youtube.com/watch?v=PaKIZ7gJlRU
Personally, I'm actually siding with Richard Stallman & the FSF, but it surely is interesting to watch. #AGPLv3Everywhere #FreeAndOpenSource #FreeAsInFreedom #GNU #GPLv2 #GPLv3 #Freedom #Software #License

The whole #OpenGameLicense debacle reminds me a lot of when version 3 of the #GNU #GPL came out, except that this time it's being done by a for-profit company that may make use of the new terms to go after other for-profit companies, so it's much more difficult to support the decision on intent (regardless of wording).

#OGL #GPLv2 #GPLv3 #GPL2 #GPL3 #freeSoftware #freeCulture

Friendly reminder to uninstall #Audacity and install Tenacity.

Audacity is now owned by the Muse Group, who've continued to demonstrate poor stewardship of this open-source gem (more here. Tenacity is a pre-Muse Group #fork of Audacity that aims to preserve the project's original goals and #GPLv2 #licensing.

#FOSS @tenacity

Wenn ihr zufällig auf der Suche nach einem erweiterbaren und flexibel einsetzbarem Lernmanagementsystem seid, das für den deutschsprachigen Raum und dessen Anforderungen entwickelt wurde und zudem freie Software ist, dann schaut euch doch mal Stud.IP an:

https://www.studip.de/

(Transparenzhinweis: Ich arbeite beruflich an Stud.IP)

#StudIP #LMS #Bildung #FLOSS #Software #GPLv2

Wenn ihr zufällig auf der Suche nach einem erweiterbaren und flexibel einsetzbarem Lernmanagementsystem seid, das für den deutschsprachigen Raum und dessen Anforderungen entwickelt wurde und zudem freie Software ist, dann schaut euch doch mal Stud.IP an:

https://www.studip.de/

(Transparenzhinweis: Ich arbeite beruflich an Stud.IP)

#StudIP #LMS #Bildung #FLOSS #Software #GPLv2

@humanetech

Years ago I had a similar issue after I forked #HarveyOS after they violated #GPLv2 (details here, bad story involving #Google and @conservancy: http://www.tesio.it/2018/02/14/what-i-wish-i-knew-before-contributing-to-open-source.html ) I asked #FSF how to better attribute previous work.

The context there was a bit more complex (GPLv2 code without file level notice), but here what I've learnt:

1. Preserving commit history is not a #copyleft requirement BUT things will be way easier if you preserve it when shit happens¹

2. Retaining existing copyright statements of each file is a copyleft requirement

3. if you fork copylefted code that lacks file level licensing headers it is a good idea to add them first and foremost, or at least as soon as possible.
It makes it easier to understand who are the copyright holders of each file when shit happens even if the #git history get stripped.

4. If you import code from other copylefted project the easiest and safest approach is to import in dedicated files with proper attribution, whenever it's technically feasable.
If it's not, #FSF legal team suggested me to add to the copyright header of the modified file something along the line

```
Portions of this file are Copyright (C) 2015-2018 Giacomo Tesio <giacomo@tesio.it>
See /doc/license/gpl-2.0.txt for details about the licensing.
```

See https://gitea.it/JehanneOS/jehanne/src/branch/master/sys/src/kern/port/dev.c#L1-L6 for an example.

Hope this helps!

____

¹ that's why, after their GPL violation and their refusal to restore my #copyright statements, I asked Harvey to `git revert` up to my first contribution and remove them. And it's also why they `git rebased` instead, squashing some of my contributions in huge commits while removing my name from the repository history.

@kgerloff @rysiek

I've been working on some cool new programming projects recently that I would like to share. First, I made my very first #C program as an introductory project to the C programming language. I've also written a few of programs in #Rust and licensed them under the #GPLv2, which means I feel that these programs are worth legally protecting in this manner. I will be releasing them tomorrow on New Year's Day. There will of course be more to come.

@guenther

#COPPA compliance is a US issue¹.
So if they do not own the whole copyright, such a new restriction terminates their #GPLv2 license.

The problem is that nobody is going to sue #Audacity's new owners and they will go away with that.

¹ but where was COPPA when #Google, #Microsoft, #Zoom and friends were collecting tons of biometric and personal data of kids all over the world during remote schooling in the pandemic?

@cypnk

@Gina One? Many ;) But IMHO the unsung hero that opened up that market 19 years ago and is still being used and developed under #GPLv2 license is #osCommerce. Disclaimer: I once was member of the osCommerce core team. A long time ago.

Which #PasswordManager are folks using? I’m looking at #KeePassXC as it’s #FreeSoftware (licensed under #GPLv2). Any suggestions?

#Security #GPL #Security

Wenn also ein Haus aus nur 0,07% geklautem Material besteht, dann ist das nicht relevant? Das ist voll nachvollziehbar.

#Linux-Kernel-Entwickler gegen #VMware: #OLG #Hamburg will im Februar entscheiden
https://heise.de/-4234888

#GPLv2 #compliance

What is your #opinion on #GPLv3? or are you more of a #GPLv2 kind of person?

Let the debate begin!

There's been a lot of talk lately about developers pulling the "kill switch" and revoking their #GPLv2 licensing over their contributions to the #Linux kernel, mostly spread by a sensationalist article.

Groklaw had an interesting discussion in 2008 indicating why such revocation wouldn't be possible: http://www.groklaw.net/article.php?story=2006062204552163 and, further, in the Copyleft guide: https://copyleft.org/guide/comprehensive-gpl-guidech8.html#x11-540007.4

In short, it is incredibly unlikely that any attempt to revoke the licensing over such code would succeed.