Clarify sponsorship policy #1508
jonah
Reference in New Issue
Block a user
Delete Branch "sponsorship-edits-nov2019"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
https://github.com/privacytoolsIO/privacytools.io/pull/1451#issuecomment-553954762
@davegson I would be interested in your thoughts.
https://deploy-preview-1508--privacytools-io.netlify.com/sponsors/
Deploy preview for privacytools-io ready!
Built with commit
72cd94438fhttps://deploy-preview-1508--privacytools-io.netlify.com
I really like the clarification! Draws a clear line to rule out shady actors but still gives space for you as a team to validate each request on a case by case basis 👍👍👍
Two sentences I feel you can improve:
It's odd to single out governments here. There are many different types of malicious entities ready to spoof user data. I'd rephrase it to something more generic like: "to prevent malicious actors from..."
I think there is a logical error in here, first I do not know if you can say: "approve/deny a sponsorship" Would it not rather be that you approve/deny a sponsorship request (or inquiry) [I'm not fluent]
Also, I'd split the sentence into two so the approve/deny part is in one sentence and the reason for denying in the latter. Otherwise the misalignment seems to be both the reason for the accept & deny.
Something like:
We reserve the right to approve or deny all sponsorship inquieries from receiving the benefits detailed below. We will deny any incoming requests if we believe the organization or product is not aligned with our key values.
Make it your own 😉
So the problem is that the sponsorship tiers are published on Open Collective and nothing technically is stopping somebody like say, Facebook, from giving us $250/month or whatever. So the main point is that if you don't first email sponsors@privacytools.io and get in touch, there's no guarantee that you'll get your logo on the website or something, simply because you sent money over.
Why the moving away from variable? I am not reading further while wondering this.
@@ -17,3 +20,4 @@/LICENSE.txt @JonahAragon/.travis.yml @JonahAragon @Shifterovich @nitrohorse/CNAME @JonahAragon/nginx/ @JonahAragonI am curious on why?
@@ -46,3 +46,3 @@<p><input type="text" value="{{ site.name }} - Encryption and tools to protect against global mass surveillance - {{ site.production_url }}" class="form-control input-lg onclick-select"><input type="text" value="PrivacyTools - Encryption and tools to protect against global mass surveillance - {{ site.production_url }}" class="form-control input-lg onclick-select"><span class="help-block">For easy copy and paste. Share this text snippet.</span>Why not using the variable?
@@ -13,3 +12,4 @@<input type="search" name="q" class="form-control input-lg" id="q" placeholder="Try PrivacyTools Search, a Privacy-Respecting Search Engine" autocomplete="off" value=""><span class="input-group-btn"><button type="submit" class="btn btn-primary input-lg"><span class="hide_if_nojs"><i class="fas fa-search"></i> </span><span class="hidden active_if_nojs">start search</span></button></span>I don't understand the variable change here either.
@@ -46,3 +46,3 @@<p><input type="text" value="{{ site.name }} - Encryption and tools to protect against global mass surveillance - {{ site.production_url }}" class="form-control input-lg onclick-select"><input type="text" value="PrivacyTools - Encryption and tools to protect against global mass surveillance - {{ site.production_url }}" class="form-control input-lg onclick-select"><span class="help-block">For easy copy and paste. Share this text snippet.</span>Since I'm already on this PR. I agree the why needs to be elaborated. Your commits messages do not elaborate on that.
Wouldn't iE @abbluiz need the
{{ site.name }}variable to more easily support the Portuguese version?@JonahAragon, I like the text tweaks. 👍
@@ -46,3 +46,3 @@<p><input type="text" value="{{ site.name }} - Encryption and tools to protect against global mass surveillance - {{ site.production_url }}" class="form-control input-lg onclick-select"><input type="text" value="PrivacyTools - Encryption and tools to protect against global mass surveillance - {{ site.production_url }}" class="form-control input-lg onclick-select"><span class="help-block">For easy copy and paste. Share this text snippet.</span>It doesn’t make sense to me as we shift to in-repo translations (#1509), and it was implemented to solve a problem that doesn’t currently exist.
Ok, but
@@ -11,2 +10,3 @@PrivacyTools is an unincorporated community developing this website and a number of privacy-friendly services. The current list of public team members [can be found on GitHub](https://github.com/orgs/privacytoolsIO/people). In order to operate these services, PrivacyTools receives hosting and administration services from Aragon Ventures LLC.## How does {{ site.name }} collect data about me?## How does PrivacyTools collect data about me?I wonder if https://www.privacytools.io/about/ would be a better or at least good to mention here?
Right or deny makes no sense to me, did you perhaps mean right to?