1,035
edits
| Line 12: | Line 12: | ||
Now you and your community are set up to do the actual localization work. | Now you and your community are set up to do the actual localization work. | ||
You may want to set up a central repository for your work (code, mailing lists, newsgroups, website). Depending on your working habits and the size of your team, you may want to look into open source hosting offers like [http://mozdev.org mozdev.org] or [http://sf.net/ SourceForge]. You can also just use plain files and regular backups, or set up your own | You may want to set up a central repository for your work (code, mailing lists, newsgroups, website). Depending on your working habits and the size of your team, you may want to look into open source hosting offers like [http://mozdev.org mozdev.org] or [http://sf.net/ SourceForge]. You can also just use plain files and regular backups, or set up your own [http://en.wikipedia.org/wiki/Version_control_system#Distributed_revision_control P2P VCS]. | ||
Instead of localizing a language pack directly, you should localize in the source directory structure, and then make your work publicly available. We believe this as a good way to start out because it let's people know you are open to new collaborators and enabling a smooth path going forward. | |||
To make your work available for users to download and test, create a language pack which can be hosted on [https://addons.mozilla.org/en-US/firefox/browse/type:1/cat:37 AMO]. AMO offers many advantages for both you and your testers and users, from download capacity to automatic updates of your Add-on. | To make your work available for users to download and test, create a language pack which can be hosted on [https://addons.mozilla.org/en-US/firefox/browse/type:1/cat:37 AMO]. AMO offers many advantages for both you and your testers and users, from download capacity to automatic updates of your Add-on. | ||
edits