GSoC: Add repo links and licence information to projects

[vvolkl]

Having a link to an open source code repository should be mandatory

[sm-28601]

Having a link to an open source code repository should be mandatory

Hi @vvolkl , I’ve opened a PR for issue #1861.
Could you please review it ?

I’d also love to work on this issue also . Please assign it to me .

[gluonparticle]

Having a link to an open source code repository should be mandatory

Hi Valentin, I'd love to help with this. I've already worked on 2026 metadata (#1849 and #1850 )

Could you please clarify to help me understand the structure of your request and align me with your vision :-

1. The Rule Checker:- Create a rule-based framework which implements CI/CD checks for a new project.

2. Manual Cleanup:- Ensure all gsoc 2026 proposals have link to the repositories (As many of them don't qualify the criteria you suggest, it'll require manually adding links to all proposals lacking it.

3. Both 1 and 2. Or something else entirely? ;

[vvolkl]

I don't think we need any CI checks, it's really just about adding a git repository link and licence string to all of the .mds in https://github.com/HSF/hsf.github.io/blob/main/_gsocprojects/2026/ In principle the mentors should do this but I'm happy to accept PRs

[ritikyadav1333-gif]

Hi @vvolkl ,

My name is Ritik Kumar Yadav, I’m interested in working on this issue. I’ve reviewed the thread and the target directory, and I understand that the task is to add repository links and license information to the relevant .md files.

If assigned, I’ll ensure the updates are consistent across all project files and submit a clean PR.

Looking forward to contributing — please let me know if I can take this up.

[ritikyadav1333-gif]

Submitted a PR updating the ATLAS project as a reference implementation for adding repository and license metadata.

Happy to update the remaining 2026 project files once the format is confirmed.

[sm-28601]

Hi @vvolkl,

I’ve gone through the existing PRs and just want to confirm my understanding.

The goal is to update all files under _gsocprojects/2026/ by:

• Adding a specific repository link (not just a general organization link)
• Adding the correct license string corresponding to that repository

Before I start working on the remaining project files, I have a couple of clarifications:

• Should the repository and license be added as front-matter fields (e.g., repository: and license:), or as a visible section inside the markdown (e.g., ## Links)?
• When multiple repositories exist (for example, in large collaborations like ATLAS), should we link to a specific subproject repository?

Once confirmed, I’d be happy to update the remaining 2026 project files consistently.

[ritikyadav1333-gif]

Hi @vvolk,

Just a gentle follow-up on the PR for the ATLAS project. Please let me know if the format looks good or if any changes are needed.

If approved, I can proceed with updating the remaining 2026 project files in a consistent way.

Thank you!