@Ladsgroup Should be done :).

Conversion transcripts:

Patch got +2'ed, moving to QA.

I added in a table that covers what each of the feature flags does – hopefully that makes it easier for others to chime in whether each of the flags is needed or not. When making a decision, please note that we should probably only remove feature flags that we're fully certain we will never need again (in other words: we should only remove feature flags for features that became an essential part of Growth features at all wikis, including French Wiktionary). This is because potentially re-adding the feature flag again (after we remove it in this task) would be more costly than maintaining it along the way.

I decided to split the GrowthExperiments follow-up to T367720: GrowthExperiments CommunityConfiguration: Add minimum and maximum validation constraints to applicable fields, as this task reached some state of completionness. I did this mainly so that I could fill a bug (T367721) I just found in the merged patch in a meaningful way. Since there is nothing else to follow up here, closing as Resolved.

Done. FWIW, I rephrased the beginning of both messages to not say "Communities can", as that is a phrasing that makes sense at eg. project pages (which address multiple communities at once), while the interface messages only address a single user, rather than multiple users (or communities) at the same time. This is how it looks with my patch applied:

Moved from sprint to sprint a couple of times, resolving.

Moved from sprint to sprint a couple of times, resolving.

Uploaded a patch, but...the descriptions (both current and new) already have some problems. For example:

In T367619#9895092, @JFernandez-WMF wrote:

Some types of Newcomer Tasks are surfaced through maintenance templates. Articles containing those templates are added to the Homepage's Suggested Edit feed. To see how many articles are available for each type of task, see this page.

@KStoller-WMF, do you know which link should be attached in 'see this page'?

Thanks for catching this! Uploaded a patch that should fix the problem.

Will be verified within T367330: GrowthExperiments: Do not expose configuration for unavailable features from Community Configuration.

In T367516#9893845, @Michael wrote:

Is this effectively part of the contingency plan from T350731: Community Configuration: Monitoring & Contingency plan?

Collecting patches that should be deployed during the release at https://gerrit.wikimedia.org/r/q/hashtag:%22communityconfiguration-deployment%22+(status:open%20OR%20status:merged).

Heads-up: I filled T367576: Ensure ORES topics are not loaded through legacy CommunityConfiguration code for the MediaWiki:NewcomerTopicsOres.json migration.

Based on the T359185#9790649 discussion, I think it makes sense to go with option 2 and move the configuration to server configuration, as @Michael suggested on the other task.

I think we should start on this fairly soon (ideally before all-wikis deployment, although we can delay that if needed), so that we can verify the migrated structured mentorlist works more easily.

Not ready yet.

Thanks @KStoller-WMF!

Resolving as part of cleaning up tasks assigned to me. The rows were dropped, DBAs pinged as requested. Not sure if the optimisation @Marostegui mentioned happened, but if not (and we need to track that), feel free to reopen this task (reassigning to someone else) or fill a new one, as appropriate.

Per a discussion with @Michael, I will take over the PoC uploaded by @Michael and finalise them into mergeable code. Thanks for the investigation here!