After inconclusive new proposals and consultation of current stakeholder on Telegram, we will stick with the logo already in use since several weeks.

Thanks @Urbanecm for this informative feedback.

Logo includes a stylized human stick figure, overlaid on a circle, similar to da Vinci’s Vetruvian man. It is freely inspired by Wikimedia official logo and UN Accessibility logo. The body is dark red, shaped like a K rotated 90 degrees right, arms spread wide. The head hands and feet are represented by simple blue circles. The semi circle underneath is green. The red, blue and green colors of Wikimedia projects were chosen as representing the 3 colors of light.

Extracted from https://etherpad.wikimedia.org/p/202106-accessibility

Related discussion on Wikidata: https://www.wikidata.org/wiki/Topic:Vm9zvq0po46t93bl

Wow @Yair_rand thanks for the link to the Lua translator, that's really cool. 😄

Kubof sugested that we organize some challenge/competition to motivate people to contribute.

@Aklapper the idea went to my mind as I was about to create the Telegram channel https://t.me/wikimedia_accessibility so at least here.

Here is a first idea to move toward such a logo: go through Commons to find some SVG logo on accessibility we might might with Wikimedia official logo.

Note that this comes in the frame of Hackathon 2021, more specifically https://phabricator.wikimedia.org/T282561

So the Etherpad did play its role during the session. 😄

We will take note in https://etherpad.wikimedia.org/p/wmhack21-accessibility if needed 😄

Hello, so here we are: https://meta.wikimedia.org/wiki/Requests_for_comment/Resolve_massive_copyright_infrigment_on_Wikitionary_in_Esperanto

In T283143#7097754, @Aklapper wrote:

Removing All-and-every-Wiktionary as this is not about all Wiktionaries; please see its name and description

Thanks @Robin_van_der_Vliet for the feedback. It seems that @Taylor took the expected actions on these pages, and that's seem good to me (not as good as if we had instead free material to share on the topic of course).

Novaĵoj kaj malnovaĵoj pri PIV, Bertilo kaj kopirajto (16 jan. 2021 by @Taylor) is also related to this topic.

A conversation on this topic was launched on Esperanto Wiktionary.

Hello @Nes, it's done, you might have a look to check I didn't introduced any problematic error. 😄

In T265290#6576489, @Zache wrote:

I created a discussion on the wikidata project chat for defining the community side of the process.

• https://www.wikidata.org/wiki/Wikidata:Project_chat#Updating_SPARQL_federation_input_review_process

Also note that ⌃+⏎ , which is also widely used in instant messaging tools, do send the message as one already acculturated to this shortcase might expect. Actually, after a quick check, it is already implemented with a proper accesskey and title on the button. Sorry for just making noise then. 😅

In T271773#6741437, @Tacsipacsi wrote:

The full page editor also offers Alt+⇧+B (or whatever modifiers the browser offers for access keys) to jump to the summary field from everywhere on the page. If this is implemented, it could work regardless of whether the advanced part is open (and thus offer a way to easily open it), although not a crucial feature once the tab stop works.

Here are some sample relevant links from a quick research on LimeSurvey and code injection:

• https://snyk.io/vuln/SNYK-PHP-LIMESURVEYLIMESURVEY-1074897
• https://bugs.limesurvey.org/view.php?id=6543
• https://bugs.limesurvey.org/view.php?id=6548
• https://bugs.limesurvey.org/view.php?id=15680
• (the official bug tracker have many more report like the three later items)

By the way @Chicocvenancio, what about making most popular module preinstalled?

Thank you for the feedback @Chicocvenancio.

Oups, my bad, actually, despite the error message, it works. I guess that the error are related to some admin (wheel) specific stuff that aren't really required to make a module installed in a functional manner.

Actually, while the command does try to install the missing module, it fails to successfully do so:

Great, thank you @Chicocvenancio ❣

A related thread was launched on Commons Do we want to bot-copy descriptions to captions?, following the introduction of structured data integration on the project.

Well, @Xqt, except if there is a way to tweak the generator to use the provided list of page as target, this still doesn't provide a way to do what I wanted with this script. In the midtime I however successfully used ./pwb.py replace -file:./targets/acceptables.txt "Images from Wiki Loves Love 2019 to check" "Accepted images from Wiki Loves Love 2019" -automaticsummary -always to do what I wanted.

Ho, actually it seems that the move subcommand don't allow to provide a list of target as add does, but like remove will only work on the complete list of items in a category. So it doesn't give out of the box what I was looking for, as I had supposed in my initial description. But the evolution proposal seems still valid to me.

Yes, the email is still valid, if you can also send me the email subject here once sent, that might help find it more quickly in case it get catched by one of the many filter of my email client 🙏😁

Hello everybody, would it be possible to know how much time in average it takes for such a ticket to be treat, so we can take that into account in how we organize?

The Wikitrace project on Meta was created in link with this ticket.

Done for WLL. Thank you for pointing the need. :)

I think it's a good practice to put a template layer between the module API and the the article, it brings much flexibility. Not adding it in the VE default layout might actually be presented as a "feature not a bug". Not bothering article writers with too much technical complexity is great.

Hi @Aklapper, is there something more I should do to make this ticket go forward?

I re-open the task, as from my understanding of the documentation this is a legit action from my part as the task creator, all the more when questions are pending.

Hi @Lydia_Pintscher , I join your concern on not wasting valuable resources.

Maybe Extension:TextExtracts might help somewhat here, but at least from the documentation it doesn't appear to be usable through wikicode calls. A more invasive solution would be to use Extension:Labeled Section Transclusion which requires to explicitly mark each element that should be extractable.

So to answer a few questions I received in feedback to this ticket:

In a first time, I mean on fr.wikitionary, as I'm prototyping data separation from displaying layer there. If that happen to work well, we can see with other wiktionaries later, does that make sense.

Clicking the link toward https://riot.im/app/#/room/#mediawiki-general:matrix.org respond me that the channel doesn't exists. Maybe I need some additional configuration though. I already accepted a spontaneous request by Freenode to join what I guess was a bridge, maybe on my laptop client (Fractal), but I guess that anyway it's synchronized in the browser client and it's not the problem.

On the Wikisource global community telegram group, there was a suggestion to create a Meta page to coordinate this efforts. So that should be something to do. :)

Possibly related tickets:

Hi @Pintoch if a license is compatible with CC0 requirements, then yes it can be imported into any dataset covered by CC0, including Wikidata.

For some reason @Aklapper is on most task I create (I guess for triage reasons) but not on this one. Please let me know if I should or not add you manually in that kind of case.

I looked at the Probox documentation but didn't saw anything related to the "join" button and the role list.

The list of activity is given on Commons: