-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
fix: udpate GSOC page #532
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly grammarly suggestion
I don't think breaking space impacts the layout. To simplify Github suggestion process, I tend to always break space at the end of a sentence such that 1 sentence = 1 line and so reviews can add suggestions at the sentence level
@@ -1,6 +1,6 @@ | |||
<!-- no side column --> | |||
|
|||
<h1>Open Food Facts - Google Summer of Code (GSOC) 2023</h1> | |||
<h1>Open Food Facts - Google Summer of Code (GSOC)</h1> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<h1>Open Food Facts - Google Summer of Code (GSOC)</h1> | |
<h1>Open Food Facts - Google Summer of Code (GSOC) 2024</h1> |
Maybe it's a good practice to make sure the document is updated each year, to appapt to GSoC rule modification
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huuum, I was more on the verge of avoiding this page to decay ;-)
Those are most best practice that we decided.
Co-authored-by: Alexandre Fauquette <[email protected]>
Thanks a lot @alexfauquette 🙌 |
GSoC is coming !