On the matter of https://github.com/apache/incubator-zipkin-api/issues/62 (that is, URLs like https://zipkin.io/zipkin-api/#/default/get_services being broken), this is now mitigated by a generous layer of duct-tape (details in the ticket; short version: I copy-pasted the contents into `openzipkin/ openzipkin.github.io`). As a next step, I'll now try to reconcile the changes between the two repositories and put up a PR. I'll also put a note onto openzipkin.github.io along the lines of "go away, this is now read only and deprecated" in another PR.
> Will it be possible to redirect the Apache domain to zipkin.io for now? We have control of the contents via the `apache/incubator-zipkin-website` repo (and accompanying Jenkins job), but I think we shouldn't do this if we can avoid it. Reconciling the changes should be doable, and we'll _have_ to do it at some point, so I'd recommend focusing efforts on that. > Oh right. Yeah. We could do a JavaScript redirect with a "we have moved" > message or something. Would be good to just get users used to us being at > Apache instead, and solve the bookmark problem. Yep, that sounds about right . > To be more SEO friendly maybe we could find some way of serving redirect > responses for all the pages? I know Raja played with netlify a while ago. > Maybe that's a solution since GH pages doesn't support that AFAIK Yeah this can get messy. I guess since this is a static site, we _could_ generate a static redirect page for each URL that used to be served on zipkin.io. It shouldn't actually be all that hard :) On Sun, Apr 21, 2019 at 9:44 PM José Carlos Chávez <[email protected]> wrote: > Will it be possible to redirect the Apache domain to zipkin.io for now? > > søn. 21. apr. 2019, 22:00 skrev Brian Devins-Suresh <[email protected]>: > > > Oh right. Yeah. We could do a JavaScript redirect with a "we have moved" > > message or something. Would be good to just get users used to us being at > > Apache instead, and solve the bookmark problem. > > > > To be more SEO friendly maybe we could find some way of serving redirect > > responses for all the pages? I know Raja played with netlify a while ago. > > Maybe that's a solution since GH pages doesn't support that AFAIK > > > > On Sun, Apr 21, 2019 at 3:49 PM José Carlos Chávez <[email protected]> > > wrote: > > > > > Is this going to have some impact in SEO? > > > > > > søn. 21. apr. 2019, 21:19 skrev Zoltán Nagy <[email protected]>: > > > > > > > I'll start looking at the website problems in an hour or so to at > > least > > > > put out the current fires, please shout if there's already ongoing > work > > > so > > > > we don't step on each others toes. > > > > > > > > Regarding zipkin.io, my current understanding is we cannot do that: > > ASF > > > > doesn't serve custom domains unless in very special circumstances > (see > > > > https://issues.apache.org/jira/browse/INFRA-16996) for more on this. > > > We'll > > > > need to update everything to zipkin.apache.org, and set up a > redirect > > at > > > > zipkin.io to zipkin.apache.org. > > > > > > > > On Sun, Apr 21, 2019 at 12:46 PM Brian Devins-Suresh < > > [email protected] > > > > > > > > wrote: > > > > > > > > > We should probably also CNAME zipkin.io to zipkin.apache.org, > which > > > > might > > > > > solve the user problems too. > > > > > > > > > > On Sun, Apr 21, 2019 at 1:53 AM José Carlos Chávez < > > > [email protected]> > > > > > wrote: > > > > > > > > > > > I volunteer for this. But can't not start it until Tuesday (I am > on > > > > > > holidays). If someone else feels like fixing it just go ahead, > > > > otherwise > > > > > I > > > > > > will take this over on Tuesday. > > > > > > > > > > > > søn. 21. apr. 2019, 01:34 skrev Adrian Cole < > > [email protected] > > > >: > > > > > > > > > > > > > Hi, team. you know we have zipkin.io but the first effort was > to > > > get > > > > > > > http://zipkin.apache.org/ setup. We have a couple problems > > > > > > > > > > > > > > 1. there is drift as people make changes to > > > > > > > https://github.com/openzipkin/openzipkin.github.io instead of > > > > > > > https://github.com/apache/incubator-zipkin-website > > > > > > > 2. people don't know about http://zipkin.apache.org/ > > > > > > > 3. we are getting a bunch of support requests because the link > to > > > the > > > > > > > api is broken > > > > https://github.com/apache/incubator-zipkin-api/issues/62 > > > > > > > > > > > > > > Can someone help drive these issues to conclusion? likely > ending > > > with > > > > > > > a README change to > > > > https://github.com/openzipkin/openzipkin.github.io > > > > > > > saying go to > https://github.com/apache/incubator-zipkin-website > > > and > > > > > > > archiving the former in openzipkin-attic? > > > > > > > > > > > > > > Best, > > > > > > > -A > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > To unsubscribe, e-mail: [email protected] > > > > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
