emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matthew Lundin <mdl@imapmail.org>
To: David Libert <libert.david@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Using org-mode and git to make a wiki
Date: Wed, 17 Jun 2009 10:59:51 -0500	[thread overview]
Message-ID: <87zlc6svew.fsf@fastmail.fm> (raw)
In-Reply-To: <30672390906170009s43afecb8w7ef92e6a48257273@mail.gmail.com> (David Libert's message of "Wed, 17 Jun 2009 03:09:55 -0400")

Hi David,

Thanks for these reflections on using org-mode and git for collaborative

David Libert <libert.david@gmail.com> writes:

> I found in the org-mode home page the  worg project,  which is smilar
> to this.  A git repository, and writers contribute to worg through
> git.  But
> worg publishes the org-mode as html  and in the end serves it up as a
> web page.
> I propose we never go to html.  Stay in emacs and org-mode the whole
> time.  So you know your readers have the full functionality of org-mode
> to be reading your writing.

You can read Worg online (in html), but you can also peruse the org
source by cloning the git repository. In fact, I mainly consult Worg
offline (via the org files).

Some nice instructions on how to clone Worg can be found here:


So the good news is: You can already do everything you mention with
org-mode and git. Just clone a bare repository somewhere and allow
others to push and pull from it. 

One can certainly dream, but I imagine the difficult task would be to
convince co-workers to learn emacs and org-mode. ;) To be sure, version
control systems like git, svn, bzr, etc. are the best tools for
collaborative work I've ever found. But they are not exactly user
friendly for non-coders and they are designed to work with plain text.
And, alas, for the past three decades, software developers have worked
very hard to make modern life needlessly complicated by inventing all
sorts of incompatible binary file formats for storing text. Of course,
that was before Carsten Dominik came along to show us just how much is
possible in plain text!

All this is to say that those who do anything other than coding will
likely have to adapt to the web app, workflow, file format, or ticket
tracker that others use. And those who do code may have an even more
difficult time convincing vi users to try org-mode!

The fallback option, of course, is to clip everything you need into
org-mode and to let others wonder what is making you so efficient. :)



  parent reply	other threads:[~2009-06-17 15:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17  7:09 Using org-mode and git to make a wiki David Libert
2009-06-17  7:31 ` Nicolas Girard
2009-06-17  8:43   ` David Libert
2009-06-17 15:59 ` Matthew Lundin [this message]
2009-06-20 18:56   ` Bastien
2009-06-22 11:34     ` Sebastian Rose
2009-06-25 17:20       ` Tim O'Callaghan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zlc6svew.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=libert.david@gmail.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).