Changes between Version 236 and Version 237 of Developer/OpenProjects


Ignore:
Timestamp:
Feb 10, 2012, 8:24:38 PM (8 years ago)
Author:
Gedare
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Developer/OpenProjects

    v236 v237  
    66
    77
    8 Welcome [wiki:GSoC  Summer of Code] Students and fellow hackers.  Peruse our projects and see what interests you.  If you have questions ask them on the Wiki talk page or the [wiki:TBR/Website/RTEMSMailingLists  RTEMS mailing list].  If you plan to submit a proposal to do something for the RTEMS Project, we now require that you demonstrate that you have a basic RTEMS development environment installed. See [wiki:GSoC/GettingStarted  Getting Started for SoC Students] for details on what we want you to have done. Most of all we want you to succeed and have fun on an RTEMS related project.
     8Welcome [wiki:GSoC  Summer of Code (SOC)] Students and fellow hackers.  Peruse our projects and see what interests you.  If you have questions ask them on the Wiki talk page or the [wiki:TBR/Website/RTEMSMailingLists  RTEMS mailing list].  If you plan to submit a proposal to do something for the RTEMS Project as part of a SOC we require that you demonstrate that you have a basic RTEMS development environment installed as part of the application process; ask questions if you need help getting there. See [wiki:GSoC/GettingStarted  Getting Started for SoC Students] for details on what we want you to have done. Most of all we want you to succeed and have fun on an RTEMS related project.
    99
    10 This page captures ideas for RTEMS projects.  They range from OS projects to development environment to testing to just about anything else.  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 the core RTEMS developers to do it for you.  This is really the only way things get done -- users keep RTEMS development alive!
     10RTEMS projects span kernel hacking, improving the development environment, developing test cases and test suites, and more.  If you like one of the ideas, you can pitch in and tackle it.  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!
    1111= Overview =
    1212
     
    1616and GNU tools.  Some of these projects may consist of multiple steps.  In this case, each step is defined to fall into short discrete steps.
    1717
    18 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 either relatively small or divided into steps that can be completed and committed to the main RTEMS code repository.  Thus we have lots of experience in defining useful projects that are sized to be doable and useful to the community in relatively small work packages.
     18Many 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 either relatively small or divided into steps that can be completed and committed to the main RTEMS code repository.  Thus we have lots of experience in defining useful projects that are sized to be doable and useful to the community in relatively small work packages, or we try to identify projects that we think are beyond the scope of an SOC.
    1919
    2020Most 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 size up how many of those steps to undertake.  Similarly, some projects might be a starting point for a thesis or dissertation.
     
    2222The projects on this page are lumped into broad categories but there is no prioritization applied to the order; we have identified some high priority projects (or project areas) that can help guide you if you are at a loss of what might be interesting to work on. The order of projects in the list does not reflect their importance, difficulty, or feasibility. It is just an organized dump of ideas with enough details to give an outline of the effort required.  If you are interested in doing one, a core developer will be happy to augment the description or development plan.
    2323
    24 '''If you have a new project to add then add it to the appropriate list below and link to a wiki page that follows the recommended [wiki:TBR/Review/OpenProjectTemplate  Open Project Template].'''
     24Our project list is not exclusive: if you have an idea that is not listed don't hesitate to ask people in the RTEMS community if they think your idea is good and propose it if so. If developers are working on something similar to what you propose they may be less likely to accept your proposal. Ask on 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 if it takes awhile for your question to be answered don't give up!
     25
     26'''If you have a new project add it to the appropriate list below, link to a wiki page that follows the recommended [wiki:TBR/Review/OpenProjectTemplate  Open Project Template], and briefly (1-2 sentences) summarize the project and how it will improve RTEMS.'''
    2527= High Priority Projects =
    2628
    27 These projects have generated a lot of interest from users and are greatly desired. Most of these are large or ongoing projects that should be broken into manageable subtasks that may constitute reasonable sized projects themselves.
     29These projects have generated a lot of interest from users and are greatly desired. Most of these are large or ongoing projects that should be broken into manageable subtasks that may constitute reasonable sized projects themselves. Definitely ask before proposing to do any of these projects.
    2830
    29  *  [wiki:SMP_  Improvements to SMP support]
    30  *  [wiki:RTEMS_Test_Coverage  Test Coverage Analysis] - Improve coverage by adding more test cases.
    31  *  [wiki:Projects/TCP/IP_update  Update the RTEMS TCP/IP stack] - This project has some volunteer activity.  The effort requires providing support functional equivalents of multiple BSD kernel constructs.  The following is a very short list of them. This project may be too large for a SOC.
     31 *  [wiki:SMP_  Improvements to SMP support] - Multiprocessing is of increasing importance in modern systems and we want RTEMS to remain competitive and useful.
     32 *  [wiki:RTEMS_Test_Coverage  Test Coverage Analysis] - Improve coverage by adding more test cases. Eliminating dead code and reaching 100% coverage helps reduce the likelihood of new and recurrent bugs.
     33 *  [wiki:Projects/TCP/IP_update  Update the RTEMS TCP/IP stack] - The networking stack is old and showing it. This project has some volunteer activity.  The effort requires providing support functional equivalents of multiple BSD kernel constructs.  The following is a very short list of them. This project may be too large for a SOC.
    3234  *  [wiki:BusSpaceAPI_  Bus Space API]. Supercore namespace RTEMS-specific API in the spirit of the [http://www.freebsd.org/cgi/man.cgi?query=bus_space&sektion=9&apropos=0&manpath=FreeBSD+8.2-RELEASE BSD bus_space API]. This project may be too large for a SOC.
    3335