Re: Google Code In (GCI) starting in 2 days

On 14/12/15 16:57, Gedare Bloom wrote: Yes, removing notepads and removing task variables are good tasks. They'll need a little more write-up yet, although we can start by opening up two tasks to "investigate/fix" the tickets and see what students do with it. I will add them soon. I updated

Re: Google Code In (GCI) starting in 2 days

Hello, are these two tickets suitable for a GCI task? http://devel.rtems.org/ticket/2493 http://devel.rtems.org/ticket/2494 -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail :

Re: Google Code In (GCI) starting in 2 days

Yes, removing notepads and removing task variables are good tasks. They'll need a little more write-up yet, although we can start by opening up two tasks to "investigate/fix" the tickets and see what students do with it. I will add them soon. On Mon, Dec 14, 2015 at 7:46 AM, Sebastian Huber

Re: Google Code In (GCI) starting in 2 days

On Dec 14, 2015 5:57 AM, "Gedare Bloom" wrote: > > Yes, removing notepads and removing task variables are good tasks. > They'll need a little more write-up yet, although we can start by > opening up two tasks to "investigate/fix" the tickets and see what > students do with it. I

Re: Google Code In (GCI) starting in 2 days

On Mon, Dec 14, 2015 at 11:09 AM, Joel Sherrill wrote: > > On Dec 14, 2015 5:57 AM, "Gedare Bloom" wrote: >> >> Yes, removing notepads and removing task variables are good tasks. >> They'll need a little more write-up yet, although we can start by >> opening up

Re: Google Code In (GCI) starting in 2 days

You just contribute what you can, when you can. Much of the work is just approving that a student finished a task, and a lot of the tasks are trivial to approve. Otherwise, if you would like to create specific CFS tasks for you to mentor that would be perfectly suitable and greatly improve our GCI