Hi Docs team, Matthew Miller and I were discussing the Changes process recently and he brought up that the documentation side of the proposals is often under-appreciated. I file release notes issues for all of the externally-facing Changes, but that's not necessarily sufficient. The specific Change that brought this up is the "Strong Crypto Settings 2" change[1] that went into F33. It caused a lot of user questions. So I'd like your ideas on how we can preemptively cover some of the documentation aspects of the Changes in a way that isn't overly burdensome on Change owners or the Docs team. One thing I've added is that I'll review the accepted proposals at the Code Complete (100%) deadline to see which changes have implemented the docs they said they would. Are there other things we can do to be more proactive? [1] https://fedoraproject.org/wiki/Changes/StrongCryptoSettings2 -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis _______________________________________________ docs mailing list -- docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to docs-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@xxxxxxxxxxxxxxxxxxxxxxx
