-
Notifications
You must be signed in to change notification settings - Fork 214
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
API Design Review WG / proposal #531
Comments
@angellk actually sorry about this but I have a vacation planned on 02/21, so it'll be difficult for me to speak to it. Would it be possible to bump this topic up to 02/07 or after on 03/06? |
@toumorokoshi we'll look for a different date! |
@toumorokoshi Let's plan on 03/06 - the whole hour will be dedicated to the API discussion. cc @joshgav @lianmakesthings @thschue |
sounds good! we'll be there. |
Related: #448 |
Hi everyone, we've decided to move forward with an App Dev Working Group, in full awareness that this WG is somewhat out of scope for the App Delivery TAG. |
This is a tracking issue to discuss the possibility of a working group (or whatever construct) around API Design Review for CNCF projects.
For context: there is a group of API design leads from various organizations today (Roblox, IBM, Microsoft, Netflix, and some ex-Googlers) who meet in a regular meeting around API Enhancement Proposals (https://aep.dev/). We've previously applied to be a CNCF project or working group (see #448).
We're looking at ways to contribute to the CNCF ecosystem, and one such way is to help review new APIs that are being introduced by CNCF projects. Long-term we'd like to develop a unified specification around remote APIs, but short-term we could use our time to review new APIs being introduced, help drive them toward uniform best practices, and use that to refine our own specification in progress.
Perhaps there's time to discuss this at the next tag meeting (2/21?)
Relevant slack threads:
The text was updated successfully, but these errors were encountered: