I wanted to report a bug via Phabricator, but<br/>

It seems that, if I want to log in to '''Mediawiki''' I need a different account than '''Wikipedia'''.

If this is so, why does '''Mediawiki''' need a different account than '''Wikipedia'''?

en.wikipedia / User:Steue 2A01:C23:79B3:3900:4118:2CA:C781:B146 (talk) 02:11, 2 May 2022 (UTC)

It doesn't, wikipedia and mediawiki wiki are part of the SUL login environment, If you weren't automatically logged in via centralauth, You may just need to login again.

Phabricator is not powered by MediaWiki so it features its own authentication system, but we Use oAuth (the "Login with MediaWiki" button) so it will use the your SUL account details.

For more information on how to create a phabricator account, See Special:MyLanguage/Phabricator/Help#Creating_your_account P858snake (talk) 02:17, 2 May 2022 (UTC)

Steue (talk) 03:30, 2 May 2022 (UTC)

This was answered in your first topic on this page: Project:Village Pump/Flow/2022/05#h-Why_does_Mediawiki_need_a_different_account_than_Wikipedia-2022-05-02T02:11:00.000Z P858snake (talk) 04:50, 2 May 2022 (UTC)

On https://www.mediawiki.org/wiki/Phabricator/Help#Creating_your_account the sub-chapter "Using your global wiki account", first asterisk-entry (bullited entry) reads: First, make sure you are [logged in] to Wikimedia. This link [logged in] leads to exactly the same page on which this link is located. Not a helpful link, to me. Steue (talk) 03:58, 2 May 2022 (UTC)

That is because you are already signed into a Mediawiki Wiki, Which is apart of the Wikimedia Single User Login environment. P858snake (talk) 04:49, 2 May 2022 (UTC)

Hello everyone! Coming from wb:de.

Pages that use score are expected to be in the tracking category "Score-use-category". But they only are after an edit, which isn't that big of a deal for a new wiki, but for an existing one it's inconvenient. A wild guess by me is score was used before the category existed (compare Phab:T219603). I looked at Help:Tracking_categories trying to shed some light on the problem. Just to find, that the category isn't even listed there, let alone an explanation if (that?) tracking categories are only used when a wiki-page is published. So:

• I wasn't able to correct the help page, because of lack of deeper knowledge of mediawiki,
• the talk page Help talk:Tracking_categories doesn't seem to be in use quite a bit, bit I think this topic is somewhat important (at least to know how to handle those situations), so I came here,
• I'm not sure, if a task on Phabricator makes sense, because I'm suspecting everything is as it's supposed to be, just causing inconvenience as a side effect,
• I don't expect there to be a "automated" solution to the initial problem, but at least I wanted to raise awareness.

Anyways help, if possible, would be greatly appreciated and if there's anything I can do to help, let me know. Thanks and best regards, HirnSpuk HirnSpuk (talk) 07:56, 3 May 2022 (UTC)

