GSoC guidelines and application template edits (#121)

* Add DPS feedback

* Add links to repos in project lists

* Add Adam's feedback

* Fix link

* Support project proposals

* Add NIU wiki

* Clarify wiki procedure

Author: sfmig

docs/source/get-involved/gsoc/guidelines.md

@@ -7,13 +7,13 @@ These tips are largely based on the [OpenAstronomy guidelines](https://openastro
 
     Open source work is done and communicated in public - the idea here is to demonstrate that you can do this! Join our [Zulip](https://neuroinformatics.zulipchat.com/), or browse through our GitHub repositories - you can find a full list of the NIU repositories under the [NIU GitHub organisation](https://github.com/neuroinformatics-unit) and the [Brainglobe](https://github.com/brainglobe) one. Read, ask questions, get to know the people involved, and participate in discussions. 
 
-    Just introduce yourself, and feel free to can ask questions about specific projects, the development process, recommended readings or the community. 
+    Introduce yourself, and feel free to can ask questions about specific projects, the development process, recommended readings or the community. If you are not familiar with Zulip, have a look at this [quick guide](https://zulip.com/help/getting-started-with-zulip) first.
 
 2. **Become a user**
 
     A great way to get started in the community of our open-source tools is to experience them as a user. Try to install and use our tools, experiment with the code, and report any issues you find. This will help you understand the tools better and will give you a better idea of what you can contribute.
 
-    A good starting point as a user could be `movement`'s gallery of [examples](https://movement.neuroinformatics.dev/examples/index.html) or BrainGlobe's [tutorials](https://brainglobe.info/tutorials/index.html).
+    A good starting point as a user could be `movement`'s [gallery of examples](https://movement.neuroinformatics.dev/examples/index.html) or [BrainGlobe's tutorials](https://brainglobe.info/tutorials/index.html).
 
 3. **Get ready to be a developer**
 
@@ -27,12 +27,14 @@ These tips are largely based on the [OpenAstronomy guidelines](https://openastro
     - [Oh my git!](https://ohmygit.org/) an open-source game about Git.
     - [Julia Evan's How Git Works! zine](https://jvns.ca/blog/2024/04/25/new-zine--how-git-works-/)
     - the [NIU's software skills courses](https://software-skills.neuroinformatics.dev/courses/index.html)
+
+    We can help you with this if needed! Reach out in a relevant Zulip topic (or open one) if you have any questions, and someone from the community will be happy to help you.
 
 4. **Get started with open-source development**
 
     Check the GitHub issues for the projects you are interested in. Sometimes issues are labeled as "good first issue" or "help wanted". These are usually easier to solve and are a good way to get started with the project. Otherwise, have a look and see if there are any issues you can help with!
 
-    You will be expected to submit a pull request (ideally to one of the NIU projects) before you submit your application. It does not have to be accepted - the goal is to show that you know how git, GitHub, pull requests and code reviews work. This also allows mentors to evaluate your applications beyond a pdf, and based on a real code contribution. If you have previously contributed to an NIU or other open source project, you can point to those pull requests in your application too.
+    You will need to submit a pull request (ideally to one of the NIU projects) as part of your application. It does not have to be accepted - the goal is to show that you know how git, GitHub, pull requests and code reviews work. This also allows mentors to evaluate your application based on a real code contribution. If you have previously contributed to an NIU or other open source project, you can point to those pull requests in your application too.
 
     If you are new to open source software or would like a refresher, these are some nice resources to check:
 
@@ -41,12 +43,23 @@ These tips are largely based on the [OpenAstronomy guidelines](https://openastro
 
     Before contributing to a project, make sure you read through their contributing guidelines. These will give you an idea of the required steps, and what is expected of you. An example is `movement`'s [How to Contribute guide](https://movement.neuroinformatics.dev/community/contributing.html#target-contributing). The NIU also publishes some general [development guidelines](https://neuroinformatics.dev/get-involved/languages_frameworks.html).
 
+    You can check the issues from the tools involved in the GSoC projects in the links below:
+    - [`movement` issues](https://github.com/neuroinformatics-unit/movement/issues)
+    - [`ethology` issues](https://github.com/neuroinformatics-unit/ethology/issues)
+    - [`BrainGlobe cellfinder` issues](https://github.com/brainglobe/cellfinder/issues)
+    - [`BrainGlobe brainrender` issues](https://github.com/brainglobe/brainrender/issues)
+    - [`BrainGlobe atlasaip` issues](https://github.com/brainglobe/brainglobe-atlasapi/issues)
+    - [`BrainGlobe registration` issues](https://github.com/brainglobe/brainglobe-registration/issues)
+    - [`datashuttle` issues](https://github.com/neuroinformatics-unit/datashuttle/issues)
+
 
 5. **Prepare your application**
 
     Make sure you carefully read through the [GSoC guidelines](https://google.github.io/gsocguides//student/writing-a-proposal) (and these guidelines!) when preparing your application. 
 
-    Select one of the projects from our [project list](projects_2025/index) and prepare a plan on how to tackle it, and the time you will need to complete it. Use our [application template](#application-template) to structure your proposal and don't be shy to ask for feedback from the mentors or the community.
+    Select one of the projects from our [project list](projects_2025/index) and prepare a plan on how to tackle it, and the time you will need to complete it. Or if you have an idea that is not covered by the project list, feel free to pitch it to us. Use our [application template](#application-template) to structure your proposal and don't be shy to ask for feedback from the community. 
+    
+    To discuss your project proposal with the us, please create a new page in the [NIU GitHub wiki](https://github.com/neuroinformatics-unit/gsoc/wiki) with the project title prefixed with "GSoC 2025:" - we will discuss and polish your idea there. Please note that project proposals that are not previously discussed in the wiki will not be considered. 
 
     Include specific examples in your application to support your skills - these will help reviewers build a better picture of you. These could be things like "Qualified in final round of XXXX" or "Participated in XXXX hackathon".
 
@@ -55,7 +68,7 @@ These tips are largely based on the [OpenAstronomy guidelines](https://openastro
 
     Remember to submit your application before [the deadline](https://developers.google.com/open-source/gsoc/timeline#april_8_-_1800_utc)! 
 
-    Please do not send any applications directly to the NIU team - all applications must go through [Google's application system](https://summerofcode.withgoogle.com/)
+    Please do not send any applications directly to the NIU team, they won't be considered - all applications must go through [Google's application system](https://summerofcode.withgoogle.com/)
 
 
 ## Application template
@@ -64,6 +77,9 @@ Please use the following template to submit your application to the NIU GSoC 202
 
 The more closely you follow this template, the easier it will be for us to review your application! Please include clear headings for all the different sections.
 
+### Project title to use for the GSoC application
+Please clearly include in the title the tool the project refers to, and the title of the project you are applying for. E.g. "movement: support for Kalman filters".
+
 ### Personal details
 Please include the following information:
 - **Full name** (include preferred name if desired)
@@ -74,13 +90,12 @@ Please include the following information:
 - **Personal website / project portfolio** (optional)
 - **Code contribution**
 
-    Please link a pull request or code sample, ideally submitted to your chosen project. It must be publicly visible and represent your own work, although you may have help from other developers in the community to further improve it. You can link more than one contribution or pull request if desired.
+    Please link a pull request, ideally submitted to your chosen project or one of the NIU tools. Applications without a code contribution won't be considered. It must be publicly visible and represent your own work, although you may have help from other developers in the community to further improve it. It must be meaningful code contribution (i.e. not just fixing a minor spelling mistake). While AI tools (such as Copilot etc) can be a very useful, contributions mostly created by AI are unlikely to be useful, and will not be accepted. You can link more than one pull request if desired.
 
 ### Project proposal 
 Extension: <u> max 1 page </u> 
-
 - **Title.**
-    Please clearly include the title of the project you are applying for and the tool it refers to. E.g. "movement: support for Kalman filters".
+    Please use the same title as in the GSoC application.
 
 - **Synopsis.**
     Briefly explain: what is the project about? Why is it important? What are the goals? What are the deliverables? How would the open source community benefit from this project?

docs/source/get-involved/gsoc/index.md

@@ -65,7 +65,7 @@ You may also want to checkout other useful application guides, such as:
 
 all of which we are closely following. Applicants are given about 2 weeks to complete their applications. For further details see the [GSoC Contributor Guide](https://google.github.io/gsocguides/student/writing-a-proposal).
 
-If you are interested in any of the NIU projects on offer, feel free to get in touch with us via [Zulip](https://neuroinformatics.zulipchat.com/) with any questions. Potential GSoC contributors are encouraged to get in touch with participating organizations as soon as the list of accepted organizations is published (this year, on the [27th February 2025](https://developers.google.com/open-source/gsoc/timeline#february_27_-_1800_utc)). 
+If you are interested in any of the NIU projects on offer, feel free to get in touch on the relevant project channel via [Zulip](https://neuroinformatics.zulipchat.com/) with any questions. Please reach out in public channels, rather than via DMs or personal conversations - communicating in the open is a big part of open source! However, if you have any concerns you wish to discuss privately (such as accessibility), please contact one of the organisation admins.
 
 For clarity, please always use your full name when getting a [Zulip](https://neuroinformatics.zulipchat.com/) account, when registering for the program, and when submitting your project plan. 
 

docs/source/get-involved/gsoc/projects_2025/brainglobe.md

@@ -1,7 +1,7 @@
 # GSoC NIU Projects 2025: BrainGlobe
 
 [BrainGlobe](https://brainglobe.info) is a community-driven suite of open-source Python tools. The BrainGlobe tools are widely used to process, analyse and visualise images of brains (and other related data) in neuroscientific research.
-If you are interested in any of these projects, [get in touch](https://brainglobe.info/contact.html)! Feel free to open a new topic on [Zulip](https://brainglobe.zulipchat.com/) and tag the potential mentors.
+If you are interested in any of these projects, [get in touch](https://brainglobe.info/contact.html)! Feel free to open a new topic on [Zulip](https://brainglobe.zulipchat.com/) and ask the community.
 
 Our working language is English, but our mentors for these projects also speak Italian, French, and German.
 

docs/source/get-involved/gsoc/projects_2025/datashuttle.md

@@ -1,6 +1,7 @@
 # GSoC NIU Projects 2025: `datashuttle`
 
-If you are interested in any of these projects, [get in touch](https://datashuttle.neuroinformatics.dev/pages/community/index.html)! Feel free to open a new topic on [Zulip](https://neuroinformatics.zulipchat.com/#narrow/channel/405999-DataShuttle) and tag the potential mentors.
+If you are interested in any of these [datashuttle](https://github.com/neuroinformatics-unit/datashuttle) projects, [get in touch](https://datashuttle.neuroinformatics.dev/pages/community/index.html)! Feel free to open a new topic on [Zulip](https://neuroinformatics.zulipchat.com/#narrow/channel/405999-DataShuttle) and ask the community.
+
 Our working language is English.
 
 

docs/source/get-involved/gsoc/projects_2025/ethology.md

@@ -1,6 +1,6 @@
 # GSoC NIU Projects 2025: `ethology`
 
-If you are interested in any of these projects, get in touch! Feel free to open a new topic on [Zulip](https://neuroinformatics.zulipchat.com/#narrow/channel/483869-Ethology) and tag the potential mentors.
+If you are interested in any of these [ethology](https://github.com/neuroinformatics-unit/ethology) projects, get in touch! Feel free to open a new topic on [Zulip](https://neuroinformatics.zulipchat.com/#narrow/channel/483869-Ethology) and ask the community.
 
 Our working language is English, but our mentors for these projects also speak Spanish.
 

docs/source/get-involved/gsoc/projects_2025/movement.md

@@ -1,6 +1,6 @@
 # GSoC NIU Projects 2025: `movement`
 
-If you are interested in any of these projects, [get in touch](https://movement.neuroinformatics.dev/community/index.html)! Feel free to open a new topic on [Zulip](https://neuroinformatics.zulipchat.com/#narrow/stream/406001-Movement) and tag the potential mentors.
+If you are interested in any of these [movement](https://github.com/neuroinformatics-unit/movement) projects, [get in touch](https://movement.neuroinformatics.dev/community/index.html)! Feel free to open a new topic on [Zulip](https://neuroinformatics.zulipchat.com/#narrow/stream/406001-Movement) and ask the community.
 
 Our working language is English, but our mentors for these projects also speak Spanish.