zipkin-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [incubator-zipkin] adriancole opened a new issue #2629: Revert migration to the ASF
Date Thu, 13 Jun 2019 01:40:17 GMT
adriancole opened a new issue #2629: Revert migration to the ASF
URL: https://github.com/apache/incubator-zipkin/issues/2629
 
 
   As you know, [we voted to withdraw](https://lists.apache.org/thread.html/e3d911151dff081145886b620145924067267de998da40495b1f996b@%3Cdev.zipkin.apache.org%3E)
from the Apache Incubator. This issue tracks work towards that across all repos and will be
updated with tick boxes as we proceed.
   
   ## 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 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message