zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: Zsh hackers' list <zsh-workers@zsh.org>
Subject: Pruning developers' list
Date: Thu, 16 Aug 2018 09:31:34 +0100	[thread overview]
Message-ID: <20180816083136eucas1p2a1645c52d42d74262e5fb872f31144aa~LUDdbhDR41781317813eucas1p2f@eucas1p2.samsung.com> (raw)
In-Reply-To: <CGME20180816083136eucas1p2a1645c52d42d74262e5fb872f31144aa@eucas1p2.samsung.com>

Just looked at the zsh developers in the Sourceforge project, and there
a number of active users, which is great, but there are also a number of
people I haven't heard of in these parts for a number of years.  Rather
than let them hang on for all eternity I'll probably just remove them.
This is the only warning --- if they're not reading this list any more
then they shouldn't be there --- but I'll leave it a couple of weeks.

Please let me know if you are still around and still wish to continue,
or have reasons to suspect someone is still around and still interested.

There's no intention to remove anyone for any reason other than
defunctness.

This is probably a quite conservative list, actually.  I think there are
a number of others (if any of those with admin access, who should know
who they are, think there are others that can go let me know).
Adding people back is an easy job anyway.

     Chmouel Boudjnah (chmou)
     Motoi WASHIDA (wm3)
     Felix Rosencrantz (f_rosencrantz)
     Adam Spiers (adamspiers)
     Tanaka Akira (akr)
     Doug Kearns (dkearns)
     Andrey Borzenkov (bor)
     Paul Ackersviller (packersv)
     Sven Wischnowsky (wischnow)

Cheers
pws


           reply	other threads:[~2018-08-16  8:31 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CGME20180816083136eucas1p2a1645c52d42d74262e5fb872f31144aa@eucas1p2.samsung.com>]

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='20180816083136eucas1p2a1645c52d42d74262e5fb872f31144aa~LUDdbhDR41781317813eucas1p2f@eucas1p2.samsung.com' \
    --to=p.stephenson@samsung.com \
    --cc=zsh-workers@zsh.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.
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).