Jianbo Sun

Cool, then we confirm using `type`. BTW, let's move the API to `v1beta1`. So the final example could be: ```yaml apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: application-sample spec: components: -...

ref https://github.com/oam-dev/kubevela/pull/1282

The idea of `ComponentRevision` is really good and this don't add concept burden to OAM. And for the naming issue, I totally agree with @negz . We shouldn't add new...

> In that case, should we consider renaming ApplicationConfiguration to AppDeployment? Not necessary I think. Both of them can be understood as a deployment thing

Yes, we are designing a micro-app engine core for k8s based on OAM. Traits Registry will be included in it.

I have given a PR(#473) to solve how we give errors back to the user. My answer is k8s events. In that PR, I also give an example, when I...

Very good proposal! I have several questions: 1. What will the `Application lifecycle hooks` works like? Could you give some yaml examples. I'm really interested with it. 2. In KubeVela...

It seems what you said is a dozen of traits, including ingress trait, flow limit trait, etc.. Cloud you give some detail cases for `gateway_rule` adding into component that could...

@KaiwenWang @captainroy-hy let's work together. I could setup i18n framework in the project.

Which chapter of them do you like translate? We could split the work.