logisim-evolution / logisim-evolution/logisim-evolution

Clarify copyright notice

Open
#1,264 10 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

D'n'D required documentation pri +1
Dominant language
Java
Stars
7.6k
Forks
1k
Avg merge
17h 46m
Merged PRs (30d)
68

Description

Since Logisim-evolution does not use a CLA to transfer external contributors' copyright to the Logisim-evolution organization, the copyright holder belongs to their respective author.

I believe using "Logisim-evolution developers" implies that it's copyrighted solely by the main developers of Logisim-evolution, or in other words, by the people working for Logisim-evolution. I suggest using one of the notices below:

  • © 2001 Logisim-evolution contributors.
  • © 2001 Logisim-evolution authors.

This clarifies that the code is copyrighted under the Logisim-evolution organization AND its respective contributors. Also, stating the date in the copyright implies "and later", and therefore the "2021" in the original copyright notice can be safely removed and as a benefit for it to be easier to maintain.

The Linux Foundation also suggests a similar format: https://www.linuxfoundation.org/blog/copyright-notices-in-open-source-software-projects/#:~:text=Instead%2C%20many%20LF,the%20named%20project.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Search the repository for the existing “Logisim-evolution developers” copyright notice and identify every occurrence. Review the proposed “contributors” or “authors” wording and the suggested removal of “2021”; done means the selected notice is updated consistently wherever it appears.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.