Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 11528 invoked by uid 6000); 12 Jan 1998 03:58:34 -0000 Received: (qmail 10998 invoked from network); 12 Jan 1998 03:53:11 -0000 Received: from twinlark.arctic.org (204.62.130.91) by taz.hyperreal.org with SMTP; 12 Jan 1998 03:53:11 -0000 Received: (qmail 23516 invoked by uid 500); 12 Jan 1998 04:06:14 -0000 Date: Sun, 11 Jan 1998 20:06:14 -0800 (PST) From: Dean Gaudet To: new-httpd@apache.org Subject: Re: and while I'm pissing people off (fwd) In-Reply-To: Message-ID: X-Comment: Visit http://www.arctic.org/~dgaudet/legal for information regarding copyright and disclaimer. Organization: Transmeta Corp. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org On Thu, 8 Jan 1998, Gregory A Lundberg wrote: > Let's choose our language very carefully here. Say rather that you > 'accept the patch for consideration but cannot include it in the released > code'. There's an almost-empty apply-to heiracrchy at ftp.apache.org. At > a minimum, your users deserve a note thanking the submitter and having > their patch placed there. The Group must encourage new submitters to, > first, submit and, second, work on the development tree if they're adding > features. Are you volunteering to maintain a contrib site? We do send notes, especially to those that that are submitted as PRs we put them in the suspended state with a note saying we're in feature freeze. But I don't see our behaviour on new-httpd as much different than say the behaviour on linux-kernel when patches are posted... Linus doesn't include everything, and he frequently misses things. Dean