Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
“We're living in pieces,
I want to live in peace.” – T. Moore
בתאריך יום ג׳, 19 במאי 2020 ב-17:16 מאת Amir Sarabadani <
I have been working on improving the process of creating with the goal of
ultimately automating it
(for now, it least eliminate the toil ).
Good example. This is indeed, Manual, Repetitive, and Automatable, as that
The most exhausting (the toil) part of creating new
wikis is keeping track
of all of the moving parts, Is CX working? Is DNS entry deployed? ...
As for CX, I've just checked with Kartik, who is the cxserver deployment
guru, and he says that it can be done early, before the wiki is created.
(Although I guess that ideally it should be done right when the wiki is
created, not much earlier and not much later.)
I started a code  that takes a bug id like (like T251371) and outputs
all of the steps in pre-install and post-install if they are done or not.
If you noticed, I have been adding this to bottom of the new wikis creation
Is there a task where you track this particular work of yours? If not,
perhaps you could document it at https://phabricator.wikimedia.org/T158730
What I want to ask from langcom is to keep in mind that this code parses
the text they put in the tickets they create to find out for example if the
new wiki is a Wikipedia or a special wiki because it seems you're using a
template. Do not change that pattern please, or at least let me know if
you're changing it.
In my dream, all of this necessary info is entered in a well-structured
_form_, rather than a loose template, and then everything is done
automatically, so that people don't have to create a lot of tasks and
patches. But I guess that strict usage of a template is a good step in that