You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/mentor/18-making_your_ideas_page.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,14 +8,17 @@ sidebar: mentor_sidebar
8
8
9
9
It all begins with the "Ideas Page". This is where you compile a list of possible GSoC projects for your organization. The Ideas Page is a major piece of your organization's application to Google. It also serves as a recruiting and selection tool for GSoC contributors and mentors alike.
10
10
11
-
Depending on how your organization operates, the source of material for your Ideas Page may come from an existing list of projects maintained by your community year-round, from potential mentors as they are recruited, or from the org admin. Regardless of how it is generated, an Ideas Page should have the following:
11
+
Depending on how your organization operates, the source of material for your Ideas Page may come from an existing list of projects maintained by your community year-round, from potential mentors as they are recruited, or from the org admin. Regardless of how it is generated, an Ideas Page should have the following listed for each Project Idea:
12
12
13
-
* Brief descriptions of projects that can be completed in ~90 hour, ~175 hours or ~350 hours of your GSoC contributor's time (and labeled appropriately).
14
-
* For each project, a list of prerequisites, description of programming skills needed and estimation of difficulty level (easy, medium, hard).
15
-
* If your organization plans to focus on mostly student level potential GSoC contributors for all projects that is fine, but please state it explicitly on your Ideas Page. Or if a given project idea is geared more toward a student level or a more advanced developer please state it clearly in the project idea so there is no confusion for applicants.
13
+
* Brief description of project (usually 3-5 sentences, can be longer).
14
+
* List whether the project is scoped to be a ~90 hour (small), ~175 hour (medium) or ~350 hour (large) project.
15
+
* List prerequisites, including a description of programming skills needed
16
+
* Include an estimation of difficulty level (easy, intermediate, hard).
16
17
* A list of potential mentors.
17
18
* It must NOT be a link to your bug tracker.
18
19
20
+
If your org only plans to accept 1 or 2 GSoC contributors due to the number of mentors you have lined up (or if your org is a new org to GSoC) that is okay but you should state at the top of your Ideas List that is your intention. Otherwise GSoC Admins will think you haven't put in the time and effort with your ideas when we only see 1 or 2 ideas listed. GSoC Admins will interpret that as your org isn't prepared to be a GSoC org.
21
+
19
22
The best pages include links to more detailed descriptions and related materials for each project. They might even include actual use cases!
20
23
21
24
While the Ideas page doesn't have to be 'beautiful,' cluttered and ugly won't be attracting many participants to apply to your org either. Make it clean, which could mean more line breaks or some bold, bigger fonts when appropriate. Blocks of text are not welcoming.
0 commit comments