Date: Thu, 29 Apr 2021 20:56:15 +0200 From: Ronald Klop <ronald-lists@klop.ws> To: freebsd-ports@freebsd.org Subject: Re: security/luasec maintainer not responding Message-ID: <d3e46d03-8eab-eebe-d17d-0350ef6c3350@klop.ws> In-Reply-To: <20210430.025453.1815556892303121104.yasu@utahime.org> References: <a57e593a-6fbe-5ac8-7e49-bf67b4671169@beingboiled.info> <20210430.025453.1815556892303121104.yasu@utahime.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/29/21 7:54 PM, Yasuhiro Kimura wrote: > From: Thomas Morper <thomas@beingboiled.info> > Subject: security/luasec maintainer not responding > Date: Thu, 29 Apr 2021 19:42:35 +0200 (CEST) > >> Second: how do you deal with this situation in general? I think I've asked >> this question before, but the results were somewhat inconclusive. When is >> a port considered unmaintained despite formally having a maintainer and >> how do you either mark it as unmaintained or assign a new maintainer with >> the least amount of work for anyone involved? > > 1. Submit patch to change MAINTAINER of the port in question. > 2. Wait for timeout (for about a month). > 3. Ask committers for commiting the patch. > > --- > Yasuhiro Kimura > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > There is documentation about this: https://docs.freebsd.org/en_US.ISO8859-1/books/porters-handbook/makefile-maintainer.html Regards, Ronald.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d3e46d03-8eab-eebe-d17d-0350ef6c3350>