-Original Message-
From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com]
On Behalf Of ext Jeremiah Foster
Sent: 30 April, 2010 15:25
To: meego-dev List
Subject: Re: [MeeGo-dev] Repository Working Group - next steps
Look at it from the position of the vendor
On Apr 29, 2010, at 5:16 PM, Dave Neary wrote:
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
-Original Message-
From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com]
On Behalf Of ext Jeremiah Foster
Sent: 30 April, 2010 12:08
To: meego-dev List
Subject: Re: [MeeGo-dev] Repository Working Group - next steps
On Apr 29, 2010, at 5:16 PM, Dave Neary wrote
On Apr 30, 2010, at 12:06 PM, tero.k...@nokia.com tero.k...@nokia.com wrote:
On Apr 29, 2010, at 5:16 PM, Dave Neary wrote:
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
Hi,
tero.k...@nokia.com wrote:
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
On Wed, Apr 28, 2010 at 00:27, Spencer, Bob bob.spen...@intel.com 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
Clint Christopher Cañada wrote:
+1 from me. It looks like the best term so far.
On 4/28/2010 1:15 PM, Quim Gil wrote:
ext Graham Cobb wrote:
why don't we call this the Community Repositories Team.
+1
Quim Gil wrote:
understands it. ;) Surrounds is indeed poetic but
We
What's in a name?
Shaver, Michael R wrote:
On 4/28/10 1:39 AM, Andrew Flegg and...@bleb.org wrote:
On Wed, Apr 28, 2010 at 00:27, Spencer, Bob bob.spen...@intel.com
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
Hi,
ext David Greaves wrote:
quim@nokia.com wrote:
Hi,
I think we have a mismatch between the name and the content. How to
call this? Names carried from maemo.org or moblin.org would be
Downloads, Extras or Garage. Apps, Addons, Catalog are
also used in similar contexts. None of them
Quim Gil wrote:
Hi,
ext David Greaves wrote:
quim@nokia.com wrote:
Hi,
I think we have a mismatch between the name and the content. How to
call this? Names carried from maemo.org or moblin.org would be
Downloads, Extras or Garage. Apps, Addons, Catalog are
also used in similar
On 27 Apr 2010, at 17:04, David Greaves wrote:
Quim Gil wrote:
Hi,
ext David Greaves wrote:
quim@nokia.com wrote:
Hi,
I think we have a mismatch between the name and the content. How to
call this? Names carried from maemo.org or moblin.org would be
Downloads, Extras or Garage.
Let me insist on Downloads, then. :)
well, sure.
But it feels to me that that would be like calling the Community Working Group
Forums.
And we both know that there's a lot more to it than that :)
Obviously we (well, the CWG probably) will need to find some branding for the
services
On Tuesday 27 April 2010 17:59:16 Shaver, Michael R wrote:
I think coming up with the overall name will inform how we name the various
processes and components that make up this. An example would be if the
overall name to end users was called Extras, then for the developer
uploading their
ext Graham Cobb wrote:
why don't we call this the Community Repositories Team.
+1
Being picky someone still could say that since all MeeGo is community
all repos are community repos. Still, most people do understand that one
thing are the repos of software officially supported making a MeeGo
On Apr 20, 2010, at 12:24 AM, David Greaves wrote:
So is this area managed by the core project?
How can it be? MeeGo core is a distro, not an app-store or sourceforge. It has
no policies or processes for handling non-affiliated applications. There isn't
even community access to the core
2010/4/20 Jeremiah Foster jeremiah.fos...@pelagicore.com:
If there is no access to the build system, MeeGo is effectively closed.
There is open bug for this: http://bugzilla.meego.com/show_bug.cgi?id=615
--
Marko
___
MeeGo-dev mailing list
16 matches
Mail list logo
