Move "python-library-fuzzers" repository under the Python GitHub organization?

Core Development
1

Hello! I’m actively working on fuzzing work related to the zipfile and tarfile modules and noticed that our fuzzer definitions and corpuses for standard library modules are currently under hugovk/python-library-fuzzers. @hugovk graciously picked up where the previous maintainer left off after deleting their repositories.

I wanted to propose moving this repository under the Python GitHub organization so that more folks can contribute and review the changes proposed to the repository. This would put the fuzzers/corpuses for libraries in line with what we have today for the CPython language and modules which currently live in python/cpython under _xxtestfuzz.

I recommend recreating the repository without using GitHub’s transfer mechanism, instead manually creating a new repository and pushing the full commit history avoid GitHub commit SHA resolution weirdness, since the intent is to run code in this repository in our CI. After this is completed I can submit pull requests to our OSS-Fuzz configuration to point to the new location.

cc @gpshead @hugovk @pablogsal @alex_Gaynor @ammaraskar

12 Likes
2

I support this.

After the original repo was deleted, I made my fork from another fork, so we have a copy just in case we need it in the future. The future is now!

I’m happy with whatever approach.

If we just want to detach it from the GitHub fork network, so it’s a standalone repo, there’s some Git commands we can follow to achieve this:

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/detaching-a-fork

6 Likes
3

I think this makes sense and it’s a good idea. Centralising these under a common umbrella will certainly help with discovery and hopefully will converge efforts :ok_hand:

8 Likes
4

Sounds reasonable!
Could you add a README first? It’s not clear how to get started with this repo.

If we just want to detach it from the GitHub fork network, so it’s a standalone repo, there’s some Git commands we can follow to achieve this:

Maybe ask the owner of the (randomly chosen?) “main” repo and transfer that, to keep the existing network? GitHub - henices/python-library-fuzzers

1 Like
5

Yes definitely, I was planning on adding information to the README including how to add new fuzzers and do local development. edit: I’ve created a README in this pull request.

1 Like
6

Okay, this discussion seems to be simmering down to a positive feeling about migrating the python-library-fuzzers repository to the org. What is the next step for this sort of request, I assume I can contact a GitHub admin to take the necessary actions?

1 Like
7

Before adding a new repository to the organization, open a discussion to seek consensus in the Committers Discourse category. Once people are satisfied with that, ask the Python steering council to grant permission.

Please open an issue at GitHub · Where software is built

1 Like
8

Thank you Hugo, I’ve created an issue as requested: Request to adopt `hugovk/python-libraries-fuzzers` to Python organization · Issue #318 · python/steering-council · GitHub

2 Likes
9

Thanks to Hugo for setting up the repository, now public: GitHub - python/library-fuzzers: Fuzzer definitions, seed corpora and dictionaries to fuzz-test the stdlib I created a pull request switching over the OSS-Fuzz configuration. Thank you everyone!

5 Likes