Sage Enhancement Proposal: Improved Public Key Cryptography Functionality

[Vincent Macri]

I have opened a thread in GitHub Discussions to ask for feedback on a
proposal to improve our public key cryptography facilities. I hope the
format of the proposal may also serve as an example for future Sage
proposals. If you have any feedback about the proposal itself, please
post it to the GitHub Discussions thread. If you have any feedback about
the format of the proposal, feel free to reply on this email thread.

https://github.com/sagemath/sage/discussions/41218

--
Vincent Macri (he/him)

[Vincent Delecroix]

Excellent initiative. Could we have a "SEP" github label?

> --
> You received this message because you are subscribed to the Google Groups "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/sage-devel/0ee1dc42-10b3-4577-87ef-8ee5076a5ac9%40ucalgary.ca.

[Vincent Macri]

On 2025-11-23 11:07 a.m., Vincent Delecroix wrote:

Excellent initiative. Could we have a "SEP" github label?

For SEPs themselves I think they should just all go in https://github.com/sagemath/sage/discussions/categories/ideas, so a label wouldn't be needed for SEPs themselves since they would have a dedicated place.

A generic "SEP" label for issues or PRs to implement SEPs might be a bit too broad to be useful if there are multiple SEPs being implemented at a time. I guess we could have a label for each SEP, but I think that enabling GitHub Projects on the repo instead would result in a smoother workflow for keeping track of the progress on specific SEPs. We could have a project for each SEP that is being worked on and add issues/PRs to it without an administrator needing to create new labels for each SEP (you need a higher GitHub permission level to manage labels than to manage projects).