Proposed SIG-Docs meeting agenda for February-08-2022 about sig-docs-community

[hultonha]

Topic: As an O3DE contributor I would like to be able to submit documentation of features that are in o3de development branch without affecting the release documentation of o3de.
Presenter: @hultonha (also potentially @moraaar)
Length of time: 10 minutes

Tagging @amznestebanpapp for visibility on this as they have expressed interest in it too.

[sptramer]

Topic: SIG role in tooltips, in-editor help, etc etc
Presenter: @sptramer
Length of time: 10-15m

The docs sig occasionally gets requests to review in-editor help information, and most importantly, our role in in-editor help has come up across the PRs o3de/o3de.org#1339 and o3de/o3de#6555. Engineers may be unwarily making changes which impact the user experience of documentation, and we should consider the sig-docs-community role in making sure that in-Editor documentation resources (whether static strings, site links, or something else) are appropriately reviewed and updated.

[Ulrick28]

Topic: How much lead time does sig-docs require before a release?
Presenter: @AMZN-JoeB
Length of time: 5m

We are putting together the time cost/overhead of a release to help determine a realistic release cadence for O3DE. sig-release would like to know how much lead time sig-docs needs to prepare for a release.