-
Notifications
You must be signed in to change notification settings - Fork 13
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
43c0687
commit cf1aa7a
Showing
3 changed files
with
55 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,53 @@ | ||
--- | ||
sidebar_position: 11 | ||
title: GSoC - Guidelines for Students | ||
title: GSoC - Guidelines | ||
--- | ||
|
||
# GSoC - Guidelines for Students | ||
# Google Summer of Code Contributor Guidelines | ||
|
||
Are you interested in participating in a Google Summer of Code project with SEF? We're excited to guide you toward becoming a successful GSoC contributor in our community. To assist you, we've compiled some guidelines and sessions that address your initial questions and provide insight into what is expected of students before proposal submission, after acceptance, and during the coding period. | ||
|
||
## Before the Application | ||
1. Familiarize yourself with SEF and the project(s) you're interested in. Refer to the Developer Guide, Getting Started as a Developer, and engage with the community for any queries. | ||
2. Explore project ideas and ask questions in the GSoC category on SEF Hive. | ||
3. Actively participate in SEF slack channel and SEF Hive. | ||
4. Introduce yourself on the introduction thread on SEF Hive. | ||
5. Contribute to SEF by working on github issues. Select issues from github, work on them, and submit pull requests to the respective repository. | ||
6. Identify potential issues in SEF projects. Create new github issues for unreported issues. | ||
7. Increase visibility on SEF Hive and Slack by helping others and engaging in discussions. | ||
8. Conduct code reviews. Reviewing others' code is essential for learning the SEF code base. | ||
|
||
**Additional Expectations:** | ||
- Write blogs about SEF or related topics to contribute valuable information to others. | ||
- Properly document your work in Hive and assist others in building on it. | ||
|
||
## After Being Accepted | ||
1. Set up a blog for your open source projects, including GSoC. Share the URL on SEF Hive and write weekly posts about planning and project progress during GSoC. | ||
2. Contact your mentor immediately and establish a regular communication plan. Use slack or discussions on SEF Hive for communication. | ||
3. CC your backup mentor in communications to keep them informed of your progress. | ||
4. Review github issues related to your project and work on initial bugs or feature development with guidance from your mentor. | ||
5. Prepare a detailed project plan with SMART goals and milestones, and publish it on SEF Hive. | ||
|
||
## During the Coding Period | ||
1. Submit a short weekly progress updates. | ||
2. Write a weekly blog post to share your work publicly. | ||
3. Commit early and often to align with our open-source community values. | ||
4. Prepare mid-term and final project presentation videos for the community. | ||
|
||
**Developer Community Expectations:** | ||
- Conduct all project-related discussions on slack or SEF Hive. | ||
- Ask questions in a smart way when facing challenges. | ||
- Participate in the weekly standup calls when your schedule allows. | ||
|
||
## After GSoC | ||
1. Write a final blog post summarizing your overall experience. Consider cross-posting to the Google Open Source Blog with approval from org admins. | ||
2. Stay involved with your project or other projects based on your schedule. | ||
3. Monitor SEF Hive for additional questions or feedback about your GSoC project and for other topics of interest. | ||
4. Consider participating as a mentor for GSoC, if SEF is accepted. Your involvement will inspire secondary school students to use their programming skills in open source projects. | ||
|
||
## GSoC Awareness Sessions | ||
We have conducted a few GSoC awareness sessions. Check out the links below: | ||
|
||
- [Sun's Out with Google Summer of Code 2024](https://www.youtube.com/live/o6rBv_5FfPo?si=CQCPvymFVX51q2DK) | ||
- [Sun's Out with Google Summer of Code 2023](https://www.youtube.com/live/2hFRHc_zNvU?si=uYzptEE-b_MU3tpu) | ||
- [Google Summer of Code Awareness Session](https://youtu.be/cso2YTD3z3s?si=nrmcT8hDKR-iwXTj) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
{ | ||
"label": "Handbook", | ||
"position": 8 | ||
"position": 11 | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters