Act on findings in usability test reports

GoogleCodeExporter commented 9 years ago

Introduction:
This task doesn't require any coding skills.  Usability sense is important.
 Patience and the ability to communicate and collaborate will be needed. 
There is an opportunity to learn to read and edit code, and create and
apply patches for a willing student.

Context:
There is a lot of work happening in improving usability in drupal.  Some of
this work includes usability tests and reports.  Each of these reports find
many usability bugs.  To keep these bugs from being lost and forgotten, as
the reports move down lists of 'recent topics', it's important to store
them in drupal's issue-tracking system.  Drupal's issue tracking system is
where drupal developers track progress and collectively remember
outstanding issues that need to be resolved.

The Task:
This task will help usability in drupal by turning usability test findings
in to actionable tasks.

How:
 * Locate 1 extensive (or more if they are smaller) usability test
report/s.  (See issues 7 and 8. Also http://groups.drupal.org/node/7043 is
an extensive report).
 * Search thoroughly for existing issue nodes or patches addressing the
issue. http://drupal.org/project/issues/search/drupal
http://www.google.com/search?q=foo&sitesearch=drupal.org/node
 * If none is found, create a new issue node on drupal.org and suggest a
solution to the issue.  http://drupal.org/node/add/project-issue/drupal
 * So that your effort is not duplicated by others, annotate, comment or
otherwise mark the report with a link to the drupal.org issue you found or
created.
 * If the solution has already been discussed and consensus about the
solution has been reached, test and review the most recently submitted
patch. http://drupal.org/patch http://drupal.org/patch/review
 * If no patch has been submitted but solution is trivial, (like changing
help text, or minor tweaks to forms), fix the issue and submit a patch. 
(Opportunity to start learning to read code here!)
http://drupal.org/patch/submit

There is not a lot to do for each issue, but there are many issues in every
usability-test report.  For example, Factory Joe's review has ~50
un-actioned actionable @TODOs, and about 20-30 more actioned issues. 
http://groups.drupal.org/node/7043  http://groups.drupal.org/node/7314 

Deliverable:
The task is complete when all issues raised in the report/s have issue
nodes on drupal.org, and at least one suggested solution, patch, or patch
review.

Skills:
This task will teach you 
 * how to interact with an open source development community
 * how source code and code-related tasks are managed
 * usability sense, guidelines and tips
 * some code editing skills

All of these are very valuable skills and assets to have, especially the
online records of it (for job-searching and university applications).

Estimated time:
4 to 5 days.

Primary Contact:
Bevan Rudge http://drupal.geek.nz http://drupal.org/user/49989

Original issue reported on code.google.com by b.ru...@gmail.com on 29 Nov 2007 at 12:04

GoogleCodeExporter commented 9 years ago

Marking as open task so it can be claimed.

Original comment by webchick...@gmail.com on 2 Dec 2007 at 4:28

Changed state: Open
Added labels: Documentation, UserInterface
Removed labels: Priority-Medium, Type-Defect

GoogleCodeExporter commented 9 years ago

what is the time limit on this task

Original comment by rabidfla...@gmail.com on 2 Dec 2007 at 6:52

GoogleCodeExporter commented 9 years ago

Hi there.  Erm, not sure.  Does there need to be one?  Can you elaborate the 
question
as I'm not sure what you're asking for.  Regards, Bevan/

Original comment by b.ru...@gmail.com on 2 Dec 2007 at 7:05

Added labels: Usability

GoogleCodeExporter commented 9 years ago

I claim this task.

Original comment by marco.ro...@googlemail.com on 2 Dec 2007 at 7:06

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

Great!  Marco, feel free to contact me if you have any questions about this.  
PM me
at http://drupal.org/user/49989 so I can send you my IM details etc.

Sorry rabidflamingo if you wanted to claim this task.  There is currently one 
other
unclaimed Usability task:
http://code.google.com/p/google-highly-open-participation-drupal/issues/list?q=l
abel:Usability

