Add meeting notes for 2021-09-22.

Signed-off-by: stramer <[email protected]>

meetings/README.md

@@ -10,9 +10,12 @@ O3DE cannot work without the help and input from as many of its community member
 
 | No   | Date       | Time     | Agenda  | Media | Notes | Resources |
 | ---- | ---------- | -------- | ------- | ----- | ----- | ---- |
-| 0001 | 2021-08-27 | 1800 UTC | [Link](https://github.com/o3de/sig-docs-community/issues/5) | N/A | [Link](notes/sig-meeting-20210827.md) | N/A |
+| 0001 | 2021-08-27 | 1800 UTC | [Link](https://github.com/o3de/sig-docs-community/issues/5)  | N/A | [Link](notes/sig-meeting-20210827.md) | N/A |
+| 0002 | 2021-09-22 | 1600 UTC | [Link](https://github.com/o3de/sig-docs-community/issues/13) | N/A | [Link](notes/sig-meeting-20210922.md) | N/A |
 
-## Pre-release meetings 
+## Pre-release meetings
+
+Preserved for posterity. Thanks to everyone who helped Open 3D Engine launch!
 
 | No   | Date       | Time     | Agenda  | Media | Notes | Resources |
 | ---- | ---------- | -------- | ------- | ----- | ----- | ---- |

meetings/notes/sig-meeting-20210922.md

@@ -0,0 +1,60 @@
+# Docs & Community SIG meeting - 2021-09-22
+
+**Facilitator:** Stephen Tramer (@sptramer)
+**Notes taker:** Erik Jacobs (@thoraxe) / Stephen Tramer (@sptramer)
+
+[Agenda](https://github.com/o3de/sig-docs-community/issues/13)
+
+## SIG Updates
+
+* The SIG will be releasing an initial roadmap of documentation commitments before the next _product_ release, currently scheduled
+  for late November.
+  * [O3DE Roadmap](https://github.com/o3de/o3de/projects/1)
+  * [O3DE docs / website roadmap](https://github.com/o3de/o3de.org/projects/1)
+
+* Open items from the 2021-08-27 meeting are being closed or now have final dates for feedback. Remaining open items are:
+  * [ ] [Charter](https://github.com/o3de/sig-docs-community/issues/8) and [Charter PR changes](https://github.com/o3de/sig-docs-community/pull/6) - **Closes 9/30/2021**
+  * [ ] [PR template](https://github.com/o3de/o3de.org/pull/935) - **Closes 9/30/2021**
+  * [ ] [Blog post requirements](https://github.com/o3de/o3de.org/pull/749) - **Closes 9/30/2021**
+
+* The first official docs triage will be scheduled for sometime next week.
+
+## Contributor Requirements and Roles
+
+*Presenter*: Stephen Tramer
+
+* [O3DE has adopted contributor rules](https://github.com/o3de/community/blob/main/community-membership.md) and the SIG established [reviewer roles](https://github.com/o3de/sig-docs-community/issues/2). Contributor rules were geared towards documentation code and so we need to make some additions:
+  * "Lines of code" will not be used as a metric for docs. In its place we will consider:
+
+    * Regular contributions of good quality for promotion to Reviewer
+    * Higher numbers of reviews and regular participation for Maintainer
+
+  * Reviewer roles expressed in the role list will be _unofficial_ (other than tech reviewer requirements) and reviewers who believe they can capability fill the role should do so. Specialized roles might require training.
+
+### Action items
+
+* [ ] @sptramer - Create PR to update the contributor guidelines and add the appropriate labels.
+
+## Community coordination efforts
+
+*Presenter*: Stephen Tramer
+
+* In order to get started with O3DE and understand our existing plans for the site and content, the Amazon team needs to find and export some information for things like content taxonomy and ToC design.
+* Contributors also need guidance on where to get started, how to go through the early workflows, etc.
+
+### Action items
+
+* [ ] @stramer - Find and export internal docs information
+* [ ] @spotz - Work on onboarding for contributors to commiting to O3DE docs
+
+## Project proposal: Lua Documentation
+
+*Presenter*: Stephen Tramer (proposer not present)
+
+* [The proposal](https://github.com/o3de/sig-docs-community/pull/12) was **ACCEPTED** with minor edits to ensure that it's clearly focused on _documentation_.
+  * The proposal was not assigned an owner and is not considered an active project.
+
+### Action items
+
+
+

projects.md

@@ -1,12 +1,12 @@
 # Projects proposed for the SIG
 
-During the early days of Open 3D Engine we'll be taking project pitches through the Wiki to find people interested in running or participating in certain medium- and long-term efforts to improve the documentation of O3DE (or access to it) and community outreach.
+During the early days of Open 3D Engine we'll be taking project pitches to find people interested in running or participating in certain medium- and long-term efforts to improve the documentation of O3DE (or access to it) and community outreach.
 
 ## How to propose a project
 
 If you're planning to take long-term effort on something which affects the responsibilities of the D&C SIG according to its charter, you might want to propose a project so that at minimum, the SIG is aware that the work is happening (even if it's not "officially" approved.)
 
-Add a row in the table below via a PR to propose a project! Any proposals submitted as wiki changes will be accepted onto this page as long as they:
+Add a row in the table below via a PR to propose a project! Any proposals submitted as changes will be accepted onto this page as long as they:
 
 * Align with the [SIG Charter](https://github.com/o3de/sig-docs-community/blob/main/governance/charter.md) in some way.
 * Follow the [Code of Conduct](https://github.com/o3de/community/blob/main/code-of-conduct.md) in their description and intent.
@@ -24,5 +24,5 @@ Some notes:
 
 | **Project Name** | **Proposer** | **Description** | **In progress** | **Approved** | **Owner** |
 |--|--|--|--|--|--|
-| Example | @sptramer | Just an example. | :x: | :x: | |
-| Lua API Reference | @FiniteStateGit | Topic: Proposed project - Lua Documentation.  Determine what steps are required to generate online documentation of the Lua API.  Determine if o3de\Assets\Editor\Translation\scriptcanvas_en_us.ts is sufficient to generate an API.  If generating API documentation is technically feasible, proceed with documenting the API on the docs site.  Scope of proposed documentation: Reflected class_name, method_name, method_parameters, parameter_type. | :x: | :x: | |
+| Example | @sptramer | Just an example. | :x: | :x: | :x: |
+| Lua API Reference | @FiniteStateGit | Topic: Proposed project - Lua Documentation.  Determine what steps are required to generate online documentation of the Lua API.  Determine if o3de\Assets\Editor\Translation\scriptcanvas_en_us.ts is sufficient to generate an API.  If generating API documentation is technically feasible, proceed with documenting the API on the docs site.  Scope of proposed documentation: Reflected class_name, method_name, method_parameters, parameter_type. | :x: | :white_check_mark: | :x: |