Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating GSoC template file #41

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 9 additions & 5 deletions google-summer-of-code/GSOC-STUDENT-TEMPLATE.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,12 +7,16 @@
- Start as early as possible; Make first contacts with the mentors before starting to fill in the proposal and make sure to discuss your project idea.
- Share the first draft of your proposal as early as possible; Do not copy-paste from the official project description.
- Share the proposal link as text, markdown, Google docs or anything else as long as it is easy to share, and will not require anyone to download something.
- Final proposals should be submitted on the Google Summer of Code website before the deadline and after all the reviews have been done.
- Final proposals should be submitted on the Google Summer of Code website before the deadline and after all the reviews have been done.

> Remove this section while you are writing the proposal. These pointers are purely meant for communicating the right details with the developers interested in proposing their ideas.
### GSoC Template [Link](https://docs.google.com/document/d/1A6PnUWaxuFcl4Mwydgq7WluHJ1XkYVd5cX_-fSwgXpo/edit#)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add this as a footnote for people to copy this if they are doing this on Google Docs

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, So should I put the link to the template in the footnotes?


## Title

### Personal Details

> This will include basic personal details. Which include your Name, Email, Github, LinkedIn, and Country. You add or more fields based on your preference. With the help of this information we can contact the candidate in case of any need.
SanjaySinghRajpoot marked this conversation as resolved.
Show resolved Hide resolved

### Abstract

> Add a short description of your project. Do not copy-paste from the official project description and add your perspective about the project as well. Do not exceed 10 lines of text. Define the problem/issue, express the current state and finally propose a solution.
Expand All @@ -39,8 +43,8 @@

### About me

> Add your name, personal details and contact information (Slack ID, E-Mail). Optionally, add why you would you consider yourself as the best person for this project.
> Introduce yourself here in a brief manner. Try to answer basic qustions like Who are you? What are your interest?. Add your name, personal details and contact information (Slack ID, E-Mail).
SanjaySinghRajpoot marked this conversation as resolved.
Show resolved Hide resolved

### Appendix
### What you expect from the mentor? (optional)
SanjaySinghRajpoot marked this conversation as resolved.
Show resolved Hide resolved

> Mention any external references, information, hyperlinks here.
> This field is optional. You can put your preference for what kind of mentorship will work the best for you. Anything that you want your mentor to have or follow. Anything regarding tech stack or experience can be put here.
SanjaySinghRajpoot marked this conversation as resolved.
Show resolved Hide resolved