Date: Thu, 18 Sep 2008 20:01:57 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Jo Rhett <jrhett@netconsonance.com> Cc: freebsd-stable <freebsd-stable@FreeBSD.org>, Wesley Shields <wxs@FreeBSD.org>, Nathan Way <nathan@datanode.com>, Ben Kaduk <minimarmot@gmail.com> Subject: Re: Upcoming Releases Schedule... Message-ID: <alpine.BSF.1.10.0809181935540.16464@fledge.watson.org> In-Reply-To: <658B8861-1E78-4767-8D3D-8B79CC0BD45F@netconsonance.com> References: <1219409496.10487.22.camel@bauer.cse.buffalo.edu> <593618A3-56DA-4891-A4A0-690E9A9C5B32@netconsonance.com> <F17BE4F1F989BB4A81EB94C36712A9736F3493@dni-mail.datanode.com> <20080904133604.GB1188@atarininja.org> <CB36FE28-D125-4C22-B5DE-1001515DD8A6@netconsonance.com> <47d0403c0809051319r3c82f87bhdb15ce5b0167987a@mail.gmail.com> <alpine.BSF.1.10.0809061159410.28840@fledge.watson.org> <2742CAB1-8FF2-425D-A3B6-0658D7DB8F4D@netconsonance.com> <alpine.BSF.1.10.0809162043380.64176@fledge.watson.org> <0C2C7E9B-61E3-4720-B76F-4745A3C963DA@netconsonance.com> <alpine.BSF.1.10.0809180022580.13100@fledge.watson.org> <658B8861-1E78-4767-8D3D-8B79CC0BD45F@netconsonance.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 17 Sep 2008, Jo Rhett wrote:
> Please stop avoiding even considering what people are offering to you.
So far, this conversation has largely consisted of you telling us that you
don't like what we're doing and demanding that we change. Let's consider
three more productive avenues by which you can offer assistance with the
problem of how to increase branch support lifetimes:
(1) Become a contributor to the community by developing and maintaining
patches against unsupported branches, especially against older releases
such as 4.x and 5.x where the branches are open for commits but have
fallen out of support status. I can't promise the results will
immediately fall into the official project "umbrella", but consider Colin
Percival's freebsd-update as an example of what can be accomplished by
someone outside the project when they find a niche. What started out as
an external software project (freebsd-update) is now a core system update
tool, and Colin has gone from being a random guy with some code to our
security officer.
(2) Become a contributor to the community by identifying members of the
existing developer team for whom additional funding would enable them to
spend more time working on and supporting FreeBSD and providing that
funding. Consider approaching the FreeBSD Foundation formally to seek
matching grant funding for the project.
(3) Become a contributor to the community by working with an existing or new
company that provides support for FreeBSD commercially, and discussing
with them ways that they could provide support for branches past their
official EoL date for the project. Companies like FreeBSD Mall have
strong relationships with the project, and in the past have contributed
significantly to efforts such as release engineering. It's not hard to
imagine a company along those lines using something along th elines of a
support subscription to fund community-centered support for branches. And
those companies may be able to help you identify developers who can do the
work, as well as play an active role in seeking further customers with
similar interests.
Robert N M Watson
Computer Laboratory
University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.1.10.0809181935540.16464>