@nettrom_WMF -- per our conversation, I added a date of October 7 to this as a target. We said we could pull data at the beginning of October, and that analyzing it would be faster and easier than doing it for help panel. We can adjust this date as needed.

@nettrom_WMF -- per our conversation, I've added "edit count/volume" as one of the KPIs we want to look at, in addition to activation and retention. I also added "non-reverted edits" as a something that would be interesting, but not a high priority.

Thank you, @Dyolf77_WMF, for doing such a thorough job. I'm going to leave this task open as we continue to work with the spreadsheet. The next step (as described on the parent task) is for an engineer to count up how often each template is used.

Thanks, @Urbanecm. This looks good! I'm going to leave it open as we continue to work with this spreadsheet. The next step (as I wrote on the parent task) is to count up how often each of the templates is used.

Now that the ambassadors have created the spreadsheet listing their wiki's maintenance templates, we want to know how many articles are tagged with each one. I'm moving this to Ready for Development because it may be easiest for an engineer to query this from the database. The outcome we have in mind is a a column in each tab of the spreadsheet counting how many articles have each template.

This investigation is ready for development.

This investigation is ready for development.

A note from a conversation with @nettrom_WMF -- in analyzing the newcomer tasks impact, we may want to look at non-reverted edits, as opposed to just edits. The feature directly causes edits, but the question is whether they are valuable edits for the wiki.

FYI @Cntlsn, I deleted the row about the mentor introductory message being in quotes, because we have a more complex rule: it should be in quotes if the mentor wrote it, but not in quotes if it's the default message (since the default message is not a quote).

This is good in production. Thank you!

Because the team is prioritizing "newcomer tasks" (T227728), this additional module would not be a priority until later in the year (if at all).

Because the team is prioritizing "newcomer tasks" (T227728), this additional module would not be a priority until later in the year (if at all).

Because the team is prioritizing "newcomer tasks" (T227728), this additional module would not be a priority until later -- but could be a priority in Q2 for research and design.

Because the team is prioritizing "newcomer tasks" (T227728), this additional module would not be a priority until later in the year (if at all).

Because the team is prioritizing "newcomer tasks" (T227728), this additional module would not be a priority until later in the year (if at all).

Because the team is prioritizing "newcomer tasks" (T227728), these additional modules would not be a priority until later in the year (if at all).

Though some sub-tasks remain open, I'm closing this parent task because we have deployed the mobile homepage.

We have designed and deployed the initial version of the homepage.

Thanks for filing this, @Etonkovidova. I just looked at the numbers, and it looks like of all the users who have visited the homepage so far, 0.4% visited from Safari 10 on desktop or mobile combined. Therefore, I am going to decline this, since that number will only go down over time (it is unlikely that Safari 10 will become more popular in the future).

Thanks, @Urbanecm. This is very closely related to T228210, because a user's mentor could likely come from a program they're in.

@Urbanecm -- thanks for filing this. I see this idea as part of a larger idea to integrate the newcomer homepage with community programs. I think a great flow would be if a user takes the welcome survey, says they're part of a program, and then ends up looking at a newcomer homepage all about that program, including a mentor who is part of the contest. We'll think about that as the newcomer homepage gets more advanced. In particular, we want to see how newcomers interact with mentors, and whether they develop ongoing relationships with mentors, or if they just ask one question.

Thanks for filing this, @Trizek-WMF. We'll need to wait to see if this becomes a widespread issue for many users before spending any time with it, so I'll put this in "Revisit".

A couple notes:

This is now opening for me in mobile view. Thank you!

Thanks for the reminder, @kostajh. At Hackathon, I learned from @Bmueller that @daniel worked on the German help panel, and we could potentially ask him for help if we need it at some point. This is the project page: https://de.wikipedia.org/wiki/Wikipedia:Teestube/Konzept

@Dyolf77_WMF -- if this looks good to you (now that the train is arriving), you can resolve the task.

@kostajh -- how common is this? What percent of users are not getting a mentorship module?

Looks good. Thank you!

@kostajh @Cntlsn -- thanks for discussing this. I'll change the specifications in the description to forego the "X" to close the banner.

I'm moving this straight to Ready for Development because it is an issue that may well be affecting a lot of users, and it is higher priority than some things in that column.