From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search
 ← Index of discussion pages Babel archives (latest) →
This is the general discussion forum for Meta (this wiki). Before you post a new comment please note the following:
  • You can comment here in any language.
  • This forum is primarily for discussion of Meta policies and guidelines, and other matters that affect more than one page of the wiki.
  • If your comment only relates to a single page, please post it on the corresponding discussion page (if necessary, you can provide a link and short description here).
  • For notices and discussions related to multilingualism and translation, see Meta:Babylon and its discussion page.
  • For information about how to indicate your language abilities on your user page ("Babel templates"), see User language.
  • To discuss Wikimedia in general, please use the Wikimedia Forum.
  • Consider whether your question or comment would be better addressed at one of the major Wikimedia "content projects" instead of here.
Wikimedia Meta-Wiki
This box: view · talk · edit
Filing cabinet icon.svg
SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 1 day and sections whose most recent comment is older than 30 days.

Help with bot updated list[edit]

Hello! Could someone please help with Talk:List_of_Wikipedias_by_expanded_sample_of_articles#Please_help_updating_this this? -Theklan (talk) 10:04, 28 October 2018 (UTC)

Editing News #2—2018[edit]

14:17, 2 November 2018 (UTC)

Meta talk:Administrators[edit]


There's an ongoing discussion about changing our inactive administrator policy. Any comment is welcome.

Regards. Matiia (talk) 23:31, 10 November 2018 (UTC)

Changes to CentralNotice Access[edit]

A source of concern for some time has been that there are more people with access to CentralNotice than know how to or want to use the system. This is mainly been maintained because of CentralNotice's reliance on the MediaWiki namespace rather than a specific policy. Following the separation of interface-admin rights from general admins rights along with activity requirements for Meta Admin it has been decided to apply both of these policies to CentralNotice Administrators effective immediately as we look to proactively improve our security posture and promote a culture of security.

From today, only individuals with the “centralnotice-admin” user group will be able to modify campaigns and banners. Meta administrators will no longer be able access CentralNotice or make changes to centralnotice banners through the MediaWiki namespace.

CentralNotice-admins who have not made actions related to CN in the last 12 months as of November 16th 2018 will have the CentralNotice right removed but without prejudice. They will eligible to re-request the rights should the need arise or that they intend to work with CentralNotice on a longer term basis.

Meta-admins who have been active in the last 12 months in CentralNotice and will be added to the CentralNotice admin group by the Meta Bureaucrats shortly. Similarly Meta admins who have previously worked with CentralNotice but who have not done so in the last 12 months are eligible to re-request the rights should the need arise or that they intend to work with CentralNotice on a longer term basis without prejudice.

CentralNotice admins will also be required to undertake additional measures to secure their accounts.

It's understood this may cause some temporary disruption but I will be providing additional supports to communities in their access and use of CentralNotice through this period. Thank you all for your support and patience through this. Seddon (WMF) (talk) 05:25, 17 November 2018 (UTC)

@Seddon (WMF): and to where has this conversation been taking place? I haven't seen any invitation to participate. I was understanding that we operated with consensus, rather than by decree.  — billinghurst sDrewth 10:34, 17 November 2018 (UTC)
@Seddon (WMF): Thanks for separate follow-up email.

If you reread your post above, it is the generic big brother words that are troublesome. When a matter is undertaken, the powers that made the decision can be named. Not the amorphous nature used here which simply lacks accountability. I don't think if there are specific security concerns that you will get argument that changes should be made, and that may outweigh community consensus, however, that can be done courteously in a means sympathetic with our community approach. That said, you have now also set and direct a community policy again without identification of who has made that policy, and that is not the role of WMF staff here at meta, unless one is implementing something on the direction of the Board or the ED. If you are doing it on that, or similar authority, then say it. This is meta and staff should be cognisant of that; and you have been round long enough to know the culture of your fellow dinosaurs. You are also implementing an authority that changes the natures of the wikis, and where the Foundation may be seen as being put in greater control of day to day events. If you had applied a similar approach at enWP you would have faced a riot! So please look to update your communications around this process and identify what is staff-imposed and on whose authority, and what belongs to the community.  — billinghurst sDrewth 11:01, 18 November 2018 (UTC)

