Gsoc 2026 update (#246)

* Add banner

* Update main GSoC page

* Update wording for 2026

* Update application template

* Add note about AI

* Update docs/source/get-involved/gsoc/2026/application_template.md

Co-authored-by: Alessandro Felder <alessandrofelder@users.noreply.github.com>

---------

Co-authored-by: Adam Tyson <adam@adamltyson.com>
Co-authored-by: Alessandro Felder <alessandrofelder@users.noreply.github.com>

Author: 3 people

docs/source/conf.py

@@ -184,6 +184,7 @@
     "analytics": {
         "google_analytics_id": "G-6260TGM7TY",
     },
+     "announcement": "Would you like a paid internship with the NIU this summer? We're taking part in <a href='https://neuroinformatics.dev/get-involved/gsoc/index.html'>Google Summer of Code</a>!",
 }
 
 html_sidebars = {

docs/source/get-involved/gsoc/2026/application_template.md

@@ -0,0 +1,102 @@
+# Application template
+
+::: {admonition} AI policy
+:class: warning
+Before submitting an application, please see our [AI policy](../../ai_policy). AI tools are great to help with spelling 
+and grammar, but in these applications we want to hear what you think. We will not accept any applications in which any 
+substantial chunk (i.e. whole sentences) are created with AI.
+:::
+
+
+Please use the following template to submit your application to the NIU GSoC 2026 program, and to discuss your proposal with the community.
+
+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.
+
+**If all sections are not fully completed, the application will not be considered!**
+
+N.B. If you would like this template in Markdown format, click "Show Source" on the right hand side.
+
+
+## Project title
+Follow the following format for the proposal title: `<Package Name>-<Project Name> (<Your-Name>)` when applying.
+
+E.g. "movement: support for Kalman filters (Jane Doe)".
+
+## Personal details
+Please include the following information:
+- **Full name** (include preferred name if desired)
+- **Email**
+- **GitHub username**
+- **Zulip username**
+- **Location & time-zone**
+- **Personal website / project portfolio** (optional)
+- **Code contribution**
+
+  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
+_Length: max 1 page_
+
+- **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?
+
+- **Implementation timeline**
+
+  Please include the following information:
+    1. A bullet point list with **minimal set of deliverables**
+    2. Additional **stretch goals** or "if time allows" deliverables (optional)
+    3. A detailed **weekly timeline**: when do you plan to do what?
+        - Please use a week as a minimal unit of time, and include any planned vacations or other commitments.
+        - This timeline could be formatted as a table.
+        - Remember to also include the number of hours per week you plan to work on the GSoC project.
+        - When estimating the required time for a task, keep in mind deliverables should include investigation/research, coding and documentation.
+        - The default schedule for GSoC is 12 weeks - see the [GSoC timeline](https://developers.google.com/open-source/gsoc/timeline) for precise dates.
+        - Also please specify any prep work you plan to do during the "Community bonding period".
+        - Usually week 1's deliverables already include some code. Week 6 marks the mid-term point, where usually more than half of the project should be completed. At the end of week 11 you may want to try to "freeze" the code and complete any remaining tests or documentation in weeks 11 and 12.
+
+- **Communication plan**
+
+  Please explain: how do you plan to communicate with your mentor? How often? (e.g., daily or weekly stand-ups, longer meetings..?) What communication channels will you use? (e.g., video calls, Zulip chat...?)
+
+## Personal statement
+
+_Length: max 0.75 page_
+
+- **Past experience.**
+
+  Please describe your past experience with programming, open source, research or any other experience you deem relevant for the project you are applying for. Any successful open source projects, published work or content of the like should definitely be highlighted.
+- **Motivation: why this project?**
+
+  Why are you interested in this specific project? What aspects of it motivate you to work on it? How does it link to your personal or professional interests? How do you envision its impact in the open source community?
+- **Match: why you?**
+
+  Why should we choose you for this project? What unique skills or experiences can you bring to the project and the community? Is there something you have worked on in the past that makes you particularly well-suited for this project?
+- **Availability**
+
+  Please state if you have any other plans for the work period (school work, another job, planned vacation)? If so, how do you plan to combine them with your GSoC work?
+
+## GSoC
+
+_Length: max 0.25 page_
+
+- **GSoC experience**
+
+  What do you expect from the program?
+
+- **Are you also applying to projects with other organisations in GSoC 2025?**
+
+  If so, which ones? What would be your preference in case of a tie?
+
+## Future contributions
+_Length: max 1 page_
+
+- **After GSoC**
+
+  How do you envision your contributions to the organisation continuing after GSoC? Please be realistic, including your other commitments. We do not expect everyone to start working full-time on open-source, but we want GSoC to help build our community long-term.
+
+- **Further ideas**
+
+  Other than your chosen project, what else could best improve your chosen repository, or the overall organisation? Please describe what you would do (if given the time and resources) to improve our tools. This should not be related to any existing issue/PR etc. We want to hear what you think, and to show you have understood the organisation.
+
+

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

@@ -12,6 +12,15 @@ For more details please see our [main GSoC page](../index). Please also see our
 Our GSoC ideas are based within specific, larger open source packages we develop. Some of these have specific project ideas associated with them. 
 Others do not yet have specific project ideas, but all on this list welcome ideas developed by GSoC participants. Please reach out to us via our [GSoc Zulip channel](https://neuroinformatics.zulipchat.com/#narrow/channel/487898-Google-Summer-of-Code) to discuss.
 
+::: {admonition} Other projects
+:class: note
+The list below are just project "ideas", we are very keen to hear about other potential projects from applicants. 
+In 2026 we are particularly interested in:
+- Making our software more maintainable and reducing technical debt.
+- Making our tools more accessible to scientists. We are keen to help practicing scientists make their first contributions to open source.
+
+If you have any ideas within these themes, please reach out via our [GSoc Zulip channel](https://neuroinformatics.zulipchat.com/#narrow/channel/487898-Google-Summer-of-Code).
+:::
 
 ## 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.

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

@@ -9,6 +9,8 @@ These tips are largely based on the [OpenAstronomy guidelines](https://openastro
 
     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.
 
+    Although we love to hear from you, please don't ask questions for the sake of "getting noticed". We're happy to help out, but we unfortunately cannot guide every potential applicant through the process.
+
 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.
@@ -61,7 +63,7 @@ These tips are largely based on the [OpenAstronomy guidelines](https://openastro
 
 ## Application template
 
-In our [GSoC repository](https://github.com/neuroinformatics-unit/gsoc) you will find our application template - please use it to structure your proposal.
+Please use our [application template](2026/application_template) to structure your proposal. Applications not following this template will not be considered.
 
 
 ## References

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

@@ -1,14 +1,17 @@
 # Google Summer of Code
 
-[Google Summer of Code](https://summerofcode.withgoogle.com/) (GSoC) is a global fully online program whose aim is to bring new developers into open source software. It is a great opportunity to gain experience in real-world software development while helping the open source community. Additionally, GSoC contributors receive a stipend from Google. 
+[Google Summer of Code](https://summerofcode.withgoogle.com/) (GSoC) is a global fully online program whose aim is to bring new developers into open source software. It is a great opportunity to gain experience in real-world software development while helping the open source community. Additionally, GSoC contributors receive a [stipend from Google](https://developers.google.com/open-source/gsoc/help/student-stipends). 
 
 Initially focused on university students, since 2022 the program has expanded to welcome students and all beginner contributors to open source who are 18 years and older to participate.
 
 The Neuroinformatics Unit (NIU) takes part in GSoC to offer paid experience working on open-source neuroscience and machine learning tools. The computational neuroanatomy project, [BrainGlobe](https://brainglobe.info/) is also included within the NIU for GSoC.
 
 ::: {admonition} GSoC 2026
 :class: note
-Our [2026 project list](2026/index) is now live.
+We are taking part in GSoC again in 2026. Our [2026 project ideas list](2026/index) is now live, but we also want to hear 
+project ideas from you! In 2026 we are particularly interested in:
+- Making our software more maintainable and reducing technical debt.
+- Making our tools more accessible to scientists. We are keen to help scientists who don't normally contribute to open-source get involved.
 :::
 
 ## How does GSoC work?