From owner-freebsd-hackers@FreeBSD.ORG  Tue Oct 23 10:39:44 2012
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id 5CA24CA2;
 Tue, 23 Oct 2012 10:39:44 +0000 (UTC)
 (envelope-from erik@cederstrand.dk)
Received: from csmtp2.one.com (csmtp2.one.com [91.198.169.22])
 by mx1.freebsd.org (Postfix) with ESMTP id 14D818FC08;
 Tue, 23 Oct 2012 10:39:43 +0000 (UTC)
Received: from [192.168.1.18] (unknown [217.157.7.221])
 by csmtp2.one.com (Postfix) with ESMTPA id 333D4307A078;
 Tue, 23 Oct 2012 10:39:42 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: FreeBSD in Google Code-In 2012?  You can help too!
From: Erik Cederstrand <erik@cederstrand.dk>
In-Reply-To: <20121016101957.GB53800@FreeBSD.org>
Date: Tue, 23 Oct 2012 12:39:45 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6CEA942D-3663-41DC-A919-584F664C67D9@cederstrand.dk>
References: <20121016101957.GB53800@FreeBSD.org>
To: "Wojciech A. Koszek" <wkoszek@freebsd.org>
X-Mailer: Apple Mail (2.1499)
Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Tue, 23 Oct 2012 10:39:44 -0000

Den 16/10/2012 kl. 12.19 skrev Wojciech A. Koszek <wkoszek@freebsd.org>:

> (cross-posted message; please keep discussion on freebsd-hackers@)
>=20
> Those of you who have Wiki access, please spent 2 more minutes and =
submit
> straight to Wiki:
>=20
> 	http://wiki.freebsd.org/GoogleCodeIn/2012Tasks


There are lots of smallish tasks in the code-quality department:

* Analyze and fix Clang Static Analyzer warnings
* Analyze and fix compiler warnings to increase WARNS level
* Write regression tests for src/tools/regression
* Run include-what-you-use to clean up header inclusion
* Verify bugs with patches

I think they're too open-ended to enter in the wiki as-is, but I'd also =
like to not spam the wiki with lots of almost-identical tasks. What's =
the best way to suggest them for CodeIn?

Erik=