Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 31 Jan 2010 23:21:51 -0800
From:      "R. Tyler Ballance" <tyler@monkeypox.org>
To:        Giorgos Keramidas <keramida@freebsd.org>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: Weekend PR smashing
Message-ID:  <20100201072150.GD30608@kiwi.sharlinx.com>
In-Reply-To: <877hr9ltym.fsf@kobe.laptop>
References:  <20100117213049.GA2259@kiwi.sharlinx.com> <877hr9ltym.fsf@kobe.laptop>

next in thread | previous in thread | raw e-mail | index | archive | help

--VMt1DrMGOVs3KQwf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable


On Fri, 22 Jan 2010, Giorgos Keramidas wrote:

> On Sun, 17 Jan 2010 13:30:50 -0800, "R. Tyler Ballance" <tyler@monkeypox.=
org> wrote:
> > Are there similar resources I've not stumbled across yet? I would like =
to help,
> > I have but one machine running -CURRENT and sporadic free time over the
> > weekends.
>=20
> Hi there.  I just noticed this post in among others in -hackers.  If you
> don't know about the bugbuster team already, you should check it out.
> There's a mailing list at freebsd-bugbusters and an IRC channel at the
> EFnet network.

Righteo, I stumbled across that shortly after my email to the list, I've be=
en
lurking in there since (rtyler).

>=20
> Since you are looking for pointers to get you started, the following may
> help a bit:
>=20
>   http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/
>   http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pr-guidelines/
>   http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/
>=20
> Finally, it's worth noting that it is not a huge problem if you only have
> weekend-time to contribute.  We welcome all the help we can get, so please
> feel free to jump in and help in any way you can with the existing bugs (=
or
> new ones that you have noticed).

I certainly get that impression, one of the things that concerns me is the
sheer number of PRs with patches that either have been committed without the
PRs being updated, or the patches are simply sitting idly in PRs. The list =
by
the bugbusters waiting for committers to check them out is pretty huge as w=
ell:

    http://people.freebsd.org/~linimon/studies/prs/recommended_prs.html

    http://people.freebsd.org/~linimon/studies/prs/prs_for_tag_patch.html


It's a little difficult to muster up too much motivation to fix issues when
the fixes will then sit waiting for committer review for months on end. Wit=
hout
annoying committers, is there any way I can help get patches "through" and
into the tree in less than a lunar cycle? ;)


Cheers,
-R. Tyler Ballance
--------------------------------------
 Jabber: rtyler@jabber.org
 GitHub: http://github.com/rtyler
Twitter: http://twitter.com/agentdero
   Blog: http://unethicalblogger.com


--VMt1DrMGOVs3KQwf
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)

iEYEARECAAYFAktmgQ4ACgkQFCbH3D9R4W+A6ACbBckvCoY9r0IyIy8yA38czdxU
lY4An2KsdkPrBn7mp9t4ANZA0gcj74sb
=y46j
-----END PGP SIGNATURE-----

--VMt1DrMGOVs3KQwf--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100201072150.GD30608>