-
Notifications
You must be signed in to change notification settings - Fork 41
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
GSoC 2023 blog post draft #268
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.
Please look at the highlighted points during review. Thanks.
_posts/2023-02-22-gsoc2023.md
Outdated
development environment or how to contribute. | ||
|
||
|
||
— MDAnalysis GSoC mentors |
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.
Should we add all our names here (as in previous years) or generically (and perhaps add @MDAnalysis/gsoc-mentors
?)
Our experience shows that having the listed skills increases the | ||
chances that a project will be completed successfully, so we use them | ||
as part of our decision criteria in choosing GSoC contributors. |
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.
I changed this paragraph, in previous years we said these skills were optional and we were happy with people wanting to learn. @RMeli ?
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.
I think this is very well phrased. Makes it clear what we look for in candidates without discouraging potential applicants.
Introduce yourself on the [mailing list]. Tell us your github handle, what you plan to work | ||
on during the summer or what you have already done with MDAnalysis. | ||
|
||
### Close an issue of MDAnalysis |
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.
Do we need to be more specific here?
Need to check that blog post and FAQ are consistent.
Co-authored-by: Rocco Meli <[email protected]>
We have an active PR open for SASA. MDAnalysis/mdanalysis#4025
…ub.io into GSOC2023-blog
- fix project numbering (now same as in https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2023-Project-Ideas) - fix broken link constructs to GSoC list - add final remarks subheading for better showing difference between requirements and comments - add Discord as contact to last paragraph - close with a friendly sign off - use GitHub and Discord team handles in signature
Please have a quick check so that we can post this soon. "LGTM" reviews are fine, this means some else except I and @RMeli read it. For "changes requested" please be specific or make the changes yourself. |
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.
I updated the table of mentors here and in the wiki to remove those who are not available to formally mentor this year. Otherwise LGTM!
Co-authored-by: Lily Wang <[email protected]>
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.
LGTM
I'm probably going to be involved with some of these projects if they go ahead, but yeah I'd prefer stay as an admin on paper, thanks for remembering @lilyminium .
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.
LGTM
Ready to merge. |
Have a blog post lined up in case MDAnalysis is announced as a GSOC 2023 org on 2023-02-22.