|
12 | 12 | <link rel="stylesheet" href="css/icons.css"> |
13 | 13 | <link rel="stylesheet" href="css/responsee.css"> |
14 | 14 | <link rel="stylesheet" href="owl-carousel/owl.carousel.css"> |
15 | | - <link rel="stylesheet" href="owl-carousel/owl.theme.css"> |
| 15 | + <link rel="stylesheet" href="owl-carousel/owl.theme.css"> |
16 | 16 | <link rel="stylesheet" href="css/template-style.css"> |
17 | 17 | <link href='https://fonts.googleapis.com/css?family=Playfair+Display&subset=latin,latin-ext' rel='stylesheet' type='text/css'> |
18 | 18 | <link href='https://fonts.googleapis.com/css?family=Open+Sans:400,300,700,800&subset=latin,latin-ext' rel='stylesheet' type='text/css'> |
19 | 19 | <script type="text/javascript" src="js/jquery-1.8.3.min.js"></script> |
20 | | - <script type="text/javascript" src="js/jquery-ui.min.js"></script> |
| 20 | + <script type="text/javascript" src="js/jquery-ui.min.js"></script> |
21 | 21 | </head> |
22 | | - |
| 22 | + |
23 | 23 | <body class="size-1140"> |
24 | 24 | <a target="_blank" class="hide-s" href="https://github.com/PecanProject" style="position:fixed;top:120px;right:-14px;z-index:10;"><img src="images/view-on-github.png" alt="" style="width: 200px; padding-right: 10px;"></a> |
25 | | - |
| 25 | + |
26 | 26 | <!-- HEADER --> |
27 | 27 |
|
28 | | - <header role="banner" class="position-absolute"> |
| 28 | + <header role="banner" class="position-absolute"> |
29 | 29 | <!-- Top Navigation --> |
30 | 30 | <nav class="background-dark background-transparent-hightlight full-width"> |
31 | 31 | <div class="s-12 l-2"> |
|
37 | 37 | </a> |
38 | 38 | </div> |
39 | 39 | <div class="top-nav s-12 l-10 background-dark"> |
40 | | - |
| 40 | + |
41 | 41 | <ul class="right chevron"> |
42 | 42 | <li><a href="index.html">Home</a></li> |
43 | 43 | <li><a>About</a> |
|
57 | 57 | </ul> |
58 | 58 | </li> |
59 | 59 | <li><a href="http://opensource.ncsa.illinois.edu/projects/artifacts.php?key=PECAN">Download</a></li> |
60 | | - <li><a>Google</a> |
| 60 | + <li><a>GSoC</a> |
61 | 61 | <ul> |
62 | | - <li><a href="gsoc.html" style="color: black;font-weight: 800;"> GSoC </a></li> |
63 | | - <li><a href="gsod.html" style="color: black;font-weight: 800;"> GSoD </a></li> |
| 62 | + <li><a href="gsoc.html" style="color: black;font-weight: 800;"> Contributor Guidance </a></li> |
| 63 | + <li><a href="gsoc_ideas.html" style="color: black;font-weight: 800;"> Ideas List </a></li> |
64 | 64 | </ul> |
65 | 65 | </li> |
66 | 66 | <li><a href="Report_an_issue.html">Bug Report</a></li> |
67 | 67 | </ul> |
68 | 68 | </div> |
69 | 69 | </nav> |
70 | 70 | </header> |
71 | | - |
| 71 | + |
72 | 72 | <!-- MAIN CONTENT --> |
73 | 73 |
|
74 | 74 | <div id="main_content_wrap" class="outer"> |
75 | 75 | <section id="main_content" class="inner" style="padding-top: 80px;"> |
76 | | - |
| 76 | + |
77 | 77 | <h1><a name="background" class="anchor" href="#background"><span class="octicon octicon-link"></span></a><a href="https://summerofcode.withgoogle.com/">Google Summer of Code (GSoC)</a></h1> |
78 | | - |
79 | | -<h5>What is GSoC?</h5> |
| 78 | + |
| 79 | +<h2>What is GSoC?</h2> |
80 | 80 | For over 10 years Google has sponsored a global program that pairs students with open source software development projects. For three months over the summer students receive real world experience contributing to software development and guidance from mentors. On the other hand, participating organizations are able to bring in new developers to grow their code base. Overall, GSoC helps open source communities grow and thrive. Thousands of student and organization from around the world have participated and now you can too! |
81 | 81 | <p> </p> |
82 | 82 | |
83 | 83 |
|
84 | | -<h5><a href="gsoc_ideas.html">Project Ideas</a></h5> |
| 84 | +<h2><a href="gsoc_ideas.html">Project Ideas</a></h2> |
85 | 85 |
|
| 86 | +Ecosystem science has many components, so does PEcAn! Some Project ideas can be found here on our <a href="gsoc_ideas.html">project ideas list.</a> |
86 | 87 |
|
87 | | -<p>Ecosystem science has many components, so does PEcAn! Some Project ideas can be found here on our <a href="gsoc_ideas.html">project ideas list.</a></p> |
88 | | - |
89 | | - |
| 88 | +<p> </p> |
90 | 89 |
|
91 | | - <h4><a href="gsoc_apply.html">How to apply?</a></h4> |
92 | | - |
93 | | - <h6>There are Two Parts to the application process:</h6> |
94 | | - |
95 | | -First, follow the PEcAn specific application steps: |
| 90 | +<h2><a href="gsoc_apply.html">How to apply?</a></h2> |
96 | 91 |
|
97 | | -<p>1. Choose a project from our <a href="gsoc_ideas.html">project ideas list</a> or come up with your own.</p> |
98 | | -<p>2. Fill out <a href="https://forms.gle/dogSK8Pv1852UxMeA">PEcAn GSoC application form</a>. The form is self-explanatory.</p> |
99 | | -<p>* Please fill out the form in a timely manner so that we can review it sooner and give you feedback. *</p> |
100 | | -<p>3. Send an email/message to your project-specific mentors indicating that you have completed the form, attach your resume or CV.</p> |
| 92 | +There are two steps to the application process: |
101 | 93 |
|
| 94 | +<ol> |
| 95 | + <li>Getting acquainted with the project, mentors and ideas</li> |
| 96 | + <li>Writing a good proposal</li> |
| 97 | +</ol> |
102 | 98 |
|
103 | | -Second, write and submit your GSoC proposal: |
| 99 | +<p> </p> |
104 | 100 |
|
| 101 | +<h3>Getting acquainted with the project, mentors and ideas</h3> |
105 | 102 |
|
106 | | -<p>1. With guidance from your mentors, write your proposal.</p> |
107 | | -<p>2. Start coding! Go on our Slack channels and github repository and start coding! </p> |
| 103 | +The first step is for you to get acquainted with the PEcAn project, the ideas and to introuduce |
| 104 | +yourself with the mentors. This will help you get a significantly better proposal, and will |
| 105 | +make it more like for us to rate your propsal higher. |
108 | 106 |
|
109 | | - |
| 107 | +<p> </p> |
| 108 | + |
| 109 | +<ul> |
| 110 | + <li>Choose a project from our <a href="gsoc_ideas.html">project ideas list</a> or come up with your own.</li> |
| 111 | + <li>Join the #gsoc-2022 channel in our slack workspace and introduce yourself</li> |
| 112 | + <li>Send message to your project-specific mentors indicating that you are interested in their idea and how you plan to implement the idea</li> |
| 113 | +</ul> |
110 | 114 |
|
111 | | -<h5>Tips for your proposal</h5> |
| 115 | +<p> </p> |
112 | 116 |
|
113 | | -Our <a href="gsoc_ideas.html">project ideas list</a> and your exchange with the mentors should give an idea what <em>we</em> had in mind, but a good GSOC proposal is one that makes the project <em>yours</em>. Feel free to propose something we didn't think of! Although we hope your proposal incorporates items from our wish-lists, it need not implement everything. We expect that many of the tasks will require care and thought to do correctly, and we'd rather you finish the summer with a few features working well than with many roughed out. A successful proposal will tell us: |
114 | | -<p> </p> |
115 | | - |
| 117 | +When talking to the mentors, use the following questions to introuduce yourself: |
| 118 | + |
| 119 | +<p> </p> |
116 | 120 |
|
117 | 121 | <ul> |
118 | | -<li><p>What specific features you plan to implement, with at least an approximate timeline.</p></li> |
119 | | -<li><p>How your existing skills will help you implement these features</p></li> |
120 | | -<li><p>What new skills you will need to learn (make sure the time to learn them is included in your timeline!)</p></li> |
121 | | -<li><p>How your work on this project will advance the scientific goals of the PEcAn project</p></li> |
122 | | -<li><p>Which features are must-haves to consider the project successful, and which are stretch goals to be done as time allows</p></li> |
123 | | -<li><p>What kind of contributions you expect to need from the rest of the PEcAn team; e.g. answering questions about R, help implementing tests of specific ecosystem models, code review, etc. If you'll need help from a specific person who's not your project mentor, have you discussed the proposal with them before submitting it?</p></li> |
| 122 | + <li>What interests you most about our project?</li> |
| 123 | + <li>What is your background, and what made you pick the specific idea?</li> |
| 124 | + <li>What is your familiarity with the recommended technologies?</li> |
| 125 | + <li>As mentors and project coordinators, how can we get the best out of you?</li> |
| 126 | + <li>Is there anything that you’ll be studying or working on whilst working alongside us?</li> |
124 | 127 | </ul> |
125 | 128 |
|
| 129 | +<p> </p> |
126 | 130 |
|
127 | | -<p> </p> |
128 | | - |
| 131 | +<h3>Writing a good proposal</h3> |
| 132 | + |
| 133 | +Next, write and submit your GSoC proposal after discussing this with the mentor. In the prooposal make sure to |
| 134 | +include a well-defined, weekly schedule with clear milestones and deliverables around it. Make sure to include |
| 135 | +in your schedule any time you need to learn new technologies, as well as make sure that before the |
| 136 | +evaluations dates, you have a deliverable that we can use to evaluate. We understand that schedules change, but it |
| 137 | +would be good to add some must haves to your list of deliverables that will make your project a success as well |
| 138 | +as some extra goals in case you have additional time at the end. |
129 | 139 |
|
| 140 | +<p> </p> |
130 | 141 |
|
131 | 142 | See also <a href="https://google.github.io/gsocguides/student/writing-a-proposal.html">Google's proposal guidelines</a> |
132 | 143 |
|
| 144 | +<p> </p> |
| 145 | + |
| 146 | +Good Luck |
133 | 147 | </section> |
134 | 148 | </div> |
135 | 149 |
|
136 | | - <!-- scripts --> |
137 | | - |
| 150 | + <!-- scripts --> |
| 151 | + |
138 | 152 | <script type="text/javascript" src="js/responsee.js"></script> |
139 | 153 | <script type="text/javascript" src="owl-carousel/owl.carousel.js"></script> |
140 | 154 | <script type="text/javascript" src="js/template-scripts.js"></script> |
@@ -163,6 +177,6 @@ <h5>Tips for your proposal</h5> |
163 | 177 | }; |
164 | 178 | </script> |
165 | 179 |
|
166 | | - |
| 180 | + |
167 | 181 | </body> |
168 | 182 | </html> |
0 commit comments