= Sample Tasks for GCI = [[TOC(GCI/SampleTasks , depth=2)]] This page is for informational purposes only in applying and preparing for GCI, and represents only a small sample of the tasks we have prepared. Please refer to [wiki:GCI our GCI] main page for more. We use https://github.com/joelsherrill/gci_tasks git repository to generate the actual tasks for import into the GCI web site, which we modified slightly to prepare the below table. Short descriptions of the tasks we are planning or thinking about including are available on our [[GCI/TaskPlan]] page. Category number mapping to names (based on the import process circa 2015): 1: Coding. 2: Design. 3: Documentation & Training. 4: Quality Assurance. 5: Outreach & Research. == Sample of Tasks Prepared for GCI 2018 == || Name || Description || Max Instances || Mentors || Tags || Is Beginner? || Categories || Time to Complete (Days) || Private Metadata || Resolve Wiki Page: TBR/Delete/NewlibMemoryAllocation || Our wiki includes a number of pages that have been labeled as "TBR" to be reviewed for several years, and some have been slated for deletion without certain evidence they should be removed. In this task, you will investigate the page located on [the RTEMS Trac Wiki](https://devel.rtems.org/wiki/TBR/Delete/NewlibMemoryAllocation) Follow the [directions for this task](https://devel.rtems.org/wiki/GCI/Outreach/WikiTBR) on our wiki. The outcome of this task is a recommendation to relocate the page/contents or to delete it. || 1 || "amardtakhar@gmail.com,joelsherrill@gmail.com" || "wiki,research" || false || "2,3,4,5" || 3 || TBR || Resolve Wiki Page: TBR/Review/DateTimeHardwareIssues || Our wiki includes a number of pages that have been labeled as "TBR" to be reviewed for several years, and some have been slated for deletion without certain evidence they should be removed. In this task, you will investigate the page located on [the RTEMS Trac Wiki](https://devel.rtems.org/wiki/TBR/Review/DateTimeHardwareIssues) Follow the [directions for this task](https://devel.rtems.org/wiki/GCI/Outreach/WikiTBR) on our wiki. The outcome of this task is a recommendation to relocate the page/contents or to delete it. || 1 || "amardtakhar@gmail.com,gedarebloom@gmail.com" || "wiki,research" || false || "2,3,4,5" || 3 || TBR || Resolve Wiki Page: TBR/Review/Debugging/Start || Our wiki includes a number of pages that have been labeled as "TBR" to be reviewed for several years, and some have been slated for deletion without certain evidence they should be removed. In this task, you will investigate the page located on [the RTEMS Trac Wiki](https://devel.rtems.org/wiki/TBR/Review/Debugging/Start) Follow the [directions for this task](https://devel.rtems.org/wiki/GCI/Outreach/WikiTBR) on our wiki. The outcome of this task is a recommendation to relocate the page/contents or to delete it. || 1 || "amardtakhar@gmail.com,vattamsantosh@gmail.com" || "wiki,research" || false || "2,3,4,5" || 3 || TBR || Resolve Wiki Page: TBR/Review/GSOC_F12_ToolChainSetup || Our wiki includes a number of pages that have been labeled as "TBR" to be reviewed for several years, and some have been slated for deletion without certain evidence they should be removed. In this task, you will investigate the page located on [the RTEMS Trac Wiki](https://devel.rtems.org/wiki/TBR/Review/GSOC_F12_ToolChainSetup) Follow the [directions for this task](https://devel.rtems.org/wiki/GCI/Outreach/WikiTBR) on our wiki. The outcome of this task is a recommendation to relocate the page/contents or to delete it. || 1 || "amardtakhar@gmail.com,krzysztofmiesowicz@gmail.com" || "wiki,research" || false || "2,3,4,5" || 3 || TBR || Add Per Function Sections to sh/shsim BSP || "Compiler and Linker flags can make a big difference on the size and speed of programs. This task consists of adding per function section support for compiling and linking to sh/shsim BSP per these [instructions](https://devel.rtems.org/wiki/GCI/Coding/AddPerSectionSupportToBSPs). The outcome of this task is a patch and report of the size difference achieved." || 1 || "joelsherrill@gmail.com,gedarebloom@gmail.com" || "C,compiler,BSP" || 0 || "1,4" || 5 || "function sections BSP" || Add Per Function Sections to sparc64/niagara BSP || "Compiler and Linker flags can make a big difference on the size and speed of programs. This task consists of adding per function section support for compiling and linking to sparc64/niagara BSP per these [instructions](https://devel.rtems.org/wiki/GCI/Coding/AddPerSectionSupportToBSPs). The outcome of this task is a patch and report of the size difference achieved." || 1 || "chriscjohns@gmail.com,nickrtemsgci@gmail.com" || "C,compiler,BSP" || 0 || "1,4" || 5 || "function sections BSP" || Add Per Function Sections to sparc64/usiii BSP || "Compiler and Linker flags can make a big difference on the size and speed of programs. This task consists of adding per function section support for compiling and linking to sparc64/usiii BSP per these [instructions](https://devel.rtems.org/wiki/GCI/Coding/AddPerSectionSupportToBSPs). The outcome of this task is a patch and report of the size difference achieved." || 1 || "joelsherrill@gmail.com,chriscjohns@gmail.com" || "C,compiler,BSP" || 0 || "1,4" || 5 || "function sections BSP" || Add Per Function Sections to v850/gdbv850sim BSP || "Compiler and Linker flags can make a big difference on the size and speed of programs. This task consists of adding per function section support for compiling and linking to v850/gdbv850sim BSP per these [instructions](https://devel.rtems.org/wiki/GCI/Coding/AddPerSectionSupportToBSPs). The outcome of this task is a patch and report of the size difference achieved." || 1 || "gedarebloom@gmail.com,chriscjohns@gmail.com" || "C,compiler,BSP" || 0 || "1, 4" || 5 || "function sections BSP" || "Update Citations 2015-1" || "This task consists of updating the[RTEMS References Wiki page](https://devel.rtems.org/wiki/References/2015) according to the instructions given in the [RTEMS GCI Wiki page](https://devel.rtems.org/wiki/GCI/Outreach/Citations) for the year 2015 and page 1. You will need to request a user account on the wiki and be careful to avoid making updates that conflict or delete other relevant citations. You will upload a text file containing the entries that you added to the wiki page. We have constructed the [Google Scholar Search for this task] (http://scholar.google.com/scholar?start=0&q=RTEMS&hl=en&lr=lang_en&as_sdt=1%2C47&as_vis=1&as_ylo=2015&as_yhi=2015) for your convenience." || 1 || "vattamsantosh@gmail.com" || wiki || true || "5" || 4 || citations || "Update Citations 2015-2" || "This task consists of updating the[RTEMS References Wiki page](https://devel.rtems.org/wiki/References/2015) according to the instructions given in the [RTEMS GCI Wiki page](https://devel.rtems.org/wiki/GCI/Outreach/Citations) for the year 2015 and page 2. You will need to request a user account on the wiki and be careful to avoid making updates that conflict or delete other relevant citations. You will upload a text file containing the entries that you added to the wiki page. We have constructed the [Google Scholar Search for this task] (http://scholar.google.com/scholar?start=10&q=RTEMS&hl=en&lr=lang_en&as_sdt=1%2C47&as_vis=1&as_ylo=2015&as_yhi=2015) for your convenience." || 1 || "krzysztofmiesowicz@gmail.com" || wiki || true || "5" || 4 || citations || "Update Citations 2015-3" || "This task consists of updating the[RTEMS References Wiki page](https://devel.rtems.org/wiki/References/2015) according to the instructions given in the [RTEMS GCI Wiki page](https://devel.rtems.org/wiki/GCI/Outreach/Citations) for the year 2015 and page 3. You will need to request a user account on the wiki and be careful to avoid making updates that conflict or delete other relevant citations. You will upload a text file containing the entries that you added to the wiki page. We have constructed the [Google Scholar Search for this task] (http://scholar.google.com/scholar?start=20&q=RTEMS&hl=en&lr=lang_en&as_sdt=1%2C47&as_vis=1&as_ylo=2015&as_yhi=2015) for your convenience." || 1 || "heshamelmatary@gmail.com" || wiki || true || "5" || 4 || citations || "Update Citations 2015-4" || "This task consists of updating the[RTEMS References Wiki page](https://devel.rtems.org/wiki/References/2015) according to the instructions given in the [RTEMS GCI Wiki page](https://devel.rtems.org/wiki/GCI/Outreach/Citations) for the year 2015 and page 4. You will need to request a user account on the wiki and be careful to avoid making updates that conflict or delete other relevant citations. You will upload a text file containing the entries that you added to the wiki page. We have constructed the [Google Scholar Search for this task] (http://scholar.google.com/scholar?start=30&q=RTEMS&hl=en&lr=lang_en&as_sdt=1%2C47&as_vis=1&as_ylo=2015&as_yhi=2015) for your convenience." || 1 || "chriscjohns@gmail.com" || wiki || true || "5" || 4 || citations || !Investigate/Fix Bug: Ticket #1405 || First complete one of the Getting Started tasks.

