zsh-workers
 help / color / mirror / code / Atom feed
From: Adam Spiers <adam@spiers.net>
To: zsh-workers@sunsite.auc.dk
Subject: Re: zsh-announce moderators still alive?
Date: Tue, 30 Nov 1999 15:10:10 +0000	[thread overview]
Message-ID: <19991130151010.B28928@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <E11soBg-0008Ld-00@crucigera.fysh.org>

Zefram (zefram@fysh.org) wrote:
> Adam Spiers wrote:
> >I just had two emails I sent to zsh-announce returned to me, because
> >no moderators had acted on them in time.  Are there any moderators out
> >there?  What should I do?
> 
> I'm still a moderator, and I'm here.  I deliberately abstained on the
> question of whether your messages were suitable for -announce.  (On the
> whole I think they wouldn't be of much interest outside -workers.)

Hmm.  I'd be inclined to say that, on the contrary, they wouldn't be
of much interest /inside/ -workers, since everyone on workers is
either using the public CVS tree, or keeping track of the patches
themselves.  And it's a well-known phenomenon that these days there
are lots of people who like to live on the bleeding edge without
necessarily actively participating in development, usually because
they like having all the latest bells and whistles.  Many software
projects spring to my mind which make daily snapshot tarballs (and
even binary builds) available for this reason.  I also already know
several people that make use of these snapshots.

The only serious problem I see with zsh is that the number of people
that use it doesn't do justice to its quality.  I would like to see it
having much more exposure to the community in general; personally I
find it a crying shame that not many people reap the benefits of such
a wonderful shell, but even if a developer isn't particularly bothered
by this, he should still agree that exposure is a good thing simply
because this means more testing of the code.  This all applies
/especially/ to the development version, since the `bleeding edge
fans' I mentioned above are a particularly valuable resource to
developers if harnessed properly.

So that's why I bothered setting up these snapshots, and considering
the ahem, not exactly high level of traffic on zsh-announce, why I
thought it would be worthwhile mentioning there.  I guess I'll just
mention it on zsh-users instead.

Sorry, I keep diluting the patch/post ratio.  I'll shut up now :-)

P.S. No answers about the out of date website yet?


  reply	other threads:[~1999-11-30 15:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-30 14:14 Adam Spiers
1999-11-30 14:23 ` Zefram
1999-11-30 15:10   ` Adam Spiers [this message]
1999-11-30 15:25     ` Clint Adams
1999-12-01  9:17 Sven Wischnowsky

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=19991130151010.B28928@thelonious.new.ox.ac.uk \
    --to=adam@spiers.net \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).