Feature #12514

Add benefits for partners to partners/become.mdwn

Added by Anonymous 2017-05-05 11:06:48 . Updated 2018-03-13 13:23:13 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Fundraising
Target version:
Tails_3.6
Start date:
2017-05-05
Due date:
% Done:

100%

Feature Branch:
Type of work:
Communicate
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

similar to https://www.fsf.org/patrons/benefits

What do Donors/Sponsors/Patrons receive when they donate?
Let’s keep in mind that we could give them some T-Shirts.
And explicit that they can advertise that they help Tails.

Subtasks

Related issues

Related to Tails - Feature #6972: Create a "Partners" page Resolved 2017-05-05

History

#1 Updated by Anonymous 2017-05-05 14:23:17

I do now think that Benefits should simple be listed on the “Become a partner” page which I’ve created. What do you think?

#2 Updated by intrigeri 2017-05-11 09:13:53

> What do Donors/Sponsors/Patrons receive when they donate?

I think what matters most is that they’re listed on our Partners page :)

> Let’s keep in mind that we could give them some T-Shirts.

Yes, we could make this possibility clear (and then not bother about it unless they explicitly ask us).

> And explicit that they can advertise that they help Tails.

ACK

#3 Updated by Anonymous 2017-05-31 09:39:42

We have added the partner/become page, which will act as “benefit” page.
We’ll basically need to add some information to that one.

#4 Updated by intrigeri 2017-06-02 16:19:11

  • Tracker changed from Bug to Feature
  • Category set to Fundraising

#5 Updated by Anonymous 2017-06-06 17:07:12

#6 Updated by Anonymous 2017-06-06 17:07:20

#7 Updated by Anonymous 2017-06-14 13:01:03

  • Subject changed from Consider adding a benefit page to Add benefits for partners to partners/become.mdwn

#8 Updated by Anonymous 2017-06-14 13:09:28

  • Status changed from Confirmed to In Progress
  • Assignee set to sajolida
  • % Done changed from 0 to 20
  • QA Check set to Ready for QA
  • Feature Branch set to 415f:tails/feature/12514+list_benefits

Please review.

#9 Updated by sajolida 2017-07-10 11:52:16

  • Target version set to Tails_3.1

#10 Updated by sajolida 2017-08-06 16:40:44

  • Assignee deleted (sajolida)
  • Target version deleted (Tails_3.1)
  • QA Check changed from Ready for QA to Info Needed

Should we have the exact same markdown in this section of /partners/become and in the first email? This would avoid information duplication issues and the two copies going slightly out of sync.

To remember to keep both in sync we could add a note in an HTML comment in /partners/become.

If so, then we should wait until #12522 is completely resolved and then we should copy the whole block.

#11 Updated by sajolida 2017-08-06 16:40:59

  • blocked by #12522 added

#12 Updated by Anonymous 2017-09-12 10:49:25

  • QA Check deleted (Info Needed)

Ack.

#13 Updated by Anonymous 2018-02-04 14:25:30

  • % Done changed from 20 to 40

#14 Updated by Anonymous 2018-02-04 14:27:50

  • Status changed from In Progress to Fix committed
  • Assignee set to sajolida
  • % Done changed from 40 to 100

I’ve merged this already as we agreed on the content.

#15 Updated by Anonymous 2018-02-04 14:28:07

  • QA Check set to Ready for QA
  • Feature Branch changed from 415f:tails/feature/12514+list_benefits to tails:master

#16 Updated by Anonymous 2018-02-04 15:04:31

  • Status changed from Fix committed to In Progress

Applied in changeset commit:6ad02aec1016b34d7125ccb2ccae30584be224da.

#17 Updated by sajolida 2018-03-13 13:23:13

  • Status changed from In Progress to Resolved
  • Assignee deleted (sajolida)
  • Target version set to Tails_3.6
  • QA Check deleted (Ready for QA)
  • Feature Branch deleted (tails:master)

Ack!