Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Subject: Re: Is Apache getting too patchy?
To: dev@httpd.apache.org
References: <38B6AA15-AB3C-47AC-B96D-7DA8094F99F9@jaguNET.com>
From: Jacob Champion <champion.p@gmail.com>
Message-ID: <562E5A1F.9080201@gmail.com>
Date: Mon, 26 Oct 2015 09:51:43 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <38B6AA15-AB3C-47AC-B96D-7DA8094F99F9@jaguNET.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

On 10/24/2015 08:49 AM, Jim Jagielski wrote:
> Thoughts? Comments?

Jim,

I'm somewhat on the outside looking in, as an httpd newbie. But my 
standard experience (it's happened two or three times now) is this:

1) Non-trivial patch is proposed to the list with calls for 
discussion/debate.
2) Nothing happens.
3) List is pinged for comments.
4) Silence.
5) Patch author either gives up or pings relentlessly until...
6) ...patch is applied directly to trunk without discussion.

This being a volunteer project, I don't actually mind steps 1-5 so much. 
You're busy people, and my patches shouldn't be priority one for anyone. 
I'm more concerned about step 6, where conversations wither on the vine 
in favor of just applying the patch and seeing what happens. I think 
that could contribute to the "cruft instead of cohesion" that you're seeing.

I'd rather not feel like I'm just annoying dev@ until you submit my 
stuff -- I want to *talk* about it, and improve the server.

HTH,
--Jacob