On Sunday, March 19, 2017 at 10:45:39 AM UTC+1, Thomas Elmiger wrote: > > I am not aware of automated publishing of > https://github.com/jermolene/tiddlywiki5 for example. >
... That doesn't mean that it's non existent ... > What TW5 is lacking is a publishing process including Github. And with it > endless versioning, rollback, diff, roles for authors and publishers, > multi-user capabilities, commits with comments, … > Right! I did set up a proof of concept (POC) [1] last year for the first TW meetup. It's a continuous delivery process using travis-ci.org [2]. ... I did create an experimental landing page [4] for the "Multi Language Documentation" project. [5][6].. The landing page itself has a blog like structure. It should have some basic "teaser" texts and link to the real tw versions eg: [5][6]. The POC defines some Major Goals [7], which imo are essential for a newly created "Community Page" that is not TW. The only real problem we have here is, the github pages DNS setup for tiddlywiki.com [8] .... The repo structure would need to be changed, in a way that is controversial and therefore stalled since a year. I know that there are attempts to add some of these to TW5 – why not use > existing external solutions? (As an option. ... > Because we have a fully working prototype solution! @Jeremy and "UnaMesa Associaton": Can the community use the domain *tiddlywiki.org*, which could be linked to a completely new github organisation. Or do we need to create a new one. tiddlywiki.info seems to redirect to tiddlywiki.com atm. ... Until TW5 can take over.) > TLDR; As I wrote. Restructuring the current structure / process is a controversial topic between me and Jeremy. So we "agreed to disagree" atm ;) -------- For this to happen, we need to convince Jeremy, that we need some project restructuring, where we have an "upstream" repository, which is the CI-CD build master and the Jeremolene repo is a contributor as everyone else. .. He can have the final say on everything "core related" ... but the community stuff, is totally in control of the community groups and the whole integration and delivery process is fully automated! ... including tiddlywiki.com IMO the manual build process, that Jeremy uses at the moment [3] is very work intensive and only works for his local development setting. Imagine a documentation wiki, lets call it “TW5 Cookbook”, where every TW5 > user can contribute or improve recipes. Via Github. As soon as an update is > confirmed (merged) by a member of a certain group (on Github) it is > published to a website via a completely automated process. > Yea... see [1]. The workflow used at the moment is: If something is pushed to "master", "gh-pages" will be updated. It could be improved, like this: - If someone creates a PR pull request, a temporary page will be automatically created, for validation and testing - no tiddlyspot pollution with "throw away TWs" needed anymore. - The availability will be posted to eg: gitter chat [10], which has excellent github integration - Discussion can happen there [10] or directly within github-issues [11]. Depending on the users preferences. - If the PR is legitimated, it will be pushed, and automatically delivered. I think such a concept could cover several topics discussed in many posts > about the (lack of) central ducumentation. > You are right. ... But only for those, who are willing to join github. My language- github repo looks like this [12] ... That's the repo I have to use to create my PRs against the upstream repo [1]. > Have a nice sunday! > Thomas > Sure :) have fun! mario PS: I'll try to record a little video, how this stuff can be used. It will show one full development cycle, from editing stuff to the published content. ... If I can keep it short enough. [1] https://github.com/TiddlyWiki/languages [2] https://travis-ci.org/TiddlyWiki/languages/ [3] https://github.com/Jermolene/build.jermolene.github.io [4] http://classic.tiddlywiki.com/languages/static.html [5] http://tiddlywiki.com/languages/de-DE/ [6] http://tiddlywiki.com/languages/fr-FR/ [7] https://github.com/TiddlyWiki/languages#major-goals [8] https://github.com/TiddlyWiki [9] https://en.wikipedia.org/wiki/Continuous_delivery [10] https://gitter.im/TiddlyWiki/languages [11] https://github.com/TiddlyWiki/languages/issues [12] https://github.com/pmario/tiddlywiki-languages -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/aca99669-bddb-44b5-8f20-ec063b8b26d0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
