[tw] Re: [TW5] Documentation Contributors Edition

Hi Metabele, > It seems that downloading JSON files from a Google group is easier for a > moderator than visiting a list of blogspot wikis and, attaching a JSON file > to a post is easier for a contributor than creating and updating a blogspot > wiki. > Actually, it complicates things, as yo

[tw] Re: [TW5] Documentation Contributors Edition

Hi Jeremy On Thursday, 24 September 2015 13:44:04 UTC+2, Jeremy Ruston wrote: > > Hi Matabele > > The process of exporting a tiddler to a .tid file, then attaching this >> file to a post on this forum is fairly straightforward. >> > > Another possibility is to use the "export all" button in the

[tw] Re: [TW5] Documentation Contributors Edition

Hi Matabele The process of exporting a tiddler to a .tid file, then attaching this file > to a post on this forum is fairly straightforward. > Another possibility is to use the "export all" button in the sidebar tools tab to export a JSON file of just the changed tiddlers. Looks to me that the T

[tw] Re: [TW5] Documentation Contributors Edition

Hi The process of exporting a tiddler to a .tid file, then attaching this file to a post on this forum is fairly straightforward. A possible interim solution: 1. Publish a periodically updated TW5-docs version from where contributors can obtain a fresh copy (as you have already done here.

Re: [tw] Re: [TW5] Documentation Contributors Edition

Hi Jeremy, > During the next cycle we shall return to the usual situation where I can > push content changes as they happen. > That is good to know! Best wishes, — tb -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this

Re: [tw] Re: [TW5] Documentation Contributors Edition

I think I've said before that the problem with recent content updates is that a mistake that I made at the start of 5.1.10 means that I can't update tiddlywiki.com content until the next release. During the next cycle we shall return to the usual situation where I can push content changes as the

[tw] Re: [TW5] Documentation Contributors Edition

Hi *@Mark S.*, On Wednesday, September 23, 2015 at 3:26:51 AM UTC+12, Mark S. wrote: > > On a technical note, with the new process won't tiddlyspot become > cluttered with dozens or hundreds of "dead" TW's after a year or two? > As I mentioned earlier

Re: [tw] Re: [TW5] Documentation Contributors Edition

Thanks *@Jeremy*, I was composing a long reply to *@Mark S*, linking to those previous discussions, but you replied before I had finished, making my reply moot. Here's the link instead to Jeremy's previous post on this issue.

[tw] Re: [TW5] Documentation Contributors Edition

I didn't find the Github process too arduous. What was problematic was waiting many weeks before simple, innocent documentation changes showed up or even were pulled. Apparently, documentation is treated as code (maybe because it's mixed in with the code). It doesn't seem like the proposed syst

[tw] Re: [TW5] Documentation Contributors Edition

Hi Birthe, > A desirable feature is the ability to see line-by-line diffs for the > changes, and perhaps to be able to easily export a JSON file of the changed > tiddlers. > I suspect something like this already exists outside of TiddlyWiki in how Jeremy handles translations, although I woul

[tw] Re: [TW5] Documentation Contributors Edition

Hi Tobias You are right. I think it has to be made as simple as possible, not to add unnecessary workload on the person (I suspect Jeremy], who would have to collect the documentation suggestions. That would explain: > A desirable feature is the ability to see line-by-line diffs for the > cha

[tw] Re: [TW5] Documentation Contributors Edition

> > We'll see what Big J says ;-) > I think we're going to take one step at a time. In other words, I don't see an automated aggregate-contributions-and-provide-a-workflow-to-figure-out-what-to-merge-and-how-and-why-thingy coming up soon. These things never turn out as "simple" as one would

[tw] Re: [TW5] Documentation Contributors Edition

On Wednesday, September 16, 2015 at 5:50:28 PM UTC+12, Mat wrote: > Yeah. Unfortunate, but please don't forget that whatever IS working is > thanks to individuals just like you and me here in the community - with the > addition that they've really put in their heart to build something for us. >

[tw] Re: [TW5] Documentation Contributors Edition

On Wednesday, September 16, 2015 at 7:07:37 AM UTC+2, Hegart Dmishiv wrote: > > Oh boo, I've just found out that uploading a TW wiki to TiddlySpot, at > least the first time, requires the Google Chrome browser. > Yeah. Unfortunate, but please don't forget that whatever IS working is thanks to i

[tw] Re: [TW5] Documentation Contributors Edition

On Wednesday, September 16, 2015 at 6:52:27 AM UTC+2, Tobias Beer wrote: > > First of all, this is a very helpful idea and shall simplify both the > process of documentation as well as distributing the results. > > I believe, after having made edits, one would submit the contributions > to...

[tw] Re: [TW5] Documentation Contributors Edition

> > I definitely won't be installing Google Chrome browser on my home computer. > Consider either of these: - chromium - srware iron — tb -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" grou

[tw] Re: [TW5] Documentation Contributors Edition

Oh boo, I've just found out that uploading a TW wiki to TiddlySpot, at least the first time, requires the Google Chrome browser. Everything "Googlish" that I use at present, starting with my Gmail email account, Groups, Google+ profile, Drive, and even their link shortner, I've only started usi

[tw] Re: [TW5] Documentation Contributors Edition

Hi Mat, I believe, after having made edits, one would submit the contributions to either a GitHub issue or a groups post, whereas the former is more easy to track for Jeremy while the latter might take longer to get picked up and processed. At that point, nothing should be done with that wiki

[tw] Re: [TW5] Documentation Contributors Edition

@Mat, it would seem to me that, once the merge is completed, your own TiddlySpot wiki would need to be purged and replaced with a fresh one, downloaded again from TiddlyWiki and uploaded to your own TiddlySpot, containing all the merges from yours and other documentation editor's work, before y

[tw] Re: [TW5] Documentation Contributors Edition

Interesting idea! :-) The idea is that a would-be contributor would clone this edition to > TiddlySpot (step-by-step instructions forthcoming), and then make their > changes, saving them back to TiddlySpot. I, or anyone else, can fairly > easily then pick up the wiki and extract the changed ti