search

openzipkin / openzipkin.github.io

content for https://zipkin.io
https://zipkin.io
Apache License 2.0
39 stars 61 forks source link

Migrate content from apache wiki here #130

Closed codefromthecrypt closed 5 years ago

codefromthecrypt commented 5 years ago

Most content could likely be exported in some way (ideally not manually) here.

https://cwiki.apache.org/confluence/display/ZIPKIN

Probably some would be moving to literally the wiki here and others would be new pages. However, it is likely easier to start with wiki here, acknowledging there are likely some access concerns we'd need to work out.

abesto commented 5 years ago

Agree, I've also been thinking about using the GH wiki at least for an initial dump of content. I expect to find some half-working script somewhere on the internets that can be adapted for our needs.

On Mon, Jun 17, 2019 at 3:05 AM Adrian Cole notifications@github.com wrote:

Assigned #130 https://github.com/openzipkin/openzipkin.github.io/issues/130 to @abesto https://github.com/abesto.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/openzipkin/openzipkin.github.io/issues/130?email_source=notifications&email_token=AAAOUTRD6RUOX55ISFEYA6DP23WOPA5CNFSM4HYSSFGKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSACPE7Y#event-2416243327, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAOUTSI2CNJ7MQFVGARU6TP23WOPANCNFSM4HYSSFGA .

-- Zoltán Nagy https://abesto.net

abesto commented 5 years ago

Alright so... I kinda sorta did it.

The result is... uhh... let's just say the content is there. But

So umm... you know... :shipit: I guess. At this point I feel like any further automation would be less efficient than manually cleaning the content, and I really really don't feel like manually cleaning the content. So maybe this is good enough for now?

codefromthecrypt commented 5 years ago

thanks zoltan. I will look at this by tomorrow!

On Wed, Jun 19, 2019, 5:26 AM Zoltán Nagy notifications@github.com wrote:

Alright so... I kinda sorta did it.

  • I used https://www.npmjs.com/package/confluence-to-github-markdown to do the import
  • Then did some Bash things to move .md files into subfolders according to the structure they had on CWiki (this is a one-off, so didn't bother to put it into a script)
  • Then wrote a quick script to generate a custom sidebar based on the folder structure (this is checked into the the Wiki "repo")

The result is... uhh... let's just say the content is there. But

  • Cross-page links are borken
  • Confluence-specific headers and footers are in each page (along with comments, which you might consider a plus I guess)
  • Code blocks are not formatted as code blocks
  • Probably other problems exist as well?

So umm... you know... [image: :shipit:] I guess. At this point I feel like any further automation would be less efficient than manually cleaning the content, and I really really don't feel like manually cleaning the content. So maybe this is good enough for now?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/openzipkin/openzipkin.github.io/issues/130?email_source=notifications&email_token=AAAPVV535U6VP6R3XBZZET3P3FHHJA5CNFSM4HYSSFGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYAAN6A#issuecomment-503318264, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAPVV4LW4ZH4BW6CHDF2WDP3FHHJANCNFSM4HYSSFGA .

codefromthecrypt commented 5 years ago

I'm happy!

I will defuzz some of the content offline, but for now looks good. Thanks so much for moving the big rocks!