You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feel free to comment to claim you are interested on working with OAM maintainers to finalize the spec documentation! We will set up a separate coordination meeting ASAP if multiple interested parties show up.
Note: in general the spec related efforts are not a heavy burden but it will be preferred if you already have deep understanding on the core ideas behind OAM. Please DM @resouer or @ryanzhang-oss on oam-dev Gitter or CNCF Slack #kubevela channel for any questions.
The text was updated successfully, but these errors were encountered:
@dhiguero I've updated the remaining docs align with v0.3.0 as a bootstrap. So after the application entity merged, we can do a final review on all the existing spec.
Overview
Based on conclusion on #443, we will begin to work on finalizing https://github.com/oam-dev/spec/blob/master/SPEC.md and promote it to a formal release (v0.3.0).
Remaining Tasks
Needs re-wording to align with the core idea behind the latest spec:
Needs updating on spec content to align with the latest spec design
No significant change, but need to be reviewed to align with latest spec design
How-to
Feel free to comment to claim you are interested on working with OAM maintainers to finalize the spec documentation! We will set up a separate coordination meeting ASAP if multiple interested parties show up.
The text was updated successfully, but these errors were encountered: