[MeeGo-community] Extras and Garage need an agreed name
david at dgreaves.com
Thu Dec 9 02:13:19 PST 2010
On 09/12/10 09:24, Brendan Le Foll wrote:
> On 9 December 2010 10:18,<tero.kojo at nokia.com> wrote:
>> David, I keep telling you to keep it simple :) (and to be honest, most of
>> the time you do follow that advice) As I commented on the bug mentioned
>> above, 'Apps' is simple and tells what the thing is about.
>> So anyone in strong opposition of calling the thing and place where you get
>> community built applications to your device 'Apps' should raise their
Well, I posted the bug and then I posted a link here expecting the discussion to
happen amongst the wider audience on the mailing list - hence the suggestion :)
The issue I wanted to avoid was for Nokia or Intel "telling" the community what
to call it.
The 'task force' idea is simply a way of visibly putting this decision under the
CO and ensuring it is *seen* to be a community decision.
Does it warrant a group of people spending time on it? I don't know. I'm not
sufficiently worried about the name that I'd volunteer. Some people care more
about our marketing and have stronger opinions.
I would like the discussion to happen - even if it's only to address questions
> But then what happens when I want to put shared libraries there? Or a package
> for a new login manager or bootloader. It's not exactly an 'App'. I liked
> garage - made it seem a little dirty - but I don't really care garage/extras
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.
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).
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 breath).
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
More information about the MeeGo-community