Skip to content
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

TSC Agenda 2022-03-22 #22

Closed
jeremyong-az opened this issue Mar 15, 2022 · 2 comments
Closed

TSC Agenda 2022-03-22 #22

jeremyong-az opened this issue Mar 15, 2022 · 2 comments

Comments

@jeremyong-az
Copy link
Collaborator

TSC Meeting Details

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

Reply with a comment below to add items to the agenda

@hultonha
Copy link

Topic: Question for Open 3D Foundation (O3DF) partner Adobe - Discuss possibility of releasing an example character and some animations of a Mixamo asset with O3DE.
Presenter: @hultonha and @amzn-jillich
Length of time: 10 minutes
Information: We're working on streamlining the integration of Mixamo into O3DE. In order to further strengthen the collaboration and to demonstrate this effort we'd like to include/open source a sample Mixamo character and animations. We understand there are legal/IP questions around this but would like to discuss the idea with Adobe and see if this can be something mutually beneficial for O3DE and Adobe (attention of @amzn-jillich , @amzn-rhhong @Ulrick28, @galibzon).

@lmbr-pip
Copy link

lmbr-pip commented Mar 22, 2022

Topic: Clarification of Feature Matrix: https://github.com/o3de/community/tree/main/features
Length of time: 5mins?

Had SIG members asking for clarification on setting values.

Content: What does content mean here? Sample Content to show off feature? Test Content? UX content?

Not required: Content is not required for this feature
Incompatible: Content exists, but is incompatible with current feature.
Minimal: Minimal content is available, but may hinder feature usability
Partial: Partial content is available, but does not hinder feature usability
Complete: All content is complete for full feature usability

Code/API - also looking for clarification:

Unproven: Code/API working but has had insufficient use to really harden any corner cases or identify potential pathological issues
Deprecated: Code or API is slated to go away (accompanied with some indication of what the system will be replaced by)
Experimental: Code is unstable or API is likely to change
Volatile: Code works, but may crash or API is fixed, but may possibly change
Stable: Code/API is actively used without any serious impediments and has no immediate upgrades planned.

Some in SIG feel that we have no way to prove something that is functionally complete, cannot claim a state other than Unproven as we have not shipped any content "at scale". Unclear why unproven is the “lowest state” here. Should it be Deprecated -> Experimental -> Volatile -> Unproven -> Stable? Unproven and Volatile seem very similar states based on text, except Volatile means we know it crashes at times?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants