home.social

#softwarelicensing — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #softwarelicensing, aggregated by home.social.

  1. Software licensing is no longer just about generating and validating license keys.

    For modern ISVs, SaaS vendors, IoT platforms, fintech products, and AI-powered applications, licensing becomes part of the core business infrastructure: monetization, entitlement control, usage tracking, customer access, compliance, and automation.

    #NetLicensing #LicensingAsAService #SaaS #SoftwareLicensing #EntitlementManagement #ISV #SoftwareMonetization #Labs64 #AgenticAI

  2. Ever had to answer the question "What's included in Copilot Chat without the premium M365 Copilot license?"

    Yeah, it's tricky.😅 Microsoft's own materials are either out of date or too tiny to zoom into.🧐 So, I took their latst materials and created my own comparison slide.

    There's of course a lot more to #Microsoft365 and #Copilot licensing than can fit into a 2D table. I wrote more about the latest #CopilotChat #softwarelicensing changes in The Licensing Guide blog:
    licensing.guide/the-ever-movin

  3. 🤔 Oh, look! #Liquibase has decided that "open source" means "closed source with a twist" now. 🎩🐇 Bravo for the open-source magic trick where the license isn't what it seems, but hey, who needs #transparency when you have marketing! 🎉📜
    github.com/liquibase/liquibase #openSource #illusion #marketing #controversy #softwareLicensing #HackerNews #ngated

  4. Does anyone know of R packages that require license keys for certain features? Curious about packages with mixed open/proprietary functionality. #RStats #SoftwareLicensing

  5. Check out the lastest article I wrote for the #Fedora Magazine:

    fedoramagazine.org/beginners-g

    Tired of messy software licensing in your #OpenSource projects?

    The #FSFE #REUSE specification solves the chaos of unclear licenses, mixed origins, and compliance headaches.

    This guide shows you how to make licensing explicit, machine-readable, and auditable, including helpful experiences from real-world introductions

    #SoftwareLicensing #FOSS #Developer #Compliance

    @fedora
    @fsfe

  6. ⚠️ Legal alert: Broadcom is issuing cease-and-desist letters to VMware perpetual-license users 🚨

    📄 Perpetual-license agreements deemed non-compliant
    🛑 Users must migrate to subscriptions or face legal action
    🔒 Broadcom cites IP infringement and support violations
    💡 Action: Audit your license status and plan your upgrade path now

    #VMware #Broadcom #Compliance #ITsecurity #SoftwareLicensing
    arstechnica.com/gadgets/2025/0

  7. CW: AI legal musings

    If someone were to create a license that matches free/libre/open source licenses out there, but stipulates that any #scraping by #GenAI bots must be pre-approved and throttled - would @fsf and @osi consider this free / open source? And if so, would FSF or @conservancy be able to enforce the terms against violators?

    Now to think about it maybe the first step is a shared blocklist of AI scrapers' IP ranges. If it ends up blocking cloud providers so be it

    #DDOS
    #SoftwareLicensing

  8. So what exactly constitutes "prominent notices stating that you modified it, and giving a relevant date" for #GPLv3 code?

    For example, I'm working on a personal project and writing licensing it under the GPLv3. If I want to take and modify a single function (or a few) from another GPLv3-licened projected, how do I state the modifications and the date? Do git commits count? What exactly do I need to do?

    #FOSS #Programming #SoftwareLicensing

  9. OpenTofu may be showing us the wrong way to fork - OpenTofu’s founders had a mission. Upset by HashiCorp licensing changes in August 2023... - infoworld.com/article/3714980/ #softwarelicensing #opensource

  10. Use strong copyleft licenses for your software, please. When you use permissive licenses like MIT or BSD (2 or 3 clause), you're essentially giving up the premise that free software should remain free.

    The fact that silicon valley tech companies avoid using software with strong copyleft licensing is an argument for, not against them.

  11. Ok #SoftwareLicensing question: we have some software to interface with an #FPGA which uses the manufacturers USB python code. We want to release our code as an open source package (its currently GPL-3, but thats just my default), but it has this license:
    opalkelly.com/about-us/frontpa

    Opal Kelly hereby grants to the Licensee a temporary, non-exclusive license to install and use Software. Licensee shall not modify, distribute, resell or otherwise transfer Software for any purpose, commercial or non-commercial. Licensee may integrate and sub-license Software for distribution but Software must only be used in conjunction with Opal Kelly devices or devices incorporating Firmware.

    That to me says two opposite things: a) we are not allowed to distribute it for any purpose, and also b) we may sub-license and distribute it if we use it with their hardware (we are)

    Is this a normal thing in #embedded world? Can we just... copy and paste it into a vendor folder and call it a day, or do we need to redesign this thing?

  12. @hack , I've been using a "license where you're not allowed to attribute the original author and must pretend that you wrote it yourself" (of a sort) on a non-software work, my personal FAQ (linuxmafia.com/~rick/faq/), for decades.

    I wanted to permit either verbatim replication with attribution, preserving my views intact, or unrestricted CC-style remixing and morphing of my personal views but with blowback towards me from third-party changes averted by the altered work being required to be asserted to be someone else's. So, the wording is:

    "Copyright (C) 1995-2023 by Rick Moen. Verbatim copying, distribution, and display of this entire article (page) are permitted in any medium, provided this notice is preserved. Alternatively, you may create derivative works of any sort for any purpose, provided your versions contain no attribution to me, and that you assert your own authorship (and not mine) in every practical medium."

    federate.social/@dmarti described this licence (when I concocted it in the '90s), as "bastard reverse copyleft", and wisely cautioned about legal uncertainties owing to its novelty. (/me nods to teh.entar.net/@spacehobo)

    #SoftwareLicensing #CreativeCommons
    #OpenSourceSoftware
    #OpenSource
    #copyfight
    #SillyGeekTricks