Infra 4000 - add Publisher Agreement
Infra 4000 - update OpenVSX FAQ
Signed-off-by: Yi Liu <yi.liu@eclipse-foundation.org>
Change-Id: I4e04ef32357b94446cdfbccdd1c6790581dcfc94
diff --git a/open-vsx-registry-faq/content/en_open-vsx-registry-faq.php b/open-vsx-registry-faq/content/en_open-vsx-registry-faq.php
index 7eade5d..7be239c 100644
--- a/open-vsx-registry-faq/content/en_open-vsx-registry-faq.php
+++ b/open-vsx-registry-faq/content/en_open-vsx-registry-faq.php
@@ -20,22 +20,24 @@
<li><a href="#faq-1">What is Open VSX Registry?</a></li>
<li><a href="#faq-2">Eclipse Foundation Management</a></li>
<li><a href="#faq-3">What do I Need to know as a Consumer of Open VSX?</a></li>
- <li><a href="#faq-4">What you Need to know if you are a Publisher to Open VSX?</a></li>
+ <li><a href="#faq-4">What do I Need to Know as a Publisher to Open VSX?</a></li>
<li><a href="#faq-5">Why do I Need to Sign a Publisher Agreement?</a></li>
<li><a href="#faq-6">How Do I Sign the Publisher Agreement?</a></li>
<li><a href="#faq-7">What Happens if I do not Sign the Publisher Agreement?</a></li>
- <li><a href="#faq-8">Licensing</a></li>
+ <li><a href="#faq-8">Do I Need to Sign the Eclipse Contributor Agreement in order to Publish Open VSX Extensions?</a></li>
+ <li><a href="#faq-9">Can I sign the Publisher Agreement on behalf of a Service Account?</a></li>
+ <li><a href="#faq-10">Licensing</a></li>
<ul class="sectlevel2">
- <li><a href="#faq-8-1">Does my Extension have to be Licensed?</a></li>
- <li><a href="#faq-8-2">How do I know what License an Extension is Published under?</a></li>
+ <li><a href="#faq-10-1">Does my Extension have to be Licensed?</a></li>
+ <li><a href="#faq-10-2">How do I know what License an Extension is Published under?</a></li>
</ul>
- <li><a href="#faq-9">How do I Publish Extensions?</a></li>
- <li><a href="#faq-10">How do I Unpublish an Extension?</a></li>
- <li><a href="#faq-11">Are Open VSX Registry Extensions Royalty Free?</a></li>
- <li><a href="#faq-12">How Much is the Open VSX Account Fee?</a></li>
- <li><a href="#faq-13">How do I Opt Out of Auto-Updates?</a></li>
- <li><a href="#faq-14">How do I get Technical Support?</a></li>
- <li><a href="#faq-15">How do I get help with the Publisher Agreement?</a></li>
+ <li><a href="#faq-11">How do I Publish Extensions?</a></li>
+ <li><a href="#faq-12">How do I Unpublish an Extension?</a></li>
+ <li><a href="#faq-13">Are Open VSX Registry Extensions Royalty Free?</a></li>
+ <li><a href="#faq-14">How Much is the Open VSX Account Fee?</a></li>
+ <li><a href="#faq-15">How do I Opt Out of Auto-Updates?</a></li>
+ <li><a href="#faq-16">How do I get Technical Support?</a></li>
+ <li><a href="#faq-17">How do I get help with the Publisher Agreement?</a></li>
</ul>
<h2 id="faq-1">What is Open VSX Registry?</h2>
@@ -51,7 +53,7 @@
<p>If you are consuming extensions in applications that use the Open VSX Registry (e.g. in Gitpod or VSCodium) there will be no usage impact. You can expect a seamless experience while we work to add more extensions, raise the visibility of extensions, and increase the number of consumers to ensure the long-term viability and vibrancy of the registry.</p>
-<h2 id="faq-4">What you Need to know if you are a Publisher to Open VSX?</h2>
+<h2 id="faq-4">What do I Need to Know as a Publisher to Open VSX?</h2>
<p>All publishers are required to:</p>
<ul>
<li>
@@ -86,33 +88,40 @@
<h2 id="faq-7">What Happens if I do not Sign the Publisher Agreement?</h2>
<p>If you choose not to sign the Eclipse Foundation Open VSX Publisher Agreement, you will not be able to publish extensions and any extensions that you have previously published will be deactivated and unavailable to consumers until after you do sign the agreement.</p>
-<h2 id="faq-8">Licensing</h2>
-<h3 id="faq-8-1">Does my Extension have to be Licensed?</h3>
+<h2 id="faq-8">Do I Need to Sign the Eclipse Contributor Agreement in order to Publish Open VSX Extensions?</h2>
+<p>No, there is no requirement to sign the <a href="https://www.eclipse.org/legal/ECA.php">Eclipse Contributor Agreement</a>. You do, however, need to sign the <a href="https://www.eclipse.org/legal/documents/eclipse-openvsx-publisher-agreement.pdf">Eclipse Foundation Open VSX Publisher Agreement</a>.</p>
+
+<h2 id="faq-9">Can I sign the Publisher Agreement on behalf of a Service Account?</h2>
+<p>Yes, the Publisher Agreement accounts for this. If you are able to sign the Publisher Agreement based on a service account and related service GitHub ID, coupled with the ability to enter into the Publisher Agreement (necessary rights to do so based on the terms of the Publisher Agreement), then you may do so.</p>
+<p>Please note if you wish to publish as an individual at a later time, you will need to create an individual account against a personal GitHub ID and sign the Publisher Agreement with that ID as an individual.</p>
+
+<h2 id="faq-10">Licensing</h2>
+<h3 id="faq-10-1">Does my Extension have to be Licensed?</h3>
<p>Yes, all extensions must be licensed. Your extension’s license should be expressed by including a license expression in the <a href="https://docs.npmjs.com/cli/v6/configuring-npm/package-json#license">package.json</a> manifest. If you attempt to publish an extension without a license, you will be given the opportunity to select the <a href="https://opensource.org/licenses/MIT">MIT</a> license as a default. If you have questions about what license is best for you, we recommend that you read about open source licenses at the <a href="https://opensource.org/licenses">Open Source Initiative</a>.</p>
-<h3 id="faq-8-2">How do I know what License an Extension is Published under?</h3>
+<h3 id="faq-10-2">How do I know what License an Extension is Published under?</h3>
<p>The applicable licenses of Open VSX Registry extensions are listed on the respective Overview page in the registry and are included in the JSON metadata of each extension.</p>
-<h2 id="faq-9">How do I Publish Extensions?</h2>
+<h2 id="faq-11">How do I Publish Extensions?</h2>
<p>The publishing process is described in the <a href="https://github.com/eclipse/openvsx/wiki/Publishing-Extensions#how-to-publish-an-extension">Open VSX Wiki</a>.</p>
-<h2 id="faq-10">How do I Unpublish an Extension?</h2>
+<h2 id="faq-12">How do I Unpublish an Extension?</h2>
<p>Please file an <a href="https://github.com/eclipse/open-vsx.org/issues">issue</a> with the project and a team member will provide this assistance.</p>
-<h2 id="faq-11">Are Open VSX Registry Extensions Royalty Free?</h2>
+<h2 id="faq-13">Are Open VSX Registry Extensions Royalty Free?</h2>
<p>The Open VSX Registry does not collect fees to publish or consume extensions. All extensions in the Open VSX Registry are made available without fee, subject to the terms of the respective licenses.</p>
-<h2 id="faq-12">How Much is the Open VSX Account Fee?</h2>
+<h2 id="faq-14">How Much is the Open VSX Account Fee?</h2>
<p>There are no fees associated with publishing or consuming content from the Open VSX Registry.</p>
-<h2 id="faq-13">How do I Opt Out of Auto-Updates?</h2>
+<h2 id="faq-15">How do I Opt Out of Auto-Updates?</h2>
<p>Auto-update is a feature of VS Code (or other applications consuming extensions). Please configure the client application accordingly if you wish to disable auto-updates of extensions. Open VSX Registry itself does not provide any auto-update facility.</p>
-<h2 id="faq-14">How do I get Technical Support?</h2>
+<h2 id="faq-16">How do I get Technical Support?</h2>
<p>The Open VSX Registry and the Eclipse Foundation cannot provide support for extensions that you have installed from the registry. The individual publishers are responsible for providing support for their own offerings. </p>
<p>Users can ask questions, search for answers, enter issues and feature requests for the Open VSX Registry itself in the project’s GitHub <a href="https://github.com/eclipse/open-vsx.org/issues">repository</a>. </p>
-<h2 id="faq-15">How do I get help with the Publisher Agreement?</h2>
+<h2 id="faq-17">How do I get help with the Publisher Agreement?</h2>
<p>Questions related to the Eclipse Foundation Open VSX Publisher Agreement, licenses, privacy, etc. should be sent to <a href="mailto:license@eclipse.org">license@eclipse.org</a>.</p>
</div>
