Future of maemo.org: "The end is coming"
alan bruce, another member of the Maemo Community Council, has posted his thoughts on the transitional position the community is in: Recently, there have been calls for the Maemo community to wrest all the closed bits out of the hands of Nokia, or to somehow turn Maemo into a separate, community-run entity, free of Nokia's sponsorship. I don't see these posts accomplishing anything for two simple reasons; we're never going to get the closed bits from Nokia, and the Maemo community is (almost) nothing without Nokia, mainly because Maemo is nothing without Nokia hardware and that hardware is no longer in production.
Future of maemo.org: A "modest proposal for a direction for maemo.org activities"
"tekki" has proposed a concrete plan for reducing maemo.org costs, and providing a future-proof base for Maemo device: Make a task force to submit and maintain OBS support for Diablo and Fremantle. That would then be contributed to apps.formeego.org, providing a direction for Extras and autobuilder. If Harmattan support already exists, D and F support cant be difficult. Make a task force for maintaining a modern kernel for N8x0 devices. 770 is a lost cause due to binary wifi driver. Propose people to base efforts for N900 on the MeeGo hardware adaptation.
Future of maemo.org: Are the options for the Maemo community really limited to not-for-profit or death?
Your editor, Andrew Flegg, is not convinced of the feasibility of setting up and running a not-for-profit organisation. Instead, he proposes a continuation of the arrangement between the Community Council and Nemein - who currently manage the infrastructure on behalf of the Community: This reduces the workload (by a factor of gazillion) whilst still putting the site, and the community, on a stable footing. We'd still be lacking people to step up and do the work (either in terms of leg work [e.g. stabilisation branches and management on CSSU, sys admin tasks] or "softer" tasks like the Council and Talk moderation), but it solves the funding "crisis" without expecting an unrealistic level of work from volunteers running an NFP.
How to request a MeeGo QA meeting
MeeGo's QA team has occasionally been accused of a lack of transparency; with major changes to Bugzilla being discussed on meego-qa before being rolled out to - and impacting - the whole project. The team is moving to having meetings scheduled on an as-needed basis, rather than regularly: Whenever we get proposed topics, a meeting will be scheduled at 07:00 UTC the coming Tuesday, the same time slot as before. Pls. kindly note that you'd better propose topics 24 hours before the meeting (7:00 UTC Monday), so that we get enough time to prepare and notify people. This is the same model being followed by the project leadership, with TSG meetings now being held when required; primarily to rubberstamp nominations from other teams.
Managing MeeGo "core" and community OBS
There has been more communication between the MeeGo Release Engineering and the MeeGo Information Technology teams about how to best fix the recent downtime that has been experienced with COBS, and how best to avoid it happening again. In this thread on the MeeGo IT mailing list Ryan Ware from release engineering states: We have a very good understanding of what the technical issues are that have been causing the downtime. We are working to resolve the issue. Hopefully we will have a resolution to this problem soon, and hopefully RE and IT will be able to work closely in the future to prevent such things from happening.
Karma calculation bug with Talk accounts?
With the upcoming elections, it is as important as ever that karma - the overall metric for an individual's contribution to the community - is accurate; however Piotr Jawidzyk seems to not have his posts and "thanks" at talk.maemo.org being included. Hopefully, Henri Bergius will get to the bottom of it quickly.