Beta-Buddies, Need a beta-reader? Want to beta read? Options

[evlpez]

Hello fellow ferrets!

In an effort to help us all become better writers, I've decided to implement a beta reader sign-up topic. Beta readers will proof-read their fellow ferrets' work, offer corrections to spelling and grammar prior to posting and help writers explore or expand on their ideas.

Here's what we'll do. Anyone who wants to offer their proof-reading services can sign up in this topic. I will keep updating the following post which shows who is available to take on a 'buddy' and members will refer to this post when looking for a beta reader.

I (evlpez) am responsible for this list. If you need your information updated, please send me a PM with the particulars.

1. Beta readers will sign up following the form I'll set out in the next post.

2. Beta-buddies (reader and writer) should agree upon a term for their partnership (one piece, one month, 6 months, etc…). Using different readers over time will allow both members to benefit from different writers as time goes on.

3. When a beta reader takes on a writer, they should let me know so I can update the list. This prevents a reader from being solicited by more writers after they've taken on as many as they want. Beta-readers who've agreed to read a single piece of work for a writer (as opposed to a time period) don't need to have an update on this list.

4. Beta readers should be specific with corrections, offering correct spellings and explainations when required, describing why something requires correction (grammar, correct word usage, etc…).

5. Beta reading is a learning exercise. If you don't know if something is right, do try to look it up so you're giving your writer (and yourself) the correct information.

6. Writers are responsible for finding a beta reader by PM or e-mail, and any subsequent communication is their responsibility, not that of Project Ferret.

7. Writers should spell check and proof read their own work prior to submitting it to their beta readers whenever possible.

8. Writers are responsible for their own deadlines. Be sure to let your beta know your deadline and give him/her sufficient time to go over your work with you.

9. Beta readers who want beta readers for their own work should try to ask someone else from the list, not the writer(s) they're reading for. This is just a guideline - if members have already set up a partnership with their friends to proof-read their work, that's fine.

I should point out that members of PF are not required to have their work beta-read. I just thought we should set it up for members who want it.

We'll discuss whether Ferret Duel Challenge entrants should be allowed to have their submissions beta read at another time. I may set up a poll to decide this, I'm not sure yet.

Please use this topic to ask/answer questions about this system and to sign up to offer your services.

This post has been edited by evlpez: Jan 6 2004, 03:16 PM

[McGonagall's Cat]

Tips from About.com
http://scifi.about.com/c/ht/00/07/How_Good...r0962933665.htm

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

How to Be a Good Beta-Reader
From your Sci-Fi / Fantasy Guide

Authors need real help when they ask for a beta-read or editing job..

Difficulty Level: Hard
Time Required: Thirty minutes for a short story



--------------------------------------------------------------------------------
Here's How:

Make sure the author sends their story in a format you like (e.g. Word Perfect, Microsoft Word).

Save a new copy of the story with your comments to send back.

Put all your comments in bold.

Run a spellcheck before you try to read the story. Remember to bold the corrections, or if you're using plain text, put them in brackets.

Read it through the first time making only minimal comments as you go. You'll come back later to lengthen them.

Correct all the grammar problems you see. If you're not sure about something, indicate the problem and say you think there's something wrong.

Mark places that read awkwardly whether they're incorrect or not.

Comment whenever a character "sounds" wrong to you. Try reading the dialogue aloud to see if you sound like the character.

If you have no comments for large sections of the story, delete those sections.
(note: this isn't always a good idea. - McG's Cat)

Comment when you're aware of an emotional reaction to the story (e.g. "I'm happy that happened." "That's gross!").

Remember to have both positive and negative comments.

Always be tactful, and phrase all advice only as a suggestion.

After the first read-through, take some time, then read through it a second time.

Put your over-all comments at the top of the story so the author gets them first.

Be honest. If you don't want to beta for the author again, tactfully say so. If you do want to, be sure to say so as well!


Tips:

Before agreeing to beta-read, know the type of story you'll be getting, and its rating.

If there are a whole bunch of technical errors, you're not responsible for fixing them. Just tell the author there are many.

Use reference guides to check how to spell character names and Star Trek equipment.