Trusted maintainer policy notes (draft for discussion) (was Re: [ATTN maintainer] libunistring 1.3 needed)

On 10/01/2026 12:54, Jon Turney via Cygwin-apps wrote:
> On 10/01/2026 04:51, Marco Atzeri via Cygwin-apps wrote:
>> On 09/01/2026 23:59, Brian Inglis via Cygwin-apps wrote:
[...]
>>> Hi folks,
>>>
>>> With no response to this previous request, for a requirement to build 
>>> gettext under CI, and a new release 1.4.1 available upstream, would 
>>> anyone have an issue
>>> with my releasing an NMU?
>>>
>>
>> Not at all.
>>
>>> With NMU perms, can I push to libunistring main branch and deploy?
>>>
>>
>> No idea.
> 
> Yes.
> 
> This probably needs better documenting, but for the moment [1].
> 
> [1] https://cygwin.com/pipermail/cygwin-apps/2023-May/042910.html


I've summarized that email, along with a few others on a similar subject 
I've written, and given it a home at [1], in an effort to capture the 
kind of process I try to follow (most of the time).

Please say if there's anything shocking, obviously missing or wrong 
there! Or if you have any comments, generally.

[1] https://cygwin.com/packaging/trusted-maintainer-policy-manual.html