Ethical open source licenses #2225
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| At the same time, a chemical manufacturer often has little or no control over how their product is ultimately used once it is sold. | ||
| --> | ||
|
|
||
| Two ethical open-source licenses are currently available; the [Hippocratic License](https://firstdonoharm.dev/learn/) and the [Do No Harm License](). |
There was a problem hiding this comment.
Missing the link to the "Do No Harm License".
ksbeattie
reviewed
Jan 15, 2025
| This *viral* design sought to supercede proprietary interests and ensure that software remains a shared resource free to be modified and redistributed. | ||
| Legally speaking, GPL prevents commercial companies developing proprietary software from using any GPL software in their products. | ||
|
|
||
| Eventually, commercial interests subverted this design and permissive open source licenses took hold. |
There was a problem hiding this comment.
I don't believe it was just commercial interests that didn't like the GPL and it's viral aspect. I recall that many open source advocates disliked it as well. The more permissive licenses: BSD, MIT, etc. I believe might actually pre-date the GPL and as such were not reactions to the GPL (as is kind of implied here).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Draft article.
I drafted this because I had put together an IM on this topic and thought it would be easy to capture that as a CC too. Unfort, what I've drafted is a bit askew of a CC but I am not sure I have knowledge to try to develop further into a blog article.
EB Member: @rinkug
Resolves #
<issue-id><Other minimal information about the PR.>PR checklist for files displayed on bssw.io site
@mentionthe BSSw.io editorial board member@<eb-member-id>in Description above assigned to shepherd your PR.<issue-id>in the Description above for the associated GitHub Issue.[ ] [Author] Ensure.wikize_refs.py -i <base>.mdis run and commit (if using wikize_refs.py)*.mdfile(s) as rendered in GitHub for this PR.<eb-member-id>.<pr-author-id>.content: <content-type>for the type of contribution.Content Development(see Content Development).*.mdfile(s) (setPublish: yes).preview(so PR branch will be merged to 'preview' branch and watch for possible merge failures).[ ] [Author] Ensurewikize_refs.py -i <base>.mdis run and commit (if using wikize_refs.py).@betterscientificsoftware/bssw-maint(BSSw Maint) asking to carry out final publication steps.NOTE:
@betterscientificsoftware/bssw-maintteam (hint: type@,b,s,s,w,-,mto auto-complete to@betterscientificsoftware/bssw-maint).