mirror of
https://github.com/github/dmca.git
synced 2025-06-18 17:05:41 -04:00
Process DMCA request
This commit is contained in:
parent
e41019eb19
commit
b6a6a5ab29
83
2024/10/2024-10-29-source-code.md
Normal file
83
2024/10/2024-10-29-source-code.md
Normal file
@ -0,0 +1,83 @@
|
||||
Before disabling any content in relation to this takedown notice, GitHub
|
||||
- contacted the owners of some or all of the affected repositories to give them an opportunity to [make changes](https://docs.github.com/en/github/site-policy/dmca-takedown-policy#a-how-does-this-actually-work).
|
||||
- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice).
|
||||
|
||||
To learn about when and why GitHub may process some notices this way, please visit our [README](https://github.com/github/dmca/blob/master/README.md#anatomy-of-a-takedown-notice).
|
||||
|
||||
---
|
||||
|
||||
**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
|
||||
|
||||
Yes, I am the copyright holder.
|
||||
|
||||
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
|
||||
|
||||
No
|
||||
|
||||
**Does your claim involve content on GitHub or npm.js?**
|
||||
|
||||
GitHub
|
||||
|
||||
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
|
||||
|
||||
The alleged ProStruct prediction tool that was proclaim to be developed by [private] (https://github.com/se7en69/ProStruct), is an intellectual infringement. The project entails the work with my [private] at the [private] – [private] ([private], which just concluded.
|
||||
|
||||
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed. If possible, include a URL to where it is posted online.**
|
||||
|
||||
We are currently in the final stage of our project and we published our [private] to [private] from [private] status about a week ago ([private]). The project has also be registered as an intellectual property on the [private] website with the [private] number of [private]. Although our project is meant to be an open source where the scientific community can use it and modify it but the post allegedly copy our project work which can be observed from our GitHub time stamp, compare to his own GitHub time stamp with a little adjustment without acknowledgement of our project. Our project is currently in the final phase, where we are aiming to put finishing touches to our website and GitHub, and also publish our work in a journal for wider view to the scientific community. The copyright infringement undermine the collective effort of my team and I, over the past few months working on our project. And it also undermine the effort of [private], which host the codeathon, supported by [private] to foster scientific research development. Kind Regards
|
||||
|
||||
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
|
||||
|
||||
https://github.com/se7en69/ProStruct
|
||||
|
||||
**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology">Complaints about Anti-Circumvention Technology</a> if you are unsure.**
|
||||
|
||||
No
|
||||
|
||||
**<a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">Have you searched for any forks</a> of the allegedly infringing files or repositories? Each fork is a distinct repository and must be identified separately if you believe it is infringing and wish to have it taken down.**
|
||||
|
||||
The whole project is a copyright infringement.
|
||||
|
||||
**Is the work licensed under an open source license?**
|
||||
|
||||
Yes
|
||||
|
||||
**Which license?**
|
||||
|
||||
MIT license (https://github.com/omicscodeathon/prostruct?tab=MIT-1-ov-file#readme)
|
||||
|
||||
**How do you believe the license is being violated?**
|
||||
|
||||
The project did not acknowledged our project as the main source. The UI/UX of the project was changed and he then proceed to claim ownership.
|
||||
|
||||
**What changes can be made to bring the project into compliance with the license? For example, adding attribution, adding a license, making the repository private.**
|
||||
|
||||
Adding attribution to the original work develop by Prostruc team at the Omics-codeathon of ASBCB on October 2024 version.
|
||||
|
||||
**What would be the best solution for the alleged infringement?**
|
||||
|
||||
Other Change
|
||||
|
||||
**Describe the change.**
|
||||
|
||||
The repository itself should be removed or the project content acknowledged our project as the source code with the owner explicitly acknowledging he just improved the UI/UX of our project.
|
||||
|
||||
**Do you have the alleged infringer’s contact information? If so, please provide it.**
|
||||
|
||||
[private]
|
||||
|
||||
**I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law.**
|
||||
|
||||
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
|
||||
|
||||
**I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed.**
|
||||
|
||||
**I have read and understand GitHub's <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/">Guide to Submitting a DMCA Takedown Notice</a>.**
|
||||
|
||||
**So that we can get back to you, please provide either your telephone number or physical address.**
|
||||
|
||||
[private]
|
||||
|
||||
**Please type your full legal name below to sign this request.**
|
||||
|
||||
[private]
|
Loading…
Reference in New Issue
Block a user