Closed Bug 755351 Opened 12 years ago Closed 8 years ago

[tracking][l10n] Get Involved page + video + email responses

Categories

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

Product:
www.mozilla.org
Component:
L10N
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
Future

People

(Reporter: davidwboswell, Unassigned)

References

(
URL
)

Details

(Whiteboard: u=user c=l10n p=2)

Attachments

(1 obsolete file) 

Opening tracking bug for getting the Get Involved page localized.

For background, this page hasn't been localized before since it wasn't on a site that could host localized content, but the page recently moved over to the new www.mozilla.org infrastructure that can handle localized content.

Also, there are some open questions about how to localize the page (contribution opportunities and initial points of contact will be different for different locales so we need to sort out how the page changes).  

Our thought was to do a pilot of a couple localizations (bug 743746) to sort things out and then open this up to more locales.  I'd like to avoid asking people to re-do their localizations if we decide that we need to change our approach after we see how our initial ideas are working out.

Pascal, let me know if you have suggestions about next steps and would like to talk through this.
Currently we have experimented with mere translations and we are able to handle them, if the page needs specific text and links, that's something we haven't tried yet (although in theory we can do it as well on bedrock as we did on the php site, just differently). So maybe the first step would be to know what is needed on what page for which locale, starting with a couple of locales is fine for me, but I can't really start working on that before next week (my wednesday is already full of work and Thurday and Friday, I am on PTO).
> So maybe the first step would be to know what is needed on what page for which 
> locale

Pierros and I are going to work on some mockups this week for what a localized version of the page looks like and we'll post for discussion.
> So maybe the first step would be to know what is needed on what page for which 
> locale

