[[TOC(Developer/OpenProjects, depth=3)]] = Open Projects = Welcome! Whether you're here because of [wiki:GSoC Summer of Code (SOC)] or just want to scratch an itch to hack, we invite you to peruse our projects and ask about them on the [wiki:TBR/Website/RTEMSMailingLists RTEMS mailing list] or [wiki:Developer/IRC IRC]. If you plan to submit a proposal to do something for the RTEMS Project as part of a SOC, see [wiki:GSoC/GettingStarted Getting Started for SoC Students]. RTEMS projects span kernel hacking, adding support for a new board (BSP), improving the development environment, developing tests, and more. If you want to get your feet wet with RTEMS then check out our [wiki:Developer/SmallProjects small projects page] where you can find projects that require little coding skill and are appropriate for those new to RTEMS or open source software projects. If you are interested in one of these projects but are not able to code and test it yourself, consider sponsoring one of the core RTEMS developers to do it for you. Volunteering or sponsoring is how things get done -- users keep RTEMS development alive! Most of these projects will take between a few weeks and a few months of effort by a person who is familiar with the general use of GNU/Linux and GNU tools. Many RTEMS projects are done by student or volunteer coders, so we try to define small projects or subtasks that can be completed and committed individually. Most of the projects are feasible as a [wiki:GSoC Summer of Code] project. Since some projects have multiple steps, students should work with prospective mentors to define the scope of work in their proposal. Similarly, some projects might be a starting point for a class project or graduate thesis. == Overview == The order of projects in the ticket list does not reflect their importance, difficulty, or feasibility. Our project list is not exclusive: if you have an idea, solicit feedback from the project's [wiki:TBR/Website/RTEMSMailingLists mailing list] or [wiki:Developer/IRC IRC channel]; many developers sit in IRC and check it (and their email) infrequently throughout the day, so be patient! There may or may not be enough work on a project to constitute an SoC project, and some of these are past SOC projects. If you are interested in one of these, please ask on the mailing list or IRC. == Adding Projects as Tickets == Open projects are managed as Trac Tickets. To create a new project: * Create a new ticket by clicking on [/newticket?type=project&milestone=Indefinite New Ticket]. * The Summary field of the ticket is the title of the open project. * The Description field of the ticket is the project detail. Please use the [https://devel.rtems.org/wiki/WikiFormatting WikiFormatting] to enhance the readability of the project's details. If you are not sure please review existing open projects as an example. * Set the Type field of the ticket as "project". This would have already been filled if you clicked on the New Ticket link above. * Set the Milestone field to be "Indefinite". This would have already been filled if you clicked on the New Ticket link above. * If this is a SoC Project one of the mentors of the project should be mentioned in the Owner field and you should CC the rest of the mentors. If no mentors are mentioned, keep the fields blank. * The Keywords field should be set to "SoC" denoting any projects that can participate in the Summer of Code. The keyword is case sensitive. * You also need to set one of the following as a Keyword (comma-delimited) to define the project type, one of: testing, ecosystem, kernel, statistics, BSP, API, libbsd, languages, libraries. Please ask on the mailing before adding new keywords, as they are used to create the tables below. * Select an appropriate component for the Component field. If you are unsure about anything, please ask on the [mailto:users@rtems.org RTEMS Users mailing list]. == Project Ideas List == Open projects are held in Trac as Trac tickets. The list can be viewed using the [report:10 SoC Project Report]. If one of the projects sounds interesting, but lacks detail, ask on the [mailto:users@rtems.org RTEMS Users mailing list] for details and we can all help scope the project. The owner field indicates a possible primary mentor for the project. The list in no specific order is: === Board Support Package (BSP) Projects === [[TicketQuery(status!=closed, keywords~=SoC BSP, format=table, col=summary|owner, order=priority|id)]] === Testing Projects === 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. [[TicketQuery(status!=closed, keywords~=SoC testing, format=table, col=summary|owner, order=priority|id)]] === Development Ecosystem Projects === 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. [[TicketQuery(status!=closed, keywords~=SoC ecosystem, format=table, col=summary|owner, order=priority|id)]] === API Layers Projects === [[TicketQuery(status!=closed, keywords~=SoC API, format=table, col=summary|owner, order=priority|id)]] === Executive (!SuperCore, SuperCoreCPU, libcpu) a.k.a. kernel === [[TicketQuery(status!=closed, keywords~=SoC executive|kernel, format=table, col=summary|owner, order=priority|id)]] === Runtime Statistics Projects === [[TicketQuery(status!=closed, keywords~=SoC statistics, format=table, col=summary|owner, order=priority|id)]] === rtems-libbsd === [[TicketQuery(status!=closed, keywords~=SoC libbsd, format=table, col=summary|owner, order=priority|id)]] === Full List of Projects === [[TicketQuery(status!=closed, keywords~=SoC, format=table, col=summary|owner, order=priority|id)]] = Old Project Descriptions = We 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. Projects in ''Italic text'' are space-oriented and therefore suitable for [http://sophia.estec.esa.int/socis/ SOCIS]. * Testing * ''[wiki:Projects/Open/TestSpecification RTEMS Test Specification]'' - Develop a formal test specification. * [wiki:Projects/Open/TestScreenValidation RTEMS Test Screen Validation] - Create a tool to validate test output. * '''[wiki:Projects/Open/ImproveGDBSim Improve GDB Simulation]''' - Fixing some issues in GDB Simulators. * [wiki:Projects/Open/SimulatorUpdates Simulator Updates] - Find and fix problems in BSPs that target simulators. * [wiki:Projects/Open/GNUToolsTesting Testing of the GNU Tools] - Improve Tools Testing on RTEMS targets * [wiki:Projects/Open/TestTemplate RTEMS Test Template] - Improve automatic generation of tests. * ''[wiki:Projects/Open/Fault_injection Fault tolerance]'' - get a fault injection tool to work with RTEMS and create tutorials and examples. * Development Ecosystem * [wiki:Projects/Open/ConfigGUI Config GUI (Python)] - GUI for configuring RTEMS build. * [wiki:Projects/Open/BuildVariables Build Variables (Python)] - Add bounds checking for all build options as well as cleanup. * [wiki:Projects/Open/ImproveRSB Improve RSB (Python)] - General improvements to the [wiki:Developer/Tools/RSB RTEMS Source Builder]. * [wiki:Projects/Open/PyGDB Python GDB Support (Python)] - Add Python Script support for debugging RTEMS with GDB. * ''[wiki:Projects/Open/StackAnalysis Static Analysis of Stack Usage]'' - Develop a tool for static analysis of stack usage. * ''[wiki:Projects/Open/PythonCoverageReporting Python Coverage Reporting (Python)]'' - Convert coverage reporting to Python and integrate into RTEMS Tools. * [wiki:Projects/Open/GCovReports GCov Reports] - Use gcov output as generated by covoar to generate useful reports. * [wiki:Projects/Open/GProfReports GProf Reports] - Use gprof output as generated by covoar to generate useful reports. * [wiki:Projects/Open/AddCoverageToGDBSimulators GDB Coverage] - Add execution coverage logging to the GDB simulators used by RTEMS. * [wiki:Projects/Open/ImproveEclipsePlugin Improve Eclipse Plugin] - Improvements in the [wiki:Developer/Eclipse/Information RTEMS Eclipse Integration]. * [wiki:Projects/Open/UsingClang Using clang] - Compiling RTEMS with [wiki:Projects/CLANG CLANG]. * [wiki:Projects/Open/EVisualStudio eVisual Studio] - Integration of RTEMS cross development environment into eVisual Studio. * [wiki:Projects/Open/ArgoUML ArgoUML] - UML for RTEMS. * Executive (!SuperCore, SuperCoreCPU, libcpu): a.k.a. kernel * ''[wiki:Projects/Open/ImproveSMP Improvements to SMP support]'' - Propose an improvement to the existing [wiki:Developer/SMP SMP capabilities]. * [wiki:Projects/Open/UnifiedInterrupts Unified Interrupts] - Unify the interrupt and PCI interfaces. * ''[wiki:Projects/Open/TinyRTEMS TinyRTEMS]'' - Improve some aspect of [wiki:Projects/TinyRTEMS TinyRTEMS]. * ''[wiki:Projects/Open/Paravirtualization Paravirtualization]''- Make RTEMS suitable to run as a guest in a hypervisor. * Run-Time Statistics * ''[wiki:Projects/Open/CPU_Statistics CPU Statistics]'' - Improvements to CPU Usage Statistics. * ''[wiki:Projects/Open/StackChecker Stack Checker]'' - Improvements to Stack Bounds Checker. * Board Support Package (BSP) * [wiki:Projects/Open/EdisonBSP x86 Edison] - on hold due to unavailability of open information * API Layers (POSIX, Classic, SAPI) * [wiki:Projects/Open/OSEK OSEK] - Implement [http://portal.osek-vdx.org/ OSEK] automotive APIs. * [wiki:Projects/Open/ProgammableLogicController Programmable Logic Controller] - Enable RTEMS as a [http://en.wikipedia.org/wiki/Programmable_logic_controller Programmable Logic Controller (PLC)]. * ''[wiki:Projects/Open/ARINC653API ARINC653 in RTEMS]'' - Implement ARINC-653 avionics APIs. * rtems-libbsd * [wiki:Projects/TCP/IP_update Update the RTEMS TCP/IP stack] - Ask about possibilities about Ethernet over USB and Wifi support. * [wiki:TBR/UserManual/USBStack USB stack] - Ask about possible addition of other device types. * Languages * [wiki:Projects/Open/Mono Mono On RTEMS] - Add support for [http://www.mono-project.com Mono]. * [wiki:Projects/Open/V8 Port V8 JavaScript Engine to RTEMS] - Add support for the [http://code.google.com/p/v8/ V8 Engine]. * [wiki:Projects/Open/SWIGforRTEMS SWIG on RTEMS] - Add support for SWIG. * Libraries and Applications * [wiki:Projects/Open/InternetOfThings] Internet of Things (IoT) - Port IoT infrastructure * [wiki:Projects/Open/PortMonkey Port Monkey HTTP Server] - Port the [http://monkey-project.com/ Monkey HTTP Server]. * [wiki:Projects/Open/TIPC Port Transparent IPC] - Port [http://tipc.sourceforge.net/index.html Transparent IPC (TIPC)]. * [wiki:Projects/Open/LineEditor Line Editor]. Implement a simple line editor. Existing code can be refactored for a starting point. * '' '''[wiki:Projects/Open/Toolkits RTEMS Toolkits]''' '' - Define a generic (RTEMS Source Builder based) infrastructure for building and maintaining toolkits. * Turn the current port of [wiki:Packages/LWIP LWIP] into a first class citizen that RSB can build. Submit port, make target independent, create maintenance plan. * [wiki:Projects/Open/RockOnRTEMS Rock on RTEMS] - Improve the existing port of Rock on RTEMS. = Retired Projects = The following projects are complete or pending. * Testing * [wiki:Testing/Filesystem File System Test Suite] * Tools * [wiki:Projects/GSoC/ApplicationConfigurationGUI Application Configuration GUI]. * Runtime * [wiki:Projects/Open/AtomicAPI Classic API Atomic API] * [wiki:Projects/Open/Condition_Variables Condition Variables (CV)] * [wiki:Projects/SixtyFourBitTimestamps Sixty-Four Bit Timestamps] * [wiki:Projects/Refactor_the_filesystem_infrastructure Refactor the filesystem infrastructure] * Use [wiki:Projects/GSoC/PosixKeys Maps or Hashes] in the implementation of Classic API Notepads and POSIX API Keys. * [wiki:Projects/GSoC/Bdbuf_improvements Bdbuf improvements]. The current block device buffer implementation can benefit from a number of improvements. * Improve the RTEMS [wiki:Projects/Scheduler SuperCore Scheduler] * [wiki:Projects/SystemEvents kqueue(2) or taskqueue(9)] is a project to port the kqueue(2) or taskqueue(9) API from FreeBSD. * [wiki:GSoC/2011/ISO9660_Filesystem ISO9660 file system] * [wiki:Projects/POSIX_Asynchronous_IO POSIX Asynchronous IO]. POSIX Asynchronous IO should be nearly done, with perhaps a little more work to do. POSIX List IO is not currently implemented. This would involve implementing and fully list IO per the [http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/aio.h.html POSIX specification] as well as completing the Asynchronous IO. First step work is to save the state of the project as a report under the appropriate GSOC/YYYY year topic. * Languages * [wiki:Projects/Parrot Parrot On RTEMS] * [wiki:Projects/GCCGoRTEMS GNU GCC Go] * RTEMS port of the [wiki:Projects/GNUJavaCompiler GNU Java Compiler (gjc)] * Lua in RTEMS * [wiki:Projects/GSoC/OpenRISC Porting RTEMS to OpenRISC]. * [wiki:Projects/StrictOrderMutex Nested Mutexes]: See Ticket #2124 for a problem description. * [wiki:Projects/SequencedInitialization RTEMS Sequenced Initialization] - Initialize RTEMS dynamically, conceptually like C++ global constructors. = Obsolete Projects = Some projects have been proposed that are viewed as being of minor use. This list is meant to provide a way to avoid wasted effort on projects that are not widely desired. However, projects on this list might still be useful to someone, given a motivated individual to work on them. * Various ideas have been proposed related to using RTEMS as a [wiki:Developer/Projects/Obsolete/Hypervisor hypervisor]. The lack of protected (kernel mode) execution precludes any feasible implementations. * Merge [wiki:Developer/Projects/Obsolete/SimpleScalar BSP for Simplescalar simulator]. The BSP is heavily bit-rotted and the simulator is a dead project. * [http://code.google.com/p/rosetta-os Rosetta OS] [wiki:Developer/Projects/Obsolete/RosettaOSDeviceDriverAPI OS Independent Device Driver API]. * Implement current version of [http://www.tron.org/index-e.html µITRON Interface]. itron support was removed from RTEMS due to lack of interest. * More [wiki:Developer/Projects/Obsolete/Libbsd-port NIC device drivers for the old networking stack]. See instead [wiki:Projects/TCP/IP_update new TCP/IP stack]. * Integrate [wiki:Developer/Projects/Obsolete/CEXP CEXP] into main RTEMS distribution. Possible licensing issues, please apply to the RTL project instead. * Scripts and documentation for creating and installing prebuilt tool packages [wiki:Developer/Projects/Obsolete/RPM_Packages Building Tool RPM Packages], [wiki:Developer/Projects/Obsolete/DebianHostedTools Debian Packages], [wiki:Developer/Projects/Obsolete/MacOSHostedTools MacOS tools], [wiki:TBR/UserManual/MinGW_Tools_for_Windows MinGW Tools for Windows], [wiki:Developer/Projects/Obsolete/Canadian_Cross_Compiler Canadian Cross Compiler]. Please apply to the [wiki:Projects/Open/ImproveRSB RSB] project instead. * [wiki:Projects/Open/RumpKernels Rump Kernels] - Provide the hypercall interface for [http://rumpkernel.org/ Rump Kernels] in RTEMS. Instead, we prefer to focus efforts on improving the libbsd.