Google Code In Schedule and Tasks

Gedare Bloom gedare at
Wed Oct 23 19:42:16 UTC 2013

On Wed, Oct 23, 2013 at 2:46 PM, Joel Sherrill
<joel.sherrill at> wrote:
> Hi
> Checking the timeline for GCI...
> 28 Oct - deadline for applications
> 1 Nov  - organizations announced
> Our application is in. Thanks to those who helped me review
> and update the answers for the application.
> We now need to work on the task sets and update the wiki
> We need some bulk tasks. These are one where a single set of
> instructions can be applied to multiple sets of files. We
> got massive improvements to our Doxygen with students last
> year doing this. Ideas include:
> + Converting the original Classic API specifications (RTEID
>   or ORKID) into (a) Asciidoc and then (b) head those down the
>   path of being requirements.
Why convert to asciidoc?

> + Continuing to add Doxygen if we left files undone from last year.
We could expand the scope. Would it be worthwhile to start applying
doxygen to the BSPs?

By the way, a request was made for a "search" bar for the generated
html from doxygen.

> + Add restrict keyword as necessary to newlib .h files. [NOTE:
>   As scary as this is, OAR had a high school intern who started this.]
Is this easy to figure out where to put?

> + Add attribute notnull as appropriate to (a) Classic API.
>   Consider similar task on POSIX and newlib.
> + BRL-CAD had a standing task which each student could ONLY DO ONCE.
>   It would be to follow our GSOC hello world instructions and comment.
>   This puts more users through the procedure and lowers our entry
>   barrier.
Good idea.

> Coding tasks tend to not get taken but eliminate a warning is a good one.
> --
> Joel Sherrill, Ph.D.             Director of Research & Development
> joel.sherrill at        On-Line Applications Research
> Ask me about RTEMS: a free RTOS  Huntsville AL 35805
> Support Available                (256) 722-9985
> _______________________________________________
> rtems-devel mailing list
> rtems-devel at

More information about the devel mailing list