Notice: We have migrated to GitLab launching 2024-05-01 see here: https://gitlab.rtems.org/

Changes between Version 469 and Version 470 of Developer/OpenProjects


Ignore:
Timestamp:
02/14/19 15:03:04 (5 years ago)
Author:
Gedare Bloom
Comment:

Flatten old project descriptions. Add "executive" project section generated from tickets.

Legend:

Unmodified
Added
Removed
Modified
  • Developer/OpenProjects

    v469 v470  
    4444
    4545=== Testing Projects ===
     46Testing a large body of software like RTEMS is in a continual state of improvement.  There is always a need for more test cases and easier ways to run them all and decode the results.  In addition, we want to be  able to run all tests on as many hardware and simulator configurations as possible.  Testing doesn't sound exciting to most people but when you combine the breadth of what we need to test with our desire for 100% instruction and branch path coverage, you get some very interesting and challenging work.
     47
    4648[[TicketQuery(status!=closed, keywords~=SoC testing, format=table, col=summary|owner, order=priority|id)]]
    4749
    4850
    4951=== Development Ecosystem Projects ===
     52RTEMS applications are cross-compiled on a development host to produce executables that are transferred to and executed on target systems.  The projects in this section focus on the host side of that equation.  This means they will run on a developer's computer and possibly communicate with embedded hardware.
     53
    5054[[TicketQuery(status!=closed, keywords~=SoC ecosystem, format=table, col=summary|owner, order=priority|id)]]
    5155
     
    5357[[TicketQuery(status!=closed, keywords~=SoC API, format=table, col=summary|owner, order=priority|id)]]
    5458
     59=== Executive (!SuperCore, SuperCoreCPU, libcpu) a.k.a. kernel ===
     60
     61[[TicketQuery(status!=closed, keywords~=SoC executive, format=table, col=summary|owner, order=priority|id)]]
     62
    5563=== Runtime Statistics Projects ===
     64
    5665[[TicketQuery(status!=closed, keywords~=SoC statistics, format=table, col=summary|owner, order=priority|id)]]
    5766
    5867=== rtems-libbsd ===
    5968[[TicketQuery(status!=closed, keywords~=SoC libbsd, format=table, col=summary|owner, order=priority|id)]]
     69
    6070
    6171== Wiki Listed Open Projects ==
     
    7080----
    7181
    72 = Converting Projects To Tickets =
     82= Old Project Descriptions =
    7383
    74 We have started converting each of the projects listed here to tickets. Any help in the process is appreciated.
     84We used to describe open projects using a link to the project page and a short text description, but now we use tickets to describe open project ideas. Most of the projects that have interest from a mentor or the community have been converted. The remaining project descriptions in this section have not been converted yet, and may or may not be of interest. Please ask on the devel@rtems.org mailing list if you have interest in any of these projects. Project descriptions that are determined interesting to RTEMS Project should be converted to a Trac Ticket, while the descriptions deemed uninteresting should be moved to the Obsolete Projects section at the bottom of this page.
    7585
    76 Projects that have the 'strike-through' font have been moved to Trac Tickets.
    77 
    78 = Testing =
    79 
    80 Testing a large body of software like RTEMS is in a continual state of improvement.  There is always a need for more test cases and easier ways to run them all and decode the results.  In addition, we want to be  able to run all tests on as many hardware and simulator configurations as possible.  Testing doesn't sound exciting to most people but when you combine the breadth of what we need to test with our desire for 100% instruction and branch path coverage, you get some very interesting and challenging work.
    81 
    82 Some of the identified activities which would augment our testing capabilities are listed here:
     86* Testing
    8387 *  ''[wiki:Projects/Open/TestSpecification RTEMS Test Specification]'' - Develop a formal test specification.
    8488 *  [wiki:Projects/Open/TestScreenValidation RTEMS Test Screen Validation] - Create a tool to validate test output.
     
    8993 *  ''[wiki:Projects/Open/Fault_injection Fault tolerance]'' - get a fault injection tool to work with RTEMS and create tutorials and examples.
    9094
    91 = Development Ecosystem =
    92 
    93 RTEMS applications are cross-compiled on a development host to produce executables that are transferred to and executed on target systems.  The projects in this section focus on the host side of that equation.  This means they will run on a developer's computer and possibly communicate with embedded hardware.
    94 
    95 The following areas have been identified for projects related to improving RTEMS development:
    96 
     95* Development Ecosystem
    9796 * [wiki:Projects/Open/ConfigGUI Config GUI (Python)] - GUI for configuring RTEMS build.
    9897 * [wiki:Projects/Open/BuildVariables Build Variables (Python)] - Add bounds checking for all build options as well as cleanup.
     
    109108 * [wiki:Projects/Open/ArgoUML ArgoUML] - UML for RTEMS.
    110109
    111 = RTEMS Run-Time Oriented =
    112 
    113 The projects in this category are more focused on the development of software that runs on RTEMS on target hardware.
    114 
    115 = Executive (!SuperCore, SuperCoreCPU, libcpu): a.k.a. kernel =
    116 
     110* Executive (!SuperCore, SuperCoreCPU, libcpu): a.k.a. kernel
    117111 *  ''[wiki:Projects/Open/ImproveSMP Improvements to SMP support]'' - Propose an improvement to the existing [wiki:Developer/SMP SMP capabilities].
    118112 *  [wiki:Projects/Open/UnifiedInterrupts Unified Interrupts] - Unify the interrupt and PCI interfaces.
     
    120114 *  ''[wiki:Projects/Open/Paravirtualization  Paravirtualization]''-  Make RTEMS suitable to run as a guest in a hypervisor.
    121115
    122 = Run-Time Statistics =
    123 
     116* Run-Time Statistics
    124117 *  ''[wiki:Projects/Open/CPU_Statistics CPU Statistics]'' - Improvements to CPU Usage Statistics.
    125118 *  ''[wiki:Projects/Open/StackChecker Stack Checker]'' - Improvements to Stack Bounds Checker.
    126119
    127 = Board Support Package (BSP) =
    128 
     120* Board Support Package (BSP)
    129121 * [wiki:Projects/Open/EdisonBSP x86 Edison] - on hold due to unavailability of open information
    130122
    131 = API Layers (POSIX, Classic, SAPI) =
    132 
     123* API Layers (POSIX, Classic, SAPI)
    133124 *  [wiki:Projects/Open/OSEK OSEK] - Implement [http://portal.osek-vdx.org/ OSEK] automotive APIs.
    134125 *  [wiki:Projects/Open/ProgammableLogicController Programmable Logic Controller] - Enable RTEMS as a [http://en.wikipedia.org/wiki/Programmable_logic_controller Programmable Logic Controller (PLC)].
    135126 *  ''[wiki:Projects/Open/ARINC653API ARINC653 in RTEMS]'' - Implement ARINC-653 avionics APIs.
    136127
    137 = rtems-libbsd =
    138 
     128* rtems-libbsd
    139129 *  [wiki:Projects/TCP/IP_update  Update the RTEMS TCP/IP stack] - Ask about possibilities about Ethernet over USB and Wifi support.
    140130 *  [wiki:TBR/UserManual/USBStack  USB stack] - Ask about possible addition of other device types.
    141131
    142 = Languages =
    143 
     132* Languages
    144133 *  [wiki:Projects/Open/Mono Mono On RTEMS] - Add support for [http://www.mono-project.com Mono].
    145134 *  [wiki:Projects/Open/V8 Port V8 JavaScript Engine to RTEMS] - Add support for the [http://code.google.com/p/v8/ V8 Engine].
    146135 *  [wiki:Projects/Open/SWIGforRTEMS SWIG on RTEMS] - Add support for SWIG.
    147136
    148 = Libraries and Applications =
    149 
     137* Libraries and Applications
    150138 * [wiki:Projects/Open/InternetOfThings] Internet of Things (IoT) - Port IoT infrastructure
    151139 * [wiki:Projects/Open/PortMonkey Port Monkey HTTP Server] - Port the [http://monkey-project.com/ Monkey HTTP Server].