Case in point: During the whole Julie Horvath controversy, a few anti-Github developers started a campaign to create awareness of the harmful effects of Github's culture (or something)...but they created their standalone site using Github Pages:
https://github.com/CultureOffset/cultureoffset.github.com
I pointed out, independent of how I felt about Horvath or Github, that not only does it send a terrible message to run a boycotting campaign on the service you want to boycott...it is completely unnecessary, thanks to how git actually works and the many other great build tools/stacks to do static web development in under 24 hours. However, I got reamed for being an asshole and "man-splaining" things.
But really, as useful as Github is, every dev should spend some time on thinking through what underlies Github, and how to get by without it...especially if you intend on protesting Github.
"Offsets" may not be literally a boycott, but the message is the same. And if at all possible, the organizers of such should avoid creating more "poison" to "offset"...in this case, if you wanted to put your name as a pledge, you had to have a Github account, and you had to use Github's services...which, in the end, helps to perpetuate Github.
But the kicker is that using Github as a necessary evil is not necessary at all, thanks to the great work of open-source developers...
(and yes, the question of, what the hell does "offseting" Github's culture even mean is a whole separate mind-dislocation, but not worth debating in this thread)
> git clone git@github.com:wicketstuff/core.wiki.git
More of a problem would be your issues.
With a few plugins and some hacking, you can get vim to just browse the wiki too. (I'm currently working on getting my scripts for this into a state that is useful).
Unrelated - there are some plugins to use the github api to browse tickets in vim too.
(note not all of these workflows make sense as a primary way of using them, but they are still useful at times).