Community SSU
Contents |
What is it?
Seamless Software Update (SSU), is the term Nokia used to brand the over-the-air update. Fixes which can't be delivered easily through Extras due to the nature of the packages with conflict of interest.
Community Seamless Software Update (CSSU) has been developed in mind for the maemo community by the maemo community. The packages contained within the CSSU includes fixes for core N900 programs but not programs that exist in other repositories such as extras, extras-testing and/or extras-devel.
More information may be available through in-development Fremantle community SSU
Who is it for?
Long-term: all N900 users/owners.
For now: power-users, developers, Nokia/maemo/meego engineers, testers, documentation writers and those willing to risk a re-flash in order to help.
Installation
0) Make sure you're running PR1.3, Nokia's last official Maemo 5 update. To see if you have PR1.3, go into "Settings > About product", you should see under "Version" it has the numbers beginning with "20.2010.36".
1) Go to http://wiki.maemo.org/Community_SSU using your favourite web-browser on N900.
2) Click on the "Install" arrow next to "Testing"
3) Hildon Application Manager (HAM) will launch and will prompt you a series of messages and warnings. Click continue and let it install all the community package.
4) Once done, close HAM and go into the applications menu. Look for "Community SSU" and launch it. This will then automatically run through a series of scripts to ensure HAM will now be using community repository for updates.
5) HAM will re-open and present a system upgrade called "Maemo 5 Community SSU".
Contributing
Can you write documentation? If so, it'd be great to flesh out the wiki page with installation instructions (to make it easy for users to install without worrying about missing a step or getting it wrong); explain more about the SSU and generally spruce up the wiki page and maintain things like the changelogs etc.
Were you involved in developing Maemo? If so, with Nokia now looking to Harmattan and MeeGo, we'd love to see your itches addressed in the Community SSU (CSSU). Have you always wanted to implement something in hildon-desktop, but Management stood in your way? We'd love to have it!
Have you written a patch for Maemo? Raise a bug and let's get it in the CSSU.
Are you a developer? There are numerous patches floating around for hildon-desktop; but they can't be included in the CSSU until they are configurable (via gconf) and default to off.
Want to test? Not only testing this release, but writing test scripts so that each release of the CSSU can get sanity checked before unleashing it into a "stable" repo for end-users. How do we do it? What should be tested? How is it organised?
Want to organise? There's still lots of process left to organise; hopefully there'll be bugs and features to triage and manage in bugs.maemo.org as well as communication of the testing, releases and end-user readiness of the CSSU.
For more information: contact MohammadAG on #maemo-ssu on FreeNode IRC or council@maemo.org.
Changelog
Main article: Community SSU/Changelog
Changes in the SSU between PR1.3 and various SSU releases.
QA and bugs
Main article: Community SSU/QA
Quality is of paramount importance to the Community SSU. There are, therefore, two repositories: testing and stable. Changes are carefully tested, with an extensive set of tests, before things are made "stable".
If you have found a bug, in either the testing or stable releases, please raise a bug. Getting involved through testing, bug triaging and running of the tests is a good way to get involved; as, of course, is writing documentation!
Development
Main article: Community SSU/Development
The Community SSU is developed and managed through Gitorious. Bugs are tracked in Bugzilla. Collaboration largely happens on IRC. Getting involved through development, bug triaging and managing developers is a good way to get involved.