Proposal for a User Experience working group

Revision as of 05:22, 29 April 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.

Announcement

As noted in the Discussion section, there will be some changes to this effort:

• Redefining. This is not a working group but rather, a project that crosses various working groups and functional areas.

• Renaming. First inclination is to go with MeeGo User Engagement Framework Project, but suggestions are welcome. Given that this could go beyond just MeeGo, it might make sense to create a hierarchal nomenclature that starts general (Linux User Engagement Framework) and drills down to Mobile, then MeeGo. Of course in that case the focus here would be largely on MeeGo.

• Relocating. Based on the above, I will need to create a new wiki page and deprecate this one.

We are still looking for more help, also! --Texrat 05:14, 29 April 2010 (UTC)

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 Engagement Framework: Capturing, enhancing and leveraging the MeeGo device user experience. (renamed) --Texrat 03:12, 23 April 2010 (UTC)

Areas

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.
• Karma : Push the concept of karma (personal recognition) up and out.
• 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)
• Akademy 2010 whitepaper (editable by community)
• As a starting point, ABRT 1.0 is an implemented (Fedora 12) and tested tool to help end-users with bug reporting.
• Ubuntu Software Center is an ongoing effort to aggregate software management (aimed at a better end-user experience) such as application rating/reviews, categorized applications list and application information. The link is full of ideas.
• Monetary donations to an open source software platform (Research Policy Volume 38, Issue 2, March 2009, Pages 404-414) [1]
• KDE's Project Silk may be relevant. We will be reaching out to the team to discover possible synergies.

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:

• Jean-Philipe Morin/Mandor - Maemo5/Ubuntu/Debian user and part time wiki editor.
• Tim Samoff/timsamoff
• Nicola De Filippo - Maemo5 Qt4 contributor; technical skills: Qt (from 1997), C++, Javascript, Php, Java, Python