Writing-a-GSoC-proposal-for-CDLI.md

@@ -11,8 +11,28 @@ After joining our slack, please use https://gitlab.com/cdli/framework/-/blob/pho
 
 ## 
 ## 
-## Timeline
-Include a detailed timeline that shows what you intend to work on week by week. If you have examinations or family trips planned, insert them there too to show that you have thought of the practical aspects of your planning. This plan can be revised weekly during the project but it is a good way to organize your ideas and evaluate the time required for different tasks. Don't forget to factor in the writing of documentation, testing, and reworking your code if there is any changes to be made based on peer evaluation (when merging your work). 
+## Before writing your proposal
+Please go read the rules of the program before starting to write your proposal https://summerofcode.withgoogle.com/rules 
+## 
+## 
+## Writing your proposal
+You are free to write the proposal the way you wish, but include the information necessary for us to be able to evaluate if:
+- You understand the project at hand
+- You have the required skills or experience to take on this project
+- You can foresee how you will address the major challenges of the project
+- You seem like you could be successful in this project
+
+### Identity
+We do not need to know your age or any background information that is personal. Please avoid giving personal information, it is not required to evaluate your profile. However, we do need to be able to identify you from other people. 
+
+### Project
+Give a title and short description of your project. Do not copy and paste the content of the project idea page, write the project description in your own words. Chose a title that reflects your take on the project. 
+
+### Education and experience
+Tell us about your degrees and your past experience, remunerated, voluntary and as hobby. You don't need to include a full resume, tell us about experiences you think are relevant to your suitability to succeed in the chosen project. 
+
+### Timeline
+Include a detailed timeline that shows what you intend to work on week by week. If you have examinations or family trips planned, insert them there too to show that you have thought of the practical aspects of your planning. This plan can be revised weekly during the project but it is a good way to organize your ideas and evaluate the time required for different tasks. Don't forget to factor in the writing of documentation, testing, and reworking your code if there are any changes to be made based on peer evaluation (when merging your work). 
 
 ## Proposal examples
 Feel free to look at proposals that were submitted in the past: https://github.com/cdli-gh/Framework/tree/master/Proposal
\ No newline at end of file