On 5/8/07, Gary Johnson <[EMAIL PROTECTED]> wrote:
On 2007-05-08, Ian Tegebo <[EMAIL PROTECTED]> wrote:
> On 5/8/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
> >
> > Ian Tegebo wrote:
> > > I would like to make another implementation independent suggestion;
> > > one could make a VimWiki more valuable by importing the _extremely_
> > > valuable vim helpfiles into it.
> >
> > Please don't do this. It might sound like a nice idea, but it means
> > making a branch that will be very hard to merge back into the help files
> > of the distribution.
> I feel misunderstood but it serves me right for not saying what I mean...
>
> Synchronizing data is no fun, I agree. While I was up in the clouds I
> was imaging that the wiki would be the authoritative source for the
> helpfiles after doing an initial _import_. Then the text version
> would be exported as needed, e.g. end user runtime update or for a new
> release.
This seems like a bad idea. The vim help files are an authoritative
source because their content is under the control of an authority:
Bram. Others are encouraged to submit patches that correct errors
or clarify wording, but before any of those patches are applied,
Bram looks at them to be sure they are correct and consistent with
the help files' style.
I was assuming the wiki that would be chosen would allow for some
level of access control. I'm also assuming a group of trusted
long-time users could be delegated the responsibility of administering
the wiki. If Bram is the only one who should make changes to an
object than I agree that those objects wouldn't be useful in a wiki.
I think it's possible to have a protected part of the wiki for
helpfiles that is write restricted and have another part that is more
open that can easily reference those files. Of course, if the value
added by more hands on the helpfiles doesn't exceed the cost in
maintenance than this is a poor choice.
I don't think I've really seen any issues with updates to helpfiles,
they were just an example. So far I think the point was to just be
able to link to parts of them more easily - I didn't really mean to
dwell on the help system. I was just hoping to carry the point that
wikis _can_ provide a lot of valuable function if properly cultivated.
In all this I've lost track of what the purpose of a VimWiki would be.
Was it just meant to host vim tips? Thinking about the format of
tips now, I wonder if a blog format wouldn't be more suitable. For
example, tips are posts that then have comments while most blogs have
these features as well as search and RSS. VimBlog?
To this end I wonder if there are enough people to support more apps
given the work load the vimonline team has:
Bugs
https://sourceforge.net/tracker/?atid=391887&group_id=27891&func=browse
Features
https://sourceforge.net/tracker/?atid=391890&group_id=27891&func=browse
--
Ian Tegebo
