Migrate Confluence to Github wiki (Gollum) - github

Does somebody know a nice way to migrate a Confluence wiki to the Github wiki (aka Gollum) ?
By nice way I mean quick and effective.

You can export whole spaces to html format, and than use pandoc to rewrite pages to ReST|Markdown

I had a similar problem, so I threw together some Python code to do this:
https://github.com/gergelykalman/confluence-markdown-exporter
It is pretty basic but it worked well for me.

Related

Where can I find Markdown language documentation?

I just a newbie on github. I'm doing my Project with the Markdown file type on that. So, can you show me where can I find full of Markdown Documentation?
Markdown is a lightweight and easy-to-use syntax for styling all forms of writing on the GitHub platform.
You can find this:
https://guides.github.com/features/mastering-markdown/
The best place to learn about markdown would be https://guides.github.com/features/mastering-markdown/
Another Markdown reference I have found useful is https://www.markdownguide.org/basic-syntax . This documentation gives reference to Markdown code next to HTML code that helps users understand the syntax more easily if they are familiar with HTML and its outputs.

Full text search in gerrit?

With github you can search class name and it'll find any usages of it in your repo. Or basically any word and github will find usages of it.
Is there a way to do the same thing at gerrit?
Maybe there's a plugin or something?
Gerrit does not have any support to code search and AFAIK there isn't a plugin with such feature.
We use OpenGrok to accomplish this. It's a very nice tool.

Is there a Confluence plugin based on SVG-edit?

I'm impressed by the ease of use of SVG-edit, having a sketch editor like that in Confluence would be great! I could not find such a plugin, does anyone know more?
The answer is now yes, there is, see this new Confluence plugin

Markdown not rendered in embedded gist

My gist markdown is not rendering when I embed it. Is this a GitHub issue, or am I doing it wrong?
The gist:
https://gist.github.com/3094145
The non-rendering embedded gist:
http://jsfiddle.net/dJnBg/
Thanks!
*2012-12-11 Update: Today github pushed out a complete rewrite of gist.github.com, and this is no longer a problem. For proof, see screenshot. *
It looks deliberate. It's worth noting that syntax highlighting still works in embeds, but not (alas) markdown rendering.
A potential workaround might be to add additional JS code (after the gist embed JS) that renders the markdown client-side, perhaps via http://www.showdown.im/
I made an issue for myself to do this for the redmine gist embed plugin I wrote.
https://github.com/dergachev/redmine_gist/issues/3
Perhaps by the time you're reading this I got around to tackling this ;)

Effective Extensions for Development Wiki

Our small team of 3-4 developers uses a wiki for documentation and collaboration. I'm trying to put together a list of some solid extensions which would help make it better. We are using MediaWiki, but if you know of a good extension/plug-in for another platform I'd like to hear about that too. Thanks.
Here is my list so far:
Geshi for syntax highlighting.
FCKeditor
TagAsCategory
Promising Extensions that don't work w/ MediaWiki 1.15.0
CategoryEditor
IssueTracker
Two things come to mind:
Bug tracking tool integration
SCM tool integration
For MediaWiki there are already
Bugzilla integration:
http://www.mediawiki.org/wiki/Extension:BugzillaReports
SVN integration:
http://www.mediawiki.org/wiki/Extension:SVNIntegration
The whole list of extensions is here
Well, I think that a good starting point would be to check what we use at mediawiki.org, because this is a Development Wiki :)
My first choice would be CodeReview of course. It's not pretty, but it's very useful. See how we use it: it allows to integrate a SVN into the wiki, to add comments on code, tag commits, and put statuses on it.
At MediaWiki, we use new/verified/ok chain, adding fixme/reverted/resolved/deferred when things go wrong; but you're free to use your own statuses here.