Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
Delayed Open Source Publication -- Research
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Chad Whitacre
Delayed Open Source Publication -- Research
Commits
6cde05b2
Commit
6cde05b2
authored
1 year ago
by
Seth Schoen
Browse files
Options
Downloads
Patches
Plain Diff
Note controversy about "BUSL" vs. "BSL"
parent
c1bd5f4a
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
notes.md
+8
-0
8 additions, 0 deletions
notes.md
with
8 additions
and
0 deletions
notes.md
+
8
−
0
View file @
6cde05b2
...
...
@@ -2,6 +2,14 @@ This file contains free-form notes. Anyone working on this project,
please feel free to reformat this (including to something other than
Markdown) if you want.
# An annoying nomenclature problem
Even though we seem to think that the Business Source License should be
called BUSL, most of its end-users seem to refer to it as BSL! It
may be awkward if we end up having a ton of citations where we say
things like "the project FooWare announced it was using BUSL in 2022
(see 'Announcing FooCorp's Switch to BSL')".
# Examples
Note that some of these examples are still just pointers that will
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment