>Does it depend on resolving certain known issues?
Unfortunately, we have received a negative response from a Moizilla reviewer to
our request:
He says that he needs access to our source code before leverageing from
"experimental" to "public".
I cannot blame Mozilla policy for that. I even tend to consider that letting
unknown developer upload to "experimental" is quite dangerous and I prefered the
certificate approach available in previous versions of FireFox.
But on the other hand, I don't have to authority to decide giving away our
source code since it is part of a larger comercial application.
Sorry,
Nicolas Roumiantzeff
P.S. if anybody as a suggestion regarding this security issue...
Nicolas Roumiantzeff
Ingénieur Expert Logiciel / Chief Software Engineer
Esker SA
Tél : +33 (0)4 72 83 46 79
Fax : +33 (0)4 72 83 46 40
mailto:Nicolas.Roumiantzeff@...
http://www.esker.fr/ ¦ http://www.flydoc.fr/
From: esker-activex-plugin@yahoogroups.com
[mailto:esker-activex-plugin@yahoogroups.com] On Behalf Of leeoraharon
Sent: Sunday, October 26, 2008 9:10 AM
To: esker-activex-plugin@yahoogroups.com
Subject: Re: [Esker ActiveX Plug-in] PRIVATE
> >Is an alternative location for redistribution something you would
> consider?
>
> With previous versions of FireFox, you could copy the signed JAR
containing the Esker ActiveX Plug-in on any server of your choice.
> But unfortunately, it seems that this is not possible with FireFox 3.
> This is why I chose to upload the Esker ActiveX Plug-in to
addons.mozilla.org as it is the standard way to distribute plugins.
> I also prefere this centralized solution because it is better for
the Esker ActiveX Plug-in community synergy.
I would also like to have my users install this plugin and I agree
that distributing it through the mozilla repository is a good idea.
However, as long as it is marked as experimental, I cannot ask my
users to install it.
Is there any rough estimation to when it will cease to be
experimental? Does it depend on resolving certain known issues?
Thanks,
Leeor.