GrapheneOS android-prepare-vendor Android 12 port must not be used by CalyxOS · Issue #78 · AOSPAlliance/android-prepare-vendor
github.com
You aren't permitted to use this code and it has not been made available under an open source license permitting you to use it as we did with our past code. Drop all of our Android 12 porting w...

🤦🤦

  • hamborgr@lemmy.ml
    51·
    3 years ago

    I don’t quite understand what is happening, could someone give me some context or explain what is going on?

    • zote@lemmy.ml
      13·
      3 years ago

      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.mlM
        61·
        3 years ago

        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·
          3 years ago

          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.mlM
            3·
            3 years ago

            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).

            • m-p{3} ⛔@lemmy.ml
              2·
              3 years ago

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

            • Jedrax@lemmy.ml
              2·
              3 years ago

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

        • zote@lemmy.ml
          0·
          3 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.

      • hamborgr@lemmy.ml
        3·
        3 years ago

        Thanks for the explanation. And you’re right, it almost seems like two little kids fighting each other over something ridiculous.

        • ninchuka@lemmy.ml
          4·
          3 years ago

          the devs are also kicking everyone in the techlore rooms out of their rooms because according to one of the main devs henry has been getting his community to raid graphene and other dumb shit.

          yet I’ve never seen any of that from being in techlore rooms for probably a year? I’ve seen tons of people recommend graphene if people come in asking for a rom recommendation for their pixel phones.

          its very very childish and the graphene dev has also threatened to sue techlore for it as well 🤦🤦

    • Kromonos@fapsi.beOP
      4·
      3 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.