[Thoughts] To Github or Not -- Is it even a Question?

53 views
Skip to first unread message

@TiddlyTweeter

unread,
Jul 20, 2019, 6:20:35 AM7/20/19
to tiddl...@googlegroups.com
Its been very interesting. I got into PowerShell, with Mark S., to try design/make an additional "restore" mechanism (a "universal" approach to saving TW) that works for any browser that additionally already does Backups, Zip Archives, Restores and "Parrots" (parrots are cloned wiki to a secondary location) automatically. (Its called "Polly" after the parrot that repeats itself). 

It is going well.

An issue that came up has been about code repositories. To do GitHub for it.

But this is likely the ONLY thing like this I will ever do. So my question to myself was--should I have to learn GitHub lingo--issues, pull requests etc? 

My conclusion is "don't bother!" 

TW itself can handle the display of code changes if you use a versioning plugin. 

This is a small project with two people doing active work, and its about Windows tools, not TW directly.

But I thought it was an interesting question to what extent you can use TW to record itself? 

For TW to be its own development environment?

Best wishes
Josiah

@TiddlyTweeter

unread,
Jul 20, 2019, 7:54:50 AM7/20/19
to TiddlyWiki
Repeat for email ...

TonyM

unread,
Jul 20, 2019, 8:13:49 AM7/20/19
to TiddlyWiki
As usual Josiah you ask the questions many of us ask our selves. I would like to get into github myself but it takes some bandwidth with variable return depending on the project and the number of potential contributors (not end users).

However for sometime I have included sdk or software development kit and software development environment as features of tiddlywiki. And features we can develop further.

In some ways I take this too far because at the end of a development phase I need to start a new wiki because it contains too many development tools.

I am gradually packaging these so I can import them when I start and remove them when finished. Tiddlywiki permits one to import tools, improve them during the development process, then export them for use In the next project. Basicaly each project inspires and captures innovation in the development process.

If we can improve multiuser contributions github may be unnessasary at least for 1 to 3 contributors.

Regards
Tony

Reply all
Reply to author
Forward
0 new messages