Hi Willem,

Thanks for your reply.

I will go through those documents and sign SGA (I already implemented it).

I will write a detailed design proposal and share it here.

Thank you,
Shiqi

On Thu, Jun 16, 2022 at 9:29 AM Willem Jiang <willem.ji...@gmail.com> wrote:

> Hi Shiqi
>
> Can you explain more detail about this project?
> It could be better if you can provide a design proposal for us to review.
> I think you can find a  the committer to help you review and merge the
> code.
>
> BTW, I’m not sure if you already wrote the code, if you do that you may
> need to sign a SGA first[1].
> If you do it from scratch, you may need to fill a iCLA[2] before submit
> any code to repo first.
> Anyway, please check out the contributor agreement[3] for more information.
>
> [1]https://www.apache.org/licenses/software-grant-template.pdf <
> https://www.apache.org/licenses/software-grant-template.pdf>
> [2]https://www.apache.org/licenses/icla.pdf <
> https://www.apache.org/licenses/icla.pdf>
> [3]https://www.apache.org/licenses/contributor-agreements.html <
> https://www.apache.org/licenses/contributor-agreements.html>
>
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> > On Jun 16, 2022, at 11:06, Frenqucy Hz <shiqiwang...@gmail.com> wrote:
> >
> > Hello all,
> >
> > I suggest creating a new project servicecomb-service-center-istio to
> > integrate servicecomb-service-center with istio, I will briefly introduce
> > why we are doing this project.
> >
> > *1. What is servicecomb-service-center-istio?*
> >
> >   - It's a tool that synchronizes servicecomb-service-center microservice
> >   registration information to Istio.
> >   - It enables the Istio service to discover microservices registered to
> >   servicecomb-service-center.
> >
> >
> > *2. Motivation?*
> >
> >
> >
> >   - Application Modernization customers who are migrating Microservices
> >   from the traditional Registry (servicecomb-service-center) to the
> Service
> >   Mesh (istio) have a high demand for this tool to break the
> communication
> >   barrier between two heterogeneous tech stacks which is caused by the
> >   different Registration and Discovery mechanisms.
> >   - Other communities (Nacos
> >   <https://github.com/alibaba/nacos/tree/develop/istio> and consul
> >   <https://github.com/aeraki-mesh/consul2istio>) already have this
> >   capability.
> >
> > Any ideas?
> >
> > Regards,
> > Shiqi
>
>

Reply via email to