6 | | This page captures ideas for RTEMS projects. They range from OS projects |
7 | | to development environment to testing to just about anything else. |
8 | | If you like one of the ideas, you can pitch in and tackle it. If you |
9 | | aren't able to code and test it yourself, consider sponsoring one of |
10 | | the core RTEMS developers to do it for you. This is really the only |
11 | | way things get done -- USERS LIKE YOU KEEP RTEMS DEVELOPMENT ALIVE!!! |
12 | | |
13 | | The projects on this page are lumped into broad categories but there is |
14 | | no prioritization applied to the order. It is just an organized dump |
| 6 | This page captures ideas for RTEMS projects. They range from OS projects to development environment to testing to just about anything else. |
| 7 | If you like one of the ideas, you can pitch in and tackle it. If you aren't able to code and test it yourself, consider sponsoring one of |
| 8 | the core RTEMS developers to do it for you. This is really the only way things get done -- USERS LIKE YOU KEEP RTEMS DEVELOPMENT ALIVE!!! |
| 9 | |
| 10 | The projects on this page are lumped into broad categories but there is no prioritization applied to the order. It is just an organized dump |
17 | | We do not provide time estimates on these because the time depends |
18 | | on the experience and skill of the developer. Most of these projects |
19 | | will fall between a few weeks and a few months of effort by a |
20 | | person who is not completely unfamiliar with the general use of GNU/Linux |
21 | | and GNU tools. Some of these projects may consist of multiple steps. In |
22 | | this case, each step is defined to fall into short discrete steps. |
23 | | |
24 | | Many RTEMS projects are done as student or volunteer efforts in a person's |
25 | | spare time or as a hobby. This means it is imperative that projects be |
26 | | either relatively small or divided into steps that can be considered |
27 | | complete and committed to the main RTEMS source base. Thus we have |
28 | | lots of experience in defining useful projects that are sized to be |
29 | | doable and useful to the community in relatively small work packages. |
30 | | |
31 | | Most of the projects are feasible as a [wiki:GSoC Google Summer of Code] project. |
32 | | Since some projects have multiple steps, a [wiki:GSoC Google Summer of Code] participant |
33 | | should work with us to size up how many of those steps to undertake. |
| 13 | We do not provide time estimates on these because the time depends on the experience and skill of the developer. Most of these projects |
| 14 | will fall between a few weeks and a few months of effort by a person who is not completely unfamiliar with the general use of GNU/Linux |
| 15 | and GNU tools. Some of these projects may consist of multiple steps. In this case, each step is defined to fall into short discrete steps. |
| 16 | |
| 17 | Many RTEMS projects are done as student or volunteer efforts in a person's spare time or as a hobby. This means it is imperative that projects be |
| 18 | either relatively small or divided into steps that can be considered complete and committed to the main RTEMS source base. Thus we have |
| 19 | lots of experience in defining useful projects that are sized to be doable and useful to the community in relatively small work packages. |
| 20 | |
| 21 | Most of the projects are feasible as a [wiki:GSoC Google Summer of Code] project. Since some projects have multiple steps, a [wiki:GSoC Google Summer of Code] participant should work with us to size up how many of those steps to undertake. |