Feature #11794

Add summary of financial statement to donation page

Added by sajolida 2016-09-13 10:28:16 . Updated 2016-10-07 16:39:58 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Fundraising
Target version:
Tails_2.7
Start date:
2016-09-13
Due date:
% Done:

100%

Feature Branch:
web/11794-financial-summary-on-donate
Type of work:
Website
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Have a pie chart in a toggle. See https://supporters.eff.org/donate/button. And maybe also a link to the financial statements but quite small.

Subtasks

Related issues

Related to Tails - Feature #9854: Write a post about achievements in 2015 Resolved
Blocked by Tails - Feature #10844: Publish financial report for 2015 Resolved 2016-01-04

History

#1 Updated by sajolida 2016-09-13 10:28:30

#2 Updated by sajolida 2016-10-03 19:00:37

  • Assignee deleted (sajolida)
  • QA Check set to Ready for QA
  • Feature Branch set to web/11794-financial-summary-on-donate

#3 Updated by sajolida 2016-10-03 19:18:28

  • Target version set to Tails_2.7

#4 Updated by sajolida 2016-10-03 20:19:57

  • Status changed from Confirmed to In Progress

Applied in changeset commit:6c1769ed12d6e9068e0c8885d2aa0875613e5ca9.

#5 Updated by intrigeri 2016-10-04 07:03:22

  • Assignee set to intrigeri

(Same as Feature #9854 and friends, will try to do that today.)

#6 Updated by intrigeri 2016-10-04 08:09:01

  • Assignee changed from intrigeri to sajolida
  • % Done changed from 0 to 50
  • QA Check changed from Ready for QA to Dev Needed

Very nice!

  • I have a problem with stuffing all kinds of things into “Infrastructure, work”. I’m assuming that it includes tests writing and maintenance. That makes it appear very big, which feels surprising (and even concerning) without any more background info, and is actually a little bit misleading IMO. I’d like to avoid any unjustified “OMG they’re crazy” effect here. Let me illustrate: setting up and maintaining services, including the Jenkins CI infra, is definitely infrastructure work; but writing and maintaining automated tests is not infrastructure work IMO, it’s rather an integral part of any good software development process. That’s why we decided to now include the tests writing in the budget for each paid feature/change in the future. I’m not sure how to convey all this into the pie chart, but I would be happy to think about it and propose something if you tell me 1. how much of “Infrastructure, work” is tests writing and maintenance; 2. if any of that work is about tests for “New features” (that should be accounted for in “New features” IMO).
  • Before I noticed that problem, I was considering to merge directly without blocking on Feature #10844. Given we don’t link to our detailed finances reports, maybe it’s not blocked by Feature #10844? Or maybe it’s really blocked but that’s because we should turn the pie chart into a link to the finances reports page? I think I would prefer that last option, but whatever.
  • Does “Releases” include all the work done by RM’s before we had a foundations team? The underlying problem behind my question is that I don’t see where is the much needed maintenance work now formally covered by the foundations team, e.g. porting to Jessie or to Firefox vNN. It seems worthwhile to make this work visible, somehow: it’s a great piece of work, that’s absolutely needed, and that is hard to fund through grants, so it’s a very good reason to donate to Tails. Now, I understand that we cannot split the chart into too many pieces, so if that work is included in “Releases”, then I suggest we keep the piece as-is but rename it to something that makes the foundations work visible. What do you think?
  • s/our money/your money/, or s/our money/money/, maybe? Just forget it if you don’t like it.
  • s/use/spend/, maybe? Just forget it if you don’t like it.
  • Is the pie chart’s source available anywhere, e.g. for translators, and for the next person who’ll update or improve it?

#7 Updated by intrigeri 2016-10-04 08:24:33

  • related to Feature #9854: Write a post about achievements in 2015 added

#8 Updated by sajolida 2016-10-06 23:16:02

So here is a new version!

> * I have a problem with stuffing all kinds of things into “Infrastructure, work”. […]

I redid the stats to move the test suite coding out of “Infrastructure”
and split it in half (50% in “Releases”, 50% in “New features”) without
going into more details.

> * […] we should turn the pie chart into a link to the finances reports page?

Added a link to the full financial reports.

> * Does “Releases” include all the work done by RM’s before we had a foundations team?

I already included the migrations and foundation work in “Releases”. Now
I clarified this in the chart by using the label “Releases &
foundations” here as well.

> * s/our money/your money/, or s/our money/money/, maybe? Just forget it if you don’t like it.

That’s what I wanted to do initially but actually we are currently using
donors money in very different proportions (more “Meetings” and “Help
desk”, almost no “New features”, etc.). That’s why I switched to “our
money”.

> * s/use/spend/, maybe? Just forget it if you don’t like it.

Ok :)

> * Is the pie chart’s source available anywhere, e.g. for translators, and for the next person who’ll update or improve it?

Done in ff458e3.

And this time I sent you the spreadsheets.

#9 Updated by sajolida 2016-10-06 23:18:20

  • Assignee changed from sajolida to intrigeri
  • QA Check changed from Dev Needed to Ready for QA

#10 Updated by intrigeri 2016-10-07 16:39:58

  • Status changed from In Progress to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass

Perfect!