RFC for Core Charter

[OBWANDO]

Please read and provide feedback on our charter in this thread:

SIG Core Charter

This charter adheres to the Roles and Organization Management specified in "<sig-governance.md>".

Team information may be found in the "<readme.md>"

Overview of SIG

Two concise lines explaining what this SIG does with bullet points of the major responsibilities

• Responsibility 1

Goals

• Major goals that SIG seeks to generally achieve

Scope

• Responsible for the keybind and controller framework system

• Design and implement localization framework for editor and project runtime.

• Publish and maintain localization data format structure

• Maintain behavior context, edit context, serialization contexts, and code reflections frameworks and systems.

• Create framework for exposing profiling and metrics data that can be collected

• Maintain generic node based scripting framework and data representation model

• Maintain asset catalog, asset processor, and builder systems and framework

• Maintain Packaging artifact and catalog system

• Design and Maintain asynchronous loading stream system

• Maintain Prefab system

• Maintain Core system libraries AZCore, and AZFramework libraries

• Maintain Editor python bindings framework

• Maintain Physics API, and integration of physics related gems

• Maintain EmotionFX and Animation systems

• Maintain Logging and Trace systems and frameworks

• Publish and maintain list of use case examples for each subssystem of AZCore.

Generalized overall scope of work

In scope

Cross-cutting Processes

• Support and collaborate with all SIGs in relation to changed and updates to underlying frameworks
• Publish procedure for the intake of requests from SIGs in relation to changes and needs to core systems
• Provide consultation, discovery, and guidance for new feature support brought forth by other SIGs
• Publish and matinain best practices, usability examples, and feature documentation.

Out of Scope

• Not responsible for building bespoke solutions to meet individual needs, but may be consulted with from time to time without obligation.

SIG Links and lists:

• Joining this SIG
• Slack/Discord
• Mailing list
• Issues/PRs
• Meeting agenda & Notes

Roles and Organization Management

SIG Docs adheres to the standards for roles and organization management as specified by . This SIG opts in to updates and modifications to

Individual Contributors

Must provide a report of performance and blast radius impact of direct and indirectly affected systems

Additional information not found in the sig-governance related to contributors.

Maintainers

Additional information not found in the sig-governance related to contributors

Additional responsibilities of Chairs

Additional information not found in the sig-governance related to SIG Chairs

Subproject Creation

Additional information not found in the sig-governance related to subproject creation

Deviations from sig-governance

SIG will elect 4 Chairmembers due to vast interaction across all SIGs

Explicit Deviations from the sig-governance

[rgba16f]

The current scope section reads like a task list. We should update it to be more generic.

e.g.

Design and implement localization framework for editor and project runtime.

should be - Owns localization framework.

Then

Publish and maintain localization data format structure

is implicitly part of owning the localization framework.

This way we can also say we own X API vs owning X.