@Urbanecm_WMF -- since we decided today to deploy the dashboard with only the first module ready, I was thinking it would be good to at least include a link on the dashboard for mentors to navigate to the signup page (since they won't have anything like that until the second module). Is it possible to add this?

The next step for this task is to scope it, so that we know when it's appropriate to work on. Therefore, I'm putting it in Ready for Development for scoping.

@sdkim and I talked about when this is needed, and we think that generating this in mid-August, say August 17, will work fine for the Platform team. It would also potentially be possible to re-generate closer to Growth's deployment near the end of September.

@mewoph @RHo -- I also think there's an argument for showing this dialog even when the user has that preference off: we're discarding changes in a situation where the editor would reasonably expect them not to be discarded. Since changes are usually preserved when the user toggles between VE and source editing, they would probably expect them to be preserved between suggestions and VE. But we don't do that, and I think therefore it is good to give them a warning.

Hi all -- I'm sorry for being late to this task, but I do want to follow-up on whether the Growth team's GuidedTour popup still works as expected with this change. I'm assuming that we should check from our perspective. @Etonkovidova, could you please check it?

@Urbanecm_WMF -- that looks good to me. And it sounds fine to link to mw:Talk:Growth as @Trizek-WMF recommends. You can proceed toward deploying this addition.

Thank you @Miriam. I pasted the results from the spreadsheet below so that they're quicker to look at. I remember you told me that these counts only count the specific "citation needed" template -- not any of the other templates mentioned by @Trizek-WMF in T279606#6987071.

Thanks everyone for discussing this! It sounds like this is something important that we could sort out better synchronously. In terms of timeline, it sounds like we would want to decide how to proceed within the next three weeks, given that we want to load the data to Search by mid-August (T285817#7218640). I'll connect with some of you offline about next steps.

Thanks, @Jdlrobson. I'm having trouble reproducing this on my own, so it would be helpful if you could give me a sense of how pervasive and impactful this issue is. What do you think?

@ovasileva @Jdlrobson -- thanks for pointing this out. I have a couple questions:

In the future, we'd like to be able to filter by source type, e.g. only show Wikidata-based recommendations (which tend to be significantly more reliable).

@kostajh -- thank you for filing this and including that useful list. @MGerlach is going to be doing research in the coming months about this whole space, and so these links might be useful for him. Here's the project page we created about it: https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Structured_tasks/Copyedit

@mewoph -- okay, hearing that @RHo wants to be able to distinguish those two actions, let's add a new event for the new button.

@MPhamWMF -- thanks for checking. This task depends on its parent (T285816: Add an image: generate static file of suggestions), because the static file needs to be generated before it is loaded. Ideally, we generate the static file as soon as possible to when we deploy this feature to users so that they can experience the freshest data. That said, we'll also want the data to be present for some of our engineering and QA periods. Therefore I think we should plan to generate and load the data in mid-August, say August 17. How does that sound to you (and to @sdkim)?

@RHo -- okay, so just to make sure, the proposed solution is still to simply remove the button when an edit card is displayed? Hopefully that will be simple to implement.

@Etonkovidova -- I think what you're saying sounds fine. Ideally, we only want the "Suggested: add links" tag on those edits that are really adding links through our workflow. But what I would expect to see is the "Reverted" tag on the first edit in your screenshots (since they were undone in the second edit). I wonder why that's not there?

@Aftabuzzaman -- thanks for checking in about this. I believe that this change we've made is only going to affect the evaluation of future articles. i.e. as users proceed through the existing suggestions and complete them, the system generates new ones. Those will not contain these terms that we want to exclude. Therefore, you'll still see these during the time it takes them to cycle out and new ones to cycle in.

@nettrom_WMF -- thanks for explaining. I think basing this on May 2021 will be just fine.

@mewoph -- I think I can answer your instrumentation questions, but @nettrom_WMF and @RHo please correct me if you think differently.

We've done this and decided to proceed with the full mailing on July 19. The next set of analysis will take place in T286796: Donors to newcomers: analysis.

@mewoph -- @RHo and I think this might be a good improvement to work on in the next couple weeks. Could you please reply with a quick assessment of the difficulty of this work and any issues you foresee?

@Urbanecm_WMF -- thank you for reading closely and double-checking. The English text that's currently in production is out of date. I've updated my comment above to include the English original, and now all three languages should match in that comment. I'll also put them in the task description.

@Urbanecm_WMF -- we now have the translations for this special version of the account creation page. Could you please insert them so that they are live in production? We need this by the end of the day on Tuesday, July 12 (tomorrow):

Regarding the CentralNotice and SiteNotice banners, I do not think we should take any action on those. I know we want to put our best foot forward for this test, but banners are ongoing issue that are in front of newcomers inside and outside this test on all our wikis -- they're a normal part of the environment. If we want to do something to suppress banners on the homepage, I think that’s something we should do holistically, unrelated to the Fundraising test. @RHo -- do you think we should create a task about that? Could you please?

@Urbanecm_WMF -- could you please attempt something for this task, and then show @RHo and me a screenshot here so we can see how it looks and feels before it gets deployed?

@RHo -- we can ask Miriam for that number, but given that we're unsure whether we'll incorporate the multiple suggestions into our experience, we wanted to err on the side of including them in the API.

For our future reference: these are interesting notes from User:Bilorv about potential improvements to the impact module.

@mewoph -- thank you for this attention to detail. Are you saying that "Switch editor" is the copy that comes with VE and was already there before we started this work? If so, I think we should leave it the way it is now and not make an exception for our workflow. I'm imagining that a user who might have encountered that invisible label in the conventional editing experience might be looking for that same label in this one as they search for the same control.

@kostajh -- @Urbanecm_WMF identified this issue in T284800: Donors to newcomers: URL parameters, and I think it's something that should be fixed via this task:

The issue that @Urbanecm_WMF pointed out is something we should fix. I'll say so in T285281: Donors to newcomers: go straight to homepage.

@mewoph -- the invisible label should be "refresh suggestion". And yes, it is fine to cycle through the ten options. I'll change the task description to include these specifications.

@mewoph -- based on today's discussion, it seems like this should be assigned to you and In Progress. Is that correct? If so, please make those changes to the task. Thank you!

@kostajh @Tgr @nettrom_WMF -- I just updated the description with the two URLs that Fundraising is going to use.

@EBernhardson -- thank you for fixing this. Do you know approximately what the time period was when users experienced this? We want to note it for our analytics.

@Tgr -- as Platform works on this new version of the API to support our first iteration of image suggestions on the web, they say it would be helpful for you to spend some time with the previous proof-of-concept API to provide any feedback on performance or the format of the data that comes back.

This problem does not affect all wikis. After checking 28 wikis that have Growth features, here is what I see:

I just tested things out on frwiki, plwiki, and fawiki, and here's what I see from the desktop user's perspective. This is on fawiki:

@Trizek-WMF -- could you please create a separate task for Spanish Wikipedia's deployment so that we don't forget about it?