I added that (and the other undocumented Ext:Score tracking category, score-deprecated-category) to Help:Tracking categories for you. Unfortunately I can't really help with the category only being added to pages after they're edited, but I would definitely recommend you file a Phabricator task about it - worst that happens is the task is declined as expected behavior (or just an issue that won't be fixed). 「ディノ奴千？！」^{☎ Dinoguy1000} 10:15, 3 May 2022 (UTC)

Existing pages don't get the tracking category automatically, if the tracking category didn't exist when the page was last edited. That's expected.

To add the tracking category, all pages should be reparsed, which is a very expensive operation.

When this situation happens, the best way to deal with it is to use the standard search function to grab a list of pages using a specific tag o parser function, and then run a bot to do a null edit on all those pages. Ciencia Al Poder (talk) 13:44, 3 May 2022 (UTC)

Thanks for all the help and the insight. Then I'll restrain from using phabricator. I expected a bot would be able to do the job. Thanks again, best regards, HirnSpuk HirnSpuk (talk) 16:27, 3 May 2022 (UTC)

You can find this message translated into additional languages on Meta-wiki.

More languages • Please help translate to your language

The Movement Strategy and Governance team is looking for community members to serve as election volunteers in the upcoming Board of Trustees election.

The idea of the Election Volunteer Program came up during the 2021 Wikimedia Board of Trustees Election. This program turned out to be successful. With the help of Election Volunteers we were able to increase outreach and participation in the election by 1,753 voters over 2017. Overall turnout was 10.13%, 1.1 percentage points more, and 214 wikis were represented in the election.

There were a total of 74 wikis that did not participate in 2017 that produced voters in the 2021 election. Can you help increase the participation even more?

Election volunteers will help in the following areas:

• Translate short messages and announce the ongoing election process in community channels
• Optional: Monitor community channels for community comments and questions

Volunteers should:

• Maintain the friendly space policy during conversations and events
• Present the guidelines and voting information to the community in a neutral manner

Do you want to be an election volunteer and ensure your community is represented in the vote? Sign up here to receive updates. You can use the talk page for questions about translation.

MNadzikiewicz (WMF) (talk) 10:54, 7 May 2022 (UTC)

Hello!

Have you noticed that some wikis have a different desktop interface? Are you curious about the next steps? Maybe you have questions or ideas regarding the design or technical matters?

Join an online meeting with the team working on the Desktop Improvements! It will take place on 17 May 2022 at 12:00 UTC and 19:00 UTC on Zoom. Click here to join. Meeting ID: 86217494304. Dial by your location.

Agenda

• Update on the recent developments
• Questions and answers, discussion

Format

The meeting will not be recorded or streamed. Notes will be taken in a Google Docs file. Olga Vasileva (the Product Manager) will be hosting this meeting. The presentation part will be given in English.

We can answer questions asked in English, Italian, Polish; also, only at the first meeting: Farsi, Vietnamese; only at the second meeting: Portuguese, Spanish, Russian. If you would like to ask questions in advance, add them on the talk page or send them to sgrabarczuk@wikimedia.org.

At this meeting, both Friendly space policy and the Code of Conduct for Wikimedia technical spaces apply. Zoom is not subject to the WMF Privacy Policy.

We hope to see you! SGrabarczuk (WMF) (talk) 05:02, 14 May 2022 (UTC) MediaWiki message delivery (talk) 05:02, 14 May 2022 (UTC)

Has there been any thought about using the new talk page tools (Talk pages project) on this wiki? Barkeep49 (talk) 01:54, 18 May 2022 (UTC)

Kind of - see Project:Village Pump/Flow/2022/02#h-Discussion_tools_deployments-2022-02-16T19:15:00.000Z. I don't know/remember what the outcome of that discussion was though, @Whatamidoing (WMF)? Legoktm (talk) 02:32, 18 May 2022 (UTC)

The [reply] tool is on by default for all wikitext-based talk pages. I've asked the Editing team in the past to turn on the DiscussionTools Beta Feature by default.

Is your real question closer to "Has there been any thought about making wikitext be the default page model for talk pages on this wiki?" I don't think I would recommend that until we know whether automatic topic subscriptions (the [subscribe] button) is a good thing to enable by default for all users. Whatamidoing (WMF) (talk) 15:49, 18 May 2022 (UTC)

That really was my question and I appreciate the feedback. Barkeep49 (talk) 16:00, 18 May 2022 (UTC)

The page model was originally switched to Flow because the admins kept getting so many requests for "one-off" changes to new pages. It proved to be less work to change the default and freely grant one-off changes back to wikitext (ask any admin you know, or start a thread here whenever you want; if the page doesn't already exist, it's not considered a big deal, and Flow-to-wikitext conversions are possible).

Editing's planning an A/B test for Talk pages project/Notifications. It will hopefully emerge from instrumentation purgatory at the end of this month, run for about a month, and spend another month while the analyst figures out what happened. Depending on the results, the Editing team will make a recommendation. My guess (but data rules) is that they'll suggest enabling automatic subscriptions for newbies and manual subscriptions for old hands. My second guess is automatic for everyone, but with a highly visible opt-out button, which would have to be built. (Also, by this point, it'll be August, which means Wikimania, and nothing else will happen for weeks.)

On the assumption that the local community would first want to have this information plus (assuming the results are favorable) have the [subscribe] button deployed, I think the very earliest that people would want to talk about any changes would be September (October or even November being more realistic, since everything takes longer than it should).

As for the Editing team's role: They'll provide information and recommendations to all WMF wikis, but they weren't consulted on the switch to Flow in the past, and I don't think they expect to be consulted on any switch away from Flow in the future. Whatamidoing (WMF) (talk) 06:07, 19 May 2022 (UTC)

I support enabling DiscussionTools here, and moving away from Flow. Thanks. —MarcoAurelio (talk) 15:21, 6 June 2022 (UTC)

Update: The devs have accepted my proposal to enable DiscussionTools here, by default, for everyone. This will happen on Wednesday, when they have a backport window reserved for some other things anyway.

I believe the goal is that phab:T311456 will add to previous deployments to end up with the result that everyone has everything by default, and that logged-in users can turn off any pieces they don't want in Special:Preferences#mw-prefsection-editing-discussion. If there are problems, of course, please let me know. Whatamidoing (WMF) (talk) 22:21, 27 June 2022 (UTC)

Please have a look at User talk:Whatamidoing (WMF), which is showing the latest (but not final) version. Whatamidoing (WMF) (talk) 21:25, 8 July 2022 (UTC)

I also support enabling DiscussionTools here, and moving away from Flow. Thanks. Ladsgroup (talk) 21:53, 14 December 2022 (UTC)

Filed phab:T325907. Taavi (talk!) 11:53, 24 December 2022 (UTC)

Why would we do this? Structured Discussions is much easier for newcomers to use than DiscussionTools, especially on this wiki where most people are new and are coming here looking for support for their wiki... You also can also easily edit your responses in Structured Discussions compared to DiscussionTools. Lectrician1 (talk) 17:23, 24 December 2022 (UTC)

I respectfully disagree, Flow has much more issues than DT. For example search practically doesn't work in flow so you can't really search for old questions (at least last time I checked). DT is also much more newcomer friendly once the new design for DIP gets deployed. I agree editing your response is a good idea to have but it doesn't mean it won't be there in near future.

Also flow is a maintenance nightmare. e.g. my bot can't properly do any archive of even non-flow pages because it can't create new archive pages and I have to manually create them (e.g. Talk:Reading/Web/Desktop Improvements/Archive9) Ladsgroup (talk) 14:54, 2 January 2023 (UTC)

For example search practically doesn't work in flow so you can't really search for old questions (at least last time I checked).

For most questions I've personally had regarding MediaWiki, I always use Google to look them up, never the wiki. That way I can get results from Flow posts on this wiki or Stack Overflow. Searching the wiki sucks outright even if we're using DiscussionTools. Search engines are able to index Flow perfectly and I'd guess that's where most others do their initial searching of questions as well.

DT is also much more newcomer friendly once the new design for DIP gets deployed.

Still not as newcomer friendly in other regards though. New topics in Flow are posted at the beginning of the page, the new topic creator is clearly at the top of the page and not a small "Add topic" button in the upper right, users aren't confused what happens to their topic when it becomes "archived", and you can easily mark the topic as resolved.

Why should we remove the opportunity for users to use these features when we don't need to? Until DiscussionTools has these features and more, then that's when we should consider switching systems. We shouldn't go through the work of switching systems right now when there's no net benefit of doing so. Lectrician1 (talk) 16:07, 2 January 2023 (UTC)

This isn't some "newcomer" wiki. The people you're describing are ambitious enough technically that they can setup their own mediawiki but easily confused enough that they can't use Discussion Tools which has had fairly extensive user experience testing? I'm sure that's a real person who exists but I also don't know that mediawiki needs to be organized around them rather than other types of people who use this wiki. And it does things that would be confusing for newcomers too. For instance if hit reply to your message @Lectrician1. But it doesn't thread in a way that someone with forum or reddit experience would expect. Barkeep49 (talk) 16:35, 2 January 2023 (UTC)

I think Project:Support desk actually benefits from having Flow enabled, since it's a pretty busy discussion page.

However, all other spaces probably should default to the new talk page tools. Ciencia Al Poder (talk) 19:07, 2 January 2023 (UTC)

My opinion: StructuredDiscussions is markedly inferior to the previous ("classic") system: imposing a lot of bloat I care little for. I am neutral towards DiscussionTools, but I guess it has the advantage of not being StructuredDiscussions. CapnZapp (talk) 16:42, 6 January 2023 (UTC)

It seems to me like this is a trade-off between making this wiki more accessible to third-party MediaWiki users (using Flow), and making it more accessible to other Wikimedia wiki users (using DT). Most of us are in that second group, so that's what we prefer, but one could reasonably prefer the other.

Maybe the answer is to make it easier to enable/disable Flow on individual pages. On the other hand, I'm sensing a desire to decommission Flow entirely, so that might be giving its fans false hope. Matma Rex (talk) 21:08, 6 January 2023 (UTC)

It seems the natural compromise here is to disable flow for default (at least for now) but keep newcomer facing page as flow boards. It makes sense a newcomer might want to discuss something in Project:Support desk and flow would be useful but if that person wants to discuss something like advanced linter error issues, I assume they at least know how to use a talk page. Ladsgroup (talk) 21:50, 6 January 2023 (UTC)

If that's technically possible yes that seems like a good compromise. Barkeep49 (talk) 21:52, 6 January 2023 (UTC)

Agreed that switching Flow off by default while leaving it enabled on some specific pages is a reasonable solution, and appears to be technically possible. * Pppery * _{it has begun} 02:15, 7 January 2023 (UTC)

This was done in gerrit:871286. * Pppery * _{it has begun} 19:31, 9 January 2023 (UTC)

Hello all,

The Universal Code of Conduct (UCoC) project team has completed the analysis of the feedback accompanying the ratification vote on the Universal Code of Conduct Enforcement Guidelines.

Following the completion of the UCoC Enforcement Guidelines Draft in 2022, the guidelines were voted on by the Wikimedian community. Voters cast votes from 137 communities, with the top 9 communities being: English, German, French, Russian, Polish, Spanish, Chinese, Japanese, Italian Wikipedias, and Meta-wiki.

Those voting had the opportunity to provide comments on the contents of the Draft document. 658 participants left comments. 77% of the comments are written in English. Voters wrote comments in 24 languages with the largest numbers in English (508), German (34), Japanese (28), French (25), and Russian (12).

A report will be sent to the Revision Drafting Committee who will refine the enforcement guidelines based on the community feedback received from the recently concluded vote. A public version of the report is published on Meta-wiki here. The report is available in translated versions on Meta-wiki. Please help translate to your language

Again, we thank all who participated in the vote and discussions. We invite everyone to contribute during the next community discussions. More information about the Universal Code of Conduct and Enforcement Guidelines can be found on Meta-wiki. MNadzikiewicz (WMF) (talk) 17:02, 22 May 2022 (UTC)