Skip to content
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

Open
wants to merge 10 commits into
base: main
Choose a base branch
from
Open

Conversation

markcmiller86
Copy link
Member

@markcmiller86 markcmiller86 commented Jan 14, 2025

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

  • [Author] @mention the BSSw.io editorial board member @<eb-member-id> in Description above assigned to shepherd your PR.
  • [Author] Add the <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).
  • [Author] Inspect the content in the *.md file(s) as rendered in GitHub for this PR.
  • [EB Mem] Assign this PR to the EB member <eb-member-id>.
  • [EB Mem] Assign this PR to the author of the PR <pr-author-id>.
  • [EB Mem] Add one or more Reviewers.
  • [EB Mem] Add label content: <content-type> for the type of contribution.
  • [EB Mem] Add to Project Content Development (see Content Development).
  • [EB Mem] Add meta-data to the *.md file(s) (set Publish: yes).
  • [EB Mem] Add label preview (so PR branch will be merged to 'preview' branch and watch for possible merge failures).
  • [EB Mem] Rebuild preview site and confirm new content is there, renders correctly and is returned in searches.
  • [Author] Make any final changes to the PR based on feedback.
  • [ ] [Author] Ensure wikize_refs.py -i <base>.md is run and commit (if using wikize_refs.py).
  • [EB Mem] Rebuild preview site and re-confirm content looks correct.
  • [EB Mem] Ensure at least one reviewer signs off on the final changes.
  • [EB Mem] Move the PR to "Ready to Publish" in Content Development.
  • [EB Mem] Leave comment and @mention @betterscientificsoftware/bssw-maint (BSSw Maint) asking to carry out final publication steps.
  • [BSSw Maint] Verify that all needed files are present in the PR (article, images, updates to Site/Homepage.md carousel and/or Site/Announcements/Announcements.md as appropriate).
  • [BSSw Maint] Merge PR. (Should automatically move to "Done" in Content Development.)
  • [BSSw Maint] Verify new contribution shows up on bssw.io as expected.

NOTE:

  • Checklist items prefixed with [Author] are expected to be performed by the author of the PR or can be performed by the author.
  • Checklist items prefixed with [EB Mem] must be performed by a BSSw.io Editorial Board (EB) Member.
  • Checklist items prefixed with [BSSw Maint] must be performed by someone in the @betterscientificsoftware/bssw-maint team (hint: type @, b, s, s, w, -, m to auto-complete to @betterscientificsoftware/bssw-maint).

Copy link
Member

@bartlettroscoe bartlettroscoe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing link?

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]().
Copy link
Member

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".

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed. removed.

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.
Copy link
Contributor

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).

Copy link
Member Author

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.

@markcmiller86 markcmiller86 changed the title Ethical open source licenses Ethica source licenses Jan 23, 2025
@markcmiller86 markcmiller86 changed the title Ethica source licenses Ethical source licenses Jan 23, 2025
@markcmiller86 markcmiller86 marked this pull request as ready for review January 23, 2025 16:58
@markcmiller86
Copy link
Member Author

This now reads more like a blog or original article. It is def. no longer a CC.

Copy link
Member

@bartlettroscoe bartlettroscoe left a 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!

@markcmiller86
Copy link
Member Author

@bartlettroscoe I added one sentence about checmicals. Please have a look. Sorry for change after review.

Copy link
Member

@bartlettroscoe bartlettroscoe left a 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.

Comment on lines 31 to 33
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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

New sentences look fine.

@markcmiller86
Copy link
Member Author

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.

Copy link
Member

@bartlettroscoe bartlettroscoe left a 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
Copy link
Member

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.

@markcmiller86 markcmiller86 self-assigned this Jan 23, 2025
@markcmiller86 markcmiller86 added content: curated For curated content preview Merge PR to the 'preview' branch to allow display on preview.bssw.io labels Jan 23, 2025
@markcmiller86
Copy link
Member Author

@betterscientificsoftware/bssw-maint this is ready to publish. That said, it does currently include the inclusivity metadata and I will expect anyone carrying it forward to replace that as appropriate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content: curated For curated content preview Merge PR to the 'preview' branch to allow display on preview.bssw.io
Projects
Status: Ready to publish
Development

Successfully merging this pull request may close these issues.

4 participants