update faq for 90 hours projects

freifunk · Feb 29, 2024 · b1017a4 · b1017a4
1 parent db76a67
commit b1017a4
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/_faq/003_application_template.md b/_faq/003_application_template.md
@@ -41,7 +41,7 @@ Your GSoC Project
     * Description of software tests and test coverage
     * Performance prediction and proposal for the evaluation
  * Project Details - more detailed description
- * Project Size - choose to spend 175 hours or 350 hours.
+ * Project Size - choose to spend 90 hours, 175 hours or 350 hours.
  * Project Schedule - provide a rough timetable with milestones for every 2 weeks
  * Availability - How do you plan to spend the designated work hours during the summer? Do you choose the standard
 

diff --git a/_faq/004_how_to_write_a_proposal.md b/_faq/004_how_to_write_a_proposal.md
@@ -9,5 +9,5 @@ We have some notes you should keep in mind for your proposal:
 * Get in touch with the mentors mentioned in this idea to get into this topic and get answers to your questions.
 * Define - maybe together with the mentor - some measurable milestones, so you can design a rough timetable.
 * Refine and break down your milestones (maybe into stories), also together with the mentor.
-* Try to estimate what stories you can work on within the GSoC period. Please keep in mind that we have 2 kinds of projects: full-time with 350 hours and half-time with 175 hours over 10 weeks.
+* Try to estimate what stories you can work on within the GSoC period. Please keep in mind that we have 3 kinds of projects: large with 350 hours, medium with 175 hours andi small with 90 hours over 10 weeks.
 * Use our application template to introduce yourself and describe your project. The resulting document you should upload to the Google Summer of Code program website.