On Wed, Oct 24, 2012 at 1:11 PM, Lars Engels <lars.engels_at_0x20.net> wrote: > On Tue, Oct 23, 2012 at 03:59:07PM -0400, Eitan Adler wrote: >> On 23 October 2012 12:54, David Magda <dmagda_at_ee.ryerson.ca> 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/JuniorJobsReceived on Wed Oct 24 2012 - 15:24:13 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:31 UTC