Re: new document - how to help GNU

[Jim Sealy Jr.]

Toby,
Very nice document you have there.
I have a few suggested changes.
Jim Sealy Jr.
Proud member: Nit-pickers-is-us
-----------------------------

That wouldn't good for you, the people in your life, or the project that
you've committed to. 
* wouldn't good=wouldn't be good

-----------------------------

"You need to be realistic about how much time you'll be able to spend so
you don't overcommit yourself."
* overcommit=over commit
-----------------------------

"such as Debian GNU/Linux which is available at no cost over the
internet or for low cost on CDROM."
* internet=Internet
-----------------------------

"     Contributor. Many people want to help projects with code,
documentation, packaging, etc but aren't ready to make the commitment
(or don't have the experience) to be maintainers."
* etc=etc.,
-----------------------------

"(we trust that it's EMACS) and start learning how the program is put
together. "
* (we trust that it's EMACS)=(We trust that it's EMACS.)
-----------------------------

Maintainers are the project leaders, they commit substantial time,
energy, and emotion to their projects.
* leaders, they commit=leaders; they commit

"If you have questions, you can ask the developers (preferably via the
developers mailing lists) but please be respectful of their time. 
* Add comma after 'questions'.
-----------------------------

Start by installing a GNU/Linux distribution such as Debian GNU/Linux
which is available at no cost over the internet or for low cost on
CDROM. 
* Linux which is available=Linux, which is available
* or
* Linux which is available=Linux that is available
---------------------------

Richard Stallman launched the GNU Project in 1983 to develop a complete
Unix-like operating system which is free software: the GNU system. 
* system which=system, which  
* or
* system which=system that
----------------------------

If you have an idea to improve the program, you might want to check with
the developers to see if anyone else is working on something similar -
if so you'll want to coordinate your efforts so you don't waste time. 
* Add comma after 'program'.
----------------------------

Because of all of the different tasks at hand we are sure that you have
skills that can help the GNU Project; you don't have to be an
experienced software developer to help us. 
* hand we=hand, we
---------------------------
Obviously the answers to these questions will determine the sorts of
jobs that you'll want to attempt to do. 
* Obviously the=Obviously, the
---------------------------

There are many roles to play within a project; naturally some consume
more time than others. 
* naturally some=naturally, some
---------------------------

By doing so you're joining a community of people who are living their
beliefs. 
* By doing so you're=By doing so, you're
---------------------------

Typically a maintainer will be the ultimate arbiter of any design or
coding issues that arise within the project. 
* Typically a maintainer=Typically, a maintainer
---------------------------

toby cabot wrote:
> 
> Hi Proofreaders!
> 
> My name is Toby Cabot and I'm one of the GNU project volunteer
> coordinators.  Our job is to help people that want to help the GNU
> project.  Over the past couple of years I've found that I answer a lot
> of the same questions, so I've written a document that (I hope) will
> help people figure out how to get involved in GNU.  It's been vetted
> by Hugo Gayosso already but I just remembered this list.  I'd
> appreciate any comments that you've got.
> 
> The document is located at:
> http://www.gnu.org/software/tasklist/howto-volunteer.html
> 
> Regards,
> Toby
> 
> _______________________________________________
> Proofreaders mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/proofreaders