From owner-freebsd-current@FreeBSD.ORG Wed Oct 24 17:24:13 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D2417F82; Wed, 24 Oct 2012 17:24:13 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9E86C8FC08; Wed, 24 Oct 2012 17:24:12 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id b5so1579434lbd.13 for ; Wed, 24 Oct 2012 10:24:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HOzwriNDMu+P+uMcqIMey6HRuzC0/Gt0jOJwjuka1fA=; b=ZPlCYlBjn9Dj6eLIePWLXJG/wb6BGTOvuAAb54CQo1IW9oJQAr+/HHC3k87N3tVFJs vJJp0E/S5GMUOlH/0w4+LiHqprQRF78K6f3/af+Q43EXHwqgb/t9sECvIACTfyn8ypDv JxmPreBCKg7/IzI+fDtrX8IJpc7dTpoIL57hkqsxeFjx7YbnAl5zqSpW8OYQbShqkEaE VxnAG2sa0asD+xcMK2trPQ8meajogDPTrRWmFiMcI4YttfW7Jkblre4KrE3yypEqUGHS 0Ez+2uJIP0/SZO8zjXW9X/Gtuwn2rzcI+D7t00OZThSwj8blYStHLZmJBgMAk1r83y3j A8Rw== MIME-Version: 1.0 Received: by 10.152.104.115 with SMTP id gd19mr15216952lab.13.1351099451004; Wed, 24 Oct 2012 10:24:11 -0700 (PDT) Received: by 10.152.1.193 with HTTP; Wed, 24 Oct 2012 10:24:10 -0700 (PDT) In-Reply-To: <20121024111144.GF82606@e-new.0x20.net> References: <20121016101957.GB53800@FreeBSD.org> <20121022174457.GB59689@FreeBSD.org> <5086AC06.5070405@a1poweruser.com> <5214043c002ef030f59c2045344b8725.squirrel@webmail.ee.ryerson.ca> <20121024111144.GF82606@e-new.0x20.net> Date: Wed, 24 Oct 2012 19:24:10 +0200 Message-ID: Subject: Re: FreeBSD in Google Code-In 2012? You can help too! From: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= To: Lars Engels Content-Type: text/plain; charset=ISO-8859-1 X-Mailman-Approved-At: Wed, 24 Oct 2012 17:41:12 +0000 Cc: David Magda , freebsd-hackers@freebsd.org, Fbsd8 , "Wojciech A. Koszek" , Eitan Adler , freebsd-current@freebsd.org, freebsd-stable@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2012 17:24:13 -0000 On Wed, Oct 24, 2012 at 1:11 PM, Lars Engels wrote: > On Tue, Oct 23, 2012 at 03:59:07PM -0400, Eitan Adler wrote: >> On 23 October 2012 12:54, David Magda wrote: >> > On Tue, October 23, 2012 10:39, Fbsd8 wrote: >> >> >> >> The subject is Google Code-In and all the posted tasks are directed at >> >> creating documentation. Not one deals with coding any programs. If I was >> >> 15-17 years old I sure would not be interested in writing documentation. >> >> I would want to use and develop my coding skills. To that end there a >> >> lot of simple PR's waiting for attention. This is an target area that >> >> young coders would find more interesting. >> > >> > It would depend on what one's interests were. >> >> Google code-in is aimed at *coders* and there is an expectation of >> people writing *code*. >> >> The biggest complaint for GCI last year was "not enough coding tasks" > > What about creating a new port? That is some kind of coding. If we can > find some software that isn't ported, yet and not too hard to port (e.g. > the wanted ports page in the wiki) we could make a task proposal of it. > And one generic "create a port for a piece of software that hasn't been > ported, yet". > Feel free to add me as a mentor for such a task. Also related to that, what about writing a section about redports[1] in the porter's handbook[2]? And as a side question, shouldn't some (or all) of these tasks be listed also in JuniorTasks[3]? Just my two cents. [1] https://redports.org/ [2] http://www.freebsd.org/doc/en/books/porters-handbook/book.html [3] http://wiki.freebsd.org/JuniorJobs