Twinkle bugs are not tracked on this phabricator: They are tracked on GitHub.

@MMiller_WMF @Trizek-WMF: It's done as far as I can see, forgot to update you.

Meh, ok. Make it public please, though, so I can reference it on oth

Controversy-related Maintenance Templates

[source]

Verifiability-related Maintenance Templates

[source]

I plan to finish this earlier than the Due Date but modified the Due Date to not clash with my Wikimania preparation w/r/t banks & co. @MMiller_WMF Is the new Due Date acceptable for you?

The word counter said 237 excluding the trailing dots, and I guess (the trailing) three dots makes the total 240 chars.

The screenshot above displays 'what happens when it is too long'. Unassigning myself.

As I read, that is the intent.

Looks like it is stripped at around 237-9 chars.

Question: page name to control the mentor list is same on Beta, right?

Probably of your interest (Cc @Trizek) : https://korean.stackexchange.com/questions/5399/does-korean-make-use-of-italic (just Korean)

In T227221#5327291, @Legoktm wrote:

Proposed fixed version: P8739

If it is too big to fail (as in revert), can we get the functionality back in any possible way? It is also too big to fail for our workflow.

I can see a spike (for last few days to weeks) with someone pretending to be WMF department, employee, contractor, etc etc using the form to spam our queue and (to distribute automated reply to them).

We discussed this while ago (maybe search for checkin logs) and italic in Korean language is in most cases (almost always) inappropriate.

And just like the cross-wiki notifications I would like to have 'no discourse notifications on MW' — I don't use cross-wiki notifications because I consider one wiki's notification to that wiki only and this also applies to MW-DC as well.

LGTM as long as the custom texts can be removed by someone else in case of abuse... and since it seems to be configurable via wikipage it looks good to me

Submitted per @sbassett.

I don't know the exact reason why it is not archived, but I think most plausible reason is, in mailman, it is virtually tooooooo hard to erase stuff once archived, and cu-l is full of sensitive information under ANIP and/or to comply with Data Retention Policy.

Q: Does discourse support 'mailing list mode' with NO archives left after it is distributed? At least, that's how it works on checkuser-l.

No opposition for 3-4 weeks, proceeding.

For Korean Wikipedia either own line or just after the last paragraph is both fine. If you just want to follow cswiki rules on kowiki, that's fine from kowiki perspective.

Can I also be added to zulip for testing? (Email address (my phab handle)@(my phab handle).wiki)

This is quotes from my email on stewards-l

• No loss of log while my device is sleeping.
• No dependency on 3rd party tools to browse logs.
• No requirement for a new program to use it.

Point 1 and 2 is inter-connected as if you don't need to browse 3rd party logs to browse logs you probably don't lose logs when you disconnect at one point and then reconnect later.

Kosta is correct.

In T224930#5239143, @TheDJ wrote:

@Billinghurst well it's not a production level tool, so outages like these are to be expected.
/me whispers something about technical wishlist

No consensus at stewards-l, one suggesting Mailing list and other one (in conphrence) suggested use of somewhat chat-like system contradicts, so the best conclusion I can draw is no consensus for anything right now.

@jcrespo please consider sending an email to global-renamers - at - lists.wikimedia.org in case of improvements like this -- which everyone will love.

AFAICS VisualEditor was never enabled on Portal NS on Korean Wikipedia (by searching, tho). If you want to enable it, you need community consensus to do so.

ACK, just in time as June is coming! xD

@Aklapper I've started a discussion on stewards-l, it might take a bit of time. (Maybe worth a new task, indeed.)

CA is for locking the account, so I thought it would be related, but if it isn't, then it's my mistake :P

In T224059#5202149, @Legoktm wrote:

Locked users can't use the form if we require a login...

On a somewhat related note, please add Commons as a "tags" section and not "subscribers". Not everyone becomes member of "Commons" project to receive a bugmail on every ticket. Thank you!

Was done on the day it was merged but all of us forgot to close the ticket.

Disabled https://phabricator.wikimedia.org/p/Yyn1312/ for vandalism on trust-and-safety board (and I see vandalism on his SUL account).

I make heavy use of IRCCloud (for more than 5 years) but I would prefer something other than IRC due to it being inferior with netsplit and etc.

In the absence of official logging feature: Disabled https://phabricator.wikimedia.org/p/Mr.deVega/ for vandalism (If someone think it is fine to restore access pls do)

Cannot repro as of now so just closing.

For files that a user has contributed themselves, there should be a file page functionality/button that initiates the deletion of geolocation data from WMF databases (not the image itself)

Possible duplicate with T118024: When deleting StructuredDiscussion content, deleted content is misattributed to the sysop that deleted it?

Can't find the right project so adding Wikidata for WD team flagging :-0

Can I get an attention from Ops? Seems like this is not eligible for Puppet swat as an apache config changes and preferred way to get SRE attention is to add Operations in the ticket. (Note the target page does not exist yet and has to be moved by me or other meta admin because it is fully protectd)

I recall a request in 2018 that I had to defer to someone else because it was closed and I did not have local account there. Chatted with @Legoktm back then but if this is doable I think it should be done — in the future we might not have a steward with access to that closed wiki.

If we are really worried about showing cipher-ish error messages to newbies, maybe show the current fail message with an "advanced" button to show the real error (abusefilter, read-only, whatever)?

See also T56883: Create redirect for kr.wikimedia.org to https://meta.wikimedia.org/wiki/위키미디어_대한민국

I think we can manage with that, since we can easily look over which NS has that name (or ask people who know that language).

Looks good to me, I'll bring this to internal discussion.

As far as I can see, almost everyone who took part in the discussion (about 10 participants [or more] excluding me) has said they want to see "partial" block information in the CA workflow. I think individuals can say what they think if they are inclined to do so.