Closed
Bug 1081979
Opened 10 years ago
Closed 10 years ago
[de] Localize new auto-responders for Get Involved page redesign
Categories
(www.mozilla.org :: L10N, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jhalperin, Unassigned)
References
()
Details
Localization text is here: http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/locales/en-GB/templates/mozorg/contribute-2015/ See text in dashboard: https://l10n.mozilla-community.org/webdashboard/?locale=de Project owner: Community Building Team Length of project (in number of source strings or words): ~100 per document Description of target audience: People who submit a form on localized Get Involved page Where the source project will live: http://mozilla.org/LOCALE/contribute Target locales for first iteration: same Resources available for L10n drivers and localizers (can include personnel): Project's release schedule (URL preferred): https://wiki.mozilla.org/Websites/Mozilla.org/Get_Involved_Redesign Project's target release date: October 15 for the English version Strings are done AFAIK. I need to know where it lives. I also need a subject line for each of the emails. You can drop them in the bug. Vielen dank für die Hilfe! :) Lg, Jennie
Updated•10 years ago
|
Blocks: 1069373
Summary: Localize new auto-responders for Get Involved page redesign → [de] Localize new auto-responders for Get Involved page redesign
Comment 1•10 years ago
|
||
Hi, the German autoresponses are in <http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/locales/de/templates/mozorg/contribute-2015/> and the subject line should be (as it is now) > Willkommen bei Mozilla! If that is all you need, feel free to close this bug.
Comment 2•10 years ago
|
||
Thanks Michael, I'll wait for Jennie to confirm that everything is set-up and close this one.
Comment 3•10 years ago
|
||
There has been no update to this bug for three days. I shall wait until tomorrow, then I’ll close this one. I don’t like incomplete work sitting on my to-do list.
Comment 4•10 years ago
|
||
(In reply to Michael 'Coce' Köhler from comment #3) > There has been no update to this bug for three days. I shall wait until > tomorrow, then I’ll close this one. I don’t like incomplete work sitting on > my to-do list. This bug is the only way I have to be sure that the back-end is set up and I can push the page online. If you don't want this bug to appear on your webdashboard, we can temporarily deselect "de" in the locale switcher. But really, please don't close this one until the page is online.
Comment 5•10 years ago
|
||
I notice that is has been a month since visible action was taken here and I just wanted to ask about the current status.
Comment 6•10 years ago
|
||
Pinged again this morning since another locale (rightfully) complained, waiting for an updated schedule since we're past 10th Anniversary.
Comment 7•10 years ago
|
||
Another week has passed and I’d like to ask again: what’s going on here? If there is no schedule, can’t this bug just go?
Comment 8•10 years ago
|
||
We should have an update this week. The idea is to temporarily use the old contribute form with the new pages to avoid waiting more time, so at some point we'll still need to set up autoresponders for the new back-end (this or a new bug).
Comment 9•10 years ago
|
||
In light of the update in dev.l10n.web <https://groups.google.com/forum/#!topic/mozilla.dev.l10n.web/-tQm37TQbE4> which as I understand it means that the localized responses will be delayed even longer, I’d like to ask again about what is happening to this bug. Are we simply supposed to wait, or will there be a new one?
Comment 10•10 years ago
|
||
This bug will be used to track the setup of autoresponders with the new back-end as soon as it's ready. If closed, we'll have to open a new one.
Comment 11•10 years ago
|
||
I have seen no indication of any schedule for future development of this matter. I will not carry what seems to be incomplete work to the new year, so I will now close this bug. It can be reopened if there is any relevant progress.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•