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

Confirm mailing list openness and retention #11

Open
baentsch opened this issue Apr 4, 2024 · 3 comments
Open

Confirm mailing list openness and retention #11

baentsch opened this issue Apr 4, 2024 · 3 comments

Comments

@baentsch
Copy link
Member

baentsch commented Apr 4, 2024

LinuxFoundation is not willing to grant openness and perpetual availability to its mailing lists in general but may be willing to grant this to mailing lists pertaining to the OQS TSC.

So this issue is to suggest the TSC requests the LinuxFoundation powers that be to grant open access and perpetual availability to mailing lists pertaining to OQS TSC and to document this equally openly at registration time/by registration email reply.

The goal of the latter is to make possible future withdrawals by LF from such promise at least visible.

@baentsch
Copy link
Member Author

baentsch commented Apr 9, 2024

LinuxFoundation legal department weighed in here. So @hartm fyi, I'll create a PR in www to move this confirmation to a more prominently visible place talking about OQS mailing lists and thus close out this issue.

@baentsch
Copy link
Member Author

baentsch commented Jul 2, 2024

I now also no longer have permission to push to a branch on the www repository to close this issue. Why @dstebila @ryjones ?

@dstebila
Copy link
Member

dstebila commented Jul 2, 2024

I now also no longer have permission to push to a branch on the www repository to close this issue. Why @dstebila @ryjones ?

Looking at the permissions config file, it seems like only a few named individuals have write permissions here, not any teams. That being said, I'm not one of the named individuals here, and yet I still seem to have write access. So I have no idea what's going on with this config.

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

No branches or pull requests

2 participants