Meta:Babel/Archives/2022-11

The CampaignEvents extension will be enabled on Meta-wiki soon

SUMMARY: For your awareness, we’re sharing that a new feature is being enabled soon on Meta-wiki, which is associated with a new namespace pair. It will only be available in Meta-wiki at first. Usage is optional, and no workflows are expected to change.

Hello Meta-Wiki community members,

The Campaigns Product Team is planning to enable the CampaignEvents Extension on Meta-wiki soon, with a target release date in late November. This extension features Event Registration as its first tool, with a new namespace pair: Event and Event Talk namespaces. You can visit the project release page for the latest details on the release schedule, and you can visit this link to learn about how this project has been shared with Wikimedia communities.

Event Registration is an optional tool that enables on-wiki event registration. With this tool, event participants can click on a "Register" button to sign up for events. Meanwhile, event organizers can easily enable event registration on their event pages.

In the future, the CampaignEvents extension will be expanded to include an Event Center. The Event Center will be an optional platform for organizing and managing campaign events, along with other event types, on the wikis.

In July 2022, the Campaigns team released an early version of the event registration tool, known as V0. It is available for testing on testwiki, test2wiki, and the beta cluster. You can visit our project page, read the user guide for the tool, check out our live demo and office hour recording on the tool, and read the summary of the V0 release community feedback to learn more.

The team is currently working on building V1 of the event registration tool, which is the version we plan to release to Meta-wiki. For V1, the organizer side will only be made available to a pre-screened list of organizers. This list will be screened and compiled by the Campaigns team. If you would like to be an early test organizer, please reach out to the team (see bottom section on how to contact us). The participant side will be available to any Meta-wiki users with a registered Wikimedia account.

We welcome any feedback, questions, or ideas you may have on our plans. To contact us, you can share your feedback on our project talk page, directly contact any team members, join our subscription list, or join our upcoming community office hours.

Thank you!

Sincerely,

The Campaigns Product Team IFried (WMF) (talk) 14:01, 8 November 2022 (UTC)

@IFried (WMF) is there a list of open issues on this (primary phab tag maybe)? I posted a question at Talk:Campaigns/Foundation Product Team/Registration already. — xaosflux ^Talk 14:26, 8 November 2022 (UTC)

Hello @Xaosfluxǃ Yes, the tag for the event registration project in Phabricator is Campaign-Registration. The tag for Event Center work is Campaign-Events The tag for all of our team's projects is Campaign-Tools. To see what the team is currently working on, you can check out our sprint board. Also, I have answered your question on our project talk page and look forward to your response. Thank youǃ IFried (WMF) (talk) 14:51, 8 November 2022 (UTC)

Sysop and an RfC

Where exactly does one go to report questionable behavior by sysops on the wiki?

