> -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of ext Spencer, Bob > Sent: 29 April, 2010 04:59 > To: Shaver, Michael R; [email protected] > Subject: Re: [MeeGo-dev] Repository Working Group - next steps > > "What's in a name?"
Let's _not_ call it a rose. > Shaver, Michael R wrote: > >> On 4/28/10 1:39 AM, "Andrew Flegg" <[email protected]> wrote: > >> On Wed, Apr 28, 2010 at 00:27, Spencer, Bob <[email protected]> > >> wrote: > >>> > >>> My ears were burning and now I know why. I've read through the > >>> thread and picked here to jump in for a few comments below. > >> > >> Great to see you here, Bob. > >> > >>> Here's some more stuff to throw into the discussion. We've been > >>> focusing on the netbook "garage" client with the hopes that > >>> governance would be clear on how to proceed with process. > >> > >> I assume "garage client" is equivalent to aptitude/Hildon > >> Application Manager/...? > > That is the intent. Just much better, simpler and more user friendly :) > >> > >> Can I request that we DON'T call the gateway to community downloads > >> "Garage"? > Yes. "Garage" was picked because I spent 0 time thinking about the > name and > started working on a client to be ready for our release (and it takes > time to empower a viable, responsible, "Community Repository Team") > The current name of the app is "MeeGo Garage" and can be changed. > > >> > >> * "Garage" doesn't make me think of car showrooms, it makes > >> me think of mechanics. This gives an overly technical > >> impression to what will be a source of very high quality > >> software. > >> > >> * "Garage" has a strong, and long-lived, meaning in the > >> Maemo community as site providing GForge/Sourceforge-style > >> facilities for the building and management of projects, > >> rather than the distribution of them. > >> > >> * "Garage" was a term used by Moblin. Adopting it without > >> further discussion for MeeGo would seem like once again > >> Intel is reusing labels from Moblin directly on MeeGo, > >> seemingly short-changing the Maemo community. > > Only "seemingly". Let's get a name we all like. The app name can be > changed with the first meego update when we hook it up to the real > repos this team sets up. It is currently pointing to the MeeGo > "extras" > repo to provide a starting point for our efforts. > > I do think the name could imply experimental or unpolished. I assume > the high-quality, professional apps would be put into AppUp, which can > also have open source apps. 2c. Or anywhere the author wants. But we also need the process and mechanisms to ensure that the community apps are of good quality. The apps are one of the calling cards of the community. Also some process to ensure that the people building on the community OBS do not hog the system or try to do otherwise bad things in there. > Bob > > > I tend to agree that calling community downloads "Garage" probably > > isn't the best. As Andrew states, it doesn't have the best > > connotation and doesn't describe the quality of the software > > available. I agree also we have mixed meaning in both the Moblin and > > Maemo communities. > > > > I would take this a step further though and not create additional > > names for the related activities around community downloads. The > > Maemo Garage is an example of this. Although the Maemo Garage is > > directly related to community downloads, it's hard to tell from a > > naming perspective. Even though the management and building of > > projects is targeting a different user base, it should all clearly > > related to the final destination; ie. community downloads. I completely agree on this point. What we need is a solution from the app developers SDK to the end users device. Call it something. But as far as I can see everyone around here agrees on the concept: community applications built and shared through community infrastructure, a full end to end solution. I just want the bits and pieces in place. All the needed little things won't appear overnight but we can make a sensible start and add on to that. > > Because we may still need some distinction between app store > > downloads, I'm still inclined to name these "Add ons" or "Extras". Maybe think of the name from the end-user perspective? Those people will see different stores and then this community place. How to make it obvious to a user that this place caters community built open applications. I.e. it is not a store, but you can get useful things from there. "Community apps" ? Tero > > Mike > > > >> Thanks in advance, > >> > >> Andrew > >> > >> -- > >> Andrew Flegg -- mailto:[email protected] | http://www.bleb.org/ > >> Maemo Community Council chair > >> _______________________________________________ > >> MeeGo-dev mailing list > >> [email protected] > >> http://lists.meego.com/listinfo/meego-dev > >> > > > > _______________________________________________ > > MeeGo-dev mailing list > > [email protected] > > http://lists.meego.com/listinfo/meego-dev > > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
