help / color / mirror / code / Atom feed
From: "Daniel Shahaf" <d.s@daniel.shahaf.name>
To: zsh-users@zsh.org
Subject: Re: Call for volunteers: Patch Manager
Date: Thu, 18 Feb 2021 17:28:38 +0000	[thread overview]
Message-ID: <a77e5385-6978-4249-8bef-11966bebebca@www.fastmail.com> (raw)
In-Reply-To: <CADjGqHvGch-bdeDAv1p-AWc7zkJJzErBU3ampro=cFQ5QtnAwQ@mail.gmail.com>

TJ Luoma wrote on Thu, 18 Feb 2021 01:42 +00:00:
> On Wed, Feb 17, 2021 at 6:30 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
> > Just as well to have someone of known competence. I at least would have to learn the job on the
> > job. Still, it would be nice to be able to make some sort of contribution given all the help I've
> > received.
> Exactly my thoughts. I wouldn't have known how to do the job, but I 
> would have been glad to do something to try to give back for all the 
> help I've received over the many years.

Hmm.  I appreciate the desire to give back, but I don't know how to
clarify the several descriptions I've already given.  Again, in
a nutshell, the patch manager (PM) should, at regular intervals, go
through [PATCH] threads and for each patch do:

case $state in
  (accepted-and-committed) :;;
  (rejected) :;;
  (not-yet-reviewed) ping;;
  (has-been-reviewed-and-is-awaiting-revised-submission) ping;;
  (*) DTRT;;

As to other ways to help, well, how about writing documentation patches?
They're very helpful, and not hard to write.  See Doc/Zsh/*.yo.  (Custom
syntax highlighting for Vim is in the tree.)

> Still, glad to have someone who knows what they're doing take the helm!



  reply	other threads:[~2021-02-18 17:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 20:21 Daniel Shahaf
2021-02-15 21:06 ` TJ Luoma
2021-02-15 22:20   ` Daniel Shahaf
2021-02-15 23:29     ` Ray Andrews
2021-02-17 22:36       ` Daniel Shahaf
2021-02-17 23:30         ` Ray Andrews
2021-02-18  1:42           ` TJ Luoma
2021-02-18 17:28             ` Daniel Shahaf [this message]
2021-02-18 23:16             ` Lawrence Velázquez
2021-02-22 16:39             ` Interactive menu completion bug Paul
2021-02-22 21:50               ` Bart Schaefer
2021-02-18 23:11         ` Call for volunteers: Patch Manager Lawrence Velázquez
2021-02-19 16:04           ` Daniel Shahaf

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a77e5385-6978-4249-8bef-11966bebebca@www.fastmail.com \
    --to=d.s@daniel.shahaf.name \
    --cc=zsh-users@zsh.org \


* 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


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