Pierros and I talked yesterday and for the first pass at this we want to do a straight-forward localization -- translate what's on the page and translate the responses people get when they use the form.  We'll look at doing more locale-specific content once we get the basics done.  I'll follow up in bug 743746 with more details.
OS: Mac OS X → All
Hardware: x86 → All
Translating the page only should be relatively easy, we can work on having per locale content later.
No longer depends on: 743746
(In reply to Pascal Chevrel:pascalc from comment #4)
> Translating the page only should be relatively easy, we can work on having
> per locale content later.

Great, glad to hear it will be relatively easy.  

What do we do next?  Do we export the strings from the page to Verbatim or some other l10n tool?  Would it be possible to also export the email content from Github?
The strings will be in the usual .lang files on svn, the next version of Verbatim should also support this format, but not yet.
(In reply to Pascal Chevrel:pascalc from comment #6)
> The strings will be in the usual .lang files on svn, the next version of
> Verbatim should also support this format, but not yet.

So are we able to export strings from Bedrock now or do we need to wait for the next version of Verbatim?  If we don't put the strings in Verbatim, what workflow should localizers use?

My understanding from the last mozilla.org meeting was that it was possible to export strings now.  Copying Mike, James and Steven since they'll have more information about this than I do.
The workflow is the same as usual, we export the strings to svn in .lang files, people get notified via the web dashboard and we file per locale bugs to track progress.
(In reply to Pascal Chevrel:pascalc from comment #8)
> The workflow is the same as usual, we export the strings to svn in .lang
> files, people get notified via the web dashboard and we file per locale bugs
> to track progress.

OK, great.  Is that something you can kick off?  (Sorry for the basic questions -- I'm not that familiar with the process.)
Yes, I intend to kick that off tomorrow and wednesday, I think a good first step is to start with pure translation, then we can experiment with a couple of locales for targetted content, that will be a good test to see if the requirements we we set for bedrock in that area are met ;)
Pascal, that sounds great.  I'll try to be as responsive as I can this week as you kick things off -- we're offsite at a work week though so it might take me a little while to get back to you.
Depends on: 756093
progress update, all the strings were enclosed in l10n strings and a pull request was sent to the webdev team to have that updated page merged into the dev branch so as that it can be reflected onto the staging server. Once we have that server updated, I'll update the lang file for pt-BR and hr locales for testing.
Depends on: 743746
Target Milestone: --- → Future
Hi all,

Just finished coding the email address and canned response localization. It's waiting on a pull request here: https://github.com/mozilla/bedrock/pull/126

This patch allow us to have per locale email receivers and per locale automatic responses. If there is local receiver the email is directed to the special 'all' receiver. Currently we have no local receivers and I matched the current list to the special 'all' receiver.

Note: for this code to work playdoh-lib must be updated. I already pull requested this change also: https://github.com/mozilla/playdoh-lib/pull/13
Commits pushed to dev at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/8f576b58594fd5433abf0aa272136bd4d0bbb7ae
Allow for email address and text localization. Bug 755351.

https://github.com/mozilla/bedrock/commit/177ad0a83385df6ddeccbdd567935bd88c2684d4
Merge pull request #135 from glogiotatidis/743746-localize-contribute

Allow for email address and text localization. Bug 755351.
(In reply to Giorgos Logiotatidis [:giorgos] from comment #13)
> This patch allow us to have per locale email receivers and per locale
> automatic responses. If there is local receiver the email is directed to the
> special 'all' receiver. Currently we have no local receivers and I matched
> the current list to the special 'all' receiver.

Great.

In terms of documenting local receivers, I started a list on the wiki at

https://wiki.mozilla.org/Contribute/Point_people#By_Locale

One question: how does this patch send the inquiries to the designated local point person?  If it forwards the messages, we'll also need to make sure the contribute@ mailing list is copied on all inquiries since that's where the dashboard pulls information from.  And for the 'all' receiver, I think this probably makes sense to be the contribute@ list.

In terms of having localized auto-responses, it would be great to figure out how to get the current set of auto-responses in Github into a workflow that localizers can use to localize the content.  We'll also need to add the current set of manual emails to whatever workflow we come up with.
Summary: [Tracking bug] Localize Get Involved page → [tracking][l10n] Get Involved page + video + email responses
Whiteboard: [l10n]
Depends on: 760820
Depends on: 760821
Depends on: 760823
FYI, Giorgos has documented the workflow for what happens when someone uses the form on the Get Involved page at

https://wiki.mozilla.org/Contribute/Inquiry_Workflow

There hasn't been much documentation about this in the past, so thanks to Giorgos for getting that started.

Please feel free to post feedback or questions about how we can make that more useful.  Maybe some sort of flowchart to go along with the description of the steps?  I'm not a designer, but I may be able to put something together :)
It seems OK for me. The only problem I see is that contribute at mozilla dot org is going to receive tons of emails in dozens of languages instead of just English.
(In reply to Rubén Martín [:Nukeador] from comment #17)
> It seems OK for me. The only problem I see is that contribute at mozilla dot
> org is going to receive tons of emails in dozens of languages instead of
> just English.

Yes, having everything go to a mailing list is probably not the best way to scale this to handle more locales and more people interacting.  I think it's best to use this for now though so we don't get blocked and at the same time look at what would be a better long-term solution.
For reference, the video used on the Get Involved page has already been localized into many different languages on the Universal Subtitles site at:

http://www.universalsubtitles.org/en/videos/NNxEqfuQSaPN/info/mozilla-firefox-a-different-kind-of-browser/
There have been some questions about how the workflow of the localized Get Involved pages should operate, so I've put together a basic visualization that compares the process on the EN and non-EN pages.

https://wiki.mozilla.org/Contribute/Inquiry_Workflow

This is pretty basic and probably over-simplifies things and leaves other important details out.  Nikola has offered to help document all this better, so if you have any questions about this or if there are things missing or not explained well, please feel free to send feedback.  Nikola can then make this lots better :)
fyi, we have that page in portuguese mostly done:
https://www-dev.allizom.org/b/pt-BR/contribute/

We should be able to push that to production early July, there is still some bugs to fix there.
This is fantastic news. Thank you for the update Pascal!
Pascal, that's great.  Exciting to see the pt-BR page on dev and to hear we should be able to get this going in time for FISL.  

I'm sure you're recovering from the Fennec launch work, so would you like to find time to sync up next week to figure out what is left to do?
Let's sync up next Tuesday :)
(In reply to Pascal Chevrel:pascalc from comment #24)
> Let's sync up next Tuesday :)

Great.  Would 8 AM pacific time work for you?
Pascal, great.  I just set something up for Tuesday, July 3 at 8 AM pacific.  If anyone else wants to be added to the invite, please email me directly.
(In reply to Pascal Chevrel:pascalc from comment #8)
> The workflow is the same as usual, we export the strings to svn in .lang
> files,

I don't normally do l10n work so I'll appreciate if someone can elaborate on this with a pointer to the file on http://hg.mozilla.org/ for example.
(In reply to Kang-Hao (Kenny) Lu [:kennyluck] from comment #28)
> I don't normally do l10n work so I'll appreciate if someone can elaborate on
> this with a pointer to the file on http://hg.mozilla.org/ for example.

There is some documentation about localization on Bedrock at

http://bedrock.readthedocs.org/en/latest/l10n.html

This may or may not answer all of the technical questions, but hopefully it helps.
Depends on: 769715
Depends on: 770606
David, is this bug somehow related to bug 570716?
(In reply to Fernando Pereira Silveira from comment #30)
> David, is this bug somehow related to bug 570716?

Thanks for finding that.  I'd forgotten I had filed that, but it looks like a dupe of this one now.
FYI, I just blogged about how we've started to work on localizing the Get Involved page and how it fits in with our strategy for bringing more contributors in to projects across Mozilla.

http://davidwboswell.wordpress.com/2012/07/11/connecting-with-contributors-everywhere/
Depends on: 773322
Depends on: 780911
Depends on: 780913
Whiteboard: [l10n] → [l10n] sp-2012-08-14 u=user c=l10n
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
Depends on: 792107
Component: General → L10N
Hi David,

I am interested for localization of this landing page.
 i've already done with localizing webmaker landing page in hindi language moreover project nemo page.

http://thecyberspark.com/webmaker

Please let me know regarding this.

Thanks
(In reply to Faisal Aziz from comment #34)
> I am interested for localization of this landing page.
>  i've already done with localizing webmaker landing page in hindi language
> moreover project nemo page.
> 
> http://thecyberspark.com/webmaker

Faisal, great, I'm glad to hear you're interested in localizing the Get Involved page.  I've added you to the list of locale point people for this page at

https://wiki.mozilla.org/Contribute/Point_people#By_Locale

Pascalc, how would you prefer to handle new localization requests?  Should we file bugs that block this tracking bug for each locale or is there another way to track things?
Depends on: 795033
Depends on: 795130
A copy of this file has already checked in as r109466.
Thanks Peter, David do you mind opening separate bugs for zh-TW and hi-IN locales ?

Thanks
Comment on attachment 665872 [details]
Chinese Traditional (zh-TW) translation for contribute.lang

moved to bug 795304
Attachment #665872 - Attachment is obsolete: true
(In reply to Pascal Chevrel:pascalc from comment #37)
> Thanks Peter, David do you mind opening separate bugs for zh-TW and hi-IN
> locales ?
> 
> Thanks

Pascal, David, 
I have filed bug 795304 for zh-TW, feel free to add anything needed to the bug :)
Depends on: 795364
(In reply to Pascal Chevrel:pascalc from comment #37)
> Thanks Peter, David do you mind opening separate bugs for zh-TW and hi-IN
> locales ?

I just added bug 795364 for hi-IN.

FWIW, there are some people who expressed interest that I've tracked on the Point People wiki page that aren't being tracked here.  I'll go through that list soon about make sure every one of those locales is included here.
Depends on: 795488
Depends on: 795546
Depends on: 795779
Depends on: 796062
Depends on: 796066
Depends on: 796401
Depends on: 796406
Depends on: 796845
Depends on: 799273
Whiteboard: [l10n] sp-2012-08-14 u=user c=l10n → u=user c=l10n p=2
Depends on: 819557
Depends on: 823536
Depends on: 827693
Depends on: 830298
Depends on: 830301
Depends on: 830441
Depends on: 831987
Depends on: 837722
Depends on: 841324
Depends on: 842122
Filed bug 842122 for id.

David/Brian/Pascal could you setup the lang files and email response for id? Thanks!
Depends on: 842958
Depends on: 844167
Depends on: 854285
Depends on: 854992
Depends on: 856922
Depends on: 859537
Depends on: 873281
Depends on: 884248
Depends on: 885975
Depends on: 908714
Depends on: 956155
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: