Axel Hecht [:Pike] Reporter
	Description • 17 years ago

This is a tracker bug for releasing Firefox 3 ne-NP.

This bug is not that detailed, but as we get particular work items, they should block this bug for tracking, and better discoverability.

This is blocked on branching for Firefox 2, or at least deciding what we want to do, so marking that dependency.

	Axel Hecht [:Pike] Reporter
	Comment 1 • 17 years ago

We should add a wikipedia plugin for Fx3, either English or Nepali.

	Axel Hecht [:Pike] Reporter
	Comment 2 • 16 years ago

Moving this out to Firefox 3.1, I don't see us being far enough here to still target a release on the 3.0 tree.

	Axel Hecht [:Pike] Reporter
	Comment 3 • 15 years ago

Basanta, did you have a chance to update your work here? I'm on a sprint through our open bugs and came across this.

	Axel Hecht [:Pike] Reporter
	Comment 4 • 15 years ago

We have 3.6 now, we'll open new bugs if a ne-NP localization teams comes around again.

Resolving shipping on 3.5 as WONTFIX.

	Basanta Shrestha
	Comment 5 • 14 years ago

I want to target for next release. Please briefly suggest where do I start.

	Axel Hecht [:Pike] Reporter
	Comment 6 • 13 years ago

Morphing this bug into a version-indepent tracker.

Basanta, I see that we didn't follow up on your comment here for a good year. Sorry for that.

Would you still be up for getting ne-NP up to speed? I just ran compare-locales locally against the repo we have, and that'd be some 3000 strings behind.

	Milos Dinic [:Milos]
	Comment 7 • 13 years ago

Firstly, congratulations team!

You have worked and managed to get all the dependencies for this bug fixed, which means that productization for Nepali Firefox is all done. Please take a minute or two and read the next steps to follow.

== Aurora ==

Every 6 weeks, we will update aurora repositories with new strings that will require some additional time spent on it. As you probably already know, we advise all localizers to use Aurora channel for all translations, so that we can merge them with Beta channel when needed without any regressions. So, please use Aurora as your primary working repo, and in case you're landing a fix to Beta channel, please port it back to Aurora too. Once the Aurora builds are available, please use them as much as you can for the purpose of testing your own translations and making sure everything is as it should be.

== Bugs ==

Please check your dashboards every now and then to see if there are some bugs filed against Firefox Nepali. You can check the status of your latest builds and some team info on l10n dashboard teams page at https://l10n-stage-sj.mozilla.org/teams/ne-NP . As the website evolves, you'll start using that as your primary source of info related to localization.

One other important thing to have in mind is webdashboard. We use webdashboard to show contributors bugs related to web localization for their locale. This is really important as we use our websites to promote localized Firefox builds.

== Staying connected ==

You should also follow the Mozilla l10n newsgroup, http://www.mozilla.org/community/forums/#dev-l10n, available as mailing list, newsgroup or google group. The traffic isn't too high frequency. 

You'll find all announcements at http://www.mozilla.org/community/forums/#dev-l10n-announce . Those are vital to read, as they include things that the l10n-drivers want you to know and attend to. 

There's a third group, http://www.mozilla.org/community/forums/#dev-l10n-web, where we discuss web localization issues. That's a separate group as quite a few localization teams have dedicated volunteers for that.

Another important thing is staying in touch with community and make yourself available for anyone who wants to contribute. So, if possible, get in touch with community on community forums, get feedback and possibly more volunteers.

Enjoy and congratulations!