Trademark policy
All checks were successful
Build and publish Docker image / build (push) Successful in 18s
Build and publish Docker image / build (pull_request) Successful in 17s

This commit is contained in:
Fynn Godau 2025-02-18 23:56:47 +01:00
parent 597d68796d
commit 8ca5961c4a
3 changed files with 169 additions and 7 deletions

View file

@ -70,12 +70,10 @@
</section>
</div>
<div class="col-3 imp-medium col-12-medium">
<!-- Sidebar -->
<div class="col-3 col-12-medium"> <!-- Sidebar -->
<section>
<header>
<h2>Important links</h2>
<h2>Organization</h2>
</header>
<ul class="link-list">
<li><a href="./assets/documents/statute de.pdf">Statute (German)</a></li>
@ -85,9 +83,18 @@
</ul>
</section>
</div>
<section>
<header>
<h2>Policies</h2>
</header>
<ul class="link-list">
<li><a href="./policy/trademark.html">Trademark policy</a></li>
</ul>
</section>
<div class="row row-equal-column">
</div>
<div class="row row-equal-column">
<div class="col-4 col-6-medium col-12-small">
<section>

View file

@ -88,9 +88,10 @@
<p> We are currently supporting these projects: </p>
<div style="background:#cd201fff;padding:1em">
<p style="font-weight:600"><img style="vertical-align:middle" src="images/TNPlogo.svg" alt="" height=70 /> NewPipe</p>
<ul class="standard-list">
<ul style="standard-list">
<li>Hired part-time contractor</li>
<li>Communication and website infrastructure</li>
<li><a href="policy/trademark.html">Trademark</a> registration</li>
</ul>
</div>

154
policy/trademark.html Normal file
View file

