[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Review Required: USB FLASH MEMORY HOWTO
From: Tabatha Marshall ####@####.#### Date: 24 Nov 2003 21:03:02 -0000 Message-Id: <1069707754.20351.7.camel@mysticchild> Hi all, Another new document ready for review. Also, still outstanding is Mobile IPv6, still in need of review before it's added. If you'd like to work on either one, please email me and cc the list! I'll be glad to work with anyone who wants to give one of these a try, and will forward the source file(s) to you directly. Tab -----Forwarded Message----- From: Niko Sauer ####@####.#### To: ####@####.#### Subject: USB FLASH MEMORY HOWTO Date: Mon, 24 Nov 2003 08:22:23 +0200 Attached is a gzipped file containing the sgml source for the howto mentioned above. This has been distributed to "discuss" about three weeks ago -- with one positive reply. Looking forward to the reviews. Niko Sauer ______________________ Unit of Advanced Study University of Pretoria Pretoria 0002 South Africa Tel: [27][12] 420 3558 Fax: [27][12] 420 4025 ________________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: ####@####.#### For additional commands, e-mail: ####@####.#### -- Tabatha Marshall Web: www.merlinmonroe.com Linux Documentation Project Review Coordinator (http://www.tldp.org) Linux Counter Area Manager US:wa (http://counter.li.org) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Review Required: USB FLASH MEMORY HOWTO
From: Mary Gardiner ####@####.#### Date: 24 Nov 2003 21:52:32 -0000 Message-Id: <20031124214822.GA22884@titus.home.puzzling.org> On Mon, Nov 24, 2003, Tabatha Marshall wrote: > Hi all, > > Another new document ready for review. > > Also, still outstanding is Mobile IPv6, still in need of review before > it's added. > > If you'd like to work on either one, please email me and cc the list! > I'll be glad to work with anyone who wants to give one of these a try, > and will forward the source file(s) to you directly. I'm happy to do a language review of the USB Flash Memory HOWTO. Tabatha, is there any chance you could give some indication of the document's length when you post these (even though wc counts tags, the output of wc would be more than sufficient -- all I want to know is whether I'm signing on for a 2 000 word or 20 000 word document!) -Mary | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Review Required: USB FLASH MEMORY HOWTO
From: Mary Gardiner ####@####.#### Date: 24 Nov 2003 22:39:07 -0000 Message-Id: <20031124223859.GA23204@titus.home.puzzling.org> On Tue, Nov 25, 2003, Mary Gardiner wrote: > Tabatha, is there any chance you could give some indication of the > document's length when you post these (even though wc counts tags, the > output of wc would be more than sufficient -- all I want to know is > whether I'm signing on for a 2 000 word or 20 000 word document!) Actually, I think posting the abstract/first paragraph of the introduction/whatever approximation of an abstract you can grab to potential reviewers might be useful too. Asking authors to submit a plain text copy of their abstract might help here. (Of course, there might also need to be an answer to "what is an abstract?" -- the answer for me would be something like "200-500 words summarising the main things a reader can find in your document".) I coordinate reviewing for an academic journal, and peer reviewers find it useful to see the document abstract before signing on for the document (mind you, peer reviews are closer to technical reviews than language reviews). Sorry if this seems a bit cranky -- it's intended to be helpful, and I hope comes across this way. -Mary | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Review Required: USB FLASH MEMORY HOWTO
From: Tabatha Marshall ####@####.#### Date: 24 Nov 2003 22:42:35 -0000 Message-Id: <1069713725.20504.16.camel@mysticchild> On Mon, 2003-11-24 at 13:48, Mary Gardiner wrote: > I'm happy to do a language review of the USB Flash Memory HOWTO. > > Tabatha, is there any chance you could give some indication of the > document's length when you post these (even though wc counts tags, the > output of wc would be more than sufficient -- all I want to know is > whether I'm signing on for a 2 000 word or 20 000 word document!) No problem at all! I'll send you the file in a separate messages, since the mailing list doesn't seem to like attachments. Thanks! Tab -- Tabatha Marshall Web: www.merlinmonroe.com Linux Documentation Project Review Coordinator (http://www.tldp.org) Linux Counter Area Manager US:wa (http://counter.li.org) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Review Required: USB FLASH MEMORY HOWTO
From: Tabatha Marshall ####@####.#### Date: 24 Nov 2003 23:27:17 -0000 Message-Id: <1069716408.20504.46.camel@mysticchild> On Mon, 2003-11-24 at 14:38, Mary Gardiner wrote: > On Tue, Nov 25, 2003, Mary Gardiner wrote: > > Tabatha, is there any chance you could give some indication of the > > document's length when you post these (even though wc counts tags, the > > output of wc would be more than sufficient -- all I want to know is > > whether I'm signing on for a 2 000 word or 20 000 word document!) > > Actually, I think posting the abstract/first paragraph of the > introduction/whatever approximation of an abstract you can grab to > potential reviewers might be useful too. Asking authors to submit a > plain text copy of their abstract might help here. (Of course, there > might also need to be an answer to "what is an abstract?" -- the answer > for me would be something like "200-500 words summarising the main > things a reader can find in your document".) You know what? That's a great idea, and I'll tell you why! Because there are some documents that arrive without a scope. I can ask authors of new submissions who haven't provided an abstract to please do so, and then I can post that along with a word or line count when I let the reviewers know it's available for review. And whether or not an abstract has been provided, I can use it as an opportunity to explain to the author what we're looking for in the abstract. I usually tell authors the abstract should spell out very clearly the topic being covered, what a reader can expect to accomplish/understand by the end of it, and that it should be roughly a paragraph. > I coordinate reviewing for an academic journal, and peer reviewers find > it useful to see the document abstract before signing on for the > document (mind you, peer reviews are closer to technical reviews than > language reviews). Agreed. So I should really let all reviewers, whether peer, technical or language, know these details, or have the author post that information when submitting his draft to the discussion list for peer review. If I can get it done by the author from the get-go it will save a lot of time. > Sorry if this seems a bit cranky -- it's intended to be helpful, and I > hope comes across this way. Didn't seem cranky to me at all. I agree with the logic behind it, and so I don't mind doing it a bit. :D Tab -- Tabatha Marshall Web: www.merlinmonroe.com Linux Documentation Project Review Coordinator (http://www.tldp.org) Linux Counter Area Manager US:wa (http://counter.li.org) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |