From 02a2d2beb3a166481d951fd80ef505d991d6f597 Mon Sep 17 00:00:00 2001 From: Boris Mann Date: Tue, 15 Aug 2023 15:26:23 -0700 Subject: [PATCH] adding saturn --- .../future-of-open-source.md | 1 - _includes/head.html | 2 ++ _notes/Internet Transition.md | 2 +- _notes/Open Source Licensing.md | 27 +++++++++++++++++++ saturn-sw.js | 1 + 5 files changed, 31 insertions(+), 2 deletions(-) rename _posts/blog/2023-08-15-future-of-open-source.md => _drafts/future-of-open-source.md (99%) create mode 100644 saturn-sw.js diff --git a/_posts/blog/2023-08-15-future-of-open-source.md b/_drafts/future-of-open-source.md similarity index 99% rename from _posts/blog/2023-08-15-future-of-open-source.md rename to _drafts/future-of-open-source.md index 1503d04..2c42ee2 100644 --- a/_posts/blog/2023-08-15-future-of-open-source.md +++ b/_drafts/future-of-open-source.md @@ -1,5 +1,4 @@ --- -date: 2023-08-15T16:12:10.268-08:00 title: The Future of Open Source categories: - opensource diff --git a/_includes/head.html b/_includes/head.html index b568cbe..69ba424 100644 --- a/_includes/head.html +++ b/_includes/head.html @@ -35,6 +35,8 @@ {% if page.image %} {% endif %} + + {% if page.id == "home" %} diff --git a/_notes/Internet Transition.md b/_notes/Internet Transition.md index ef1b6b4..a50debc 100644 --- a/_notes/Internet Transition.md +++ b/_notes/Internet Transition.md @@ -3,7 +3,7 @@ title: The Internet Transition author: Robin Berjon link: https://berjon.com/internet-transition/ noteslink: https://notes.bmannconsulting.com/#/page/The%20Internet%20Transition -seed: true; +seed: true --- > To sum things up, we’re trying to run a planetary society that needs to solarpunk the fuck out of itself in a hurry on the collective intelligence of an 18th century principality that’s heard of the Enlightenment from some guy at the pub. \ No newline at end of file diff --git a/_notes/Open Source Licensing.md b/_notes/Open Source Licensing.md index 2d47223..6e286d2 100644 --- a/_notes/Open Source Licensing.md +++ b/_notes/Open Source Licensing.md @@ -63,6 +63,33 @@ I have extensive links at [[BSL]], including the version that [[Hashicorp]] uses CAL is pretty unique because it's a permissive license with a catch, that goes beyond the [[AGPL]], where the users of the software are required to be given everything that is needed to "use and modify" the software. Basically, anything you need to host the software has to be supplied. This restriction, of maintaining user autonomy, did pass the [[OSI]] approval process in February 2019. +### Cross License Collaboratives + +<https://xlcollaborative.com/> [[XLC]] + +> Maintain your projects’ licenses and create shared moneymaking opportunity without any company, foundation, or dictator. + +Labeled as [[XLC]] for short, Kyle Mitchell has [written a couple of posts about XLC back in 2019](https://writing.kemitchell.com/series/cross-license-collaboratives). + +I'm going to quote the [landing page for the XLC in full](https://xlcollaborative.com/): + +> Cross license collaboratives are co-op-like networks of contributors to online projects that can… +> +> * change the license terms for their projects democratically, without getting permission from every contributor +> * gift or sell commercial licenses and other licenses, sharing proceeds equally +> * welcome new contributors from all over the world +> …all without the overhead of a company, foundation, or other legal organization. +> +> Contributors can start a collaborative for their project by adopting a new kind of plain-language contributor license agreement. You can read the latest version online or browse other formats and versions. +> +> Unlike other contributor license agreements, the cross license collaborative agreement is _decentralized_ and _peer-to-peer_. No single contributor or organization gets any special licensing powers. Rather, every contributor licenses _every other contributor_, subject to rules about how new licensing decisions will be made. + +There is also an [XLC introduction with some illustrations](https://xlcollaborative.com/introduction). From that page is this useful paragraph about how you can combine XLC with one of the previous licenses, to share licensing revenue: + +> Cross license collaborative governance rules also require sharing of any proceeds related to licensing. If the collaborative makes its project available under a share-alike or noncommercial licensing, and then chooses to sell an exception for closed or commercial use, they must share the license fee with all contributors. + +What is not specified in this license is quite how to recognize new contributors, how to share value. aka all the hard stuff. But I _love_ this conceptually. It's "co-op like" without the overhead of creating a formal co-op organization rooted in some particular jurisdiction. "An open source peer co-op" might be a good short form, where "collaborative" is probably the right word so it doesn't trick people into thinking it is a co-op. + ## Permissive License, Fenced Community What if you permissively license software, but restrict access to scarce community resources around an open source project? diff --git a/saturn-sw.js b/saturn-sw.js new file mode 100644 index 0000000..cc2670e --- /dev/null +++ b/saturn-sw.js @@ -0,0 +1 @@ +(()=>{"use strict";const e="https://saturn.tech";"undefined"!=typeof ServiceWorkerGlobalScope?importScripts(e+"/saturn-sw-core.js"):"undefined"!=typeof SharedWorkerGlobalScope?importScripts(e+"/shared-worker.js"):"undefined"!=typeof DedicatedWorkerGlobalScope&&importScripts(e+"/dedicated-worker.js")})(); \ No newline at end of file -- 2.51.2