3
edits
Changes
m
= Potential Fedora+Mozilla Projects =
Create an add-on that will be able Currently it requires many many steps to tell which are the official produce another language packages for each release and allow the user of Firefox.It would really easy to select which ones package these many steps to download and allow reduce the user to select from the language packages that have been downloaded.The extension should allow required knowledge to provide custom URLs pointing to unofficial language packages.Once this extension proves its usability we can generate a custom build that includes this extension and therefore a user would be able to choose their new language upon first start.
References: armenzgAdding a few make steps to wrap this process would help everyone.This is a very easy project to tackle but very benefitial if the time and love is given to it.
== Automate generation of regionalized locales ==Reference: armenzg
ReferencesReference: armenzg- Bug 498641
* Approved review requests - http://fedoraproject.org/wiki/PackageMaintainers/ApprovedReviewRequests
-->
= Potential Mozilla Projects =
NOTE: if someone has already created the project page, speak to this person and see if you can join them. If so, simply add your name to the '''Project Leader(s)''' page. Otherwise, you can become a contributor later.
== Autoload language packs Improve Localization build system ==
== Create a cross-repo pushlog to see all locales's checkins ==We have currently check many different repositories to trigger builds when a script from developer makes a previous Moz-Seneca project change. We also check the localizer's repositories to see if they have pushed any changes. The problem is that we have close to eighty different localization repositories and that can generate a new locale by providing takes a set long time to check each one of rules in a filethem. If we can generate new locales by providing an automated way with buildbot, we could had a joint view that would improve our systems. An example of that view is:https://l10n-stage-sj.mozilla.org/pushes/but the format should be generating locales more like enthis:http://hg.mozilla.org/mozilla-CA central/pushlogwhich is what our release engineering systems check for.This project would require you to hack hg and leverage the dependence for official approvalspushlog to make it work.armenzg has many blog posts explaining how to setup pushlog in your local machine.
== Thunderbird SMTP Auto-Sensing ==
