Verbatim: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (16 intermediate revisions by 4 users not shown) | |||
| Line 4: | Line 4: | ||
*'''Code Name:''' Verbatim (sometimes called ''mozootle'') | *'''Code Name:''' Verbatim (sometimes called ''mozootle'') | ||
*'''Start Date:''' April 2008 | *'''Start Date:''' April 2008 -- ([http://spreadsheets.google.com/ccc?key=pOtMYJlCOxhWN78j_JFQWGw 2008 goals spreadsheet]) | ||
*'''Site Repository:''' | *'''Site Repository:''' | ||
** | ** Live site: https://github.com/mozilla/verbatim | ||
** Mozilla specific external: http://svn.mozilla.org/projects/verbatim/ | ** Pootle upstream: https://github.com/translate/pootle <del>https://translate.svn.sourceforge.net/svnroot/translate/src/trunk ([http://translate.svn.sourceforge.net/viewvc/translate/src/trunk/ ViewVC])</del> | ||
*''' | ** Mozilla specific external (currently unused): http://svn.mozilla.org/projects/verbatim/ | ||
*'''Production Site:''' | ** Mozilla Pootle branch (deprecated): https://translate.svn.sourceforge.net/svnroot/translate/src/branches/mozootle ([http://translate.svn.sourceforge.net/viewvc/translate/src/branches/mozootle/ ViewVC]) | ||
* '''QA Test Plan''': | *'''Dev/Stage Site:''' https://localize.allizom.org/ (uses "development" branch) | ||
*'''Bugs''': [ | *'''Production Site:''' https://localize.mozilla.org/ (uses "master" branch) | ||
* '''QA Test Plan''': TBD | |||
*'''Bugs''': [https://bugzilla.mozilla.org/buglist.cgi?product=Webtools&component=Verbatim&resolution=--- Current Bugs] || [https://bugzilla.mozilla.org/enter_bug.cgi?product=Webtools&component=Verbatim File a new bug] | |||
*'''Development Contact:''' join #verbatim on irc.mozilla.org | *'''Development Contact:''' join #verbatim on irc.mozilla.org | ||
== Links == | == Links == | ||
* [[ | * Meeting Notepad: [[#Weekly_Meetings|See below]] | ||
* [[Verbatim:Deployment|Deployment]] | * [[Verbatim:Deployment|Deployment]] (vastly out of date and might be replaced soon anyway) | ||
* Development Planning | * Development Planning | ||
** [[Verbatim:Development/Dev Instance|Setting up a Verbatim development instance]] | |||
** [[Verbatim:Development/filetypes|Interaction with file types]] | ** [[Verbatim:Development/filetypes|Interaction with file types]] | ||
** [[Verbatim:Development/commithooks|Commit Hooks]] | ** [[Verbatim:Development/commithooks|Commit Hooks]] | ||
** [[Verbatim: | ** [[Verbatim:Interaction with SVN|Interaction with SVN]] | ||
** [ | ** [[Verbatim:Development/development_refresh|2009 Q3 Development Refresh]] | ||
== Brief Description== | == Brief Description== | ||
| Line 29: | Line 31: | ||
* Using extensible libraries, provide an interface for localizing content of different types (e.g. AMO .po files, Firefox .properties files, etc.) | * Using extensible libraries, provide an interface for localizing content of different types (e.g. AMO .po files, Firefox .properties files, etc.) | ||
* Provide a UI for localizing strings on the web, but '''don't require | * Provide a UI for localizing strings on the web, but '''don't require its use'''. It's important that localizers can still interact directly with code repositories as many of them find this the most efficient way to contribute. | ||
* Notification of changes to an English page and a way to diff those changes to locales | * Notification of changes to an English page and a way to diff those changes to locales | ||
* Provide statistical data including percentage of localized content per locale, overall project (e.g. Firefox 3 or mozilla.com) progress, etc. | * Provide statistical data including percentage of localized content per locale, overall project (e.g. Firefox 3 or mozilla.com) progress, etc. | ||
| Line 36: | Line 38: | ||
==Weekly Meetings== | ==Weekly Meetings== | ||
The project contributors will meet weekly to discuss project goals and progress. [[Verbatim/Weekly_Meetings | Status updates can be found here]]. | |||
Latest revision as of 16:13, 6 September 2013
Verbatim is the codename of Mozilla's install of Pootle.
Project Information
- Code Name: Verbatim (sometimes called mozootle)
- Start Date: April 2008 -- (2008 goals spreadsheet)
- Site Repository:
- Live site: https://github.com/mozilla/verbatim
- Pootle upstream: https://github.com/translate/pootle
https://translate.svn.sourceforge.net/svnroot/translate/src/trunk (ViewVC) - Mozilla specific external (currently unused): http://svn.mozilla.org/projects/verbatim/
- Mozilla Pootle branch (deprecated): https://translate.svn.sourceforge.net/svnroot/translate/src/branches/mozootle (ViewVC)
- Dev/Stage Site: https://localize.allizom.org/ (uses "development" branch)
- Production Site: https://localize.mozilla.org/ (uses "master" branch)
- QA Test Plan: TBD
- Bugs: Current Bugs || File a new bug
- Development Contact: join #verbatim on irc.mozilla.org
Links
- Meeting Notepad: See below
- Deployment (vastly out of date and might be replaced soon anyway)
- Development Planning
Brief Description
As the number of localized Mozilla properties (both browser and web) grow, coordination is becoming more difficult and more of a timesink. This project's goals are broad but will have a big impact on the number of localizations we can manage by lowering the barrier to entry and by giving localizers options to make their work easier. Initial goals are:
- Using extensible libraries, provide an interface for localizing content of different types (e.g. AMO .po files, Firefox .properties files, etc.)
- Provide a UI for localizing strings on the web, but don't require its use. It's important that localizers can still interact directly with code repositories as many of them find this the most efficient way to contribute.
- Notification of changes to an English page and a way to diff those changes to locales
- Provide statistical data including percentage of localized content per locale, overall project (e.g. Firefox 3 or mozilla.com) progress, etc.
These main project goals may be tweaked (e.g. adding anonymous contributions) but this set will be our first milestone.
Weekly Meetings
The project contributors will meet weekly to discuss project goals and progress. Status updates can be found here.