Closed Bug 1075589 Opened 10 years ago Closed 9 years ago

[pl] Localize new auto-responders for Get Involved page redesign

Categories

(www.mozilla.org :: L10N, defect)

Production
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jhalperin, Assigned: stef)

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=pl

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
Blocks: 1069373
Summary: Localize new auto-responders for Get Involved page redesign → [pl] Localize new auto-responders for Get Involved page redesign
We also need subject lines for each of the autoresponders (English uses "Inquiry about Mozilla ________" for example).

Thanks so much!
Sara, Stefan, do we want this? How does it look with regards to our plans for utilizing contribute.m.o?
One more note: there are currently autoresponders for all categories, but we can also have one generic autoresponder with instructions to get in touch with the Polish community (it's also the solution easier to setup).
(In reply to Francesco Lodolo [:flod] from comment #3)
> One more note: there are currently autoresponders for all categories, but we
> can also have one generic autoresponder with instructions to get in touch
> with the Polish community (it's also the solution easier to setup).

I think we as aviary.pl localization team are only a good target for people wanting to localize stuff. Everyone else should be directed somewhere else...
I do not understand the purpose of having both „Why do you want to be a Mozilla volunteer? (Optional)” text field and autoresponders but is it possible to differentiate form target and autoresponder reply-to email address per category?
Assignee: nobody → jmazgaj
Assignee: jmazgaj → splewako
OS: Mac OS X → All
Hardware: x86 → All
Current Polish contribute page is disaster and I'm trying to figure out how the situation could be improved. New version looks nicer but…

What is the rationale behind contribute/signup/ chooser directing to e-mail form (way more complicated than the old one)? Why do we simply do not show contribute autoreplies content on the page?

Are messages from the form being directed to the one e-mail account (like in the old one) or the target could be chosen by category?
(In reply to Stefan Plewako [:stef] from comment #6)
> What is the rationale behind contribute/signup/ chooser directing to e-mail
> form (way more complicated than the old one)? Why do we simply do not show
> contribute autoreplies content on the page?

I'm not sure I understand the question. Both the new and the old contribute form send an email to a recipient, in which sense one is more complicated than the other?

With the old version (the one currently used by locales other than en-US) you could decide to not have auto-responders at all and manage things manually. One request for the new system is to have at least a generic auto-responder.

I guess the idea behind "sending an email" is to create a way to engage with people, while you wouldn't have anything like that by just showing instructions on the page.

> Are messages from the form being directed to the one e-mail account (like in
> the old one) or the target could be chosen by category?

Old form -> one recipient per locale.
New form: I think it would be possible to have different recipients, but at this point I have no idea if we'll be able, and when, to implement it.
(In reply to Francesco Lodolo [:flod] (UTC+2) from comment #7)
> (In reply to Stefan Plewako [:stef] from comment #6)
> > What is the rationale behind contribute/signup/ chooser directing to e-mail
> > form (way more complicated than the old one)? Why do we simply do not show
> > contribute autoreplies content on the page?
> 
> I'm not sure I understand the question. Both the new and the old contribute
> form send an email to a recipient, in which sense one is more complicated
> than the other?

In a sense that the new form on the page is more complicated (than the old, simple one) to fill/complete for volunteer (the one that do not exactly understands why he is expected to do that).

> I guess the idea behind "sending an email" is to create a way to engage with
> people, while you wouldn't have anything like that by just showing
> instructions on the page.

What exactly "engage with people" means and what exactly localization team is expected to do when someone will choose category outside the area of expertize of form messages receivers?
(In reply to Stefan Plewako [:stef] from comment #8)
> What exactly "engage with people" means and what exactly localization team
> is expected to do when someone will choose category outside the area of
> expertize of form messages receivers?

Talk with them if they expressed interest in an area that you work on, or send them to the right place if you don't? Note that each mail is also received by the en-US contact point, not just the localizer.
(In reply to Francesco Lodolo [:flod] (UTC+2) from comment #9)
> Talk with them if they expressed interest in an area that you work on, or
> send them to the right place if you don't?

First we ask people to give us an e-mail address without explaining exactly what for, then the simple autoreply is sent to them (with all possibly relevant information) and after that, l10n team is supposed to engage with them somehow?

Either I don't get it or we don't have resources to properly manage this (also applies to the old version).

> Note that each mail is also
> received by the en-US contact point, not just the localizer.

Assuming this also applies to the old version, how do we know if someone was not yet engaged by the other contact point?
Let's clarify one point: I don't manage what's behind the contribute page (intents included), I simply manage the l10n bits of it. That's all I can answer about.

Auto-responders are there exactly to help you manage the incoming requests. For example our community doesn't have resources to manage email communications, especially support inquiries, so we send people to the appropriate channels.
(In reply to Francesco Lodolo [:flod] (UTC+2) from comment #11)
> Let's clarify one point: I don't manage what's behind the contribute page
> (intents included), I simply manage the l10n bits of it. That's all I can
> answer about.

Sure, I'm just trying to figure way to improve situation by asking questions. You are also not the only one receiving them and anyone may answer them or cc someone who can.

> Auto-responders are there exactly to help you manage the incoming requests.
> For example our community doesn't have resources to manage email
> communications, especially support inquiries, so we send people to the
> appropriate channels.

I don't think we even know appropriate channels, assuming they are not the same as content in "Find an opportunity" categories from the old version. I also think that we don't have resources to send those people to the appropriate channels in such setup.

On the other hand, maybe autoreplies content is enough to engage? But if so, why it is not presented on site and what is this whole email harvesting thing for?
There's no progress in porting localized pages to the new back-end system, no point in using resources to localized these autoresponders at this point.

I left only a generic_template.txt file in case you decide to localize it. No point in leaving this bug open forever though.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.