home.social

#softwarelicensing — Public Fediverse posts

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

fetched live
  1. @[email protected]

    This would be nice, but there are a couple legal details that would need to get hammered out. We probably wouldn’t want the government to directly enforce copyleft licenses, because that would basically obligate the government to involve itself in any copyright dispute between two parties, potentially even if the parties didn’t want it. In the US, the judge can say that the person whose copyright was infringed gets their legal fees back, but this is not guaranteed.

    I’m no lawyer, but I suspect the main barrier to GPL enforcement is the high upfront cost and the risk of losing a whole bunch of money if you aren’t awarded legal fees or lose the case.


    #copyright #software-licensing
  2. 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

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

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

  5. 🔐 USB over IP for Software Licensing Dongles in Corporate IT

    Managing licensing dongles at scale is a persistent IT challenge—lost devices, manual handovers, and costly over-purchasing. USB over IP centralizes dongles in a secure location, enables controlled sharing, and adds redundancy to avoid downtime.

    Learn more 👉️usbmanager.net/usb-over-ip-for

    #USBoverIP #SoftwareLicensing #DongleManagement #ITOptimization #CostReduction #EnterpriseIT

  6. Managing multiple software subscriptions doesn’t have to be stressful. MERAK consolidates your tools, monitors usage, and keeps everything compliant — so you can focus on growth.
    #MERAK #ITManagement #SoftwareLicensing #CloudSolutions #BusinessGrowth

  7. 2026 is a turning point for software monetization. The license management market is set to grow as vendors move from perpetual licenses to hybrid and consumption-based models, powered by AI and cloud-native platforms.

    Read our new market report on how entitlements, real-time license intelligence, and usage-based pricing will shape the next decade of SaaS revenue 👉 netlicensing.io/blog/2026/01/0
    .
    .
    .
    #SoftwareLicensing #Monetization #MarketTrends #Report2026 #NetLicensing #MarketAnalysis #BizOps

  8. Stripe is great at payments — but it was never designed to manage software licenses.

    NetLicensing adds automated license lifecycle management, flexible models, security, and analytics on top of Stripe’s checkout.

    If you sell software with Stripe and still “manually manage licenses”, this article is a must‑read 👉 netlicensing.io/blog/2025/12/2
    .
    .
    .
    #NetLicensing #Stripe #SaaS #API #SoftwareLicensing #LicenseManagement #Payments #Monetization

  9. We at Labs64 GmbH & Labs64 NetLicensing would like to thank our customers, partners, and community for the collaboration and trust over the past year! 🙏

    A new year brings new opportunities, new challenges, and new ideas worth turning into reality.
    Wishing you a successful, healthy, and inspiring start into 2026 🎉

    netlicensing.io
    .
    .
    #NetLicensing #SoftwareLicensing #licensemanagement #monetization #SaaS #LaaS #NewYear2026 #Partnerships #Innovation

  10. 🤔 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

  11. 🤔 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

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

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

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

  15. ⚠️ 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

  16. ⚠️ 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

  17. 🚀 Privative-Friendly Source-Shared License (PFSSL) v1.0

    A unique license that fills the gap between permissive licenses (like MIT or BSD) and more protective ones (like LGPL, or AGPL), offering a middle ground that ensures non-infective usage with proprietary software, while still requiring source code availability, proper attribution, and accounting for network-based usage.

    🔗 Check it out here:
    rsm92.fr/licenses/pfssl-v1.0

    #OpenSource #PFSSL #SoftwareLicensing #DevTools #AGPL #MIT #MPL

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

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

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

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

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

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

  24. Thinking about a software license for the code of the IPA (intelligent personal assistant) framework that we are currently developing in the #w3c #voiceinteraction community group.

    The document drafts that we are publishing are using this one w3.org/copyright/software-lice

    Maybe, this is also good enough for our software?

    #programming #foss #softwarelicensing

  25. 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?