From owner-freebsd-hackers@FreeBSD.ORG Tue Oct 23 14:30:01 2012 Return-Path: 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 C38E26F9; Tue, 23 Oct 2012 14:30:01 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id 3A3BA8FC12; Tue, 23 Oct 2012 14:29:49 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.5/8.14.5) with ESMTP id q9NETmIL072073; Tue, 23 Oct 2012 08:29:48 -0600 (MDT) (envelope-from freebsd@damnhippie.dyndns.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id q9NETPgG097080; Tue, 23 Oct 2012 08:29:25 -0600 (MDT) (envelope-from freebsd@damnhippie.dyndns.org) Subject: Re: FreeBSD in Google Code-In 2012? You can help too! From: Ian Lepore To: Erik Cederstrand In-Reply-To: <6CEA942D-3663-41DC-A919-584F664C67D9@cederstrand.dk> References: <20121016101957.GB53800@FreeBSD.org> <6CEA942D-3663-41DC-A919-584F664C67D9@cederstrand.dk> Content-Type: text/plain; charset="us-ascii" Date: Tue, 23 Oct 2012 08:29:25 -0600 Message-ID: <1351002565.1123.271.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "freebsd-hackers@freebsd.org" , "Wojciech A. Koszek" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Oct 2012 14:30:01 -0000 On Tue, 2012-10-23 at 12:39 +0200, Erik Cederstrand wrote: > Den 16/10/2012 kl. 12.19 skrev Wojciech A. Koszek : > > > (cross-posted message; please keep discussion on freebsd-hackers@) > > > > Those of you who have Wiki access, please spent 2 more minutes and submit > > straight to Wiki: > > > > 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? > Analyzing and fixing warnings is the last thing I'd assign to a young inexperienced programmer. It's far too easy (and tempting) to cast away warnings or otherwise treat the symptoms when what's really needed is to dig deeply into code (often including analyzing call chains) to evaluate the consequences of any changes. On the last 3 tasks in your list, I agree completely, just the sort of thing you'd assign to an intern or new junior engineer to get them started on a large existing project. -- Ian