community
community copied to clipboard
kubeedge
REQUEST: Create <api>: the canonical location of the KubeEdge API definition.
1. Name for new repository:
api
2. Who should have admin access(subproject owners)?
@kevin-wangzefeng @fisherxu
3. Who should have write access?
@kevin-wangzefeng @fisherxu @WillardHu @Shelley-BaoYue @wbc6080 for sync codes from kubeedge/kubeedge
4. Who should be listed as approvers and reviewers in OWNERS?
approvers: @kevin-wangzefeng @fisherxu @WillardHu @Shelley-BaoYue reviewers: @kevin-wangzefeng @fisherxu @WillardHu @Shelley-BaoYue @wbc6080
5. What should the repo description be?
Repository for KubeEdge API, providing KubeEdge standard API definition
6. What SIG does this fall under?
All related SIGs
7. Additional context for request.
This repository provides KubeEdge standard API definitions, such as device crd definition and cloudcore, edgecore configuration. During subsequent development, API changes will still be completed under the original path of the KubeEdge main repository(https://github.com/kubeedge/kubeedge/tree/master/staging/src/github.com/kubeedge), and the changes will be synchronized to the API repository later.
Thanks for initiating this.
During subsequent development, API changes will still be completed under the original path of the KubeEdge main repository(kubeedge/kubeedge/staging/src/github.com/kubeedge/api/), and the changes will be synchronized to the API repository later.
Is there a more formal location for this description? This is very important for people who would contribute to API, and release team members to make sure they add corresponding tag here when new releases cut in the main repo.
It should be located in https://github.com/kubeedge/kubeedge/tree/master/staging/src/github.com/kubeedge, I've updated it in the issue description. In addition, the api files have not been migrated to this directory yet. I will complete the migration as soon as possible.
