From: "Robin S. Socha" <robin-dated-1016467962.552def@socha.net>
Cc: Justin Sheehy <justin@iago.org>
Subject: Re: Gnus FAQ maintainership
Date: Fri, 15 Mar 2002 11:32:19 -0500 [thread overview]
Message-ID: <deathsquad.871yelhjvw.fsf@blitzkrieg.socha.net> (raw)
In-Reply-To: <x7d6y5vnim.fsf@ra.iago.org> (Justin Sheehy's message of "Fri, 15 Mar 2002 10:50:09 -0500")
* Justin Sheehy <justin@iago.org> writes:
> "Robin S. Socha" <robin-dated-1016459156.2abe03@socha.net> writes:
> [regarding the my.gnus.org team taking over the FAQ]
>
>>> - Maintain the FAQ such that it can be published to the following
>>> three formats easily:
>>>
>>> - a useful format for Usenet, preferable the existing
>>> minidigest
>>> - TexInfo
>>> - a single HTML page
>>
>> I presume this is subject to negotiation? If so, we've got a comple
>> of ideas that might make handling the FAQ a little easier (not too
>> many people speak texi, including myself).
>
> I can't be too strict on this one, since the FAQ currently only exists
> in the 1st and 3rd of those two formats.
Good.
> Conversion to texi has been on my todo list for a very long time.
> While it isn't required, it would have a huge benefit: the FAQ could
> be checked in to the Gnus distribution.
I've thought about that, too. We'll discuss this in-depth, because
submissions are somewhat easier using makefaq.
> The gnus-faq.texi currently distributed is so out of date as to be worse
> than useless. Having a somewhat up-to-date FAQ in the distribution
> would be a significant benefit to users.
I wholeheartedly agree. But we'll have to see if we know enough texi for
this.
>> I've taken the liberty to include the Ding list and the MGO staff to,
>> well, let you guys know that we're volunteering.
>
> This sounds like a nearly ideal situation to me: multiple maintainers
> working together, using an already well-known site.
We've also just recruited the maintainer of the German
de.comm.software.newsreaders FAQ, Christoph Garbers.
> I will hand things off to MGO. I will send a separate message to that
> group with the necessary details.
Thanks. We'll try to live up to the standards you've set over the past
years.
> Robin, does faq@my.gnus.org exist yet, or should I just send it to
> webmasters for now?
I just set it up:
ezmlm-showctl ~/domains/my.gnus.org/faq
.-== list config for my.gnus.org/faq ==----
| [x] (a) webarchive
| [x] (H) require confirmation on subscription
| [x] (i) indexed for webaccess
| [x] (m) moderated list
| [x] (p) public list
| [x] (s) subscription moderation
| - listname 'faq'
| - hostname 'my.gnus.org'
'-== list config for my.gnus.org/faq ==----
I suggest taking this off the Ding list now. You can sub to faq by
sending a blank mail to faq-subscribe@my.gnus.org.
There is a (moderately... .-)) unrestricted list
"faq-submissions@my.gnus.org" now, too.
next prev parent reply other threads:[~2002-03-15 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 21:08 Justin Sheehy
2002-03-15 14:27 ` Robin S. Socha
2002-03-15 15:50 ` Justin Sheehy
2002-03-15 16:32 ` Robin S. Socha [this message]
2002-03-16 15:47 ` Kai Großjohann
2002-03-18 11:12 ` Per Abrahamsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=deathsquad.871yelhjvw.fsf@blitzkrieg.socha.net \
--to=robin-dated-1016467962.552def@socha.net \
--cc=justin@iago.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).