Difference between revisions of "Proposal Template"

From Ελεύθερο Λογισμικό / Λογισμικό ανοιχτού κώδικα
Jump to navigation Jump to search
m
m
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
# Proposal Template:
+
== Proposal Template ==
 +
 
 +
'''A good proposal is structured, complete and backed by your code contributions''' ;-). We want you to be honest and realistic while writing your proposal.  You should also see [https://google.github.io/gsocguides/student/writing-a-proposal Google's guide to Writing a Proposal].
  
'''A good proposal is structured, complete and backed by your code contributions''' ;-). We want you to be honest and realistic while writing your proposal.  You should also see [Google's guide to Writing a Proposal](https://google.github.io/gsocguides/student/writing-a-proposal)
 
  
 
'''It's good to have a well spaced timeline with doable goals for each week and buffers for each task.''' If you end up not being able to complete what you proposed, then we might consider failing your project.
 
'''It's good to have a well spaced timeline with doable goals for each week and buffers for each task.''' If you end up not being able to complete what you proposed, then we might consider failing your project.
Line 12: Line 13:
  
 
---------------
 
---------------
## Basic Details
+
==== Basic Details ====
 
  - Full Name
 
  - Full Name
 
  - Email and GitHub Username
 
  - Email and GitHub Username
Line 18: Line 19:
 
  - Your first language
 
  - Your first language
 
  - Location and Timezone
 
  - Location and Timezone
  - Share links, if any, of your previous work on open source projects ?<br>
+
  - Share links, if any, of your '''previous work on open source projects''' ?<br>
  
 
+
==== Your Motivation ====
## Your Motivation
 
 
  - What is your motivation to take part in Google Summer of Code ?
 
  - What is your motivation to take part in Google Summer of Code ?
 
  - Why did you choose Sugar Labs ?
 
  - Why did you choose Sugar Labs ?
Line 28: Line 28:
  
  
## Project Details
+
==== Project Details ====
 
  - What are you making ?  
 
  - What are you making ?  
 
  - How will it impact Open Technologies Alliance(GFOSS) ?
 
  - How will it impact Open Technologies Alliance(GFOSS) ?
 
  - What technologies (programming languages, etc.) will you be using ?
 
  - What technologies (programming languages, etc.) will you be using ?
  
## Timeline:
+
==== Timeline: ====
  - Break down the entire projects into chunks and tell us what will you work on each week.<br>
+
  - Break down the entire projects into chunks and tell us what will you work on each week.
  As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.
+
- As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan  
 +
at the beginning so you have an idea of where you're headed.
 
  - If you will be off-the-grid for a few days, then mention those in the timeline.
 
  - If you will be off-the-grid for a few days, then mention those in the timeline.
 
  - GSoC has three evaluations, once after every 30 days. Highlight the work you plan to complete before each evaluation.
 
  - GSoC has three evaluations, once after every 30 days. Highlight the work you plan to complete before each evaluation.
  - Also discuss your plans after the GSOC period ends. Do you plan to continue working on the project after GSOC ends ?
+
  - '''Also discuss your plans after the GSOC period ends'''. Do you plan to continue working on the project after GSOC ends?
 
  - Mention how much time will you spend each week working on your project
 
  - Mention how much time will you spend each week working on your project
  
## Motivation:
+
==== Motivation: ====
  - Convince us that you will be a good fit for this project, by sharing links to your contribution to GFOSS Projects.
+
  - '''Convince us that you will be a good fit''' for the GFOSS project you have selected, by sharing links from [https://ellak.gr/wiki/index.php?title=Google_Summer_of_Code_2019_proposed_ideas GFOSS Projects].
  - If your project is on an idea you proposed, convince us that the idea is useful to GFOSS Projects.
+
  - If your project is on an idea you proposed, convince us that the idea is useful to '''[https://gfoss.eu/ GFOSS]'''.
 +
 
 +
[[Κατηγορία:GSOC]] [[Κατηγορία:GSOC2019]]

Latest revision as of 16:21, 12 March 2019

Proposal Template[edit | edit source]

A good proposal is structured, complete and backed by your code contributions ;-). We want you to be honest and realistic while writing your proposal. You should also see Google's guide to Writing a Proposal.


It's good to have a well spaced timeline with doable goals for each week and buffers for each task. If you end up not being able to complete what you proposed, then we might consider failing your project.


Hofstadter's Law: It takes longer than you expect, even when you take into account Hofstadter's Law.


Finish writing your proposal early so that you can get it reviewed by your mentors and the community, before the deadline. They can give you valuable suggestions on your timeline and project details.


Basic Details[edit | edit source]

- Full Name
- Email and GitHub Username
- IRC nickname on #sugar
- Your first language
- Location and Timezone
- Share links, if any, of your previous work on open source projects ?

Your Motivation[edit | edit source]

- What is your motivation to take part in Google Summer of Code ?
- Why did you choose Sugar Labs ?
- Why do you want to work on this particular project ?
- What are your expectations from us during and after successful completion of the program ?


Project Details[edit | edit source]

- What are you making ? 
- How will it impact Open Technologies Alliance(GFOSS) ?
- What technologies (programming languages, etc.) will you be using ?

Timeline:[edit | edit source]

- Break down the entire projects into chunks and tell us what will you work on each week.
- As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan 

at the beginning so you have an idea of where you're headed.

- If you will be off-the-grid for a few days, then mention those in the timeline.
- GSoC has three evaluations, once after every 30 days. Highlight the work you plan to complete before each evaluation.
- Also discuss your plans after the GSOC period ends. Do you plan to continue working on the project after GSOC ends?
- Mention how much time will you spend each week working on your project

Motivation:[edit | edit source]

- Convince us that you will be a good fit for the GFOSS project you have selected, by sharing links from GFOSS Projects.
- If your project is on an idea you proposed, convince us that the idea is useful to GFOSS.