You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zipkin.apache.org by Zoltán Nagy <ab...@gmail.com> on 2018/09/07 09:01:09 UTC
Re: Moving Zipkin repositories from the openzipkin to apache
> The process here I do believe is that we'll need to add admin rights to
whomever from ASF infra picks up the ticket and then they will transfer the
repository to the apache github organisation. All history will be
maintained.
I can do that as well if Adrian is not available when that happens. Oh,
and, after checking
https://github.com/orgs/openzipkin/people?query=+role%3Aowner: so can you!
> Adrian, what about 'openzipkin/openzipkin.github.io' ?
> I believe the website is to be hosted on ASF infrastructure, which means
this repo will need to be transferred as well.
That's my understanding as well. Though, note: just moving the repo will
not be enough to get the site hosted on ASF infrastructure (unless some
super-smart ASF automation would somehow automatically pick it up); we'll
need to update ... something, probably
https://github.com/openzipkin/openzipkin.github.io/blob/master/.circleci/config.yml
to push the generated site to wherever it needs to go. I'm happy to do
that, especially if you can point me at relevant docs :)
Please note that moving 'openzipkin/openzipkin.github.io' out of the GitHub
openzipkin organization right now would break the site, as it's hosted
directly through GH Pages, so let's make sure the domain is redirected
before doing so. Speaking of, FTR: zipkin.io currently goes through
CloudFlare (for HTTPS). Shouldn't change the migration process, just good
to know to avoid confusion.
On Fri, Sep 7, 2018 at 9:51 AM Mick Semb Wever <mc...@apache.org> wrote:
> Per the Zipkin Proposal I've created the infra ticket to request moving
> the listed zipkin repositories from the openzipkin github organisation to
> the apache organisation.
>
> https://issues.apache.org/jira/browse/INFRA-16989
>
> The process here I do believe is that we'll need to add admin rights to
> whomever from ASF infra picks up the ticket and then they will transfer the
> repository to the apache github organisation. All history will be
> maintained.
>
> Speak up if there's anything wrong here!!
>
> Adrian, what about 'openzipkin/openzipkin.github.io' ?
> I believe the website is to be hosted on ASF infrastructure, which means
> this repo will need to be transferred as well.
> Zipkin.io will then point to where it's hosted, the same as skywalking.io
> -> skywalking.apache.org
>
> cheers,
> Mick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
> For additional commands, e-mail: dev-help@zipkin.apache.org
>
>
--
Zoltán Nagy
https://abesto.net
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by Adrian Cole <ad...@gmail.com>.
I will love to accept Zoltan's lead on helping ensure details are
sorted during the move especially the website as he knows where all
the things that should be somewhere are. I'm still a bit
distracted/cloudy (not as in amazon)... it is wonderful to have clear
minds on this.
Best,
-A
On Fri, Sep 7, 2018 at 5:01 AM Zoltán Nagy <ab...@gmail.com> wrote:
>
> > The process here I do believe is that we'll need to add admin rights to
> whomever from ASF infra picks up the ticket and then they will transfer the
> repository to the apache github organisation. All history will be
> maintained.
> I can do that as well if Adrian is not available when that happens. Oh,
> and, after checking
> https://github.com/orgs/openzipkin/people?query=+role%3Aowner: so can you!
>
> > Adrian, what about 'openzipkin/openzipkin.github.io' ?
> > I believe the website is to be hosted on ASF infrastructure, which means
> this repo will need to be transferred as well.
> That's my understanding as well. Though, note: just moving the repo will
> not be enough to get the site hosted on ASF infrastructure (unless some
> super-smart ASF automation would somehow automatically pick it up); we'll
> need to update ... something, probably
> https://github.com/openzipkin/openzipkin.github.io/blob/master/.circleci/config.yml
> to push the generated site to wherever it needs to go. I'm happy to do
> that, especially if you can point me at relevant docs :)
>
> Please note that moving 'openzipkin/openzipkin.github.io' out of the GitHub
> openzipkin organization right now would break the site, as it's hosted
> directly through GH Pages, so let's make sure the domain is redirected
> before doing so. Speaking of, FTR: zipkin.io currently goes through
> CloudFlare (for HTTPS). Shouldn't change the migration process, just good
> to know to avoid confusion.
>
> On Fri, Sep 7, 2018 at 9:51 AM Mick Semb Wever <mc...@apache.org> wrote:
>
> > Per the Zipkin Proposal I've created the infra ticket to request moving
> > the listed zipkin repositories from the openzipkin github organisation to
> > the apache organisation.
> >
> > https://issues.apache.org/jira/browse/INFRA-16989
> >
> > The process here I do believe is that we'll need to add admin rights to
> > whomever from ASF infra picks up the ticket and then they will transfer the
> > repository to the apache github organisation. All history will be
> > maintained.
> >
> > Speak up if there's anything wrong here!!
> >
> > Adrian, what about 'openzipkin/openzipkin.github.io' ?
> > I believe the website is to be hosted on ASF infrastructure, which means
> > this repo will need to be transferred as well.
> > Zipkin.io will then point to where it's hosted, the same as skywalking.io
> > -> skywalking.apache.org
> >
> > cheers,
> > Mick
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
> > For additional commands, e-mail: dev-help@zipkin.apache.org
> >
> >
>
> --
> Zoltán Nagy
> https://abesto.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
For additional commands, e-mail: dev-help@zipkin.apache.org
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by Willem Jiang <wi...@gmail.com>.
I think it should be fine for the website. There are only 20+ start there.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Mon, Sep 10, 2018 at 7:14 AM Adrian Cole <ad...@gmail.com> wrote:
>
> 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)
>
> -A
>
> On Sun, 9 Sep 2018, 17:55 Mick Semb Wever, <mc...@apache.org> wrote:
>
> >
> > > This means the next step is the actual migration. Looking for any strong
> > > +1s or -1s on creating a new repo (and copying any issues) to save on
> > > migration overhead.
> > > Let's try something new: if not vetoed in 48 hours, I'll go ahead with
> > this
> > > plan. Will do it sooner given +1s.
> >
> >
> > Pushing _everything_ from the existing repo into the new repo should not
> > be a problem.
> >
> >
> > > Any idea how we're doing wrt. expected timelines moving onto ASF infra?
> > Are
> > > we in a hurry?
> >
> >
> > They have a work queue, they get to it when they can.
> > Usually within a week.
> >
> > Mick
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
> > For additional commands, e-mail: dev-help@zipkin.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
For additional commands, e-mail: dev-help@zipkin.apache.org
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by Adrian Cole <ad...@gmail.com>.
Agree redirects should work, but we should also update them :P Also
good with the names.
On Sun, Sep 9, 2018 at 11:22 PM 吴晟 Sheng Wu <wu...@foxmail.com> wrote:
>
> Hi Reja
>
>
> AFAIK, the repositories transform is pretty safe, the link redirect will be supported automatically by GitHub.
>
>
> We will have enough time to fix them. as long as we don't create the repository in same name insider Zipkin repo. I doubt that will happen, right?
>
>
> ------------------
> Sheng Wu
> Apache SkyWalking
>
>
>
>
>
>
>
> ------------------ Original ------------------
> From: "Raja Sundaram Ganesan"<su...@gmail.com>;
> Date: Mon, Sep 10, 2018 11:07 AM
> To: "dev"<de...@zipkin.apache.org>;
>
> Subject: Re: Moving Zipkin repositories from the openzipkin to apache
>
>
>
> The new names meaningful. Great. After moving the repositories we may have
> to update the links in the documents so that it doesn't point to old
> repositories.
>
> -Regards
> Raja
>
> On Mon, Sep 10, 2018 at 9:21 AM Mick Semb Wever <mc...@apache.org> wrote:
>
> > > another choice could be to go with a -docker suffix. it is slightly more
> > > mechanical to "bash" around when there is a matching convention. for
> > > example zipkin -> zipkin-docker or zipkin-dependencies ->
> > > zipkin-dependencies-docker.
> >
> > Cool. That would make it:
> >
> >
> > incubator-zipkin
> > incubator-zipkin-docker
> > incubator-zipkin-dependencies
> > incubator-zipkin-dependencies-docker
> > incubator-zipkin-api
> > incubator-zipkin-b3-propagation
> > incubator-zipkin-reporter-java
> > incubator-zipkin-aws
> > incubator-zipkin-aws-docker
> > incubator-zipkin-azure
> > incubator-zipkin-azure-docker
> > incubator-zipkin-gcp
> > incubator-zipkin-gcp-docker
> >
> > incubator-zipkin-brave
> > incubator-zipkin-brave-cassandra
> > incubator-zipkin-brave-karaf
> >
> > incubator-zipkin-docker-jre-full
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
> > For additional commands, e-mail: dev-help@zipkin.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
For additional commands, e-mail: dev-help@zipkin.apache.org
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by Zoltán Nagy <ab...@apache.org>.
Coolness! I'm +1 for the new repo names. Thanks for opening those issues, Mick!
Indeed as Sheng Wu says, GH sets up redirects for moved repos (but not
their GH Pages). More on this:
https://help.github.com/articles/about-repository-transfers/
Thanks for the +1s on the website migration. Jira ticket is open,
includes asking ASF Infra folks for advice:
https://issues.apache.org/jira/browse/INFRA-16996. A GH issue seems
like a good way to raise awareness and get any input from the
community, so I also opened
https://github.com/openzipkin/openzipkin.github.io/issues/116.
On Mon, Sep 10, 2018 at 5:22 AM 吴晟 Sheng Wu <wu...@foxmail.com> wrote:
>
> Hi Reja
>
>
> AFAIK, the repositories transform is pretty safe, the link redirect will be supported automatically by GitHub.
>
>
> We will have enough time to fix them. as long as we don't create the repository in same name insider Zipkin repo. I doubt that will happen, right?
>
>
> ------------------
> Sheng Wu
> Apache SkyWalking
>
>
>
>
>
>
>
> ------------------ Original ------------------
> From: "Raja Sundaram Ganesan"<su...@gmail.com>;
> Date: Mon, Sep 10, 2018 11:07 AM
> To: "dev"<de...@zipkin.apache.org>;
>
> Subject: Re: Moving Zipkin repositories from the openzipkin to apache
>
>
>
> The new names meaningful. Great. After moving the repositories we may have
> to update the links in the documents so that it doesn't point to old
> repositories.
>
> -Regards
> Raja
>
> On Mon, Sep 10, 2018 at 9:21 AM Mick Semb Wever <mc...@apache.org> wrote:
>
> > > another choice could be to go with a -docker suffix. it is slightly more
> > > mechanical to "bash" around when there is a matching convention. for
> > > example zipkin -> zipkin-docker or zipkin-dependencies ->
> > > zipkin-dependencies-docker.
> >
> > Cool. That would make it:
> >
> >
> > incubator-zipkin
> > incubator-zipkin-docker
> > incubator-zipkin-dependencies
> > incubator-zipkin-dependencies-docker
> > incubator-zipkin-api
> > incubator-zipkin-b3-propagation
> > incubator-zipkin-reporter-java
> > incubator-zipkin-aws
> > incubator-zipkin-aws-docker
> > incubator-zipkin-azure
> > incubator-zipkin-azure-docker
> > incubator-zipkin-gcp
> > incubator-zipkin-gcp-docker
> >
> > incubator-zipkin-brave
> > incubator-zipkin-brave-cassandra
> > incubator-zipkin-brave-karaf
> >
> > incubator-zipkin-docker-jre-full
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
> > For additional commands, e-mail: dev-help@zipkin.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
For additional commands, e-mail: dev-help@zipkin.apache.org
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by 吴晟 Sheng Wu <wu...@foxmail.com>.
Hi Reja
AFAIK, the repositories transform is pretty safe, the link redirect will be supported automatically by GitHub.
We will have enough time to fix them. as long as we don't create the repository in same name insider Zipkin repo. I doubt that will happen, right?
------------------
Sheng Wu
Apache SkyWalking
------------------ Original ------------------
From: "Raja Sundaram Ganesan"<su...@gmail.com>;
Date: Mon, Sep 10, 2018 11:07 AM
To: "dev"<de...@zipkin.apache.org>;
Subject: Re: Moving Zipkin repositories from the openzipkin to apache
The new names meaningful. Great. After moving the repositories we may have
to update the links in the documents so that it doesn't point to old
repositories.
-Regards
Raja
On Mon, Sep 10, 2018 at 9:21 AM Mick Semb Wever <mc...@apache.org> wrote:
> > another choice could be to go with a -docker suffix. it is slightly more
> > mechanical to "bash" around when there is a matching convention. for
> > example zipkin -> zipkin-docker or zipkin-dependencies ->
> > zipkin-dependencies-docker.
>
> Cool. That would make it:
>
>
> incubator-zipkin
> incubator-zipkin-docker
> incubator-zipkin-dependencies
> incubator-zipkin-dependencies-docker
> incubator-zipkin-api
> incubator-zipkin-b3-propagation
> incubator-zipkin-reporter-java
> incubator-zipkin-aws
> incubator-zipkin-aws-docker
> incubator-zipkin-azure
> incubator-zipkin-azure-docker
> incubator-zipkin-gcp
> incubator-zipkin-gcp-docker
>
> incubator-zipkin-brave
> incubator-zipkin-brave-cassandra
> incubator-zipkin-brave-karaf
>
> incubator-zipkin-docker-jre-full
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
> For additional commands, e-mail: dev-help@zipkin.apache.org
>
>
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by Raja Sundaram Ganesan <su...@gmail.com>.
The new names meaningful. Great. After moving the repositories we may have
to update the links in the documents so that it doesn't point to old
repositories.
-Regards
Raja
On Mon, Sep 10, 2018 at 9:21 AM Mick Semb Wever <mc...@apache.org> wrote:
> > another choice could be to go with a -docker suffix. it is slightly more
> > mechanical to "bash" around when there is a matching convention. for
> > example zipkin -> zipkin-docker or zipkin-dependencies ->
> > zipkin-dependencies-docker.
>
> Cool. That would make it:
>
>
> incubator-zipkin
> incubator-zipkin-docker
> incubator-zipkin-dependencies
> incubator-zipkin-dependencies-docker
> incubator-zipkin-api
> incubator-zipkin-b3-propagation
> incubator-zipkin-reporter-java
> incubator-zipkin-aws
> incubator-zipkin-aws-docker
> incubator-zipkin-azure
> incubator-zipkin-azure-docker
> incubator-zipkin-gcp
> incubator-zipkin-gcp-docker
>
> incubator-zipkin-brave
> incubator-zipkin-brave-cassandra
> incubator-zipkin-brave-karaf
>
> incubator-zipkin-docker-jre-full
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
> For additional commands, e-mail: dev-help@zipkin.apache.org
>
>
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by Mick Semb Wever <mc...@apache.org>.
> another choice could be to go with a -docker suffix. it is slightly more
> mechanical to "bash" around when there is a matching convention. for
> example zipkin -> zipkin-docker or zipkin-dependencies ->
> zipkin-dependencies-docker.
Cool. That would make it:
incubator-zipkin
incubator-zipkin-docker
incubator-zipkin-dependencies
incubator-zipkin-dependencies-docker
incubator-zipkin-api
incubator-zipkin-b3-propagation
incubator-zipkin-reporter-java
incubator-zipkin-aws
incubator-zipkin-aws-docker
incubator-zipkin-azure
incubator-zipkin-azure-docker
incubator-zipkin-gcp
incubator-zipkin-gcp-docker
incubator-zipkin-brave
incubator-zipkin-brave-cassandra
incubator-zipkin-brave-karaf
incubator-zipkin-docker-jre-full
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
For additional commands, e-mail: dev-help@zipkin.apache.org
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by Adrian Cole <ad...@gmail.com>.
another choice could be to go with a -docker suffix. it is slightly more
mechanical to "bash" around when there is a matching convention. for
example zipkin -> zipkin-docker or zipkin-dependencies ->
zipkin-dependencies-docker. Basically, this ends up requiring no thinking
when updating something... just look for the repo that ends in -docker and
update that.
-A
On Sun, 9 Sep 2018, 20:20 Adrian Cole, <ad...@gmail.com> wrote:
> The docker-x prefix was a helpful convention but I can see how the
> repetition would be distracting. I am fine with the names you mentioned.
>
> -A
>
> On Sun, 9 Sep 2018, 19:51 Mick Semb Wever, <mc...@apache.org> wrote:
>
>>
>> > Because the repositories will need to be renamed to have a `incubator-
>> > zipkin` prefix, some of them will end up with clumsy names, like
>> > `incubator-zipkin-docker-zipkin`. It would be great if we find better
>> > names now for those.
>>
>> I suspect that all that needs to be done to clean up the repository names
>> is to ensure `zipkin` doesn't appear twice in the name.
>> That would be the list:
>>
>> incubator-zipkin
>> incubator-zipkin-dependencies
>> incubator-zipkin-api
>> incubator-zipkin-b3-propagation
>> incubator-zipkin-reporter-java
>> incubator-zipkin-aws
>> incubator-zipkin-azure
>> incubator-zipkin-gcp
>>
>> incubator-zipkin-brave
>> incubator-zipkin-brave-cassandra
>> incubator-zipkin-brave-karaf
>>
>> incubator-zipkin-docker
>> incubator-zipkin-docker-dependencies
>> incubator-zipkin-docker-gcp
>> incubator-zipkin-docker-azure
>> incubator-zipkin-docker-aws
>> incubator-zipkin-docker-jre-full
>>
>>
>> What do folk think?
>>
>> Mick
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
>> For additional commands, e-mail: dev-help@zipkin.apache.org
>>
>>
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by Adrian Cole <ad...@gmail.com>.
The docker-x prefix was a helpful convention but I can see how the
repetition would be distracting. I am fine with the names you mentioned.
-A
On Sun, 9 Sep 2018, 19:51 Mick Semb Wever, <mc...@apache.org> wrote:
>
> > Because the repositories will need to be renamed to have a `incubator-
> > zipkin` prefix, some of them will end up with clumsy names, like
> > `incubator-zipkin-docker-zipkin`. It would be great if we find better
> > names now for those.
>
> I suspect that all that needs to be done to clean up the repository names
> is to ensure `zipkin` doesn't appear twice in the name.
> That would be the list:
>
> incubator-zipkin
> incubator-zipkin-dependencies
> incubator-zipkin-api
> incubator-zipkin-b3-propagation
> incubator-zipkin-reporter-java
> incubator-zipkin-aws
> incubator-zipkin-azure
> incubator-zipkin-gcp
>
> incubator-zipkin-brave
> incubator-zipkin-brave-cassandra
> incubator-zipkin-brave-karaf
>
> incubator-zipkin-docker
> incubator-zipkin-docker-dependencies
> incubator-zipkin-docker-gcp
> incubator-zipkin-docker-azure
> incubator-zipkin-docker-aws
> incubator-zipkin-docker-jre-full
>
>
> What do folk think?
>
> Mick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
> For additional commands, e-mail: dev-help@zipkin.apache.org
>
>
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by 吴晟 Sheng Wu <wu...@foxmail.com>.
LGTM
Sheng Wu
Apache SkyWalking
From Wu Sheng 's phone.
------------------ Original ------------------
From: Mick Semb Wever <mc...@apache.org>
Date: Mon,Sep 10,2018 7:51 AM
To: dev <de...@zipkin.apache.org>
Subject: Re: Moving Zipkin repositories from the openzipkin to apache
> Because the repositories will need to be renamed to have a `incubator-
> zipkin` prefix, some of them will end up with clumsy names, like
> `incubator-zipkin-docker-zipkin`. It would be great if we find better
> names now for those.
I suspect that all that needs to be done to clean up the repository names is to ensure `zipkin` doesn't appear twice in the name.
That would be the list:
incubator-zipkin
incubator-zipkin-dependencies
incubator-zipkin-api
incubator-zipkin-b3-propagation
incubator-zipkin-reporter-java
incubator-zipkin-aws
incubator-zipkin-azure
incubator-zipkin-gcp
incubator-zipkin-brave
incubator-zipkin-brave-cassandra
incubator-zipkin-brave-karaf
incubator-zipkin-docker
incubator-zipkin-docker-dependencies
incubator-zipkin-docker-gcp
incubator-zipkin-docker-azure
incubator-zipkin-docker-aws
incubator-zipkin-docker-jre-full
What do folk think?
Mick
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
For additional commands, e-mail: dev-help@zipkin.apache.org
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by Mick Semb Wever <mc...@apache.org>.
> Because the repositories will need to be renamed to have a `incubator-
> zipkin` prefix, some of them will end up with clumsy names, like
> `incubator-zipkin-docker-zipkin`. It would be great if we find better
> names now for those.
I suspect that all that needs to be done to clean up the repository names is to ensure `zipkin` doesn't appear twice in the name.
That would be the list:
incubator-zipkin
incubator-zipkin-dependencies
incubator-zipkin-api
incubator-zipkin-b3-propagation
incubator-zipkin-reporter-java
incubator-zipkin-aws
incubator-zipkin-azure
incubator-zipkin-gcp
incubator-zipkin-brave
incubator-zipkin-brave-cassandra
incubator-zipkin-brave-karaf
incubator-zipkin-docker
incubator-zipkin-docker-dependencies
incubator-zipkin-docker-gcp
incubator-zipkin-docker-azure
incubator-zipkin-docker-aws
incubator-zipkin-docker-jre-full
What do folk think?
Mick
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
For additional commands, e-mail: dev-help@zipkin.apache.org
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by Mick Semb Wever <mc...@apache.org>.
> All repos listed in INFRA-16989 will be transferred, not recreated.
Issues have been created in each repository informing of the pending transfer.
Because the repositories will need to be renamed to have a `incubator-zipkin` prefix, some of them will end up with clumsy names, like `incubator-zipkin-docker-zipkin`. It would be great if we find better names now for those.
incubator-zipkin:
https://github.com/openzipkin/zipkin/issues/2187
incubator-zipkin-dependencies:
https://github.com/openzipkin/zipkin-dependencies/issues/113
incubator-zipkin-api:
https://github.com/openzipkin/zipkin-api/issues/53
incubator-zipkin-b3-propagation:
https://github.com/openzipkin/b3-propagation/issues/25
incubator-zipkin-docker-zipkin:
https://github.com/openzipkin/docker-zipkin/issues/189
incubator-zipkin-docker-zipkin-dependencies:
https://github.com/openzipkin/docker-zipkin-dependencies/issues/13
incubator-zipkin-reporter-java:
https://github.com/openzipkin/zipkin-reporter-java/issues/122
incubator-zipkin-brave:
https://github.com/openzipkin/brave/issues/782
incubator-zipkin-aws:
https://github.com/openzipkin/zipkin-aws/issues/107
incubator-zipkin-docker-zipkin-aws:
https://github.com/openzipkin/docker-zipkin-aws/issues/6
incubator-zipkin-azure:
https://github.com/openzipkin/zipkin-azure/issues/52
incubator-zipkin-docker-zipkin-azure:
https://github.com/openzipkin/docker-zipkin-azure/issues/6
incubator-zipkin-gcp:
https://github.com/openzipkin/zipkin-gcp/issues/95
incubator-zipkin-docker-zipkin-gcp:
https://github.com/openzipkin/docker-zipkin-gcp/issues/4
incubator-zipkin-brave-cassandra:
https://github.com/openzipkin/brave-cassandra/issues/15
incubator-zipkin-docker-jre-full:
https://github.com/openzipkin/docker-jre-full/issues/10
incubator-zipkin-brave-karaf:
https://github.com/openzipkin/brave-karaf/issues/7
Mick
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
For additional commands, e-mail: dev-help@zipkin.apache.org
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by Adrian Cole <ad...@gmail.com>.
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...@foxmail.com> wrote:
> Oh, website repo shouldn't be problem. 😊
>
>
>
> Sheng Wu
> Apache SkyWalking
>
> From Wu Sheng 's phone.
>
>
> ------------------ Original ------------------
> From: Mick Semb Wever <mc...@apache.org>
> Date: Mon,Sep 10,2018 7:26 AM
> To: dev <de...@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
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by 吴晟 Sheng Wu <wu...@foxmail.com>.
Oh, website repo shouldn't be problem. 😊
Sheng Wu
Apache SkyWalking
From Wu Sheng 's phone.
------------------ Original ------------------
From: Mick Semb Wever <mc...@apache.org>
Date: Mon,Sep 10,2018 7:26 AM
To: dev <de...@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
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by Mick Semb Wever <mc...@apache.org>.
> 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
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by 吴晟 Sheng Wu <wu...@foxmail.com>.
+1 on this. Star can't represent the good or bad of a project, we all know what i am referring, but new incoming users sometimes focus on this, and judge project by this.
Also, 10k stars is an exciting thing for me, I assume it is to others.
Just simpling submit JIRA ticket to Infra team, ask for repo transform.
Need I do that? Adrian, Mick.
Sheng Wu
Apache SkyWalking
From Wu Sheng 's phone.
------------------ Original ------------------
From: Adrian Cole <ad...@gmail.com>
Date: Mon,Sep 10,2018 7:14 AM
To: dev <de...@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)
-A
On Sun, 9 Sep 2018, 17:55 Mick Semb Wever, <mc...@apache.org> wrote:
>
> > This means the next step is the actual migration. Looking for any strong
> > +1s or -1s on creating a new repo (and copying any issues) to save on
> > migration overhead.
> > Let's try something new: if not vetoed in 48 hours, I'll go ahead with
> this
> > plan. Will do it sooner given +1s.
>
>
> Pushing _everything_ from the existing repo into the new repo should not
> be a problem.
>
>
> > Any idea how we're doing wrt. expected timelines moving onto ASF infra?
> Are
> > we in a hurry?
>
>
> They have a work queue, they get to it when they can.
> Usually within a week.
>
> Mick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
> For additional commands, e-mail: dev-help@zipkin.apache.org
>
>
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by Adrian Cole <ad...@gmail.com>.
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)
-A
On Sun, 9 Sep 2018, 17:55 Mick Semb Wever, <mc...@apache.org> wrote:
>
> > This means the next step is the actual migration. Looking for any strong
> > +1s or -1s on creating a new repo (and copying any issues) to save on
> > migration overhead.
> > Let's try something new: if not vetoed in 48 hours, I'll go ahead with
> this
> > plan. Will do it sooner given +1s.
>
>
> Pushing _everything_ from the existing repo into the new repo should not
> be a problem.
>
>
> > Any idea how we're doing wrt. expected timelines moving onto ASF infra?
> Are
> > we in a hurry?
>
>
> They have a work queue, they get to it when they can.
> Usually within a week.
>
> Mick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
> For additional commands, e-mail: dev-help@zipkin.apache.org
>
>
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by Mick Semb Wever <mc...@apache.org>.
> This means the next step is the actual migration. Looking for any strong
> +1s or -1s on creating a new repo (and copying any issues) to save on
> migration overhead.
> Let's try something new: if not vetoed in 48 hours, I'll go ahead with this
> plan. Will do it sooner given +1s.
Pushing _everything_ from the existing repo into the new repo should not be a problem.
> Any idea how we're doing wrt. expected timelines moving onto ASF infra? Are
> we in a hurry?
They have a work queue, they get to it when they can.
Usually within a week.
Mick
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
For additional commands, e-mail: dev-help@zipkin.apache.org
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by Zoltán Nagy <ab...@apache.org>.
Update:
https://github.com/openzipkin/openzipkin.github.io/blob/master/.circleci/update-asf-site.sh
should take care of generating the site and updating the `asf-site` branch.
The output is in
https://github.com/openzipkin/openzipkin.github.io/tree/asf-site, seems to
be fine. Automation will need push access to the repo; I'll post-pone
configuring that until the new repo is up to save on duplicate effort.
This means the next step is the actual migration. Looking for any strong
+1s or -1s on creating a new repo (and copying any issues) to save on
migration overhead.
Let's try something new: if not vetoed in 48 hours, I'll go ahead with this
plan. Will do it sooner given +1s.
Any idea how we're doing wrt. expected timelines moving onto ASF infra? Are
we in a hurry?
On Sun, Sep 9, 2018 at 10:14 PM Zoltán Nagy <ab...@apache.org> wrote:
> That may improve things, depending on how exactly we lay out the migration
> process. At the same time, I feel like the complexity of the migration is
> getting out of hand; at this point I'd propose creating a brand-new
> repository instead (which apparently can be done at least semi-self-service
> via https://gitbox.apache.org/setup/newrepo.html). This can be a good
> opportunity to triage the open issues, close invalid ones, and migrate
> (copy, referencing the original) ones we want to keep.
>
> Not to mention: while GH Pages takes care of generating HTML from the
> markdown in the repo, there's no ASF-standard automation for that. This
> needs to be created no matter what, so I'll get started on updating the
> existing Circle CI job to generate the site into a new `asf-site` branch
> (which seems to be the convention).
>
> In the meanwhile, I'm open to being convinced that dropping the current GH
> issues is a no-go, and we should invest in a more complex migration or
> accept some hours of down-time.
> (I've checked on the Jira ticket asking to move the other repos at
> https://issues.apache.org/jira/browse/INFRA-16989, is still in “waiting
> for infra” status. Not planning any action on this.)
>
> On Sat, Sep 8, 2018 at 4:04 AM Willem Jiang <wi...@gmail.com>
> wrote:
>
>> We could add a redirect of zipkin.io to zipkin.incubator.apache.org
>> once the Apache site is online.
>> Then we can move the openzipkin.github.io as we want.
>>
>> Willem Jiang
>>
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>> On Fri, Sep 7, 2018 at 11:53 PM Zoltán Nagy <ab...@gmail.com> wrote:
>> >
>> > Ah, I was missing the bit on git pub automatically updating the website
>> > from the repo. In that case yes, the plan you outlined seems best. The
>> only
>> > thing to keep an eye out for is to make sure that the website doesn't
>> break
>> > (too long, at least) during the migration of the repo. Specifically:
>> >
>> > - Create ASF website repo
>> > - Push current git history to ASF website repo, triggering upload of
>> the
>> > website to ASF hosting
>> > - Switch zipkin.io to the ASF-hosted site
>> > - Delete the ASF website repo
>> > - *At this point, if automation tries to update the website from the
>> > repo, depending on how things are implemented, the website might go
>> blank*
>> > - Move and rename `openzipkin/openzipkin.github.io` to be the ASF
>> > website repo
>> >
>> > We need that extra complexity to keep the issues tracked on the repo.
>> If we
>> > didn't need that, we could just push the commit history, archive the old
>> > repo, switch the DNS, and call it a day.
>> >
>> > My ICLA is still pending processing from ASF, so hands currently tied
>> > behind my back. I'm happy to collaborate on doing this if it's urgent,
>> or
>> > do the whole thing myself once my account is ready.
>> >
>> > On Fri, Sep 7, 2018 at 5:28 PM Willem Jiang <wi...@gmail.com>
>> wrote:
>> >
>> > > Apache is using the git pub to manage the website, we just need to
>> > > keep generated website updated.
>> > > I think we can create a site repo first, then just publish the
>> > > generated website there and keep 'openzipkin/openzipkin.github.io'
>> for
>> > > a while.
>> > > In this way, we can still us the Github GH pages as a back up, once
>> > > the apache website is online we can consider to move
>> > > 'openzipkin/openzipkin.github.io'
>> > >
>> > > Any thought?
>> > >
>> > > Willem Jiang
>> > >
>> > > Twitter: willemjiang
>> > > Weibo: 姜宁willem
>> > > On Fri, Sep 7, 2018 at 5:01 PM Zoltán Nagy <ab...@gmail.com> wrote:
>> > > >
>> > > > > The process here I do believe is that we'll need to add admin
>> rights to
>> > > > whomever from ASF infra picks up the ticket and then they will
>> transfer
>> > > the
>> > > > repository to the apache github organisation. All history will be
>> > > > maintained.
>> > > > I can do that as well if Adrian is not available when that happens.
>> Oh,
>> > > > and, after checking
>> > > > https://github.com/orgs/openzipkin/people?query=+role%3Aowner: so
>> can
>> > > you!
>> > > >
>> > > > > Adrian, what about 'openzipkin/openzipkin.github.io' ?
>> > > > > I believe the website is to be hosted on ASF infrastructure, which
>> > > means
>> > > > this repo will need to be transferred as well.
>> > > > That's my understanding as well. Though, note: just moving the repo
>> will
>> > > > not be enough to get the site hosted on ASF infrastructure (unless
>> some
>> > > > super-smart ASF automation would somehow automatically pick it up);
>> > > we'll
>> > > > need to update ... something, probably
>> > > >
>> > >
>> https://github.com/openzipkin/openzipkin.github.io/blob/master/.circleci/config.yml
>> > > > to push the generated site to wherever it needs to go. I'm happy to
>> do
>> > > > that, especially if you can point me at relevant docs :)
>> > > >
>> > > > Please note that moving 'openzipkin/openzipkin.github.io' out of
>> the
>> > > GitHub
>> > > > openzipkin organization right now would break the site, as it's
>> hosted
>> > > > directly through GH Pages, so let's make sure the domain is
>> redirected
>> > > > before doing so. Speaking of, FTR: zipkin.io currently goes through
>> > > > CloudFlare (for HTTPS). Shouldn't change the migration process,
>> just good
>> > > > to know to avoid confusion.
>> > > >
>> > > > On Fri, Sep 7, 2018 at 9:51 AM Mick Semb Wever <mc...@apache.org>
>> wrote:
>> > > >
>> > > > > Per the Zipkin Proposal I've created the infra ticket to request
>> moving
>> > > > > the listed zipkin repositories from the openzipkin github
>> organisation
>> > > to
>> > > > > the apache organisation.
>> > > > >
>> > > > > https://issues.apache.org/jira/browse/INFRA-16989
>> > > > >
>> > > > > The process here I do believe is that we'll need to add admin
>> rights to
>> > > > > whomever from ASF infra picks up the ticket and then they will
>> > > transfer the
>> > > > > repository to the apache github organisation. All history will be
>> > > > > maintained.
>> > > > >
>> > > > > Speak up if there's anything wrong here!!
>> > > > >
>> > > > > Adrian, what about 'openzipkin/openzipkin.github.io' ?
>> > > > > I believe the website is to be hosted on ASF infrastructure, which
>> > > means
>> > > > > this repo will need to be transferred as well.
>> > > > > Zipkin.io will then point to where it's hosted, the same as
>> > > skywalking.io
>> > > > > -> skywalking.apache.org
>> > > > >
>> > > > > cheers,
>> > > > > Mick
>> > > > >
>> > > > >
>> ---------------------------------------------------------------------
>> > > > > To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
>> > > > > For additional commands, e-mail: dev-help@zipkin.apache.org
>> > > > >
>> > > > >
>> > > >
>> > > > --
>> > > > Zoltán Nagy
>> > > > https://abesto.net
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
>> > > For additional commands, e-mail: dev-help@zipkin.apache.org
>> > >
>> > >
>> >
>> > --
>> > Zoltán Nagy
>> > https://abesto.net
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
>> For additional commands, e-mail: dev-help@zipkin.apache.org
>>
>>
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by Zoltán Nagy <ab...@apache.org>.
That may improve things, depending on how exactly we lay out the migration
process. At the same time, I feel like the complexity of the migration is
getting out of hand; at this point I'd propose creating a brand-new
repository instead (which apparently can be done at least semi-self-service
via https://gitbox.apache.org/setup/newrepo.html). This can be a good
opportunity to triage the open issues, close invalid ones, and migrate
(copy, referencing the original) ones we want to keep.
Not to mention: while GH Pages takes care of generating HTML from the
markdown in the repo, there's no ASF-standard automation for that. This
needs to be created no matter what, so I'll get started on updating the
existing Circle CI job to generate the site into a new `asf-site` branch
(which seems to be the convention).
In the meanwhile, I'm open to being convinced that dropping the current GH
issues is a no-go, and we should invest in a more complex migration or
accept some hours of down-time.
(I've checked on the Jira ticket asking to move the other repos at
https://issues.apache.org/jira/browse/INFRA-16989, is still in “waiting for
infra” status. Not planning any action on this.)
On Sat, Sep 8, 2018 at 4:04 AM Willem Jiang <wi...@gmail.com> wrote:
> We could add a redirect of zipkin.io to zipkin.incubator.apache.org
> once the Apache site is online.
> Then we can move the openzipkin.github.io as we want.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
> On Fri, Sep 7, 2018 at 11:53 PM Zoltán Nagy <ab...@gmail.com> wrote:
> >
> > Ah, I was missing the bit on git pub automatically updating the website
> > from the repo. In that case yes, the plan you outlined seems best. The
> only
> > thing to keep an eye out for is to make sure that the website doesn't
> break
> > (too long, at least) during the migration of the repo. Specifically:
> >
> > - Create ASF website repo
> > - Push current git history to ASF website repo, triggering upload of
> the
> > website to ASF hosting
> > - Switch zipkin.io to the ASF-hosted site
> > - Delete the ASF website repo
> > - *At this point, if automation tries to update the website from the
> > repo, depending on how things are implemented, the website might go
> blank*
> > - Move and rename `openzipkin/openzipkin.github.io` to be the ASF
> > website repo
> >
> > We need that extra complexity to keep the issues tracked on the repo. If
> we
> > didn't need that, we could just push the commit history, archive the old
> > repo, switch the DNS, and call it a day.
> >
> > My ICLA is still pending processing from ASF, so hands currently tied
> > behind my back. I'm happy to collaborate on doing this if it's urgent, or
> > do the whole thing myself once my account is ready.
> >
> > On Fri, Sep 7, 2018 at 5:28 PM Willem Jiang <wi...@gmail.com>
> wrote:
> >
> > > Apache is using the git pub to manage the website, we just need to
> > > keep generated website updated.
> > > I think we can create a site repo first, then just publish the
> > > generated website there and keep 'openzipkin/openzipkin.github.io' for
> > > a while.
> > > In this way, we can still us the Github GH pages as a back up, once
> > > the apache website is online we can consider to move
> > > 'openzipkin/openzipkin.github.io'
> > >
> > > Any thought?
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > > On Fri, Sep 7, 2018 at 5:01 PM Zoltán Nagy <ab...@gmail.com> wrote:
> > > >
> > > > > The process here I do believe is that we'll need to add admin
> rights to
> > > > whomever from ASF infra picks up the ticket and then they will
> transfer
> > > the
> > > > repository to the apache github organisation. All history will be
> > > > maintained.
> > > > I can do that as well if Adrian is not available when that happens.
> Oh,
> > > > and, after checking
> > > > https://github.com/orgs/openzipkin/people?query=+role%3Aowner: so
> can
> > > you!
> > > >
> > > > > Adrian, what about 'openzipkin/openzipkin.github.io' ?
> > > > > I believe the website is to be hosted on ASF infrastructure, which
> > > means
> > > > this repo will need to be transferred as well.
> > > > That's my understanding as well. Though, note: just moving the repo
> will
> > > > not be enough to get the site hosted on ASF infrastructure (unless
> some
> > > > super-smart ASF automation would somehow automatically pick it up);
> > > we'll
> > > > need to update ... something, probably
> > > >
> > >
> https://github.com/openzipkin/openzipkin.github.io/blob/master/.circleci/config.yml
> > > > to push the generated site to wherever it needs to go. I'm happy to
> do
> > > > that, especially if you can point me at relevant docs :)
> > > >
> > > > Please note that moving 'openzipkin/openzipkin.github.io' out of the
> > > GitHub
> > > > openzipkin organization right now would break the site, as it's
> hosted
> > > > directly through GH Pages, so let's make sure the domain is
> redirected
> > > > before doing so. Speaking of, FTR: zipkin.io currently goes through
> > > > CloudFlare (for HTTPS). Shouldn't change the migration process, just
> good
> > > > to know to avoid confusion.
> > > >
> > > > On Fri, Sep 7, 2018 at 9:51 AM Mick Semb Wever <mc...@apache.org>
> wrote:
> > > >
> > > > > Per the Zipkin Proposal I've created the infra ticket to request
> moving
> > > > > the listed zipkin repositories from the openzipkin github
> organisation
> > > to
> > > > > the apache organisation.
> > > > >
> > > > > https://issues.apache.org/jira/browse/INFRA-16989
> > > > >
> > > > > The process here I do believe is that we'll need to add admin
> rights to
> > > > > whomever from ASF infra picks up the ticket and then they will
> > > transfer the
> > > > > repository to the apache github organisation. All history will be
> > > > > maintained.
> > > > >
> > > > > Speak up if there's anything wrong here!!
> > > > >
> > > > > Adrian, what about 'openzipkin/openzipkin.github.io' ?
> > > > > I believe the website is to be hosted on ASF infrastructure, which
> > > means
> > > > > this repo will need to be transferred as well.
> > > > > Zipkin.io will then point to where it's hosted, the same as
> > > skywalking.io
> > > > > -> skywalking.apache.org
> > > > >
> > > > > cheers,
> > > > > Mick
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
> > > > > For additional commands, e-mail: dev-help@zipkin.apache.org
> > > > >
> > > > >
> > > >
> > > > --
> > > > Zoltán Nagy
> > > > https://abesto.net
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
> > > For additional commands, e-mail: dev-help@zipkin.apache.org
> > >
> > >
> >
> > --
> > Zoltán Nagy
> > https://abesto.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
> For additional commands, e-mail: dev-help@zipkin.apache.org
>
>
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by Willem Jiang <wi...@gmail.com>.
We could add a redirect of zipkin.io to zipkin.incubator.apache.org
once the Apache site is online.
Then we can move the openzipkin.github.io as we want.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Fri, Sep 7, 2018 at 11:53 PM Zoltán Nagy <ab...@gmail.com> wrote:
>
> Ah, I was missing the bit on git pub automatically updating the website
> from the repo. In that case yes, the plan you outlined seems best. The only
> thing to keep an eye out for is to make sure that the website doesn't break
> (too long, at least) during the migration of the repo. Specifically:
>
> - Create ASF website repo
> - Push current git history to ASF website repo, triggering upload of the
> website to ASF hosting
> - Switch zipkin.io to the ASF-hosted site
> - Delete the ASF website repo
> - *At this point, if automation tries to update the website from the
> repo, depending on how things are implemented, the website might go blank*
> - Move and rename `openzipkin/openzipkin.github.io` to be the ASF
> website repo
>
> We need that extra complexity to keep the issues tracked on the repo. If we
> didn't need that, we could just push the commit history, archive the old
> repo, switch the DNS, and call it a day.
>
> My ICLA is still pending processing from ASF, so hands currently tied
> behind my back. I'm happy to collaborate on doing this if it's urgent, or
> do the whole thing myself once my account is ready.
>
> On Fri, Sep 7, 2018 at 5:28 PM Willem Jiang <wi...@gmail.com> wrote:
>
> > Apache is using the git pub to manage the website, we just need to
> > keep generated website updated.
> > I think we can create a site repo first, then just publish the
> > generated website there and keep 'openzipkin/openzipkin.github.io' for
> > a while.
> > In this way, we can still us the Github GH pages as a back up, once
> > the apache website is online we can consider to move
> > 'openzipkin/openzipkin.github.io'
> >
> > Any thought?
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> > On Fri, Sep 7, 2018 at 5:01 PM Zoltán Nagy <ab...@gmail.com> wrote:
> > >
> > > > The process here I do believe is that we'll need to add admin rights to
> > > whomever from ASF infra picks up the ticket and then they will transfer
> > the
> > > repository to the apache github organisation. All history will be
> > > maintained.
> > > I can do that as well if Adrian is not available when that happens. Oh,
> > > and, after checking
> > > https://github.com/orgs/openzipkin/people?query=+role%3Aowner: so can
> > you!
> > >
> > > > Adrian, what about 'openzipkin/openzipkin.github.io' ?
> > > > I believe the website is to be hosted on ASF infrastructure, which
> > means
> > > this repo will need to be transferred as well.
> > > That's my understanding as well. Though, note: just moving the repo will
> > > not be enough to get the site hosted on ASF infrastructure (unless some
> > > super-smart ASF automation would somehow automatically pick it up);
> > we'll
> > > need to update ... something, probably
> > >
> > https://github.com/openzipkin/openzipkin.github.io/blob/master/.circleci/config.yml
> > > to push the generated site to wherever it needs to go. I'm happy to do
> > > that, especially if you can point me at relevant docs :)
> > >
> > > Please note that moving 'openzipkin/openzipkin.github.io' out of the
> > GitHub
> > > openzipkin organization right now would break the site, as it's hosted
> > > directly through GH Pages, so let's make sure the domain is redirected
> > > before doing so. Speaking of, FTR: zipkin.io currently goes through
> > > CloudFlare (for HTTPS). Shouldn't change the migration process, just good
> > > to know to avoid confusion.
> > >
> > > On Fri, Sep 7, 2018 at 9:51 AM Mick Semb Wever <mc...@apache.org> wrote:
> > >
> > > > Per the Zipkin Proposal I've created the infra ticket to request moving
> > > > the listed zipkin repositories from the openzipkin github organisation
> > to
> > > > the apache organisation.
> > > >
> > > > https://issues.apache.org/jira/browse/INFRA-16989
> > > >
> > > > The process here I do believe is that we'll need to add admin rights to
> > > > whomever from ASF infra picks up the ticket and then they will
> > transfer the
> > > > repository to the apache github organisation. All history will be
> > > > maintained.
> > > >
> > > > Speak up if there's anything wrong here!!
> > > >
> > > > Adrian, what about 'openzipkin/openzipkin.github.io' ?
> > > > I believe the website is to be hosted on ASF infrastructure, which
> > means
> > > > this repo will need to be transferred as well.
> > > > Zipkin.io will then point to where it's hosted, the same as
> > skywalking.io
> > > > -> skywalking.apache.org
> > > >
> > > > cheers,
> > > > Mick
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
> > > > For additional commands, e-mail: dev-help@zipkin.apache.org
> > > >
> > > >
> > >
> > > --
> > > Zoltán Nagy
> > > https://abesto.net
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
> > For additional commands, e-mail: dev-help@zipkin.apache.org
> >
> >
>
> --
> Zoltán Nagy
> https://abesto.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
For additional commands, e-mail: dev-help@zipkin.apache.org
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by Zoltán Nagy <ab...@gmail.com>.
Ah, I was missing the bit on git pub automatically updating the website
from the repo. In that case yes, the plan you outlined seems best. The only
thing to keep an eye out for is to make sure that the website doesn't break
(too long, at least) during the migration of the repo. Specifically:
- Create ASF website repo
- Push current git history to ASF website repo, triggering upload of the
website to ASF hosting
- Switch zipkin.io to the ASF-hosted site
- Delete the ASF website repo
- *At this point, if automation tries to update the website from the
repo, depending on how things are implemented, the website might go blank*
- Move and rename `openzipkin/openzipkin.github.io` to be the ASF
website repo
We need that extra complexity to keep the issues tracked on the repo. If we
didn't need that, we could just push the commit history, archive the old
repo, switch the DNS, and call it a day.
My ICLA is still pending processing from ASF, so hands currently tied
behind my back. I'm happy to collaborate on doing this if it's urgent, or
do the whole thing myself once my account is ready.
On Fri, Sep 7, 2018 at 5:28 PM Willem Jiang <wi...@gmail.com> wrote:
> Apache is using the git pub to manage the website, we just need to
> keep generated website updated.
> I think we can create a site repo first, then just publish the
> generated website there and keep 'openzipkin/openzipkin.github.io' for
> a while.
> In this way, we can still us the Github GH pages as a back up, once
> the apache website is online we can consider to move
> 'openzipkin/openzipkin.github.io'
>
> Any thought?
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
> On Fri, Sep 7, 2018 at 5:01 PM Zoltán Nagy <ab...@gmail.com> wrote:
> >
> > > The process here I do believe is that we'll need to add admin rights to
> > whomever from ASF infra picks up the ticket and then they will transfer
> the
> > repository to the apache github organisation. All history will be
> > maintained.
> > I can do that as well if Adrian is not available when that happens. Oh,
> > and, after checking
> > https://github.com/orgs/openzipkin/people?query=+role%3Aowner: so can
> you!
> >
> > > Adrian, what about 'openzipkin/openzipkin.github.io' ?
> > > I believe the website is to be hosted on ASF infrastructure, which
> means
> > this repo will need to be transferred as well.
> > That's my understanding as well. Though, note: just moving the repo will
> > not be enough to get the site hosted on ASF infrastructure (unless some
> > super-smart ASF automation would somehow automatically pick it up);
> we'll
> > need to update ... something, probably
> >
> https://github.com/openzipkin/openzipkin.github.io/blob/master/.circleci/config.yml
> > to push the generated site to wherever it needs to go. I'm happy to do
> > that, especially if you can point me at relevant docs :)
> >
> > Please note that moving 'openzipkin/openzipkin.github.io' out of the
> GitHub
> > openzipkin organization right now would break the site, as it's hosted
> > directly through GH Pages, so let's make sure the domain is redirected
> > before doing so. Speaking of, FTR: zipkin.io currently goes through
> > CloudFlare (for HTTPS). Shouldn't change the migration process, just good
> > to know to avoid confusion.
> >
> > On Fri, Sep 7, 2018 at 9:51 AM Mick Semb Wever <mc...@apache.org> wrote:
> >
> > > Per the Zipkin Proposal I've created the infra ticket to request moving
> > > the listed zipkin repositories from the openzipkin github organisation
> to
> > > the apache organisation.
> > >
> > > https://issues.apache.org/jira/browse/INFRA-16989
> > >
> > > The process here I do believe is that we'll need to add admin rights to
> > > whomever from ASF infra picks up the ticket and then they will
> transfer the
> > > repository to the apache github organisation. All history will be
> > > maintained.
> > >
> > > Speak up if there's anything wrong here!!
> > >
> > > Adrian, what about 'openzipkin/openzipkin.github.io' ?
> > > I believe the website is to be hosted on ASF infrastructure, which
> means
> > > this repo will need to be transferred as well.
> > > Zipkin.io will then point to where it's hosted, the same as
> skywalking.io
> > > -> skywalking.apache.org
> > >
> > > cheers,
> > > Mick
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
> > > For additional commands, e-mail: dev-help@zipkin.apache.org
> > >
> > >
> >
> > --
> > Zoltán Nagy
> > https://abesto.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
> For additional commands, e-mail: dev-help@zipkin.apache.org
>
>
--
Zoltán Nagy
https://abesto.net
Re: Moving Zipkin repositories from the openzipkin to apache
Posted by Willem Jiang <wi...@gmail.com>.
Apache is using the git pub to manage the website, we just need to
keep generated website updated.
I think we can create a site repo first, then just publish the
generated website there and keep 'openzipkin/openzipkin.github.io' for
a while.
In this way, we can still us the Github GH pages as a back up, once
the apache website is online we can consider to move
'openzipkin/openzipkin.github.io'
Any thought?
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Fri, Sep 7, 2018 at 5:01 PM Zoltán Nagy <ab...@gmail.com> wrote:
>
> > The process here I do believe is that we'll need to add admin rights to
> whomever from ASF infra picks up the ticket and then they will transfer the
> repository to the apache github organisation. All history will be
> maintained.
> I can do that as well if Adrian is not available when that happens. Oh,
> and, after checking
> https://github.com/orgs/openzipkin/people?query=+role%3Aowner: so can you!
>
> > Adrian, what about 'openzipkin/openzipkin.github.io' ?
> > I believe the website is to be hosted on ASF infrastructure, which means
> this repo will need to be transferred as well.
> That's my understanding as well. Though, note: just moving the repo will
> not be enough to get the site hosted on ASF infrastructure (unless some
> super-smart ASF automation would somehow automatically pick it up); we'll
> need to update ... something, probably
> https://github.com/openzipkin/openzipkin.github.io/blob/master/.circleci/config.yml
> to push the generated site to wherever it needs to go. I'm happy to do
> that, especially if you can point me at relevant docs :)
>
> Please note that moving 'openzipkin/openzipkin.github.io' out of the GitHub
> openzipkin organization right now would break the site, as it's hosted
> directly through GH Pages, so let's make sure the domain is redirected
> before doing so. Speaking of, FTR: zipkin.io currently goes through
> CloudFlare (for HTTPS). Shouldn't change the migration process, just good
> to know to avoid confusion.
>
> On Fri, Sep 7, 2018 at 9:51 AM Mick Semb Wever <mc...@apache.org> wrote:
>
> > Per the Zipkin Proposal I've created the infra ticket to request moving
> > the listed zipkin repositories from the openzipkin github organisation to
> > the apache organisation.
> >
> > https://issues.apache.org/jira/browse/INFRA-16989
> >
> > The process here I do believe is that we'll need to add admin rights to
> > whomever from ASF infra picks up the ticket and then they will transfer the
> > repository to the apache github organisation. All history will be
> > maintained.
> >
> > Speak up if there's anything wrong here!!
> >
> > Adrian, what about 'openzipkin/openzipkin.github.io' ?
> > I believe the website is to be hosted on ASF infrastructure, which means
> > this repo will need to be transferred as well.
> > Zipkin.io will then point to where it's hosted, the same as skywalking.io
> > -> skywalking.apache.org
> >
> > cheers,
> > Mick
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
> > For additional commands, e-mail: dev-help@zipkin.apache.org
> >
> >
>
> --
> Zoltán Nagy
> https://abesto.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
For additional commands, e-mail: dev-help@zipkin.apache.org