search

open-quantum-safe / www

https://openquantumsafe.org/
1 stars 0 forks source link

Change integrations text #215

Open baentsch opened 3 weeks ago

baentsch commented 3 weeks ago

https://openquantumsafe.org/applications/tls.html#demo-integrations is pretty much dated as the interest in providing ready-made docker images to ease the user "journey to PQC" does not really seem to be wanted and lacks support by the community.

This issue thus is to suggest replacing the section above with a one-liner reference to the oqs-demos project which then can provide different levels of integration "support", from simple blogs posts, to more fully operational integration code samples, to working Dockerfiles, and for the more active integrations, some fully supported docker images.

Not exactly a revitalization but a more correct external representation of the real state of reduced support in this area such as to fix/no longer create incorrect perceptions by the "unwary" OQS user community reading the web site.

FYI @maximilien @dstebila @hartm as this proposal somewhat goes in the opposite direction to https://github.com/PQCA/TAC/issues/34.

dstebila commented 2 weeks ago

I'm all for having the text on openquantumsafe.org reflect reality.

My own preference is for it to not just be one-line pointers to Github. I realize that's more effort to keep up to date, but I believe there's value in having the information presented in a second and differently organized way on the website. That being said, I don't have any evidence that other people find this valuable, and I don't track usage statistics on the website.

baentsch commented 2 weeks ago

I realize that's more effort to keep up to date

That's the core problem. Do you have the time for that?

I believe there's value in having the information presented in a second and differently organized way on the website

I also think so. But shouldn't priority be given to two things: 1) Accurate information 2) Efficiency in information delivery

These things lead me to suggest improvements in efficiency in the face of complications (e.g., access rights removals) and new demands (e.g., change of PQCA mission) thrown at the project and the (very few) people doing the work.

Should we help the community (and people hopefully joining it) understand our work? Yes, absolutely. Does this have to be the (conceptually technical) maintainers' obligation? I don't think so any more: LF wants to run this project as a "large contributor base project" so they should be responsible to make it into that, i.e., attract more contributors, e.g., by way of attractively designing the web site.

Please consider tabling this in some suitable PQCA venue. Thanks.