...
| View file |
|---|
| name | anuket release process goals and objectives .mp4 |
|---|
| height | 150 |
|---|
|
| View file |
|---|
| name | Anuket Release Process Issues and Objectives-2.pdf |
|---|
| height | 150 |
|---|
|
Minutes
Slides are just a framework to spark discussions. The follow up to this session will be taken into the Anuket TSC. Anuket has a challenge because the artifacts are not only code. They are documents, implementations, etc. Have to explain the concept of a feature from its lifecycle that folds in requirements to conformance platforms end to end. Something that is integrated is important to make it useful to the community. Anuket happened because the components need to be integrated, however it requires changes on how the community thinks about the artifacts and how they can be consumed by the operators and vendors alike. There are artifacts in RM and RA that do not always translate into components that go into RI and RC artifacts. Sometimes the components are forward thinking, can drive use cases and gaps in the technology, that spawns work with peer, downstream and upstream communities – e.g. CNCF Working Group, Barometer project, are influenced by the Anuket use cases and models.
...
