Thanks Offray for your detailed and informative response.
On Friday, January 20, 2012 5:34:21 PM UTC+7, Offray Vladimir Luna Cárdenas
wrote:
>
> When you suggested DocuWiki I thought of MoinMoin which has also support
> of plain files as storage mechanism but is also scalable to databases if
> this is needed and it supports reStructuredText and is made in python, a
> language that "leonizens" are familiar with.
>
I for some reason missed the MoinMoin's "simple page storage" option -
thanks so much for pointing that out. For all the reasons you cite, and
most importantly is much more mainstream, more actively developed and
well-supported than Gitit, I'll definitely give it a higher priority in my
testing.
> the "sub-optimal distopic world of everything is a file".
>
I personally disagree with your dislike for "everything is a file" - I see
that principle as a fundamental part of the *nix tool philosophy, and IMO
this is a perfect example:
I certainly think that a distributed off-line collaboration system for
> documentation is needed and, if MoinMoin can't
>
> support the use of distributed wikis (and seems is not planned or in
> development
>
To my mind, any wiki platform that can store the page data as plain text
(as opposed to binary/database), in a format suitable for diff tools
("light" markup as opposed to html/xml) can make use of whatever VCS for
distribution/replication.
> On a related matter one of the problems I see with actual server
> technology is its gigantism which concentrates
> power in the people who has the resources, knowledge and time to possess,
> understand and administer/intervene this technology so a Global South Test
> for me about which server technology to choose is: "it runs from a USB
> thumb drive?".
>
IMO "server" is a function, not a question of scale or complexity - the
better question for my workflow is "does the app run portably?". I
personally find actually running stuff from flash drives too slow and
data-dangerous.
In my workflow, at the beginning of a session I first sync the relevant
data and "portable apps" filesystem branches, then run everything off the
local HD. At the end of a session I sync it all back - most of the time
these days this is to/from a central filer, but I do have portable drives I
use for this when that's required or more convenient, which then get sync'd
to the filer next chance I get.
So far I've found that anything that runs under Linux is inherently
portable in that sense.
> This, for example, favors Web2py/Smalltalk instead of Zope and Fossil
> instead of GitHub.
>
I haven't any experience with these others, but note that Git does not =
GitHub. I share your dislike for server/storage platforms out of my direct
control, not least for privacy/security issues for many use cases. If I
used Git for data distribution I wouldn't use GitHub, and my understanding
is that even "Git for Windows" is already fully portable.
For myself, I think mercurial would be a good fit, but my main point is
that any moves toward a "distributed Leo" should IMO be VCS-agnostic, just
as my plans for enabling community editing of Leo-managed content will be
wiki-platform agnostic.
To me, the key enabler for that is "everything as a file". . .
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/leo-editor/-/7lfzkoQni7IJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
