Proposed SIG-Docs meeting agenda for 2022-08-23

[FiniteStateGit]

Meeting Details

• Date/Time: August 23, 2022 @ 1730 UTC / 10:30 AM PT
• Location: Discord SIG-Docs Voice Room
• Moderator: FiniteStateGit
• Note Taker: TBD

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

SIG Updates

• SIG triage guide has been added to the repo: https://github.com/o3de/sig-docs-community/blob/main/governance/sig-triage.md
• SIG-Docs-Community Election | Nominations 18 Aug - 29 Aug | Elections 31 Aug - 14 Sep #57
• RFC: Docs Versioning #54

Open action items

• RFC NEEDED: C++ API reference generation and coverage chart #50
• RFC NEEDED: Documentation deprecation path #49
• "Self-hosted" Gem documentation #52

Newly resolved items

• ✅ Monthly SIG meetings moved to 10:30AM PST on the 2nd and 4th Tuesday of the month.
• ✅ Docs versioning: Pre-RFC Discussion #46
• ✅ We need a standard for referencing and linking to source code #47

Initial Agenda

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

• Determine open action items to carry forward into next SIG term. Proposed SIG-Docs meeting agenda for 2022-08-09 #45

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!

👍 reactions to proposed agenda items are counted as YEA votes for taking up discussion, and 👎 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 👍 and 👎 reactions manually, so they appear and are obvious to voters!

[willihay]

Stabilization branch for source repo will be created on 29 Aug. Checking in to make sure we have plans to do the same for docs.

[FiniteStateGit]

Meeting Notes:

Action items carried forward from previous meetings:

• Delete stale branches.
• Add code-owners.md and maintainer restrictions (@sptramer).
• Decide if and where to place target user definitions.
• Add information on contributing to O3DE and the SIG on readme: https://docs.google.com/document/d/1Uuz0mvEOMcXBAzcJpop7EqFGzbU2nhXK52wG_c_ls08/edit.
• Remove docs subdomain from o3de.org.
• Add automated submission checks (broken links, spelling, style issues).
• Incorporate feedback into SIG docs feature grid (@FiniteStateGit). Proposed SIG-Docs-Community Feature Grid #40

Create Stabilization branch:

• SIG approved creating Stabilization branch after Main to dev/220816 o3de.org#1915 is merged.
• SIG will announce branch and branch policies.
• Release notes, with a topic containing known issues for the 22.10 release will be made against Stabilization.
• Any docs changes related to 22.10 release should be made against Stabilization.