zsh-announce moderators still alive?

zsh-announce moderators still alive?

[Adam Spiers]

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?

Re: zsh-announce moderators still alive?

[Zefram]

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.)
Peter is also a moderator.

-zefram

Re: zsh-announce moderators still alive?

[Adam Spiers]

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?

Re: zsh-announce moderators still alive?

[Clint Adams]

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

For "normal" users, snapshots become less useful when there are
frequent releases ("release early, release often").  For all the
bleeding edge fans there are those that want stability.  Bart isn't
maintaining 3.0 to stroke his ego; there are plenty of people that
want protection from the craziness of the development tree.

I like the fact that I can get a snapshot of Tanaka's CVS repository
anytime I want and not have to apply patches by hand, but for the
casual zsh user, only bugfixes are important.  Witness the confusion
of someone running a modularized 3.1.6-pws-10 who is hitting TAB
and not getting any results because no completion modules are loaded.

Re: zsh-announce moderators still alive?

[Sven Wischnowsky]

Adam Spiers wrote:

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

Just had a look at your published .zshrc. Some styles have now been
changed to boolean ones and for those `yep' is not treated as the
value `true'....

And the parameters should now be replaced with:

# {{{ Common usernames

# compstyle '*' users  tom dick harry

# }}}
# {{{ Common hostnames

compstyle '*' hosts  localhost sunsite.doc.ic.ac.uk

# }}}
# {{{ (user,host) pairs

# All my accounts:
# compstyle '*:my-accounts' users-hosts \
#    joe:                               \
#    {joe,root}:mymachine.com           \
#    jbloggs:myothermachine.com
#

# Other people's accounts:
# compstyle '*:other-accounts' users-hosts \
#    bob:                                  \
#    {fred,root}:hismachine.com            \
#    vera:hermachine.com
#

# }}}
# {{{ (host, port, user) triples for telnet
#
# compstyle '*::telnet:*' hosts-ports-users \
#    host1::user1                           \
#    host2::user2                           \
#    mail-server:{smtp,pop3}:               \
#    news-server:nntp:                      \
#    proxy-server:8000:
# }}}

Or something like that.

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de