Awesome. I'll work on cleaning it up and making it clearer.
Mike.
On 11/23/15 8:23 AM, Nicholas Skaggs wrote:
This sounds like a plan Mike. We'll just need to make sure the
description for the task makes sense to students.
We have to have 75 tasks to start, and need to supply at least 150
over the course of the program I believe. There's no upper limit ;-)
Nicholas
On 11/20/2015 12:07 PM, Mike Lloyd wrote:
Well, I've already crawled some of them with a Python script. I still
have to go through them and remove various image and external links.
Once I've done that, I'll create a spreadsheet based off this list. I
am thinking of letting the students work on whatever part of the list
they would like, whatever interests them most.
I'm fine with the review idea. I have the task set to the max of 10
days, with the max amount of students allowed. Later reviews are most
likely going to be easier.
Yeah, I think a QA wiki task would be good, and have it separate from
the Help wiki task. I think we get 75 tasks as an org? I saw three,
including mine, last night when I was logged in.
Mike.
On 11/20/15 9:08 AM, Nicholas Skaggs wrote:
On 11/19/2015 05:54 PM, Mike Lloyd wrote:
Hey guys. I created a documentation task that will help go through and
clean up help pages.
For students to pick work from, I will generate a master
spreadsheet of
pages based off a site crawler, then each student can pick whatever
page
they want to review from the spreadsheet.
To verify the what wiki help pages need to be updated, I would have
the
student assigned to the page walk through the page, following it
step-by-step to make sure it is correct. If it doesn't work, the
student
can then do research into how to make it work. If the student get's
stuck
and can't figure out what steps are needed to make the information
current,
they can ask a mentor for help. Before updating the page, I would
have the
student email the changes to a mentor, have the mentor review the
student's
changes, and then have the student update the page once a mentor has
verified.
If a page should be deleted, then the student can mark a page for
deletion.
After the GCI is over, the list can be reviewed by the QA community
before
a page is deleted.
I figure this is the best way to keep our help pages current. What
are the
community thoughts? I based this off the Wiki Pages task example
from here:
http://people.canonical.com/~alan/Google_Code-In_2015_Sample_Tasks.pdf
Here is the initial task:
https://codein.withgoogle.com/dashboard/tasks/4830110020534272/
Mike.
Mike, a master list of potential pages is a good idea. Do you have a
list to start? How will you crawl them? For the edits, I think it
would be 'OK' to have the students edit the page directly, and then
ask for a review. You could also do the whole clone / replace thing
too if you don't like the idea of direct editing. That is, you copy
the wiki page to a temporary page and edit it there. Once reviewed,
you replace the original page and delete the copy.
Specific to the QATeam wiki, I think having a task to go through
each of the Roles pages is an excellent place to start. I imagine
there's also some dead pages / cloned pages, etc that could be found
by looking at things like
https://wiki.ubuntu.com/QATeam?action=LikePages and
https://wiki.ubuntu.com/Testing?action=LikePages. I'm sure wiki
experts would have even more tricks.
Nicholas
--
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
