From owner-freebsd-hackers@FreeBSD.ORG  Wed Jan 18 17:48:24 2012
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 94598106566C;
	Wed, 18 Jan 2012 17:48:24 +0000 (UTC)
	(envelope-from julian@freebsd.org)
Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16])
	by mx1.freebsd.org (Postfix) with ESMTP id 5E6DB8FC0C;
	Wed, 18 Jan 2012 17:48:24 +0000 (UTC)
Received: from julian-mac.elischer.org (c-67-180-24-15.hsd1.ca.comcast.net
	[67.180.24.15]) (authenticated bits=0)
	by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id q0IHmKmo002931
	(version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO);
	Wed, 18 Jan 2012 09:48:20 -0800 (PST)
	(envelope-from julian@freebsd.org)
Message-ID: <4F170623.4080006@freebsd.org>
Date: Wed, 18 Jan 2012 09:49:23 -0800
From: Julian Elischer <julian@freebsd.org>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US;
	rv:1.9.2.25) Gecko/20111213 Thunderbird/3.1.17
MIME-Version: 1.0
To: Robert Watson <rwatson@freebsd.org>
References: <alpine.BSF.2.00.1112211415580.19710@kozubik.com>	<op.v78i3yxi34t2sn@tech304>
	<4F15C44F.1030208@freebsd.org>	<1326836797.1669.234.camel@revolution.hippie.lan>	<4F16019F.2060300@FreeBSD.org>	<1326843399.1669.249.camel@revolution.hippie.lan>	<4F160B99.1060001@FreeBSD.org>	<CADWvR2jdeu6R+mX1n2Uz1WUBcZ=BKWSDB4nR-rEv_P4jAZg3HQ@mail.gmail.com>	<4F16900A.90905@FreeBSD.org>
	<alpine.BSF.2.00.1201181121010.51158@fledge.watson.org>
In-Reply-To: <alpine.BSF.2.00.1201181121010.51158@fledge.watson.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Ian Lepore <freebsd@damnhippie.dyndns.org>,
	Igor Mozolevsky <igor@hybrid-lab.co.uk>,
	Andriy Gapon <avg@freebsd.org>, freebsd-hackers@freebsd.org
Subject: Re: FreeBSD has serious problems with focus, longevity,
	and lifecycle
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jan 2012 17:48:24 -0000

On 1/18/12 3:32 AM, Robert Watson wrote:
>
> Another possibility is to get some combination of {The FreeBSD 
> Foundation, iX Systems, ...} to trawl the bug report database in a 
> more official capacity. The problem there is that this will be a 
> high burn-out job.  I'll bring it up at the next Foundation board 
> meeting, especially after a bumper year of fund-raising, and see 
> what we can do.


we really need a bud-submitting-user advocate..

Someone (need not have a commit bit) who doesn't take charge of the 
patch, but, rather,
acts as a project manager in hte process of getting it in.
i.e. finding, and then pinging the approriate developer, and 
occasionally nagging them or
finding an alternate dev if the first choice is unresponsive.

diplomatic skill would be important..  maybe a woman might be best in
this job as the developers tend to not want to be rude to women :-)  .


>
> Robert
> _______________________________________________
>