> On 3 May 2021, at 12:17, David Demelier <markand@malikania.fr> wrote:
> 
> On Mon, May 03, 2021 at 12:37:15PM +0200, Jakub Jirutka wrote:
>> Hi David,
>> I mostly agree with you, but I think that 2 weeks is too long time
> 
> I think this could be discussed but two weeks can be very short too. If
> someone is on a vacation it may not have any kind of time to review a
> merge request depending on the change.
> 
> Perhaps we can set a number of timeout depending on the nature of the
> merge request.
> 
>> That’s specifically why a maintainer should always add documentation
>> comments into APKBUILD! If you, as a maintainer, have a knowledge of
>> some non-standard/unexpected and non-obvious thing important for the
>> future upgrades, you should document it (for example [1]). Also, if
>> some dependencies are tightly coupled, you should specify the required
>> version range (e.g. `depends="foo>=3.5.0"` or `depends="foo=~3.5.5"`).
>> Maintainers should share important knowledge (comments in APKBUILD)
>> and document all non-obvious changes (commit messages), not keep it
>> for themselves.
> 
> You're entirely right on that point. I'll also update my APKBUILD to
> include any useful notes too.
> 
> PS: you seemed have replied only to me so I add a CC to the list because
> you've shared interesting points as well.
> 
> -- 
> David

Hi,
I would like to add there is the other problem of packages that list a maintainer where the maintainer is no longer actively maintaining the package.

If there was an authorisation period with timeout, it would make it clear then if no response was received that they no longer wished to maintain it or there contact details were wrong.

Duncan

Sent from my iPad