Hi Hegart,

I wouldn't think of the current process as "permission based". It's simply 
the way things are managed atm, that is by Jeremy himself.

As for "wiki-wiki", try to decouple TiddlyWiki itself from the actual 
website introducing it, e.g. imagining that tiddlywiki.com wasn't actually 
running on TiddlyWiki itself. Traditionally both have been interwoven, so 
one could expectat that working with the official presentation would be 
just as simple as working with a local copy. Well, it isn't quite the same 
process. ^_^

The current process surely is nothing high-speed, but it has its merits...

   - Jeremy does an excellent job of assuring content quality and integrity
   - problems with merging content for new features for the next release 
   are avoided
   - which would otherwise complicate the release process, trying to avoid 
      content edits being overwritten
   
A more community driven process might be speedier at the ramp up but would 
come with risks with respect to both of the above. Personally, I would 
advocate the same process, but decoupled from actual TW release. That way, 
content updates could be refreshed maybe once a day, or even just once a 
week, whereas release content — both release components and documentation — 
would be merged and updated during release rollout. The longer the release 
cycles might be(come), the more this is a favorable approach.

An entirely community-driven documentation process (and platform) would 
surely require vigilant and rigorous moderation so as to avoid things 
becoming all too bloated, chaotic, redundant, amateurish... and all that 
jazz.

— tb

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5112569d-c217-4c2c-bb0c-3c63ebe125ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to