In T341599#11502003, @Mathglot wrote:

Random note: I casually stumbled into the fact that Special:Impact is translated to Especial:Incidencia. Incidencia means incident in spanish. Which is far from the correct meaning for the page. Is this something to rise with the community? Or maybe @IZapico-WMF can make the change if it's not problematic?

Sidebar on translation:

Yes, it is the wrong word, but I sort of see where it came from. Incidencia also means "incidence" in Spanish, which is an epidemiological term which measures the rate or frequency of something and in that sense, where a researcher might write about the incidencia de la influenza in a journal, they might talk about the impacto de la gripe to a group of secondary school educators. I suspect that that (or something like it) was behind the choice of incidencia.

However, it is still the wrong word, because incidencia measures something bad (disease, etc.) and Special:Impact measures something good (streaks, total edits, thanks), and because incidencia only has that meaning in academic jargon, and our terms should be more familiar, common terms for a general public. Even though translators must always be on the lookout for false friend traps, impacto is the right word in this case.

As of May 8, 2025, eswiki has 20 mentors enrolled in Mentorship, with 2 of them in Away status. Considering that 24 mentors are needed to provide support to 100% of the new accounts, these 18 active mentors could already support at least 70% of the new accounts.

I suggest to wait for the release of invitation lists to eswiki. Our Event Organizers policy does not include any reference to invitation lists, so I believe is preferable to wait while we define the best approach.

The admin who will grant the organizer right to @vaughnwalters after the release will be @Raystorm.

This is also happening in eswiki.

Thank you @Urbanecm_WMF It looks good enough to me.

Thank you @Urbanecm_WMF. The autogenerated list looks good to me. Also, as we commented in our meeting, I would add the following section titles:

• Galería
• Galería de imágenes
• Fase final
• Estadísticas
• Palmarés
• Ránking
• Ranking
• Estadísticas
• Obra
• Obras
• Obras destacadas
• Obras seleccionadas
• Filmografía
• Filmografía destacada
• Filmografía seleccionada
• Películas
• Discografía
• Discografía destacada
• Discografía seleccionada
• Novelas
• Novelas destacadas
• Novelas seleccionadas

For Spanish, a more accurate translation is: Configuración comunitaria

It seems that this problem is related to a gadget called "Disabled the typography refresh".

Hello Martin. Here is my username for eswiki beta: IZapico test. Thank you!

Just FYI, in the latest weeks, some users from es.wp has made me the same request, to have a persistent link, especially in long articles, to jump to the top of the page.

A few days ago, a similar conversation took place among es.wp mentors in a Telegram group. They find confusing that experienced users (even admins) appeared in their Mentorship dashboard. They believe it adds noise to the mentor and could be even feel like "offensive" for an experience user to be assigned a mentor (that potentially can have even less editing experience as the mentee).

Hello all. Thank you very much for all the work behind this idea. I believe I am arriving late to this discussion, but in case it helps, I was reviewing the designs, and I also believe that it is more convenient to create the Help module and have it also available along the Resources module. So, my vote for Option 1.
But, since the new module will be placed at the bottom of the page, I am afraid that some mentors never would become aware of it. That is why I was thinking that maybe the first time a mentor accesses their mentorship dashboard after the Help module is deployed, a dismissible notice message could be displayed at the top, informing them of the existence of the new module (similar to Option 2).

Users of eswiki had reported in this thread the same issue happening with both Monobook and Legacy Vector.

In case it helps, yesterday this image was suggested to add in this article that already has the same image, with the same format (jpg) but with different file name. Also, the suggested image was cropped, so it is slightly different from the original one included in the article.

I have been suggested for praise a mentee that not only has all their edits reverted but it is already permanently blocked. Block accounts should not be suggested for praise neither.

When testing the section image suggestions in Spanish, some of the suggestion are being repeated after completing them before (and not skipping them). For example, this is one of the articles/section repeated and the image suggested is always the same.

At eswiki, during the current discussion to deploy Vector 2022, user:Dodecaedro is reporting to experience the same issue: after opting-out from the compact list, the language list remains the same as when the compact list is activated (when using Vector 2022 as skin).

In case it helps, some users (see the threads here and here) are reporting that, when there is not additional languages related to an article, it should be possible to add interlanguage links also from the Language menu since, in those cases, the menu title is "Add languages".

It was also reported to happen on tewiki at the DI talk page.

On es.wp and pt.wp we seem to have the same problem:

Regarding the list of praiseworthy mentees preselected at eswiki:

• User:MaryTory seems to not have yet enough relevant praiseworthy edits.
• User:Mary Fortuny belongs to my UG (which means that I guide and praiseworth her personally in our in-person meetings)
• User:ProyectowikiMNCN also belongs to my UG (in this case, she attends the online sessions)

In T220139#8591389, @kostajh wrote:

Thanks for sharing that perspective.
A possible simpler alternative is to dynamically update the bar chart, so if your account is less than 24 hours old, we'd show 3 days for the bar chart, and once it's more than 3 days old, we'd show 7 days, and once it's more than 7 days, we could show 30; once older than 30, we'd show the default 60 days. That might be less complicated than providing a dropdown option for configurability and hopefully address the demoralizing aspect to this for newcomers?

I find very interesting the possibility to show less than 60 days to offer a more customize experienced for newcomers. Especially to those who have just registered a few days (or hours) ago, maybe can be frustrating and demotivating to see a empty 60-day bar with only 1 day of activity. On the other hand, an empty bar could be seen as a goal (or challenge) for them to "complete", but still, I find that 2 months could be seen as too far away and difficult. By decreasing the number of days to be closer to the real number of the days of activity, user can feel that the experience is more real and personalized and the editing goal is more accessible.

In Spanish Wikipedia, I am finding different situations:

• The article is very short in Spanish, and since it already has an infobox with an image, does not need more images. In these cases, I am selecting "Section should not have an image".
• When the suggested image is already used in an equivalent section in other language, sometimes the content of that section is different in Spanish, so it could happen that there is no point in suggesting/adding that image. In these cases, I am selecting "Not good"
• The article itself has already many images similar to the one suggested and, when the section is very short, there is no point in adding an image, since the article itself has enough. I am choosing "Section should not have an image".
• Sometimes, the image suggested is already in the article. Eg. this article and this image.
• In the original article, images are part of a graphic or table (like this one). In Spanish, it could happen that images are not used in the same schema, so there is no point to add just one. I am selecting "Section should not have an image".
• The same article is suggested more than one time (like this one).
• IMO, a number (or date) should not be the trigger to suggest an image.
• Many times, for a Demographics section it is suggested an image related to a landscape. For example, in the article Condado de Letcher it was suggested t[[ https://commons.wikimedia.org/wiki/File:View_from_Pine_Mountain_(Kentucky).jpg | his image ]] in the Demographics alleging that is also used in the same section in the enwiki article (which is not true). Probably, that image would fit better in other section.
• In some cases, like in this article, the image is suggested in a wrong section (in this case, Condecoraciones when would have more sense in the Later life section).

In T327287#8542877, @kostajh wrote:

Would it be possible to share the username of this newcomer, to help us debug? When (with timezone) was this screenshot taken?

In T327050#8533965, @kostajh wrote:

@KStoller-WMF @Urbanecm_WMF @Trizek-WMF would it make sense to automatically drop inactive mentees after a certain period of time, e.g. 3 months? So, not just to hide them on the dashboard, but to update the database to remove the relationship with the mentor. If those mentees return, they would be re-assigned a new mentor at random, so there wouldn't be continuity, but that probably doesn't matter since they were inactive for so long.

Thank you Benoît for opening this task. At es.wp, some mentors that joined before the deployment of the mentorship has reported they feel overwhelmed because the huge amount of mentees they have assigned. They already know they can reduce the amount of mentees that would be assigned to them (and, indeed, some of them change to "less than the average"), but still the number keeps growing.

In my opinion, with 16 consolidated mentors (although 3 of them are away these weeks) eswiki is already prepared to increase the percentage of mentees receiving mentorship. So, I can retake the conversation to check if the community (and mentors) agree with us. I am adding the topic to the list of our next ambassadors meeting.

I believe is a good plan what you said Benoît. We do not want to overburden mentors (specially those who experienced the first pike), so let's take it easy. I find very reasonable to increase to 50% when 17 mentors (33/2 rounded up) will signup. I will let you all know once we achieved it.

@Etonkovidova indeed it was disabled. I have activated "Enable the editor help panel" now and finally Add a Link and Add an Image work properly again.

Yes, I used the same browsers with the other account and always in the same visible mode. None adblockers are activated. And, just in case, I have tried now in incognito mode, and everything works the same. I have also tested it from my mobile (iOS 15).

I have deactivated all my gadgets and beta functions and the problem is still happening (tested in Chrome, Firefox and Safari, both with Vector 2010 and Vector 2022). With another account where the tools were working normally, I have activated all the gadgets and beta functions and both tools keeps working well.

Hi @kostajh. In my browser console appears the last line you can see in these images after completing one of the task. Now I am deactivating my gadgets one by one trying to figure out where the problem could be... but with no success so far. If I find something I will inform it here. Thank you.

Thank you very much for your help! The pads look perfect, and we are very happy to know that the "restorePad" feature already exists :)

Hello. I have received some feedback from the es.wiki community. I have compiled it in this document.

Please, take into account that the event name now is "#1Picture1Article", so it is necessary to update it at the headline: "Te damos la bienvenida al evento #1Picture1Article".

Hi, we have just received the style guide and the designs.

Request made to Spanish Wikipedia newcomers. Waiting for feedback.