-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TAC/TSC Monthly Sig Meeting 1/2023 #64
Comments
Consider linking the comment, roadmap item, issue or other over here. |
As SIG/Network chair I will miss this meeting. Hopefully SIG/Network co-chair can make it: For SIG/Network
Our roadmap is here https://github.com/orgs/o3de/projects/22 (but like many roadmaps its currently private and we need to find who has the permissions to flip to public) - still a work in progress. |
SIG-Testing roadmap |
Here's the SIG-Build roadmap. @dshmz and I are planning on attending. Some notable items:
|
Here is sig-simulation's roadmap - still WIP but more issues will be added soon. It's relatively up to date in terms of things that have been completed and are in progress (tagging @lgleim and @epsilon-delta for visibility - co-chairs of sig-simulation). |
SIG-Release Update is here. o3de/sig-release#131 |
Here is the link to the WIP SIG-Core roadmap |
SIG-Platforms: roadmap |
As we have more people starting to come over from cross-pollination and awareness some are unsure why and where to get into SIGs. It may be helpful if the SIG readme could answer a few of these questions where they can be found. How can people get involved in each area? |
SIG Docs and Community
|
I'd like to discuss the good first issue label. If you click on this link it takes you to a query based on the label "good first issue". However we are using the label "good-first-issue" (with hyphens) and so that link returns no results, even though we have dozens of issues we have labelled. This is obviously problematic for attracting new community participants. |
All SIG's please leave a comment on your SIG's roadmap for reading in the next meeting.
The text was updated successfully, but these errors were encountered: