Task description update
ADDING:

• As @Sdkb shared on mw.org here in the context of the New Discussion Tool:
  • Newcomers are not clear which call to action ("Edit," "Add topic" or "Ask a question") they ought to use to ask the question they came to ask.
  • It can be difficult for newcomers to post questions that comply with conventions considering 2 out of the 3 potential workflows ("Edit" and "Add topic") do not offer them any kind of guidance?

Potential test question
@Parkywiki noted [i] how at en.wiki's Teahouse, many newcomers mistakenly add the question they are wanting help with to the page via the "Edit" button. In doing so, they end up adding said question to the end of an unrelated topic.

Call for feedback
I've drafted announcement we'll use to invite feedback on Office wiki (limited access): https://office.wikimedia.org/wiki/User:PPelberg_(WMF)/sandbox#Talk%3ATalk_pages_project%2FNew_discussion.

In T265499#6576500, @Esanders wrote:

WFM on en.wiki

Note: next steps on this ticket are blocked on outcome of the conversation happening on fi.wiki here: https://fi.wikipedia.org/wiki/Wikipedia:Kahvihuone_(sekalaista)#New_Beta_Feature_next_week.

I'm boldly closing this considering @dchan already reviewed the spreadsheet and Noam's contract is likely to have finished by now.

We still need some concept of sub-sections so that watching a parent section notifies you about comments in subsections

@matmarex can you describe how these "define" the boundaries of a topic? E.g. Does the software consider topic to be bounded by ==H2==?

! In T247139#6568676, @ppelberg wrote:
...we can reflect the decisions we come to in a single comment here and then any necessary changes to the task description.

The decisions @MNeisler and I came to are summarized below; the task description has been updated to reflect the changes resulting from these decisions.

In T247139#6526794, @ppelberg wrote:

REFINEMENTS

1. Are people publishing the replies they start?

• CHANGE how we are measuring the comment completion rate so we can understand the full comment funnel. Said another way, we'd like to know:

✅ We're going to measure the edit completion rate such that we can see at what steps in comment funnel people might be dropping out.

• ADD grouping by experience level for each of the above

✅ We're going to measure this.

• ADD grouping by editing interface – source and visual – for each of the above
• ADD a baseline of the above for full-page wikitext editing so we have a baseline to compare to.

✅ We're going to measure this.

2. Are people abandoning the replies they start?

• REMOVE

❗️We're not going to measure this.

3. Are people satisfied with the feature?

The thinking below is based on the thinking we did in T249386#6283682 .

• ADD how many people posted a comment with the tool on only one day?

✅ We're going to measure this.

• ADD how many people posted a comment with the tool on ___ (see grouping below) distinct days:

✅ We're going to measure this.

• ADD % of talk page edits people make with the Reply Tool, grouped by experience level and platform.

❗️We're not going to measure this.

• ADD the number of people who are posting varying numbers of comments with the Reply Tool:

✅ We're going to measure this.

• ADD how many distinct people have explicitly turned off the Reply Tool preference (name: Enable quick replying) in Special:Preferences

✅ We're going to measure this now that T260867 is resolved.

In T265953#6562579, @ppelberg wrote:

@Whatamidoing-WMF: I've started drafted the selection criteria in this sheet (also linked in the task description): Talk pages project/Partner wiki selection.

@matmarex are you able to verify the patch is working as expected?

In T265499#6569142, @ppelberg wrote:

@Esanders notes: the JS will only work on wikis that do not have DiscussionTool enabled in any way (e.g. it can not be enabled as a Beta Feature or an opt-out user preference).

I'm boldly resolving this task for now.

In T261423#6571195, @Esanders wrote:

We should probably change the mobile editor preference to be a database-stored user preference, rather than using localStorage.

Here is a ticket for what you are describing: T266304.

@Samat, are you able to share links to the, "...the guidelines and the common practice on some projects..." you are referencing in the task description?

In T238332#6565723, @JTannerWMF wrote:

@ppelberg to check to see if this is still and issue based on the steps in Bartosz's comment

In T206278#6565739, @JTannerWMF wrote:

@ppelberg will see if this is still happening and determine if it can be closed

In T178976#6565748, @JTannerWMF wrote:

@ppelberg will test this task

Static image of an audio player seems to be appearing:

Task description update
I've added the "Questions" we will seek answers to and the "Context" we will share alongside those questions to the task description.

Assigning this to @Esanders to determine what changes this new API is implementing and what – if any – corresponding changes will be made in VE to support it/them.

@Esanders notes: the JS will only work on wikis that do not have DiscussionTool enabled in any way (e.g. it can not be enabled as a Beta Feature or an opt-out user preference).

In T260467#6562080, @DLynch wrote:

There's a label, it's defined with:

"tag-discussiontools-newtopic": "Add topic",
"tag-discussiontools-newtopic-description": "User added a new topic to the page with DiscussionTools",

Roger that – thank you, David.

In T247139#6566410, @MNeisler wrote:

@ppelberg - I reviewed the task scope and suggested refinements.

For ease of editing, I copied the workflow scope and refinements into a google doc. My revisions are noted in my comments and suggested changes in the doc. Let me know if you have any questions.

In T265446#6568278, @Zache wrote:

In T265446#6566619, @ppelberg wrote:

Deployment timing
Note, the Reply Tool was not made available as a Beta Feature at fi.wiki today, 20-October, as previously planned.

This happening is blocked on us, the Editing Team and volunteers at fi.wiki, coming up with a way resolution to T265291.

Your comment was a little unclear. Does this mean that you are actually doing something for the problem with ETA or that fiwiki should change the policy before you are ready to deploy?

Ah, I'm sorry about that. [i]

@MNeisler, what you shared in T263050#6565226 makes sense to me and sounds good.

Deployment timing
Note, the Reply Tool was not made available as a Beta Feature at fi.wiki today, 20-October, as previously planned.

@Whatamidoing-WMF: I've started drafted the selection criteria in this sheet (also linked in the task description): Talk pages project/Partner wiki selection.

Task description update
I've added the following to the task description's ===Done section:

• Editing Team to provide code review for newly instrumented events

Thank you for pulling this together, @MNeisler. A few comments and clarifying questions in line, below...

In T265291#6557326, @Zache wrote:

! In T265291#6557038, @ppelberg wrote:
With the above said, we'd like to experiment with the Reply Tool not outputting any content/syntax that people did not explicitly type themselves to start.

So technical options are

1.) for old wikieditor to changes to wikitext syntax which is not plausible(?)

• @Zache are you able to describe what you are referring to above in a bit more detail? I want to make sure I'm understanding what you are saying before responding.

Notes from this morning's standup

• @Esanders can you check in the code to see whether a label has been defined for the 'discussiontools-newtopic' tag? And if so, what the label has been defined as?

Neat use of custom stylings for conversation topic headings at it.wikipedia:

Italian Wikipedia custom talk styling
Link: https://w.wiki/hA4