Changes between Version 60 and Version 61 of GoogleCodeIn2010Tasks
- Timestamp:
- 11/06/10 16:11:37 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GoogleCodeIn2010Tasks
v60 v61 7 7 '''2. What are the goals of this contest?''' 8 8 9 Google Code-in (GCI) is intended to help students who may have wanted to get involved in open source but didn't know where to start. By working through the tasks suggested by organizations, contestants will be given the opportunity to engage with the open source community and get involved. The participating open source projects gain the benefit of additional contributions to their project, often in important areas that may get overlooked for whatever reason. 9 Google Code-in (GCI) is intended to help students who may have wanted to get involved in open source but didn't know where to start. By working through the tasks suggested by organizations, contestants will be given the opportunity to engage with the open source community and get involved. The participating open source projects gain the benefit of additional contributions to their project, often in important areas that may get overlooked for whatever reason. 10 10 11 11 It is Google's not so secret hope that the student contestants of today will be long-term contributors to these and other open source projects in the future. … … 22 22 6. Training: Tasks related to helping others learn more 23 23 7. Translation: Tasks related to localization 24 8. User Interface: Tasks related to user experience research or user interface design and interaction 24 8. User Interface: Tasks related to user experience research or user interface design and interaction 25 25 26 26 == How to Write a Task == … … 30 30 * Give it a descriptive title. 31 31 32 * Explain any acronyms or slang that an outsider would not know. 32 * Explain any acronyms or slang that an outsider would not know. 33 33 34 34 * List potential mentors and give both a recommended and an optional background. 35 35 36 36 * Also give an estimate for roughly how long this task should take. 37 37 38 38 * Provide as many links and background information as possible. 39 39 … … 64 64 Links: A list of links that should help the student start on this task. 65 65 66 Potential Mentor: The person we should list as the "owner" of the task, who will monitor student submissions and give the final sign-off. This should be either you or someone who you've talked to about taking this on. 66 Potential Mentor: The person we should list as the "owner" of the task, who will monitor student submissions and give the final sign-off. This should be either you or someone who you've talked to about taking this on. 67 67 68 68 [http://live.gnome.org/GoogleCodeIn/HowToWriteAGoodTask GNOME's How To Write a Good Task] … … 189 189 '''Details''': We would like a short paper (roughly 1000 words, with some charts/graphics) that compares and contrasts the Dalvik VM to Parrot VM, describing which characterists each shared, what things are different, how optimizations are done and which ideas Parrot can utilize from Dalvik. This paper should be in an open source format, and can take the form of a blog post or a POD file that can be included with the Parrot documentation or on the Parrot website. 190 190 191 '''Links''': 191 '''Links''': 192 192 193 193 http://parrot.org … … 211 211 '''Details''': We would like a short paper (roughly 1000 words, with some charts/graphics) that compares and contrasts the Neko VM to Parrot VM, describing which characterists each shared, what things are different, how optimizations are done and which ideas Parrot can utilize from Neko. This paper should be in an open source format, and can take the form of a blog post or a POD file that can be included with the Parrot documentation or on the Parrot website. 212 212 213 '''Links''': 213 '''Links''': 214 214 215 215 http://parrot.org … … 784 784 785 785 }}} 786 786 787 787 788 788 == Task : Increase test coverage of PMCs - This represents several tasks. == … … 798 798 PMCs according to test coverage: 799 799 {{{ 800 29.4 multisub.pmc 800 29.4 multisub.pmc 801 801 37.1 socket.pmc 802 802 45.5 role.pmc … … 806 806 67.9 eventhandler.pmc 807 807 71.1 undef.pmc 808 73.8 continuation.pmc 808 73.8 continuation.pmc 809 809 76.0 complex.pmc 810 810 76.9 bigint.pmc … … 920 920 921 921 '''Potential Mentor''': Whiteknight 922 923 924 == Task : Create a website for http://parrot.github.org == 925 926 '''Title''': Create a website for http://parrot.github.org 927 928 '''Category''': User Interface 929 930 '''Difficulty''': easy 931 932 '''Estimated time''': 4 hours 933 934 '''Task description''': Consists of: 935 936 * Parrot has a website at http://parrot.org. Github, where Parrot's source code repository will be, allows creating websites on its servers for users and organizations. The Parrot organization could use such a website to help direct new visitors to other resources. 937 * The new website can be a simple, single-page site. It does not need to be fancy. 938 * The new site should contain links to common Parrot resources including Parrot's home page, the issue tracker, the souce code repository, the mailing lists, and online documentation. 939 940 '''Benefits''': Users going to htp://parrot.github.org will be able to find the resources they are looking for without getting lost or confused. 941 942 '''Requirements''': Basic understanding of the web. Prior experience with markup languages (especially HTML/CSS, but also Markdown, Textile, or others would be fine). Ability to use Git a plus. 943 944 '''Links''': http://www.parrot.org 945 946 '''Potential Mentor''': Whiteknight 947