Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move cuPQC ML-KEM upstream away from personal repo #2053

Open
praveksharma opened this issue Jan 24, 2025 · 1 comment
Open

Move cuPQC ML-KEM upstream away from personal repo #2053

praveksharma opened this issue Jan 24, 2025 · 1 comment
Assignees

Comments

@praveksharma
Copy link
Member

The cuPQC ML-KEM upstream added by #2044 resides in a personal GitHub repo. Either move this upstream to a Nvidia repo or update copy_from_upstream.py to accomodate a new class of local upstream.

@baentsch
Copy link
Member

move this upstream to a Nvidia repo

That's my clear preference: It makes clear whose code this is and who has the responsibility (and capability) to update the code with future updates to the NVIDIA library or any potential breakages in cuPQC becoming visible only in liboqs or downstream.

or update copy_from_upstream.py to accomodate a new class of local upstream.

What do you understand by "local upstream"? Either something is external (copied from a site where there is support and maintenance) or there is code internal to liboqs (i.e., maintained by the OQS team). "local upstream" thus sounds like something with no support/maintenance responsibility: Can you please clarify @praveksharma ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

2 participants