Date: Wed, 15 Aug 2012 00:47:34 +0200 From: Radim Kolar <hsn@filez.com> To: Eitan Adler <lists@eitanadler.com> Cc: Chris Rees <crees@freebsd.org>, freebsd-ports@freebsd.org Subject: Re: maintainer timeout for FreeBSD commiters Message-ID: <502AD586.2090006@filez.com> In-Reply-To: <CAF6rxgng6x3jFm9ZCDCUDnnCQrnQBvKezyu3zE2uH=0QrY3u3g@mail.gmail.com> References: <50017C97.3050200@filez.com> <CADLo83_a=qOqTgGQF%2BLSYyGDaJoT6B2vF9JGV=a2ZHRXRyR6Pw@mail.gmail.com> <CAF6rxgng6x3jFm9ZCDCUDnnCQrnQBvKezyu3zE2uH=0QrY3u3g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/165939 http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/169910 > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/166488 > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/167289 > Have you reminded them by email recently? Apache@ is a team, so it's > a little uncertain where timeouts and approval stands with them. I mailed them, after 1 month no change. I would not bother with creating patches next time. I have same experience with pretty much every open source project, everybody talks on list, nobody works. If i send patch, it takes months to review even 1 or 2 line patch. Fork is necessity for any serious development.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?502AD586.2090006>