[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[address@hidden: [IMPORTANT] Ideas for Summer of Code 2016]

From: Samuel Thibault
Subject: [address@hidden: [IMPORTANT] Ideas for Summer of Code 2016]
Date: Wed, 10 Feb 2016 19:10:58 +0100
User-agent: Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30)


Any ideas/mentors for the summer of code?


----- Forwarded message from Giuseppe Scrivano <gscrivano@gnu.org> -----

From: Giuseppe Scrivano <gscrivano@gnu.org>
To: summer-of-code@gnu.org
Subject: [IMPORTANT] Ideas for Summer of Code 2016
Reply-To: summer-of-code@gnu.org

Hi everyone!

Google is accepting applications for the next Summer of Code and as
usual we are going to apply for it.

We should start thinking about a list of ideas for the next Summer of
Code and potential mentors.

This is the list of ideas we had last year:


Is there anything left undone that can be reused this year?

Please start sending ideas to add to the page and link them to the
potential mentors that can help with it.

Please send the html snippet for the ideas (look at the html for the
previous year to get an idea), so that it can be embedded in the page as
it is.


----- End forwarded message -----

Now, it we had this sort of thing:
  yield -a     for yield to all traffic
  yield -t     for yield to trucks
  yield -f     for yield to people walking (yield foot)
  yield -d t*  for yield on days starting with t
...you'd have a lot of dead people at intersections, and traffic jams you
wouldn't believe...
(Discussion in comp.os.linux.misc on the intuitiveness of commands.)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]