Feature #7176

Research how to tell existing users they can donate

Added by intrigeri 2014-05-08 19:25:09 . Updated 2017-09-12 10:42:46 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Fundraising
Target version:
Start date:
2014-05-08
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

On Feature #7146, we decided to hint new users (through the download page) about donating or contributing to Tails. However, existing satisfied users, when applying an automatic update, won’t see it… while they are possibly the (satisfied) people who are the most likely to donate. How do we reach them?

  • Notifications somewhere on the desktop
  • Message during the upgrade mechanism

Subtasks


Related issues

Related to Tails - Feature #7146: Add a more prominent "Donate" button? Resolved 2014-05-01
Related to Tails - Feature #8842: Consider integrating donation in the flowchart Rejected 2015-02-03
Related to Tails - Feature #9834: Clarify our roadmap for 2016 Rejected 2015-08-01

History

#1 Updated by intrigeri 2014-05-08 19:25:23

  • related to Feature #7146: Add a more prominent "Donate" button? added

#2 Updated by sajolida 2014-05-09 07:35:27

  • Description updated

#3 Updated by sajolida 2014-07-11 09:57:14

  • Assignee set to hyas

#4 Updated by Anonymous 2014-07-11 10:04:36

We actually talked about this at the contributor meeting in may: https://tails.boum.org/contribute/meetings/201405/#index1h1

#5 Updated by BitingBird 2014-07-19 21:14:11

A mention with a link in the upgrader seems a good idea, and in the upgrade documentation too.

#6 Updated by sajolida 2014-10-12 02:11:25

See also to ticket on the Tor tracker about making donations part of the download process:

https://trac.torproject.org/projects/tor/ticket/11569

#7 Updated by hyas 2014-10-12 13:13:13

Advertising our contribute section within the upgrader won’t work for the following reasons:
First, there is an implementation problem with that: it’s a pain to open links from the upgrader, due to the fact that it is running as a different user. People have to manually select and copy the URL, and paste it into the browser.
Second, if the upgrader downloads too fast, they might see the network connection shut down (for applying the upgrade) while they’re reading the donate page or donating.
Third, the upgrader recommends to stop all apps and this would in contradiction.

#8 Updated by hyas 2014-10-12 13:41:37

Idea to investigate: when the user creates a persistent folder, we could send a notification when the operation is finished and before the reboot.

#9 Updated by sajolida 2014-10-13 06:33:06

I would solve the second and third issue by proposing to donate before
starting the upgrade process.

In the screen
https://tails.boum.org/doc/first_steps/upgrade/upgrader.png, we could
have a button “Donate and upgrade” and another one “Upgrade for free”.
If the use chooses “Donate and upgrade” she is taken through the donate
process first, and then only through the upgrade process.

Still, we are left with the first issue. But I’m sure that we can
workaround this :)

#10 Updated by BitingBird 2015-01-24 09:26:02

  • Assignee deleted (hyas)

#11 Updated by sajolida 2015-02-03 11:01:10

  • related to Feature #8842: Consider integrating donation in the flowchart added

#12 Updated by BitingBird 2015-04-10 20:47:38

Not sure if this is still relevant… we do get quite some donations AFAIK. The message on the homepage was good for that, and seems like a better place to do so actually.

#13 Updated by sajolida 2015-04-14 16:49:14

I think it’s still relevant to bother about donations people that use Tails the most. That’s a common strategy (see Ubuntu for example) to ask for donation at installation time. Our amount of donated money is not that high compared to our annual budget, and I think that the more the better.

#14 Updated by sajolida 2015-08-01 11:46:59

  • Assignee set to mercedes508

We said this would be on our roadmap for 2016 but we did took this into account during the roadmap meeting and we have not assignees… So I’m not sure what to do and mark it temporarily as for mercedes508 according to Feature #9834.

#15 Updated by sajolida 2015-08-01 11:47:10

#16 Updated by mercedes508 2017-02-14 15:02:01

  • Status changed from Confirmed to Resolved
  • Assignee deleted (mercedes508)

I’m closing it as it’s now pretty clear on the website?

Cheers.

#17 Updated by intrigeri 2017-02-14 15:11:40

> I’m closing it as it’s now pretty clear on the website?

Yes and no. IMO the way it’s been done during the 2016 donation campaign was an OK’ish workaround to the lack of something like what’s been discussed on this ticket. I still think we could do better (e.g. outside of donation campaigns) for existing users, but I won’t insist, and likely won’t work on it much, so I don’t dare reopening this ticket myself.

#18 Updated by mercedes508 2017-02-14 15:18:51

  • Status changed from Resolved to Confirmed
  • Assignee set to sajolida

#19 Updated by sajolida 2017-09-12 10:42:46

  • Status changed from Confirmed to Resolved
  • Assignee deleted (sajolida)

Before we do more elaborate things, we should start with Feature #14559, wait for the results and then only decide on the next steps (upgrade? download?). So we have a plan and I’m closing this ticket :)