This level of effort is not easy to maintain, so we need to justify the costs. Given Maemo has been end-of-lifed, there is little desire to continue at the current level of effort. I'd like to create some proposals for Mozilla's roadmap for Firefox for Maemo. I'll go first.
Baseline Proposal:
Let's move Firefox for Maemo to a Tier 3 build configuration. Tier 3 is defined as:
"Tier-3 platforms have a maintainer or community which attempt to keep the platform working. These platforms may or may not work at any time, and often have little test coverage"
from https://developer.mozilla.org/en/Supported_build_configurations
Firefox for Maemo has a somewhat active community. Bugs get filed and patches get created. This is a good thing. This is the baseline proposal. Essentially, this means:
* The code is not removed from the Mozilla source tree
* Developers could pull the source and make builds
* Bugs and patching are the core responsibility of the community, not Mozilla
* Any L10N outside of the core source code would also fall to the community to manage
* Mozilla would stop doing any builds and testing (automated or otherwise) - this falls to the community to manage
-----
There are other levels of effort we can discuss as well. Mozilla has build infrastructure in place and might be able to continue creating builds will little effort. Maybe not. Mozilla has a large pool of N900 devices used for automated testing. Maybe these could be managed by a community group and not Mozilla. Maybe not.
The main point you should take away from this posting is that the staus quo can not continue. Feedback, corrections and additional information is welcome.
Mark Finkle
* Builds are not considered "tier 1", which means any breakage is not fixed immediately, but breakage is still fixed as soon as feasible.
> _______________________________________________
> dev-platforms-mobile mailing list
> dev-platfo...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platforms-mobile
>
This will make the community shrink considerably and probably mostly die
out - but I guess that's the actual intention. After all, us
freedom-loving Maemo/MeeGo freaks are not an interesting market due to
the sheer number of followers of the various more closed up mobile
religions out there (and I'm trying hard to hold back any [de]valuing
attributes).
Robert Kaiser
--
Note that any statements of mine - no matter how passionate - are never
meant to be offensive but very often as food for thought or possible
arguments that we as a community should think about. And most of the
time, I even appreciate irony and fun! :)
Robert,
Don't you think the lack of credible hardware running these platforms is
the main reason for MoCo lowering its official support?
Freedom-loving freaks should work on getting meego running on top of
cyanogenmod kernels to reach current android users IMHO (personally I
would love this).
Fabrice
The crappy fork called the "android kernel" is nothing us freaks will
want to run. There's no reasons (once the GPL requirement to make free
drivers available is being followed) not to run a real Linux kernel and
a full MeeGo on the same devices - just that there's no good handset UX
for MeeGo yet. The community will probably fill that gap one day - or
some vendor may help, as there are some vendors doing R&D with MeeGo
nowadays (no officially release hardware yet, though, but Mozilla hasn't
stated any support or interest for MeeGo anyhow, and they are going with
WebKit-based browsers instead, which probably are a better solution for
them).
What do you think?
cheers,
Armen
[1]
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/6.0b2-candidates/build1/contrib/
On 11-07-13 5:51 PM, Doug Turner wrote:
> I support this decision. Maemo hasn't be a priority in practice and
> it is good to see we are taking about it.
>
> On Wed, Jul 13, 2011 at 2:38 PM, Mark Finkle<mfi...@mozilla.com> wrote:
>> To make responsible use of our limited resources, it's time to discuss the future status of the Firefox for Maemo 5 (GTK and Qt) releases and infrastructure. Mozilla is currently treating the Maemo builds with a medium to high priority:
>> * Builds, unit tests and performance tests are executed for all changes landed in mozilla-central (and other project branches)
>> * Nightlies are created and tested
>> * Aurora, Beta and Final releases are created and tested
>> * Final releases are in the Ovi Store
>> * Builds are not considered "tier 1", which means any breakage must be fixed immediately, but breakage is still fixed as soon as feasible.
>>
>> This level of effort is not easy to maintain, so we need to justify the costs. Given Maemo has been end-of-lifed, there is little desire to continue at the current level of effort. I'd like to create some proposals for Mozilla's roadmap for Firefox for Maemo. I'll go first.
>>
>> Baseline Proposal:
>>
>> Let's move Firefox for Maemo to a Tier 3 build configuration. Tier 3 is defined as:
>>
>> "Tier-3 platforms have a maintainer or community which attempt to keep the platform working. These platforms may or may not work at any time, and often have little test coverage"
>>
>> from https://developer.mozilla.org/en/Supported_build_configurations
>>
>> Firefox for Maemo has a somewhat active community. Bugs get filed and patches get created. This is a good thing. This is the baseline proposal. Essentially, this means:
>> * The code is not removed from the Mozilla source tree
>> * Developers could pull the source and make builds
>> * Bugs and patching are the core responsibility of the community, not Mozilla
>> * Any L10N outside of the core source code would also fall to the community to manage
>> * Mozilla would stop doing any builds and testing (automated or otherwise) - this falls to the community to manage
>>
>> -----
>>
>> There are other levels of effort we can discuss as well. Mozilla has build infrastructure in place and might be able to continue creating builds will little effort. Maybe not. Mozilla has a large pool of N900 devices used for automated testing. Maybe these could be managed by a community group and not Mozilla. Maybe not.
>>
>> The main point you should take away from this posting is that the staus quo can not continue. Feedback, corrections and additional information is welcome.
>>
>> Mark Finkle
>>
>> _______________________________________________
>> dev-platforms-mobile mailing list
>> dev-platfo...@lists.mozilla.org
>> https://lists.mozilla.org/listinfo/dev-platforms-mobile
>>
--
Armen Zambrano Gasparnian (armenzg)
Mozilla Corp Release Engineer
~ Jesus Christ is my Lord
Doug