Meego Wiki
Views

Architecture/MeeGo FRAME Resource

From MeeGo wiki
< Architecture
Revision as of 19:57, 6 March 2011 by Tswindell (Talk | contribs)
Jump to: navigation, search

We support development of a comprehensive solution or solutions that makes bug reporting, applications testing and developer donations easier on end-users, and places the mobile user experience (feedback) in more useful locations and contexts (rating items of interest, gaming achievements, etc on-the-go).

Contents

Introduction

Think of this as a meta-project. We are the research arm, pipeline and clearinghouse for all things feedback-related. Maybe umbrella is a better term. The hope is that we will identify key areas of a mobilized feedback ecosystem, perform landscape and gap analysis, then list needs for tasks and/or sub-projects. Ultimately, we hope that our research will stimulate real development projects. Consider us one of your resources!

So why do we need an open, mobilized feedback ecosystem?

  • A mobile Internet is the future (per recent Gartner study)
  • We (users) want to be fully engaged in Internet activities
  • We (users) are more interested in the opinions of friends than strangers (ratings context)
  • Walled garden social networks will stifle the free flow of information and cripple discovery opportunities
  • Feedback enables developers to provide better products and services than their competitors

Project's scope

The main areas addressed by the project are (in no particular order):

  • Infrastructure : Add/use necessary “hooks” (APIs, metadata) to the current infrastructures (Ovi Store / Intel App Store).
  • Bug reporting : Provide end-users with a device-based wizard that walks them through the process, and also automate log file submission. Discussion with the Quality Assurance working group will be necessary.
Here is what MeeGo 1.0 currently presents on bootup:
Backtrace Collection
Automatically submit application crash reports to MeeGo reporting database?
  • Yes
  • No
PRIVACY NOTE:
Enabling this option causes your system to submit certain application output to the crashdb.meego.com website, which then allows the information to be viewed by developers and end users.
The information submitted includes a "backtrace", which is an application's crash signature. However, due to the nature of backtraces, it may happen that a few instances of user input will be sent with the backtrace.
  • Developer donation : Educate end-users on the vital role played by developers in creating an ecosystem and provide them an easy and trusted way to make donations. Discussion with the relevant Community working group will be necessary on certain points.
  • Feedback / Rating : Provide end-users with an operating system and applications integrated solution for items of interest:
    • Media (Videos, Images, Music, Podcasting, eBooks, Websites, etc)
    • Applications (Utilities, Games, etc)
    • Events (Concerts, Movies, Conferences, etc)
    • Services
    • Location-based feedback (point-of-interest identification and ratings)
    • Improvement of documentation
  • Gaming achievement : Create and promote a proper achievement system (possible strategy with Ovi?).
  • Karma : Push the concept of karma (personal recognition) up and out (note: this is highly controversial and will likely have low priority).
  • Open Social Networking (eg, Diaspora*)
  • Augmented reality

Note: there may very well end up being separate projects wrapped around any or all of the above topics.

How to contribute

We are currently looking for the following:

  • whitepapers/studies on ratings systems, especially those touching on media ratings, points of interest ratings, psychology of participants, science behind such systems and current open source solutions. Also, any studies showing the value of ratings systems in search (internet mostly) would be VERY helpful!
  • usage of metadata in audio, video, podcasting, image and gaming ratings systems
  • pointers to existing projects that are already doing what we propose!

We also need help turning the theoretical into the practical! Before anything material can be done, the landscape needs assessing. Ready to help shape this project? Then--

  • Identify an area that interests you
  • Research the subject matter. Try to find existing best practices, preferrably open source BUT it can also help to point out successful endeavors in closed source that have no open equivalent (challenge the community!). Independent studies and academic papers can also be very helpful.
  • Synthesize your findings, and update where appropriate (see below)

Communicate your thoughts! Don't be shy!

This project needs people with the following experience or interests (in no particular order):

  • Audio metadata (id3v2)
  • RPM packaging (especially extending XML metadata)
  • Bugzilla API
  • Online payment API(s) (Paypal, Obopay, Flattr, et al)
  • Qt
  • Feedback and/or Usability science
  • Media ratings systems
  • Social Media
  • Gaming ecosystems (especially in an open, mobile context such as Gluon provides)
  • Augmented reality (it's coming!)

Feel free to add to this if you see a missing need. We could especially use help with implementation details (libraries, functions, services, etc) as well as simulations and actual applications.

Related projects and resources

(Original project page).

Contributors

Coordinators of this project (co-coordinators welcome):

MeeGo members interested in taking an active role on the project team:

Retrieved from "http://wiki.meego.com/Architecture/MeeGo_FRAME_Resource"
Personal tools