<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body smarttemplateinserted="true" bgcolor="#FFFFFF" text="#000000">
<div id="smartTemplate4-template">So, what happens now with
PageLines?<br>
It gets removed from the directory?<br>
</div>
<br>
<div class="moz-signature">
<b>Design 311</b><br>
E-mail: <i><a href="mailto:hello@design311.com">hello@design311.com</a></i><br>
Tel: <i>+32 478 91 67 89</i><br>
Website: <i><a href="http://design311.com/">http://design311.com</a></i></div>
<br>
<div id="smartTemplate4-quoteHeader"><br>
<br>
<hr><b>From:</b> Trent Lapinski <br>
<b>Sent:</b> Wednesday, October 09, 2013 10:18PM <br>
<b>To:</b> Discussion list for WordPress theme reviewers. <br>
<b>Cc:</b> <br>
<b>Subject:</b> Re: [theme-reviewers] GPL and limiting usage <br>
<br>
</div>
<blockquote
cite="mid:F1E7BF28-910E-4961-B55C-F3101DAB9983@cyberchimps.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<span style="font-family: ProximaNova, 'Helvetica Neue',
helvetica, arial, sans-serif; font-size: 16px; line-height:
21px; text-align: left; background-color: rgb(255, 255, 255); ">We
just received confirmation from the GNU (</span><a
moz-do-not-send="true"
href="http://www.gnu.org/licenses/gpl-violation.html"
style="margin: 0px; padding: 2px 0px; font-size: 16px;
vertical-align: baseline; background-color: rgb(255, 255, 255);
color: rgb(28, 92, 118); word-wrap: break-word; font-family:
ProximaNova, 'Helvetica Neue', helvetica, arial, sans-serif;
line-height: 21px; text-align: left; ">http://www.gnu.org/licenses/gpl-violation.html</a><span
style="font-family: ProximaNova, 'Helvetica Neue', helvetica,
arial, sans-serif; font-size: 16px; line-height: 21px;
text-align: left; background-color: rgb(255, 255, 255); ">) that
DMS paid features are NOT GPL compatible due to usage
limitations (</span><a moz-do-not-send="true"
href="http://www.pagelines.com/pricing/" style="margin: 0px;
padding: 2px 0px; font-size: 16px; vertical-align: baseline;
background-color: rgb(255, 255, 255); color: rgb(28, 92, 118);
word-wrap: break-word; font-family: ProximaNova, 'Helvetica
Neue', helvetica, arial, sans-serif; line-height: 21px;
text-align: left; ">http://www.pagelines.com/pricing/</a><span
style="font-family: ProximaNova, 'Helvetica Neue', helvetica,
arial, sans-serif; font-size: 16px; line-height: 21px;
text-align: left; background-color: rgb(255, 255, 255); ">).</span><br
style="font-family: ProximaNova, 'Helvetica Neue', helvetica,
arial, sans-serif; font-size: 16px; line-height: 21px;
text-align: left; background-color: rgb(255, 255, 255); ">
<br style="font-family: ProximaNova, 'Helvetica Neue', helvetica,
arial, sans-serif; font-size: 16px; line-height: 21px;
text-align: left; background-color: rgb(255, 255, 255); ">
<span style="font-family: ProximaNova, 'Helvetica Neue',
helvetica, arial, sans-serif; font-size: 16px; line-height:
21px; text-align: left; background-color: rgb(255, 255, 255); ">This
issue has continually been swept under the rug and now we have
irrefutable confirmation that there is a valid GPL issue with
PageLines usage licenses and limitations.</span><br
style="font-family: ProximaNova, 'Helvetica Neue', helvetica,
arial, sans-serif; font-size: 16px; line-height: 21px;
text-align: left; background-color: rgb(255, 255, 255); ">
<br style="font-family: ProximaNova, 'Helvetica Neue', helvetica,
arial, sans-serif; font-size: 16px; line-height: 21px;
text-align: left; background-color: rgb(255, 255, 255); ">
<span style="font-family: ProximaNova, 'Helvetica Neue',
helvetica, arial, sans-serif; font-size: 16px; line-height:
21px; text-align: left; background-color: rgb(255, 255, 255); ">This
isn't personal, this is about protecting the community and most
importantly, the users from unethical business practices. This
is our duty as a Theme Review Team and in this case, we've
failed miserably. </span><br style="font-family: ProximaNova,
'Helvetica Neue', helvetica, arial, sans-serif; font-size: 16px;
line-height: 21px; text-align: left; background-color: rgb(255,
255, 255); ">
<br style="font-family: ProximaNova, 'Helvetica Neue', helvetica,
arial, sans-serif; font-size: 16px; line-height: 21px;
text-align: left; background-color: rgb(255, 255, 255); ">
<b style="margin: 0px; padding: 0px; border: 0px; outline: 0px;
font-size: 16px; vertical-align: baseline; background-color:
rgb(255, 255, 255); font-family: ProximaNova, 'Helvetica Neue',
helvetica, arial, sans-serif; line-height: 21px; text-align:
left; ">These are the facts:<br>
</b><br style="font-family: ProximaNova, 'Helvetica Neue',
helvetica, arial, sans-serif; font-size: 16px; line-height:
21px; text-align: left; background-color: rgb(255, 255, 255); ">
<span style="font-family: ProximaNova, 'Helvetica Neue',
helvetica, arial, sans-serif; font-size: 16px; line-height:
21px; text-align: left; background-color: rgb(255, 255, 255); ">•
The GPL applies to both the copyright holder, and users.</span><br
style="font-family: ProximaNova, 'Helvetica Neue', helvetica,
arial, sans-serif; font-size: 16px; line-height: 21px;
text-align: left; background-color: rgb(255, 255, 255); ">
<span style="font-family: ProximaNova, 'Helvetica Neue',
helvetica, arial, sans-serif; font-size: 16px; line-height:
21px; text-align: left; background-color: rgb(255, 255, 255); ">•
DMS (Paid Version) violates the GPL according to the GNU (see
official clarification from the GNU below).</span>
<div style="margin: 0px; padding: 0px; border: 0px; outline: 0px;
font-size: 16px; vertical-align: baseline; background-color:
rgb(255, 255, 255); font-family: ProximaNova, 'Helvetica Neue',
helvetica, arial, sans-serif; line-height: 21px; text-align:
left; position: static; z-index: auto; ">• DMS (Paid Version)
thus violates <a moz-do-not-send="true"
href="http://WordPress.org">WordPress.org</a> Guidelines and
Policy yet DMS (Free Version) was still approved anyway despite
these concerns being raised multiple times by the community.<br>
<br>
<b style="margin: 0px; padding: 0px; border: 0px; outline: 0px;
vertical-align: baseline; background-color: transparent; ">We
can all agree on the WP guidelines:<br>
</b><br>
"Commercial versions of free Themes (i.e. “freemium” or
“up-sell” Themes) are required to be released under
GPL-compatible licenses"<br>
<br>
Source: <a moz-do-not-send="true" data-behavior="truncate"
href="http://make.wordpress.org/themes/guidelines/guidelines-license-theme-name-credit-links-up-sell-themes/"
target="_blank"
title="http://make.wordpress.org/themes/guidelines/guidelines-license-theme-name-credit-links-up-sell-themes/"
style="margin: 0px; padding: 2px 0px; vertical-align:
baseline; background-color: transparent; color: rgb(28, 92,
118); word-wrap: break-word; ">http://make.wordpress.org/themes/guidelines/guidelines-license-theme-name-c…</a><br>
<br>
<div style="margin: 0px; padding: 0px; border: 0px; outline:
0px; vertical-align: baseline; background-color: transparent;
"><b style="margin: 0px; padding: 0px; border: 0px; outline:
0px; vertical-align: baseline; background-color:
transparent; ">It has always been </b><a
moz-do-not-send="true" href="http://wordpress.org/"
style="margin: 0px; padding: 2px 0px; vertical-align:
baseline; background-color: transparent; color: rgb(28, 92,
118); word-wrap: break-word; "><b style="margin: 0px;
padding: 0px; border: 0px; outline: 0px; vertical-align:
baseline; background-color: transparent; ">WordPress.org</b></a><b
style="margin: 0px; padding: 0px; border: 0px; outline: 0px;
vertical-align: baseline; background-color: transparent; "> Policy
that themes or plugins or their pro versions that </b><b
style="margin: 0px; padding: 0px; border: 0px; outline: 0px;
vertical-align: baseline; background-color: transparent; ">are
not 100% GPL compatible are not allowed on </b><a
moz-do-not-send="true" href="http://wordpress.org/"
style="margin: 0px; padding: 2px 0px; vertical-align:
baseline; background-color: transparent; color: rgb(28, 92,
118); word-wrap: break-word; "><b style="margin: 0px;
padding: 0px; border: 0px; outline: 0px; vertical-align:
baseline; background-color: transparent; ">WordPress.org</b></a><b
style="margin: 0px; padding: 0px; border: 0px; outline: 0px;
vertical-align: baseline; background-color: transparent; ">.</b></div>
<br>
However, we have not been able to all agree on the GPL, so here
it is, irrefutably, from the GNU themselves so there's no longer
any confusion:<br>
<br>
<b style="margin: 0px; padding: 0px; border: 0px; outline: 0px;
vertical-align: baseline; background-color: transparent; ">Question:</b><br>
<br>
"1. There are 3 licensing options for how many sites you're
allowed to use the software on, 1, 6 or unlimited. It's always
been my understanding that you cannot restrict usage at all.
That once the code is in the user's hands they're free to use it
on as many websites as they need, both for personal and
commercial sites."<br>
<br>
<b style="margin: 0px; padding: 0px; border: 0px; outline: 0px;
vertical-align: baseline; background-color: transparent; ">GNU
Response:<br>
</b><br>
"That is correct, the user is free to install, copy, and share
as much as they like. Sometimes, however, companies offering
service/support will word their plans in such a way that it
appears that you are limited, when in fact, it is only that
their service/support is limited to a certain number of
installs. For example, they could offer hosted GPLed software
and the limit is actually on the number of hosted instances."<br>
<br>
<b style="margin: 0px; padding: 0px; border: 0px; outline: 0px;
vertical-align: baseline; background-color: transparent; ">Question:</b><br>
<br>
"2. There is no option to outright buy the software. You're
forced into monthly fees and if you stop payment at any time
(meaning that you're suppose to pay forever) the "pro" features
of the software are crippled. It's my understanding that a
developer cannot put such restrictions in place or force a user
to pay for the same software more than once."<br>
<br>
<b style="margin: 0px; padding: 0px; border: 0px; outline: 0px;
vertical-align: baseline; background-color: transparent; ">GNU
Response:<br>
</b><br>
"This is also correct, there cannot be any ongoing restriction
such as this. Again, however, sometimes companies can be
misleading about what is restricted. There can also be instances
where there is GPLed software involved, but also proprietary
software which they can restrict. Determining whether a
violation is occurring requires looking at the actual facts
involved in the case.<br>
<br>
With all that said, the GPL is a copyright license, and it is
the copyright holder who is empowered to enforce the terms of
the license. Sometimes companies will nominally release GPL
software, but fail to live up to its terms. As long as they are
the sole copyright holder, there is no one with the power to
force them to change their wrongful ways. There are other ways
to gain compliance, however. Even if they can't be forced by law
to follow the terms, people can still send in requests, publicly
call them out for their bad practices, or even campaign against
them for being bad community members."<br>
<br>
<b style="margin: 0px; padding: 0px; border: 0px; outline: 0px;
vertical-align: baseline; background-color: transparent; ">Conclusion: <br>
</b><br>
PageLines “service” is NOT a GPL compatible Software As A
Service business model since PageLines does not host the
customers websites. Their “service” is not just a support either
since it uses software and an API to limit usage and features to
sell variably priced non-GPL compatible usage licenses.<br>
<br>
It was argued by some admins that the GPL only applies to users,
and not the copyright holder but that is simply not true
according to the GNU. While there is no "GPL police" we do have
the choice as a community to call this out for what it is, which
is a clever marketing scheme designed to supersede the rights of
users, the GPL, and WPORG policy.
<div style="margin: 0px; padding: 0px; border: 0px; outline:
0px; vertical-align: baseline; background-color: transparent;
"><br>
</div>
<div style="margin: 0px; padding: 0px; border: 0px; outline:
0px; vertical-align: baseline; background-color: transparent;
">Are we really going to continue to reward and promote these
kind of deceptive business practices on <a
moz-do-not-send="true" href="http://WordPress.org">WordPress.org</a>?<br>
<br>
<div style="margin: 0px; padding: 0px; border: 0px; outline:
0px; vertical-align: baseline; background-color:
transparent; ">This issue requires actual action be taken
immediately as this is no longer a discussion open to
interpretation.</div>
<br>
Thank you.
<div style="margin: 0px; padding: 0px; border: 0px; outline:
0px; vertical-align: baseline; background-color:
transparent; "><br>
<div style="margin: 0px; padding: 0px; border: 0px; outline:
0px; vertical-align: baseline; background-color:
transparent; ">--Trent Lapinski<br>
=============<br>
CEO of CyberChimps Inc<br>
<a moz-do-not-send="true" data-behavior="truncate"
href="mailto:trent@cyberchimps.com" target="_blank"
style="margin: 0px; padding: 2px 0px; vertical-align:
baseline; background-color: transparent; color: rgb(28,
92, 118); word-wrap: break-word; ">trent@cyberchimps.com</a><br>
Twitter @trentlapinski<br>
<a moz-do-not-send="true" data-behavior="truncate"
href="http://cyberchimps.com/" target="_blank"
style="margin: 0px; padding: 2px 0px; vertical-align:
baseline; background-color: transparent; color: rgb(28,
92, 118); word-wrap: break-word; ">http://CyberChimps.com</a></div>
</div>
</div>
</div>
<div apple-content-edited="true">
</div>
<br>
<div>
<div>On Sep 23, 2013, at 1:21 PM, Emil Uzelac <<a
moz-do-not-send="true" href="mailto:emil@uzelac.me">emil@uzelac.me</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div dir="ltr">Thanks Bryan, we appreciate your efforts!</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Mon, Sep 23, 2013 at 10:32 AM,
Bryan Hadaway <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:bhadaway@gmail.com" target="_blank">bhadaway@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>This isn't an empty discussion, no discussion
is ever empty, knowledge is power. "Moving on"
from a discussion that has come to no reasonable
understanding whatsoever is what is less than
ideal.<br>
<br>
</div>
I've actually bumped this issue up to a WP
foundation lawyer (who I actually spoke with) and
Matt to hopefully get some sort of officially ruling
on this otherwise stalemate issue. I'll let you guys
know if I hear back.<br>
<br>
</div>
Thanks<br>
</div>
<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a moz-do-not-send="true"
href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a moz-do-not-send="true"
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br>
</blockquote>
</div>
<br>
</div>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a moz-do-not-send="true"
href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a class="moz-txt-link-freetext" href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</blockquote>
</div>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
theme-reviewers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a>
<a class="moz-txt-link-freetext" href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre>
</blockquote>
<br>
</body>
</html>