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

added MIT license #175

Merged
merged 4 commits into from
Aug 11, 2024
Merged

added MIT license #175

merged 4 commits into from
Aug 11, 2024

Conversation

reece
Copy link
Collaborator

@reece reece commented Jul 29, 2024

This PR:

  • adds an MIT license and CC0 deed in files LICENSE.txt and LICENSE-CC0.txt respectively
  • adds an Availability section in README.md and index.md about licensing and public domain status
  • adds a footer declaring CC0

Availability section (similar presentation in index.md on site and README.md on github):
image

And the footer:
image

@jtdendunnen @ifokkema @ahwagner

@reece reece linked an issue Jul 29, 2024 that may be closed by this pull request
@ahwagner
Copy link
Collaborator

This looks good to me. I agree we would also want something to specify that the documentation generated by our site code is available for free reuse. A CC0 public domain attestation in-text would be sufficient IMO.

Copy link
Collaborator

@ifokkema ifokkema left a comment

Choose a reason for hiding this comment

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

Yes, indeed, we need a license! Some thoughts:

  • Placing an MIT license in the repo, and thus the software that generates the site, does not license the output of this software, i.e., the HGVS-nomenclature.org website.
  • As such, the website itself also requires a license. I suggest CC-BY-4.0, and placing an icon + link on the website, either in the header somewhere or the footer. Alternatively, we could create a page (e.g., "Terms" or "Legal"), in which we explain the basics and link to the license document.

@reece
Copy link
Collaborator Author

reece commented Jul 31, 2024

I agree with both of you. I added CC0 to this PR. Please see PR notes at top for details and re-review.

@reece reece requested review from ifokkema and ahwagner July 31, 2024 03:55
docs/index.md Outdated Show resolved Hide resolved
reece and others added 2 commits August 6, 2024 14:53
Added Ivo and Alex's merged comments

Co-authored-by: Alex H. Wagner, PhD <Alex.Wagner@nationwidechildrens.org>
@reece
Copy link
Collaborator Author

reece commented Aug 6, 2024

@ifokkema and @ahwagner: I accepted your suggestions, made a minor tweak, and copied verbatim to README.md so that they were identical. Please re-review.

@reece reece requested a review from ifokkema August 6, 2024 21:59
Copy link
Collaborator

@ifokkema ifokkema left a comment

Choose a reason for hiding this comment

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

Great, that works! Looks good to me!

@marinadistefano
Copy link
Collaborator

Thanks all. I agree with this license. ClinGen has the same one and I think it makes the most sense.

@reece reece merged commit 7b7e932 into main Aug 11, 2024
1 check passed
@reece reece deleted the 174-add-license-file branch August 11, 2024 23:02
@reece reece restored the 174-add-license-file branch August 11, 2024 23:37
@reece reece deleted the 174-add-license-file branch August 11, 2024 23:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add license file
4 participants