[MeeGo-community] Extras and Garage need an agreed name
Brendan Le Foll
brendan at fridu.org
Thu Dec 9 02:27:47 PST 2010
On 9 December 2010 11:13, David Greaves <david at dgreaves.com> wrote:
> On 09/12/10 09:24, Brendan Le Foll wrote:
>> On 9 December 2010 10:18,<tero.kojo at nokia.com> wrote:
> So I see both an 'app store' like Mameo Extras:
> and a set of libraries called 'Surrounds' that is a little like Universe on
> Ubuntu. We also have personal repositories (which replace Extras:Devel from
> the Maemo days and also should prevent repository fragmentation). Shared
> libraries clearly go in Surrounds but I'd also see typical cli programs in
> there too. I'd hope well designed Apps would simply depend on the cli/libs
> and provide a nice UI.
That sounds good to me. Providing an App area and Package/Surrounds area.
> We then need a policy to handle QA and package naming, ownership, takeover
> etc for all this and we need to understand how this relates to core MeeGo
> and how we support updates without breaking things. (All of which is not
> really dependent on the name).
We should definately keep any of these policies very simple as to
encourage participation. Could they be implemented from OBS? For
example I could submit my package in home:arfoll to Surrounds and then
have a public feedback on my package and then someone would approve
There should probably be a distinction between new packages and
upgrades. Also should there be a policy on using stable upstream in
apps/surrounds for the case of common FOSS apps or would this be done
on a case by case basis?
> I discussed this with a few people at the conference and *really* need to
> write up some of the points raised. Watch this space (but don't hold your
More information about the MeeGo-community