The in-development Maemo 5 Community SSU
 

Where the hell is this documented?

Edit, a month later: Here, apparently.

Support this plan if you'd like to see this development done in public, as opposed to some arcane IRC channel at random times.

Re: Ask the Council!
 

Given the Community SSU hasn't been launched yet, nowhere except a few news articles (personally, I suggest <plug>MWKN</plug>).

I assure you, when it's ready, it'll be announced to the world.

Re: Ask the Council!
 

Sweet. A "community" ssu that will get "announced" instead of developed by the community. I assume MohammedAG's work will be included, but what else is there that warrants an SSU? Maybe we can get an update that removes all the links to defunct Ovi services?

Re: Ask the Council!
 

I'm confused by your antagonism, which seems to be driven from a lack of information. (Although you seem to be arguing that the SSU is necessary, but also unnecessary within two sentences).

Firstly, it is being developed by the community; specifically MohammadAG and a few others. It's being openly discussed on IRC, and has been mentioned and discussed both in TMO and MWKN.

What is included, at the moment, is (OTTOMH):

• Updated hildon-desktop, hildon-home
• Modest updated to the trunk, and community patches which have been languishing on Bugzilla integrated
• PulseAudio fixes

However, most importantly, it provides a mechanism to deliver enhancements to the numerous open source components by the community, including Nokia engineers who are no longer working on them as part of their day job.

This mechanism is more important than the first tranche of fixes.

I don't know what services you're talking about; but create such a package and either users can install it via Extras or it can be installed via the SSU. However, the scope of an SSU is to update the OS components - updating HAM or hildon-desktop via Extras is problematic.

So, for example, the CSSU shouldn't contain fMMS, despite it being massively useful & popular, because it can be trivially installed from Extras.

Re: Ask the Council!
 

stenny,

do you happen to know *specifically* which web links are working/not working and where they are stored (package as well as file location)
so that this information could be put nto the SSU?

Re: Ask the Council!
 

IRC is hardly an open discussion. Is there at least a public log of the channel somewhere?

Re: Ask the Council!
 

only because you don't visit a restaurant doesn't mean it isn't open to the public.

logs are here:
https://wiki.maemo.org/IRC#Logs

Re: Ask the Council!
 

If a restaurant is open for one hour every week, but they don't say which hour, it is hardly public.

Can you point to another distribution where the main discussion and decision making is on IRC?

And of all those channels, where is "community SSU" discussed?

Can you point me to the discussion that resulted in hildon-desktop changes included in SSU? Was inclusion of kernel-power discussed?

Re: Ask the Council!
 

As I said above, at the moment the mechanism of having an SSU managed by the community is more important than the first testing release's content. As I also said, the processes around the SSU are still being formed, and will be discussed when the idea is proven to actually work.

Mohammad integrated patches and created a repo. It's been discussed in the hildon-desktop patch thread, the Modest patch thread, on maemo-developers with regards to getting HAM to recognise the repository as authorised and on maemo-community for some initial very-high level testing and feedback.

The conduit I set up to publicise potential avenues for exploration has covered it (1, 2, 3, 4, 5, 6); so I'm not going to get drawn into another debate about the visibility of pieces of information to individuals who may have missed it.

Nor do I think a debate on the support the Council is giving to an individual (and now small team)'s efforts is appropriate or useful. If you have your own effort that you'd like the Council to support, please get in touch.

Re: Ask the Council!
 

Is a patched kernel going to be included to fix the CPU speed bug when charging?