@Eee888 Can you put the current placeholder text from the commit in the description (explaining where each message is used), as well as any messages without placeholder text?

Okay, I think I know what it is.

Current patch has:

Can not reproduce.

I didn't really mean it should be free text, just that we shouldn't limit to a fixed set (e.g. not only 1, 3, and 7).

@ssastry It's not a bug per se, but basically Parsoid uses relative links starting with .:

In T168387#3365100, @Mooeypoo wrote:

• Do we have a set range of options to choose from, or a free-text number with days?

Added a note to description, about cancelling a scheduled event.

"Needs Review" means there is an associated patch.

It doesn't look like there's a clean way to delete existing jobs. We might be able to edit them with deduplicateRootJob, but I don't see a way to delete them or list them (which has already been mentioned). So we might want to go back to a DB-based solution.

As stated in the description, this (still) works. It should have been closed back then.

We'd like @jmatazzoni to come up with text for this.

It is configurable (wgLearnerEdits, wgExperiencedUserEdits, wgLearnerMemberSince, wgExperiencedUserMemberSince), but it's not actively configured (all the wikis use the same values).

This might be a duplicate, but not sure.

@aaron What kind of performance guarantees does getReleaseTimestamp have?

This is needed for T2582: Remind me of this article in X days, an active Outreachy project.

Please hold off on this temporarily.

Also, we need to confirm with Ops about Redis persistence (from T158239: Improve GettingStarted data storage strategy, "Persistency on redis (and replication) has always been guaranteed as best-effort, which doesn't seem to be great in this case.") We may need a new instance.

In T158572#3046973, @Trizek-WMF wrote:

That nesting issue is known. That's why most category-searching tools have a parameter to limit depth in search. After, filtering is irrelevant. Would it help?

By 'notification types', do you mean 'web' and 'email'? (The terminology here is poorly standardized, but you can call it a "notification method" or "delivery method". Notification type is something else).

Flow (though it impacts MF)

wgRevisionId (from https://www.mediawiki.org/wiki/Manual:Interface/JavaScript) is 0. This is an issue in itself, and also the cause of T91886: the message mobile-frontend-last-modified-with-user-just-now appears unnecessarily on the top of Flow mobile web pages (hence why this is a subtask of that). However, T91886 could probably workaround this.

In T165540#3323678, @MZMcBride wrote:

@Tgr: I'm struggling to see how you filing this task, reviewing https://gerrit.wikimedia.org/r/355875 with a +1, and then merging the changeset yourself (+2) is kosher. You have a pretty clear conflict of interest with respect to this change.

Even if you hadn't filed this task and reviewed the changeset, both you and @Mattflaschen-WMF are both partisan crusaders for establishing this code of conduct. How is it ethical for you two to be making changes like this to any repository?