search

open-quantum-safe / liboqs

C library for prototyping and experimenting with quantum-resistant cryptography
https://openquantumsafe.org/
Other
1.92k stars 466 forks source link

docs: add PQCA Discord Server badge to README #1845

Closed anvega closed 4 months ago

anvega commented 4 months ago

Note: This does not add new features, affect input/output behavior, or alter the list of algorithms. No version bump or downstream project updates are required.

baentsch commented 4 months ago

Thanks for contributing @anvega! But just (again) for the record--I'm still not particularly happy about listing Discord prominently: Is there enough "care and attention" by OQS contributors and maintainers there? I for sure never will sign up to its t's and c's. Second, can we make sure GH discussions are self-contained/can be understood without also reading Discord? My main worry there is that they simply may delete content and posterity (just with GH access) won't be able to understand why some things happened within OQS.

Second thing, @anvega could you please tag such "non code" PRs with [skip ci] in the commit message? (Earth's) resources will be grateful.

SWilson4 commented 4 months ago

I'm also not sure about linking to Discord from the repo. My main concern is that it may funnel reports that really should be in GitHub issues or discussions to Discord, which is a more difficult platform for asynchronous triage and discussion (by design, it's built for live chat). I do attempt to monitor Discord, but messages can accumulate when you're offline, and there's no convenient dashboard to catch up on missed activity (unlike on GitHub, where I can easily view what I've missed, mark issues/discussions as read, etc).

I wouldn't object to linking to Discord in places which aren't directly tied to development (e.g., openquantumsafe.org).

anvega commented 4 months ago

Makes sense.

With GitHub is the primary communication platform, this could be clarified in the contributing guidelines, with Discord mentioned as a secondary, informal channel.

Might help others to be explicit with the project's communications strategy. This helps folks like me who land directly on the repo and seek help to know issues are the best way to get assistance.

I'll use [skip ci] for non-code PRs.