Seddon asked us Meta bureaucrats to implement the described changes. I have done so now. --MF-W 10:44, 17 November 2018 (UTC)
@MF-Warburg: I've touched CN's in the l2 months and are an admin and int-admin with 2FA, but don't see this access added - does a request need to be filed? — xaosflux Talk 12:34, 17 November 2018 (UTC)
I acted based on a list Seddon gave me. Looks like it may have been incomplete. I would wait for a correction to be made, if none happens, then please file a request. --MF-W 12:55, 17 November 2018 (UTC)
@Seddon (WMF): for comment. — xaosflux Talk 13:11, 17 November 2018 (UTC)
I used to make an edit to banners translation (even earlier this month) and still excluded? Can I edit translations without being barked by system? — regards, Revi 04:01, 18 November 2018 (UTC)
Some admins were indeed left out. It is fixed now. --MF-W 01:17, 19 November 2018 (UTC)


This is de facto policy according to the description, but what do we need to do to make it de jure policy? Unless there is any stuff that raises a big red siren, I think we can do formal stuff and make it de jure. — regards, Revi 15:04, 18 November 2018 (UTC)

Do you want some specific change? Unless that is the case, I do not see any reason to deviate from common practice. Not everything has to be written in stone, unless it is controversial. --Vogone (talk) 15:17, 18 November 2018 (UTC)
Mostly agree with Vogone. I don't think the issue is with the policy, it is possibly the lack of clarity that we will utilise non-compliance to block. We do not heavily link to it; it is not mentioned in our welcome message; and we do not have a block policy. With each of those it could be said that there is not sufficient emphasis on this from the community.  — billinghurst sDrewth 20:53, 18 November 2018 (UTC)
Meta-Wiki intentionally avoids having very detailed behavioural policies, because if we summed up all the different expectations and habits of people from hundreds of projects we would end up having dozens of megabytes of text for every user to read. Meta also happens to be the place where many of the "universal" or ancient wiki or Wikimedia principles are discussed and summarised, which often provide useful guidance.
So I see it fitting that Meta:Urbanity was created as a mere explanation of how to read and use previously expressed policies and principles, and I'm not aware of any case where explicitly making it policy would have helped. I don't rule out that there may be, though. Nemo 22:14, 18 November 2018 (UTC)

Proposal: Updating requirements for autoconfirmed accounts[edit]

At the moment, autoconfirmed accounts at Meta are set after 4 days and zero edits. This is being problematic for some spam accounts, and at least one LTA who is creating accounts, and then waiting out the autoconfirmed period, then vandalising semi-protected pages. I propose that we have our configuration amended to be

  • autoconfirmage 4 days; and
  • autoconfirmedits 5 edits

In a conversation with user:Ajraddatz I suggested 10 as used at other wikis, however, they counter-proposed to 5.  — billinghurst sDrewth 05:47, 19 November 2018 (UTC)



Propose discussion for 14 days, so closing 3 December 2018 if no disagreement.

  • support as proposer.  — billinghurst sDrewth 05:47, 19 November 2018 (UTC)
  • Support - would provide a bit of a buffer to keep autoconfirmed protection useful, while not preventing experienced users from across Wikimedia from participating here. I would be OK with either 5 or 10, but would lean towards 5 for now. We can always raise to 10 if this continues to be an issue. – Ajraddatz (talk) 05:53, 19 November 2018 (UTC)
  • Support Support --Rschen7754 06:07, 19 November 2018 (UTC)
  • Support Supportmake sense to do this. I will prefer 7/50 as per my homewiki but this is better than nothing.--Cohaf (talk) 06:22, 19 November 2018 (UTC)
  • Support and agree with Cohaf as well. —MarcoAurelio (talk) 10:30, 19 November 2018 (UTC)