User:Sipaq
Contents
What sipaq has been doing
The Calendar project
L10n Coordinator
This is a list of tasks, that I've performed when I was Calendar l10n coordinator and the necessary time that is needed to do the job (from my perspective). I've tried to remember as much as possible, but it may be that I've missed some things.
The time that is assigned to each task is the minimum amount of time, that I think is necessary to do a particular job properly. More time will surely improve things in a lot of areas, most notably localizer recruitment and l10n documentation. Also keep in mind, that I've performed these tasks for more than three years, so a newcomer will likely take more time until he becomes acquainted with all the different aspects of the job.
| Task |
Time spent |
|---|---|
| Monitoring newsgroups and mail account for l10n relevant issues |
10 minutes per day |
| Regularly watching the L10n dashboardfor new sign-offs |
3-5 minutes a day |
| Checking a sign-off before approving it (normally what I would do is look at each hg revision between the last sign-off and the current sign-off request and look for any glaring errors) |
5-30 minutes per locale (depending on the amount of research) |
| Stay in contact with current localizers (answer upcoming questions, contact them in case of broken checkins, participate in newsgroup discussions, visit #l10n on IRC, etc.) [Localizer contact addresses are at wiki.mozilla.org/L10n:Teams] |
10 minutes per day (this may increase to an hour during release crunch) |
| Work on localizer recruitment (basically I would contact newly added Firefox localizations and ask them whether they would want to join our team as well. You don't get any quick successes there normally, but being persistent gets you where you want in time) |
1 hour each month |
| Post to the calendar weblogabout upcoming events (e.g. release planning) that are relevant for localizers |
1 hour each month |
| Stay in contact with Firefox l10n drivers (Axel Hecht/Pike and Seth Bindernagel/SethB in particular) to stay abreast of technological progress and other issues relevant for localizers that you need to be aware of as l10n coordinator |
1 hour each month |
| Stay in contact with the calendar developer community (this encompasses participating in the release planning, giving feedback on issues that are relevant or directly affect localizers, bugging developers about keeping localizers informed of major changes or late-l10n changes |
10 minutes per day (this may increase to an hour each day during release crunch) |
| Checkin/commit/push new localizations for new localizers with minor hg skills |
1 hour per added localization |
| Document l10n relevant issues for new localizers and developers, e.g. https://developer.mozilla.org/en/Calendar/Localization |
1 hour each month |
| Bug-Triaging This is especially important during the release preparation phase, where the bugs need to be triaged in bugs with l10n impact and those without. Bugs with l10n impact need to be prioritized by developers so that they are fixed before a string freeze date. |
1 hour in the release preparation phase |
Relevant skills that are needed for the position:
- Strong knowledge of the Mozilla l10n system and l10n infrastructure
- Good communication skills
- Good written English
- Good knowledge of Mercurial (hg)
- Minor HTML skills (sufficient for blog posting)
- Commit rights for Mozilla Mercurial repositories (optional)
- Good knowledge of the Calendar community (optional)
The last two items are considered to be optional, as the job can initially be done without the last two items and over time things will sort themselves out naturally. Though someone who has these skills already obviously has an advantage.
Calendar webmaster
This is a list of tasks, that I've performed when I was Calendar webmaster. I've tried to remember as much as possible, but it may be that I've missed some things.
- Watch the Website component in the Calendar product on bugzilla for new bugs and comments in existing bugs.
- Add new files or update existing files as the need arises (especially for new and updated holiday files)
- Update the website for new releases
- Work on a plan (and hopefully implement it) to improve the website, its design, its contents, etc.
Relevant skills that are needed for the position:
- Good HTML/CSS skills (JS skills are a plus, but not really needed)
- Good written English
- Some knowledge of the Calendar community
- Good knowledge of bugzilla
- Good knowledge of SVN (version control system to keep the website up-to-date)
Various things in the Calendar project
- Work on press contacts
- Update the calendar weblog with current news about the project, status updates, etc.
- Minor fundraising (we could really do a lot with regards to Lightning on AMO if someone had the time and the energy to pursue it)
- Keep in contact with various players in the wider Mozilla World, e.g. Mark Surman and David Boswell at MoFo, Mitchell Baker, etc.
- Minor QA and bug-triaging efforts
- Giving people elevated permissions (CANCONFIRM, EDITBUGS) in bugzilla.
- Working on calendar-related issues on Get Satisfaction
- Working on issues and answering questions in various newsgroups (e.g. de.comm.software.mozilla.*, mozilla.support.calendar, mozilla.dev.apps.calendar)
- Regularly watch download/usage statistics for Lightning and Sunbird and put them in a spreadsheet
Thunderbird
L10n Coordinator
This is a list of tasks, that I've performed when I was Thunderbird l10n coordinator and the necessary time that is needed to do the job (from my perspective). I've tried to remember as much as possible, but it may be that I've missed some things.
The time that is assigned to each task is the minimum amount of time, that I think is necessary to do a particular job properly. More time will surely improve things in a lot of areas, most notably localizer recruitment and l10n documentation. Also keep in mind, that I've performed these tasks for more than two years, so a newcomer will likely take more time until he becomes acquainted with all the different aspects of the job.
| Task |
Time spent |
|---|---|
| Monitoring newsgroups and mail account for l10n relevant issues |
10 minutes per day |
| Regularly watching the L10n dashboardfor new sign-offs |
6-10 minutes a day (more for Thunderbird as there always at least two release branches open) |
| Checking a sign-off before approving it (normally what I would do is look at each hg revision between the last sign-off and the current sign-off request and look for any glaring errors) |
5-30 minutes per locale (depending on the amount of research) |
| Stay in contact with current localizers (answer upcoming questions, contact them in case of broken checkins, participate in newsgroup discussions, visit #l10n on IRC, etc.) [Localizer contact addresses are at wiki.mozilla.org/L10n:Teams] |
10 minutes per day (this may increase to an hour during release crunch) |
| Work on localizer recruitment (basically I would contact newly added Firefox localizations and ask them whether they would want to join our team as well. You don't get any quick successes there normally, but being persistent gets you where you want in time) |
1 hour each month |
| Post to the Thunderbird l10n blog'about upcoming events (e.g. release planning) that are relevant for localizers' |
1 hour each month |
| Stay in contact with Firefox l10n drivers (Axel Hecht/Pike and Seth Bindernagel/SethB in particular) to stay abreast of technological progress and other issues relevant for localizers that you need to be aware of as l10n coordinator |
1 hour each month |
| Stay in contact with the Thunderbird developer community (this encompasses participating in the release planning, giving feedback on issues that are relevant or directly affect localizers, bugging developers about keeping localizers informed of major changes or late-l10n changes |
10 minutes per day (this may increase to an hour each day during release crunch) |
| Checkin/commit/push new localizations for new localizers with minor hg skills |
1 hour per added localization |
| Document l10n relevant issues for new localizers and developers, e.g. https://developer.mozilla.org/en/Thunderbird_Localization |
1 hour each month |
| Bug-Triaging This is especially important during the release preparation phase, where the bugs need to be triaged in bugs with l10n impact and those without. Bugs with l10n impact need to be prioritized by developers so that they are fixed before a string freeze date. |
3 hours in the release preparation phase |
Relevant skills that are needed for the position:
- Strong knowledge of the Mozilla l10n system and l10n infrastructure
- Good communication skills
- Good written English
- Good knowledge of Mercurial (hg)
- Minor HTML skills (sufficient for blog posting)
- Commit rights for Mozilla Mercurial repositories (optional)
- Good knowledge of the Thunderbird community (optional)
The last two items are considered to be optional, as the job can initially be done without the last two items and over time things will sort themselves out naturally. Though someone who has these skills already obviously has an advantage.
