├── .github └── ISSUE_TEMPLATE │ ├── config.yml │ └── gsoc-idea.md ├── IDEA-template.md ├── LICENSE ├── MENTOR-contribution-guide.md ├── README.md ├── STUDENT-contribution-guide.md └── STUDENT-proposal-template.md /.github/ISSUE_TEMPLATE/config.yml: -------------------------------------------------------------------------------- 1 | blank_issues_enabled: true 2 | contact_links: 3 | - name: ESIP GSOC GitHub page 4 | url: http://github.com/ESIPFed/gsoc 5 | about: Please review this page for information about ESIP Summer of Code (contact details are at end of page) . 6 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/gsoc-idea.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: GSoC Idea 3 | about: Propose an ESIP idea for Google Summer of Code 4 | title: "[GSoC Idea] " 5 | labels: 'GSoC 2020' 6 | assignees: '' 7 | 8 | --- 9 | 10 | # ESIP Member Organization Name 11 | Your organization: 12 | 13 | ## Mentors 14 | 15 | Please list the names of available mentors 16 | 17 | ## Information for Students 18 | 19 | If you have special information / instructions for an application you should 20 | list/link to it here. If not you can delete it. Please keep in mind that we 21 | do have some general instructions for students at the 22 | [ESIP Student Guide](https://github.com/ESIPFed/gsoc/blob/master/STUDENT-contribution-guide.md). 23 | 24 | ## Project Idea: 25 | 26 | ### Abstract 27 | 28 | ### Technical Details 29 | 30 | Long description of the project. **Should** include all technical details of the 31 | projects like libraries involved. Please also link to relevant docs / issues / theory / 32 | papers for your project if available. 33 | 34 | ### Helpful Experience 35 | 36 | List of background experience that we would like / expect from the student. 37 | 38 | ### First steps 39 | 40 | Students doesn't need to do this before Google Summer of Code code period starts 41 | but will be good if they do just because they will be sure if this is how they 42 | want to spend the summer. 43 | -------------------------------------------------------------------------------- /IDEA-template.md: -------------------------------------------------------------------------------- 1 | # ESIP Member Organization Name 2 | 3 | ## Mentors 4 | 5 | Please list the names of available mentors 6 | 7 | ## Information for Students 8 | 9 | If you have special information / instructions for an application you should 10 | list/link to it here. If not you can delete it. Please keep in mind that we 11 | do have some general instructions for students. 12 | 13 | ## Project Ideas 14 | 15 | ### Idea Title 16 | 17 | #### Abstract 18 | 19 | #### Technical Details 20 | 21 | Long description of the project. **Should** include all technical details of the 22 | projects like libraries involved. Please also link to relevant docs / issues / theory / 23 | papers for your project if available. 24 | 25 | #### Helpful Experience 26 | 27 | List of background experience that we would like / expect from the student. 28 | 29 | #### First steps 30 | 31 | Students doesn't need to do this before Google Summer of Code code period starts 32 | but will be good if they do just because they will be sure if this is how they 33 | want to spend the summer. 34 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /MENTOR-contribution-guide.md: -------------------------------------------------------------------------------- 1 | # Contributing Guide for Mentors 2 | ## Organizations Eligible Under ESIP Umbrella 3 | 4 | To be eligible to participate in GSoC under the ESIP umbrella, any individual submitting an 5 | idea must: 6 | 7 | 1. Be employed at a current ESIP member organization. 8 | 2. Be willing to commit for the full GSoC period (see timeline [here](https://summerofcode.withgoogle.com/how-it-works/)). 9 | 3. Be a willing and engaged mentor. 10 | 11 | When you submit your idea, please contact us (lab@esipfed.org) and tell us your preferred way for students 12 | to contact you. 13 | 14 | ## Mentors Project Guidance 15 | To participate in a mentor for GSOC, you must submit a project idea. Please read the below guidance before submitting an idea. 16 | 17 | ### Projects 18 | 19 | Please make sure that the project can be partly completed during the summer so 20 | that students pass the final evaluation. Please also read 21 | the [student guide](/STUDENT-contribution-guide.md), paying particular attention to what we require from students. 22 | 23 | To ensure a project can be completed, we recommend as a guideline that the 24 | project should be possible to complete by the mentor in about one week of full 25 | time work. This doesn't sound like a lot of time but students generally take 26 | much longer then a long-time developer. They have to get familiar with the code 27 | and have to acquire a huge amount of domain knowledge. 28 | 29 | There has to be at least one primary mentor and one backup mentor per project. 30 | This means you should have at least 2 mentors available. A mentor can only be 31 | 'primary' for one student but a backup for as many as they like. 32 | 33 | If you have a project idea, you can use our [idea templates](https://github.com/ESIPFed/gsoc/blob/master/IDEA-template.md) and 34 | publish it to the [issues page](https://github.com/ESIPFed/gsoc/issues) for this repo. 35 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Google Summer of Code 2 | 3 | [![Join the chat at https://gitter.im/ESIPFed/gsoc](https://badges.gitter.im/ESIPFed/gsoc.svg)](https://gitter.im/ESIPFed/gsoc?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) 4 | 5 | 6 | 7 | 8 | Earth Science Information Partners (ESIP) will be applying again as an umbrella mentoring organization 9 | for [Google Summer of Code 2020][GSOC]. [ESIP][ESIP] is funded by NASA, NOAA, and USGS and supports the development of visionary Earth science technologies that advance our knowledge of Earth system science. 10 | 11 | We are looking to recruit talented GSoC students to help us push the state-of-the-art in Earth sciences cyberinfrastruction. We plan to post all code contributed by GSoC students for dissemination to the general public under open source licenses. 12 | 13 | ## Mentors 14 | * [Mentor Contribution Information][MCG] 15 | 16 | ## Students 17 | * [Student Contribution Information][SCG] 18 | * [Student Proposal Template][SPT] 19 | 20 | ### Questions? 21 | 22 | Contact us: lab@esipfed.org 23 | 24 | More questions? Check out the GSoC mentor/student guides here: https://google.github.io/gsocguides/ 25 | 26 | [ESIP]: https://esipfed.org 27 | [GSOC]: https://summerofcode.withgoogle.com/ 28 | [MCG]: MENTOR-contribution-guide.md 29 | [SPT]: STUDENT-proposal-template.md 30 | [SCG]: STUDENT-contribution-guide.md 31 | -------------------------------------------------------------------------------- /STUDENT-contribution-guide.md: -------------------------------------------------------------------------------- 1 | 2 | **Table of Contents** 3 | 4 | - [Contributing Guide for Students](#contributing-guide-for-students) 5 | - [Getting Started Early](#getting-started-early) 6 | - [Am I experienced enough?](#am-i-experienced-enough) 7 | - [Our Expectations From Students](#our-expectations-from-students) 8 | - [Default Instructions](#default-instructions) 9 | - [How to write a great Proposal](#how-to-write-a-great-proposal) 10 | - [Dividing your project](#dividing-your-project) 11 | - [How to estimate time needed for development](#how-to-estimate-time-needed-for-development) 12 | - [Final Proposal](#final-proposal) 13 | 14 | 15 | 16 | 17 | # Contributing Guide for Students 18 | 19 | ## Getting Started Early 20 | 21 | Experience shows that the best thing to help your application is to contact the 22 | organization you want to work with early. For this you can introduce yourself on 23 | the mailing list of the organization, maybe fix a small 24 | bug. [The opensource guide](https://opensource.guide/how-to-contribute/) has a 25 | good introduction how to start contributing to open source projects. 26 | 27 | ## Am I experienced enough? 28 | 29 | The answer is generally: **Yes**. We value creativity, intelligence and 30 | enthusiasm above specific knowledge of the libraries or algorithms we use. We 31 | think that an interested and motivated student who is willing to learn is more 32 | valuable than anything else. The range of available projects should suit people 33 | with different backgrounds. At the same time if you have experience using your 34 | project of choice or one of its dependencies (e.g. language) make sure to let 35 | us know about that as 36 | well. 37 | [FLOSS manual](http://write.flossmanuals.net/gsocstudentguide/am-i-good-enough/) 38 | gives a good overview of this part for GSoC. 39 | 40 | ## Our Expectations From Students 41 | 42 | ### During the application phase 43 | 44 | *The tips listed here can help your application. They are not required* 45 | 46 | Organizations usually favor students that show a regular communication with 47 | possible mentors / organization until Google announces the accepted projects. 48 | 49 | Establishing a regular communication is good for 2 reasons. It shows that you 50 | are a reliable student and that you have good communication skills. Good 51 | communication skills are an important part of GSoC since a student and mentor 52 | can rarely meet in person. 53 | 54 | When we evaluate an application we use the following point system to get a 55 | baseline comparison of students. We are listing those points to help you 56 | successfully apply and not missing an obvious point. You can always do more, but 57 | please check those points. We will be fair, we promise. You can always ask us 58 | and we will help you. 59 | 60 | - 5pts Communicated with us org mentors ? 61 | - 5pts Communicated with the community ? 62 | - 5pts Do you reference projects you coded WITH links to repos or provided code? 63 | - 5pts Do you provide all demanded ways of contact (email, skype, mobile/phone, and twitter, chat and/or skype if available) 64 | - 3pts Do you add a preliminary project plan (before, during, after GSOC)? 65 | - 3pts Do you state which project you are applying for and why you think you can do that? 66 | - 3pts Do you have time for GSOC? This is a paid job! State that you have time in your motivation letter, and list other commitments! 67 | - 1pts Added a link to ALL your application files to a cloud hoster like github or dropbox? (easy points! 😉 ) 68 | - 0pts Be honest! Only universal Karma points. 🙂 69 | - 5pts Did you push code to the existing code? Or did you do a bugfix? 70 | - 5pts Communication until accepted students are announced. 71 | 72 | ### During the summer 73 | 74 | *The items here are a requirement for students during the summer* 75 | 76 | **Communication** 77 | 78 | - Write a short report for us every second week in a blog 79 | - Commit early and commit often! Push to a public repository (e.g. github) so 80 | that we can see and review your work. 81 | - Actively work on our project timeline and communicate with us during the 82 | community bonding period. 83 | - Communicate every working day with your mentor. Preferably in public using the 84 | standard channels of your project. 85 | - If there is a reason why you can't work or can't contact us on a regular basis 86 | please make us aware of this. 87 | - If you don't communicate with us regularly we will fail you. 88 | 89 | **Evaluations** 90 | 91 | - Set a realistic goal for all evaluation deadlines. If you fail to meet your 92 | own goal we are more likely to fail you in the evaluations. 93 | - Communicate ASAP with the project mentor if evaluation metrics are unclear. 94 | 95 | **Blog** 96 | 97 | - keep a regular journal of your experience as a student and blog at least once 98 | every 2 weeks. 99 | 100 | ## Default Instructions 101 | 102 | **This is a general guide. Organizations can have different instructions and you 103 | must follow their instructions** 104 | 105 | Projects proposed by mentors are listed at our [issues page](https://github.com/ESIPFed/gsoc/issues). 106 | 107 | You are welcome to propose your own project. If you wish to do so, please 108 | contact the organization you want to work with before you start writing your 109 | proposal and explain your idea to them. If you choose to propose your own 110 | project idea you will need to find a mentor for the project. **Proposals without 111 | a mentor will not be considered.** 112 | 113 | ### How to write a great Proposal 114 | 115 | Firstly, think about your choice of project carefully, you're going to be doing 116 | it for a couple of months, so it's important that you choose something you're 117 | going to enjoy. Once you've made your mind up: 118 | 119 | 1. Make sure you've thought about the project and understand what it entails. 120 | 2. Contact us early! The earlier you contact us the earlier you will be able to 121 | get feedback from us to improve your application. 122 | 3. Don't be afraid to come up with original solutions to the problem. 123 | 4. Don't be afraid to give us lots of detail about how you would approach the 124 | project. 125 | 126 | Overall, your application should make us believe that you are capable of 127 | completing the project and delivering the functionality to our users. If you 128 | aren't sure about anything, get in touch with us, we're happy to advise you. 129 | 130 | ### How to estimate time needed for development 131 | 132 | To get experience with a code base we recommend you try to fix some 133 | easy/beginner bug or refactor a piece of code that doesn't conform to the 134 | current style guides. Look at the code that you want to change, check if it 135 | follows our coding guidelines. Do some research on the API's you want to use, 136 | plan what classes you will add and how their public API will look. Write down 137 | your algorithms in pseudo code. The better your research is and the better you 138 | plan ahead the easier it will be to judge how long a given task will take. For 139 | your time estimates you should also consider that you can do less stuff during 140 | exams and try to be a bit conservative. If you have never done anything like 141 | GSoC before you will tend to underestimate the time to complete a task. We know 142 | that giving these estimates is not easy and that also professionals have 143 | problems with it. Having a good plan, knowing its weak and strong points will 144 | help a lot. 145 | 146 | ### Final Proposal 147 | 148 | Your final proposal must be submitted to [GSoC](summerofcode.withgoogle.com) as 149 | a PDF file, using [this template](https://github.com/ESIPFed/gsoc/blob/master/STUDENT-proposal-template.md). Your proposal name should start with *[esip-member-name]* to make 150 | identification easier for the mentors. To convert a draft that you have written 151 | before into PDF you can use [Pandoc][Pandoc]. 152 | 153 | ~~~ 154 | $ pandoc -f markdown -t pdf YYYY/proposals/your-name.md 155 | ~~~ 156 | 157 | [issues]: https://github.com/esip/gsoc/issues 158 | [GSoC]: http://summerofcode.withgoogle.com/ 159 | [Pandoc]: http://pandoc.org/ 160 | -------------------------------------------------------------------------------- /STUDENT-proposal-template.md: -------------------------------------------------------------------------------- 1 | # Title 2 | 3 | ## Abstract 4 | 5 | Short description of your project. Max 10 sentences. This **SHOULD NOT** be a 6 | copy of the project idea text. 7 | 8 | ## Technical Details 9 | 10 | Long description of the project. **Must** include all technical details of the 11 | projects like libraries involved. 12 | 13 | Here it is important to show if you had previous conversations with your 14 | mentors. You can show relevant pieces of code that you want to change. You can 15 | link to literature you used during the research. 16 | 17 | ## Schedule of Deliverables 18 | 19 | Here should come a list of your milestones. This list is a start based on the 20 | difference phases of GSoC. Use it as a start. You can/should add more details 21 | for each phase by breaking it down into weeks or set specific targets for each 22 | phase. Each target should be split into sub task with a time estimate, [work 23 | breakdown structures][wbs] are helpful here. 24 | 25 | ### **Community Bonding Period** 26 | 27 | This phase is to get to know the community better. Check that your build 28 | environment is setup. This time should also be used to discuss your project in 29 | more detail with the community and in general introduce it. 30 | 31 | *Note:* We require you to write regular blog posts. Now is a good time to make 32 | sure your blog works and send us the link. 33 | 34 | ### **Phase 1** 35 | 36 | Delieverables 37 | 38 | ### **Phase 2** 39 | 40 | Delieverables 41 | 42 | ### **Final Week** 43 | 44 | At this stage you should finish up your project. At this stage you should make 45 | sure that you have code submitted to your organization. Our criteria to mark 46 | your project as a success is to submit code before the end of GSoC. 47 | 48 | ## Development Experience 49 | 50 | Do you have code on github? Can you show previous contributions to other projects? 51 | Did you do other code related projects or university courses? 52 | 53 | ## Other Experiences 54 | 55 | 56 | ## Why this project? 57 | 58 | --------------------------------------------------------------------------------