- Initial onboarding of 4 MLKEM implementation repositories
- 14 contributors
- Getting discussions going on the project
These are the people added to the org (github ids) as maintainers/contributors to the projects below
- mkannwischer
- planetf1
- dstebila
- rpls
- MQuaresma
- ajbozarth
- cryptojedi
- franziskuskiefer
- jschanck
- karthikbhargavan
- mbbarbosa
- potsrevennil
- tfaoliveira
- ashman-p
Aided by others in discussion including Hart, Ry, Max.
| repository | activity during hackathon |
|---|---|
| tsc | Record requests for new repo/teams/access |
| mlkem-c-embedded | Created repo and teams Code added - Based on pqm4 repo |
| mlkem-c-generic | Created repo and teams Awaiting code |
| mklkem-libjade | Created repo and teams Awaiting code (assembly) |
| mlkem-rust-libcrux | Created repo and teams Awaiting code |
| mlkem-c-aarch64 | Created repo and teams after hackathon |
| documentation | mkdocs-material https://docs.pqcodepackage.org |
| template-code | Standard files README, CODEOWNERS scorecard action |
| pq-code-package-hackathon | mini site with links https://hackathon.pqcodepackage.org |
- Licensing. Aiming for Apache 2.0 (code) & CC-BY-4.0 (docs). some followups
- Test vectors being investigated - license unknowns (Norm Ashley)
- code flow ?upstream -> pqcp -> liboqs. Pipelines/strategy
- need to have commonality across sub-projects. Swap in/out algorithms. Documentation describing characteristics of implementation
- What is a package?
- artifact Distribution to repositories (->github)
- github practices - merge/rebase/squash, versioning, forks
- Managing access control groups was redious. post session adopted tooling to help (defined in yaml)
- TSC formation
- continued onboarding & addressing issues
- another hackathon?