Investigate the bug described in Ticket #1405 on [the RTEMS Trac](https://devel.rtems.org/ticket/1405) Follow the [directions for this task](https://devel.rtems.org/wiki/GCI/QA/InvestigateTicket) on our wiki. The outcome of this task will be a comment on the ticket to suggest a path forward. If a bug fix is available, you may be expected to test the fix and possibly produce an updated patch. || 1 || "joelsherrill@gmail.com,gedarebloom@gmail.com,vattamsantosh@gmail.com" || "c,debugging" || false || "1,3,4" || 5 || bugfix || !Investigate/Fix Bug: Ticket #1406 || First complete one of the Getting Started tasks.

Investigate the bug described in Ticket #1406 on [the RTEMS Trac](https://devel.rtems.org/ticket/1406) Follow the [directions for this task](https://devel.rtems.org/wiki/GCI/QA/InvestigateTicket) on our wiki. The outcome of this task will be a comment on the ticket to suggest a path forward. If a bug fix is available, you may be expected to test the fix and possibly produce an updated patch. || 1 || "joelsherrill@gmail.com,gedarebloom@gmail.com,krzysztofmiesowicz@gmail.com" || "c,debugging" || false || "1,3,4" || 5 || bugfix || !Investigate/Fix Bug: Ticket #2024 || First complete one of the Getting Started tasks.

