Skip to content

Commit c98f69e

Browse files
authored
Update GSoC contributor page (#165)
1 parent abc2e7a commit c98f69e

File tree

1 file changed

+103
-53
lines changed

1 file changed

+103
-53
lines changed

src/pages/gsoc.js

Lines changed: 103 additions & 53 deletions
Original file line numberDiff line numberDiff line change
@@ -1,95 +1,145 @@
11
import React from "react";
22
import Layout from "@theme/Layout";
3+
import Link from "@docusaurus/Link";
34
import styles from "./about.module.css";
45
import clsx from "clsx";
6+
57
function gsoc() {
68
return (
7-
<Layout title="About">
9+
<Layout title="Google Summer of Code (GSoC)">
810
<div className={styles.aboutContainer}>
9-
<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>
11+
<h1>
12+
<a id="background" className="anchor" href="#background" aria-label="Background">
13+
<span className="octicon octicon-link" aria-hidden="true"></span>
14+
</a>
15+
<a href="https://summerofcode.withgoogle.com/">
16+
Google Summer of Code (GSoC)
17+
</a>
18+
</h1>
1019
<div className={clsx(styles.cardContainer)}>
1120
{" "}
12-
13-
<div class="card">
14-
<div class="card__header" style={{ textAlign: "center" }}>
15-
16-
</div>
17-
<div class="card__body">
18-
19-
21+
<div className="card">
22+
<div className="card__body">
2023
<h2>What is GSoC?</h2>
21-
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!
22-
<p> </p>
23-
&nbsp;
24-
25-
<h2><a href="/gsoc_ideas/">Project Ideas</a></h2>
26-
27-
Ecosystem science has many components, so does PEcAn! Some Project ideas can be found here on our <a href="/gsoc_ideas/">project ideas list.</a>
24+
<p>
25+
Google Summer of Code is a global program that pairs contributors
26+
with open source software projects. Over the summer, contributors
27+
gain real-world experience contributing to software development and
28+
working with mentors, while participating organizations grow their
29+
communities and codebases.
30+
</p>
2831

2932
<p>&nbsp;</p>
3033

31-
<h2><a href="#how-to-apply" onClick={(e) => e.preventDefault()}>How to apply?</a></h2>
32-
33-
There are two steps to the application process:
34+
<h2>
35+
<Link to="/gsoc_ideas/">Project Ideas</Link>
36+
</h2>
3437

35-
<ol>
36-
<li>Getting acquainted with the project, mentors and ideas</li>
37-
<li>Writing a good proposal</li>
38-
</ol>
38+
<p>
39+
Ecosystem science has many components, so does PEcAn. Some project
40+
ideas can be found on our{" "}
41+
<Link to="/gsoc_ideas/">project ideas list</Link>.
42+
Contributors are also welcome to develop new ideas with feedback from
43+
the community.
44+
</p>
3945

4046
<p>&nbsp;</p>
4147

42-
<h3>Getting acquainted with the project, mentors and ideas</h3>
48+
<h2>Getting Started</h2>
4349

44-
The first step is for you to get acquainted with the PEcAn project, the ideas and to introuduce
45-
yourself with the mentors. This will help you get a significantly better proposal, and will
46-
make it more like for us to rate your propsal higher.
50+
<p>
51+
If you are interested in contributing to PEcAn through GSoC, the
52+
best place to start is our{" "}
53+
<a href="https://github.com/PecanProject/pecan/discussions/3469">
54+
getting started discussion
55+
</a>.
56+
{" "}Please read that page first and follow the instructions there.
57+
</p>
4758

4859
<p>&nbsp;</p>
4960

61+
<h3>A few good places to start</h3>
62+
5063
<ul>
51-
<li>Choose a project from our <a href="/gsoc_ideas/">project ideas list</a> or come up with your own.</li>
52-
<li>Join the <a href="https://pecanproject.slack.com/archives/C0853U6GF71" target="_blank" rel="noopener noreferrer">#gsoc-2025</a> channel in our slack workspace and introduce yourself</li>
53-
<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>
64+
<li>
65+
Read the{" "}
66+
<a href="https://github.com/PecanProject/pecan/discussions/3469">
67+
getting started discussion
68+
</a>
69+
, along with our{" "}
70+
<a href="https://github.com/PecanProject/pecan/blob/develop/CONTRIBUTING.md">
71+
contributing guide
72+
</a>{" "}
73+
and{" "}
74+
<a href="https://github.com/PecanProject/pecan/blob/develop/CODE_OF_CONDUCT.md">
75+
code of conduct
76+
</a>.
77+
</li>
78+
<li>
79+
Review our <Link to="/gsoc_ideas/">project ideas list</Link> and
80+
identify one or two ideas that interest you.
81+
</li>
82+
<li>
83+
Join the{" "}
84+
<a
85+
href="https://pecanproject.slack.com/archives/C0853U6GF71"
86+
target="_blank"
87+
rel="noopener noreferrer"
88+
>
89+
#gsoc
90+
</a>{" "}
91+
channel in Slack and introduce yourself.
92+
</li>
93+
<li>
94+
Improve documentation, work on tests, or help triage open pull
95+
requests and issues.
96+
</li>
97+
<li>
98+
Look for a{" "}
99+
<a href="https://github.com/search?q=org%3APecanProject+label%3A%22good+first+issue%22+&type=issues">
100+
good first issue
101+
</a>{" "}
102+
when you are ready to start contributing code.
103+
</li>
54104
</ul>
55105

56106
<p>&nbsp;</p>
57107

58-
<h3>When talking to the mentors, use the following questions to introuduce yourself:</h3>
108+
<h2>Applying to GSoC</h2>
59109

60-
<ul>
61-
<li>What interests you most about our project?</li>
62-
<li>What is your background, and what made you pick the specific idea?</li>
63-
<li>What is your familiarity with the recommended technologies?</li>
64-
<li>As mentors and project coordinators, how can we get the best out of you?</li>
65-
<li>Is there anything that you’ll be studying or working on whilst working alongside us?</li>
66-
</ul>
110+
<p>
111+
After reviewing the project ideas and getting started guidance, reach out
112+
in Slack. Contact the project mentor(s) if you have questions about a
113+
specific project idea.
67114

68-
<p>&nbsp;</p>
115+
If multiple mentors are listed, create a thread with all mentors. This
116+
helps us give more efficient and consistent feedback.
69117

70-
<h3>Writing a good proposal</h3>
118+
Becoming part of the community before submitting a proposal is important.
119+
Proposals submitted at the last minute, without prior engagement with the
120+
project or mentors, are much less likely to be competitive.
71121

72-
Next, write and submit your GSoC proposal after discussing this with the mentor. In the proposal make sure to
73-
include a well-defined, weekly schedule with clear milestones and deliverables around it. Make sure to include
74-
in your schedule any time you need to learn new technologies, as well as make sure that before the
75-
evaluations dates, you have a deliverable that we can use to evaluate. We understand that schedules change, but it
76-
would be good to add some must haves to your list of deliverables that will make your project a success as well
77-
as some extra goals in case you have additional time at the end.
122+
Once you have gotten acquainted with the project and discussed your
123+
interests with potential mentors, you can begin drafting your proposal.
124+
A strong proposal should include a realistic timeline, clear milestones,
125+
and concrete deliverables.
126+
</p>
78127

79128
<p>&nbsp;</p>
80129

81-
See also <a href="https://google.github.io/gsocguides/student/writing-a-proposal.html">Google's proposal guidelines</a>
130+
<p>
131+
See also{" "}
132+
<a href="https://google.github.io/gsocguides/student/writing-a-proposal.html">
133+
Google&apos;s proposal guidelines
134+
</a>.
135+
</p>
82136

83137
<p>&nbsp;</p>
84138

85-
Good Luck
86-
87-
88-
139+
<p>Good luck</p>
89140
</div>
90141
</div>
91142
</div>
92-
93143
</div>
94144
</Layout>
95145
);

0 commit comments

Comments
 (0)