Community SSU/QA

(Move notes to Development)
Line 1: Line 1:
-
Set of notes and action points from the discussions about Community [[Seamless Software Update|SSU]] on #maemo-ssu freenode.
 
-
 
-
Main participants:
 
-
* lcuk
 
-
* MohammadAG
 
-
* Jaffa
 
-
* Venemo
 
-
* lma
 
-
* x-fade
 
-
* rst38h
 
-
* crashanddie
 
-
 
-
and more
 
-
 
-
== Discussion topics ==
 
-
 
-
* finding source locations and identifying GOOD patches
 
-
* submitting potential patches to a central testing source
 
-
* making a new <code>mp-generic*</code> meta package
 
-
* discussing with lma about current N8x0 community SSU problems and workarounds and insight
 
-
* looking into getting the wiki sorted
 
-
** need wiki editor :P
 
-
* looking at how to manage the patchsets
 
-
** we know the N900 Fremantle system works well using git tags
 
-
** the 8x0 patchset currently contains 10 local based quilts
 
-
* we need a gitorious group to cover these ''Done: http://gitorious.org/community-ssu''
 
-
 
-
== Build Sources ==
 
-
 
-
We must gather together and list the main giturl sources and tags used to build from.
 
-
 
-
for instance:
 
-
http://gitorious.org/modest/modest tag 3.4.8
 
-
 
-
This allows us to reproduce builds and get source to the same location we build from.
 
-
 
-
<pre>
 
-
<lcuk> how many packages for n8x0 are you looking at including in an ssu?
 
-
<lcuk> and how have you considered looking at updating the system so far - you said its all manual at the moment
 
-
<lma> I have 10 (source) packages at the moment
 
-
<lcuk> do you mind listing them
 
-
<lma> busybox dnsmasq loudmouth modest osso-pdf-viewer osso-software-version tinymail community-ssu-enabler xorg-server kernel-diablo
 
-
</pre>
 
-
 
-
''This has started at http://gitorious.org/community-ssu, but needs completing with things like Modest.''
 
== Process ==
== Process ==

Revision as of 14:46, 20 January 2011

Process

As started being discussed on talk.maemo.org:

  1. Who ultimately owns the CSSU?
    • Council?
  2. How will included improvements be decided?
    • Will there be an inclusive policy - every improvement that someone is willing to work on will be included - or will there be a gatekeeper that will decide what to include?
    • Is the scope limited to improving packages which are included by Nokia in the OS; or should it grow to include "useful" stuff?
    • Should wholesale replacement of apps (such as Media Player) be done with open source, feature- & UI-compatible versions; if available?
  3. How will testing be organised?
    • Positive
    • Negative
    • Regression
    • Installation from scratch
    • Upgrade from previous version
  4. How will it be advertised?
  5. How will it be supported?
    • Bugzilla
    • IRC?
    • Forum
  6. At what point do bugs get set to RESOLVED FIXED? Such as #3700

Technical

  1. How to work out value of Maemo-Required-Free-Space header in mp-fremantle-community-pr?

Changelog

Main article: Community SSU changelog