Investigate the bug described in Ticket #2024 on [the RTEMS Trac](https://devel.rtems.org/ticket/2024) Follow the [directions for this task](https://devel.rtems.org/wiki/GCI/QA/InvestigateTicket) on our wiki. The outcome of this task will be a comment on the ticket to suggest a path forward. If a bug fix is available, you may be expected to test the fix and possibly produce an updated patch. || 1 || "joelsherrill@gmail.com,gedarebloom@gmail.com,heshamelmatary@gmail.com" || "c,debugging" || false || "1,3,4" || 5 || bugfix || !Investigate/Fix Bug: Ticket #2581 || First complete one of the Getting Started tasks.

Investigate the bug described in Ticket #2581 on [the RTEMS Trac](https://devel.rtems.org/ticket/2581) Follow the [directions for this task](https://devel.rtems.org/wiki/GCI/QA/InvestigateTicket) on our wiki. The outcome of this task will be a comment on the ticket to suggest a path forward. If a bug fix is available, you may be expected to test the fix and possibly produce an updated patch. || 1 || "joelsherrill@gmail.com,gedarebloom@gmail.com,chriscjohns@gmail.com" || "c,debugging" || false || "1,3,4" || 5 || bugfix || !Investigate/Fix Bug: Ticket #1778 || First complete one of the Getting Started tasks.

