On Mon, 14 Apr 2008 12:18:42 -0400
Jeremy Maitin-Shepard <jbms@cmu.edu> wrote:

Hi Jeremy,

quoted text
> I've thought about this possibility myself, but it seems that the clone,
> edit, commit, push cycle may not really be ideal for a wiki.  For one
> thing, it is hardly ever necessary or useful to have anything more than
> per-file commits.  Also, if there are a large number of simultaneous
> users trying to push to the repository, you could run into a problem
> whereby you can never successfully push because ever time you try, it is
> not a fast-forward, so you have to fetch then merge (we can assume the
> merge is just done automatically because e.g. only different files were
> modified) then try to push again, but before you have a chance to retry
> the push, the branch head may have changed again due to another push.
> 
> I suppose in practice this may not be a problem for the git wiki as it
> may not have so many contributors, but this would certainly be a problem
> for e.g. wikipedia.

Yeah, it should be okay on this scale, its the same as having multiple developers
push into a common source repo.  Ikiwiki itself is hosted in Git and handles its
own wiki exactly this way.  It can be updated via the web site or Git push.
Running  "git pull --rebase" before doing a push into the wiki isn't onerous.

quoted text
> More generally, though, although we may all dislike using webpage
> interfaces, actually having to keep the entire wiki updated locally
> doesn't seem terribly useful.  Really, you just want a way to edit a
> particular page in your text editor, have various commands available for
> e.g. previewing, and have commands available for showing the log
> information with a nicer interface than a web page.

The goal would be to make the help texts available in multiple ways.  In a
text editor, or converted into other formats for use with other tools.  More
importantly they should continue be easy to find with Google and editable
via a browser for quick fixes by casual users.  But as it stands, the wiki
information is stuck on the web.

Git's documentation is already handled very close to this today.  It's easy to
clone the asciidoc source, read in a text editor, and turned into web or man
pages.   It seems attractive to do likewise for the wiki docs since the tools
are all at hand.

Cheers,
Sean
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html