<div><span style><font color="#222222" face="sans-serif"><span style="line-height:22px">Something like this maybe? </span></font></span><span style>Note: API calls, e.g. </span><span style>Google Libraries</span><span style>, are acceptable. </span></div>
<div><span style><font color="#222222" face="sans-serif"><a href="http://code.google.com/apis/libraries/">http://code.google.com/apis/libraries/</a></font></span></div><br><div class="gmail_quote">On Thu, Mar 8, 2012 at 2:32 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">That was attempted to be covered by:<div><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div>
<span style="line-height:22px;font-size:13px;font-family:sans-serif">Note: API calls, e.g. GoogleFonts, are acceptable.</span></div>
</blockquote><div><br></div><div>Any wordsmithing/improvement needed? The intent is NOT to prevent legitimate calls to third-party resources.</div><span class="HOEnZb"><font color="#888888"><div><br></div></font></span><div>
<span class="HOEnZb"><font color="#888888">Chip</font></span><div><div class="h5"><br><br><div class="gmail_quote">On Thu, Mar 8, 2012 at 2:30 PM, Emil Uzelac <span dir="ltr"><<a href="mailto:emil@themeid.com" target="_blank">emil@themeid.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><font color="#333333" face="arial, helvetica, sans-serif">So no more Google or MS JS libs either correct?</font></div>
<div><font color="#333333" face="arial, helvetica, sans-serif"><br></font></div><div><font color="#333333" face="arial, helvetica, sans-serif"> </font></div>
<div><br><div class="gmail_quote"><div><div>On Thu, Mar 8, 2012 at 2:17 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>
Roughed-in Privacy guidelines:<div><a href="http://codex.wordpress.org/Theme_Review#Privacy" target="_blank">http://codex.wordpress.org/Theme_Review#Privacy</a></div><div><br></div><div>These privacy guidelines are adapted from the Plugin guidelines regarding "phoning home". Please comment so we can revise/improve, as necessary.</div>
<div><br></div><div>I've renamed "Theme Settings and Data Security" as "Security and Privacy", with "Theme Settings and Data Security" and "Privacy" being sub-sections under this guideline.</div>
<div><br></div><div>Thanks,</div><div><br></div><div>Chip<div><div><br><br><div class="gmail_quote">On Thu, Mar 8, 2012 at 1:53 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div>On Thu, Mar 8, 2012 at 1:38 PM, Trent Lapinski <span dir="ltr"><<a href="mailto:trent@cyberchimps.com" target="_blank">trent@cyberchimps.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Woh.<br>
<br>
It is truly a shame you guys have already made the decision to restrict PressTrends use from WordPress.org without any discussion, or reason.<br></blockquote><div><br></div></div><div>Nothing is being restricted. You are free to use PressTrends in your WPORG repository-hosted Theme. We're merely stipulating that you have to *disclose* to end users that the Theme is using this service, and that you have to allow end users to *opt-in* to use of this service. </div>
<div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
There is absolutely nothing wrong with knowing how many people are using your themes, and what version numbers they are using. In fact, I wish WordPress.org itself provided this kind of data publicly.<br></blockquote><div>
<br></div></div><div>I refer you to <a href="http://www.gnu.org/philosophy/free-sw.html" target="_blank">Free Software philosophy</a> [<b>emphasis </b>added]:</div><div><br></div></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div class="gmail_quote"><div><span style="line-height:20px;color:rgb(53,56,42);font-size:16px;font-family:FreeSans,clean,sans-serif">The freedom to run the program means the freedom for any kind of person or organization to use it on any kind of computer system, for any kind of overall job and purpose, <b>without being required to communicate about it with the developer or any other specific entity</b>. In this freedom, <b>it is the <em style="font-style:italic">user's</em> purpose that matters, not the <em style="font-style:italic">developer's</em> purpose</b>; you as a user are free to run the program for your purposes, and if you distribute it to someone else, she is then free to run it for her purposes, but <b>you are not entitled to impose your purposes on her</b>.</span></div>
</div></blockquote><div class="gmail_quote"><div><br></div><div>Simply put: you, as a developer, do not have the right to this information without the user's informed consent. </div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
There is absolutely no private information that is garnered from PressTrends.<br></blockquote><div><br></div></div><div>From the <a href="http://presstrends.io/privacy" target="_blank">PressTrends privacy policy</a>:</div>
<div><br></div></div>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div class="gmail_quote"><div><span style="color:rgb(85,85,85);font-family:Arial,sans-serif;font-size:13px;line-height:20px">Themes containing the PressTrends tracking code track the following information only: number of posts published, number of comments, blog name, theme version, site url, and the number of plugins.</span></div>
</div></blockquote><div class="gmail_quote"><div><br></div><div>Those data, in that combination, ARE potentially personally identifiable. </div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
This isn't a privacy issue, and the metrics it does gather are extremely valuable to theme developers.<br></blockquote><div><br></div></div><div>Whether such data constitute a privacy concern is a matter for each end user to decide for him/herself. </div>
<div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
The only thing PressTrends "tracks" is theme activations of what theme version number of the theme is being activated, the average number of posts, comments, and plugins, and abandonment rates telling you if people have stopped using the theme after 30-days.<br>
<br>
I have absolutely no problem disclosing this better in our documentation, but to make it an option that has to be enabled makes the data it does gather pretty much useless.<br></blockquote><div><br></div></div><div>Useless to whom: the end user, or the developer? If the service is useful to the end user, then make the usefulness argument to end users. If the service is *not* useful to the end user, then it absolutely should not be enabled by default.</div>
<div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
It enables us to see if our users are upgrading their themes to the latest versions, and gives us insight into those who stop using our themes.<br>
<br>
Having to turn PressTrends off by default and then asking users to enable it as a theme option makes the data useless because you will only get activation numbers from people who enable the theme option which means they are already using and configuring your theme.<br>
<br>
If this is truly a requirement, this should be in the theme review guidelines.<br></blockquote><div><br></div></div><div>Certainly. I will copy the <a href="http://wordpress.org/extend/plugins/about/guidelines/" target="_blank">similar policy wording from the Plugin repository</a> (see #7: No "phoning home"), and find the appropriate place for it in the Theme guidelines. </div>
<div><br></div><div>Thanks,</div><div><br></div><div>Chip</div></div>
</blockquote></div><br></div></div></div>
<br></div></div><div>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></div></blockquote></div><br></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a 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></div></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a 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>