Community SSU

2011-01-29T17:04:30Z

85.225.133.69: /* Installation */ "Be patient.." added

<div style="float:right">
<imagemap>
Image:ClickToInstall.png|center|thumb|Testing
desc none
default [http://repository.maemo.org/community-testing/community-testing-fremantle.install Install testing]
</imagemap>
</div><div style="float:right">
<imagemap>
Image:ClickToInstallDisabled.png|center|thumb|Stable
desc none
default [[Changelog]]
</imagemap>
</div><div style="float: right">
[[Image:app_install_updates.png]]
</div>

==What is it?==
Seamless Software Update ([[SSU]]), is the term Nokia used to brand the over-the-air updates of Maemo.

Community Seamless Software Update (CSSU) is being developed by the Maemo community, ''for'' the Maemo community. It aims to deliver fixes which can't be delivered easily through Extras, such as core N900 packages. It won't, however, bundle software which can be installed through the Extras repositories.
<br clear="all">

==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==
# Make sure you're running [[Maemo 5/PR1.3|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'''.
# Click on the [http://repository.maemo.org/community-testing/community-testing-fremantle.install Install testing] button above.
# Hildon Application Manager (HAM) will launch and will prompt you a series of messages and warnings. It takes a second for HAM to display the installation progress, be patient. Click continue and let it install all the community package. Have patient,
# 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.
# HAM will re-open and present a system upgrade called ''Maemo 5 Community SSU''. Once installed, your device will reboot.

Problems? Check the [[Community_SSU/Installation_FAQ|Installation FAQ]]

==Contributing==
{| style="background: #e8d8c8; border: 1px solid #666; width: 100%; text-align: center"
| Get involved on [[IRC]] (<code>#maemo-ssu</code>), [http://talk.maemo.org/showthread.php?t=67905 Talk], [https://bugs.maemo.org/buglist.cgi?query_format=advanced&product=Maemo%205%20Community%20SSU&classification=Extras Bugzilla] and [http://gitorious.org/community-ssu Gitorious].
|}

'''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 [[Community_SSU/QA#Test scripts|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 [mailto:council@maemo.org council@maemo.org].

== Changelog ==
{{main|Community SSU/Changelog}}

Changes in the SSU between PR1.3 and various SSU releases.

== QA and bugs ==
{{main|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 [https://bugs.maemo.org/enter_bug.cgi?product=Maemo%205%20Community%20SSU 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|Community SSU/Development}}

The Community SSU is developed and managed through [http://gitorious.org/community-ssu Gitorious]. Bugs are tracked in [https://bugs.maemo.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Maemo%205%20Community%20SSU&classification=Extras Bugzilla]. Collaboration largely [http://mg.pov.lt/maemo-ssu-irclog/ happens on IRC]. Getting involved through development, bug triaging and managing developers is a good way to get involved.

[[Category:Community]]
[[Category:Fremantle]]

GSoC 2010/Projects/Extending Shepherd

2011-01-27T11:10:26Z

85.225.133.69: /* Extending Shepherd - GSoC 2010 Project */ Fixed broken link

== Extending [[Shepherd]] - GSoC 2010 Project ==

*'''Student''': Linus Wallgren ([[User:ecksun|ecksun]]) , email: linus dot wallgren at gmail dot com
*'''Mentor''': Attila Csipa ([[User:achipa|achipa]])
*'''Project Status''': accepted, in development
*'''Repository''':
** http://gitorious.org/~ecksun/shepherd/shepherd-plugins
*'''Status updates''':
**http://ecksun.com/blog/?tag=maemo

===Project summary===
[[Shepherd]] is an advanced scheduler that can do a wide variety of tasks depending on a number of triggers.

The project will aim to improve on the capabilities of Shepherd. I plan to add more ways of triggering an action and more actions to be taken when the triggers is meet.

===Progress===

I have planned to write a couple of plug-ins for shepherd as well as to get the core and GUI in working order.

{| class="wikitable"
|-
! Name
! Progress
! Status
! Category
! Description
|-
|WLAN SSID
|95%
|Real life testing left
|Trigger
|Check if a WLAN SSID is nearby
|-
|Location
|80%
|Real life testing left. A gui is needed however the plan is to use the Qt Mobility location packate for that, which is not yet released.
|Trigger
|Check if the device is in a certain location by using the GPS and Cellular towers
|-
|Calendar
|95%
|Real life testing left
|Trigger
|Check if certain events are happening
|-
|Change profile
|95%
|Real life testing left
|Action
|-
|Turn Radio on/off
|95%
|Real life testing left
|Action
| Turn both WLAN and 3G on/off
|-
|Change Telepathy status
|0%
|Have been unsuccessfull in implementing this, might be a bug in TelepathyQt4.
|Action
|-
|Secure device
|95%
|Real life testing left
|Action
|Lock the device in the same way as the menu option
|-
|Display a notification
|95%
|Real life testing left
|Action
|Display a notification
|-
|Sensors - accelerometer, ambient light sensor, orientation, proximity sensor, rotation sensor.
|95%
|Real life testing left.
|Triggers
|Several triggers involving the sensors
|-
|Sensors (several triggers) - compass, magnetometer, tap sensor
|90%
|Untested as I have no device with these sensors.
|Triggers
|Several triggers involving the sensors.
|-
|Core
|~50%
|
|Shepherd
|Finish the core
|-
|GUI
|5%
|
|Shepherd
|Finish the GUI
|-
|}

The part that is missing from most of the plug-ins is to adopt it to the shepherds current API, the actual functionality is already there.

[[Category:Google Summer of Code]]

Maemo Wiki Mirror - User contributions [en]

Community SSU

GSoC 2010/Projects/Extending Shepherd