I ask this because I think of the recent switch of Ubuntu to the Rust recode of the GNU core utils, which use an MIT license. There are many Rust recodes of GPL software that re-license it as a pushover MIT or Apache licenses. I worry these relicensing efforts this will significantly harm the FOSS ecosystem. Is this reason to start worrying or is it not that bad?

IMO, if the FOSS world makes something public, with extensive liberties, then the only thing that should be asked in return is that people preserve these liberties, like the GPL successfully enforces. These pushover licenses preserve nothing.

  • eleijeep@piefed.social
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    2 hours ago

    Interesting, but ultimately a roundabout justification for why the author chose a non-FOSS license for their startup Slack-clone built on ATProto.

    They talk about “pro-labor licensing” but what they mean is pro- their -labor, not pro- anyone else’s -labor.

    GPL is already the most pro-labor licensing since it respects the work of anyone who contributes in equal measure, and does not hold the “original” founding author in higher regard.

    It’s really quite something to rail so unequivocally against the “fascistic mega-corps” and “autocratic corpostates” in your licensing justification blog post and then build your commercial product on top of Bluesky .