Meego Wiki
Views

Proposal for a User Experience working group

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
m (→Area)
(→How to contribute)
Line 9: Line 9:
=== How to contribute ===
=== How to contribute ===
-
Please expand.
+
This project needs people with the following experience:
 +
 
 +
* RPM packaging (especially extending XML metadata)
 +
* Bugzilla API
 +
* Paypal API
 +
* Obopay API
 +
* Qt
 +
 
 +
Feel free to add to this if you see a need.
=== Mission ===
=== Mission ===

Revision as of 14:53, 24 March 2010

The role of MeeGo working groups are explained at http://meego.com/about/governance

This is a request to the Technical Steering Group to approve the creation of a Development working group. There is no procedure defined but we can can improvise with some common sense.

Contents

Announcement

None

How to contribute

This project needs people with the following experience:

  • RPM packaging (especially extending XML metadata)
  • Bugzilla API
  • Paypal API
  • Obopay API
  • Qt

Feel free to add to this if you see a need.

Mission

Develop a comprehensive solution that makes bugs reporting, applications rating and developer donations easier on end-users and puts user experience capturing (feedback) in more appropriate locations and contexts.

MeeGo User Experience Framework: Capturing, enhancing and leveraging the MeeGo device user experience.

Area

The main areas within the scope of the working group are (in no particular order):

  • 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.
  • Feedback / Rating : Provide end-users with an operating system and applications integrated solution.
  • 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 Community working group will be necessary on certain points.
  • Gaming achievement : Create a proper achievement system.
  • Infrastructure : Add/use necessary “hooks” (APIs, metadata) to the current infrastructures (Ovi Store / Intel App Store).

Rationale

Currently, bug reporting is difficult for end-users, testing is too ad hoc (specific) and ratings systems are not fully utilized. Support for donation-ware and gaming achievements is totally missing.

Materials

  • Presentation (Draft)
  • As a starting point, ABRT 1.0 is an implemented (Fedora 12) and tested tool to help end-users with bug reporting.
  • Monetary donations to an open source software platform (Research Policy Volume 38, Issue 2, March 2009, Pages 404-414) [1]

Contributors

Coordinator of this working group:

  • Randall Arnold/Texrat - Maemo Community Council member, former Nokia QA engineer for Maemo devices, Data Analyst and best practices blogger.

Meego members interested in taking an active role in this working group:

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