Date: Mon, 06 Feb 2017 12:39:57 +0100 From: "Julian H. Stacey" <jhs@berklix.com> To: Kurt Jaeger <lists@opsec.eu> Cc: Jochen Neumeister <joneum@bsdproject.de>, "freebsd-ports@freebsd.org" <freebsd-ports@FreeBSD.org> Subject: Re: No reaction - what can I do? Message-ID: <201702061140.v16Bdv6j015090@fire.js.berklix.net> In-Reply-To: Your message "Mon, 06 Feb 2017 11:55:39 %2B0100." <20170206105539.GI13006@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Reference: > From: Kurt Jaeger <lists@opsec.eu> > Date: Mon, 6 Feb 2017 11:55:39 +0100 Kurt Jaeger wrote: > Hi! > > > > Is it normal that maintainers / committer will not respond? > [...] > > https://www.freebsd.org/portmgr/policies_contributors.html > > "The time limit for a maintainer to respond to a PR is two weeks. > > After that period, ....." > > The problem in this case is that nobody suggested a solution, so > what does the timeout help ? Purpose of Timeouts is to remove a Maintainer that is not responding &/or maintaining. Timeout works in my experience, eg I've both been removed from port[s] when not having time to respond & maintain, & on other ports after MAINTAINER= was zeroed out, I've been invited to become Maintainer, which put pressure on me spend more time researching & finding a solution. Zeroing out a Maintainer invites entire ports user base to volunteer for that port, & saves a Maintainer being further pestered for something they simply have no further time to maintain, & saves Ports Mgr & users writing enquiries for all eternity. > > -- > pi@opsec.eu +49 171 3101372 3 years to go ! > Cheers, Julian -- Julian Stacey, BSD Linux Unix Sys Eng Consultant Munich Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, quoted-printable. http://berklix.eu/brexit/#stolen_votes
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201702061140.v16Bdv6j015090>