mirror of
https://github.com/github/dmca.git
synced 2025-06-19 09:25:33 -04:00
Process DMCA request
This commit is contained in:
dmca-sync-bot
parent
8dd0272e12
commit
e77d5e7ab8
118
2024/10/2024-10-29-obscreen.md
Normal file
118
2024/10/2024-10-29-obscreen.md
Normal file
@ -0,0 +1,118 @@
|
||||
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?**
|
||||
|
||||
Yes
|
||||
|
||||
**Please provide the Zendesk ticket number of your previously submitted notice. Zendesk ticket numbers are 7 digit ID numbers located in the subject line or body of your confirmation email.**
|
||||
|
||||
3055415
|
||||
|
||||
**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.**
|
||||
|
||||
I am the [private] of the software Obscreen.
|
||||
|
||||
**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.**
|
||||
|
||||
I am the [private] of the software Obscreen, initially released under the GPL v2 license. However, I later transitioned the project to a proprietary license (OBPLv1) and made the [private]. Unfortunately, the project remained public for a period before these changes were fully implemented, during which time several forks were created. https://www.obscreen.io
|
||||
|
||||
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
|
||||
|
||||
https://github.com/AdakHaddad/obscreen
|
||||
[invalid]
|
||||
[invalid]
|
||||
https://github.com/apersonintech/obscreen
|
||||
[invalid]
|
||||
https://github.com/brycemarquardt/obscreen
|
||||
https://github.com/Faithless35/obscreen
|
||||
https://github.com/GrLinkDn/obscreen
|
||||
https://github.com/nabilch900/obscreen
|
||||
https://github.com/riksilvap/obscreen
|
||||
https://github.com/ryanapp/obscreen
|
||||
[invalid]
|
||||
|
||||
**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.**
|
||||
|
||||
https://github.com/AdakHaddad/obscreen
|
||||
[invalid]
|
||||
[invalid]
|
||||
https://github.com/apersonintech/obscreen
|
||||
[invalid]
|
||||
https://github.com/brycemarquardt/obscreen
|
||||
https://github.com/Faithless35/obscreen
|
||||
https://github.com/GrLinkDn/obscreen
|
||||
https://github.com/nabilch900/obscreen
|
||||
https://github.com/riksilvap/obscreen
|
||||
https://github.com/ryanapp/obscreen
|
||||
[invalid]
|
||||
|
||||
**Is the work licensed under an open source license?**
|
||||
|
||||
Yes
|
||||
|
||||
**Which license?**
|
||||
|
||||
Gnu GPLv2
|
||||
|
||||
**How do you believe the license is being violated?**
|
||||
|
||||
Hello,
|
||||
|
||||
I am writing to request assistance with ensuring that several forks of my project, Obscreen, hosted on GitHub are fully compliant with the necessary legal and project guidelines.
|
||||
|
||||
While these forks may technically be licensed under GPL v2, I have identified a few concerns that need to be addressed to avoid confusion or non-compliance with the project's broader guidelines:
|
||||
|
||||
1. Use of the Project Name and Branding: Some forks continue to use the exact name and branding of Obscreen (https://www.obscreen.io) which may cause confusion about the relationship between the forks and the original project. Although the GPL v2 governs the code, the use of the project’s name or branding should be modified to avoid potential misunderstandings about the source or ownership of the software.
|
||||
|
||||
2. Non-Code Elements: Some forks may include non-code elements that are not covered by the GPL v2 license, such as logos, documentation, or other media specific to the original project. These elements should not be reused without proper permission or should be removed to maintain the project's intellectual property rights.
|
||||
|
||||
3.Full Compliance with GPL v2 Distribution Requirements: Although the forks are under GPL v2, it appears that some have failed to include essential files such as the full license text, proper copyright notices, or acknowledgments required by the GPL v2. These must be included to ensure full compliance with the terms of the license.
|
||||
|
||||
**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.**
|
||||
|
||||
- Rename their projects to avoid confusion with the original project.
|
||||
- Remove any non-code elements that are not licensed under GPL v2.
|
||||
- Ensure that they include all required licensing files and copyright notices.
|
||||
|
||||
**What would be the best solution for the alleged infringement?**
|
||||
|
||||
Repository can be made private
|
||||
|
||||
**Do you have the alleged infringer’s contact information? If so, please provide it.**
|
||||
|
||||
No
|
||||
|
||||
**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]
|
||||
[private] (mail preferred)
|
||||
|
||||
**Please type your full legal name below to sign this request.**
|
||||
|
||||
[private]
|
||||
Loading…
Reference in New Issue
Block a user