sorry I answered wrong context!
I agree that there is much less collateral damage on a website repo redo.
If redoing that makes it easier let's go for it. If questions or concerns
arise later, I would offer to also help explain or defend the choice.
best,
-A
On Sun, 9 Sep 2018, 19:29 吴晟 Sheng Wu, <wu.sheng@foxmail.com> wrote:
> Oh, website repo shouldn't be problem. 😊
>
>
>
> Sheng Wu
> Apache SkyWalking
>
> From Wu Sheng 's phone.
>
>
> ------------------ Original ------------------
> From: Mick Semb Wever <mck@apache.org>
> Date: Mon,Sep 10,2018 7:26 AM
> To: dev <dev@zipkin.apache.org>
> Subject: Re: Moving Zipkin repositories from the openzipkin to apache
>
>
>
>
>
> > please don't re create the repos. it will drops all stars, followers etc.
> > many in the community spent years assembling it so I think it would be
> best
> > to try best to preserve especially as others have been able to. As a
> > historical note, years ago when we redid the server we also had pushback
> > about the same suggestion. That was back when Zipkin had a couple
> thousand
> > stars (it is now nearing 10k)
>
>
> Adrian, AFAIK Zoltan here has *only* been talking about the website repo:
> https://github.com/openzipkin/openzipkin.github.io
>
> All repos listed in INFRA-16989 will be transferred, not recreated.
>
> Mick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
> For additional commands, e-mail: dev-help@zipkin.apache.org
|