On Mon, 9 Jan 2012 08:07:26 -0800 (PST) HansBKK <[email protected]> wrote:
> 2. They get served up, directly and as-is, by DokuWiki - plaintext files > **are** its native datastore. In effect the @files are available on the web > for you, me and Joe Blow to edit - subject of course to whatever > open/secure balance the developers desire. My thought was that if Leo is a premier platform for editing rst, as we like to believe it is, it should work as an environment for editing documentation for Leo, by anyone. One requirement would be to avoid forcing the user to set up bzr / ssh / launchpad. That part could probably be handled by Leo itself. I like DokuWiki well enough, used it once long ago, but I think we need to think hard before tying ourselves to having things running on platform XYZ. If we revamp Leo's hosting say by moving from LP to bitbucket, there'd be a strong argument for accepting bitbucket's wiki system, whatever it is. Right now I don't think we have developer time for any major changes, unless we add more developers... :-) I understand you're trying to avoid using developer time here, and I suppose in theory the DokuWiki stuff could be completely separate from the Leo distribution process and require no developer input beyond responding to requests to check new content. But Leo already has way too many homes on the web, so we need plan carefully before adding more. Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. 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.