Investigate the bug described in Ticket #1778 on [the RTEMS Trac](https://devel.rtems.org/ticket/1778) Follow the [directions for this task](https://devel.rtems.org/wiki/GCI/QA/InvestigateTicket) on our wiki. The outcome of this task will be a comment on the ticket to suggest a path forward. If a bug fix is available, you may be expected to test the fix and possibly produce an updated patch. || 1 || "joelsherrill@gmail.com,gedarebloom@gmail.com,jenniferaverett@gmail.com" || "c,debugging" || false || "1,3,4" || 5 || bugfix || Create POSIX Timing Test psxtmonce01 (13-#1) || This task consists of creating the timing test testsuites/psxtmtests/psxtmonce01 for the POSIX API method when used in a particular manner. The test case is: pthread_once: first time. Please check testsuites/psxtmtests/psxtmtests_plan.csv and make sure this description match that in the spreadsheet file. Also there may be multiple test cases in one test name. The .csv file along with advice from mentors is truth. In some cases a single test name may have multiple timing cases and be listed on two lines in the .csv file. Just be careful. As a hint if there is no dash in the description then this is the only case of interest for that method. If there are multiple methods then test both methods. The test should be created using the test instantiation helper and templates in rtems-testing/rtems-test-templates. This test will be using the template: psxtmtest_single. See https://devel.rtems.org/wiki/GCI/Coding/POSIXTimingTest for more details. The outcome of this task will be a patch to add the new test to RTEMS. || 1 || gedare || C,benchmarking,testing || 0 || 1,4 || 3 || psxtmtest || Create POSIX Timing Test psxtmonce02 (13-#2) || This task consists of creating the timing test testsuites/psxtmtests/psxtmonce02 for the POSIX API method when used in a particular manner. The test case is: pthread_once: second time. Please check testsuites/psxtmtests/psxtmtests_plan.csv and make sure this description match that in the spreadsheet file. Also there may be multiple test cases in one test name. The .csv file along with advice from mentors is truth. In some cases a single test name may have multiple timing cases and be listed on two lines in the .csv file. Just be careful. As a hint if there is no dash in the description then this is the only case of interest for that method. If there are multiple methods then test both methods. The test should be created using the test instantiation helper and templates in rtems-testing/rtems-test-templates. This test will be using the template: psxtmtest_single. See https://devel.rtems.org/wiki/GCI/Coding/POSIXTimingTest for more details. The outcome of this task will be a patch to add the new test to RTEMS. || 1 || crempel2 || C,benchmarking,testing || 0 || 1,4 || 3 || psxtmtest || Create POSIX Timing Test psxtmmqrcvblock01 (13-#3) || This task consists of creating the timing test testsuites/psxtmtests/psxtmmqrcvblock01 for the POSIX API method when used in a particular manner. The test case is: mq_receive: not available: block. Please check testsuites/psxtmtests/psxtmtests_plan.csv and make sure this description match that in the spreadsheet file. Also there may be multiple test cases in one test name. The .csv file along with advice from mentors is truth. In some cases a single test name may have multiple timing cases and be listed on two lines in the .csv file. Just be careful. As a hint if there is no dash in the description then this is the only case of interest for that method. If there are multiple methods then test both methods. The test should be created using the test instantiation helper and templates in rtems-testing/rtems-test-templates. This test will be using the template: psxtmtest_blocking. See https://devel.rtems.org/wiki/GCI/Coding/POSIXTimingTest for more details. The outcome of this task will be a patch to add the new test to RTEMS. || 1 || hiddenpearls || C,benchmarking,testing || 0 || 1,4 || 3 || psxtmtest || Create POSIX Timing Test (13-#5) || This task consists of creating the timing test testsuites/psxtmtests/ for the POSIX API method when used in a particular manner. The test case is: . Please check testsuites/psxtmtests/psxtmtests_plan.csv and make sure this description match that in the spreadsheet file. Also there may be multiple test cases in one test name. The .csv file along with advice from mentors is truth. In some cases a single test name may have multiple timing cases and be listed on two lines in the .csv file. Just be careful. As a hint if there is no dash in the description then this is the only case of interest for that method. If there are multiple methods then test both methods. The test should be created using the test instantiation helper and templates in rtems-testing/rtems-test-templates. This test will be using the template: . See https://devel.rtems.org/wiki/GCI/Coding/POSIXTimingTest for more details. The outcome of this task will be a patch to add the new test to RTEMS. || 1 || chrisjohns || C,benchmarking,testing || 0 || 1,4 || 3 || psxtmtest