How we prioritise our objectives
We use a Mural board with a priority radar to discuss our shared priorities across different topics. Cards that are of primary importance are placed in the radar's innermost circle.
| Info |
|---|
Cards can be added at anytime to the categories on the left but we move the cards to radar as a team. |
Summary
| Expand |
|---|
| title | Clarify and Define Separation of Concerns |
|---|
|
Features Ownership - Who owns data value resolving? (USD?)
- Who owns usd<->mtlx synchronization? (USD?)
- Who owns the mtlx->usd conversion?
- Who owns the usd->mtlx conversion?
- Who owns validation (USD?)
- Who owns reference definitions, who owns implementations (MaterialX?), including USDPreviewSurface?
- Who owns code generation access.
- Who decides what is common material metadata? There's not a 1:1 mapping between USDShade and MaterialX so how can we drive standardisation?
|
...
