bug-gnuzilla
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnuzilla] New GNUzilla and IceCat maintainer


From: Simon Josefsson
Subject: Re: [Bug-gnuzilla] New GNUzilla and IceCat maintainer
Date: Thu, 26 Apr 2012 10:30:43 +0200
User-agent: Gnus/5.130004 (Ma Gnus v0.4) Emacs/24.0.94 (gnu/linux)

"Loic J. Duros" <address@hidden> writes:

> Hi,
>
> I have just been made maintainer of IceCat and GNUzilla.

Congratulations!

> Thanks to Giuseppe Scrivano for all his work in the past and how far
> he took the project. I have contacted him aside and I hope we'll be
> able to discuss how IceCat has been run until now, and the direction
> towards which the project will go in the future.
>
> As you may already know, our plans for IceCat are big, starting with
> an improved privacy extension and the detection of nonfree nontrivial
> JavaScript. GNU LibreJS detects nonfree nontrivial JavaScript and will
> be enabled by default in IceCat after a few interactions with the
> extensions currently used by IceCat are addressed.
>
> We will also need an add-on list that is more up to date and easily
> searchable. One idea was to use the AMO API to find which add-ons have
> a free license to get an up-to-date list of add-ons that could
> potentially make it to the IceCat add-on list. Some of you on the list
> have already shown some interest to work on this (Thanks
> Leonardo!). As Jason Self suggested, we could then use such tools as
> Fossology to ensure all the extension code is effectively under a free
> license, and automate as much as possible, the ongoing maintenance
> work that the IceCat add-on manager requires.
>
> The initial release of IceCat 12 might take a little longer since
> there is a lot to work on, but I expect subsequent versions will
> regularly become available shortly after Mozilla publishes new
> versions of its browser.
>
> Thanks, and I'm looking forward to getting the next release up.

Great.  From my selfish point of view, I suggest to postpone as much of
new development as possible, and focus on getting the version 12 release
out and *.deb packages built so that people can start to use the latest
version as soon as possible.  Then incrementally address the issues you
want done.  Just my $.2.

/Simon



reply via email to

[Prev in Thread] Current Thread [Next in Thread]