Changes between Version 120 and Version 121 of Developer/OpenProjects


Ignore:
Timestamp:
Mar 25, 2009, 4:42:20 AM (10 years ago)
Author:
JoelSherrill
Comment:

/* Small Projects */ Shorten and move to new page

Legend:

Unmodified
Added
Removed
Modified
  • Developer/OpenProjects

    v120 v121  
    6464
    6565
    66 These are small projects that could be tackled by anyone.  They are mostly projects which can easily be nibbled on in small work units. 
    67 = No Coding Required =
    68 
    69 
    70 The following requires no coding although it may help to be able to read C code:
    71 
    72  *  Improve the Wiki pages for the various [http://www.rtems.org/wiki/index.php/BoardSupportPackageInformation BSPs]
    73   *  There are approximately 100 boards supported by RTEMS.  Each board has a page in the Wiki and there is an standard Wiki Infobox. Most BSPs still do not have any information here, links to vendor information, or even a good description of the board.  This effort just requires a bit of web research and Wiki editing.
    74 
    75  *  Flesh out our POSIX API User's Guide
    76   *  RTEMS supports the POSIX 1003 standard following the "single process, multi-threaded" profile.  We have permission from The Open Group and IEEE to excerpt text from their standards (available online) for use in this manual if cited.  This manual is in the doc/posix_users directory in the source tree and by looking at it, I am sure you can find something that needs to be written.  The corresponding code is in cpukit/posix or cpukit/libcsupport.
    77 = Modest Coding Required =
    78 
    79 
    80 The following require only modest coding experience.  Remember you can test RTEMS on a simulator so no special hardware is required.
    81 
    82  *  Doxygen markup
    83   *  RTEMS predates Doxygen and thus our .h files were not created with Doxygen markup.  We have added this to a lot of files but would eventually like to see it in the score, rtems, posix, libcsupport, and libfs subdirectories of cpukit.  In much of the code, the information is there but not in Doxygen markup format.
    84 
    85  *  Writing test code
    86   *  There is a continual need for more test code.   We would like a timing test suite for the POSIX thread support that is comparable to the current Classic API timing test suite.  We expect this will eventually comprise about 50 different tests so could be tackled as a class project with the individual tests assigned to different people or groups.
     66These are small projects that could be tackled by anyone.  They are mostly projects which can easily be nibbled on in small work units.  They may require no coding or modest coding skill.  Some of these will require the ability to read code and analyse it.  Some of these will be good projects to tackle in an "Introduction to FOSS" class or as a class project by a student.  Individual tasks may also be useful for those new to RTEMS and looking to try a simple project to earn the ropes.  See [wiki:Developer/SmallProjects Small Projects] for details.
    8767= RTEMS Run-Time Oriented =
    8868