Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
Delayed Open Source Publication -- Report
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
ots
Delayed Open Source Publication -- Report
Commits
d50531bd
Commit
d50531bd
authored
5 months ago
by
Karl Fogel
Browse files
Options
Downloads
Patches
Plain Diff
Further update README following publication
This continues the change that commit
1c3dd320
started.
parent
1c3dd320
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
README.md
+15
-20
15 additions, 20 deletions
README.md
with
15 additions
and
20 deletions
README.md
+
15
−
20
View file @
d50531bd
Research on
*delayed open source publication*
(DOSP): the practice of
publishing a software release under a proprietary license initially,
then later (usually in a planned fashion) publishing that release's
source code under an open source license.
While delayed open source publication has been somewhat rare, there are
some examples of it across the history of open source -- in fact, some
of the examples (e.g., Aladdin Ghostscript) predate the coining of the
term "open source". To the best of our knowledge, when software
authors have done this it has usually been in a fairly predictable
way. For example, when release N goes out under a proprietary
license, release N-1 is then (re)published under an open source
license.
This repository is a collection of research, and a resultant
[
whitepaper
](
https://opensource.org/delayed-open-source-publication
)
,
about various examples of DOSP and show how they are alike or
different. We also analyze the effects (if any) of this practice
generally on open source as a field. Our purpose is to provide
accurate historical description and objective analysis; our work here
represents no position on the desirability or undesirability of
delayed open source publication.
about
*delayed open source publication*
(DOSP): the practice of
publishing a software release under a proprietary license initially,
then later publishing that release's source code under an open source
license. (This is often, but not always, done in a predictable
fashion: e.g., when release N goes out under a proprietary license,
release N-1 is then (re)published under an open source license.)
There are examples of DOSP across the history of open source -- in
fact, some of the examples (e.g., Aladdin Ghostscript) predate the
coining of the term "open source". We looked at various instances of
DOSP and examined how they are alike or different. We also analyzed
the effects (if any) of DOSP on open source as a field. Our purpose
was to provide accurate historical description and objective analysis;
our work here represents no position on the desirability or
undesirability of delayed open source publication.
This research was supported by the
[
Open Source Initiative
(OSI)
](
https://opensource.org/
)
. The report is now completed and
...
...
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