Each year from ~mid-October through the end of December, the Tor Project runs its year-end fundraising campaign (aka "YEC"). This is the time during which we raise the most money per year from individual donors. A key strategy in this campaign is a branded takeover of about:tor (desktop + mobile) that includes the year-end campaign "mini brand," new assets, a fundraising message, and a donate button.
I'd like to make a plan to get the about:tor year-end campaign takeover assets ready for this early October release. Ideally, the about:tor takeover would not launch with that release, but would be included in the package. The campaign launch assets would be gated until mid-October, with another gated release early/mid-November.
To put it another way:
first week of October - TB release
Monday, October 16 - gated YEC takeover of about:tor appears
Monday, November 13Wednesday, November 22, roughly - second gated YEC takeover of about:tor appears, based on FF release timing and need to push back match confirmation.
All of that being said, I'd like to understand, based on an early October release:
When should about:tor assets be ready?
When should strings be delivered to localization? (Maybe that's a question for @emmapeel?)
What else should we know, provide, or otherwise be prepared to deliver to the Apps team to make this as painless as possible ()?
@richard please let me know if I missed anything important I should include. cc @nicob
Ideally we would have all finalized assets ideally no later than the 4th of September to have everything implemented and tested on mobile and desktop for the planned September 27th release. We can be flexible about the November assets, as if need be we can implement that half in October in which case we would need those assets by October 2nd.
When should strings be delivered to localization? (Maybe that's a question for @emmapeel?)
I don't know how long it typically takes for things to get translated, but obviously sooner here is better. We can add strings without affecting the rest of the product, and the sooner we have them the sooner we can check/verify and iterate if necessary.
What else should we know, provide, or otherwise be prepared to deliver to the Apps team to make this as painless as possible ()?
I think on our side the biggest concern is the complexity of the design w/ respect to text layout. We had some issues last year with text skew which apparently Android's rendering engine doesn't support in the year of our lord 2023. We should also minimize the amount of interaction between localization and the graphic design as well (the dynamically translated protest signs from 2021 were fun to implement but probably not a good use of resources). Finally please make sure the final designs will work properly in RTL locales.
Basically @nicob please keep @dan and @henry in the loop during the design process so they can spoil everyone's fun ensure we land on something implementable.
yeah, what Richard said. some years we had more time and we could do a nice review, which is important for this kind of slogans, at least on our main locales
@emmapeel@richard we're leaning into a more text-based ask this year. Should I add more buffer time, like, would it take take longer to localize 3-5 sentences vs. one phrase?
the number of strings does not make such a difference. the thing is to
find good translators that know the project and can have a look at the
strings in time.
@richard will we be targeting 12.5 or 13.0 for this
and secondly i'm just getting to the point where I can start experimenting with loading pages in TBA, for onboarding it doesn't make sense since it needs to control things in TBA (tor, android) but for the donation page, it's just a html page and link, should be fine to try and reuse the desktop html, so hopefully well before sept I'll have a better idea on the feasibility of that
Ideally we would have all finalized assets ideally no later than the 4th of September to have everything implemented and tested on mobile and desktop for the planned September 27th release. We can be flexible about the November assets, as if need be we can implement that half in October in which case we would need those assets by October 2nd.
Got it. @nicob, can you use the Sept. 4 date to work back on delivery dates for the YEC task schedule?
@richard good to know re: assets for the November release. I hope we can have everything wrapped up by September 4. There's one piece of information that really depends on fundraising success over time, and that's the Friends of Tor match amount. If we have everything good to go by September 4, is there any wiggle room for updating one number in the text string (e.g., confirming it's $150,000 or $200,000 match) a few days after that?
Yeah we should be able to work around the precise numbering of the match.
@emmapeel@pierov should we plan on a generic sentence like 'These guys are gonna give us {} USD!' or should we just explicitly have both versions of the sentence 'they gonna give us 150k' and 'they gonna give us 200k' etc etc?
@smith checking the calendar and do want to note that we have a company-wide holiday days off from Aug 31 to Sept 4 - @richard does that change when you would need it by? Sept 5? or before the holiday?
@richard@emmapeel where should I put final text for TB & TBA such that they can be turned into strings for you and your teams to use?
--
Reply to this email directly or view it on GitLab: #41898 (comment 2935524)
You're receiving this email because you have been mentioned on gitlab.torproject.org.
Right now, Tor Browser is protecting your privacy and the privacy of millions of people like you! This is possible because of donations from our community.
If you value the privacy that Tor Browser offers yourself and others, please make a donation today. You’ll ensure Tor Browser continues to provide online privacy to everyone who needs it.
[donate button with text "Donate now" {link to donate page using appropriate rewrite rule, see this ticket}]
Gated release Nov 13
Right now, Tor Browser is protecting your privacy and the privacy of millions of people like you! This is possible because of donations from our community.
If you value the privacy that Tor Browser offers yourself and others, please make a donation today. You’ll ensure Tor Browser continues to provide online privacy to everyone who needs it.
From now until December 31, your gift will be matched one-to-one, up to {amount}!
[donate button with text "Donate now" {link to donate page using appropriate rewrite rule, see this ticket}]
Tor Browser for Android about:tor YEC text
Gated release Oct 16
Right now, Tor Browser for Android is protecting your privacy! This is possible because of donations from our community. If you value the privacy that Tor Browser for Android offers yourself and others, please make a donation today.
[donate button with text "Donate now" {link to donate page using appropriate rewrite rule, see this ticket}]
Tor Browser will always be free to use—no donation is required to use this app.
Gated release Nov 13
Right now, Tor Browser for Android is protecting your privacy! This is possible because of donations from our community. If you value the privacy that Tor Browser for Android offers yourself and others, please make a donation today.
From now until December 31, your gift will be matched one-to-one, up to {amount}!
[donate button with text "Donate now" {link to donate page using appropriate rewrite rule, see this ticket}]
Tor Browser will always be free to use—no donation is required to use this app.
I think we would still need a little UX input (@nicob@donuts) to get an idea of how these strings would be used in about:tor.
I guess the other out-standing part is that last years YEC had a new title shown in the home page, with three separate strings. Are we expecting any new title this year? I guess we can always add more strings for translators later.
Right now, Tor Browser is protecting your privacy and the privacy of millions of people like you! This is possible because of donations from our community.
Here, we would need to know whether we will want these to be within the same paragraph or not. E.g.
<p>Right now, Tor Browser is protecting your privacy and the privacy of millions of people like you!</p><p>This is possible because of donations from our community.</p>
versus
<p><spanclass="some-style-class">Right now, Tor Browser is protecting your privacy and the privacy of millions of people like you!</span> This is possible because of donations from our community.</p>
If you value the privacy that Tor Browser offers yourself and others, please make a donation today{link to donate page using appropriate rewrite rule, see this ticket}. You’ll ensure Tor Browser continues to provide online privacy to everyone who needs it.
This should be ok, but I'm not sure why we would have both this link and the donate button going to the same place.
From now until December 31, your gift will be matched 1:1, up to {amount}!
I'm not sure "1:1" is as clear as an explicit "one-to-one".
I guess the other out-standing part is that last years YEC had a new title shown in the home page, with three separate strings. Are we expecting any new title this year?
We are trying a different strategy with no anchoring 'slogan' or title this year—just the text shared above.
Here, we would need to know whether we will want these to be within the same paragraph or not.
This may depend on the design. @nicob, any feedback here?
This should be ok, but I'm not sure why we would have both this link and the donate button going to the same place.
This is relatively common fundraising tactic—offering multiple avenues to the donate page throughout the ask. But if there are usability / accessibility / experience reasons we don't want to do two links, that's fine with me.
I'm not sure "1:1" is as clear as an explicit "one-to-one".
Good point. I will edit my comment above to update this.
Here, we would need to know whether we will want these to be within the same paragraph or not.
This may depend on the design. @nicob, any feedback here?
based on the mock-ups I'm working on, I think we should keep them in the same paragraph for sake of space since this is a text heavy approach this year!
based on the mock-ups I'm working on, I think we should keep them in the same paragraph for sake of space since this is a text heavy approach this year!
This is relatively common fundraising tactic—offering multiple avenues to the donate page throughout the ask. But if there are usability / accessibility / experience reasons we don't want to do two links, that's fine with me.
One link would be neater (and probably better for those using keyboard controls/screen readers? @henry is the expert), but it's probably not the end of the world :P
and probably better for those using keyboard controls/screen readers? @henry is the expert
It is more a general usability question of having two equivalent controls right next to each other, which could be confusing. Personally, I would have assumed that the button would do something different from the link, so I wouldn't know from the text alone which was the "right" one to use.
It is more a general usability question of having two equivalent controls right next to each other, which could be confusing. Personally, I would have assumed that the button would do something different from the link, so I wouldn't know from the text alone which was the "right" one to use.
OK thanks for the feedback! I will edit the text in the comment above to NOT include a link in the text, only in the donate button.
Here, we would need to know whether we will want these to be within the same paragraph or not.
This may depend on the design. @nicob, any feedback here?
based on the mock-ups I'm working on, I think we should keep them in the same paragraph for sake of space since this is a text heavy approach this year!
@henry I'm working on posting the mockups in a ticket specific to the about:tor takeover on desktop so you can see what I'm talking about, but just a heads up that this format has since changed, and these are now in two different paragraphs - the first sentence acting more like a headline now. @emmapeel tagging you here in case this is important for l10n too
@alsmith just a wee little reminder that we still need the final {amount} value here for the November 23rd gate. It would be better to have it now for our release next week but we can also merge it in November too without issue.
yes - unfortunately we're having way more trouble here than we expected
and i don't think oct 23 will be possible. what is the november merge
date we could use?
@alsmithhttps://gitlab.torproject.org/alsmith just a wee little
reminder that we still need the final {amount} value here for the
November 23rd gate. It would be /better/ to have it now for our
release next week but we can also merge it in November too without issue.
We have decided to push the Friends of Tor update to a Nov 23 gate, with numbers getting to you by Nov 15. That means we would not update any content on Nov 13. Who do I need to tell for this change, or would you like to speak to the team about it?
Firefox is expected to release on November 21, and we usually try to release on the same date or the day after, so November 22.
However, the real target for us is no later than November 16-17 (ma1 usually gets the drafts of the security backports to do for Android on Thursdays or Fridays, and we build just right after that).
What's the status on this ticket? We're past the first date in the timeline here, yet the ticket is still opened so I'm not sure we have actually settled a timeline here...
From what I understand, the about:tor changes were made already, even though the donate side of things is not actually ready...
We don't need to solve the process for this -- i opened tpo/web/team#48 (closed) to keep track of that for the future -- but I would still like to understand what our current status is, and whether we can improve on this for the next "gate".
The decision to gate the first TB release for Oct 16 has been settled for ~2 months, as you can see in the body of this ticket. Setting this timeline informed all of the related tickets (e.g., TB, TBA, and web projects). Web projects are linked below, each of which re-state the date the changes should be ready to be deployed live:
Do we have final launch date and matching $ amount? I want to get phase2 into android this week and i hear I might be doing desktop as well. Def need to get them in this week so we can keep the estimated nov 22ish
Do we have final launch date and matching $ amount? I want to get
phase2 into android this week and i hear I might be doing desktop as
well. Def need to get them in this week so we can keep the estimated
nov 22ish
Sorry, I still don't have my internet connection to be able to properly
contribute through git and gitlab
Here's the patch that would apply, with the commit message. Can one of
you git apply it and put the commit and merge request together for me?
fixup! Bug 42072: 2023 year end campaign for about:tor.
Set donation matching amount and date.
diff --git a/browser/components/abouttor/content/aboutTor.htmlb/browser/components/abouttor/content/aboutTor.htmlindex af1634b76979d..cd709861e858a 100644--- a/browser/components/abouttor/content/aboutTor.html+++ b/browser/components/abouttor/content/aboutTor.html@@ -36,11 +36,10 @@ alt="" src="chrome://browser/content/abouttor/yec-2023-image.svg" />- <!-- TODO: Set "amount" to final USD matching amount. --> <p id="yec-2023-matching" data-l10n-id="yec-2023-matched-donation"- data-l10n-args='{ "amount": 0 }'+ data-l10n-args='{ "amount": 75000 }' ></p> <h2 id="yec-2023-heading" data-l10n-id="yec-2023-introduction"></h2> <p id="yec-2023-body" data-l10n-id="yec-2023-please-donate">diff --git a/browser/components/abouttor/content/aboutTor.jsb/browser/components/abouttor/content/aboutTor.jsindex dbe7ed02b1637..a55de9b3ba920 100644--- a/browser/components/abouttor/content/aboutTor.js+++ b/browser/components/abouttor/content/aboutTor.js@@ -203,12 +203,11 @@ const YecWidget = { this.isOpen = false; });- // TODO: Uncomment once we have a final donation matching amount.- //const donateMatchStart = Date.UTC(2023, 10, 13); // November 13th- //document.body.classList.toggle(- // "yec-2023-is-donation-matching",- // now >= donateMatchStart- //);+ const donateMatchStart = Date.UTC(2023, 10, 22); // November 22nd+ document.body.classList.toggle(+ "yec-2023-is-donation-matching",+ now >= donateMatchStart+ ); this._updateDonateLocale(); },
Also, @dan, I recommended the android string
yec_2023_matched_donation, but unlike Fluent the donation amount is
meant to be pre-formatted as a string: (new Intl.NumberFormat(stringLocale)).format(75000), where stringLocale
should match the locale the message is shown in (either the app locale,
or en-US if yec_2023_matched_donation doesn't have a translation in
that locale).
Thanks @alsmith the UX was gated on the new year, so it shouldn't be displaying for anyone anymore. We'll revert the YEC patches in the next stable release.
Thanks @alsmithhttps://gitlab.torproject.org/alsmith the UX was
gated on the new year, so it shouldn't be displaying for anyone
anymore. We'll revert the YEC patches in the next stable release.