Changes between Version 445 and Version 446 of Developer/OpenProjects


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

Make Trac Tickets the default for new open projects.

Legend:

Unmodified
Added
Removed
Modified
  • Developer/OpenProjects

    v445 v446  
    1 [[TOC(Developer/OpenProjects, depth=2)]]
     1[[TOC(Developer/OpenProjects, depth=3)]]
    22
    33= Open Projects =
     
    99Most 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.
    1010
    11 Projects 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].
     11== Overview ==
    1212
    13 = Overview =
     13The 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.
    1414
    15 The order of projects in the 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.
     15== Project List ==
    1616
     17Open projects are held in Trac as Trac tickets and can be viewed using the [report:10 SoC Project Report].
    1718
     19If 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.
    1820
    19 If you have a new project add it to the appropriate list below, link to a wiki page below !Projects/Open/ and use the [wiki:PageTemplates/ProjectDescriptionTemplate  Open Project Template]. Briefly (1 sentence) summarize the project.
     21== Adding Projects as Tickets ==
    2022
    21 If one of the projects sounds interesting, but lacks detail, ask on an RTEMS mailing list for details and we can all help scope the project.
     23Open projects are managed as Trac Tickets. To create a new project:
    2224
    23 = Help Convert to Tickets =
     25 * Create a new ticket by clicking on [/newticket?type=project&milestone=Indefinite New Ticket].
     26 * The Summary field of the ticket is the title of the open project.
     27 * 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.
     28 * Set the Type field of the ticket as "project". This is done if you click on the New Ticket link above.
     29 * Set the Milestone field to be "Indefinite". This is done if you click on the New Ticket link above.
     30 * 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.
     31 * The Keywords field should be set to "SoC" denoting any projects that can participate in the Summer of Code. The keyword is case sensitive.
     32 * We might want to use some other Keywords e.g. to define the project type (e.g. one of: testing, ecosystem, kernel, statistics, BSP, API, libbsd, languages, libraries). Please ask on the mailing before adding new keywords.
     33 * Select an appropriate component for the Component field.
     34
     35If you are unsure about anything, please ask on the [mailto:users@rtems.org RTEMS Users mailing list].
     36
     37== Wiki Listed Open Projects ==
     38
     39The Wiki listed open projects are in the process of being moved to Trac Tickets. The tickets are the newer and more relevant version of any project still listed on this page. When in doubt, consider the description in the tickets as valid.
     40
     41The wiki page will be cleaned up and Wiki Projects will be removed once all open projects have been moved to Trac Tickets.
     42
     43For 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].
     44
     45=== Converting Projects To Tickets ===
    2446
    2547We have started converting each of the projects listed here to tickets. Any help in the process is appreciated.
    26 A standard workflow for the same would be:
    27  * Create a new ticket (New Ticket(direct) in Trac).
    28  * The summary of the ticket should be the title of the open project.
    29  * The content of the project page should form the description of the ticket. May require [https://devel.rtems.org/wiki/WikiFormatting WikiFormatting]. (Perhaps it would be a good idea to just click on "Edit this page" down on the project's page and copy the already wikiformatted text.)
    30  * Put the "Type" of the ticket as "project"
    31  * Put the "milestone" to be "indefinite".
    32  * One of the mentors of the project should be mentioned in the "Owner" field and you should CC the rest of them. If no mentors are mentioned, keep the fields blank.
    33  * The "Keywords" field should be put to "SoC" denoting any Summer of Code RTEMS participates in.
    34  * We might want to use some other keywords e.g. to define the project type (e.g. one of: testing, ecosystem, kernel, statistics, BSP, API, libbsd, languages, libraries)
    35  * Add an appropriate "component"
    36 If you are unsure about anything, ask on the mailing list.
    3748
    38 The tickets are the newer and more relevant version of the content on the project's page. When in doubt, consider the description in the tickets as valid.
     49----
     50----
    3951
    4052= Testing =