GSoC 2023 blog post draft

_config.yml

@@ -70,6 +70,9 @@ mailinglists:
   developer: 
     name:         developer
     url:          https://groups.google.com/group/mdnalysis-devel
+  gsoc:
+    name:         MDAnalysis GSoC list
+    url:          https://groups.google.com/a/mdanalysis.org/g/gsoc
 twitter:
   name:           mdanalysis
   url:            https://twitter.com/mdanalysis

_posts/2023-02-22-gsoc2023.md

@@ -0,0 +1,148 @@
+---
+layout: post
+title: Google Summer of Code 2023
+---
+
+<p>
+<img
+src="https://developers.google.com/open-source/gsoc/resources/downloads/GSoC-Vertical.svg"
+title="Google Summer of Code 2023" alt="Google Summer of Code with
+MDAnalysis 2023"
+style="float: right; height: 10em; " />
+</p>
+
+MDAnalysis has been accepted as an [organization][org] for [Google Summer of
+Code 2023][gsoc]! If you are interested in working with us this summer and you
+are new to open source, please read the advice and links below and write to us
+on the [GSoC with MDAnalysis mailing list][mailing list].
+
+We are looking forward to all applications from *any new and beginner
+open source contributors over 18 years old* or *students*. Projects
+are scoped as either 175-hour (medium) or 350-hour (long) size. The
+duration can be extended from the standard 12 weeks to 22 weeks.
+
+The application window **deadline** is **April 4, 2023 - 18:00 UTC**.
+As part of the application process you must familiarize
+yourself with [Google Summer of Code 2023][gsoc].
+
+If you are interested in working with us please read on and contact us
+on our [GSoC with MDAnalysis mailing list][mailing list].  Apply as
+soon as possible at
+[https://summerofcode.withgoogle.com](https://summerofcode.withgoogle.com);
+the application window opens on March 20, 2023 but potential GSoC
+Contributors are expected to familiarize themselves with application
+requirements and mentoring organizations as soon as possible. It's
+also never too early to discuss application ideas with us!
+
+## Project Ideas
+
+If you have your own idea about a potential project we'd love to work with you
+to develop this idea; please write to us on the [mailing list][]
+to discuss it there.
+
+We also have listed several [possible projects][ideas] for you to work on. Our
+initial list of ideas (see summaries in the table below) contains various
+projects of different scope and with different skill requirements. However,
+check the [ideas][] page — we might add more ideas after the posting date of
+this post.
+
+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.
+
+
+
+| project | name                                                                                                                                                      | difficulty | project size | description                                                                                    | skills                      | mentors                                |
+|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------|------------------------------------------------------------------------------------------------|-----------------------------|----------------------------------------|
+| 1       | [Generalise Groups]({{ site.github.wiki }}/GSoC-2023-Project-Ideas#project-1-bead-and-ring-groups)                                         | hard     | 350 hours   | Generalise concept of groups                                                                   | Python, NetworkX, Molecular modelling                  | @lilyminium, @fiona-naughton, @richardjgowers, @IAlibay, @micaela-matta, @ojeda-e, @yuxuanzhuang, @RMeli |
+| 2       | [Extend MDAnalysis Interoperability]({{ site.github.wiki }}/GSoC-2023-Project-Ideas#project-2-extend-interoperability)                  | medium     | 350 hours   | Extend converters module to other relevant packages                                            | Python, Molecular Modelling                      | @lilyminium, @IAlibay, @fiona-naughton, @hmacdope, @yuxuanzhuang, @RMeli|
+| 3       | [Benchmarking and performance optimization]({{ site.github.wiki }}/GSoC-2023-Project-Ideas#project-3-benchmarking-and-performance-optimization)                  | medium/hard     | 175 hours   |  write benchmarks for automated performance analysis and address performance bottlenecks | Python, Molecular Modelling                      | @hmacdope, @orbeckst, @ojeda-e, @RMeli |
+| 4       | [Transport property calculations]({{ site.github.wiki }}/GSoC-2023-Project-Ideas#project-4-transport-property-calculations) | medium     | 350 hours   |  write analysis code to calculate physical transport properties | Python, Physics/Mathematics      | @orionarcher, @hmacdope |
+| 5       | [Implementation of parallel analysis framework]({{ site.github.wiki }}/GSoC-2023-Project-Ideas#project-5-implementation-of-parallel-analysis-in-mdanalysis) | hard     | 350 hours   |  implement parallel framework in MDAnalysis| Python, Parallel Programming, Molecular Modelling      | @yuxuanzhuang, @orbeckst, @RMeli |
+
+
+
+## Information for prospective GSoC Contributors
+
+You must meet our [own requirements] if you want to be a GSoC
+Contributor with MDAnalysis this year (read all the docs behind these
+links!). You must also meet the [eligibility criteria]. Our [GSoC
+FAQ][] collects common questions from applicants.
+
+The MDAnalysis community values diversity and is committed to providing a
+productive, harassment-free environment to every member. Our [Code of Conduct]
+explains the values that we as a community uphold. *Every member (and every
+GSoC Contributor) agrees to follow the [Code of Conduct]*.
+
+As a start to get familiar with MDAnalysis and open source development you
+should follow these steps:
+
+### Watch the MDAnalysis Trailer
+
+The [MDAnalysis Trailer](https://www.youtube.com/watch?v=uMAfvwFkD3o) on YouTube
+is a one minute introduction to MDAnalysis.
+
+<div class="js-video">
+	<iframe src="https://www.youtube.com/embed/uMAfvwFkD3o" frameborder="0"
+	allowfullscreen class="video"></iframe>
+</div>
+
+
+### Complete the Quick Start Guide
+
+We have a [Quick Start Guide] explaining the basics of MDAnalysis. You
+should go through it at least once to understand how MDAnalysis is
+used. Continue reading the [User Guide] to learn more.
+
+### Introduce yourself to us
+
+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
+
+You must have *at least one commit in the development branch of MDAnalysis* in
+order to be eligible, i.e., you must demonstrate that you have been seriously
+engaged with the MDAnalysis project.  We have a list of [easy bugs][] and
+suggested [GSOC Starter issues][GSOC Starter] to work on in our issue tracker
+on GitHub. *We only accept one [GSOC Starter issue][GSOC Starter] per
+applicant* so that everybody gets a chance. If you want to dive deeper, we
+encourage you to tackle some of the other issues in our issue tracker.
+
+We also appreciate contributions which add more tests or update/improve our documentation.
+
+## Final remarks
+
+We recommend you start your application by working on an issue. It will give
+you a better understanding of MDAnalysis as a project and improve the quality
+of your application.
+
+To start developing for MDAnalysis have a look at our guide on
+[contributing to MDAnalysis][dev-guide] and write to us on the [GSoC
+with MDAnalysis mailing list][mailing list] if you have more questions
+about setting up a development environment or how to contribute. We
+are also happy to chat on our [{{ site.discord.name }} Discord
+server][discord] in the `#gsoc` channel (join with the public
+[invitation link]({{ site.baseurl }}/#participating)).
+
+We look forward to working with you in GSoC 2023!
+
+
+— MDAnalysis GSoC mentors (GitHub [@MDAnalysis/gsoc-mentors], Discord `@gsoc-mentor`)
+
+
+[org]: https://summerofcode.withgoogle.com/programs/2023/organizations/mdanalysis
+[Code of Conduct]: {{ site.baseurl }}/pages/conduct/
+[eligibility criteria]: https://developers.google.com/open-source/gsoc/faq#what_are_the_eligibility_requirements_for_participation
+[own requirements]: {{ site.github.wiki }}/Google-Summer-Of-Code#our-expectations-from-gsoc-contributors
+[easy bugs]: https://github.com/MDAnalysis/mdanalysis/issues?q=is%3Aopen+is%3Aissue+label%3ADifficulty-easy
+[GSOC Starter]: https://github.com/MDAnalysis/mdanalysis/issues?q=is%3Aopen+is%3Aissue+label%3A%22GSOC+Starter%22
+[Quick Start Guide]: https://userguide.mdanalysis.org/stable/quickstart.html
+[User Guide]: https://userguide.mdanalysis.org/
+[ideas]: {{ site.github.wiki }}/GSoC-2023-Project-Ideas
+[gsoc]: https://summerofcode.withgoogle.com/
+[dev-guide]: https://userguide.mdanalysis.org/stable/contributing.html
+[mailing list]: {{ site.mailinglists.gsoc.url }}
+[GSoC FAQ]: {{ site.github.wiki }}/GSoC-FAQ
+[@MDAnalysis/gsoc-mentors]: https://github.com/orgs/MDAnalysis/teams/gsoc-mentors
+[discord]: {{ site.discord.url }}