TB and AMO...
ben.bucksch at beonex.com
Wed Nov 20 15:42:06 UTC 2013
while that reasoning makes sense from the AMO perspective, please
consider this perspective:
* Seamonkey is a grass-roots Mozilla project, and customization (incl.
extensions) is important to its user base. Killing AMO would be a
serious discouragement to the last few volunteer Mozilla developers we have.
* Seamonkey does generate money through search. We had been talking
about making contracts directly with search engines, but eventually, the
Seamonkey searches go to Mozilla. In exchange, Seamonkey can use the
Mozilla infrastructure. So, while I don't know the concrete cost that an
additional AMO product imposes, it might indeed be financially reasonable.
Wil Clouser wrote, On 04.11.2013 19:01:
> It was requested I reply to this thread so I'll paste in a private response I
> wrote earlier. The summary is what has already been said here - don't panic,
> we'll cross that bridge when we get there.
> My other email:
>> There hasn't been an official discontinuing of either TB or Seamonkey add-ons
>> on AMO, however, every application we support has a cost and some applications
>> can't be justified. We disabled Sunbird in 2010 because it wasn't worth the
>> maintenance cost.
>> We reviewed our project stats again in 2012 and for the month of March 2012 we
>> averaged 1.2MM visits per day from Firefox UAs, and 6k per day from Seamonkey
>> UAs. When you're looking at where to put resources, it's a pretty clear
>> decision. I expect those numbers are even further apart today.
>> As it stands today, there are no FTE resources working on AMO so it's just in
>> a holding pattern. When work picks up on it again, we'll start making
>> decisions on applications to support.
> tb-planning mailing list
> tb-planning at mozilla.org
More information about the tb-planning