Changes between Version 13 and Version 14 of Developer/SmallProjects


Ignore:
Timestamp:
Dec 20, 2015, 1:10:40 AM (19 months ago)
Author:
Tan Gemicioglu
Comment:

Fixed broken links.

Legend:

Unmodified
Added
Removed
Modified
  • Developer/SmallProjects

    v13 v14  
    1414 *  Improve the Wiki (requires Wiki editing)
    1515  *  [wiki:TBR/Website/Board_Support_Packages BSPs]: 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.
    16   *  [wiki:Developer/OpenProjects Open Projects]: Create a template and prioritization for adding/updating open projects. See [wiki:Developer/OpenProjectTemplate Open Project Template]. Update all projects.
     16  *  [wiki:Developer/OpenProjects Open Projects]: Create a template and prioritization for adding/updating open projects. See [wiki:PageTemplates/ProjectDescriptionTemplate Open Project Template]. Update all projects.
    1717
    1818 *  Wikipedia presence
     
    2222  *  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.
    2323
    24  *  Use [http://www.languagetool.org| LaunguageTool] on RTEMS documentation, wiki pages, etc. to report spelling and grammar mistakes. If you start to tackle a large area, please help us make a checklist so we know what hasn't been checked.
     24 *  Use [http://www.languagetool.org LanguageTool] on RTEMS documentation, wiki pages, etc. to report spelling and grammar mistakes. If you start to tackle a large area, please help us make a checklist so we know what hasn't been checked.
    2525
    2626 *  Verify that every directive manual page indicates whether it can or cannot cause the current thread to be rescheduled.
    2727
    28  *  Replace the top level index.html for the [http://rtems.org/onlinedocs/doc-current/share/rtems/html/| RTEMS Documentation Set] with one that is a clickable image using the [http://rtems.org/wiki/index.php/File:RTEMSArchitecture.png| RTEMS Architecture figure OpenProjectTemplate].
     28 *  Replace the top level index.html for the [http://rtems.org/onlinedocs/doc-current/share/rtems/html/ RTEMS Documentation Set] with one that is a clickable image.
    2929= Modest Coding Required =
    3030
     
    3838  *  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.
    3939
    40   *  Write tests to improve [wiki:Projects/TestingImprovements  Test Coverage].  We want full object coverage for as much of RTEMS as possible.  In this light, there are areas which are under tested in the automated test suite.  This is an ongoing project with a variety of areas that need test cases written.  Please ask for a current coverage report and a recommended area you can tackle.
     40  *  Write tests to improve [wiki:Developer/Projects/Open/CoverageAnalysis  Test Coverage].  We want full object coverage for as much of RTEMS as possible.  In this light, there are areas which are under tested in the automated test suite.  This is an ongoing project with a variety of areas that need test cases written.  Please ask for a current coverage report and a recommended area you can tackle.
    4141
    4242 *  Add example uses of each Manager to User's Guide.  The C User's manual for the Classic API currently does not include example uses.  One part of this is letting readers know that counting semaphores may be used to manage a pool of resources and binary may be used for mutual exclusion or condition synchronization.  But the other part is moving it beyond the theoretical to show code and give examples of how this might be used in a real application.  For example, condition synchronization with binary semaphore to announce that an interrupt occurred to a waiting task.