To help those who want to help fix/report bugs, have someone experienced with
the system record 5-minute "How to Report a Bug" and a "How to Find a Bug to
Tackle" screencasts.

When I go to bugs.python.org and search for things to help with, I'm overwhelmed
with the query options and am not sure where to start.  This is the kind of
thing a screencast is good for and a written document/wiki page is bad for.

Might also expand the screencast a bit, in that do one for tech-writers, teach
briefly how the doc tools work, then how to find an unfixed doc bug to work,
then how to submit their finished work into the system for integration.

This should probably wait until we redesign the workflow of the issue
tracker.  Once people have experience with it and all initial bugs are
worked (and Erik is ready for more trouble  =) out I plan to bring up
with python-dev the question of how we want our bugs to look instead
of continuing to force ourselves to work within SF's issue workflow.

On 9/13/07, Jeff Rush <metatracker@psf.upfronthosting.co.za> wrote:
>
> New submission from Jeff Rush:
>
> To help those who want to help fix/report bugs, have someone experienced with
> the system record 5-minute "How to Report a Bug" and a "How to Find a Bug to
> Tackle" screencasts.
>
> When I go to bugs.python.org and search for things to help with, I'm overwhelmed
> with the query options and am not sure where to start.  This is the kind of
> thing a screencast is good for and a written document/wiki page is bad for.
>
> Might also expand the screencast a bit, in that do one for tech-writers, teach
> briefly how the doc tools work, then how to find an unfixed doc bug to work,
> then how to submit their finished work into the system for integration.
>
> ----------
> messages: 779
> nosy: jrush
> priority: wish
> status: unread
> title: Have a Core Bug Chaser Create a Bug Reporting Screencast
>
> _______________________________________________________
> Meta Tracker <metatracker@psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue156>
> _______________________________________________________
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss@python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>

Will this be a part of your PSF-sponsored job?  I prefer text over video personally but understand screencasts are en vogue, so.

Wasn't planning on it, but it could be a possibility if people really show an interest and it is decided to be worth my time.

Good start would be with collecting user stories. Because the process may be different for core developers and users.

For example, this story "I'm overwhelmed with the query options" is extremely good. I may add a few more - "I want find all bugs for Python module", "I want to see the source code where bug happens", "I want to classify my bugs", "I want to vote on features I like", "I want to rate and filter comments" etc.