Hello, I have been working on improving the process of creating with the goal of ultimately automating it (for now, it least eliminate the toil [1]). 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? ...
I started a code [2] 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 tickets: https://phabricator.wikimedia.org/T251371
My next plan is to actually make maintenance bot [3] add these and keep track of them and in the next steps it would start creating patches and close/create tickets too but writing this is quite exhausting and gerrit's API is no less than a disaster. Any help is appreciated!
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.
[1]: More about what "toil" is: https://landing.google.com/sre/sre-book/chapters/eliminating-toil/ [2]: https://github.com/Ladsgroup/Phabricator-maintenance-bot/commit/016fac156abd... [3] https://phabricator.wikimedia.org/p/Maintenance_bot/
Best
The template which creates the ticket text is < https://meta.wikimedia.org/wiki/Template:New_wiki_request%3E. So if you need it to be different in order to be able to process it better, you can also change it.
Am Di., 19. Mai 2020 um 16:16 Uhr schrieb Amir Sarabadani < ladsgroup@gmail.com>:
Hello, I have been working on improving the process of creating with the goal of ultimately automating it (for now, it least eliminate the toil [1]). 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? ...
I started a code [2] 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 tickets: https://phabricator.wikimedia.org/T251371
My next plan is to actually make maintenance bot [3] add these and keep track of them and in the next steps it would start creating patches and close/create tickets too but writing this is quite exhausting and gerrit's API is no less than a disaster. Any help is appreciated!
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.
[1]: More about what "toil" is: https://landing.google.com/sre/sre-book/chapters/eliminating-toil/ [2]: https://github.com/Ladsgroup/Phabricator-maintenance-bot/commit/016fac156abd... [3] https://phabricator.wikimedia.org/p/Maintenance_bot/
Best
Amir (he/him)
Langcom mailing list Langcom@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/langcom
Hi Amir,
Great news. This will can only smoth creation of new wikis.
Does this take into account the specificity of some Wikimedia projects ? (I'm thinking about the Proofread extension for the Wikisources but there is probably others).
Cheers, ~nicolas
Le mar. 19 mai 2020 à 16:16, Amir Sarabadani ladsgroup@gmail.com a écrit :
Hello, I have been working on improving the process of creating with the goal of ultimately automating it (for now, it least eliminate the toil [1]). 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? ...
I started a code [2] 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 tickets: https://phabricator.wikimedia.org/T251371
My next plan is to actually make maintenance bot [3] add these and keep track of them and in the next steps it would start creating patches and close/create tickets too but writing this is quite exhausting and gerrit's API is no less than a disaster. Any help is appreciated!
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.
[1]: More about what "toil" is: https://landing.google.com/sre/sre-book/chapters/eliminating-toil/ [2]: https://github.com/Ladsgroup/Phabricator-maintenance-bot/commit/016fac156abd... [3] https://phabricator.wikimedia.org/p/Maintenance_bot/
Best
Amir (he/him)
Langcom mailing list Langcom@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/langcom
Hey, @MF-Warburg: Thanks for the pointer. I might be missing something obvious but I can't find the way it produces the output for the ticket. Do you copy paste it from the template and manually replace parts?
@Nicolas: Not right now, I should try to take them into account when trying to automate patch creation but OTOH, these special bits always can be done after the wiki creation (You can enable Extenion:Foo and bar later). So not a super big deal I guess.
Best
On Tue, May 19, 2020 at 4:25 PM Nicolas VIGNERON vigneron.nicolas@gmail.com wrote:
Hi Amir,
Great news. This will can only smoth creation of new wikis.
Does this take into account the specificity of some Wikimedia projects ? (I'm thinking about the Proofread extension for the Wikisources but there is probably others).
Cheers, ~nicolas
Le mar. 19 mai 2020 à 16:16, Amir Sarabadani ladsgroup@gmail.com a écrit :
Hello, I have been working on improving the process of creating with the goal of ultimately automating it (for now, it least eliminate the toil [1]). 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? ...
I started a code [2] 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 tickets: https://phabricator.wikimedia.org/T251371
My next plan is to actually make maintenance bot [3] add these and keep track of them and in the next steps it would start creating patches and close/create tickets too but writing this is quite exhausting and gerrit's API is no less than a disaster. Any help is appreciated!
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.
[1]: More about what "toil" is: https://landing.google.com/sre/sre-book/chapters/eliminating-toil/ [2]: https://github.com/Ladsgroup/Phabricator-maintenance-bot/commit/016fac156abd... [3] https://phabricator.wikimedia.org/p/Maintenance_bot/
Best
Amir (he/him)
Langcom mailing list Langcom@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/langcom
Langcom mailing list Langcom@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/langcom
It's in the source code when you search for "PHABRICATOR LINK+PREFILL". The link with the prefilled text appears if status = approved, e.g. here: https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wiktionary_Konkan... (in the very last line of the expanded template).
Am Mi., 20. Mai 2020 um 12:06 Uhr schrieb Amir Sarabadani < ladsgroup@gmail.com>:
Hey, @MF-Warburg: Thanks for the pointer. I might be missing something obvious but I can't find the way it produces the output for the ticket. Do you copy paste it from the template and manually replace parts?
@Nicolas: Not right now, I should try to take them into account when trying to automate patch creation but OTOH, these special bits always can be done after the wiki creation (You can enable Extenion:Foo and bar later). So not a super big deal I guess.
Best
On Tue, May 19, 2020 at 4:25 PM Nicolas VIGNERON < vigneron.nicolas@gmail.com> wrote:
Hi Amir,
Great news. This will can only smoth creation of new wikis.
Does this take into account the specificity of some Wikimedia projects ? (I'm thinking about the Proofread extension for the Wikisources but there is probably others).
Cheers, ~nicolas
Le mar. 19 mai 2020 à 16:16, Amir Sarabadani ladsgroup@gmail.com a écrit :
Hello, I have been working on improving the process of creating with the goal of ultimately automating it (for now, it least eliminate the toil [1]). 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? ...
I started a code [2] 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 tickets: https://phabricator.wikimedia.org/T251371
My next plan is to actually make maintenance bot [3] add these and keep track of them and in the next steps it would start creating patches and close/create tickets too but writing this is quite exhausting and gerrit's API is no less than a disaster. Any help is appreciated!
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.
[1]: More about what "toil" is: https://landing.google.com/sre/sre-book/chapters/eliminating-toil/ [2]: https://github.com/Ladsgroup/Phabricator-maintenance-bot/commit/016fac156abd... [3] https://phabricator.wikimedia.org/p/Maintenance_bot/
Best
Amir (he/him)
Langcom mailing list Langcom@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/langcom
Langcom mailing list Langcom@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/langcom
-- Amir (he/him)
Langcom mailing list Langcom@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/langcom
Oh thanks! I see it now.
On Wed, May 20, 2020 at 12:21 PM MF-Warburg mfwarburg@googlemail.com wrote:
It's in the source code when you search for "PHABRICATOR LINK+PREFILL". The link with the prefilled text appears if status = approved, e.g. here: https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wiktionary_Konkan... (in the very last line of the expanded template).
Am Mi., 20. Mai 2020 um 12:06 Uhr schrieb Amir Sarabadani < ladsgroup@gmail.com>:
Hey, @MF-Warburg: Thanks for the pointer. I might be missing something obvious but I can't find the way it produces the output for the ticket. Do you copy paste it from the template and manually replace parts?
@Nicolas: Not right now, I should try to take them into account when trying to automate patch creation but OTOH, these special bits always can be done after the wiki creation (You can enable Extenion:Foo and bar later). So not a super big deal I guess.
Best
On Tue, May 19, 2020 at 4:25 PM Nicolas VIGNERON < vigneron.nicolas@gmail.com> wrote:
Hi Amir,
Great news. This will can only smoth creation of new wikis.
Does this take into account the specificity of some Wikimedia projects ? (I'm thinking about the Proofread extension for the Wikisources but there is probably others).
Cheers, ~nicolas
Le mar. 19 mai 2020 à 16:16, Amir Sarabadani ladsgroup@gmail.com a écrit :
Hello, I have been working on improving the process of creating with the goal of ultimately automating it (for now, it least eliminate the toil [1]). 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? ...
I started a code [2] 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 tickets: https://phabricator.wikimedia.org/T251371
My next plan is to actually make maintenance bot [3] add these and keep track of them and in the next steps it would start creating patches and close/create tickets too but writing this is quite exhausting and gerrit's API is no less than a disaster. Any help is appreciated!
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.
[1]: More about what "toil" is: https://landing.google.com/sre/sre-book/chapters/eliminating-toil/ [2]: https://github.com/Ladsgroup/Phabricator-maintenance-bot/commit/016fac156abd... [3] https://phabricator.wikimedia.org/p/Maintenance_bot/
Best
Amir (he/him)
Langcom mailing list Langcom@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/langcom
Langcom mailing list Langcom@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/langcom
-- Amir (he/him)
Langcom mailing list Langcom@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/langcom
-- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com “We're living in pieces, I want to live in peace.” – T. Moore
בתאריך יום ג׳, 19 במאי 2020 ב-17:16 מאת Amir Sarabadani < ladsgroup@gmail.com>:
Hello, I have been working on improving the process of creating with the goal of ultimately automating it
ENORMOUS THANKS!
(for now, it least eliminate the toil [1]).
Good example. This is indeed, Manual, Repetitive, and Automatable, as that page says.
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 [2] 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 tickets: https://phabricator.wikimedia.org/T251371
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 direction.
Hehe, I wasn't aware of that link at all – when I've been creating tasks, I've just copied previous tasks and substituted the necessary fields. Apparently I did it right since Amir's new script has understood them. :-)
Thank you very much to Amir S. for doing this, I think it's already a great improvement to the process. And I do believe the creation of the patches etc. could be mostly automated – I have done a fair share of initial config patches over the last year, and they're nearly always the same for each type of wiki, so it sounds feasible to me.
fre. 22. mai 2020 kl. 10:51 skrev Amir E. Aharoni < amir.aharoni@mail.huji.ac.il>:
-- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com “We're living in pieces, I want to live in peace.” – T. Moore
בתאריך יום ג׳, 19 במאי 2020 ב-17:16 מאת Amir Sarabadani < ladsgroup@gmail.com>:
Hello, I have been working on improving the process of creating with the goal of ultimately automating it
ENORMOUS THANKS!
(for now, it least eliminate the toil [1]).
Good example. This is indeed, Manual, Repetitive, and Automatable, as that page says.
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 [2] 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 tickets: https://phabricator.wikimedia.org/T251371
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 direction. _______________________________________________ Langcom mailing list Langcom@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/langcom
I started the ticket as subticket of the main epic: https://phabricator.wikimedia.org/T253439
I will pick it up soon.
HTH
On Fri, May 22, 2020 at 4:25 PM Jon Harald Søby jhsoby@gmail.com wrote:
Hehe, I wasn't aware of that link at all – when I've been creating tasks, I've just copied previous tasks and substituted the necessary fields. Apparently I did it right since Amir's new script has understood them. :-)
Thank you very much to Amir S. for doing this, I think it's already a great improvement to the process. And I do believe the creation of the patches etc. could be mostly automated – I have done a fair share of initial config patches over the last year, and they're nearly always the same for each type of wiki, so it sounds feasible to me.
fre. 22. mai 2020 kl. 10:51 skrev Amir E. Aharoni < amir.aharoni@mail.huji.ac.il>:
-- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com “We're living in pieces, I want to live in peace.” – T. Moore
בתאריך יום ג׳, 19 במאי 2020 ב-17:16 מאת Amir Sarabadani < ladsgroup@gmail.com>:
Hello, I have been working on improving the process of creating with the goal of ultimately automating it
ENORMOUS THANKS!
(for now, it least eliminate the toil [1]).
Good example. This is indeed, Manual, Repetitive, and Automatable, as that page says.
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 [2] 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 tickets: https://phabricator.wikimedia.org/T251371
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 direction. _______________________________________________ Langcom mailing list Langcom@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/langcom
-- mvh Jon Harald Søby _______________________________________________ Langcom mailing list Langcom@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/langcom