6.3 KiB
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.
- provided information on how to submit a DMCA Counter Notice.
To learn about when and why GitHub may process some notices this way, please visit our README.
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 Co. W.L.L, 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 applications' source codes:
1- Base Extension (oi_base) https://apps.odoo.com/apps/modules/13.0/oi_base/
2- Recurring Entries (oi_recurring_entries) https://apps.odoo.com/apps/modules/13.0/oi_recurring_entries/
What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.
The links (certain sections of the repository) provided below are infringing. For more clarifications, the links that refer to these sections is provided below:
1- https://github.com/izzihector/odoo-13/tree/main/oi_base
2- https://github.com/izzihector/odoo-13/tree/main/oi_recurring_entries
Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our Complaints about Anti-Circumvention Technology if you are unsure.
No
Have you searched for any forks 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.
No, we did not search for any existing forks.
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 properties 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.
We request to remove the repository sections containing our apps' source codes as these are intellectual properties. 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 infringer’s contact information? If so, please provide it.
Only their [private]: [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 fair use 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 Guide to Submitting a DMCA Takedown Notice.
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]5 | 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]