Changes between Version 446 and Version 447 of Developer/OpenProjects


Ignore:
Timestamp:
Feb 6, 2017, 10:20:25 PM (3 years ago)
Author:
Chris Johns
Comment:

Add strike-through for move projects. Use the report for the project list.

Legend:

Unmodified
Added
Removed
Modified
  • Developer/OpenProjects

    v446 v447  
    1212
    1313The 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.
    14 
    15 == Project List ==
    16 
    17 Open projects are held in Trac as Trac tickets and can be viewed using the [report:10 SoC Project Report].
    18 
    19 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.
    2014
    2115== Adding Projects as Tickets ==
     
    3529If you are unsure about anything, please ask on the [mailto:users@rtems.org RTEMS Users mailing list].
    3630
     31== Project List ==
     32
     33Open projects are held in Trac as Trac tickets. The list is no specific order is:
     34
     35[[TicketQuery(status!=closed&keywords=SoC&component=bsps, format=table, col=summary|owner, order=priority|id)]]
     36
     37The list can be viewed using the [report:10 SoC Project Report].
     38
     39If 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.
     40
    3741== Wiki Listed Open Projects ==
    3842
     
    4347For the Wiki porjects those in '''Bold text''' are '''higher priority''' simply meaning that users or developers have expressed a lot of interest in such projects. Projects in ''Italic text'' are space-oriented and therefore suitable for [http://sophia.estec.esa.int/socis/ SOCIS].
    4448
    45 === Converting Projects To Tickets ===
     49----
     50----
     51
     52= Converting Projects To Tickets =
    4653
    4754We have started converting each of the projects listed here to tickets. Any help in the process is appreciated.
    4855
    49 ----
    50 ----
     56Projects that have the 'strike-through' font have been moved to Trac Tickets.
    5157
    5258= Testing =
     
    108114= Board Support Package (BSP) =
    109115
    110  * '''[wiki:Projects/Open/x86_64_BSP x86_64 BSP]''' - Create an x86_64 BSP to allow RTEMS to run on OTS hardware and popular emulators. This is related to some of the pc386 BSP Improvements.
    111  * '''[wiki:Projects/Open/ImprovePC386 PC386 BSP Improvements]''' - The BSP needs to support non-legacy PC configurations as well as address a few other issues. The x86_64 BSP project should only support non-legacy PC configurations.
    112  * '''[wiki:Projects/Open/ImproveBeagleBSP Beagle BSP improvements]''' - More peripherals and other improvements for the Beagleboard family.
    113  * '''[wiki:Projects/Open/ImproveRaspberryPiBSP Raspberry Pi improvements]''' - More peripherals and other improvements for Raspberry Pi.
    114  * [wiki:Projects/Open/Emulatei386BIOS x86 BIOS emulation for VESA] - This is Pavel Pisa's idea.
    115  * [wiki:Projects/Open/MicroblazePort Port RTEMS to Microblaze architecture] - New architecture port.
     116 * ~~~'''[wiki:Projects/Open/x86_64_BSP x86_64 BSP]''' - Create an x86_64 BSP to allow RTEMS to run on OTS hardware and popular emulators. This is related to some of the pc386 BSP Improvements.~~~
     117 * ~~~'''[wiki:Projects/Open/ImprovePC386 PC386 BSP Improvements]''' - The BSP needs to support non-legacy PC configurations as well as address a few other issues. The x86_64 BSP project should only support non-legacy PC configurations.~~~
     118 * ~~~'''[wiki:Projects/Open/ImproveBeagleBSP Beagle BSP improvements]''' - More peripherals and other improvements for the Beagleboard family.~~~
     119 * ~~~'''[wiki:Projects/Open/ImproveRaspberryPiBSP Raspberry Pi improvements]''' - More peripherals and other improvements for Raspberry Pi.~~~
     120 * ~~~[wiki:Projects/Open/Emulatei386BIOS x86 BIOS emulation for VESA] - This is Pavel Pisa's idea.~~~
     121 * ~~~[wiki:Projects/Open/MicroblazePort Port RTEMS to Microblaze architecture] - New architecture port.~~~
    116122 * [wiki:Projects/Open/SimulatorBSPs More BSPs for Simulators] - RTEMS can always use more BSPs for simulators (and readily available boards or open cores).
    117  * [wiki:Projects/Open/MemoryProtection Memory Protection] - Implement MMU low-level support code for more BSPs.
    118  * ''[wiki:Projects/Open/MergeLEON Merge Leon]'' - Merging Gaisler LEON support code into mainstream RTEMS.
     123 * ~~~[wiki:Projects/Open/MemoryProtection Memory Protection] - Implement MMU low-level support code for more BSPs.~~~
     124 * ~~~''[wiki:Projects/Open/MergeLEON Merge Leon]'' - Merging Gaisler LEON support code into mainstream RTEMS.~~~
    119125 * [wiki:Projects/Open/EdisonBSP x86 Edison] - on hold due to unavailability of open information
    120 
    121 [[TicketQuery(status!=closed&keywords=SoC&component=bsps, format=table, col=summary|owner, order=priority|id)]]
    122 
    123126
    124127= API Layers (POSIX, Classic, SAPI) =