Browse Source

feat(site): update FAQ

xizhao 1 year ago
parent
commit
c8a431e919
2 changed files with 34 additions and 16 deletions
  1. 6 0
      src/css/main.css
  2. 28 16
      src/index.html

+ 6 - 0
src/css/main.css

@@ -19,6 +19,10 @@ p
   line-height: 1.5em;
 }
 
+a {
+  color: #3c6bdc;
+}
+
 section.letter
 {
   border: solid 16px rgba(247, 202, 201, .25);
@@ -69,6 +73,8 @@ section.letter h2
 section.letter h3
 {
   margin-top: 40px;
+  max-width: 500px;
+  font-size: 1.5em;
 }
 
 footer

+ 28 - 16
src/index.html

@@ -1,5 +1,5 @@
 <!DOCTYPE html>
-<html class="no-js" prefix="og: http://ogp.me/ns#" xmlns:og="http://ogp.me/ns#">
+<html class="no-js" lang="en" prefix="og: http://ogp.me/ns#" xmlns:og="http://ogp.me/ns#">
     <head>
         <meta charset="utf-8">
         <meta http-equiv="X-UA-Compatible" content="IE=edge">
@@ -42,22 +42,34 @@
 
       <h2>FAQ</h2>
       <h3>What is Commons Clause?</h3>
-      <p>The Commons Clause is a license condition drafted by <a>Heather Meeker</a> that applies a minimal-form commercial restriction on top of an existing open source license to transition the project to a source-available licensing scheme.  It was designed to a minimal and readable “textual” change to meet business and legal requirements.</p>
-      <p>This Clause is not intended to be applied against at-scale existing open source projects, but incrementally on top of commercial counterparts that need to be transitioned to source-availability to satisfy urgent business or legal requirements.</p>
+      <p>The Commons Clause is a license condition drafted by <a href="https://heathermeeker.com/about-me/">Heather Meeker</a> that applies a narrow, minimal-form commercial restriction on top of an existing open source license to transition the project to a <a href="https://en.wikipedia.org/wiki/Source-available_software" target="_blank">source-availability</a> licensing scheme.  The combined text replaces the existing license, allowing all permissions of the original license to remain except the ability to "Sell" the software as defined in the text.</p>
+      <p>This Clause is not intended to be replace licenses of existing open source projects in general, but to be used by specific projects to satisfy urgent business or legal requirements without resorting to fully "closing source".</p>
       <h3>It this “Open Source”?</h3>
-      <p>No, at least not by the official definition set forth by the <a href="https://opensource.org/osd" target="_blank">OSD</a>. Applying the Clause to an open source project will transition the project to “source-available”.</p>
-      <h3>How does this affect my project?</h3>
-      <p>When the Commons Clause is applied to a project, it only affects code moving forward -- meaning no existing users are immediately affected.  Licenses applied to previous versions cannot be revoked, the Clause will only apply to future development.</p>
-      <p>If you choose to adopt the Commons Clause, you should understand the implications any license change will have on your community and weigh that against threat towards financing of your open source project.</p>
-      <p>The Commons Clause was intended, in practice, to have virtually no effect other than force a conversation with only the most predatory of use cases against your OSS community.  The Commons Clause was not designed to restrict code sharing or development, however those that adopt the Clause should understand the broader implications of making a license change and commitments to source availability.</p>
-      <h3>Why not AGPL?</h3>
-      <p>The AGPL was drafted in a different era where Cloud ecosystem was not nearly as well-developed.  After deep legal analysis, many of the AGPL’s features were determined to be insufficient towards some of the requirements modern projects face.  </p>
-      <p>For example, much of the value for cloud-based software comes outside of the actual code (i.e. hosting) thereby nullifying many of the incentives to enforce source-availability.  In addition, many of the AGPL's features can be more restrictive towards an end user that wishes to incorporate software into a new work, which makes a source-available license with additional grants more permissive.</p>
-      <h3>What will this do for the future of Open Source projects?</h3>
-      <p>The Commons Clause is a first step at starting an important discussion about the state of modern open source businesses. </p> 
-      <p>The original Open Source Definition represents an immensely important set of ideals that carried many projects to success during the earlier days.  However, the open source ecosystem has changed a lot over the past 10 years, and the conditions of the modern landscape has forced change for the sustainability of many projects.</p>
-      <p>Open Source projects are far from free to maintain -- they require incredible amounts of work and financing to stay afloat.  While a blanket-permissive licensing scheme may have been a great fit for the early days of a project, a more sustainable model is required when maintainers are faced with the responsibility to support billion-dollar revenue pipelines that depend on their software.</p>
-      <p>The Commons Clause was drafted by a group of developers behind many of the world’s most popular open source projects who feel pressure from rapidly-developing projects and ecosystems.  Honestly, we're not entirely sure what the best long-term solution is.  However, we need to start a conversation on what we can do to meet the financial needs of commercial open source projects and the communities behind them.</p>
+      <p><i>No.</i></p>
+      <p>“Open source”, has a <a href="https://opensource.org/osd" target="_blank">specific definition</a> that was written years ago and is by the Open Source Initiative, which approves Open Source licenses.  Applying the Commons Clause to an open source project will mean the source code is available, and meets many of the elements of the Open Source Definition, such as free access to source code, freedom to modify, and freedom to re-distribute, but not all of them.  So to avoid confusion, it is best not to call Commons Clause software “open source.”</p>
+      <h3>If I change from an open source license to Commons Clause, how does this affect my project?</h3>
+      <p>When the Commons Clause is applied to a project, it only affects code moving forward -- meaning no existing users are immediately affected.  Licenses applied to previous versions are not revoked, so the Clause will only apply to future releases.</p>
+      <p>If you choose to adopt the Commons Clause, you should understand the implications any license change will have on your community and weigh that against the threat of allowing others to trade on your work developing your open source project.</p>
+      <p>The Commons Clause was intended, in practice, to have virtually no effect other than force a negotiation with those who take predatory commercial advantage of open source development.  In practice, those are some of the biggest technology businesses in the world, some of whom use open source software but don’t give back to the community.  Freedom for others to commercialize your software comes with starting an open source project, and while it's important to uphold, growth and commercial pressures will inevitably force some projects to close.  The Commons Clause provides an alternative.</p>
+      <p>The Commons Clause was not designed to restrict code sharing or development, but preserves the rights of developers to benefit from commercial use of their work.  However, those that adopt the Clause should understand the broader implications of making a license change and commitments to source availability.</p>
+      <h3>Why not just use AGPL?</h3>
+      <p>AGPL simply doesn't work to solve this problem. It is not a widely adopted license, and its “network” clause is not clearly written, so companies are not willing to stake its entire development resources on using AGPL to prevent free riding.</p>
+      <p>AGPL doesn't go far enough to preserve the rights of developers.  If cloud-based software is licensed under AGPL, often, much of the value for improvements to the cloud-based software arguably falls outside of the “Program” thereby nullifying many of the benefits of mandating enforcing source code offers.  Hosting, management, and other elements are often just as important as the core code.</p>
+      <p>In addition, the ambiguity of what is covered by AGPL’s network clause (“interacting ..remotely through a computer network”) means that many potential users are more confused and cautious about using AGPL code than a source-available license.  Like the group behind Commons Clause, the drafters of AGPL were concerned about the “cloud loophole” in licenses like GPL.  Unfortunately, AGPL’s network clause was a compromise; one camp in the GPL3 drafting process wanted to introduce a network clause into GPL3, and many more than wanted to preserve the “distribution trigger”.  So the network clause was never popular, and even after 10 years, AGPL has not been broadly accepted, particularly in business.  Most companies still won’t use AGPL code at all.  So it is not a useful open source solution for emerging companies.</p>
+      <h3>The open source community says this is a bad idea.  I love open source software.  Should I refuse to use Commons Clause software?</h3>
+      <p>Some people believe that all software must be open source, and they will never condone anything else.  But in reality, there are lots of models for licensing software.  Commons Clause is just one alternative.</p>
+      <p>But the important thing is that the developers who have chosen Commons Clause have been faced with the choice of doing something new or allowing their businesses to fail.  And the other possibility -- the completely proprietary, closed source model of companies like Oracle and Adobe -- is always a possibility.  So if anyone tries to convince you that Commons Clause is wrong because it doesn't meet all the requirements of the Open Source Definition, you should ask them if proprietary is better -- or no software at all.</p>
+      <p>You probably use plenty of software that is “freeware” -- under free of charge proprietary licenses (JRE, Acrobat).  If you refuse to use Commons Clause, you should refuse to use those, too.  Those licenses give you less rights.</p>
+      <h3>Why did you use open source licenses as the basis for Commons Clause?</h3>
+      <p>We didn’t have to, we could have just written a new, proprietary license.  But people understand the popular open source licenses, and we wanted to be clear that we were allowing everything those licenses allow, except for one kind of use.</p>
+      <p>For maintainers, this portability was a specific design constraint to support the legacy schemes they were transitioning from.</p>
+      <h3>Why not just use Creative Commons non-commercial (sharealike)?</h3>
+      <p>CC-NC is a similar idea, but CC licenses are not software licenses.  Also, there is a lot of confusion about what is a “commercial” use, and we only wanted to restrict <i><b>one narrow kind</b></i> of commercial use.</p>
+      <p>CC-NC is actually much more restrictive than Commons Clause.</p>
+      <h3>What will this do to Open Source?</h3>
+      <p>Open source is here to stay.  But open source works better for some kinds of software than others.  The Open Source Definition and the development model it represents is an immensely important set of ideals that have carried many projects to success.  But most of those projects were basic infrastructure projects, as opposed to advanced applications.  And very few true open source businesses have flourished.</p> 
+      <p>Open Source projects are not free of cost, they often support billions of dollars of revenue and can require tens of millions of dollars in financing to stay afloat.  That can work -- with a lot of effort -- for software that everyone uses, like operating systems.  Also, lots of companies are successful using open source -- when they are selling something else, like hardware or services.  But many software companies can’t keep the doors open with an open source licensing model.</p>
+      <p>The Commons Clause was drafted by a group of developers behind many of the world’s most popular open source projects who feel a lot of pain and pressure from a rapidly-developing business ecosystem and the realities of the cost of developing projects. It wasn’t created to end open source, but start a conversation on what we can do to meet the financial needs of commercial software projects and the communities behind them.</p>
       <img class="flair flair-circles" src="img/flair-circles.svg"/>
       <img class="flair flair-plus" src="img/flair-plus.svg"/>
       <img class="flair flair-zag" src="img/flair-zag.svg"/>