Talk:Tech/News/2017/06

Tidy[edit]

Hi, Johan (WMF). I think the Tidy item is wrong. One can understand that if his wiki has 0 errors in this list, the site is ok. But the list shows only a little part of the problems that should be fixed. IKhitron (talk) 19:19, 2 February 2017 (UTC)[reply]

IKhitron: Indeed, that's what I tried to say with the last two sentences: "You can see if your wiki still has something to fix here for one HTML problem. This list does not cover all problems." You think this needs to be more clear? /Johan (WMF) (talk) 19:33, 2 February 2017 (UTC)[reply]

I don't know. For me, the last sentence is the opposite than the one before, so it's confusing. Maybe I'm wrong. IKhitron (talk) 19:36, 2 February 2017 (UTC)[reply]

OK, I'll revisit this at latest before it's sent out again tomorrow and see if I can make it clearer. /Johan (WMF) (talk) 19:38, 2 February 2017 (UTC)[reply]

Thanks. Please think about replcing "for one HTML problem. This list does not cover all problems." by "for one of the possible HTML problems." or something like this. IKhitron (talk) 19:40, 2 February 2017 (UTC)[reply]

Thanks for the suggestion. Also (partly as a note to self when I look at this later), Elitre has suggested it shouldn't convey a sense of urgency in the way she currently perceives it, so I'll look into that too. /Johan (WMF) (talk) 20:01, 2 February 2017 (UTC)[reply]

Hi Johan (WMF), Tidy replacement will be enabled by default only after we have confidence that we have addressed the majority of issues. The current description ("Tidy will be replaced") might alarm people unnecessarily. Secondly, self-closing tags should be fixed, but it is the one problem that has already been addressed very well by editors PLUS we have backward compatibility workarounds in the parser to handle them. So, it would be better to use the scarce real estate of Tech News to flag all the other things that need fixing by pointing directly to https://www.mediawiki.org/wiki/Parsing/Replacing_Tidy#Detailed_information_about_what_to_fix instead. SSastry (WMF) (talk) 04:37, 3 February 2017 (UTC)[reply]

For context, this is the original request, posted elsewhere: Lego created this dashboard to track progress on one of the steps for mw:Parsing/Replacing Tidy: https://tools.wmflabs.org/wikitext-deprecation/ Most communities are set, but some have more than a thousand pages that need to be fixed. It's not a sortable table, so it's not easy to grab a list of the ten with the most problems, but at a quick glance, I believe that arwiki, fawiki, idwiki, kawiki, thwiki, euwiktionary, lawikitionary, and hewikisource all have more than 2,000 pages to fix – and ocwiki leads the list with an astonishing 37,000+ pages to fix, and mswiki is in second place with 17,000 pages in the category. (It's category-based, so the problem may actually be bigger than it looks.)

Could a link to this tool be provided, with some encouragement to check your home wiki and make sure that these errors get fixed soon? Whatamidoing (WMF) (talk) 18:19, 2 February 2017 (UTC)[reply]

She has good points that some wikis do have a huge backlog, so I believe an item about this makes sense. Just, when replacing Tidy is mentioned, we could add "later this year", so to underline that this is only a first step in a process. My 2c! Elitre (WMF) (talk) 09:26, 3 February 2017 (UTC)[reply]

You're right, Whatamidoing (WMF), 37,682 pages in ocwiki is terrible. So I spent half an hour from my life and fixed 37,661 of them. IKhitron (talk) 17:03, 3 February 2017 (UTC)[reply]

You're awesome, IKhitron. Thanks for doing that. Whatamidoing (WMF) (talk) 18:30, 3 February 2017 (UTC)[reply]

IKhitron (talk) 18:53, 3 February 2017 (UTC)[reply]

Subbu, I think we need a series of announcements. This is the easy one, and the "news" is that there is now a one-click way to check for problems on my favorite wikis, so it makes sense to start with this one. Whatamidoing (WMF) (talk) 18:30, 3 February 2017 (UTC)[reply]

FYI to all here, I spent a couple of weeks cleaning up templates on some of the wikis listed on the report. The vast majority the pages listed as having errors, including almost all of the 37,000 pages on oc.WP (there are currently just 11 pages listed there), were cleared out of the error category by fixing a hundred or so templates. Legoktm helpfully added a link to the affected templates for each wiki, which sped up the process. There are some fully protected templates left to fix, along with some that I have not figured out yet.

Unfortunately, we are still blocked by task T157670. Pages are still appearing in the en.WP error category; here's one that appeared a couple of days ago. I found many templates on non-English wikis that had errors but had not made it into the error category yet. Also see this discussion for links to more blocking bugs. Jonesey95 (talk) 22:24, 27 February 2017 (UTC)[reply]

Ping Whatamidoing (WMF): ^. /Johan (WMF) (talk) 22:37, 27 February 2017 (UTC)[reply]

Hey Jonesey95 :) Thanks for all the work so far. Do the relevant Phab tasks include the necessary information? The Parsing team does a good job at following them. Thank you. Elitre (WMF) (talk) 07:44, 28 February 2017 (UTC)[reply]

I believe that the phab tasks contain the information needed to describe the various problems. Some of them are not linked to the "Replacing Tidy" task tree, though. That might be something useful to do. Whatamidoing (WMF) has been helpful and communicative on en.WP, especially at the discussion linked above and at this page. Jonesey95 (talk) 16:09, 28 February 2017 (UTC)[reply]

I've asked for timing information at phab:T157670. I think it might make more sense to carry on the conversation there. Whatamidoing (WMF) (talk) 17:26, 2 March 2017 (UTC)[reply]