You're right, I hadn't thought through the implications of using post_faq
to submit a FAQ for approval. I haven't done it that way myself (I use
post_faq for postings, but not to send in requests).
I think what you'd have to do is pretend to post_faq that the awaiting-
approval FAQ is a separate FAQ. You'd want to do this anyway, so that you
can have the previously approved FAQ still in place and still being
posted. Then you simply don't set up any regular posting interval for the
temporary FAQ entity; instead use -force to make post_faq submit it when
you want to. When you get approval, update the existing FAQ file and
delete the temporary FAQ.
And I don't even want to think about how to do it if you use the RTFM
posting daemon rather than post_faq. In that case you'd probably be
best off just to mail the same document to the moderators that you would
mail to the daemon. A note to the moderators explaining that you plan to
use the daemon should clue them in sufficiently about what headers will
get added later.
This sort of stuff, as well as an unambiguous explanation of the
approved-line business, should probably be in a "FAQ Author's Guide"
that would not be publicly posted, but would be mailed out to new
submitters to news.answers. Sending it to the faq-maintainers list
every so often would be a good idea too.
I agree with Chris that the moderation process needs rethinking and
some software upgrades. I'm glad to see Chris volunteer some time
for this, because the moderators obviously haven't got enough time.
(I'd help, but I don't have time either :-()
Also, I suspect that Robert is right that iterations on getting a FAQ
approved would go faster and more pleasantly if a single moderator were
assigned to deal with that FAQ until approval is obtained. Sure, there
would have to be ways to pick up the pieces if a moderator unexpectedly
got sick or whatever, but *most of the time* this would be considerably
more efficient than the present approach.
regards, tom lane
[
Usenet Hypertext FAQ Archive |
Search Mail Archive |
Authors |
Usenet
]
[
1993 |
1994 |
1995 |
1996 |
1997
]
© Copyright The Landfield Group, 1997
All rights reserved