Original comment by b.ru...@gmail.com on 2 Dec 2007 at 7:17

GoogleCodeExporter commented 9 years ago

Say, Marco, I know you've been doing work on this task.. is is possible to 
respond at
http://drupal.org/node/197248 with a list of issues you've created? Also report 
there
how close you think you are to this being done?

No pressure at all -- you still have plenty of time, I just want to make sure 
your
work stays on peoples' radars.

Original comment by webchick...@gmail.com on 5 Dec 2007 at 2:24

Added labels: DrupalIssue-197248

GoogleCodeExporter commented 9 years ago

It came to my attention via b.rudge that marco's sick and will be out for a few 
days.
I'd like to extend this task's deadline until he gets back -- he's already has 
some
great work done on this (even a core patch to fix one of the things he found!), 
so
let's hold off on the "ActionNeeded" status for a bit.

Original comment by webchick...@gmail.com on 6 Dec 2007 at 5:19

GoogleCodeExporter commented 9 years ago

Marco should be back with us next week sometime.  I think he's having/had an
appendectomy, which I believe is a fairly major operation, but I think is quick 
to
recover from.   Here's the chat log from the conversation with his father for 
reference;

    8:27:37 AM Marco (GHOP): Hello Bev! I am the father of marco huenseler. marco is
working with you at the google projekt. i am sorry to tell you that marco is 
very
ill, he is in the hospital because of a hard attack of appendicitis. So he is 
out of
order till monday...Please give him an extra time to close his projekt. Best 
wishes
from marco who is looking forward to the next session for your google projekt!  

    8:28:47 AM Bevan: Hi there
    8:30:14 AM Bevan: I'm very sorry to hear about Marco's illness.  I hope he is
okay and gets well soon.  :s
    8:31:11 AM Bevan: He mentioned to me about 22 hours ago that he wasn't feeling
well but I had no idea!  How is he doing?
    8:32:00 AM Marco (GHOP): In the morning he had hard pain in the stomache area and
so we drove to the hospital
    8:32:24 AM Bevan: Please send him my best wishes to get well soon.  And let him
know that we'll hold his Google HOP task open for him as long as possible.
    8:33:07 AM Marco (GHOP): thank you very much! i will snd him best wishes. i think
he will be happy to hear this...
    8:34:53 AM Bevan: Once he is well he may need to re-evaluate his priorities as he
will have missed some school, I imagine, and need to catch up.  Let him know 
that
it's completely okay to 'drop' the google task if he wants to.
    8:35:43 AM Bevan: Nevertheless I'll do what I can to keep it open for him as long
as possible.  I'm sure we can make an exception to the deadlines given the
circumstances! :)
    8:35:59 AM Bevan: Thank you for letting me know about this.  I (and the drupal
community) appreciate that very much.  

Get well soon Marco!  :)

Original comment by b.ru...@gmail.com on 6 Dec 2007 at 8:00

GoogleCodeExporter commented 9 years ago

Technically, this is due the 9th, but let's make it due the 14th instead 
because of
marco's poor appendix. ;(

Original comment by webchick...@gmail.com on 8 Dec 2007 at 5:09

Added labels: DueDate-2007-12-14

GoogleCodeExporter commented 9 years ago

So if marco doesn't get better by the 14th, we can claim this task? Sorry marco 
:( I hope you get better soon!

Original comment by AriXm...@gmail.com on 11 Dec 2007 at 9:07

GoogleCodeExporter commented 9 years ago

Hi, today's the first day I really feel well enough to continue to work on this 
task,
sorry. Would be really nice if you could extend the time limit a bit, maybe 
three
days more (17th December CET)?

Thank you very much in advance!

Original comment by marco.ro...@googlemail.com on 14 Dec 2007 at 4:49

GoogleCodeExporter commented 9 years ago

Ok, I'll set the due date to the 17th.  If you don't think you'll be able to 
make
significant progress by then, it's probably best that you drop this task and 
then
claim another once you feel better.  There will be plenty available for you 
most likely!

But I'm glad to hear you're feeling better.  Let us know if you have any 
questions or
further problems!

Original comment by acli...@gmail.com on 14 Dec 2007 at 4:58

Added labels: DueDate-2007-12-17
Removed labels: DueDate-2007-12-14

GoogleCodeExporter commented 9 years ago

Glad to hear you are well Marco.  Keep us updated with your progress.  B/

Original comment by b.ru...@gmail.com on 16 Dec 2007 at 2:09

GoogleCodeExporter commented 9 years ago

I think all I can do will be done today or tomorrow. The few who aren't in the 
issue
tracker then weren't understood by myself. I'll have a look in #drupal or
#drupal-ghop these days ;-)

Original comment by marco.ro...@googlemail.com on 17 Dec 2007 at 1:33

GoogleCodeExporter commented 9 years ago

I'm almost finished. I will do the rest tomorrow morning (going to bed now) and 
ask 
bevan tomorrow evening for helping me to finish the rest (12h time difference, 
*doh*).

Original comment by marco.ro...@googlemail.com on 19 Dec 2007 at 12:07

GoogleCodeExporter commented 9 years ago

It would be helpful if you could go ahead and post what you have done so far.  
That
way we can take a look and make sure you are on the right track.  It's OK if 
you are
still working on it and haven't finished yet.

Original comment by acli...@gmail.com on 19 Dec 2007 at 12:12

GoogleCodeExporter commented 9 years ago

Just take a look at the usability report. There should be very few or no Todos 
left
when I'm done. And - I'm almost done...

Original comment by marco.ro...@googlemail.com on 19 Dec 2007 at 11:32

GoogleCodeExporter commented 9 years ago

Hi Marco any progress? Can you upload what you have to the drupal issue
(http://drupal.org/node/197248), even if its not finished? That way the 
community can
help you along.

Original comment by addi.be...@gmail.com on 21 Dec 2007 at 4:38

Changed state: ActionNeeded

GoogleCodeExporter commented 9 years ago

Hi,
I'm done. To see my work, just have a look at 
http://groups.drupal.org/node/7043 .
There are no TODOs left the wireframing ones - this would've been really too 
much
work for one task. You could create another GHOP task for that. To see all 
created
issues for this just search for issues
(http://drupal.org/project/issues/search/drupal) created by me 
(marco.robotangel). I
didn't create any other issues before.

I'm very sorry this took so much longer than planned. I am - or mostly was - a
complete drupal newbie before accepting this task so I had to learn a bit about
drupal first (I guess that's what I did most of the time). I think I learned a 
lot
the last 3 weeks (one week in hospital and a few days I couldn't really work at 
it,
though), so I will continue to read myself in all this stuff and claim another 
task
later :-)

Original comment by marco.ro...@googlemail.com on 21 Dec 2007 at 4:05

GoogleCodeExporter commented 9 years ago

setting status to NeedsReview.

Original comment by acli...@gmail.com on 21 Dec 2007 at 4:38

Changed state: NeedsReview

GoogleCodeExporter commented 9 years ago

I reviewed this issue at http://drupal.org/node/197248

There's a little work that needs to be done before this task is closed, but not 
much.
 Great job so far!

Original comment by acli...@gmail.com on 21 Dec 2007 at 6:18

Changed state: ActionNeeded

GoogleCodeExporter commented 9 years ago

Aclight;  Some of the TODOs I added there were more of a personal note/reminder 
and
are things I will likely be covering as part of the SoU (Season of Usability)
programme.  I asked no Marco not to worry about those ones.

Marco;  There is one more that does need a d.o issue in order to complete this 
GHOP
task; "The actions on this page should be "Save term and add more..." and "Save
term". Going back to the containing vocabulary is not possible without going to
Categories and THEN to the vocabulary... too many clicks!"

Also, I noticed that you haven't created links to the drupal issues for each 
@TODO or
each @DONE.  This is important to ensure that others don't have to duplicate 
your
effort in searching for and/or creating the issue nodes on drupal.org.  Can you
please add in the links?  It also enables someone like me, who has a special 
interest
in these issues to follow up the issues and create/review/submit patches.  
Finding
them by searching can be cumbersome due to the massive number of issues.

Original comment by b.ru...@gmail.com on 21 Dec 2007 at 9:51

GoogleCodeExporter commented 9 years ago

Hi,

I'm sorry, it really seems I forgot this one. Well, I personally didn't just 
"delete"
TODOs without adding issues below, maybe someone else did? I will figure them 
out and
add issue links to them, too. Stay tuned...

Original comment by marco.ro...@googlemail.com on 22 Dec 2007 at 3:02

GoogleCodeExporter commented 9 years ago

Thanks Marco!  It looks to me like you've finished that.  Please confirm so I 
can
mark this as closed.  tks!  :)

Original comment by b.ru...@gmail.com on 23 Dec 2007 at 8:17

GoogleCodeExporter commented 9 years ago

Confirmed this via chat with Marco, closing task

Original comment by b.ru...@gmail.com on 23 Dec 2007 at 8:20

Changed state: Closed

GoogleCodeExporter commented 9 years ago

In order to get credit for this task, please upload your final work to this 
issue.
See the wiki page at
http://code.google.com/p/google-highly-open-participation-drupal/wiki/HowToGetCr
editForYourTask
for more information.

Original comment by acli...@gmail.com on 21 Jan 2008 at 5:25

GoogleCodeExporter commented 9 years ago

We still need to have you upload your final work to this Google task in order 
for you
to receive credit.

Also, if you have not done so already, please read my post at
http://groups.drupal.org/node/8391 to learn about what you *must* do to claim 
your prize.

Original comment by acli...@gmail.com on 29 Jan 2008 at 4:46

GoogleCodeExporter commented 9 years ago

Adam (aclight/admin),

Uploading the work for this task would involve copying and pasting large 
amounts of
text from about 30-50 d.o issue nodes and from Factory Joe's usability report.  
I'm
not sure what else Marco (student) could do to show the work was done and task 
complete.

Bevan/

Original comment by b.ru...@gmail.com on 29 Jan 2008 at 9:05

GoogleCodeExporter commented 9 years ago

@Bevan:  Good point.  Let me check with Google and I'll post the results here. 
Thanks for bringing up this point.

Original comment by acli...@gmail.com on 29 Jan 2008 at 11:08

GoogleCodeExporter commented 9 years ago

Here's the response I got from Google:
Please post the patches to the issue tracker and have the student
enter a comment hyperlinking to the issues in the Drupal tracker that
were the result of work on the task.  That way students in the future
can get a good idea of the work required to complete a task of that
type.

So posting the few (or maybe only 1) patch created in this task should be easy. 
Posting a list of the URLs of issues created will be a little more difficult.

Original comment by acli...@gmail.com on 30 Jan 2008 at 12:38

GoogleCodeExporter commented 9 years ago

Here's a list of all the issues with links created by marco:
Changing "story" content type to "article" or "news" : 
http://drupal.org/node/197765
Swapping error/status messages and help text (in core themes) :
http://drupal.org/node/202821
Add link to add items on new menu form submit page : 
http://drupal.org/node/203004
Add a real hierachical menu admin interface to Drupal : 
http://drupal.org/node/203010
Replace "preview posts" radios with a checkbox : http://drupal.org/node/202538
Simplify/Rework the timezone picker : http://drupal.org/node/197442
Content Types - Generate machine name onblur : http://drupal.org/node/201565
Offer some vocabularys by default : http://drupal.org/node/203051
Improve help text for content types : http://drupal.org/node/201566
"Create Content Type" - move some comment options into a new fieldset :
http://drupal.org/node/202199
Clean up theme settings pages : http://drupal.org/node/202333
Rewrite node-type description of "story" : http://drupal.org/node/197825
Changing "page" content type to "static page" : http://drupal.org/node/197775
Replace "Sticky at top of lists" with an more meaningful equivalent :
http://drupal.org/node/197460
Shorten the block configuration page : http://drupal.org/node/202183
Change "moderation queue" to "approval queue" : http://drupal.org/node/201490
Auto-enable required modules at the module configuration page :
http://drupal.org/node/202364
Clean up theme configuration page : http://drupal.org/node/202336
Offer ATOM (RFC 4287) in addition to RSS : http://drupal.org/node/202018
Rename "RSS Publishing" to "Feed Publishing" : http://drupal.org/node/202020
Changing "story" content type to "article" or "news" : 
http://drupal.org/node/197765
Swapping error/status messages and help text (in core themes) :
http://drupal.org/node/202821
Add link to add items on new menu form submit page : 
http://drupal.org/node/203004
Add a real hierachical menu admin interface to Drupal : 
http://drupal.org/node/203010
Replace "preview posts" radios with a checkbox : http://drupal.org/node/202538
Simplify/Rework the timezone picker : http://drupal.org/node/197442
Content Types - Generate machine name onblur : http://drupal.org/node/201565
Offer some vocabularys by default : http://drupal.org/node/203051
Improve help text for content types : http://drupal.org/node/201566
"Create Content Type" - move some comment options into a new fieldset :
http://drupal.org/node/202199
Clean up theme settings pages : http://drupal.org/node/202333
Rewrite node-type description of "story" : http://drupal.org/node/197825
Changing "page" content type to "static page" : http://drupal.org/node/197775
Replace "Sticky at top of lists" with an more meaningful equivalent :
http://drupal.org/node/197460
Shorten the block configuration page : http://drupal.org/node/202183
Change "moderation queue" to "approval queue" : http://drupal.org/node/201490
Auto-enable required modules at the module configuration page :
http://drupal.org/node/202364
Clean up theme configuration page : http://drupal.org/node/202336
Offer ATOM (RFC 4287) in addition to RSS : http://drupal.org/node/202018
Rename "RSS Publishing" to "Feed Publishing" : http://drupal.org/node/202020

Also, I've attached the patch that marco created.  This issue is all set now.

Original comment by acli...@gmail.com on 1 Feb 2008 at 5:01

Added labels: AdminChecked

Attachments:

node.pages_.inc_sticky.patch

GoogleCodeExporter commented 9 years ago

Thanks Adam.  I had thought Marco would do this.  If I had known you were doing 
it I
would have said I'll do it.  :)

Just to clarify for anyone else following up on this thread: Marco contributed
several patches, just one of them is attached here.

Original comment by b.ru...@gmail.com on 1 Feb 2008 at 10:37

GoogleCodeExporter commented 9 years ago

I wasn't sure if he was getting the emails since he didn't reply, and I just 
wanted
to make sure that he gets credit.  I wrote a simple PHP function to parse the
project_issue RSS feed to pull out the issue titles and links, so it wasn't a 
big
deal.  I didn't see any other patches he created, but feel free to upload any 
others
you know of if you'd like.

Original comment by acli...@gmail.com on 1 Feb 2008 at 10:50

GoogleCodeExporter commented 9 years ago

If it's needed for Marco to get the credit I'm sure Marco or I could do that.

Original comment by b.ru...@gmail.com on 1 Feb 2008 at 10:55

GoogleCodeExporter commented 9 years ago

I think what's been uploaded so far is sufficient.

Original comment by acli...@gmail.com on 1 Feb 2008 at 10:57

gcode-mirror / google-highly-open-participation-drupal

Act on findings in usability test reports #48