@ -0,0 +1,154 @@
<!DOCTYPE HTML>
<!--
Halcyonic by HTML5 UP
html5up.net | @ajlkn
Free for personal and commercial use under the CCA 3.0 license (html5up.net/license)
-->
<html lang="en">
<head>
<title>NewPipe&nbsp;e.V.</title>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no" />
<link rel="stylesheet" href="../assets/css/main.css" />
</head>
<body class="subpage">
<div id="page-wrapper">
<!-- Header -->
<section id="header">
<div class="container">
<div class="row">
<div class="col-12">
<!-- Logo -->
<h1><a href="../index.html" id="logo">NewPipe&nbsp;e.V.</a></h1>
<!-- Nav -->
<nav id="nav">
<a href="../about.html">About</a>
<a href="../join.html">Join us</a>
<a href="../blog.html">Blog</a>
<a href="../donate.html" class="button-large">Donate</a>
</nav>
</div>
</div>
</div>
</section>
<!-- Content -->
<section id="features">
<div class="container">
<div class="row">
<div class="col-12">
<!-- Sidebar -->
<section>
<p>
<header>
<h2>Why trademark?</h2>
</header>
<p>Unfortunately, NewPipe is faced with an increasing amount of copycat clones and unofficial download sites that pretend to be official sources. Of course, in the light of redundancy and NewPipe's permissive <a href="https://github.com/TeamNewPipe/NewPipe/blob/dev/LICENSE">GPL v3 license</a>, we do not in itself have a problem with independent projects who leverage TeamNewPipe's work. That said, we continue to expect derivatives to meet their end of the GPL v3's license terms, requiring application source code to be made available under the same license terms.</p>
<p>Additionally, from now on, we expect third-party projects to clearly distinguish themselves from official NewPipe releases, for the following goals:</p>
<ul class="check-list">
<li>
<strong>Users should know what they are downloading.</strong><br>
Unofficial releases of NewPipe often contain advertisements or other unwanted contents. We want our users who search the net for "NewPipe" to find what they are looking for, and not fall for any scam websites.</li>
<li>
<strong>Downstream projects deserve a unique, strong identity.</strong><br>
While derivatives of NewPipe often use the term "NewPipe" in their own name to signalize a shared history of code, it also incorrectly implies endorsement from the NewPipe project. In the future, we expect downstream projects to distinguish themselves from our project and to develop their own brand.</li>
</ul>
<p>Hence, NewPipe e. V. has registered the term "NewPipe" as a word mark in the European Union (<a href="https://euipo.europa.eu/eSearch/#details/trademarks/019104121">https://euipo.europa.eu/eSearch/#details/trademarks/019104121</a>) and devised the following policy for using the mark. It is applicable to all uses of the mark within the European common market, including global uses that target (parts of) the European common market.</p>
<header><h2>Trademark policy</h2></header>
<em>Downloadable apps</em>
<ul>
<li>This policy applies to <strong>end-user facing applications</strong> only. Development-oriented test releases (for instance, as a convenient way of gathering feedback to a feature you developed) or application source code (for instance, because a derivative of NewPipe is using the term 'newpipe' in its internal structure) are not affected.</li>
<li>Per definition, the following distribution ways serve official versions of NewPipe. All other distributions are unofficial distributions, even if they serve the same binary package.
<ul>
<li><a href="https://newpipe.net/#download">https://newpipe.net/#download</a></li>
<li><a href="https://archive.newpipe.net/fdroid/repo/">https://archive.newpipe.net/fdroid/repo/</a></li>
<li><a href="https://f-droid.org/packages/org.schabi.newpipe/">https://f-droid.org/packages/org.schabi.newpipe/</a></li>
</ul>
</li>
<li>Non-official releases of NewPipe may be released to the public, provided they are compiled from one of the code revisions (commits) provided via <a href="https://github.com/TeamNewPipe/NewPipe/">https://github.com/TeamNewPipe/NewPipe/</a>. Supplementary material like the download website must clearly indicate
<ul>
<li>the commit number to uniquely identify the code revision used for the build,
<ul style="margin:0"><li>or alternatively, the version name, if the revision is marked as a release on <a href="https://github.com/TeamNewPipe/NewPipe/">https://github.com/TeamNewPipe/NewPipe/releases</a>,</li></ul>
</li>
<li>that the installation file was not assembled by TeamNewPipe,</li>
<li>that the release is not official and</li>
<li>that it is not compatible with official releases.</li>
</ul>
</li>
<li>Supplementary software designed to enhance functionality of official NewPipe releases may make use of the mark as a secondary component of the name, for instance, "Downloader for NewPipe", but not "NewPipe Downloader". Derivatives of official NewPipe are not considered supplementary software.</li>
<li>Other downloadable apps that are not built from one of the aforementioned code versions and are not supplementary software may not make use of the mark.</li>
<li><strong>Transition period:</strong> We grant existing NewPipe derivative projects which are <em>currently</em> already making use of the term "NewPipe" in their name additional time to rebrand until April 30th, 2025.</li>
</ul>
<em>Website representation</em>
<ul>
<li>The following websites are official NewPipe websites entitled to use the mark.
<ul>
<li><a href="https://newpipe-ev.de/">https://newpipe-ev.de/</a></li>
<li><a href="https://newpipe.net/">https://newpipe.net/</a></li>
<li><a href="https://f-droid.org/packages/org.schabi.newpipe/">https://f-droid.org/packages/org.schabi.newpipe/</a></li>
</ul>
</li>
<li>All other websites that make use of the mark are required to:
<ul>
<li>Explicitly, recognizably and clearly state that it is neither affiliated with nor endorsed by TeamNewPipe.</li>
<li>Not present themselves in a way which implies affiliation with, endorsement of or authorship by TeamNewPipe or NewPipe e. V..</li>
<li>Not endorse downloadable apps in violation of this trademark policy or of NewPipe's GPL v3 license.</li>
<li>If they contain links to downloadable apps that resemble an official NewPipe release, they must indicate the version name of the version provided. In the case of unofficial releases, they must instead include the additional information as required for the distribution of unofficial releases per above.</li>
</ul>
</li>
</ul>
<header><h2>Changes to the policy</h2></header>
<p>We reserve the right to change the trademark policy from time to time. Changes will become visible on this website.<br/>
The policy was last amended by the <a href="../posts/2025-02-08_5th_plenum.html">plenum meeting on Feburary 8, 2025</a>.</p>
<h2>Questions and Answers</h2>
<ol>
<li><em>NewPipe is no longer free software!</em><br>This is not the case; many other free software applications have chosen to register a mark for similar reasons.<br>You are still free to run, study, modify, and distribute NewPipe. However, for end-user facing distributions, we ask that you communicate to your recipients whether you self-compiled an official release, or whether you created a derivative project, by following our guidelines. We believe that this will make it clearer to your users what they are getting!</li>
<li><em>This is truly a capitalistic, corporate move!</em><br>The decision to take this step was not made in a typical corporate, top-down fashion. Rather, there was very broad consent within TeamNewPipe that registering a mark is a good idea. Also, keep in mind that NewPipe e. V. is bound towards all its members to act within the purpose of promoting digital media software.<br>You may have noticed that the phrasing on this page differs from the more relaxed tone you might know from NewPipe's blog posts we want this document to be as free from misunderstands as possible, hence a more formal tone.<br></li>
<li><em>When is an application considered end-user facing?</em><br>A build can be considered as a developer-facing test build if it is short-lived and intended for gathering early feedback, for instance, because it is part of a Pull Request on GitHub. On the other hand, an APK file uploaded to GitHub releases is to be considered end-user facing.<br></li>
<li><em>When am I using a mark?</em><br>Generally, a mark is "used" when it is put in a place where it promotes a product. In our case, the NewPipe application is a product which the mark is used to promote, because the app bears the mark as its name. We are also using the mark on our websites to promote our app, because we want our users to know which features it contains.<br>End-users who are, for instance, reviewing a product, are generally not "using" the mark in this sense.<br></li>
<li><em>When am I using a mark in the European common market?</em><br>A use of the mark happens in the European common market if it is reaches out to customers within the European common market. We understand this to be the case for websites that are reachable or apps that are downloadable from within the European common market and are localized to at least one of the languages officially spoken there.<br></li>
</ol>
<p>If you have any further questions, please contact <a href="mailto:board@newpipe-ev.de">board@newpipe-ev.de</a>.
</section>
</div>
</div>
</div>
</section>
<!-- Footer -->
<section id="footer">
<div class="container">
<div class="row aln-center">
<div class="col-12">
<a href="https://git.newpipe-ev.de/NewPipe-eV/website">Website repository</a> |
<a href="../contact.html">Contact</a> | <a href="../license.html">Licensing</a> | <a href="../privacy.html">Privacy Policy</a> | <a href="../credits.html">Credits</a> | <a href="../imprint.html">Imprint</a>
</div>
</div>
</div>
</section>
<!-- Copyright -->
<div id="copyright">
Copyright &copy; NewPipe&nbsp;e.V., all rights reserved. | Design: <a href="https://html5up.net">HTML5 UP</a>
</div>
</div>
<!-- Scripts -->
<script src="../assets/js/jquery.min.js"></script>
<script src="../assets/js/browser.min.js"></script>
<script src="../assets/js/breakpoints.min.js"></script>
<script src="../assets/js/util.js"></script>
<script src="../assets/js/main.js"></script>
</body>
</html>