Please review work for potential copyright infringement

[NGenetzky]

First, I want to thank you for contributing your time to this project. Next, I want to bring it to your attention that you are potentially infringing on the copyrights held by the authors of the projects whose code was copied into this project.

1. Please consider reviewing the documentation mentioned.
2. Please consider reaching out to the authors of those projects so that they can suggest the proper corrective actions to ensure this project does not violate their copyright.

Documentation:

• https://github.com/github/dmca
• https://docs.github.com/en/site-policy/content-removal-policies/dmca-takedown-policy
• https://docs.github.com/en/site-policy/content-removal-policies/guide-to-submitting-a-dmca-takedown-notice

Copyright holders:

• @alondmnt
• @cqroot (https://github.com/cqroot)
• @CalebJohn (https://github.com/CalebJohn)
• @ylc395 (https://github.com/ylc395)

[bobpaul]

It looks like all of the projects are MIT licensed. CalebJohn/joplin-inline-todo and ylc395/joplin-plugin-note-link-system are not obviously MIT licensed as they neither include a license file nor declare to github they are MIT licensed, but both declare via package.json they are MIT licensed. It would be good to get them to clarify their license, though. I've filed issues in both of those projects

Ensuring compliance with MIT is pretty simple as it's essentially "attribution required".

Check compliance with

• [ ] Outline: https://github.com/cqroot/joplin-outline
  • [x] Verify upstream license (MIT)
  • [ ] Copy of Upstream MIT License included in this project (ex: in src/outline)
• [ ] Inline Todo: https://github.com/CalebJohn/joplin-inline-todo
  • [ ] Verify license (Appears to be MIT due to upstream package.json)
  • [ ] Copy of upstream MIT license included in this project (ex: in src/inlineTodo)
• [ ] Daily Note: https://github.com/liamcain/obsidian-calendar-plugin
  • [x] Verify License (MIT)
  • [ ] Copy of Upstream MIT License included in this project (ex: in src/dailyNote)
• [ ] History Panel https://github.com/alondmnt/joplin-plugin-history-panel
  • [x] Verify License (MIT)
  • [ ] Copy of Upstream MIT License included in this project (ex: in src/history)
• [ ] Note Link System https://github.com/ylc395/joplin-plugin-note-link-system
  • [ ] Verify License (appears to be MIT due to upstream package.json)
  • [ ] Comply with license
• [ ] Writing Marker
  • [ ] Verify License, or is this an original work?
  • [ ] Comply with License
• [ ] Aggregated Search
  • [ ] Original work?
• [ ] RedCube Papers https://www.papersapp.com/
  • [ ] Verify License
  • [ ] Comply with License
• [ ] ArchiveBox https://github.com/ArchiveBox/ArchiveBox
  • [x] Verify License (MIT)
  • [ ] Copy of Upstream MIT License included in this project
• [ ] Code Mirror?
• [ ] Related Notes
  • [ ] Original work?

As an outside observer, it's not entirely clear what's copied from other projects vs what's been custom developed. Technically MIT doesn't require that's clear. To comply you can have a single attributions or license file that contains all of the upstream MIT texts. But it might be worth putting code derived from upstream projects all in a folder of their own. That might also help with keeping up with upstream changes. I think ideally you might use git submodule to include the upstream projects and wrap or subclass their code rather than copy/paste/modify, but I see that's already on your TODO list. But including their whole repo or installing their module via package.json would both make license compliance a lot easier.