[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: cvs commit to ddp/manuals.sgml/securing-howto by jfs



On Tue, Sep 03, 2002 at 08:34:49PM -0400, Brian Masinick wrote:
> 
> 
> Larry Holish wrote:
> 
> >On Mon, Sep 02, 2002 at 10:35:50AM +0200, Javier Fern?ndez-Sanguino Pe?a 
> >wrote:
> > 
> >
> >>On Mon, Sep 02, 2002 at 02:03:17AM -0600, Debian Doc Project CVS Master 
> >>wrote:
> >>   
> >>
> >>>Repository: ddp/manuals.sgml/securing-howto
> >>>who:        jfs
> >>>time:       Mon Sep  2 02:03:17 MDT 2002
> >>>
> >>>
> >>>     
> >>>
> >>	BTW. I will soon ask for reviewers/proof readers since I would like 
> >>	to
> >>finish off the document soon (remove all FIXMEs and clear most TODOs). Is 
> >>anyone
> >>interested?
> >>	Since I have written quite a lot during vacation proof reading would 
> >>	be
> >>appreciated (probably many typos out there...)
> >>
> >>	Javi
> >>   
> >>
> >
> >Yes, I'm interested, but I'm new to this list (and effort).  I have
> >been a Debian user since slink, and I wanted to give something back to
> >the project.  I'm a native English speaker/writer and would like to
> >donate some time to improving our documentation.  Proofreading seems
> >like a quick way to get started.
> >
> >I have browsed through http://www.debian.org/doc/ddp, installed the sarge
> >version of debiandoc-sqml, and am reading it's documentation.  What's
> >my next step?
> >
> >Larry
> >
> > 
> >
> I join Larry in that interest.  I've been running Debian software since 
> last fall and GNU/Linux distros since 1995, and UNIX systems since 1982. 
> I do a lot of technical writing and documentation, and I'd be delighted 
> to help out in this effort, proof reading, contributing, or whatever 
> else may be needed.  But I could use some suggestions on where to look 
> and what to do to get started.  In terms of the project itself, I am a 
> newbie.  I did, however, attend this summer's Debconf2 in Toronto, so I 
> have a few ideas... even so, I could use some help and guidance on how I 
> can dig in and how I can best be of help in this kind of endeavor.
> 
> -- 
> Brian Masinick
> mailto:masinick@yahoo.com

We would certainly appreciate your help, Brian and Larry. I proofed
about 30% of the document last night, and I was really flagging after
3 hours. It is a very long document, and while Javi is a good
English-as-second-language speaker, there are still a lot of little
things to edit to make it sound good to a native speaker.

Would you guys like to split the other two thirds? I ended up at
the beginning of <sect id="kernel-patch">, and the two-thirds point
would be about <sect id="vpn">. I did check my changes in.

To get started, select the download link from 

http://cvs.debian.org/ddp/manuals.sgml/securing-howto/securing-debian-howto.sgml?rev=1.66&cvsroot=debian-doc&content-type=text/vnd.viewcvs-markup

That should get you a copy of the current version of the sgml source.

Then make another copy of that download before starting, and name it 
securing-debian-howto.sgml.orig . Use a text editor to 
edit the downloaded document (not .orig). When you're ready to 
turn in your changes, run

diff -u securing-debian-howto.sgml.orig securing-debian-howto.sgml > securing-debian.patch

You can name the patch whatever you want, but then attach it to an email
and send it to the list; either Javi or someone else can then apply it.

When you want to help out on other docs, you'll want to learn how to 
check out a cvs tree anonymously, a good reference example doc is 

http://cvs.debian.org/boot-floppies/README-CVS

It's just you don't need to mess with that if you're not already familiar 
with it, since Javi has everything in one file.

-- 
*------v--------- Installing Debian GNU/Linux 3.0 --------v------*
|      <http://www.debian.org/releases/stable/installmanual>     |
|        debian-imac: <http://debian-imac.sourceforge.net>       |
|            Chris Tillman        tillman@voicetrak.com          |
|                  To Have, Give All to All (ACIM)               |
*----------------------------------------------------------------*



Reply to: