dmca/2022/01/2022-01-31-open-inside-3.md

115 строки
6.5 KiB
Markdown
Исходник Ответственный История

Этот файл содержит неоднозначные символы Юникода!

Этот файл содержит неоднозначные символы Юникода, которые могут быть перепутаны с другими в текущей локали. Если это намеренно, можете спокойно проигнорировать это предупреждение. Используйте кнопку Экранировать, чтобы подсветить эти символы.

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 authorized to act on the copyright owner's behalf.
**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 [private] of Openinside W.L.L Co., responsible for [private] developed by the company and the [private].
**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.**
Following applications are Openinside's intellectual properties. Please find below links to ensure that Openinside is the owner of the applications and has the exclusive right to the application's source code:
Base Extension https://apps.odoo.com/apps/modules/14.0/oi_base/ (oi_base)
User Activity Audit https://apps.odoo.com/apps/modules/14.0/oi_user_audit/ (oi_user_audit)
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repositorys URL.**
The links (certain sections of the repository) provided below are infringing. For more clarifications, the links that refer to these sections are provided below:
https://github.com/blue-connect/pruebainternaPZ/tree/main/oi_base
https://github.com/blue-connect/pruebainternaPZ/tree/main/oi_user_audit
**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.**
We did not search for any existing forks for this specific repository. But according to your advice, we noticed that this repo is a fork from the repo that we already submitted a takedown request for it.
**Is the work licensed under an open source license?**
Yes
**Which license?**
Odoo Proprietary License v1.0
This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).
You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).
It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.
The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.
**How do you believe the license is being violated?**
These applications are the intellectual property of the Openiside company. These are paid apps and licensed under Odoo Proprietary License v1.0. As mentioned in the copyright law, their codes should not be exposed to public repositories.
**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.**
Our request is to remove the repository sections that contain our apps' source codes as they are intellectual properties, and Openiside has the exclusive right to the applications' source codes. The requested sections are already provided in the previous fields with links.
**What would be the best solution for the alleged infringement?**
Reported content must be removed
**Do you have the alleged infringers contact information? If so, please provide it.**
Just their GitHub account: https://github.com/blue-connect
**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]
[private]
Office: [private] | Fax: ([private]
[private]: [private] | www.open-inside.com
Physical Address: [private]
Phone: [private]
Fax: [private]
[private] , [private]
**Please type your full legal name below to sign this request.**
[private]