From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4024 invoked by alias); 6 May 2003 13:17:21 -0000 Mailing-List: contact ecos-maintainers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@sources.redhat.com Received: (qmail 4005 invoked from network); 6 May 2003 13:17:21 -0000 From: Mark Salter To: gary@mlbassoc.com Cc: ecos-maintainers@sources.redhat.com In-reply-to: <1052225944.30126.4370.camel@hermes> (message from Gary Thomas on 06 May 2003 06:59:04 -0600) Subject: Re: Patch policy References: <1052225944.30126.4370.camel@hermes> Message-Id: <20030506131719.AF3727885A@deneb.localdomain> Date: Tue, 06 May 2003 13:17:00 -0000 X-SW-Source: 2003-05/txt/msg00005.txt.bz2 > ** Disclaimer: I'm sure that I'm as guilty as anyone > There seems to be a gap [i.e. failing] in the response to > patches from outsiders. Sometimes they are handled quite > quickly, sometimes never. I think we need to establish > some policies on how to handle these efficiently. > In an ideal world, patches from outside our group would > be posted to a database which could be queried by anyone. > Maybe the easiest way to do this would be to forward the > patch to BugZilla. > At the very least, we should try and assign a patch to > a maintainer within some short period of time and then it's > that person's responsibility to take care of it - whatever > the outcome. As is, I see things come in that I'm comfortable > with that sometimes I take up, sometimes I leave by. In the > latter case, I simply assume that someone else will handle > it. I think this is the failing. I've been thinking about this as well. I'm not sure what the best policy approach is. Anyway, I'm going to take time out to do some testing with Pierre's patches today. I'll get them checked in or pushed back in the next day or two. --Mark