codefromthecrypt
commented
5 years ago added rough draft of steps for the website
Closed codefromthecrypt closed 4 years ago
codefromthecrypt
commented
5 years ago added rough draft of steps for the website
codefromthecrypt
commented
5 years ago Added reference to https://issues.apache.org/jira/browse/INFRA-18604
codefromthecrypt
commented
5 years ago note: until the repositories are moved back to the openzipkin org, our deployment automation will fail (ex bintray will reject uploads even with encrypted credentials). Until https://issues.apache.org/jira/browse/INFRA-18604 is solved, or another mechanism is made, uploads are manual similar to apache.
codefromthecrypt
commented
5 years ago all repos are back now
codefromthecrypt
commented
5 years ago https://issues.apache.org/jira/browse/INFRA-18809 is about getting zipkin.apache.org decommissioned or redirecting or something thx @abesto for raising it
abesto
commented
5 years ago Redirect is up:
$ curl -D- https://zipkin.apache.org/quickstart.html
HTTP/1.1 301 Moved Permanently
Date: Tue, 30 Jul 2019 08:32:06 GMT
Server: Apache/2.4.18 (Ubuntu)
Location: https://zipkin.io/quickstart.html
Content-Length: 241
Content-Type: text/html; charset=iso-8859-1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="https://zipkin.io/quickstart.html">here</a>.</p>
</body></html>
jorgheymans
commented
4 years ago Migration reverted thanks.
As you know, we voted to withdraw from the Apache Incubator. This issue tracks work towards that across all repos and will be updated with tick boxes as we proceed.
The Zipkin podling has retired to its former community [OpenZipkin](https://zipkin.io)Get releases back online ASAP
We are critically behind schedule for things like brave releases: 3 months which is a time period we've never experienced before. Above all, we need to get functional again so that we don't further injure our community.
License, group IDs etc.
First step is to change project assets back to the old group IDs, remove mention of the disclaimer and revert the license headers to the more generic one we had before (except possibly leaving out the year).
Deploying under zipkin.io
Deployment wise, the quickest way to get back online would be to deploy to sonatype directly and skip setting up bintray again, using the same tooling as we have with ASF. This is probably better anyway, as bintray we were over resources with anyway.
Signing keys
There is no legal exclusivity as far as I know to the GPG keys we have. IOTW, we can use them to sign anything, including things not in the ASF. Folks who desire to make new keys surely can, but I don't think it is required to.
Migration of repos back to OpenZipkin
You'll remember github was a one way street access wise.. we had to grant Apache INFRA admin, and lose our access except to commit files (ex we have no control over anything including webhooks, much less the ability to move our repos back). This means we need to place a ticket and that might happen soon or not depending on their workload.
Migration of Website
The website is more straightforward as almost all content updates were ASF in nature and in a new repo. If it is possible to "un-archive" our old repo, I suggest we just do that and fix the DNS.
cc @apache/zipkin-committers