From 357ae33f6cb7399e4d46d7ffd33a67a683d3f5ca Mon Sep 17 00:00:00 2001 From: hegner Date: Mon, 29 Jan 2024 13:11:51 +0100 Subject: [PATCH] Update students-guideline.md --- gsoc/students-guideline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gsoc/students-guideline.md b/gsoc/students-guideline.md index a86d49ad5..701b3edd5 100644 --- a/gsoc/students-guideline.md +++ b/gsoc/students-guideline.md @@ -36,7 +36,7 @@ Get started checking out the [Google Summer of Code Guides for students](https:/ 5. You will have to write a proposal that must contain: * A detailed plan of work with a timeline spanning over **90 or 175 or 375 hours**, which is the GSoC coding period duration this year. Note that your availability for working on the project has to be clearly stated (agreed upon with your mentors) and represents an engagement on your side. Breaking it during the coding period without prior notice and mentor's agreement represents a reason for being failed. * Well defined tasks and their objectives, with a list of deliverables upon which the success of the project will be determined. - * Between **Mar 18 - Mar 26** you will have the possibility to share your proposal draft with the project mentors to get improvement suggestions, before making your GSoC application due on `Apr 2`. + * Between **Mar 18 - Mar 26** you will have the possibility to share your proposal draft with the project mentors to get improvement suggestions, before making your GSoC application due on **Apr 2**.

6. Your proposal will be evaluated and ranked by your mentors, who give their feedback to the HSF Org Admins. If a project has eligible candidates, it will be considered for the request of slots made to GSoC, due on **Apr 20**. Note that the result of this Phase 2 selection process cannot be made available before the official announcement by Google of the successful student projects, on **May 1**.