Changes between Initial Version and Version 1 of Ticket #3892


Ignore:
Timestamp:
02/29/20 05:58:45 (4 years ago)
Author:
Amar Takhar
Comment:

Finish project, some current tools may be missing.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #3892 – Description

    initial v1  
    1212A qualified developer for this project does not need to know anything about RTEMS or an RTOS in general.
    1313
     14----
    1415
    1516= Project =
    … …  
    2930 * Tutorial using new Python utility for running code on hardware.
    3031
     32=== What you will learn ===
     33
     34 * How to properly test Python software.
     35 * Using code coverage tools.
     36 * Using performance tools.
     37 * Writing technical documentation both in and out of source.,
     38 * Writing a beginner tutorial from a technical perspective.
     39 * Library/API design and consumption.
     40 * Using modern documentation tools.
     41
    3142
    3243== Prerequisite ==
    … …  
    3849
    3950
    40 == Good to Have ==
     51== Good to have ==
    4152
    4253None of these are required but having them will strengthen a candidates chances of being accepted.
    … …  
    4758
    4859
    49 == Current Tools ==
     60== Current tools ==
     61
     62The following tools are among the programs that current exist that need to be worked on.
     63
     64  * [https://git.rtems.org/rtems-tools/ rtems-run]
     65  * [https://git.rtems.org/rtems-tools/ rtems-test]
     66  * [https://git.rtems.org/rtems-tools/ tftp proxy]
     67  * [https://git.rtems.org/rtems-source-builder/ rtems-source-builder]
    5068
    5169
    52 == New Tools ==
     70
     71== New tools ==
    5372
    5473Currently, low-level tools exist that help with running binaries on real hardware.  However RTEMS lacks a high level management utility for configuring `tftp-proxy`, `rtems-test`, `rtems-run` and `ser2net`.