Linux man-pages project maintenance [LWN.net]
lwn.net

From: Alejandro Colomar <alx-AT-kernel.org>

Hi all,

As you know, I’ve been maintaining the Linux man-pages project for the last 4 years as a voluntary. I’ve been doing it in my free time, and no company has sponsored that work at all. At the moment, I cannot sustain this work economically any more, and will temporarily and indefinitely stop working on this project. If any company has interests in the future of the project, I’d welcome an offer to sponsor my work here; if so, please let me know.

Have a lovely day! Alex

  • fossphiEnglish
    9·
    10 days ago

    I agree, but this is mostly an issue with permissive licenses like MIT. GPL and its variants have enough teeth in them to deal with shit like this. I’m scared of the rising popularity of these permissive licenses. A lot of indie devs have somehow been convinced by corpos that they should avoid the GPL and go with MIT and alike

    • csm10495@sh.itjust.worksEnglish
      4·
      9 days ago

      I might be misunderstanding the licenses so correct me if wrong.

      Can companies use GPL code internally without release as long as the thing written with it doesn’t get directly released to the public?

      … or does GPL pollute everything even if used internally for commercial purposes?

      • fossphiEnglish
        4·
        9 days ago

        I think it kicks in when you distribute. For example, let’s say I have a fork of some GPL software and I’m maintaining it for myself. I don’t need to share the changes if I’m the only one using it.

        The point is that people using a software should be able to read and modify (and share) the source when they want to.

        IANAL and all that good stuff

      • skulbuny@sh.itjust.worksEnglish
        2·
        8 days ago

        If it’s only internal then technically the internal users should have access to the source code. Only the people who receive the software get the rights and freedoms of the GPL, no one else.

      • skulbuny@sh.itjust.worksEnglish
        3·
        8 days ago

        AGPL? Google has a ban on all AGPL software. Sounds like if you write AGPL software, corporations won’t steal it.

        Code licensed under the GNU Affero General Public License (AGPL) MUST NOT be used at Google.

        The license places restrictions on software used over a network which are extremely difficult for Google to comply with. Using AGPL software requires that anything it links to must also be licensed under the AGPL. Even if you think you aren’t linking to anything important, it still presents a huge risk to Google because of how integrated much of our code is. The risks heavily outweigh the benefits.

        Any FLOSS license that makes a corporation shit its pants like this is good enough to start from IMO.

        https://opensource.google/documentation/reference/using/agpl-policy