Moderator of tiddlywikidocs saying hi and has a few questions
285 views
Skip to first unread message
Mat
Nov 24, 2014, 8:44:34 PM11/24/14
to tiddlyw...@googlegroups.com
Hi all! Previous moderator (or even group owner?) Daniel Baird flattered me into becoming a moderator ;-)
As I understand it there will be, or are already, additional moderators. It's a nice job (...but the salary) where you accept someones posts "from now on" or ban him or her. If there is a delay, even for a day or more, the first time you post now you know why. As moderator you also get to stick posts to the top!
Another previlige is to write the welcoming message as seen above the thread list. Please come with input if you think I've missed something, or misspelled something, or whatever problem there may be.
I'm thinking that we should bring up an official guide for writing documentation and put a link to it in the welcoming message. As you understand from guideline #1 in the welcoming message, this guide is just for anyone who cares.
A note on guideline #1 "even bad documentation is better than no documentation":
Someone wrote this on the tw google group just a few days ago (can't find it now tho). I think it is a brilliant insight. As he mentions, people are more likely to improve an existing document than to create one from scratch. I think this is true. An error, perhaps particularly in text, can even be enticing. "Oh, that's not right! It ought to be like this!"
We need all the enticement, ideas, systemic improvements, crazy opinions - and documentation - that people can bring.
...so bring it on.
But for a starter - what do you say about the definition for this list I wrote in the welcoming message? Is this a group for ALL things tiddly-documentation related? Also plugins, i.e not core? What about TiddlySpace, TiddlyWeb, TiddlySpot, TiddlyFox and other relatives in the family? How about CSS, html, javascript? Browser-TW issues? Philosophical aspects? etc etc.
I do feel that, for instance, "CSS, html, javascript" are areas of their own and should not be documentet by us... but who am I to argue if someone thinks there is a need for it? And, when I think about it a bit more, I definitely need help with that and if it was from a "tiddly aspect" that would just be great. My point is; we don't really know what potential readers would find valuable so we should probably not limit things. Any opinions on this stance?
However, it is one thing if we accept everything but another where it should be accepted for hosting. Obviously tiddlywiki.com comes to mind. And perhaps tiddlywiki.org. Would these places be suitable for hosting any documentation? And... in what way? As direct tiddlers? Maybe links for less appropriate documentation? Maybe there are totally different ways to deal with documentation?
...Core vs non-core documentation? And what about stuff that Eric will cover in his books? Community developed documentation should obviously not be obstacle to this project. But then, documentation should obviously be as good as possible for as many as possible. Is this an issue?
Ok, please share your thoughts. Maybe best start new threads because it's such a multi-facetted question that one thread would be confusing.
<:-)
As I understand it there will be, or are already, additional moderators. It's a nice job (...but the salary) where you accept someones posts "from now on" or ban him or her. If there is a delay, even for a day or more, the first time you post now you know why. As moderator you also get to stick posts to the top!
Another previlige is to write the welcoming message as seen above the thread list. Please come with input if you think I've missed something, or misspelled something, or whatever problem there may be.
I'm thinking that we should bring up an official guide for writing documentation and put a link to it in the welcoming message. As you understand from guideline #1 in the welcoming message, this guide is just for anyone who cares.
A note on guideline #1 "even bad documentation is better than no documentation":
Someone wrote this on the tw google group just a few days ago (can't find it now tho). I think it is a brilliant insight. As he mentions, people are more likely to improve an existing document than to create one from scratch. I think this is true. An error, perhaps particularly in text, can even be enticing. "Oh, that's not right! It ought to be like this!"
We need all the enticement, ideas, systemic improvements, crazy opinions - and documentation - that people can bring.
...so bring it on.
But for a starter - what do you say about the definition for this list I wrote in the welcoming message? Is this a group for ALL things tiddly-documentation related? Also plugins, i.e not core? What about TiddlySpace, TiddlyWeb, TiddlySpot, TiddlyFox and other relatives in the family? How about CSS, html, javascript? Browser-TW issues? Philosophical aspects? etc etc.
I do feel that, for instance, "CSS, html, javascript" are areas of their own and should not be documentet by us... but who am I to argue if someone thinks there is a need for it? And, when I think about it a bit more, I definitely need help with that and if it was from a "tiddly aspect" that would just be great. My point is; we don't really know what potential readers would find valuable so we should probably not limit things. Any opinions on this stance?
However, it is one thing if we accept everything but another where it should be accepted for hosting. Obviously tiddlywiki.com comes to mind. And perhaps tiddlywiki.org. Would these places be suitable for hosting any documentation? And... in what way? As direct tiddlers? Maybe links for less appropriate documentation? Maybe there are totally different ways to deal with documentation?
...Core vs non-core documentation? And what about stuff that Eric will cover in his books? Community developed documentation should obviously not be obstacle to this project. But then, documentation should obviously be as good as possible for as many as possible. Is this an issue?
Ok, please share your thoughts. Maybe best start new threads because it's such a multi-facetted question that one thread would be confusing.
<:-)
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages