Re: Call for volunteers: Patch Manager

[Daniel Shahaf <d.s@daniel.shahaf.name>]

TJ Luoma wrote on Mon, Feb 15, 2021 at 16:06:42 -0500:
> On Mon, Feb 15, 2021 at 3:21 PM Daniel Shahaf <d.s@daniel.shahaf.name>
> wrote:
> 
> > You needn't be a zsh developer yourself; you just need to be able to follow
> > a patch thread, and have time once a week or so to review a few such
> > threads and reply with short reminders where needed.
> 
> By "follow a patch thread" do you mean:
> 
> 1. Read emails related to a topic and see that the conversation has stopped
> or slowed, but no resolution (closed or merged) has occurred.
> 
> or
> 
> 2. Be able to understand what a patch does and why it is important?
> 
> 
> I think I could do the former. I could not do the latter.
> 
> ~ Tj
> (not officially volunteering just yet, but wanting to understand what the
> 'job' entails)

Thanks for asking.  I mean #1.  The patch manager doesn't actually have to
understand what a patch does at either the implementation level or the
user-facing level; a patch manager just needs to be able to determine "This
patch has been committed", "This patch has been rejected", "This patch has not
yet been reviewed", etc..

There's also a write-up in
https://producingoss.com/en/share-management.html#patch-manager, which I
neglected to link to earlier.

Cheers,

Daniel
(By the way, sourceforge sends email notifications of each push to the
repository.  I assume it'll be possible for the patch manager to
subscribe to these notifications, if they wish.  That'll help them track
which patches have been committed.)