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

[Sebastian Huber]

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 the tickets with some notes on how to do it. Open question: 
How do we document the API removals? Add a new chapter? Keep the 
directive documentation as is and just mention that this directive is 
obsolete in 4.11 and removed in 4.12?


--
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  : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Sebastian Huber]

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  : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Gedare Bloom]

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
 wrote:
> 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  : sebastian.hu...@embedded-brains.de
> PGP : Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Joel Sherrill]

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 will add them soon.

Can a procedure for deprecating a feature be added? Include  marking it as
deprecated with the warning, filing a ticket with one final release first
it to remain in, then removing it.

It may also be an opportunity to have a prepaid for removing a test. That
has the straightforward git commands but should mention configure.ac
possibly, Makefile.am and a search through BSP test configurations.

Having these procedures as we move forward should be a good thing and the
GCI procedure can reference them.

> On Mon, Dec 14, 2015 at 7:46 AM, Sebastian Huber
>  wrote:
> > 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  : sebastian.hu...@embedded-brains.de
> > PGP : Public key available on request.
> >
> > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
> >
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Gedare Bloom]

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 two tasks to "investigate/fix" the tickets and see what
>> students do with it. I will add them soon.
>
> Can a procedure for deprecating a feature be added? Include  marking it as
> deprecated with the warning, filing a ticket with one final release first it
> to remain in, then removing it.
>
Well, we started doing this with notepads and task variables. I don't
know how far we got in documenting the procedure itself though.

> It may also be an opportunity to have a prepaid for removing a test. That
> has the straightforward git commands but should mention configure.ac
> possibly, Makefile.am and a search through BSP test configurations.
>
> Having these procedures as we move forward should be a good thing and the
> GCI procedure can reference them.
>
>> On Mon, Dec 14, 2015 at 7:46 AM, Sebastian Huber
>>  wrote:
>> > 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  : sebastian.hu...@embedded-brains.de
>> > PGP : Public key available on request.
>> >
>> > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>> >
>> ___
>> devel mailing list
>> devel@rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Gedare Bloom]

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 efforts. I think a great task would be a
CFS "Getting Started" Tutorial which should be done by a relatively
advanced student and build from the RTEMS Getting Started

You can get a sense of the kinds of tasks at:
https://devel.rtems.org/wiki/GCI/Projects



Gedare

On Sun, Dec 6, 2015 at 10:41 AM, Mathew Benson  wrote:
> Is there a web page that lists the projects?  I had tentatively volunteered 
> as a mentor, not really knowing what to expect.
>
> Sent from my iPhone
>
>> On Dec 5, 2015, at 7:59 AM, Gedare Bloom  wrote:
>>
>> Hello Everyone,
>>
>> This is a friendly reminder that GCI starts soon. Please be prepared
>> for a possible flood of new users and questions as high schoolers
>> attempt to work with different parts of RTEMS Project. If you see a
>> question on the mailing list or IRC that you may know how to answer,
>> please don't hesitate to give back by helping these students to find
>> answers.
>>
>> If anyone is able/willing to spend a few minutes each day answering
>> questions, we would really like the extra hands to help "mentor"
>> students doing tasks. Mentoring GCI is basically just answering a few
>> questions or directing the student to someone who might have the
>> answer, or to devel mailing list. Let me or Joel know if you can
>> participate!
>>
>> Thanks, and Happy Holidays to everyone.
>> Gedare
>> ___
>> users mailing list
>> us...@rtems.org
>> http://lists.rtems.org/mailman/listinfo/users
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel