Changes between Version 23 and Version 24 of GCI/SampleTasks


Ignore:
Timestamp:
Sep 17, 2018, 2:39:27 PM (9 months ago)
Author:
Gedare Bloom
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GCI/SampleTasks

    v23 v24  
    33[[TOC(GCI/SampleTasks , depth=2)]]
    44
    5 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
    6 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.
     5This page is for GCI application informational purposes and represents only a small sample of the tasks we have prepared. We use [https://github.com/joelsherrill/gci_tasks a git repository] to generate most of our tasks for importing into the GCI web site.
     6
     7Short descriptions of the tasks we are planning or thinking about including are available on our [[GCI/TaskPlan]] page.
    78
    89Category number mapping to names (based on the import process circa 2015):
     
    1112== Sample of Tasks Prepared for GCI 2018 ==
    1213
    13 
    1414|| Name || Description || Max Instances || Mentors || Tags || Is Beginner? || Categories || Time to Complete (Days) || Private Metadata
    1515|| Getting Started: Hello World || This task consists of performing the hello world task that Google Summer of Code students do, plus providing feedback and improvement on the instructions. It is a necessary step to be able to build RTEMS itself and perform some of the other GCI coding and documentation tasks. The detailed instructions are at https://devel.rtems.org/wiki/GCI/Coding/HelloWorld. This task can only be performed once per GCI student, but you can do the "Getting Started Redux: Hello World 2.0" task as an extension activity. || 30 || "joelsherrill@gmail.com,gedarebloom@gmail.com" || C,programming || true || 1,3,4 || 3 || hello
     16|| "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
     17|| "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
     18|| "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
     19|| "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
     20|| Design a square organization logo || Our current logo (https://www.rtems.org/logo_list) is an oval that embeds in a rectangular bounding box. We could use a nice square variant of our current logo of at least 300x300 px. Familiarity with a graphics design package like Gimp, Photoshop, Inkscape, or Illustrator are useful for completing this task. Gimp and Inkscape are open source (and free). <p> You MUST have attention to detail to complete this task. Aliasing artifacts and fuzzy scaled images will not be acceptable.  This logo would be used for GCI and GSoC, and would also make a better logo for square presentations such as on GitHub. || 10 || "joelsherrill@gmail.com,gedarebloom@gmail.com" || graphics,logo || true || 2 || 3 || logo
     21
    1622|| Getting Started Redux: Hello World 2.0 || This task consists of performing the hello world task that Google Summer of Code students do, but either using a new host operating system or for a different RTEMS target besides sparc/erc32, and otherwise follow the same instructions as at https://devel.rtems.org/wiki/GCI/Coding/HelloWorld. This task can be performed multiple times by a single student, but each time must use a new host or target. || 20 || "joelsherrill@gmail.com,gedarebloom@gmail.com" || C,programming || false || 1,3,4 || 3 || hello
    1723|| 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
     
    2329|| 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"
    2430|| 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"
    25 || "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
    26 || "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
    27 || "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
    28 || "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
    2931|| !Investigate/Fix Bug: Ticket #1405 ||  First complete one of the Getting Started tasks.<p><p>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
    3032|| !Investigate/Fix Bug: Ticket #1406 ||  First complete one of the Getting Started tasks.<p><p>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
     
    3638|| 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
    3739|| 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
    38 || Design a square organization logo || Our current logo (https://www.rtems.org/logo_list) is an oval that embeds in a rectangular bounding box. We could use a nice square variant of our current logo of at least 300x300 px. Familiarity with a graphics design package like Gimp, Photoshop, Inkscape, or Illustrator are useful for completing this task. Gimp and Inkscape are open source (and free). <p> You MUST have attention to detail to complete this task. Aliasing artifacts and fuzzy scaled images will not be acceptable.  This logo would be used for GCI and GSoC, and would also make a better logo for square presentations such as on GitHub. || 10 || "joelsherrill@gmail.com,gedarebloom@gmail.com" || graphics,logo || false || 2 || 3 || logo
    3940|| Design a new organization logo || This task involves designing a new logo for RTEMS. We would like to have two variations, one as a rectangular shape at least 300x400px, and the other as a square at least 300x300 px. Logos must clearly portray the name RTEMS. <p> You can see current / previous versions of the RTEMS logo for perspective (see https://www.rtems.org/logo_list) but you should design something completely different. Familiarity with a graphics design package like Gimp, Photoshop, Inkscape, or Illustrator are useful for completing this task. Gimp and Inkscape are open source (and free). <p> Be creative and make it aesthetically associated with RTEMS in some manner! You must be able to explain how your design relates to RTEMS. Search the web for design inspiration before working on this, but you must submit a completely original design of your own creation that does not use 3rd party images from the web. If you create a design similar to something you found on the web, it is considered a derivative work and you should give proper attribution (i.e., credit) to that author by name with a link to their work. Failure to give credit is plagiarism and can be grounds for dismissal from GCI. When in doubt, design something unique. ;) <p> Logo design tips are in abundance around the web such as these [65 tips](https://www.creativebloq.com/graphic-design/pro-guide-logo-design-21221) and these [7 tips](https://mashable.com/2014/04/30/logo-design-tips/#lQ5SODB0iSqz). <p> Submit a preview of your design in PNG format as well as your original artwork files ideally in vector format (e.g., PSD, XCF, SVG, AI, etc). <p> If you would like credit, please provide your name and join our mailing list to hear if we use your logo design. || 30 || "joelsherrill@gmail.com,gedarebloom@gmail.com" || graphics,logo || false || 2 || 3 || logo
    4041|| Design a T-Shirt || Design a T-shirt for RTEMS users and/or developers. It can feature a tagline, showcase some killer feature, incorporate some illustration regarding RTEMS, incorporate the RTEMS logo (see https://www.rtems.org/logo_list), or be something completely different (but obviously still clearly pertaining to RTEMS). Search the web for design inspiration before working on this, but you must submit a completely original design of your own creation that does not use 3rd party images from the web. If you create a design similar to something you found on the web, it is considered a derivative work and you should give proper attribution (i.e., credit) to that author by name with a link to their work. Failure to give credit is plagiarism and can be grounds for dismissal from GCI. When in doubt, design something unique. <p> Submit a preview image of the t-shirt front and back in PNG format as well as your original artwork files ideally in vector format (e.g., PSD, XCF, SVG, AI, etc). <p> If you would like credit, please provide your name and join our mailing list to hear if we use your t-shirt design. <p> Be awesome, be creative, be inspired, be original!  || 30 || "joelsherrill@gmail.com,gedarebloom@gmail.com" || graphics,logo,t-shirt || false || 2 || 3 || tshirt