|
2010-02-24
, 07:59
|
Posts: 434 |
Thanked: 325 times |
Joined on Sep 2009
|
#162
|
Discussion and support about official and community supported developer tools.
|
2010-02-24
, 08:38
|
|
Posts: 3,105 |
Thanked: 11,088 times |
Joined on Jul 2007
@ Mountain View (CA, USA)
|
#163
|
|
2010-02-24
, 09:04
|
Posts: 220 |
Thanked: 129 times |
Joined on Nov 2009
|
#164
|
However, how much can we do to prevent that? Why device vendors, operators and private businesses would act differently with MeeGo?
|
2010-02-24
, 09:19
|
Posts: 220 |
Thanked: 129 times |
Joined on Nov 2009
|
#165
|
If we agree with the idea of starting from scratch, then we can agree also with the idea of starting new subforums based on real needs at the time.
Imagine we would start today. The setting could be:
- General
- Community (substituting the mailing list?)
- Development
More on request. If such requests would come with a concrete purpose, scope and 2 moderators identified then such forum could start soon and grow fast.
The limits would not be put by a predefined scope but on real interest coming with real commitment to keep some quality standards.
Under this premise we could be proactive with Nokia, LG and whoever else shipping MeeGo devices to see if they are happy getting related forums under this umbrella. Ideally they would provide the moderators or people acting as gateways with their own organizations.
|
2010-02-24
, 09:51
|
|
Posts: 2,121 |
Thanked: 1,540 times |
Joined on Mar 2008
@ Oxford, UK
|
#166
|
Do you mean what I would call a "sub-forum" (forum within a forum) for each device, rather than a forum per device on a separate server?
The Following User Says Thank You to pelago For This Useful Post: | ||
|
2010-02-24
, 11:28
|
|
Posts: 103 |
Thanked: 20 times |
Joined on Jan 2008
|
#167
|
|
2010-02-24
, 12:13
|
Posts: 92 |
Thanked: 127 times |
Joined on Oct 2009
@ Italy
|
#168
|
If we agree with the idea of starting from scratch, then we can agree also with the idea of starting new subforums based on real needs at the time.
Imagine we would start today. The setting could be:
- General
- Community (substituting the mailing list?)
- Development
|
2010-02-24
, 13:16
|
|
Posts: 1,309 |
Thanked: 1,187 times |
Joined on Nov 2008
|
#169
|
What matters is the people, and there is nothing stopping anybody from registering at meego.com. If someone here is not intersted personally about doing this step, then why bother about organizing complex user/content migrations.
MeeGo is a new community project and it makes total sense that the new community members step in by their own feet. Nobody has made a big fuzz about registering to the mailing lists and we have some already, being active and useful.
The Following User Says Thank You to volt For This Useful Post: | ||
|
2010-02-24
, 13:26
|
Posts: 14 |
Thanked: 18 times |
Joined on Jan 2010
|
#170
|
Tags |
forum, maemo.org, meego |
Thread Tools | |
|
With regards to the user part of the forum, I think Texrat made an excellent point (#155). I still think we need to consider the purpose of talk.meego (in particular the end-user section), what it aims to do. For example, thinking out loud, we could remove ‘end user tech support’ role from the equation and instead consider the user section of the forum as (i) feedback and testing from users (ii) a vehicle to push advancements made in the development section to the community of power users (iii) a resource for hackers/developers to interact with a community of power users. This would provide a symbiotic relationship between hardcore developers and a manageable community of power users, and would provide a concrete and tangible benefit to the project. At the same time, the scope of the forum can be more clearly defined (as in, it concentrates on the meego platform, as opposed to ‘everything meego’ which would encompass support of individual meego devices). This would minimise the noise from novice users’ questions and wouldn’t require the massive forum structure which might otherwise be needed for ‘all devices, all users’. For tech support, manufacturers ought to take on the responsibility, as they are widely expected to and probably prepared to do (for example, if your average consumer has a problem with the software on their new symbian phone, they will seek advice from the network or manufacturer of the handset, they are unlikely to go and track down symbian and post something to the developer community. Maybe this is technically the correct course of action if it is a problem with Symbian, but it is not done because this doesn’t make sense to the user!). This is where I think meego forums shouldn’t become the next tmo, and should serve a different purpose from the off.
Like I said anyway, this is all just thinking out loud and I’m very much expecting large holes to be found in my logic!
Edit: my bad! I'm a bit behind, having only just caught up with the meego-community mailing list. Sorry some of whats above isn't really necessary! Anyone not familiar can catch up here
Last edited by happyblob; 2010-02-24 at 05:34.