[prev in list] [next in list] [prev in thread] [next in thread] 

List:       meego-community
Subject:    [Meego-community] meego.com target audience
From:       amby () ovi ! com (Amby)
Date:       2010-02-24 10:49:40
Message-ID: 886EF52C-2570-4035-957F-E9C9F0E48185 () ovi ! com
[Download RAW message or body]

Hello everyone,

coming from Maemo background, the only thing which I was missing is good catering for \
                end-users, so for me MeeGo does have 4 target audiences:
- end-users (newcomers, power users)
- community (community members, contributors, council)
- developers
- builders (vendors, hobbyist) [new with MeeGo]

I differentiate only these 4 on the highest level due to their different interest in \
                coming to MeeGo:
E: use, get answers (Q&A, FAQ), learn
C: discuss, contribute
D: develop, distribute
B: build MeeGo devices

I think the high noise ratio on TMO is due to the fact, that there is no focused \
attempt to serve end-users for their typical need. TMO itself was a step to provide a \
place for community besides developers. My opinion is that there is no need to \
drastically change what has evolved previously - just add end-user focus and builder \
focus.

This being said, separation can be only a technical detail: filtering options to only \
look at developer or vendor/device specific forums/news/actions/bugs/brainstorms, \
different portal pages.

Let me know what you think,

Amby

Ps.: I cannot really decide on audiences, like testers, localization - I would \
                include them under community contributors.
Ps2.: I've drafted a Milestones page based on my assumptions above - without the \
audiences definition and objectives of MeeGo, I would find it a futile attempt to do \
prioritization in community tasks. http://wiki.meego.com/MeeGo_Milestones

On Feb 23, 2010, at 2:23 PM, Jeremiah Foster wrote:

> 
> On Feb 23, 2010, at 1:48 PM, David Greaves wrote:
> 
> > On Tue, 2010-02-23 at 13:26 +0200, Quim Gil wrote:
> > > > The harder question, in my mind, is what about developers of apps that need 
> > > > something that is not in MeeGo?  But that is really part of my other thread.
> > > 
> > > Like what?
> > I think this relates to the vast number of 'trivially' obtainable
> > solutions that make linux an integration oriented place rather than a
> > re-invention oriented place.
> 
> Precisely. And this is where the business case lies as well - cost of development \
> just dropped by an order of magnitude if you don't have to write new software.
> > 
> > So all the Python/perl libs, maybe things like nfs/samba.
> 
> If one looks at Popcorn Hour for example, I would think MeeGo would fit really well \
> there. Popcorn Hour is a "embedded linux" black box that adds support for every \
> media format imaginable. MeeGo could easily do this and come up with a better \
> interface, or perhaps just a way to input your IP address on something other that a \
> infrared remote control.
> > 
> > As much as anything we need MeeGo to not stifle innovation; we can't say
> > "oh, our users will never want/need to do that..."
> 
> MeeGo aims to serve _lots_ of devices and more than one architecture. Isn't that \
> the idea? 
> Jeremiah
> _______________________________________________
> Meego-community mailing list
> Meego-community at meego.com
> http://lists.meego.com/listinfo/meego-community


--------------------------------------------------------------
Ovi Mail: Create an account directly from your phone
http://mail.ovi.com


[prev in list] [next in list] [prev in thread] [next in thread]