Archive obsolete repositories

[Jermolene]

Some of the repositories in https://github.com/TiddlyWiki appear to be obsolete. I propose to archive them, which will keep them available for access but make them read-only. See the docs for more details.

The repositories that appear to be obsolete are:

• https://github.com/TiddlyWiki/languages - @pmario I think this was yours?
• https://github.com/TiddlyWiki/php-server - empty
• https://github.com/TiddlyWiki/cooker
• https://github.com/TiddlyWiki/Poster - still active at https://tiddlywiki.com/poster/, but no further updates are planned
• https://github.com/TiddlyWiki/beta - appears to be an experiment

Please let me know if you have any thoughts.

[pmario]

https://github.com/TiddlyWiki/languages - @pmario I think this was yours?

TLDR; I'd like to create a "translators" team in the organisation, create some team repos and invite the maintainers of the French, Chinese and German version of the translations to join the corresponding teams and get that stuff going.

---

The idea, that it presents IMO is still valid. The main idea is, to have a local nodejs development server, that creates content for a landing page of community translations.

• It's about translations for tiddlywiki.com reference documentation
• There can be different teams for different languages
• Every team should have its own independent repo, where they have write access
  • Users can be part of more than 1 team if they know the language well enough
• For step 1 the version can be built locally and have to be manually pushed to be published
  • Only "main maintainers" can push
• For step 2 should be automated
  • a push to "main" will create a "pre-release like docs page" with an unguessable URL if needed
  • The URL can be sent to contributors with automated actions
  • a push to "live" branch will replace the live version of the page
  • Only "main mantainers" can push to "live"
• There should be 2 "live" versions
  • A single file wiki, similar to tiddlywiki.com -- Untranslated content will show up in English
  • A static version of the wiki, that may look completely different.
    • It only contains static html pages with no JS and only the CSS needed

The test landing page the I did envision looked as follows. The page below is created from a nodejs wiki and built with tiddlywiki edition/xxx --build static

Click to see the: Test landing page


Edit: The repo also contained a working development environment, with "live reload", "live rebuild" and so on. (The code is now outdated and would need to be rewritten. But the concept still works)

[YakovL]

I think /beta and /cooker can be archived right away (TWC no longer uses cooker); /php-server may be used for MainTiddlyServer, especially if somebody wants to help me adapt it to TW5 as well; no idea about /Poster and /languages. There's also some initiative to update /translations [for TWC], but currently I can't provide enough help to make it progress, that repo also requires restructuring.

[Jermolene]

Hi @pmario

A couple of thoughts. I am committed to keeping TW5 in a monorepo. The key advantage is that there's no confusion about which version of one repo matches the version of the other repo. A consequence is that the authoritative versions of the translations must reside in the main TW5 repo. That in turn means that mechanisms such as the one you describe must ultimately end up by sending a pull request to the main TW5 repo (and of course we could automate merging "trusted" translation PRs).

In terms of this repo, it feels like it's a bit experimental to be in github.com/TiddlyWiki. Would it make sense to move it to a personal repo until we get to the point where we're considering adopting it officially?

Hi @YakovL

I think /beta and /cooker can be archived right away (TWC no longer uses cooker);

Done.

/php-server may be used for MainTiddlyServer, especially if somebody wants to help me adapt it to TW5 as well;

Given the fact that it's empty I'm inclined to delete it. I think we can always recreate it if needed.

no idea about /Poster and

I've archived that one too.

/languages. There's also some initiative to update /translations [for TWC], but currently I can't provide enough help to make it progress, that repo also requires restructuring.

No problem, thanks for all your hard work. I'm sorry I've not been able to support you better.

[pmario]

I did remove it. I do have a copy in my ropo

[Jermolene]

Thanks @pmario!