Forgejo is changing its license to a Copyleft license. This blog post will try to bring clarity about the impact to you, explain the motivation behind this change and answer some questions you might have.

…

Developers who choose to publish their work under a copyleft license are excluded from participating in software that is published under a permissive license. That is at the opposite of the core values of the Forgejo project and in June 2023 it was decided to also accept copylefted contributions. A year later, in August 2024, the first pull request to take advantage of this opportunity was proposed and merged.

…

Forgejo versions starting from v9.0 are now released under the GPL v3+ and earlier Forgejo versions, including v8.0 and v7.0 patch releases remain under the MIT license.

  • whou@lemmy.ml
    91·
    3 months ago

    always a pleasure to see big projects going full copyleft amidst the recent influx of projects sadly going source-available

    this is the main reason not to sign a CLA (edit: both the aforementioned projects seem to adopt CLAs, though it seems that they aren’t hostile and are especially pro-copyleft. see this amazing correction by @princessnorah@lemmy.blahaj.zone for context). you should not let a third-party use your copyright to restrict user freedom in the future because they swear “they ❤️ open source” now, and would never use your code to only their own benefit.

    • Norah - She/They@lemmy.blahaj.zoneEnglish
      271·
      3 months ago

      Except both of the projects you just linked too have CLAs, which they updated on switching to AGPLv3. Both use them as a way to offer dual-licensing, so they can charge companies for an AGPL-exception by selling them a proprietary-licensed version, which then supports the FOSS-development. They both were also only able to change to AGPL because of already existing CLAs. At least in Element’s case though, they created a two-way commitment in their CLA:

      Now, CLAs come in all shapes and sizes: some good and some bad. It’s critical to understand that our reason for requiring one here is to give us the right to sell AGPL exceptions: not to “do a Hashicorp” and switch to a non-FOSS licence in future. We’ve made this clear in the wording of the CLA (using a similar approach to Signal’s CLA) by committing to distributing contributions as FOSS under an OSI-approved licence – many thanks to those who gave feedback on the original announcement to suggest this. You can find the final CLA wording here, derived from the well-respected Apache Software Foundation CLA.

      Here’s the specific text from the CLA:

      Element shall be entitled to make Your Contribution available under Element’s proprietary software licence, provided that Element shall also make Your Contribution available under the terms of an OSl-approved open-source license.

      I personally consider that a fairly reasonable term. Especially because they specified an OSI-approved license. Element are always going to be bound to that now. This is like the copyleft of contributor license agreements.

      • whou@lemmy.ml
        2·
        3 months ago

        whoa! thanks a lot! that’s my mistake.

        thanks for the awesome info, I should’ve at least check the repo of the individual projects first (only did so with Forgejo).

        I totally agree with you, and do think that it is possible to have positive and harmless CLAs. though I do think we should always take a step back and not assume that a project’s CLA will be in favor of our copyright, with the case being more the exception than the norm, unfortunately.

        in the end, I will always be happy that a copyright holder wants to be able to reliably make money with copyleft software, but I can never really face a CLA without at least initial hostility anymore. you may say I have prejudice against CLAs lol

        • Norah - She/They@lemmy.blahaj.zoneEnglish
          21·
          3 months ago

          Yeah honestly these feelings are so bloody valid after the way they’ve been used lately. It’s always good to be sure of these things.

      • LemoineFairclough@sh.itjust.worksEnglish
        1·
        3 months ago

        Maybe a more appropriate practice is to only engage with a Contributor License Agreement if the repository one contributes to is already available with the GNU AGPL or one is actually in control of some money the person one contracts with will gain due to one’s changes. For example:

        • Before I contribute to a project, I should make a copy of as many relevant repositories I’m able to and ensure each one is easy to redistribute, and only make changes to my copies. That way, I can continue distributing the improved software if a person I engage in a CLA with does something I don’t like later, but they are still able to apply any change of mine to a repository that gets more attention (thus helping more people). Also, I might get money (as an employee) for doing this, which would prevent that money from being used against the Free Software Movement.
        • If I were a board member, manager, or employee and someone engaged in a CLA with an entity I have influence over, I have a good chance to direct more money to support the Free Software Movement (or block dealing with a person where doing so would be harmful).

        If I have already fixed a software issue, made it clear what license should be used with my change, and made it available to the public, I wouldn’t necessarily be against engaging in a CLA (though I might ask to be paid to do so since I wouldn’t normally go out of my way to manually sign things, and I do value my time).

        FYI I can navigate to https://blog.hansenpartnership.com/why-microsoft-is-a-good-steward-for-github/ from https://drewdevault.com/2018/10/05/Dont-sign-a-CLA.html (using https://blog.hansenpartnership.com/gpl-as-the-best-licence-governance-and-philosophy/ for an intermediary step), so I’m a little suspicious about the author’s thoughts on these matters. I also didn’t find any useful information about the GNU Affero General Public License from the same author, and I consider the GNU AGPL to be important based on https://ploum.net/2024-07-01-opensource_sustainability.html and https://lemmy.world/post/16602135

        • Norah - She/They@lemmy.blahaj.zoneEnglish
          31·
          3 months ago

          Would you not consider signing a CLA (without remuneration) if it binds a project to releasing your code under an OSI license? The only way they could have done better I think is by specifying AGPL instead. I’m not trying to argue that all CLAs are good here, but I don’t think that when they achieve the goals of the free software movement, they should be treated with suspicion or derision.

          Honestly, all of the recent light shone on CLAs is a great thing. But there are still valid reasons to maintain a unified copyright for a project. None of these projects would have been able to move to AGPL without having used a CLA for that purpose. It also allows enforcement of that license via things like litigation, because you can have one entity on the docket, instead of a thousand contributors all defending their copyright.

          I think the correct course of action isn’t to avoid signing one, but to force projects to commit to the social contract of open source in writing. I think there’s also a discussion that no one has earnestly talked about. A contributor license agreement is a contract between two parties, and under contract laws both parties must materially benefit. “I will get x, and you will get y”. This is known as consideration, and courts will nullify contracts that only benefit one of the parties. The only consideration I think there is to be found in most of the CLAs that have been brought up lately, is basically “your code will be merged into the project and released under it”. They don’t specify the continuation of open source, but it’s heavily implied by the aforementioned social contract. So when someone like RHEL goes and closes their source, they’ve essentially changed that contract to “you will sign over your copyright to us, and we will exploit your labour for profit”. That is not consideration, and it calls into question the validity of every single CLA signed. I genuinely think there’s grounds for every RHEL contributor that signed one to form a class and sue, and I would love to see FSF or EFF organising and supporting that sort of effort.

          Back to Element for a second though, as far as I can see, their new CLA is a valid contract, because it gives a right to the contributor, that their code will always be released under an OSI license. So if a successful suit was brought against someone like RHEL, or Hashicorp, we could see other projects scramble to repeat Element here. That would be, in my opinion, a very good thing for the free software movement.

          • LemoineFairclough@sh.itjust.worksEnglish
            1·
            2 months ago

            I would probably be most upset if a program had its license changed to be “permissive” like the Expat License. I might accept making a reasonable number of contracts to provide a “proprietary” license that doesn’t give any new person (or corporation) permission to distribute software, but a “permissive” license allows people to work against the Free Software Movement without any oversight.

            That being said, I don’t think I would be satisfied if a contract specified that “an OSI license” will be used: I would prefer for a specific license to be used rather than just one of a class of licenses. However, if an appropriate license is already being used, I wouldn’t have to sign anything to protect myself!

            In general, I’m probably against changing the license of any software: changing a license seems like a lot of work that can probably be better spent elsewhere, and I consider it to be unlikely that any GPL license will need to have a new version anytime soon (they might, and the v3 versions are clearly better to use than any preexisting version, but they might also change for the worse if the FSF changes for the worse), and the GNU AGPLv3 clearly reflects the present state of the art of licensing (so using any other license that is compatible with it would strike me as strange). If I actually had a reason to study any source code that wasn’t available with the GNU AGPLv3 or the GNU GPLv3, I would probably be better off studying the requirements of people who use that software and making my own version with a license I prefer: that way I’d provide more certainty that my changes are available with an appropriate license.

            Changing the license of existing projects is clearly useful sometimes, but adapting proprietary programs for use with more open systems hasn’t been very useful to me so far. For example, I use LibreOffice rather than trying to get Microsoft Word to work with my computer.

            There might be some people who argue that any influence of a GPL license will make their business model less profitable, but if that’s the case we’re already dealing with business, so I might as well receive my fair share of money and influence from the business (or withhold my participation entirely, if that would be less harmful).

            Just to be clear, I’d avoid studying source code only available with the GNU Lesser GPL unless things change.

            FYI, I’m discussing “studying” instead of “changing”, since avoiding even looking at source code of questionable provenance might help protect me from accusations of plagiarism. If someone exploits a computer system to copy source code without permission and shares it with me, and then I make a similar program, the copyright holders whose program I copied might have a justified reason to complain. However, there is less chance of that if I study people’s public messages or even compare the behavior of one program to another, and if I don’t study a program, I probably can’t change it either.

            I’ll note that, despite what I’ve written,

            • I don’t actually scrutinize licenses of repositories very much: if I come up with a useful patch, I’m inclined to share it even if it’s unclear what license will be used with it. However, I do scrutinize the license of programs I install (for example, I like that yast2 lets you see the license of packages before installing them), so I’m more likely to want to contribute to programs that are compatible with a GPL license.
            • I have submitted a patch with text like “By submitting this I give permission to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of this contribution to any person obtaining a copy of this software” that was provided as a template.
            • I wouldn’t complain much if someone got paid $1,000,000 to distribute some software with the Expat License, since I can’t fault them for taking care of themselves.

            FYI, “nominal consideration” is very likely sufficient to establish a contract (“contracts in the United States have sometimes have had one party pass nominal amounts of consideration, typically citing $1”), and a contract is probably hard to neutralize in general due to things like mutual drafting clauses and savings clauses.

  • theshatterstone54@feddit.uk
    651·
    3 months ago

    Unless you’re selling the software or licenses to it, I don’t really see a reason not to go copyleft. I mean, think about it. If someone tries to make your thing but better, they have to release the modifications, so you can grab it for yourself and suddenly you’re at the same level. If they piggyback off your work, you can piggyback off theirs, and you have the advantage of being the original. Correct me if I’m wrong.

        • leopold@lemmy.kde.social
          1·
          3 months ago

          You can do that with permissively licensed software too. Except with those, the party distributing their repackaged version doesn’t have to distribute source code alongside it. A lot of companies avoid copyleft software because they don’t want to or cannot deal with stricter licensing terms. If you’re a company creating commercial software which you intend to sell, you don’t want to use any GPL code, because you want to keep your software closed source to avoid exactly what you described from happening.

          This can be exploited by primarily licensing your open source code using strong copyleft (like the AGPLv3) while selling commercial licenses to businesses that don’t want to comply with the AGPL and are willing to pay up. Qt is able to successfully use this even with weaker copyleft (LGPLv3) because it’s used a lot in embedded systems (like smart cars) which cannot comply with the LGPLv3’s anti-tivoization clause.

          This means copyleft licenses can make it easier to profit if you’re the author of the code, but of course third parties can more easily profit from permissive licenses.

        • Thann@lemmy.mlEnglish
          1·
          3 months ago

          Torrenting has existed for a long time, yet people still buy software. There is a lot more to software distribution than traditional product sale.

          You want to have frequent fixes, compatibility with modern tools, new features and a trustworthy distribution pipeline. These are all things people and corps are willing to pay for in FOSS software.

    • Pup Biru@aussie.zoneEnglish
      3·
      3 months ago

      there’s certainly a camp in FOSS that considers “whatever you like including commercial activity” to be the one true valid version of “free software”

      like… if someone wants to take an MIT project, add a bunch of extra features to it keeping some available only with payment, and contribute back bug fixes and some minor features etc, i wouldn’t necessarily say that’s harming the project and this is overall a good thing? it gets the original project more attention

      like it’s perhaps a little unfair, but if the goal is quality and scope of the original project - or even broader of the goal is simply to have technology AVAILABLE even if it is with a few - then that goal has been met more with an MIT-like license than it would be with a copyleft license

  • Darkassassin07@lemmy.caEnglish
    50·
    3 months ago

    So, for the slow people in the back… (me)

    Copyleft = permanently open source? Ie, you can’t take the open source code/project and make it closed source? (or build a new closed project off of it?)

    Or am I misunderstanding?

    • ambitiousslab@lemmy.mlEnglish
      401·
      3 months ago

      Yep, that’s the gist of it. In order to change the license from the GPL, they’d need the permission of all of the copyright holders who’ve contributed code under the GPL to the project. After a few months have passed, this basically makes it impossible (or at least extremely difficult) since at least one person (and likely many people) will say no.

    • logging_strict@lemmy.ml
      9·
      3 months ago

      AGPLv3 is not anti-business or anti-money. It’s saying if you want to use the code in a closed source project you need to pay the copyright holder

      The copyright holder is the original author, not a maintainer or someone who forked a project and renamed it.

      That’s why the #1 thing mentioned in copyleft licenses is you can’t alter the copyright notice and declare yourself the original author

      AGPLv3 is a good license to choose. All the other licenses are naive and do not combat closed source projects and the slave worker that keeps our projects unfunded

    • cadekat@pawb.social
      8·
      3 months ago

      Copyleft means: “if you modify the program and share it, you also have to include the source code for your modifications.”

      The owner of the copyright (usually the developers or their employer) can still change the license later.

  • ampersandcastles@lemmy.mlEnglish
    351·
    3 months ago

    “Copyleft licenses do not only benefit the developers. They also guarantee freedoms to users of the software. They reduce the risk of exploitive business practices, like creating a modified version of Forgejo with less freedoms to the users, which could ultimately trap users in a vendor lock-in.”

    God, you absolutely love to see it. So called “permissive” licenses should be banned because of this.

    • Urist@lemmy.mlEnglish
      201·
      3 months ago

      GitHub has long sought to discredit copyleft generally. Their various CEOs have often spoken loudly and negatively about copyleft, including their founder (and former CEO) devoting his OSCON keynote on attacking copyleft and the GPL. This trickled down from the top. We’ve personally observed various GitHub employees over the years arguing in many venues to convince projects to avoid copyleft; we’ve even seen a GitHub employee do this in a GitHub bug ticket directly.

      You only need to know that corporations do not like copyleft to know it is good. The same goes with capitalists and wealth tax / inheritance tax.

      • whoisearth@lemmy.ca
        7·
        3 months ago

        It really applies to anything. Whenever you read of policy related arguments always look at the people complaining. Rule of thumb is it gives you a good idea of who the policy hurts the most. If it’s large companies or rich people complaining by and large it’s probably a good policy.

      • LemoineFairclough@sh.itjust.worksEnglish
        512·
        3 months ago

        Wealth Tax

        I am against any wealth tax. The revenue services for many governments are very focused on not blocking economic growth, and then periodically taking a reasonable amount of wealth.

        In the end, only wealth can be taxed (things that aren’t physical can’t be seized and auctioned). However, I don’t want to be forced to let someone into my house to calculate how much stuff I have.

        In general, I think it’s more reasonable to monitor wealth moving (and more so if wealth moves between people) rather than to force people to cooperate with monitoring wealth staying in the same place. I don’t want someone checking up on whether I own the same stock certificates or gold bars each year; that seems like an insult to my dignity.

        Enforcement Complications

        Distribution

        The top 10% as a whole pays 71.22%, while the bottom 50% of taxpayers account for only 2.89% of all income taxes.

        I don’t think that focusing on people who already pay a disproportionate amount of tax will be very helpful. Rapidly changing what is taxed (wealth vs income) would probably be harmful, as people will probably have trouble adapting to significantly different policies. For example, we’d probably hear about people who happen to have inherited expensive houses being unable to pay thousands of dollars for tax bills, after thinking that they wouldn’t be affected by policy changes.

        Avoidance

        If there was a wealth tax and I was rich enough to spend a lot of time managing my money, I would just create a “charitable organization” that I and my family completely control, then have it pay people to do things I would want them to do anyway, and maybe even try to let the charity pay a high wage to its managers (such that I could be a manager and get the charity to pay for my yearly living expenses, directly or indirectly). I also might be able to get away with using a trust or charitable remainder trust to avoid being affected by a wealth tax.

        I don’t know the degree to which tax exempt organizations affect my life, but I do know that trusts have a relevant affect on my life, since they are often used to own land, specifically by landlords of housing and by people who own land that is worth a lot of money. How they are dealt with would probably have to significantly change in order to accommodate a wealth tax.

        Inheritance Tax

        I’m not sure I’m against inheritance tax, but it might be an unnecessary complication. Treating inheritance like a gift from one person to another at the moment of their death might make things easier for everyone. The policies regarding gifts are relatively clear: https://www.irs.gov/businesses/small-businesses-self-employed/gift-tax https://www.irs.gov/faqs/capital-gains-losses-and-sale-of-home/property-basis-sale-of-home-etc/property-basis-sale-of-home-etc

        However, having separate inheritance law might also make things less painful for some people. If my assets suddenly gained or lost a large amount of value just before I died, I wouldn’t want that to justify taking more wealth from my heirs. Having a special way to value assets gained due to someone dying might be more reasonable than treating each receipt as a gift.

        • Urist@lemmy.mlEnglish
          41·
          3 months ago
          1. Wealth tax does not block economic growth, rather the opposite, because it forces wealth to be reinvested to not lose too much value.
          2. You clearly need a lesson in proportional taxation if you think people would have their personal property appropriated.
          3. I do not give a fuck about you placing your dignity in ownership of material assets, that is a you problem.
          4. The top 10% pay less income taxes as a fraction of their income than the bottom 10%.
          5. Really, we should remove the capitalist class because they will fight back to the detriment of everyone else.
          6. I do not give a fuck about the IRS. I am not an American. My country actually has a wealth tax.
          7. You are repeating misinformation and capitalist propaganda with little understanding of what you are saying. Have you even reflected on what “the economy” really is? If you are a trickle-down Reaganomics-follower, you might want to get your brain checked.
          • iopq@lemmy.world
            2·
            3 months ago

            I would give up my US citizenship if it were passed. It’s enough I live abroad and still pay taxes for my dividends. If you start taxing my investments directly, I’ll have to get a different passport

            • Urist@lemmy.mlEnglish
              2·
              3 months ago

              The (then) right-wing Norwegian government (left-wing by US standards ordered a study because they wanted to claim this. The results (source in Norwegian, use a translator) were the opposite of what they wanted.

              For example: “the businesses used more money on their workers when the stock owners were subjected to higher wealth tax” (paraphrasing here).

              Is a car or shirt or house personal property?

              Yes.

              I reference “dignity” because it’s part of “the unshakeable foundation of the Republic of Poland”

              Yea, not sure I care about the right-wingers in Poland either.

              cooperate with you if you remind them of the Soviet Union, and I expect that saying “we should remove the capitalist class” will do that.

              Well, I think we should be honest about our intentions, unlike the capitalist class that tell you “brown people” or “the economy” is the reason they pay you slave wages.

              What misinformation am I repeating? I wouldn’t have written a statement that I don’t think is true, so I suggest you point out anything you think is incorrect and explain your perspective, and maybe share a URL for some more interesting sources.

              The part about seizing personal property to pay taxes, for instance. A progressive tax system can have bottom tiers paying no taxes. The right are those who impose high tax rates on the middle class and poor, in order to make them hate taxes.

            • bane_killgrind@slrpnk.netEnglish
              2·
              3 months ago

              The top 10% as a whole pays 71.22%, while the bottom 50% of taxpayers account for only 2.89% of all income taxes.

              This is misinformation, because it paints a picture of the rich being hard done by.

              The bottom 50% pays an actual tax rate that is a higher percentage of their earnings than the top 50%. The richer you are, the more opportunity you have to reduce your tax burden. https://www.pbs.org/newshour/economy/column-much-poor-actually-pay-taxes-probably-think

              Your own numbers are an indicator of massive income disparity.

              • LemoineFairclough@sh.itjust.worksEnglish
                1·
                3 months ago

                I think the tax system in the USA is designed to reward people who form corporations and then get people employed. People who are employed don’t have as much time to work on reforming institutions, so giving a tax break for employing people makes powerful people’s lives easier. In order to keep this process revenue neutral, earned income is taxed instead of taxing business as much. After extracting money from people’s labor (since labor is clearly necessary in order to create wealth), the remainder of budget needs is made up from whatever resources are easily available (which is currently the assets of rich people, since they have been given a lot of money to get people employed).

                • bane_killgrind@slrpnk.netEnglish
                  2·
                  3 months ago

                  Yeah dude. The value of these corporations in inflated or neutral at best. Corporations pop up that are solely created to shelter or exploit to expand wealth.

                • bane_killgrind@slrpnk.netEnglish
                  2·
                  3 months ago

                  That doesn’t take into account non federal tax.

                  https://itep.org/who-pays-taxes-in-america-in-2024/

                  This says it more explicitly.

                  using a more realistic definition of income that includes unrealized capital gains, they found that the same 25 Americans paid just 3.4 percent of their income in taxes during that period. If unrealized capital gains were included in these estimates, ITEP, too, would calculate a much lower effective tax rate for the rich

        • bane_killgrind@slrpnk.netEnglish
          2·
          3 months ago

          I thought this was going to be fun satire.

          You don’t really know how anything works if you think all this.

          • LemoineFairclough@sh.itjust.worksEnglish
            1·
            3 months ago

            How do things work? I provided my perspective, partly so that I could refer to it later, so it would be enlightening to learn about yours.

            • bane_killgrind@slrpnk.netEnglish
              31·
              3 months ago

              Nah

              Question is, do you know how much the tax revenue is in your area

              Is that tax revenue transaction based or wealth based

              Would taxing in your paradigm be reasonable or sustainable in the context of the government expenditures in your area?

        • LemoineFairclough@sh.itjust.worksEnglish
          11·
          3 months ago

          FYI, I think that focusing on proportional representation electoral reform is the best way to increase respect to the inherent dignity of the person, and that to “choose a defining fight” is better than trying to focus on more than one thing.

          I happen to be interested in tax policy, but I would prefer for the electoral system to improve before tax policies change.

          See also !fairvote@lemmy.ca / https://sh.itjust.works/comment/12708609

  • solrize@lemmy.world
    22·
    3 months ago

    Forgejo appears to be a self hostable code sharing web platform like gitea or GitHub. I’ve used gitea for this. Is Forgejo better or what? There is also Gitlab which is way bloated.

    • λλλ@programming.dev
      15·
      3 months ago

      Its a fork of gitea. It formed when gitea did something that the community didn’t like. I don’t remember the reasoning. But, I remember someone sending me a bunch of info about it in the past and it was enough for me to switch.

      • solrize@lemmy.world
        5·
        3 months ago

        Thanks, I didn’t know about that. Gitea itself is a fork of Gogs though. Wheel of karma?

        • Opisek@lemmy.world
          2·
          3 months ago

          You can actually (for now) just replace gitea with forgejo while keeping all the files in place and it just works. Really easy then using docker, cause all it takes is changing the container image.

          • solrize@lemmy.world
            1·
            3 months ago

            Thanks. I’ve run gitea without docker and it was fine. I’ll have to figure out docker someday though.

  • exu@feditown.comEnglish
    20·
    3 months ago

    I wonder why they didn’t go with AGPL, which is made for server-based software like Forgejo.

    From my understanding GPL does nothing to force hosting services to open their code as long as they don’t distribute builds.

    • thatsnothowyoudoit@lemmy.ca
      15·
      3 months ago

      As someone who worked at a business that transitioned to AGPL from a more permissive license, this is exactly right. Our software was almost always used in a SaaS setting, and so GPL provided little to no protection.

      To take it further, even under the AGPL, businesses can simply zip up their code and send it to the AGPL’ed software owner, so companies are free to be as hostile as possible (and some are) while staying within the legal framework of the license.

      • ulterno@lemmy.kde.socialEnglish
        1·
        3 months ago

        simply zip up their code and send it to the AGPL’ed software owner

        That seems good enough to me. No?

        Sure, it would be nice to have the whole versioning system history, but even having the current version of the code makes it possible to do a code review. And modification too.

        Self-Building and deployment might turn out to be harder, but that would just be about which side is having to put the effort of making something comprehensive.

        • thatsnothowyoudoit@lemmy.ca
          4·
          3 months ago

          Good enough? I mean it’s allowed. But it’s only good enough if a licensee decides your their goal is to make using the code they changed or added as hard as possible.

          Usually, the code was obtained through a VCS like GitHub or Gitlab and could easily be re-contributed with comments and documentation in an easy-to-process manner (like a merge or pull request). I’d argue not completing the loop the same way the code was obtained is hostile. A code equivalent of taking the time (or not) to put their shopping carts in the designated spots.

          Imagine the owner (original source code) making the source code available only via zip file, with no code comments or READMEs or developer documentation. When the tables are turned - very few would actually use the product or software.

          It’s a spirit vs. letter of the law thing. Unfortunately we don’t exist in a social construct that rewards good faith actors over bad ones at the moment.

          • ulterno@lemmy.kde.socialEnglish
            01·
            3 months ago

            Or it could just be laziness.

            In case you don’t want to put the effort into making a system into your organisation, to update code in a public-facing versioning system hosted setup, just tell someone to zip whatever you compiled and package it along with the rest of the stuff.

            • Packaging the whole .git directory would make it significantly larger
            • This method is bankruptcy-safe, as compared to hosting on the internet.
              • Ideally, I would like there to be both, a zip (in case I don’t have an internet atm) and a link to the vcs
            • Yes, the companies mostly don’t care enough and people doing it won’t think of it as being hostile, just as putting the least effort.
    • LemoineFairclough@sh.itjust.worksEnglish
      6·
      3 months ago

      It seems there was a pre-existing agreement to use the GNU GPL with Forgejo, and it seems to me that the GNU AGPL is not compatible with the GNU GPL.

      There is more discussion about that around https://codeberg.org/forgejo/discussions/issues/201

      I’m assuming that there has been some resistance to using the GNU AGPL with Forgejo (it seems the discussions about licenses has been contentious), and the GNU GPL seems to have been discussed much more than the GNU AGPL. It was probably overwhelmingly likely that we would get Forgejo with the GNU GPL rather than the GNU AGPL. I would have preferred that the GNU AGPL was used instead, but I’m not going to worry about it much since I probably can’t change this situation for the better.

      • exu@feditown.comEnglish
        4·
        3 months ago

        You’re right, seems like GPLv2 is incompatible with AGPL. GPLv3 includes extra clauses to allow it.

        From the GNU Licensing page

        Please note that the GNU AGPL is not compatible with GPLv2. It is also technically not compatible with GPLv3 in a strict sense: you cannot take code released under the GNU AGPL and convey or modify it however you like under the terms of GPLv3, or vice versa. However, you are allowed to combine separate modules or source files released under both of those licenses in a single project, which will provide many programmers with all the permission they need to make the programs they want. See section 13 of both licenses for details.

    • logging_strict@lemmy.ml
      21·
      3 months ago

      Exactly. They obviously didn’t research licensing enough.

      Closed source projects need to pay for licensing. Or they will force you to work for them designing web forms and smartphone apps

      Am i wrong?

    • Fisch@discuss.tchncs.deEnglish
      10·
      3 months ago

      It means you don’t have to release the source code of your software if you use the source code of the open source project

    • dgkf@lemmy.ml
      61·
      3 months ago

      Permissive licenses permit a broader range of use compared to “copyleft” licenses.

      “copyleft” here just being a cute way of being the opposite of copyright - instead of disallowing others from what they can do with “copyrighted” code, “copyleft” requires that they (upon request) share modifications to your code.

      Permissive takes away this requirement to share your modifications. “copyleft” is considered more free and open source (FOSS), permissive is more business friendly.