TSC Agenda 2022/08/02

[jeremyong-az]

TSC Meeting Details

Date/time: 2022-08-02 @ 8am Pacific (Timezone Converter)
Location: Discord tac-tsc voice channel

[lmbr-pip]

There are TSC issues in GItHub which do not seem have owners: o3de/o3de#10184 seems like it needs some what urgent action (other issues https://github.com/o3de/o3de/issues?q=is%3Aissue+is%3Aopen+label%3Atsc)

[jeremyong-az]

Thanks @lmbr-pip I've closed that issue with a comment. As for the other issues, I've closed them or removed the label depending on direct TSC relevance.

[hultonha]

Topic: Suggest sigs as part of the triage process check the O3DE nightly builds.
Presenter: @hultonha
Length of time: 5 minutes
Information: The O3DE nightly builds quite often break (it's usually something to do with a break in the Release configuration when asserts are disabled for example). Engineers often don't check the state of the nightly build and it's easy for problems to hang around for longer than we'd like. It would be great to include checking the nightly builds in the sig triage process to make sure we have more eyes on the nightly build at a more regular cadence.

Tagging @moraaar, @greerdv, @amzn-jillich and @SergeyAMZN for visibility

[lmbr-pip]

For external Gems (AWS Gems, PopcornFX etc) what expectations should we have around functionality around Development? For example PopcornFX (https://www.popcornfx.com/docs/popcornfx-v2-12/plugins/o3de-gem/) works against last major release, but is broken against Dev and its been a long times since the last release of O3DE.

The way the gem is vended means we can't make changes or even provide a cloned / patched version.

Should we have:

• Expectations around external gems and how they track dev?
• Clear guidance to provide issue feedback to gem vendors?

Concern is that any content in O3DE that relies on these gems right now has to be pinned to a major engine version, which causes a huge gap in demonstrating or using new features, if you want to want to use critical gems like WWise or PopcornFX (where there is no alternative in place).

[galibzon]

Topic: Managing Proprietary 3rdParty Gems.

1. Find open source alternatives. Engage with those developers and incentivize to create an O3DE integration.
2. Create a "kitchen sink" game project where all the Proprietary 3rdParty Gems, e.g. PopcornFX, WWise, AWS Gems are compiled against. Define a build cadence and if the project doesn't compile, under the development branch, report to the owners to fix.

[jeremyong-az]

I would like to discuss #45

[thefranke]

Topic: Switching Github accounts and transferring rights for O3DE.

In the future people who have company-bound Github accounts may switch affiliation but still want to contribute to O3DE. Should we transfer their rights?