-
Notifications
You must be signed in to change notification settings - Fork 92
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
Ethical source licenses #2225
base: main
Are you sure you want to change the base?
Ethical source licenses #2225
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing link?
CuratedContent/EthicalOpenSource.md
Outdated
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing the link to the "Do No Harm License".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed. removed.
CuratedContent/EthicalOpenSource.md
Outdated
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I stand corrected and did not know this tidbit prior to reading material about licensing. Thank you. Content substantially revised making the above now no longer applicable.
This now reads more like a blog or original article. It is def. no longer a CC. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice article. Thanks!
@bartlettroscoe I added one sentence about checmicals. Please have a look. Sorry for change after review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New sentences look fine to me.
CuratedContent/EthicalOpenSource.md
Outdated
But, these restrictions are rarely if ever based on *ethical* considerations and are instead based on things like environmental or human health impacts often supported by a volume of scientific evidence. | ||
|
||
Two good examples to consider are ammonium nitrate and fuel oil. | ||
Two good example chemicals to consider are ammonium nitrate and fuel oil. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New sentences look fine.
Ok, followed @ksbeattie advice and found an article to curate from this article. Adjusted text slightly to accomodate that curation but didn't change meaning. @rinkug I think this is ready to carry forward as needed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With the new Wikipedia article as the main CC article, I think this is a legitimate CC article.
:--- | :--- | ||
Resource title | Wikipedia Article on the Organization for Ethical Source | ||
Authors | Various | ||
Website | https://en.wikipedia.org/wiki/Organization_for_Ethical_Source |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, that is a balanced article (and you might even say it is more negative that positive about the ethical software license movement).
With this Wikipedia article the main CC, I think you can classify this as a CC article.
@betterscientificsoftware/bssw-maint this is ready to publish. That said, it does currently include the |
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
@mention
the 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>.md
is run and commit (if using wikize_refs.py)*.md
file(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).*.md
file(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>.md
is run and commit (if using wikize_refs.py).@betterscientificsoftware/bssw-maint
(BSSw Maint) asking to carry out final publication steps.NOTE:
@betterscientificsoftware/bssw-maint
team (hint: type@
,b
,s
,s
,w
,-
,m
to auto-complete to@betterscientificsoftware/bssw-maint
).