Visit Mozilla.org

User:KaiRo

From MozillaWiki

Contents

About me [edit]

My name is Robert Kaiser, I've been localizing the Mozilla "Seamonkey" application suite to German (Mozilla deutsch) since late 1999, since summer 2004 I'm leading the Mozilla Localization Project (MLP), and since March 2005 I'm in the team working on a future of "Seamonkey".
For more info about me (and if you understand German), visit Home of KaiRo.

SeaMonkey project [edit]

I'm part of the team working on a future of Seamonkey (long-time internal code name of the "Mozilla Application Suite", often only called "Mozilla", final name is not public yet).

Here's a list of I what I plan to do or am working on:

  • Re-branding work: We need to change the product name and version numbers, and reflect that in the software. See bug 285696. That also involves artwork that still has to be done, and adjusting the User Agent and executable name.
  • Project Management: I'm trying to keep an overview of the project and drive progress in several organizational areas, while other Council members concentrate more on coding or review. All that stuff gets discussed in the Coucil though, and decisions need an agreement of all Council members.
  • L10n: As it overlaps with my tasks as MLP leader and German L10n contributor, I want to make SeaMonkey L10n work as smooth as possible. That involves cooperation with gandalf and bsmedberg to get source L10n for SeaMonkey (see bug 286110), and that might also involve work on getting rid of seperate content packs.
  • Communication with MoFo: I'd like to keep good contacts with Mozilla Foundation (Asa and others) and toolkit/aviary people (e.g. mconnor) so that our project can work as smooth as possible, leveraging MoFo infrastructure as good as possible.
  • UI design: work on proposals and take part in discussion for improving the appearance of SeaMonkey UI. This includes polishing the default theme (better icon set?), thinking of how to improve prefs dialog without going as far as Firefox, and various other stuff

And this is stuff I'd like to see happening/landing in SeaMonkey (maybe even before 1.0, no stuff that needs a full toolkit migration):

  • Plugin Finder Service (pfs) - probably should use info bars, mcsmurf has a patch - bug 278831
  • XPI whitelisting UI - needs info bars, current behaviour is quite bad - bug 270170
  • Info bars - see above why, CTho has a patch - bug 270443
  • Error Pages - may just need to be turned on, but still have some small issues - bug 28586
  • Source L10n - bug 286110

Stuff I'd like to see later (may need toolkit):

  • Possibility to access mail/news messages by message ID, so that news URLs using that can be used correctly, and that we can parse and display References headers with links to the messages
  • Some UI for "Find As You Type" - find bar at the bottom looks strange though
  • Extension Manager: needed for chrome versioning, one of the first migration steps
  • Merge region and platform locale packages into the main locale package (en-US.jar) and remove content pack switching stuff - covers bugs 180508/102509 in some way
  • Polishing of default theme, esp. new icon set
  • Find a way to keep grippies and the splash screen even with toolkit
  • Turn on calendar by default

Personal TODO list for MLP [edit]

  • add policies/guidelines for "how to get a localization into CVS initially" to registration.html (text will be written up by gandalf and proof-read by the L10n call team, including marcia)
  • talk to bsmedberg if can we move stuff from FF/l10n to MLP again, decide what to do about old (pre-FF 1.0) contributor list
  • make a draft for "about MLP" page, including list from bug 257931 - or perhaps better the one from my FOSDEM talk
  • work on L10n:MLP page structure document on the wiki, get MLP pages into shape based on that

Random thoughts, would-be-nice-to-have things [edit]

  • may be nice to have L10n of some products in CVS, even if we can't automatically build it, e.g. SeaMonkey. (It would really help me much if I could place German SeaMonkey help files on the CVS server, for example.)
    <bsmedberg> KaiRo: I am opposed to putting locales into CVS which don't 1) get built by an automated system or 2) appear as a website
    <KaiRo> bsmedberg: good to know... so that would mean we will have an automated build system to get full seamonkey into CVS, but you'd allow seamonkey help to get in?
    <bsmedberg> Basically, yes.
    <bsmedberg> Although *where* seamonkey help should live is a mystery. I don't even know where firefox help lives.
    <bsmedberg> If it's online. Or even if we have a standardized place for it.

Other resources [edit]