How to get past improvised model licensing
Revisiting the Open Source Business Model
In the past few years, many companies have come to me asking for help drafting a “new open source license.” As a rule, drafting a new open source software license is not a good idea, s…
Introducing the Functional Source License: Freedom without Free-riding
Sentry started life in 2008 as an unlicensed, 71-line Django plugin. The next year we began publishing it under BSD-3, and ten years later we switched to the Business Source License (BSL or BUSL). Last year we purchased Codecov, and a few months ago we published it under BSL/BUSL as well. That led to some vigorous debate because of our use of the term “Open Source” to describe Codecov, from which emerged this helpful suggestion from Adam Jacob, co-founder of Chef:
Licenses in a Subscription World
Most new startups default to a subscription model for their software. Should they consider selling licenses instead?
How to set up a new Programme | The Commons Conservancy
So you are responsible for some ‘free and open’ project or effort that is in the public interest. This could be free software/open source, open hardware, open science, open content, etcetera. With open, we mean that you are sharing not just the final end result as something immutable, but you’ve made it part of the ‘Commons’ by explicitly allowing anyone to build and extend on what you’ve created. In legal terms this is normally done through a ’license’, and each incremental author actually needs to license his or her part. However, once different people start contributing, managing who can license what becomes cumbersome - especially if you need to make upgrades to a license. Mix in the need to collectively raise funds for promotion, development and maintenance, and you’ve just experienced why people that are involved with larger projects sometimes feel victim to their own success. None of this matters when a project is young, but as soon as it is about to outgrow the original creator it becomes urgent - there is a window of opportunity for quick and effective repair which slowly starts to close once you’ve passed a certain scale, The critical fase of scale up is where we aim to help out.
Solving the Commercial Open Source Licensing Dilemma With Triple-Licensing
As you may have noticed, the move away from approved open source licenses to commercial almost-like-open-source licenses by single-vendor-owned open source projects has created a lot of bad press f…
nobody should type code by hand anymore. here's what's left.
Josh Wulf and I talked loop engineering for four episodes. The models stopped being the constraint a long time ago; what's left is vision, verification and agency. Delete your skill packs, put the whole system under test, and revisit everything that used to be hard.
en:license [CoopCycle]
This License grants rights to study, execute, modify and redistribute the Software or its derivatives to any Licensee, but reserve the commercial use of these rights to the only entities defined in Article 3. Any redistribution or online interaction with the Software or its derivative must be done accordingly to the License’s conditions.
Chapter Eight—Technology and the Law: The Automobile · University of Wisconsin Law School Digital Repository · University of Wisconsin Law School Digital Repository
University of Wisconsin Law School Law Library 975 Bascom Mall Madison, WI 53706 608-262-3394
An Anti-License Manifesto
software licenses are unavoidably a legal tool. the legal system, in the US and approximately everywhere else, is not a machine that leads to justice. therefore, software licenses do not lead to justice.
Licenses Alone Do Not Govern Behavior in Open Source
I put things here so they are on the internet
