[bksvol-discuss] Re: Creating a Process for Creating Guidelines
- From: Cindy <popularplace@xxxxxxxxx>
- To: bksvol-discuss@xxxxxxxxxxxxx
- Date: Wed, 10 Jun 2009 16:50:22 -0700 (PDT)
A very good team
Cindy
Wish List (i.e., books wanted added to the collection) and books-being-scanned
list available at sites below
Wish List: https://wiki.benetech.org/display/BSO/Bookshare+Wish+List
Books Being Scanned List:
https://wiki.benetech.org/display/BSO/Books+Being+Scanned+List
--- On Wed, 6/10/09, Pavi Mehta <pavim@xxxxxxxxxxxx> wrote:
> From: Pavi Mehta <pavim@xxxxxxxxxxxx>
> Subject: [bksvol-discuss] Re: Creating a Process for Creating Guidelines
> To: bksvol-discuss@xxxxxxxxxxxxx
> Cc: carrie.k@xxxxxxxxxxxxx
> Date: Wednesday, June 10, 2009, 10:46 AM
> Hi All,
>
> Great to see the responses to this email! Overnight we've
> had 10 experienced Bookshare volunteers step forward to form
> this team of Advisors/Shapers -- or whatever they might
> choose to name themselves (smile). Ten is a great size to
> begin with -- not too small and not too unwieldy either.
>
> The 10 volunteers are: Judy S., Christina, Amber, Mayrie,
> Chanelle, Elizabeth, Shelley, Bob, Evan and Roger. (If
> anyone else wrote in who I inadvertently missed, please let
> me know).
>
> I'll be in touch with this team off-list today so we can
> get some of the logistical details underway and work out a
> process for getting started. As things develop we'll be sure
> to update the Volunteer list (and the blog) so people can
> stay in touch with how things develop.
>
> Nancy thanks for your comments and suggestions. We'll have
> the team take them into consideration for sure.
>
> With appreciation for this new team that's ready to go the
> extra mile to make volunteering with Bookshare continually
> smoother!
>
> All good things,
> Pavi
>
> Pavi Mehta
> Volunteer Coordinator, Bookshare
>
> Benetech
> 480 S. California Ave., Suite 201
> Palo Alto, CA 94306-1609 USA
> Phone: +1 650 644-3459
>
> pavim@xxxxxxxxxxxx
>
> www.benetech.org
>
> The Benetech Initiative - Technology Serving Humanity
> A Nonprofit Organization
>
>
>
>
>
>
> -----Original Message-----
> From: bksvol-discuss-bounce@xxxxxxxxxxxxx
> [mailto:bksvol-discuss-bounce@xxxxxxxxxxxxx]
> On Behalf Of Chanelle Hill
> Sent: Wednesday, June 10, 2009 8:36 AM
> To: bksvol-discuss@xxxxxxxxxxxxx
> Subject: [bksvol-discuss] Re: Creating a Process for
> Creating Guidelines
>
> I agree that instructions for Word, Openbook, and Kurzweil
> would be
> helpful. When new volunteers begin proofing and scanning,
> they
> frequently have questions about validating and scanning
> with the
> devices and programs they have. At least, I had questions
> and I have
> seen several posts to this list asking for help
> proofreading. To make
> the volunteer manual less intimidating, there could be a
> separate
> document detailing how to use each program. It would be
> helpful to
> have a section on proofing with the BrailleNote, Pacmate,
> and/or other
> devices volunteers use for editing documents as well.
> Alternatively,
> instructions could also be appended to the end of the
> manual with
> different headings for each program. The volunteer manual
> could give
> Bookshare's proofreading requirements and reference the
> document or
> sections containing more specific instructions for those
> who want
> them. A separate document or appendices would help those
> who want to
> submit the very best book they possibly can. The manual
> and
> Bookshare's requirements--especially pertaining to
> pagination and
> numbering--were a little confusing for me at first, so
> having
> instructions for how to do common proofreading tasks might
> clarify
> things for others.
> Maybe there could be an email list for new volunteers that
> specifically discusses proofreading and scanning. We could
> still keep
> this list for announcing wish list requests, items that are
> being
> scanned, newly submitted books, and asking one another for
> help with
> issues that come up with specific books. Maybe two lists
> might be
> time-consuming or too much; however, new volunteers could
> join the
> proofreading and scanning list, which would probably have
> fewer
> emails, so that they would not need to be bombarded with
> tons of
> messages. Some of the people on the advisory committee
> could join the
> list to facilitate discussion and assist new volunteers.
> New
> volunteers could be automatically signed up for the
> scanning and
> proofing list to ensure that the situation with NW will not
> be
> repeated.
> I am sorry for my verbose email and for bringing up two
> different
> topics. By the way, I never received the email or
> newsletter detailing
> font requirements for submissions.
> I would be interested in joining the volunteer advisory
> committee.
>
> Chanelle
>
> On 6/10/09, Rogerbailey81@xxxxxxx
> <Rogerbailey81@xxxxxxx>
> wrote:
> > I can see a definite value to having these suggestions
> incorporated into
> > the manual. However, thinking back to almost a year
> ago when I first became
> > a
> > volunteer, if I had read a manual that long an
> complicated I think I might
> > have been intimidated into backing out. If I saw a lot
> of instructions
> > dealing with programs and equipment I did not have I
> might have decided that
> > I was
> > unable to volunteer at all.
> >
> >
>
>
> "I find
> > capitalism repugnant. It is filthy, it is gross, it is
> alienating... because
> > it
> > causes war, hypocrisy and competition." Fidel Castro
> >
> > The Militant: http://www.themilitant.com/txtindex.shtml
> Pathfinder Press:
> > http://www.pathfinderpress.com
> > Granma International: http://granma.cu/ingles/index.html
> >
> _
> >
> > table with 2 columns and 6 rows
> > Subj:
> > [bksvol-discuss] Re: Creating a Process for Creating
> Guidelines
> > Date:
> > 6/10/2009 9:42:40 AM Eastern Daylight Time
> > From:
> > rpet@xxxxxxx
> > Reply-to:
> > bksvol-discuss@xxxxxxxxxxxxx
> > To:
> > bksvol-discuss@xxxxxxxxxxxxx
> > Sent from the Internet
> > (Details)
> > table end
> >
> > As an Openbook user, and someone who has had four
> books rejected, I concur.
> > Robert
> >
> > Attention: The information contained in this message
> and/or attachments is
> > intended only for the person or entity to which it is
> addressed and may
> > contain
> > confidential and/or nonpublic material. Any review,
> retransmission,
> > dissemination or other use of, or taking of any action
> in reliance upon,
> > this
> > information
> > by persons or entities other than the intended
> recipient is prohibited. If
> > you received this in error, please contact the sender
> and delete the
> > material
> > from any system and destroy any copies.
> >
> >>>> "Nancy Martin" <nancyam@xxxxxxxxxxx>
> 6/9/2009 10:03 PM >>>
> > Hi Pavi and list,
> > One presumably change which should be made in the
> manual is that books are
> > initially checked for fourteen days and not 30 as the
> manual states.
> >
> > I personally would like to see program-specific
> sections in the manual.
> > For example, a section on using MS Word to proof
> books. The section might
> > include
> > a checklist type approach with instructions for
> accomplishing those tasks.
> > For example, 1. check and fix fonts with appropriate
> instructions. 2.
> > taking
> > out paragraph breaks with Word instructions. This
> would help proofers make
> > sure they remembered to do all these things before
> submitting a book.
> > Another
> > set of instructions would be written for OpenBook,
> Kurzweil 1000, etc.
> >
> > I hope I'm making some sense.
> > Just my two cents worth,
> > Nancy Martin
> > Oklahoma
> > ----- Original Message -----
> > From: Pavi Mehta
> > To: bksvol-discuss@xxxxxxxxxxxxx
> > Sent: Tuesday, June 09, 2009 4:06 PM
> > Subject: [bksvol-discuss] Re: Creating a Process
> for Creating Guidelines
> >
> > That's great to hear Christina! It's definitely
> possible to have you be
> > on the team. Judy S. has also volunteered to be a part
> of it. As more
> > feedback
> > comes in we will keep everyone posted.
> >
> >
> > All good things,
> >
> > Pavi
> >
> >
> > From: bksvol-discuss-bounce@xxxxxxxxxxxxx
> > [mailto:bksvol-discuss-bounce@xxxxxxxxxxxxx]
> On Behalf Of Christina
> > Sent: Tuesday, June 09, 2009 2:03 PM
> > To: bksvol-discuss@xxxxxxxxxxxxx
> > Subject: [bksvol-discuss] Re: Creating a Process
> for Creating Guidelines
> >
> >
> > Hi, Pavi.
> >
> > This guideline shapers group is a wonderful idea.
> >
> > I'd like to be included on this team if that's
> possible.
> >
> > Christina
> >
> >
> > ----- Original Message -----
> >
> > From: Pavi Mehta
> >
> > To: bksvol-discuss@xxxxxxxxxxxxx
> >
> > Cc: carrie.k@xxxxxxxxxxxxx
> >
> > Sent: Tuesday, June 09, 2009 4:26 PM
> >
> > Subject: [bksvol-discuss] Creating a Process for
> Creating Guidelines
> >
> >
> > Hi All,
> >
> >
> > As you know the recent guidelines that went out
> on Page Numbering have
> > generated some understandable concern and confusion
> among the volunteers.
> > Some
> > of you have written in to staff with detailed emails
> articulating those
> > areas of concern and where the guidelines appear
> more inconvenient than
> > helpful.
> > Others have expressed their opinions on the list.
> Carrie and I have had
> > several discussions recently on how best to address
> these concerns and
> > modify
> > the
> > guidelines so that they serve as a tool and not a
> hindrance. As hands-on
> > volunteers all of your input is valuable and we want
> the guidelines to
> > reflect
> > the best practices and collective wisdom of the
> volunteer community.
> >
> >
> > Regarding page numbers Carrie will send out a
> note shortly to clarify
> > some of the areas of confusion and concern and explain
> how the guidelines
> > for
> > this will be implemented. Bottom line is that we do
> understand the wide
> > variety of challenges volunteers face with including
> page numbers in books,
> > and
> > we're glad to have had your feedback. We intend hereon
> for this guideline
> > to be implemented with a large degree of flexibility -
> and will be rewriting
> > the guidelines to clearly reflect the difference
> between page number
> > requirements for educational books and other
> submissions.
> >
> >
> > Moving forward though, for us one of the
> overarching questions that the
> > Page Number issue brings up is:
> >
> >
> > What is the most efficient and effective way for
> Bookshare to do the
> > following:
> >
> >
> > 1. Identify volunteer areas that need
> guidelines
> >
> > 2. Draft guidelines and have them
> reviewed by a small pool of
> > volunteers(in a sort of beta phase)
> >
> > 3. Finalize and share these guidelines
> among the greater
> > volunteer community
> >
> >
> > Ideally, Carrie and I feel that volunteers
> should have a leading and
> > more transparent role to play in steps 1 and 2 above.
> >
> > Here is a suggested approach, that it would be
> great to get your input
> > on:
> >
> >
> > 1. Form a self-selected team of
> "Bookshare Guideline Shapers" (we
> > can think of a better name down the line- smile). The
> Guideline Shapers are
> > Bookshare volunteers who step forward to help
> identify, draft and sound out
> > missing guidelines. Even if something is brought to
> staff attention
> > regarding
> > a missing guideline, we would turn it over initially
> to this group with our
> > suggestions if any.
> >
> >
> > 2. The Guideline Shapers would decide
> on areas that need
> > guidelines, work on an initial draft of these
> guidelines and then send them
> > over to
> > Carrie/me for review from the Bookshare staff
> perspective. The Guideline
> > Shapers would go over any edits from us and come up
> with a revised
> > guideline.
> > They would then solicit feedback on the guideline from
> the volunteer list
> > before making any final tweaks to it.
> >
> >
> > 3. Once the guideline has been
> finalized, I will incorporate it
> > in the Volunteer Manual, and ensure that it is
> announced on the volunteer
> > blog
> > as well as on the volunteer discussion list. (We will
> create a separate
> > section of the manual for Updates to the Manual so
> that it is easy for
> > people
> > to
> > keep up with the changes).
> >
> >
> >
> > Participation from the volunteer community while
> shaping policy, we
> > feel is key and we think this approach could be a
> really invigorating way of
> > facilitating
> > the creation of useful guidelines from the inside-out.
> Of course we would
> > be more than glad to help with the logistics of
> setting up a group alias and
> > other etcs for Guideline Shapers, and to provide
> assistance wherever we
> > can. We would love your feedback on this approach as
> well as to know if any
> > of
> > you are interested in being part of such a team.
> >
> >
> > Warm regards,
> >
> >
> > Pavi & Carrie
> >
> >
> > Pavi Mehta
> >
> > Volunteer Coordinator, Bookshare
> >
> >
> > Benetech
> >
> > 480 S. California Ave., Suite 201
> >
> > Palo Alto, CA 94306-1609 USA
> >
> > Phone: +1 650 644-3459
> >
> >
> > pavim@xxxxxxxxxxxx
> >
> >
> > www.benetech.org
> >
> >
> > The Benetech Initiative - Technology Serving
> Humanity
> >
> > A Nonprofit Organization
> >
> >
> > To unsubscribe from this list send a blank Email to
> > bksvol-discuss-request@xxxxxxxxxxxxx
> > put the word 'unsubscribe' by itself in the subject
> line. To get a list of
> > available commands, put the word 'help' by itself in
> the subject line.
> >
> >
> >
> > **************
> > Download the AOL Classifieds Toolbar for local deals
> at your
> > fingertips.
> > (http://toolbar.aol.com/aolclassifieds/download.html?ncid=emlcntusdown00000004)
> >
> To unsubscribe from this list send a blank Email to
> bksvol-discuss-request@xxxxxxxxxxxxx
> put the word 'unsubscribe' by itself in the subject
> line. To get a list of available commands, put the
> word 'help' by itself in the subject line.
>
> To unsubscribe from this list send a blank Email to
> bksvol-discuss-request@xxxxxxxxxxxxx
> put the word 'unsubscribe' by itself in the subject
> line. To get a list of available commands, put the
> word 'help' by itself in the subject line.
>
>
To unsubscribe from this list send a blank Email to
bksvol-discuss-request@xxxxxxxxxxxxx
put the word 'unsubscribe' by itself in the subject line. To get a list of
available commands, put the word 'help' by itself in the subject line.
Other related posts:
