Open Source

30339 readers

1268 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Posts must be relevant to the open source ideology
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago

MODERATORS

Cloak@lemmy.ml

kevincox@lemmy.ml

CrypticCoffee@lemmy.ml

Lettuceeatlettuce@lemmy.ml

More drama around GrapheneOS and CalyxOS (github.com)

submitted 2 years ago by kromonos@fapsi.be to c/opensource@lemmy.ml

12 comments fedilink hide all child comments

🤦🤦

all 14 comments

sorted by: hot top controversial new old

[+] hamborgr@lemmy.ml 7 points 2 years ago* (last edited 2 years ago) (2 children)

[deleted]

[–] zote@lemmy.ml 14 points 2 years ago (2 children)

something about calyx kicking graphene out of their AOSP alliance project, which graphene retaliated too by denying calyx the right to use their code. It seems a little bit like a game where both parties brought their ball to play, and then both sides said screw you guys, we're going home.

[–] AgreeableLandscape@lemmy.ml 4 points 2 years ago (2 children)

which graphene retaliated too by denying calyx the right to use their code

If they're actually open source, this should be literally impossible.

[–] jedrax@lemmy.ml 5 points 2 years ago (1 children)

Talk about just throwing the licenses out the window. It’s still open source, since you can read it all to audit, but the use of the code is no longer free with attribution if they decide a single person cannot use it.

Though there’s no way the maintainer cares about this. Given how long this dick measuring contest has been going for.

[–] AgreeableLandscape@lemmy.ml 3 points 2 years ago (2 children)

Talk about just throwing the licenses out the window. It’s still open source, since you can read it all to audit, but the use of the code is no longer free with attribution if they decide a single person cannot use it.

Actually, most open source licenses (including GPL) have a clause saying that the freedoms granted by the license cannot be revoked as long as the user follows the obligations (namely crediting the author and making their changes open source).

[–] jedrax@lemmy.ml 1 points 2 years ago

That's why I said they're throwing the license out the window. Flagrantly disregarding the text of the license.

[–] mp3@lemmy.ml 1 points 2 years ago

They can change the license for future releases, which would basically block them from using the updated source code.

[–] zote@lemmy.ml 1 points 2 years ago

I'm no legal expert, but it's something to do with the fact that the original code for this was not open source, and was written by a dev not associated with either project. Some Graphene dev updated it for android 12, under whatever license, which somehow meant they could tell calyx they couldn't use the code for android 12. I seem to remember reading somewhere that Graphene are rewriting the code under a full OS license, which they said they would have no issue with calyx using that under the rules of that license.

[–] kromonos@fapsi.be 4 points 2 years ago

To be honest, I would also like to know that. I only know about the beef, but I don't know, how it started and going on exactly.

[–] hello_lebbit@lemmy.ml 6 points 2 years ago

*menchildren's playground 😑😑😑

[–] jedrax@lemmy.ml 4 points 2 years ago

Spicy 🌶

[–] Yujiri@lemmy.ml 1 points 2 years ago

I don't know the context here, but I'm reminded of a time I got into an argument on twitter about secure boot with a Graphene OS rep and it ended with them telling me "you are not welcome to use our upstream Linux and LLVM patches"