A particular sysop has accused me of "trolling" Ukrainian Wikipedia because I have created an RfC (or rather, several, because they deleted it after no dicussion) expressing concern about a userbox that endorsed an SS unit. At first I was told not that the problem was a wording problem and that I was "taking things out of context", but no matter how many times I read the rules, I don't see how saying a particular wiki has a problem with Nazi sentiments (re: dozens of users using a userbox that endorses the SS) is against the rules. After all, there was a very similar discussion about such problems in Croatian Wikipedia. So this time, I carefully worded the RfC to not mention any users by name (previously I cited usernames as examples of accounts using nazi slogans/dog whistles, like 8814, accompanied by a link to the ADL explaining the Nazi use of the numbers). The current RfC is very carefully worded, yet the still accuse me of trolling. I don't see any legal (wiki-wise) rationale for censoring discussion, nor does it seem standard with policy for a single sysop who readily admits their bias on a matter on their userpage with a flag is allowed to unilaterally prohibit someone from discussing a topic and even going so far as reverting (not strikethroughing) a simple comment where I said that there is no excuse to glorify the SS. Am I missing something here? I thought it was pretty uncontroversial to say that celebrating the SS is deeply offensive and degrading. I never would have imagined that saying that a userbox that endorses the SS is "Nazi" would be considered out of line behavior. I don't deny that I've fucked up on the wiki in other places (ergo why I'm banned in enwiki...ruwiki is a different story), but does anyone know if there are any actual wiki-regulations regarding when it is ok to say that something is Nazi? I know that there's Godwin's law and all but I assume that doesn't apply to military formations affiliated with the actual Nazi Germany. What is the best course of action here? And are any topics banned from RfC that I'm not aware of?--PlanespotterA320 (talk) 00:58, 29 November 2022 (UTC)

This section was archived on a request by: Poster is GLocked. — xaosflux ^Talk 14:59, 8 December 2022 (UTC)

Usability of the CAT interface here

On this wiki, translations are primarily done through some sort of a CAT (computer-aided translation) interface, which currently does some checks (for example, on bracket matching) in such a way that impedes usability. I wonder if this can be remedied.

The main issue here is that when you, for example cannot quickly close some bracket (within an unreasonably short amount of time, especially when a non-Latin language is involved, or when the user is experiencing disability), a warning message will be inserted into the panel, between the current segment and the text field for the commit message, shifting the commit field, the Publish and Skip buttons down. If the translator then resolves the warning (e.g., closes the bracket) then proceeds to write a commit message, they can instead inadvertently push the Publish button instead, without a commit message. In other words, the current UI design actually causes user errors.

I’d like to propose that a blank row be always reserved for status and warnings messages, so that warning messages will never change the position of the Publish or Skip buttons on the screen. Alternatively, the status message should be shown below the buttons, so that the display or removal of the warning message will not shift any important UI elements.

I believe fixing this is important, as this is actually an accessibility issue. — Al12si (talk) 07:31, 1 November 2022 (UTC)

@Al12si I see a closely-related task at phab:T164306, but that was about changing the timing. I like your suggestion of a reserved space in the UI. I suggest filing a short feature request, or I can help if you'd prefer. :) Quiddity (WMF) (talk) 23:36, 4 November 2022 (UTC)

@Quiddity (WMF) If you’re interested, I’ve opened phab:T322801. I don’t think it’s going to get us anywhere (if you asked me I’d say our devs are ableist and culturally insensitive, but judging from what I see on FB or LI I’m not surprised) but if you want to chime in... Al12si (talk) 22:07, 12 November 2022 (UTC)

Creation of EventːSandbox to test CampaignEvents extension

Helloǃ As previously posted, the Campaigns Product Team is planning to enable the CampaignEvents Extension on Meta-Wiki soon. For this reason, we are proposing that we create a page on Meta-Wiki called EventːSandbox after the release (see Phabricator ticket T323299 for details). This page would allow users to test out the tool, which would be done by creating "test" event pages as subpages within Event:Sandbox. We would add documentation, such as a basic "how to use this sandbox" guide, on the Event:Sandbox main page. So, we would like to knowː What do people think of this proposal? Do they have any major concerns or alternative suggestions? Do they think the EventːSandbox page would be useful to theɱ? Thank you in advanceǃ IFried (WMF) (talk) 18:44, 21 November 2022 (UTC)

“Suggestions” in CAT interface: Strange algorithm?

I’m asking because when translating Tech News, the CAT interface often behaves very strangely, most often not offering any suggestions even when there’re segments in the translation memory that are perfect matches; also, it seems to prefer very old matches over recent corrections. In both cases the translator is forced to find a recent translation, then manually copy the correct translations over from a recent article.

Is this the right place to raise this, or is there a more appropriate forum? Thanks. Al12si (talk) 22:42, 4 November 2022 (UTC)

@Al12si Re: your last question: Per the box at the top, this page "is primarily for discussion of Meta policies and guidelines" - and - "For notices and discussions related to multilingualism and translation, see Meta:Babylon and its discussion page". So that page's talkpage would be better for most of your questions here.

Re: problems with the translation memory - Ideally, software bugs can be filed directly in Phabricator, the software bug/feature/task tracking tool used for most of our software. If you want to do that, and aren't already familiar with how to write an effective (for the devs!) task, see mw:How to report a bug. -- Alternatively, you could describe it on the talkpage of mw:Extension:Translate. (I tried 2 very brief keyword searches within the extension's workboard, but I couldn't quickly see an existing task about this.) Hope that helps! Quiddity (WMF) (talk) 23:27, 4 November 2022 (UTC)

For the record, I’ve just opened phab:T323856 Al12si (talk) 22:08, 26 November 2022 (UTC)

GLAM Glossary

I find the page Open Culture/GLAM Glossary is too large. Do you see a way to lighten it? Splitting it with one page per initial letter is probably not a better accessibility. What do you think? -- Pols12 (talk) 14:27, 26 November 2022 (UTC)

Hi :) We took this glossary as a "template".Sintegrity (talk) 21:32, 26 November 2022 (UTC)

Hi! The page was really too big 😅. As the ideia is being a collaborative work, we hope it grows along time. So we broke the Glossary by letters, as you suggested. Could you please take a look and see if we did it in the proper way? Sintegrity (talk) 23:46, 10 December 2022 (UTC)

Given no one else answered here, I wanted to go forward marking the page for translation, but I see it was being splitted. That seems be better now, thank you! I’m marking the pages for translations. -- Pols12 (talk) 14:37, 11 December 2022 (UTC)

@Sintegrity, in H page, I have turned the Wikipedia link list as vertical. Can you review it to consider apply this change to other pages? Also, if those links only come from Wikidata linked item, we should generate them automatically: that would simplify the code and ever keep the list up-to-date. -- Pols12 (talk) 19:15, 11 December 2022 (UTC)

Hi ! I understand the idea of a link list as vertical, but sometimes it would be really longer. See Copyright Open Culture/GLAM Glossary/C. Yeah the links to wikipedias come only from Wikidata. Could you help with the automation? Thanks Sintegrity (talk) 20:27, 11 December 2022 (UTC)