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 <[email protected]> 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 <[email protected]> > 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 <[email protected]> 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 <[email protected]> >> 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 <[email protected]> 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 <[email protected]> >> 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: [email protected] >> > > > > For additional commands, e-mail: [email protected] >> > > > > >> > > > > >> > > > >> > > > -- >> > > > Zoltán Nagy >> > > > https://abesto.net >> > > >> > > --------------------------------------------------------------------- >> > > To unsubscribe, e-mail: [email protected] >> > > For additional commands, e-mail: [email protected] >> > > >> > > >> > >> > -- >> > Zoltán Nagy >> > https://abesto.net >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >>
