Meego Wiki
Views

Talk:Proposal for a User Experience working group

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(Title of this working group)
 
(3 intermediate revisions not shown)
Line 4: Line 4:
: It depends on the mission of this working group.  "Develop a solution" or "Develop a solution and Educate end-user on why they should use said solution".  Educate end-user on why it is important to report bugs, why they should care about developers donation, etc ...  Either you leave the education part to the Community working group and steer this working group at the development part -or- you aim for both and change the title to what you suggested.  Might be a good idea to ask the Community working group is they feel end-user education is within their scope ? --[[User:Mandor|Mandor]] 16:22, 25 March 2010 (UTC)
: It depends on the mission of this working group.  "Develop a solution" or "Develop a solution and Educate end-user on why they should use said solution".  Educate end-user on why it is important to report bugs, why they should care about developers donation, etc ...  Either you leave the education part to the Community working group and steer this working group at the development part -or- you aim for both and change the title to what you suggested.  Might be a good idea to ask the Community working group is they feel end-user education is within their scope ? --[[User:Mandor|Mandor]] 16:22, 25 March 2010 (UTC)
 +
 +
:: I am reading the March 24 [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-03-24-19.58.html meeting minutes].  I few things that has been said we should be aware of : "[Working groups] should be more about the governance. Technical work should be done in the projects".  I suspect that the proposal for a User Experience working group will be rejected as it stands right now.  Following my previous comment, "Develop a solution" should not be in this working group mandate, as it might be considered technical work, but "Educate end-user" should be.  I guess we are welcome the propose technical solutions nonetheless.  --[[User:Mandor|Mandor]] 12:46, 26 March 2010 (UTC)
 +
 +
::: I discussed this with Quim Gil recently and there is interest but I think we need to develop it further before we can see traction.  I am touching base with KDE Project Silk folks to see if we can plug into their work.  No matter what, though, I intend to rename this and am leaning toward User Engagement as a more accurate description.  Also note that as of today I still cannot send anything to the email lists. --[[User:Texrat|Texrat]] 16:12, 21 April 2010 (UTC)
 +
 +
I should have noted in the previous comment: in the discussion with Quim, it became obvious this was not really a working group issue but one of a project... especially since it potentially spans multiple groups and areas.  I am in the process of submitting a white paper to Akademy 2010 on this and will later refactor this effort as a project. --[[User:Texrat|Texrat]]

Latest revision as of 16:57, 26 April 2010

Title of this working group

I'm starting to think that User Engagement Framework makes more sense as a title-- thoughts welcome. --Texrat 14:51, 25 March 2010 (UTC)

It depends on the mission of this working group. "Develop a solution" or "Develop a solution and Educate end-user on why they should use said solution". Educate end-user on why it is important to report bugs, why they should care about developers donation, etc ... Either you leave the education part to the Community working group and steer this working group at the development part -or- you aim for both and change the title to what you suggested. Might be a good idea to ask the Community working group is they feel end-user education is within their scope ? --Mandor 16:22, 25 March 2010 (UTC)
I am reading the March 24 meeting minutes. I few things that has been said we should be aware of : "[Working groups] should be more about the governance. Technical work should be done in the projects". I suspect that the proposal for a User Experience working group will be rejected as it stands right now. Following my previous comment, "Develop a solution" should not be in this working group mandate, as it might be considered technical work, but "Educate end-user" should be. I guess we are welcome the propose technical solutions nonetheless. --Mandor 12:46, 26 March 2010 (UTC)
I discussed this with Quim Gil recently and there is interest but I think we need to develop it further before we can see traction. I am touching base with KDE Project Silk folks to see if we can plug into their work. No matter what, though, I intend to rename this and am leaning toward User Engagement as a more accurate description. Also note that as of today I still cannot send anything to the email lists. --Texrat 16:12, 21 April 2010 (UTC)

I should have noted in the previous comment: in the discussion with Quim, it became obvious this was not really a working group issue but one of a project... especially since it potentially spans multiple groups and areas. I am in the process of submitting a white paper to Akademy 2010 on this and will later refactor this effort as a project. --Texrat

Personal tools