We manage the TiddlyWiki source code and build process on GitHub, like most open source projects. We also manage the documentation as thought it were part of the software. That's not terrible: it's pretty useful to keep the core reference documentation under tight control to make it easier to try to improve and assure the quality and reliability. The downside is that the barriers to participation through GitHub are pretty high, requiring the ability to use both GitHub and the Node.js configuration of TiddlyWiki.
It would be great to start using an online collaborative system to which the broad community can contribute, starting with community documentation and eventually moving the reference documentation there too. One issue is that I am personally not keen to take the entire responsibility for a community collaboration space as I do for the TiddlyWiki code itself; managing a shared wiki is an onerous task and I'm not confident that I've the bandwidth to be the best person to do it. I'm thinking particularly of the issues around spam and community standards of behaviour. We faced the same challenges with TiddlyWiki Classic. At first we used an instance of MediaWiki, and then we migrated to the TiddlySpace-based tiddlywiki.org that you see today. For TiddlyWiki5, my goal is to use federation features, as previously discussed. In a nutshell, very similar to Erwan's experiments: a process for registering wikis that participate in the community federation, and conventions for marking tiddlers as being comments directed to other users, or threaded into shared conversations. The main technical requirement is the ability for any participant to trigger a rebuild of the static files that are served to visitors. I'm hoping to use Amazon Lambda for that. Finally, I should say that there are two particular problems with content updates at the moment: * The TW5 release cycle has slowed down. Partly that's a natural consequence of its maturity, and partly its because I've been much busier with my dayjob over the last few months * I accidentally broke the ability for me to push content updates independently of updates to the core code :( Hopefully, post-5.1.10 I'll resume being able to push content updates every few days Best wishes Jeremy. On Tue, Sep 15, 2015 at 10:18 AM, Evolena <[email protected]> wrote: > The issue with being able to directly edit the TW5.com is that, unlike > other wikis systems, the TW core is also editable, so anyone could break > it, or worse. So the moderation is far more important than content-only > moderation. > > -- > 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/fdae3b5d-8daa-4516-b494-0e2ecf2072f8%40googlegroups.com > <https://groups.google.com/d/msgid/tiddlywiki/fdae3b5d-8daa-4516-b494-0e2ecf2072f8%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Jeremy Ruston mailto:[email protected] -- 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/CAPKKYJbc-R3aOPbryRGgcDGu1LNSPhvGQ%2BhFY%3DMM9XYZXcH__A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
