소스 검색

Merge branch 'main' into update-meetings-readme

Signed-off-by: chanmosq <[email protected]>
chanmosq 2 년 전
부모
커밋
8b460580fe
4개의 변경된 파일25개의 추가작업 그리고 12개의 파일을 삭제
  1. 17 9
      .github/ISSUE_TEMPLATE/reviewer-maintainer-nomination.md
  2. 4 1
      README.md
  3. 1 0
      meetings/README.md
  4. 3 2
      rfcs/README.md

+ 17 - 9
.github/ISSUE_TEMPLATE/reviewer-maintainer-nomination.md

@@ -4,9 +4,14 @@ about: Nominate yourself or someone else to become a SIG reviewer or maintainer
 title: 'SIG Reviewer/Maintainer Nomination'
 ---
 
-The Documentation and Community SIG maintains two reviewer roles requiring SIG approval: *Documentation reviewer* and *technical reviewer*. Documentation reviewers review for conformance with the [style guide](https://o3de.org/docs/contributing/to-docs/style-guide/), appropriateness of content, and other subjective factors to keep documentation content aligned. Technical reviewers review for technical accuracy alone: They make sure that described steps, features, file formats, code examples, and other parts of documentation that are deeply technical match the _current_ product state.
+The Documentation and Community SIG maintains several reviewer roles requiring SIG approval:
 
-For more on the Reviewer and Maintainer roles, read our [Community Membership](https://github.com/o3de/community/blob/main/community-membership.md) information.
+* **Documentation reviewer** - Documentation reviewers review for conformance with the [style guide](https://o3de.org/docs/contributing/to-docs/style-guide/), appropriateness of content, and other subjective factors to keep documentation content aligned.
+* **Technical reviewer** - Technical reviewers review documentation for technical accuracy: They make sure that described steps, features, file formats, code examples, and other parts of documentation that are deeply technical match the _current_ product state.
+
+Any individual can be a member of multiple reviewer or maintainer roles within this SIG!
+
+For more on the general requirements of Reviewer and Maintainer roles, read our [Community Membership](https://github.com/o3de/community/blob/main/community-membership.md) information.
 
 ----
 <!-- CUT ABOVE THIS LINE BEFORE POSTING -->
@@ -14,26 +19,29 @@ For more on the Reviewer and Maintainer roles, read our [Community Membership](h
 
 #### Documentation reviewer
 
-* [ ] 6+ documentation contributions merged to o3de.org or O3DE
-* [ ] 2+ Reviewer or Maintainers of the Documentation and Community SIG.
+* [ ] 6+ documentation contributions merged to o3de.org or O3DE. The following count as documentation contributions:
+  * Contributions to the Atom Guide, User Guide, Welcome Guide, or Tutorials sections of https://o3de.org/docs
+  * High-quality error messages, tooltips, UX text, or API documentation submitted to https://github.com/o3de/o3de involving approval of
+    at least one sig-docs-community reviewer.
+* [ ] 2+ Reviewers or Maintainers of the Documentation and Community SIG approve the nomination.
 
-**Maintaining status:** 4+ Pull Requests reviewed per month.
+**Maintaining status:** 4+ Pull Requests reviewed per month, or as-assigned. Light loads of PRs relax these requirements.
 
 #### Technical reviewer
 
 * [ ] Is a Reviewer or Maintainer for a SIG governing the appropriate technology.
 * [ ] 1+ of the appropriate SIG's Reviewers or Maintainers who support the promotion.
-* [ ] 1+ D&C Reviewers or Maintainers who support the promotion.
+* [ ] 1+ Reviewers or Maintainers of the Documentation and Community SIG who support the promotion.
 
 **Maintaining status:** Serve in the technical review rotation for your SIG as required by their available pool of reviewers.
 
 #### Documentation maintainer
 
 * [ ] Has been a Reviewer for 2+ months
-* [ ] 8+ reviewed Pull Requests in the previous 2 months
-* [ ] 2+ D&C SIG Maintainers who support promotion.
+* [ ] 12+ reviewed Pull Requests in the previous 2 months (exceptions may be made during periods of light load)
+* [ ] 2+ Documentation and Community SIG Maintainers who support promotion. In the absence of enough maintainers, chairs will promote.
 
-**Maintaining status:** 8+ Pull Requests reviewed per month.
+**Maintaining status:** 8+ Pull Requests reviewed per month. Maintainers are encouraged to attend SIG triage and other regular meetings.
 
 -------
 ### Reviewer/Maintainer Nomination

+ 4 - 1
README.md

@@ -6,7 +6,7 @@ We run the [o3de.org/docs](http://o3de.org/docs) website, manage its content, an
 
 You can reach us at @sig-docs-community on Discord!
 
-For a broader view of the whole O3DF community, go to the [o3de/community](https://github.com/o3de/community/) repo.
+For a broader view of the whole O3DE community, go to the [o3de/community](https://github.com/o3de/community/) repo.
 
 ## D&C SIG Responsibilities
 In summary, our responsibilities include:
@@ -20,17 +20,20 @@ For more information, see the official [Documentation and Community SIG Charter]
 ## How can you contribute? 
 
 **Contribute to O3DE Documentation**
+
 Whether it's filing an issue, updating existing docs, or even writing completely new docs - we highly appreciate all efforts to improving the documentation. 
 
 If you're thinking of contributing to the docs, review [Contributing to O3DE Documentation](https://www.o3de.org/docs/contributing/to-docs/)  for onboarding instructions, style guides, and docs templates. 
 
 
 **Write a blog post** 
+
 If your team is working on an exciting project with O3DE or developing an awesome feature for the engine, then share the news in a blog post! 
 
 Read about [How to Submit a Blog Post for o3de.org](https://www.o3de.org/docs/contributing/to-docs/blog-posts/) and check out the latest [O3DE blogs](https://www.o3de.org/community/) from the community. 
 
 **Attend our meetings** 
+
 Everyone is welcome to attend our meetings in the #sig-docs-community voice channel! We triage [`o3de/o3de.org` GitHub issues](https://github.com/o3de/o3de.org/issues) weekly, and have docs-/community-related discussions bi-weekly. 
 
 Check out the [calendar](https://lists.o3de.org/calendar#) for events, and view past [meeting notes](meetings/README.md). Look out for upcoming meeting agendas in [sig-docs-community issues](https://github.com/o3de/sig-docs-community/issues).

+ 1 - 0
meetings/README.md

@@ -26,6 +26,7 @@ O3DE cannot work without the help and input from as many of its community member
 | 2022-11-08 | [Link](https://github.com/o3de/sig-docs-community/issues/68) | [On Agenda](https://github.com/o3de/sig-docs-community/issues/68#issuecomment-1307737835) |
 
 
+
 ## Pre-release meetings
 
 Preserved for posterity. Thanks to everyone who helped Open 3D Engine launch!

+ 3 - 2
rfcs/README.md

@@ -11,9 +11,9 @@ This is the tracking list for proposed, open, and accepted RFCs for sig-docs-com
 
 | RFC | Summary |
 |-----|---------|
-| https://github.com/o3de/sig-docs-community/issues/54 | Website versioning for different releases of O3DE, including better visibility and maintenance policies around the `development` branch. |
+| https://github.com/o3de/sig-docs-community/issues/64 | Feature grid requested by the Linux Foundation, supplemental docs edition. |
+| https://github.com/o3de/sig-docs-community/issues/61 | Access control and ownership of o3de/o3de.org. |
 | https://github.com/o3de/sig-docs-community/issues/43 | Assignment of O3DE issues to `sig/docs-community`; Without a global triage there needs to be a formal process for SIGs to follow. **NOTE:** Gavin may have taken over the global sync, which means this RFC may no longer be needed. |
-| https://github.com/o3de/sig-docs-community/issues/40 | Feature grid requested by the Linux Foundation, supplemental docs edition. |
 
 ## Accepted 
 
@@ -21,6 +21,7 @@ This section is a running list of RFCs that have been accepted by the SIG.
 
 | RFC | Summary |
 |-----|---------|
+| https://github.com/o3de/sig-docs-community/issues/54 | Website versioning for different releases of O3DE, including better visibility and maintenance policies around the `development` branch. |
 | https://github.com/o3de/sig-docs-community/issues/32 | Separate `main` and `development` branches of o3de.org to reflect different product states and to prepare for website versioning. |
 | https://github.com/o3de/sig-docs-community/issues/8 | Accepting SIG charter. |
 | https://github.com/o3de/sig-docs-community/issues/64 | Documentation health in each important feature area needs to be reported in some way for the O3DE feature grid. This RFC covers the column extensions and terminology used by sig-docs-community for reporting on the state of documentation in a way that aligns with how SIGs report on the state of their features to the TSC, TAC, and Governing Board. |