Proposed SIG-Docs meeting agenda for 2023-01-10

[chanmosq]

Meeting Details

• Date/Time: Month Date, Year @ 10:30 to 11:00 am PT
• Location: Discord SIG-Docs Voice Room
• Moderator: @chanmosq
• Note Taker: @chanmosq

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

SIG Updates

What happened since the last meeting? - The creator of this issue is responsible for providing a brief summary here to be used as an update to start any important discussions.

Open action items

• [ ] Checkbox list of open action items from previous meetings. If these are closed before or during the meeting, mark them off.
• [ ] ...

Newly resolved items

• :white_check_mark: Unordered list of action items resolved since the last meeting.
• :white_check_mark: ...

Initial Agenda

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

• 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!

[chanmosq]

Meeting notes

Docs updates

• Updates from JT(SCB_GameDesign): Working with a local community group on providing some agile onboarding documentation and will be sharing that back with O3DE community
• Tackling the backlog of o3de/o3de.org
  • For Amazon writers, we need to just start working on the issues. Currently, we rarely look at it because we get caught up in other work to do. We usually only close out issues because it's related to something we're working on. This helps, but still a lot of issues remain because not all contributors look at the issue backlog.
  • We'll need to clean this up as a team
  • How will we divide up the work? we can connect it back to the audit
    • Look through issues, has it been connected to audit. If not and it relates to a section of the audit, add the issue to the audit.
  • Suggestion to request developers also close out related documentation issues as they work on developing their systems.
    • Idea - We can create a Git Action that gets triggered when someone submnits a PR. Depending on the files that the PR touches, it can determine which issues might be relevant to it and produce a list that appears on the PR browser page. This can push the contributor to review the issues that the PR might be related to.
    • We can label the different folders of o3de.org/docs, and trigger the workflow mentioned above.
    • Blender has mechanisms for this too. They've continued to iterate on their process, the community has grown with it, and it's been helping them maintain the pool of issues, PRs, and contributor work.

Community Updates

• Finchy working on a lot of process documentation to hand off to LF:
  • How to write a blog, README.md, etc.
• Working with Marketing meeting to plan for Asset and Content Jam. Goal is to have two asset jams and two content jams. The idea is for the Asset Jam to produce assets that the later Content Jam can use.
  • Will be hosted on itch.io
  • Planning to have the first one in Q1, but no official dates yet.
• Issue - Lots of people in Discord, but not much engagement. Brainstorm how we can drive more engagement?
• Issue - Challenging to get engineers to write blogs. Even more so getting engagement from engineers outside of AWS.
  • It's easier to get content for interviews than blogs.
  • Blog management is planned to hand off to LF.