|
|
| (5 intermediate revisions not shown) |
| Line 1: |
Line 1: |
| - | The role of MeeGo working groups are explained at http://meego.com/about/governance
| + | Refactored as a project. [http://wiki.meego.com/MeeGo_User_Engagement_Framework_Project New project location] |
| | | | |
| - | 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.
| + | All content except discussion relocated |
| - | | + | |
| - | === 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! --[[User:Texrat|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) --[[User:Texrat|Texrat]] 03:12, 23 April 2010 (UTC)
| + | |
| - | | + | |
| - | === 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 [http://wiki.meego.com/Proposal_for_a_Quality_Assurance_working_group 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 [http://wiki.meego.com/Proposal_for_a_Community_working_group 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 ===
| + | |
| - | | + | |
| - | * [http://maemo-daemons.org/MeeGo_User_Experience_Framework.pdf Presentation (Draft)]
| + | |
| - | * As a starting point, [http://fedoraproject.org/wiki/Features/ABRTF12 ABRT 1.0] is an implemented (Fedora 12) and tested tool to help end-users with bug reporting.
| + | |
| - | * [https://wiki.ubuntu.com/SoftwareCenter Ubuntu Sofware 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) [http://www.sciencedirect.com/science?_ob=ArticleURL&_udi=B6V77-4V6YSW1-1&_user=10&_coverDate=03%2F31%2F2009&_rdoc=1&_fmt=high&_orig=search&_sort=d&_docanchor=&view=c&_searchStrId=1263842519&_rerunOrigin=google&_acct=C000050221&_version=1&_urlVersion=0&_userid=10&md5=27ae17462f87e0f72bc504566073f846]
| + | |
| - | * KDE's [http://lwn.net/Articles/353630/ Project Silk] may be relevant. We will be reaching out to the team to discover possible synergies.
| + | |
| - | | + | |
| - | === Contributors ===
| + | |
| - | | + | |
| - | Coordinator of this working group:
| + | |
| - | | + | |
| - | * [http://meego.com/users/texrat 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:
| + | |
| - | | + | |
| - | * [http://meego.com/users/mandor Jean-Philipe Morin/Mandor] - Maemo5/Ubuntu/Debian user and part time wiki editor.
| + | |
| - | * [http://meego.com/users/timsamoff Tim Samoff/timsamoff]
| + | |
| - | * [http://meego.com/users/niqt Nicola De Filippo] - Maemo5 Qt4 contributor; technical skills: Qt (from 1997), C++, Javascript, Php, Java, Python
| + | |