One thing that I've been thinking about is the difficulty of making a
trivial change to the standard tiddlywiki at widdlywiki.com.

If I download the page at tiddlywiki.com and edit a page I get a prompt
saying 'how to improve this documentation'

To do this you have to 'clone the repository' find the correct tiddler -
edit it and push the change back to the repository. The receiver has to
check the push request and accept or reject them.

This strikes me as being far too onerous for a casual user. Correction of
simple things like spelling errors should be one mouse click away without
any sign-ups or any repository cloning or any knowledge of github. There
must be many people who could use the tiddlywiki but not understand how to
use github.

I have only seen one web site that does this properly.

The Real World Haskell site is amazingly good at this. See
http://book.realworldhaskell.org/read/

If I'm reading a page and notice a typo or want to ask a question - it's
literally one mouse click away with no sign up.

I suggest taking a quick look at any one of therio pages to see how they
have organised things.

It would be very nice to have this kind of functionality in the TW.

Cheers

/Joe


On Thu, Mar 8, 2018 at 9:07 PM, 'Mark S.' via TiddlyWiki <
[email protected]> wrote:

> If you haven't tried to submit a document or document change to TiddlyWiki
> on github you should try it. It's not a user-friendly experience, even once
> you learn the ropes or have your own forked version set up.
>
> And that's not even getting to the part where you make a pull request. In
> order to make a PR, you have to "sign" the copyright or permission
> document. So that's how the IP issues are dealt with. And then each
> document and/or change has to await approval the same way it would if you
> were submitting a major change to the core.
>
> There's no accreditation given to contributors. Since github keeps
> everything I suppose there is some way of spelunking the depths to find out
> who made what change when, but it's not trivial.
>
> Creating a fork and making it semi-publicly available would quickly run
> into history problems I think. For instance, someone on the fork would
> submit a document about feature "A". Meanwhile, someone else would submit
> another document about feature "A"  and it then gets merged. When the next
> version of TW comes out and you try to reconcile the two trees, you now
> have two tiddlers about feature "A", that may be somewhat inconsistent.
> Which one is canon?
>
> All this is why having a real stand-alone wiki would be so much more
> expeditious. But it would take forever to populate if you couldn't grab an
> existing information source as a starting point.
>
> Thanks!
> -- Mark
>
>
> On Thursday, March 8, 2018 at 11:42:11 AM UTC-8, Steven Schneider wrote:
>>
>> Interesting discussion on the "definitive" TiddlyWiki. There has been
>> much talk here lately about documentation, community, etc, and this thread
>> becomes a part of it.
>>
>> In my view, the community of tiddlywiki users is, and always will be,
>> self-organizing. Though we all use different aspects of the community, I
>> would currently identify the following as elements of it (I'd be interested
>> in the aspects that I've missed):
>>
>> * *github*: https://github.com/Jermolene/TiddlyWiki5 --  - repo for
>> tiddlywiki5. I'm not an active github user, and don't participate in this
>> community at all. But there is activity: https://github.com/Jermolene/T
>> iddlyWiki5/pulse/monthly suggests in the past month, 21 merged pull
>> requests, 7 new issues. Perhaps someone here could elaborate on the ways in
>> which the community participates through github, especially for those of us
>> who are not active github users.
>>
>> * tiddlywiki *google group* (this group: https://groups.google.com/foru
>> m/#!forum/TiddlyWiki -- a long-lived group (first message available
>> <https://groups.google.com/forum/#!topic/TiddlyWiki/gaFdSTuQj0I> that I
>> could find is from 2005!), with ~6500 members. In February, there were 922
>> posts in 107 topics; January 1,329 (155)  and December 1,275 (143). In
>> March to date, there are 229 posts; about 3/4 of them have been written by
>> the 10 most active posters. (see https://groups.google.com
>> /forum/#!aboutgroup/tiddlywiki)
>>
>> * tiddlywiki dev google group: https://groups.google.c
>> om/forum/#!forum/tiddlywikidev.  1677 members, 165 posts, 25 topics in
>> February. Most active posters for March have some overlap with end-user
>> group. I don't read or write to this group; perhaps someone could elaborate
>> on what happens here?
>>
>> * tiddlywiki docs google group: https://groups.google.c
>> om/forum/#!forum/tiddlywikidocs. 92 members, relatively inactive most of
>> the time.
>>
>> * reddit: r/TiddlyWiki (75 subscribers) and r/TiddlyWiki5 (272
>> subscribers). (most posts by one user, the moderator
>> https://www.reddit.com/user/surelynotmymainacc/
>>
>> * twitter: https://twitter.com/search?q=%23tiddlywiki&src=typd
>>
>> I'm very interested in continuing to develop tutorials and guides and
>> help systems and better documentation etc.. In the spirit of tiddlywiki,
>> and in the spirit of open source software, we should just do it. There is
>> no real need to change tiddlywiki.com -- but if there were a group or an
>> individual user who wanted to modify / add on to the contents of
>> TiddlyWiki.com, it would be sort-of-easy.
>>
>> Perhaps one could use github, and allow folks to submit "pull requests"
>> (might not be the right term) that consisted of additional tiddlers built
>> within tiddlywiki.com. We could run a quasi-independent repository (
>> plus.tiddlywiki.com?) that included the current version of tiddlywiki.com
>> plus any additions "we" made.  Any one of us could do something like that,
>> and it might yield interesting results.
>>
>> As to Mark's question, is this kind of effort ethical or legal: I believe
>> it it fully in the terms of the license and spirit of open source software
>> generally and tiddlywiki specifically. Here is the quote from
>> https://tiddlywiki.com/#License: "you can take TiddlyWiki (meaning, I
>> believe: tiddlywiki.com) and do anything you want with it without any
>> license fee payment or other legal obligation to the creators of TiddlyWiki
>> or anyone else"
>>
>> I hope this was helpful to our ongoing discussion in this thread.
>>
>>
>> //steve.
>>
>>
>>
>> On Thursday, March 8, 2018 at 11:38:52 AM UTC-5, Mark S. wrote:
>>
>>> Setting up an independent Wiki about TiddlyWiki that could be updated in
>>> real-time would be an advantageous thing.
>>>
>>> What I've wondered, and asked before, is whether it is legal/acceptable
>>> to import the content of TiddlyWiki.com into such a wiki. If not, it would
>>> take years to generate comparable material.
>>>
>>> -- Mark
>>>
>>> On Thursday, March 8, 2018 at 4:45:38 AM UTC-8, Joe Armstrong wrote:
>>>>
>>>> A couple of questions:
>>>>
>>>> 1) Is there a "definitive" TW (definitive in the sense that it serves
>>>> as some kind of master
>>>> reference copy for  documentation of how TW works -- I'm assuming this
>>>> is at
>>>> https://tiddlywiki.com/
>>>>
>>>> 2) Every wikipedia has a Talk page - for discussions about a page.
>>>> This seems like a good idea - currently the only way to comment on a
>>>> page
>>>> is to make a better version and send a push request to github -- this
>>>> seems
>>>> a bit awkward
>>>>
>>>> Case in point :the SetWidget has an example saying
>>>>
>>>>
>>>> <$set name="myVariable" value="Some text">
>>>> <$text text=<<myVariable>>/>
>>>> </$set>
>>>>
>>>>
>>>> But the text says name is a variable - but the <<myVariable>> is a
>>>> macro expansion.
>>>> So here set has defined a macro. The Variable tiddler talks about
>>>> 'special types of variable'
>>>>
>>>> It might be difficult to explain this in the SetWidget tiddler itself
>>>> so one could have a convention
>>>> that (say) SetWidget-talk always had discussions about SetWidget
>>>> (somewhat like the Wkikpedia)
>>>>
>>>> Cheers
>>>>
>>>> /Joe
>>>>
>>>>
>>>>
>>>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/tiddlywiki/Fd53v6QTJao/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/tiddlywiki.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/tiddlywiki/6a10f737-b314-4d5b-af4f-dbc33271bb2e%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/6a10f737-b314-4d5b-af4f-dbc33271bb2e%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAL6cY6F9_DGhrKTy-VYMGyD8_AQjtwrwaxGx0narA0rctz19%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to