GSoC 2026 - cve-bin-tool may not be participating

[terriko]

Quick heads up:

I am NOT going to be able to coordinate gsoc for cve-bin-tool this year -- there's too much work that needs doing while I'm going to be in the middle of an international move.

If you're a GSoC aspirant: right now I'd recommend you find another project to work on. I am not available to give you guidance on how to do this, please read "How Do I Choose a Project or Sub-org?" and our other getting started instructions.

If you're a mentor who's worked with me in previous years and want to take over the coordination part of thing, hit me up. There's probably 100+ hours of work that needs doing to get us ready, including:

1. Fixing CI so the build no longer reports failing and making sure nothing else blocks new users from getting code merged.
2. Cleaning up our current open pull requests so things are either merged or closed and it's clear which bugs are available to work on.
3. Going through the list of open bugs and finding ones that are suitable for beginners and marking them appropriately with tags and also with more detailed instructions for first-timers. Make especially sure that any bugs that need to be closed are closed, and any that have a PR in progress can be un-tagged as "good first issue" so people don't keep tripping on them.
4. Going through the list of open bugs and preparing a list of 1-3 project ideas for new features or other major-ish work that we'd like done.
5. Preparing a whole "project ideas" page that includes other instructions (you can probably re-use a lot of the text from previous years)
6. Making sure you have mentors who are interested and able to work with students for the duration of the program and getting them signed up with the Python Software Foundation and Google (won't happen until January)
7. Signing up as a project admin with the Python Software Foundation

Pinging @anthonyharrison and @mastersans as the two people I think most likely interested in taking in this role.

[alex-ter]

I'm not ready to sign up for the GSoC, but I'll be happy to help out with 1-3 on the list as a part of general project participation (and helping out with maintenance, as we discussed in the past).

[terriko]

@alex-ter always happy to have help! I can't grant any repo permissions right now (waiting on the openssf transfer to complete) but let me know if there's anything confusing that needs explanation from me specifically, i guess?

[alex-ter]

Sure, thank you. I'll probably start with just commenting on issues and PRs that could be closed or tagged differently, etc. I was planning to do that for a while, but was holding off to avoid additional noise during this transition period.

[joydeep049]

Hey @terriko

I'd also be interested in mentoring for GSoC if that's possible. Please let me know if there are any steps I would need to complete.