Google Code In Schedule and Tasks
joel.sherrill at OARcorp.com
Wed Oct 23 20:12:07 UTC 2013
On 10/23/2013 2:42 PM, Gedare Bloom wrote:
> On Wed, Oct 23, 2013 at 2:46 PM, Joel Sherrill
> <joel.sherrill at oarcorp.com> wrote:
>> 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?
Per Amar, Sphinx/REST is a superset of asciidoc. That is supposed
to be easy to process in web and database programs. As we head to
using these as requirements, my long term goal is to trace them to
code and tests. That will require processing them somehow.
And.. I am begging for help defining that traceability process
and automated management so we have high quality SW processes but
don't overburden ourselves.
>> + 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?
Yes. If we prioritize the BSPs and define the pattern. :)
> By the way, a request was made for a "search" bar for the generated
> html from doxygen.
Hmm.. that should be just a configuration setting. If someone knows
it, just post what to change.
>> + 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?
The POSIX specification states where to put it. We know which files
need to have it added. Our intern got that far and fixed some.
Beyond that, we taught him cscope to find if there were architecture
specific implementations to touch.
This requires instructions to be written but we did this task with
>> + Add attribute notnull as appropriate to (a) Classic API.
>> Consider similar task on POSIX and newlib.
No comments? :)
>> + 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
> Good idea.
I thought so.
>> 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 OARcorp.com 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 rtems.org
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill at OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
More information about the devel