Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Promote "hard to violate" to the Definition #64

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 3 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,8 +19,6 @@ you're using BUSL we will need to review your license more closely since BUSL
can have highly variable implementations.

For **licenses**, we're still working out specifics but we intend to be fairly
stringent in order to avoid license proliferation. Of course your license must
meet the [Fair Source Definition](https://fair.io/about/). It must also not put
an undue burden on the user to monitor their compliance with your license (any
compliance checks should be built into your software itself). It should also be
adopted at more than one company, at least.
stringent in order to avoid license proliferation. Uour license must meet the
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/Uour/Your/

[Fair Source Definition](https://fair.io/about/), and it should be adopted at
more than one company, at least.
Copy link
Collaborator

@ezekg ezekg Jan 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mentioned here but may be worth being lax on "adopted at more than one company" for now if we want to see a more diverse license pool outside of BUSL variations.

Probably a separate issue but figured I'd mention it.

12 changes: 10 additions & 2 deletions src/pages/about.astro
Original file line number Diff line number Diff line change
Expand Up @@ -45,9 +45,10 @@ const heroData = {
<li>is publicly available to read;</li>
<li>
allows use, modification, and redistribution with minimal restrictions
to protect the producer’s business model; and
to protect the producer’s business model;
</li>
<li>undergoes delayed Open Source publication (DOSP).</li>
<li>undergoes delayed Open Source publication (DOSP); and</li>
<li>does not put an undue burden on the user to monitor compliance.</li>
Copy link
Collaborator

@ezekg ezekg Jan 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like this uses heavy language compared to the other points. It'll need clarification anyways (which we have below), so might as well use simpler wording imo. It also reads like an anti-feature compared to the others that are more like features, or at least positives.

Maybe something simple like "is easy to comply with"? Maybe too simple?

</ol>
<div>
<p class="pb-[1.5rem]">
Expand Down Expand Up @@ -100,6 +101,13 @@ const heroData = {
Will this be meaningful in practice? Again, time will tell.
</p>

<p>
The fourth point is that Fair Source software must not put an undue
burden on the user to monitor their compliance with the license.
For the most part, compliance checks should be built into the software
itself. It should be difficult to violate the license terms.
</p>

<h3>Why Fair Source?</h3>

<p class="pb-[1.5rem]">
Expand Down