Welcoming myself to the team!
mh at glandium.org
Tue Oct 12 07:54:55 UTC 2010
On Mon, Oct 11, 2010 at 11:34:26PM -0400, Asheesh Laroia wrote:
> Hello dear Mozilla maintainers,
> I'm a DD (paulproteus at Debian), and I've decided to join y'all's
> list since I think good maintenance of things like Iceweasel is very
> important. So I should be able to put a little time into that.
> I don't have oodles of time, and I'm new to the vagaries and
> difficulties of Mozilla maintenance. So I'd appreciate pointers to
> documentation and things to read, or good first packaging bugs to
> look at. Or if there are other ways the team could use help, let me
> I couldn't find a wiki page on this team, so maybe you guys aren't
> interested in new people. Maybe you'll say the right thing to do is
> to just read through the bugs in the packages list here: http://firstname.lastname@example.org
> Either way, my plan is to see if you guys answer this thread, and
> then lurk for a few weeks, and get a sense of what life is like
> inside the pkg-mozilla-maintainers world.
The reason there is no wiki page for this team, and not much
documentation in general is mainly because the Mozilla maintainers team
is a "team" of roughly one active member. So any external help is
At the moment, I'm handling the workload induced by new upstream
releases quite well, but any help is appreciated.
There are a few things I've been slacking on that could be a good start:
- Follow up on all the logo proposals that ended up on this list,
- Write some documentation on the packaging.
- Finish the remaining parts of the plan for squeeze I announced to the
0. Please note that work is ongoing to get a trademark agreement with
the mozilla foundation for the use of the Firefox trademark. This
however doesn't mean iceweasel is going to die, as we'll still need a
"stable" fallback for derivatives who don't want to bother with a
1. I've been postponing that forever, though the package has almost
gotten in the shape I wanted it to have before really documenting.
2. Remaining items are:
- Improve or remove the restart popup that shows up when upgrading the
package. The main problem it is trying to avoid is the impossibility
to cleanly close iceweasel after an upgrade. I need to test further,
but there are chances this is really only needed when upgrading
between major versions. I'm not entirely sure it has a benefit for
other cases, though apart from one complaint on planet.debian.org, I
saw no feedback... there are a bunch of known issues with it, like
with multiple iceweasel windows, or like not activating again when
the user doesn't want to restart now but the browser is upgraded again
- Improve the situation with search box icons (those showing up in the
box on the top right of the UI):
the main problem is that the icons had to be removed from the source,
because they are not free. The result is that now, the icons are
really links to the icons on the original web sites. The problem is
that the code surrounding this upstream is not adequate for such use,
and the cache is not persistent enough, and a failure to load the icon
once results in the icon never been reloaded ever again (except maybe
after an upgrade)
- Improve the xpcom standalone glue so that it loads the most
appropriate version instead of the first one it finds that matches the
Otherwise, any help is appreciated on bug triaging.
And here I realize I'm mainly talking about Iceweasel, but we mustn't
forget about Iceape and Icedove, speaking of which it would be great if
we could finally get Icedove maintainer(s) to join the party.
Please tell me if you're interested in one or some of the topics above.
Thanks for your help.
More information about the pkg-mozilla-maintainers