First mayor re-structuring of the live notes and transcribed post-its.
Fri, Nov 15
Wed, Nov 13
Just poking the fact, that there are probably some useful ideas on what could be done in the field of code review in the action items from T234662: Wikimedia Technical Conference 2019 Session: Integrating contributions from other teams or volunteers.
Following the good example of @Physikerwelt I just submitted an un-conference session where some of us could try to implement ideas generated above. Just poke me if you're interested. :-)
Tue, Nov 12
Just a quick short notice update for people interested. - If you find the time, you could take a quick glimpse at some of the tickets linked above that already dealt with that topic before. ( You can also do that afterwards obviously and add thoughts later.)
Sat, Nov 9
Wed, Nov 6
Tue, Nov 5
Thanks for the feedback.
Mon, Nov 4
Sun, Nov 3
Fri, Nov 1
Thu, Oct 31
Just as a random note here for the case it's relevant: There's a patch still waiting for review and an already merged patch, that are both not part of the latest ( released ) version 1.9.0.
Tue, Oct 29
In the spirit of transparency and participation, here's the next step to further define the session. I gathered some "key" questions that we could try to answer in the session. Again feel free to comment, extend and favor.
Mon, Oct 28
I extended my comment above to show examples for the different aspects of contributions I identified in this first exploration.
Fri, Oct 25
For this session I see roughly the following areas that could be addressed. We might want to focus on some of these beforehand or try to figure that out during the session. Also it might be, that some other session is covering some of this. I have not checked everything there yet ( and probably the other sessions will also begin to from more over the next days )
Isn't this sort of the same as T234660: Wikimedia Technical Conference 2019 Session: Code Health/Code Review?
Thu, Oct 24
Just as a first collection...
Wed, Oct 23
I haven't seen sectionTitles returned in the labs compare endpoint output. Even if we aren't passing in section byte offsets yet, I would expect an empty sectionTitles array. This makes me think 1.9.0 doesn't include my latest changes to output section titles for each diff line: https://gerrit.wikimedia.org/r/#/c/mediawiki/php/wikidiff2/+/539906/
Tue, Oct 22
I would say the investigation is done.
Mon, Oct 21
I just checked and it seems, wikidiff2 is really not installed on TranslateWiki. I'll remove the tag. - ( using wikidiff2 might solve the issue ;-) )
Oct 2 2019
Sep 30 2019
@Pikne the task description reads as if this is concerning the FileImporter - so Move-Files-To-Commons should be the correct tag. - Or is something similar happening with the Two-Column-Edit-Conflict-Merge feature? :-)
Hello! We are starting to ramp up on session creation for the 2019 Wikimedia Technical Conference. If there is no longer anything remaining to do here please close this task to avoid confusion.
Sep 10 2019
Aug 26 2019
The same also works on commons with the "normal" title change page.
The above PoC gives a good rough understanding for where changes to display the refined parts must happen. The parameter itself could easily be forwarded to the model and then used in the code printing the preview.
Aug 23 2019
Aug 22 2019
Some things were done here already to wrap up the technical aspects of the gendered categories feature. Keeping this task open for questions that might come in from @JStrodt_WMDE when working on the communication part of the topic.
What happens if a page with book references is opened with the VisualEditor
Using the current PHP only PoC patch, the VE cannot make sense out of the refines attribute in the ref tag and introduces new footnote entries for these tags in the WYSIWYG preview :-(
@WMDE-Fisch please undelete this file when you have a moment: https://commons.wikimedia.beta.wmflabs.org/wiki/File:File_moving_to_Commons2.png
This is a zombie created by the importer, we should be able to learn things from the ruins.
Aug 21 2019
Aug 16 2019
And here's the line responsible in Scribunto:
So looking into the pages affected it seems, this was always happening on pages in the Module namespace, what makes sense since we do not have a preview button when editing modules there. - I'll add a patch that checks if the button exists before we try to disable it.