If this is not a proposal, then there is no concern from me. Once PMC agrees to establish a new repo(not necessary a new project), it is good to go.
Sheng Wu 吴晟 Twitter, wusheng1108 wei jin <[email protected]> 于2020年7月25日周六 下午8:30写道： > thanks, I will keep apisix-* repo naming style > > the shared doc is a tech topic, the context of the project is in the mail > list we discussed before,which title is [DISCUSS]Hope to add the following > capabilities to APISIX. > copy some topics here: > ``` > Hope to add the following capabilities to APISIX > > 1. Config APISIX with yaml; > 2. Define the data structure to conform to the general behavior of the > gateway; > 3. Incremental update; > > Why do you want to do this? > 1. In order to facilitate the integration of k8s, use yaml to define > APISIX; > 2. For easier synchronization across clusters; > 3. Can be better adapted to multiple platforms (k8s, vm); > > ``` > > > Sheng Wu <[email protected]> 于2020年7月25日周六 下午4:39写道： > > > wei jin <[email protected]> 于2020年7月25日周六 上午10:49写道： > > > > > Hello, community, > > > I want to create a new project under APISIX, I have a few questions: > > > > > > 1. Are there any restrictions on project naming? Does the name have to > > > contain the keyword `apisix`? > > > > > > > I think in today's practice, INFRA keep apisix-* as the default repo > naming > > style. > > If you want another name, we may need to reach the INFRA team, the > > self-service platform requires this way AFAIK. > > > > And I want to second Ming Wen's question > > > > "Is this a newly developed project or a donation? What is the > relationship > > between this project and APISIX?" > > The shared doc seems a tech topic only, still, it is not clear about the > > context. > > > > > > > 2. How many ways do we name the project? > > >
