o3de / community Goto Github PK

monthly to start most likely, then quarterly

This will affect how we submit pull requests to the repo. Either through a branch in the repo of through a fork owned by our team.

due: 2021-05-31

• JoinNow page
• Get involved webform w/ autoresponder
• Charter
• (broader messaging/content)"

due: 2021-04-30

How will maintainers get elected etc

due: 2021-01-11

due: 2021-01-12

due: 2021-05-07

due: 2021-01-22

Create security disclosure policy

due: 2021-02-26

due: 2020-12-18

due: 2021-05-01

The would we look at using AWS services that would be covered by credits or funds from the LF.

If we have to host some resources outside Github because of Github rules or limitations can we use an AWS account that the foundation has access to?

Are there any example links or projects that use a full CI/CD chain as an example?

due: 2021-01-13

due: 2020-10-14

due: 2021-01-21

due: 2020-10-15

due: 2021-06-14

• Governing Board
• Outreach
• Members
• Announce"

due: 2021-01-18

due: 2021-03-09

due: 2021-06-01

due: 2021-03-09

(March 9-11, 2021)

due: 2021-01-29

due: 2021-04-16

due: 2020-12-02

due: 2020-11-10

(overall concept and timeline; also provide governance docs with high-level orientation)

due: 2020-10-16

Lumberyard currently has metrics gathering in it as well as things like periodic questions about how well the software its doing, these goes to Amazon currently - would we remove them, or route the results elsewhere? Is there a pre-existing crash reporting stack we can adopt? Are there guidelines about disclosure to users or opt-in?

due: 2021-03-09

due: 2020-10-14

due: 2021-05-17

due: 2020-12-08

due: 2021-03-09

due: 2020-12-15

Clyde's team will need a SME + a couple months lead time

due: 2020-10-19

due: 2020-12/08