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
2a809d74
Commit
2a809d74
authored
1 year ago
by
Seth Schoen
Browse files
Options
Downloads
Patches
Plain Diff
Taxonomize
parent
f328f355
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
+21
-9
21 additions, 9 deletions
notes.md
with
21 additions
and
9 deletions
notes.md
+
21
−
9
View file @
2a809d74
...
...
@@ -54,21 +54,33 @@ need followup.
-
uses it's self-rolled _"Delayed Open Source Attribution License"_
-
[
license file on GH
](
https://github.com/ChildMindInstitute/mindlogger-applet-builder/blob/master/LICENSE.md
)
#
Categorization question
#
Taxonomy
I
s
there a distinction to be made between these cases
?
I
(Seth) think
there
's
a distinction to be made between these
three
cases
:
*
licenses that are not open source licenses but that state (in the license
text somewhere) that they automatically convert / automatically permit use
and redistribution subject to a specified open source license after a period
of time
*
publicly announced practices of manually relicensing old codebase snapshots
on a particular schedule, which depend on a person at the company explicitly
making a delayed open source release
*
"automatic": licenses that are not open source licenses but that state
(in the license text somewhere) that they automatically convert /
automatically permit use and redistribution subject to a specified
open source license after a period of time
*
"manual": publicly announced practices of manually relicensing old codebase
snapshots on a particular schedule, which depend on a person at the company
explicitly making a delayed open source release
(In some sense, this is a potential distinction between a "delayed open
source licensing business practice" and a "delayed open source license".)
*
"post-hoc" / "unscheduled": proprietary software that eventually was
relicensed under an open source license, without a public statement of
intent to do so at the time of its original publication, or without a
published schedule for the conversion
I would include the former two in the scope of the report but not the
latter one (except to explain how it's different). Some people have been
suggesting some of these cases (which can be fairly famous, like Netscape
Navigator!), but I think these should be thought of as more of a one-time
"change" than a "delay".
# Threads where we have posted
Look in the follow-ups in these threads (and subthreads thereof) for
...
...
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