Re: [HTCondor-devel] Considering moving design docs to Google Drive

[Will Benton <willb@xxxxxxxxxx>]

----- Original Message -----
> From: "Igor Sfiligoi" <sfiligoi@xxxxxxxx>
> To: htcondor-devel@xxxxxxxxxxx
> Sent: Friday, June 21, 2013 10:45:44 AM
> Subject: Re: [HTCondor-devel] Considering moving design docs to Google Drive
> 
> You mention the major downside in the proposal:
> You become reliant on Google... i.e. you do not own the complete history
> anymore.

Consider also github's wiki support.[1]  Since a github wiki is simply a git repository with plain-text files in it, it does not suffer from the downsides of Google Docs (e.g., third-party control, opaque file formats, necessity of manual export or backups).  Since it is hosted, it does not suffer from the obvious downsides of self-hosting collaboration software.  There is a nice web frontend for editing github wikis, but you can use your preferred text editor (even offline) instead.  The github wiki software itself is open-source[2] and your data and history are always available in the repo, so if you needed to stop using github for whatever reason, you could still use the same software elsewhere without losing documents or history.  Finally, the github wiki system supports eight (maybe more these days) lightweight markup languages and has special support for code highlighting in at least some of them.



best,
wb

[1] see https://github.com/blog/699-making-github-more-open-git-backed-wikis and https://github.com/blog/774-git-powered-wikis-improved
[2] see https://github.com/gollum/gollum