Mat, If those with more experience than me think Git is a useful way to do it, we need simplified documentation on how to use git to do this. Most people are unlikely to be experienced with Git unless they code in teams.
Personally I would be happy to build a series of tools to collaborate collate documentation info which is destined to be published by the proposed method. The team can harvest info from Google Groups, clarify and enhance, cross reference then publish. If I were doing it I would build a WordPress membership site, Wiki Media instance, Yammer forum or more to discuss the details or similar. Despite my experience, I have not being able to progress on GitHub this myself. Regards Tony On Wednesday, 13 December 2017 09:17:34 UTC+11, Mat wrote: > > @Jeremy and @TonyM > > Jeremy, in another thread you wrote out some of the standards you had use > to correct a doc-contribution I made. > > These are no doubt high standards and the result looks *great* - but few > can live up to these standards. It's a double edged sword. > > It sparks an idea - or maybe it's what Tony has been talking about; It > would be useful with an *unofficial* but still *publicly viewable > subdomain* - like http://unofficial.tiddlywiki.com for "potential docs" > and finge stuff that is not suitable for the main wiki! If possible, with a > github organization, separate from the main one, with its own Issue and PR > boards so it doesn't burden Jeremy. Is that even theoretically possible? > > <:-) > > -- 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/742861b6-d45a-42e8-8427-7162b8bbc4b3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
