SIG Content Assets Discussion Group

[lmbr-pip]

What is this?

SIG-content is huge, it covers a lot of different topics: scripting, editor, assets, project-manager etc. As such we proposed creation of a number of working or discussion groups around a specific sub-area in SIG/content. See #81

sig-content-assets is working-group/discussion group within SIG/content that focuses on all things assets: the asset pipeline, processor, scene pipeline, asset loading, formats and asset bundling. Its designed as focal point for these discussions, to assist SIG/content in its wide ownership.

sig-content-assets will focus on issues and PRs with the following labels (assuming underlying issue/PR is also owned by sig\content)

• feature/asset-pipeline
• feature/scene-pipeline

The group will give input into feature/asset-browser issues where it interacts with the asset system but expect to own in conjunction with the Editor experts of SIG/Content.

This group is contained within and is part of SIG/content. The group must demonstrate benefit to SIG/content and work to support the goals and charter of the SIG. Reviewers and maintainers for sig-content-assets are general SIG/content reviewer and maintainers. The group has no specific powers unless explicitly granted by SIG/content chair(s). SIG/content chair(s) can dissolve the working group at any time, especially if its not functional or proving beneficial for the SIG.

What the group does?

• Triage any issues on behalf of SIG/content which are specific to assets, including those tagged with feature/asset-pipeline, feature/scene-pipeline and feature/asset-browser that requires expertise or additional information.
  • These issues to be flagged by general SIG/content issue triage.
• Reviews asset related issues, RFCs and PRs.
• Meets at least once a month, in a public meeting, to discuss asset issues relevant to SIG/content
  • Provides notes of meetings to SIG/content
• Provides a representative to the general SIG/content monthly meeting to provide updates on asset related activity of relevance to the SIG.
• Assists SIG/content in managing roadmap items relating to assets.
• Provide support help to the community about working with assets, asset conversion, asset pipeline, scene pipeline, working with assets in O3DE and asset packaging.
• Provide a forum to discuss asset related issues within the SIG.

These are suggestions, would love to get ideas about how we can make group effective and meet the needs of users and contributors in the asset space for O3DE.

Who can attend or participate?

O3DE cannot work without the help and input from as many of its community members as possible. You do not need anyone’s permission to get involved and contribute to the project. The #sig-content-asset thread on O3DE’s Discord is a great place to begin getting involved or raising and discussions issues in #sig-content as before.

How do I get involved?

• Join in the initial asset thread under sig-content on Discord (needs to be created)
• Attend our meetings
  • Initial meeting will be posted to O3DE calendar and announced in sig-content
  • Aim to establish a cadence relevant to the workload of group.
• We will nominate facilitator(s) for the working group in our first meeting. Group will self-organize facilitator(s).

Why a discussion group?

• SIG/content is huge and covers many things. We want to create a more focus place to discuss just the asset pieces owned by SIG/Content.
• Can hold specialized office hours with experts.
• Try and drive engagement in specialized areas of SIG/content

See #81 for more details

Things to create

• [x ] An initial meeting agenda open to all
• An initial sig-content-assets thread in sig/content
• A poll for first meeting to be held in the week starting Dec 12th Scheduled initial meeting based on availability and so we can start discussions prior to the end of year break.
• Add an entry into the general SIG/content README.md to describe what the group does, how to get involved.
• Meeting notes captured in SIG/content notes section for all to see

[lmbr-pip]

Look to the SIG/chair(s) @lsemp3d and @monroegm for any feedback about what we should and shouldn't be doing. As this is the first group to launch, any and all guidance is appreciated.

[lmbr-pip]

Am proposing that we either:

Meet weekly and alternate between issue triage and an asset meeting

Week 1 - Issue triage (issue of note to group)

Week 2 - Asset meeting, which would cover

• Office hours Items (15 mins) - 3 x 5 min slots
• Demo new features (10 mins) - 2 x 5 min slots
• Roadmap Review (If time permits) - 5 mins

Pros: More reactive, more timely discussions
Cons: Less time to discuss things

** Or meet monthly **
Alternative is to meet at less regular cadence, such as once per month, and have an hour long meeting with the agenda:

• Office hours Items (15 mins) - have 3 x 5 min slots
• Demo new features, discuss RFCs or roadmap items (15 mins) - have 3 x 5 min slots
• O3DE Roadmap Review for assets - 10mins
• Open Discussion / Group business
• Issue Triage

Representatives will continue to attend SIG/content issue as per normal

Pros: More discussion time, less demand on folks time.
Cons: Less reactive

[lmbr-pip]

Agenda for Dec 14 meeting

• Quick introduction to SIG/content assets group
• Agree on meeting cadence and time
• Agree on meeting organization
• Cover what should be in scope for group and how we work within SIG/content
• If time permits, hold office hours or other items folks want to discuss

[lmbr-pip]

Alternative name suggestion sig-content-asset-pipeline

Agreed two week cadence, starting second week in January (approx).

Also discussed some potential contributions from Film/video spaces:

• JT: Raised that there maybe USD datasets contributors are looking to contribute for testing (more film orientated for now)
• Decal library is being discussed for contribution (see January, looking to set up github repro).