Currently, ​​Scaffold_CRM  Demo [1],Company Demo [2] and Seckill [3]  are
popular with users.
It is useful to create a sub project to host these demos before closing
ServiceComb organization.

​[1] https://github.com/zhengyangyong/scaffold
[2] https://github.com/ServiceComb/ServiceComb-Company-WorkShop
[3] https://github.com/ServiceComb/seckill


Best Wishes & Regards
-------------------------------
Mabin



Willem Jiang <[email protected]> 于2018年7月26日周四 上午8:06写道:

> ServiceComb-Company-WorkShop has some stuff relates to Huawei cloud, so we
> don't put it as a sub project as the Apache ServiceComb.
> If we have more demo project come out, we may consider to create sub
> project in Apache.
> For those demo or personal projects, we need to go through the donation
> process before we move them into Apache.
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Wed, Jul 25, 2018 at 10:20 PM, Zen Lin <[email protected]>
> wrote:
>
> > Summarize:
> > Scaffold_CRM  Demo [1], which shows how to use servicecomb scaffold to
> > develop a CRM application.
> > Company Demo [2], which shows how to use servicecomb to develop a
> ordinary
> > microservices application.
> > start.servicecomb.io,  which is the cold generator website of
> servicecomb.
> >
> > [1] https://github.com/zhengyangyong/scaffold
> > <https://github.com/zhengyangyong/scaffold>
> > [2] https://github.com/ServiceComb/ServiceComb-Company-WorkShop
> > [3] https://github.com/wangkirin/initializr
> >
> > Anymore?
> >
> > Hi Willem, JB,
> > We do not know how to keep these official demos and tools  in a Apache
> > project usually.
> > A centralized repository for Demos or tools? something like
> > https://github.com/apache/servicecomb-demos?
> >
> > Best Regards,
> > ---
> > Zen Lin
> > [email protected]
> > Focused on Micro Service and Apache ServiceComb
> >
> >
> > Jean-Baptiste Onofré <[email protected]> 于2018年7月25日周三 下午8:54写道:
> >
> > > Should not be on Apache gitbox ?
> > >
> > > Regards
> > > JB
> > >
> > > Le 25 juil. 2018 à 11:13, à 11:13, Willem Jiang <
> [email protected]>
> > > a écrit:
> > > >Yeah, we can just transfer the repo to another group.
> > > >If the user use the older URL to access the repo, github can redirect
> > > >the
> > > >request to the new transfer URL.
> > > >
> > > >
> > > >Willem Jiang
> > > >
> > > >Twitter: willemjiang
> > > >Weibo: 姜宁willem
> > > >
> > > >On Wed, Jul 25, 2018 at 4:47 PM, Yang Bo <[email protected]> wrote:
> > > >
> > > >> +1 for removing the ServiceComb organization.
> > > >>
> > > >> Some issues:
> > > >> The go-chassiss and related forked third parties are still hosted on
> > > >this
> > > >> group. We should migrate those first before closing.
> > > >>
> > > >>
> > > >> On Wed, Jul 25, 2018 at 4:45 PM Willem Jiang <
> [email protected]>
> > > >> wrote:
> > > >>
> > > >> > I think we just need to find a home for
> > > >> > https://github.com/ServiceComb/ServiceComb-Company-WorkShop
> > > >> >
> > > >> > huaweicse could be a way to go.
> > > >> >
> > > >> >
> > > >> > Willem Jiang
> > > >> >
> > > >> > Twitter: willemjiang
> > > >> > Weibo: 姜宁willem
> > > >> >
> > > >> > On Wed, Jul 25, 2018 at 4:25 PM, bismy <[email protected]> wrote:
> > > >> >
> > > >> > > +1.
> > > >> > > Does huawei has an organization to hosting these contents? Maybe
> > > >we can
> > > >> > > move them all there. And I have an organization to host
> temporary
> > > >> > contents.
> > > >> > > https://github.com/huaweicse
> > > >> > >
> > > >> > >
> > > >> > > ------------------ 原始邮件 ------------------
> > > >> > > 发件人: "Zen Lin"<[email protected]>;
> > > >> > > 发送时间: 2018年7月25日(星期三) 下午4:13
> > > >> > > 收件人: "dev"<[email protected]>;
> > > >> > > 抄送: "Xiaoliang Tian"<[email protected]>;
> > > >> > > 主题: 【Proposal】Close ServiceComb group on github
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > Hi Guys,
> > > >> > >
> > > >> > > As we known, Apache ServiceComb (incubating) is in the "Near
> > > >> Graduation"
> > > >> > > status.
> > > >> > > There still a ServiceComb group on the github [1], projects
> under
> > > >this
> > > >> > > group is not in the incubator scope of ServiceComb now, my
> > > >suggestion
> > > >> is
> > > >> > to
> > > >> > > close this group.
> > > >> > >
> > > >> > > I  have gone though the projects and find out the corresponding
> > > >> > maintainers
> > > >> > > , please transfer the project to other place but not
> ServiceComb,
> > > > as
> > > >> > > follows,
> > > >> > >
> > > >> > > Maintainer: Shawn
> > > >> > > https://github.com/ServiceComb/go-chassis
> > > >> > > <goog_637124993>
> > > >> > > https://github.com/ServiceComb/cse-collector
> > > >> > > <goog_637124993>
> > > >> > > https://github.com/ServiceComb/go-cc-client
> > > >> > > <goog_637124993>
> > > >> > > https://github.com/ServiceComb/go-archaius
> > > >> > > <goog_637124993>
> > > >> > > https://github.com/ServiceComb/go-sc-client
> > > >> > > <goog_637124993>
> > > >> > > https://github.com/ServiceComb/paas-lager
> > > >> > > <goog_637124993>
> > > >> > > https://github.com/ServiceComb/http-client
> > > >> > > <goog_637124993>
> > > >> > > https://github.com/ServiceComb/auth
> > > >> > >
> > > >> > > Maintainer: Willem
> > > >> > > https://github.com/ServiceComb/spring-cloud-servicecomb-plugins
> > > >> > > <goog_637124994>
> > > >> > > https://github.com/ServiceComb/seckill
> > > >> > > <goog_637124994>
> > > >> > > https://github.com/ServiceComb/incubator-servicecomb-website
> > > >> > >
> > > >> > > Maintainer: Asif
> > > >> > >
> > > >https://github.com/ServiceComb/incubator-servicecomb-service-center
> > > >> > >
> > > >> > > To the project below, it is a official demo of servicecomb, I am
> > > >not
> > > >> sure
> > > >> > > how to deal with this, any thoughts?
> > > >> > > https://github.com/ServiceComb/ServiceComb-Company-WorkShop
> > > >> > >
> > > >> > >
> > > >> > > [1] https://github.com/ServiceComb
> > > ><https://github.com/ServiceComb>
> > > >> > >
> > > >> > > Best Regards,
> > > >> > > ---
> > > >> > > Zen Lin
> > > >> > > [email protected]
> > > >> > > Focused on Micro Service and Apache ServiceComb
> > > >> > >
> > > >> >
> > > >>
> > > >>
> > > >> --
> > > >> Best Regards,
> > > >> Yang.
> > > >>
> > >
> >
>

Reply via email to