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