Proposed SIG-Docs meeting agenda for 2022-09-27

Meeting Details

Date/Time: September 27, 2022 @ 1730 UTC / 10:30 pm PT
Location: Discord SIG-Docs Voice Room
Moderator: Chanelle Mosquera
Note Taker: TBD

The SIG-Docs Meetings contains the history past calls, including a link to the agenda, recording, notes, and resources.

SIG Updates

Upcoming 22.10.0 release

Our official policy for submissions until release is:

If it's a small fix to existing content published on o3de.org, submit your PR against main.
If it's documentation intended to be provided for the 22.10 release, such as any documentation for a new feature, replacement, or improvement, submit your PR against stabilization/22.10.
If you're writing something for future work that was not accepted into the o3de 22.10 stabilization, submit your PR against development.

[Updated] Important release dates for docs:

Release notes finalized (features + known issues) by 9/30/2022 (tandem with code freeze)
Versioned API reference generation: 9/30/2022

Open action items

[ ] Add code-owners.md and maintainer restrictions (@sptramer). https://github.com/o3de/sig-docs-community/issues/61
[x] https://github.com/o3de/community/issues/157

Newly resolved items

:white_check_mark: https://github.com/o3de/sig-docs-community/issues/54

Initial Agenda

The pre-approved agenda for this meeting is as follows:

SIG Updates - @chanmosq
Agenda item name - Presenter - Length of time
- Description of the item
...

Suggesting and voting on agenda items

Our community is welcome to suggest and vote on agenda items. If you suggest an item you need to have a designated presenter (normally the issue filer), but any community member can vote and isn't required to attend meetings or even participate in further discussion. If you think something is a good idea to discuss for the O3DE community, please upvote!

:+1: reactions to proposed agenda items are counted as YEA votes for taking up discussion, and :-1: as NAY. Votes on items don't determine the final agenda, but do influence it and are strongly taken into consideration as a representation of what the O3DE community wants to see from the project.

Agenda item format

If you leave a comment on this issue to propose an agenda item, please use the following format:

**Topic**: The topic you'll be presenting on
**Presenter**: Who will present (may be a team name or TBD)
**Length of time**: Estimate the amount of time you believe discussion will take. This should not be more than 15 minutes without SIG approval.

Include a description of your topic. Make sure to link to any supplementary materials such as RFCs, forum discussions, issues, etc.

Remember to add the :+1: and :-1: reactions manually, so they appear and are obvious to voters!

Meeting notes

Proposed RFC: Merge access control and designated ownership of o3de/o3de.org

Need response from LF and Marketing, as this affects them
[x] @chanmosq / @stramer To bring up to TSC or other channels to get more traction.

Proposed RFC Suggestion: Discord Forums

(JT) Suggestion to make use of reactions and text formatting to further classify questions. The default reaction is to plus-one the question. If needed, we can further classify things using reactions and by formatting the title of the question. For example including "[Q/A]" in the title.
The primary way to organize a general forum is use of tags. There are a limited number of tags we can have. At this time, they include Resolved, Graphics, Docs, UI-UX, and other O3DE/development verticals.
[x] No pending action items yet, RFC will be open for another week for comments.

Feature Grid

(FiniteState) Working on changes to the overall process of the Feature Grid.
Need more information - Unclear what's expected for the Docs Feature Grid
[x] @chanmosq / @FiniteStateGit To find out more information, possibly reach out to SIG-Release

RFC: Docs Versioning

Need to discuss with LF and Marketing about their website efforts and how it might include helping support docs versioning. Items we need help with include 1) Getting a drop-down box to select the docs version, 2) A DNS for each docs version.
[x] @chanmosq / @willihay To bring up to Marketing and LF.

o3de / sig-docs-community