DZ
DefZone.Net

Kien thuc cong nghe & giai tri

Wiki Article

Talk:Main Page

Nguồn dữ liệu từ Wikipedia, hiển thị bởi DefZone.Net

Xem trên WikipediaBài ngẫu nhiên khác
Archives: Sections of this page older than three days are automatically relocated to the newest archive.

001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 016 017 018 019 020 021 022 023 024 025 026 027 028 029 030 031 032 033 034 035 036 037 038 039 040 041 042 043 044 045 046 047 048 049 050 051 052 053 054 055 056 057 058 059 060 061 062 063 064 065 066 067 068 069 070 071 072 073 074 075 076 077 078 079 080 081 082 083 084 085 086 087 088 089 090 091 092 093 094 095 096 097 098 099 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211

Main Page error reports

[edit]
Shortcuts

To report an error in content currently or imminently to appear on Main Page, use the appropriate section below. Reports should contain:

  • Where is the error? An exact quotation using {{!xt}} of the text in question helps.
  • Offer a correction if possible using {{xt}}.
  • References are helpful, especially when reporting an obscure factual or grammatical error.
  • Time zones. The Main Page runs on Coordinated Universal Time (UTC, currently 21:54 on 28 May 2026) and cannot be adjusted to your local time zone.
  • Can you resolve the problem yourself? If the error lies primarily in the content of an article linked from the Main Page, fix the problem there before reporting it here. Text on the Main Page generally defers to the articles with bolded links. Upcoming content on the Main Page is usually only protected from editing beginning 24 hours before its scheduled appearance. Before that period, you can be bold and fix any issues yourself.
  • Do not use {{edit fully-protected}} on this page, which will not get a faster response. It is unnecessary, because this page is not protected, and causes display problems. (See the bottom of this revision for an example.)
  • No chit-chat. Lengthy discussions should be moved to a suitable location elsewhere, such as the talk page of the relevant article or project.
  • Actual errors only. Failures of subjective criteria such as taste or interestingness, or failure to divert enough DYK readers to articles that aren't new or recently improved, are not errors.
  • Respect other editors. Another user wrote the text you want changed, or reported an issue they see in something you wrote. Everyone's goal should be producing the best Main Page possible. The compressed time frame of the Main Page means sometimes action must be taken before there has been time for everyone to comment. Be civil to fellow users.
  • Reports are removed when resolved. Once an error has been addressed or determined not to be an error, or the item has been rotated off the Main Page, the report will be removed from this page. Check the revision history for a record of any discussion or action taken; no archives are kept.
Administrators: Clear all reports

Errors in the summary of the featured article

[edit]
Please do not remove this invisible timestamp. See WT:ERRORS and WP:SUBSCRIBE. - Dank (push to talk) 01:24, 29 September 2022 (UTC)[reply]

Today's FA

[edit]

Tomorrow's FA

[edit]

Day-after-tomorrow's FA

[edit]

Errors with "In the news"

[edit]

Errors in "Did you know ..."

[edit]

Current DYK

[edit]

Next DYK

[edit]
  • " that the Ukrainian National Union's newspaper waited for the rise of a Ukrainian Mussolini or Hitler?". You will know that it is part of Putin's propaganda that Ukraine is currently run by fascists. Please can we make clear in the hook that the newspaper in question operated long ago. I think writing "that in 1939 the ..." would do the trick. JMCHutchinson (talk) 20:01, 28 May 2026 (UTC)[reply]
    I would normally think it's not an issue because it's in the article, but I am fine with it being changed. SL93 (talk) 20:16, 28 May 2026 (UTC)[reply]

Next-but-one DYK

[edit]

Errors in "On this day"

[edit]

Today's OTD

[edit]

Tomorrow's OTD

[edit]

Day-after-tomorrow's OTD

[edit]
[edit]

Monday's FL

[edit]
(June 1)

Wednesday's FL

[edit]
(June 3)

Friday's FL

[edit]
(May 29, tomorrow)
[edit]
Notice to administrators: When fixing POTD errors, please update the corresponding regular version (i.e. without "protected" in the page title) in addition to the Main Page version linked below.

Today's POTD

[edit]

Tomorrow's POTD

[edit]

General discussion

[edit]
Shortcuts

Some sprucing up

[edit]

I was recently on the front page of RuWiki [1] and I was struck by how nice it looked. While I'm not suggesting we wholesale change our front page, there are some changes I suggest that might spruce the place up here a bit.

  1. De-bold the links in "Other areas of Wikipedia" mockup
  2. De-bold the links in "Wikipedia's sister projects" mockup
  3. Add the Foundation logo, like as is done on RuWiki, over the "Wikipedia's sister projects" section
  4. Center "Wikipedia is written by volunteer editors and hosted by the Wikimedia Foundation, a non-profit organization that also hosts a range of other volunteer projects:"
  5. Center "This Wikipedia is written in English. Many other Wikipedias are available; some of the largest are listed below."

I think that would help make things a little nicer and smoother. If there is appetite for that, I can draw up some drafts for more formal approval. CaptainEek Edits Ho Cap'n!⚓ 23:35, 25 May 2026 (UTC)[reply]

Debolding Other areas feels like it'll help everything look smoother. Not sure it'll make the same impact for the sister projects as the font there already seems small but worth a look. Neutral on the other changes, I assume the centering is to be tested at the default page width? CMD (talk) 03:33, 26 May 2026 (UTC)[reply]
These are all minor formatting changes. Could you mock them up (e.g. on Main Page/sandbox) so we can see the effect of your proposal? Centring might look odd, because the content columns are not equal width. Modest Genius talk 13:22, 26 May 2026 (UTC)[reply]

(Possible) Grammatical Error

[edit]

"In association football, Arsenal (manager Mikel Arteta pictured) win the Premier League." Here, "win" should be replaced with "won", since it's a bit weird when you ignore the parentheses. Please correct me if I am wrong, I am using AmE. Welovecontributors! [talk] 23:33, 26 May 2026 (UTC)[reply]

A team can be considered a plural noun, especially in UK-English, according to MOS:PLURALS. However, switching it to the past tense would make it grammatically correct regardless of singular vs plural, so that would be an improved MOS:COMMONALITY. DMacks (talk) 23:47, 26 May 2026 (UTC)[reply]
ITN is always written in present tense. Plural here would be "wins". 1brianm7 (talk) 00:20, 27 May 2026 (UTC)[reply]
"wins" is for singular subjects: "John wins the game" vs "John and Jane win the game". DMacks (talk) 00:42, 27 May 2026 (UTC)[reply]
Yeah. I don't think there's an error here (and we're not at WP:ERRORS regardless), ITN is always written in present tense, and win is the most correct in both American and British English, per MOS:PLURALS, this is the best we're gonna get. 1brianm7 (talk) 00:59, 27 May 2026 (UTC)[reply]
Passive voice would solve it: "In association football, the Premier League is won by Arsenal (manager Mikel Arteta pictured)." But again, that's a more substantive style change that might be contrary to general ITN style. DMacks (talk) 01:14, 27 May 2026 (UTC)[reply]
Chicago win the NBA Finals or Giants win the Super Bowl instead of the (Chicago) Bulls win the NBA Finals or the Giants win the Super Bowl would ungrammatical in American English the team names are almost all plural like Dodgers, Titans, Chiefs, Dolphins, Jets, Nets, Yankees, Hawks, Rangers, Islanders, Broncos, Cowboys, Twins, Jaguars, Lions, Cubs, Patriots, Tigers, Brewers, Flyers, Eagles, Ravens, Celtics, Steelers, Colts, Bears, Rams, Chargers, Warriors, Ducks, Cardinals, Texans, Spurs, Golden Knights, Grizzlies, Braves, Panthers, Commanders, Guardians, Vikings, Trailblazers, Raiders, Buccaneers, Athletics, Diamondbacks, Suns, Stars, Saints, Hurricanes, Blue Jackets, Penguins, Bills, Sabres, Pistons, Pacers, Red Wings, Bucks, Canadiens, Maple Leafs, Senators, Nationals, Wizards, Capitals, Canucks, Oilers, Hornets, Pelicans, Blues, Nuggets, Rockies, Seahawks, Mariners, Marlins, Rays, Rockets, Astros, Royals, Packers, the future Sonics or Supersonics, etc. Sagittarian Milky Way (talk) 17:32, 28 May 2026 (UTC)[reply]
ITN typically uses passive wording to avoid this WP:ENGVAR misunderstanding. In this case, I suggest:
In association football, the Premier League concludes with Arsenal as champions.
Modest Genius talk 10:52, 27 May 2026 (UTC)[reply]

Pre-RfC workshopping: Brooke Vibber day notice

[edit]

With June 1 approaching, I would like to propose a temporary Main Page banner to mark Wikipedia:Brooke Vibber Day, building on the suggestions raised at WP:VPWMF and Wikipedia talk:Wiki Workers United solidarity.

June 1 has been celebrated on-wiki for over twenty years to honour Brooke Vibber, the first developer hired by the Wikimedia Foundation, the former and first Wikimedia Foundation CTO and the second all-time contributor to the MediaWiki software that powers our project. The day was created and first celebrated in 2004 by Jimbo Wales, the founder of Wikipedia.

This year's milestone is particularly significant following the WMF's recent decision to disband the Community Tech team, which resulted in the layoffs of several key developers, as well as Brooke's own separate departure from the WMF under undisclosed circumstances on May 26.

These announcements were sudden and unexpected, and occurred approximately 90 days after the formation of a union by Brooke alongside most developers on the Community Tech team. Some community members noted that under California law (SB 497), the WMF is rebuttably presumed to be retaliating if they lay off employees within 90 days after they begin forming a union.[1] Thus, for these reasons, these events sparked a major on-wiki discussion, including a community solidarity petition signed by over 320 active editors, administrators, and Arbitrators, which is at the time of writing the 10th most supported proposal or petition ever on Wikipedia. You can learn more about the situation at WP:COMMTECHGATE and WP:WWUS (which also hosts statistics about the impact of editors who have signed the petition).

In light of Brooke's longstanding holiday, and the current developing situation, I think a temporary banner that both celebrates Brooke and neutrally presents the current situation, is appropriate. The Main Page does have a limited amount of self-referentiality (e.g. artist credits for featured pictures). I think celebrating one of the most influential developers on a longstanding (20 years plus!) day created by our very own founder, as well as acknowledging a serious and developing situation occurring in the community (as demonstrated by the 320 signatures, and growing), is exceptional enough to deserve this self referentiality too, just for a day.

I propose the following text and Wikilinks (thank you to Tamzin for helping copy-edit it!).

Today, June 1, marks Brooke Vibber Day. Brooke is a pioneering developer who wrote much of the original code for MediaWiki, the software that powers Wikipedia, and remains one of its most influential maintainers.
Recently, Brooke and several other unionising developers were laid off or terminated from the Wikimedia Foundation.
The Wikipedia community opened a discussion and over 320 editors have signed a solidarity petition.
The Foundation's response to the situation, in which they deny any union-busting behaviour, can be viewed here.

Of course, this is just a draft and I am happy to workshop it as a community to settle on the correct wording for this sensitive situation. - In solidarity, MolecularPilot (talk) 08:16, 27 May 2026 (UTC)[reply]

References

Support, as proposer. - In solidarity, MolecularPilot (talk) 08:22, 27 May 2026 (UTC)[reply]
Strong support for reasons already stated on village pump Gnomingstuff (talk) 08:37, 27 May 2026 (UTC)[reply]
We’d need an RfC for this. Personally I’d suggest

Today, 1 June, is Brooke Vibber Day on Wikipedia, in celebration of the legendary developer who wrote much of the original code for MediaWiki (the software that powers Wikipedia); while assisting with the unionisation of Wikimedia Foundation (WMF) staff, Brooke was recently laid off by the WMF under unclear circumstances.
We invite you to create an account and start editing (see Help:Introduction for guidance), the volunteer community that runs Wikipedia is made up of people like you! There is currently a discussion related to prioritisation of the community needs and workers' rights at the WMF, consider signing a petition in support of the unionising effort. Thank you.

Kowal2701 (talk, contribs) 08:39, 27 May 2026 (UTC)[reply]
If we start the RfC later today or tomorrow and WP:CENT it there should be adequate time to form a consensus before Monday Kowal2701 (talk, contribs) 08:44, 27 May 2026 (UTC)[reply]
Thank you for the help! I've already added it to CENT. I'm not too sure if a formal RfC is needed or just consensus of the community in this discussion with appropriate noticing (like CENT, which I've done) is needed. If a formal RfC is needed, you (or anyone!) is welcome to WP:BOLDly add the needed RfC tags, I would do so myself but I have to go do something IRL now. I like your wording too, perhaps we can incorporate some of it as well? It is so hard to find the right words for something like this, and thank you also for helping with that. - In solidarity, MolecularPilot (talk) 08:48, 27 May 2026 (UTC)[reply]
Oppose the original wording. Bluntly this just seems to be an attempt to stick it to the WMF, particularly with the 2nd and 4th lines. — Czello (music) 08:49, 27 May 2026 (UTC)[reply]
Happy to make any changes needed to change that to a support! What do you think should be changed to make those lines more neutral more neutral (which is my aim)? Perhaps unionising developers and The Foundation's response to the situation, in which they deny any union-busting behaviour, can be viewed here, though I'm not sure if that's taking too much context out. Wording is tricky so thanks for helping point out! - In solidarity, MolecularPilot (talk) 08:52, 27 May 2026 (UTC)[reply]
I'll suggest a copyedit:

Today, June 1, marks Brooke Vibber Day. Brooke is a pioneering developer who wrote much of the original code for the software that powers Wikipedia, and remains one of the software's most influential maintainers. Until recently, Brooke was employed by the Wikimedia Foundation, the entity that hosts Wikipedia on its servers; she was one of many seeking to unionise those who work tirelessly to support the Foundation, and through it, the mission to make knowledge available for free, for everyone. This month, however, Brooke and several other developers attempting to unionise were laid off or termianted by the Wikimedia Foundation.

The Wikipedia community has opened a discussion and over 320 editors have signed a solidarity petition. The Foundation has released a response statement to the situation, and has denied engaging in any union-busting.

But I have two big questions. One, why are we doing this – is this a call to action, and so, what are we calling readers to do? I think many will sign the solidarity petition, despite their signatures not being the ones we want there. The text currently hangs awkwardly; no matter how I write it, my first thought scanning the text as a hypothetical reader is "okay, and what do you want from me?". Two, I'm not sure where the initial discussion for this is – did Brooke ask us to tell millions of visitors to one of the world's biggest websites that she was laid off? That is a matter of concern to us as the community, but it is also her private life and reputation and I don't want to embarrass her inadvertently. theleekycauldron (talk • she/her) 09:04, 27 May 2026 (UTC)[reply]
Yeah, we need to target the message at readers. I think adding We invite you to create an account and start editing (see Help:Introduction for guidance), the volunteer community that runs Wikipedia is made up of people like you! or similar to the start of the second paragraph is necessary Kowal2701 (talk, contribs) 09:13, 27 May 2026 (UTC)[reply]
Btw, see [2] re Brooke being okay w this Kowal2701 (talk, contribs) 09:13, 27 May 2026 (UTC)[reply]
Isn't inviting people to edit the exact opposite of what we want to do, in case an editorial strike is called for? Thanks for the link re: Brooke's privacy, I'm queasy but understand why a clear "yes" is too dicey. theleekycauldron (talk • she/her) 09:17, 27 May 2026 (UTC)[reply]
They can't strike if they're not editors! Tbh I doubt a strike would be called on 1 June? It's also a bit of a dig at the WMF prioritising donation banners while we want more people to know they can edit Kowal2701 (talk, contribs) 09:21, 27 May 2026 (UTC)[reply]
personally I'd like

Today, June 1, marks Brooke Vibber Day. Brooke is a pioneering developer who wrote much of the original code for the software that powers Wikipedia, and remains one of the software's most influential maintainers. Until recently, Brooke was employed by the Wikimedia Foundation, the entity that hosts Wikipedia on its servers; she was one of several seeking to unionise staff at the Foundation, people who work tirelessly to support Wikipedia and, through it, the mission to make knowledge available for free, for everyone. This month, however, Brooke and several other developers attempting to unionise were laid off or terminated by the Wikimedia Foundation.

We invite you to create an account and start editing (see Help:Introduction for guidance), the volunteer community that runs Wikipedia is made up of people like you! The community has opened a discussion about the prioritisation of community needs and workers' rights at the Foundation, and over 320 editors have signed a solidarity petition in support of the unionisation efforts. The Foundation has released a response statement to the situation, and has denied engaging in any union-busting.

Kowal2701 (talk, contribs) 09:25, 27 May 2026 (UTC)[reply]
I like this, but I think what it's missing is, as you allude to, a clear sense of why it's being said. I think the best way to present this is to focus on this message being one of genuine gratitude to Brooke and the laid-off engineers. That sets a tone that makes the rest of the message make a lot more sense, and also means we've conveyed something important independent of any implied call to action. So I propose something like this:

Today, June 1, marks Brooke Vibber Day. Brooke is a pioneering developer who wrote much of the original code for the software that powers Wikipedia, and remains one of the software's most influential maintainers. Until recently, Brooke was employed by the Wikimedia Foundation, the entity that hosts Wikipedia on its servers; she was one of many seeking to unionise those who work tirelessly to support the Foundation, and through it, the mission to make knowledge available for free, for everyone. This month, however, Brooke and several other developers attempting to unionise were laid off or terminated by the Wikimedia Foundation, which has released a response statement and has denied engaging in any union-busting.

The Wikipedia community would like to take this year's Brooke Vibber Day to say "dankon" to Brooke for her decades of service to Wikipedia and its editors, and to thank the laid-off engineers for their years of hard work developing software requested as part of the Community Wishlist—a process many fear will languish with them gone. They are valued members of our community, and the Wikimedia Foundation is worse for their absence. Over the past week, dozens of community members have made their feelings known in a lengthy discussion of the controversy and over 340 editors have signed a solidarity petition with Wiki Workers United.

-- Tamzin[cetacean needed] (they|xe|🤷) 09:37, 27 May 2026 (UTC)[reply]
As an addendum, I'm not inherently opposed to Kowal's idea of adding encouragement to create an account, but I don't see it as very central to what's going on here, and think every word added increases the percentage of people who stop reading there, so I've left it out of this wording as uneconomical. -- Tamzin[cetacean needed] (they|xe|🤷) 09:40, 27 May 2026 (UTC)[reply]
I haven't made it through today's 99+ notifications, hopefully I haven't overlooked any major developments. I have a personal fondness for this wording as I recently went looking for my earliest communication with Brooke and think I found it on my Esperanto talk page in 2003. (I never did progress much beyond "saluton" and "dankon".) —In solidarity with Wiki Workers United · ClaudineChionh (she/her · talk · email) 09:55, 27 May 2026 (UTC)[reply]
Ngl I don’t want the implication that the community is a gated/exclusive group, but otherwise this is good Kowal2701 (talk, contribs) 09:58, 27 May 2026 (UTC)[reply]
On second thought I struggle to see this gain consensus among those not closely involved in this debacle, it’s the deprioritisation of the community that widely resonates, the sole focus on lay-offs and unionising may be undue, and our readers will just be confused as to why they're being shown this, it’s irrelevant for them unless we note the incorporative nature of the community Kowal2701 (talk, contribs) 11:50, 27 May 2026 (UTC)[reply]
I think Tamzin's current Sandbox version emphasises the deprioritisation and impact on the community better. From that version, are there any further edits you think should be made before RfC? - In solidarity, MolecularPilot (talk) 11:59, 27 May 2026 (UTC)[reply]
In all honesty I think it was a mistake to solely make the basis of collective action about the 7 individuals and unionising rather than the advancing of governance reforms surrounding community representation in tandem with that. I fear that the petition doesn’t really amount to much more than posturing which management can ignore, and that striking of volunteers would be quiet and ineffective. But since we’re here now, we might as well shoot our shot w that RfC as it’s much better than nothing, and the banner's well-written. I’d support as it means we’ll get more media coverage Kowal2701 (talk, contribs) 12:16, 27 May 2026 (UTC)[reply]
Very well-written, I would support this. Some1 (talk) 10:48, 27 May 2026 (UTC)[reply]
I think this is so perfectly worded and would support it strongly. Thank you so much! - In solidarity, MolecularPilot (talk) 11:03, 27 May 2026 (UTC)[reply]
Since all that's needed for the pre-RfC stage is a rough consensus among people who would support about what it is they'd be supporting, I think we're about there. @Gnomingstuff @Theleekycauldron: Do you have any thoughts here? If neither has objections, @MolecularPilot, I'd suggest you start the RfC proper in an hour or two; see § Procedural note below as well. -- Tamzin[cetacean needed] (they|xe|🤷) 11:05, 27 May 2026 (UTC)[reply]
no further thoughts - also no need to ping, rest assured I’m following the discussion Gnomingstuff (talk) 11:42, 27 May 2026 (UTC)[reply]
Could we add a link to Special:CreateAccount somewhere? Maybe as a parenthetical on the second paragraph to be

The Wikipedia community (which you can join) would like to take...

In solidarity, ScrubbedFalcon (talk) 12:11, 27 May 2026 (UTC)[reply]
OMG yes great idea, thank you! I think Help:Introduction would be more appropriate, though. - In solidarity, MolecularPilot (talk) 12:43, 27 May 2026 (UTC)[reply]
If I recall correctly I think people get taken through the same introduction tutorials after creating an account that are linked on the help page. I'm open to either option though. In solidarity, ScrubbedFalcon (talk) 12:49, 27 May 2026 (UTC)[reply]
  • I've changed the section heading to frame this as a pre-RfC workshop for now, and for the same reason removed it from T:CENT for now. I think we have a lot of good ideas here but it's good to have some sense of what wordings people like before we invite a much larger audience. -- Tamzin[cetacean needed] (they|xe|🤷) 09:43, 27 May 2026 (UTC)[reply]
  • This seems misguided to me. If there's a staffing or union issue at WMF, the WP:SIGNPOST would be a better venue to describe it. Plastering a banner on the Main Page is WP:POINTy campaigning and unlikely to appeal to readers. No-one is going to see any of the proposed banners and be prompted to make their first edit. It's just going to annoy readers while making Wikipedia look bad. Modest Genius talk 10:59, 27 May 2026 (UTC)[reply]
    I wouldn't characterise this as "disrupt[ing]" anything really, it's a small box, present for only 24 hours, that wouldn't impede access to anything - much less drastic than the strikes, lock-outs etc that have been proposed elsewhere. Reading Tamzin's version above (which I think is so-far the best and ideal proposed version), it is less about purely raising a staffing or union issue, but instead honouring Vibber's day and her contributions (as well as those of the laid off engineers) that are the entire reason we can use Wikipedia today, and their legacy. A purely signpost issue would not recognise these really fundamental and crucial contributions (which I can attest to as a MediaWiki developer) to readers, who also benefit greatly from Brooke's and the CommTech team's work, which was so great that even back in 2004 Jimbo attested that it deserved an entire day of recognition. I can't imagine why such a statement would annoy or make anyone think badly of Wikipedia, but if you do have reasons, we would love your feedback to keep workshopping and improve the notice to avoid this. - In solidarity, MolecularPilot (talk) 11:09, 27 May 2026 (UTC)[reply]
    I think to illustrate how non-disruptive this will be (which will also help with the RfC voter confidence) I will begin prototyping the Wikipedia:Main Page/sandbox with how it might look. Feedback is of course appreciated, and I'll comment here once I've got smth I think is workable. - In solidarity, MolecularPilot (talk) 11:12, 27 May 2026 (UTC)[reply]
    My mockup is published now and available at Wikipedia:Main Page/sandbox. I'd like to get some feedback on this before starting the full RfC, and if anyone has the time, I would be greatly appreciative! - In solidarity, MolecularPilot (talk) 11:18, 27 May 2026 (UTC)[reply]
    I've tightened up the prose a bit more, let me know if you have any objections. I feel like the ending doesn't quite hit right, but I'm still thinking on it. -- Tamzin[cetacean needed] (they|xe|🤷) 11:26, 27 May 2026 (UTC)[reply]
    The new prose seems good. Maybe it needs a little more tightening, I feel that the length of the box is inversely proportional to the chance of passing RfC, but I'm not sure. I agree about the ending, I'll think a bit about it too. Thank you again so much for all your help, hopefully we can get a good refined version out before the end of today. - In solidarity, MolecularPilot (talk) 11:31, 27 May 2026 (UTC)[reply]
    I flipped the order of the last two sentences and I think it ends better that way. But if I'm wrong feel free to just rv, I don't want to overthink this. Will think on if there's any way to tighten things further. -- Tamzin[cetacean needed] (they|xe|🤷) 11:32, 27 May 2026 (UTC)[reply]
    I think that sounds good. Maybe a bit of a crazy idea but what if we just make the main page announcement something like June 1, 2026, marks the 23rd annual Brooke Vibber Day. Brooke is a pioneering developer who has been perhaps the most influential maintainer of the software that powers Wikipedia. The community has an important message to share about Brooke, which can be accessed here. to minimise the real estate taken up on the main page, and then link to the full message. That way, it doesn't annoy uninterested readers much, but those who are interested can read more. But I'm not really sure about the phrasing, particularly "about Brooke" because it isn't just about her, and maybe we need to make the importance clearer. - In solidarity, MolecularPilot (talk) 11:44, 27 May 2026 (UTC)[reply]
    Okay so I thought of 3 versions (if we go for the short approach with link) but idk which is best:
  • Today, June 1, marks the 23rd annual Brooke Vibber Day, honoring a pioneering developer of the software that powers Wikipedia. The volunteer editing community has released an important statement concerning Brooke's legacy and the future of our technical teams, which can be read here.
  • June 1 is Brooke Vibber Day, celebrating one of Wikipedia's most influential software maintainers. In light of recent changes to our developer teams, the volunteer community has published a statement of gratitude and support, which can be viewed here.
  • Today is Brooke Vibber Day, honouring the developer who helped build Wikipedia. Read the volunteer community's urgent message regarding Brooke, our technical staff, and the future of community software development here.
- In solidarity, MolecularPilot (talk) 11:50, 27 May 2026 (UTC)[reply]
No, I think if you're gonna demand readers' attention, you don't want to also ask them to click on something. Most simply won't. I think what we've got in sandbox is roughly as good as it's gonna get. I'm not sure this'll pass in an RfC, but can't think of any way to make that more likely than what I've done. -- Tamzin[cetacean needed] (they|xe|🤷) 11:51, 27 May 2026 (UTC)[reply]
Actually, really good point, yeah. Re-reading what's in Sandbox right now, I agree and think it's pretty good. I feel the same about the RfC honestly, could go either way and I feel like some people won't like it, but the reason I started this thread, and will start the RfC, is because if we don't try, the chance of anything happening is 0%, but if there's an attempt, it still might happen. I'm going to take some time away from the computer now, and if there's no other comments and I (and you!) can't think of anything else, when I get back I might start the RfC. I think we have the rough consensus needed. Thank you again so much for all your help. - In solidarity, MolecularPilot (talk) 11:57, 27 May 2026 (UTC)[reply]
  • Professional lurker here -- I've been following this from the start, but haven't said anything until now. I don't think the main page should be used for this purpose. Like Modest Genius, I see this as rather pointed, and quite frankly I doubt our readers care. I would really prefer that the main page not be hijacked to spread the word about internal troubles... The people who are interested in this situation are already aware of it. MediaKyle (talk) 11:11, 27 May 2026 (UTC)[reply]

Procedural note

[edit]

Given how quickly things need to move, I would suggest that any RfC begin with a note that it will be procedurally closed at 12:00 on 31 May UTC no matter what, and that we try to get one or more admins to sign on to close it in advance of that. If there is no consensus at that time, then so be it; easier to have a clear endpoint and a clear process to get things closed and (if there's consensus for something) implemented. -- Tamzin[cetacean needed] (they|xe|🤷) 10:06, 27 May 2026 (UTC)[reply]

RfC: Brooke Vibber Day gratitude note

[edit]

From 1 June 2026 00:00 UTC to 2 June 2026 00:00 UTC, to celebrate the long-standing Wikipedia tradition of Brooke Vibber Day, should the Main Page include a gratitude note towards Brooke Vibber and other engineers which were recently separated from the Wikimedia Foundation, as stylised at Wikipedia:Main Page/sandbox (see comment below for various Options as to the text, the mockup represents only one such option)?

Note: This RfC will be procedurally closed at 12:00 on 31 May UTC, should a close fail to develop prior to that. - In solidarity, MolecularPilot (talk) 12:58, 27 May 2026 (UTC)[reply]

Options

[edit]

Option 1 - mentions controversy as context (current mockup on Sandbox)

Community Announcement: Brooke Vibber Day
June 1, 2026 marks the 23rd annual Brooke Vibber Day. Brooke is a pioneering developer who has been perhaps the most influential maintainer of the software that powers Wikipedia. Until recently, she was employed by the Wikimedia Foundation, a nonprofit that maintains Wikipedia's technical infrastructure; she was one of many seeking to unionise the Foundation's workers, who work tirelessly to support its mission to make knowledge available for free, for everyone. This month, however, Brooke and several other developers attempting to unionise were laid off or terminated by the Wikimedia Foundation, which has released a response and has denied engaging in any union-busting.
The Wikipedia community (which you can join) would like to take this year's Brooke Vibber Day to say "dankon" to Brooke for her decades of service to Wikipedia and its editors, and to thank the laid-off engineers for their years of hard work developing software listed on the Community Wishlist—a process many fear will languish with them gone. Over the past week, dozens of community members have made their feelings known in a lengthy discussion of the controversy and over 350 editors have signed a solidarity petition with Wiki Workers United. The terminated engineers are valued members of our community, and the Wikimedia Foundation is worse for their absence.
Option 2 - mostly gratitude, link to discussion
Community Announcement: Brooke Vibber Day
June 1, 2026 marks the 23rd annual Brooke Vibber Day. Brooke is a pioneering developer who has been perhaps the most influential maintainer of the software that powers Wikipedia . Brooke and a number of other engineers recently separated with the Wikimedia Foundation.
The Wikipedia community (which you can join) would like to take this year's Brooke Vibber Day to say "dankon" to Brooke for her decades of service to Wikipedia and its editors, and to thank the laid-off engineers for their years of hard work developing software listed on the Community Wishlist. Over the past week, dozens of community members have made their feelings known in a lengthy discussion on the issue.

Option 3: add .., including encouraging unionisation efforts at the Foundation. to the end of option 2

Option 4, middle ground that still mentions the unionisation and the solidarity efforts but remains more concise.
Community Announcement: Brooke Vibber Day
June 1, 2026 marks the 23rd annual Brooke Vibber Day. Brooke is a pioneering developer who has been perhaps the most influential maintainer of the software that powers Wikipedia. Until recently, she was employed by the Wikimedia Foundation, a nonprofit that maintains Wikipedia's technical infrastructure. This month, however, Brooke and several other developers attempting to unionise were laid off or terminated by the Foundation, which has denied engaging in any union-busting.
The Wikipedia community (which you can join) would like to take this year's Brooke Vibber Day to say "dankon" to Brooke for her decades of service to Wikipedia and its editors, and to thank the laid-off engineers for their years of hard work developing software listed on the Community Wishlist—a process many fear will languish with them gone. Over the past week, dozens of community members have made their feelings known in a lengthy discussion of the controversy and over 350 editors have signed a solidarity petition with Wiki Workers United.
Option 5 - all about Brooke with a link to Brooke's public statement, no mention of CommTech or the union
Community Announcement: Brooke Vibber Day
June 1, 2026 marks the 23rd annual Brooke Vibber Day. Brooke is a pioneering developer who has been perhaps the most influential maintainer of the software that powers Wikipedia, and is no longer employed by the Wikimedia Foundation. The Wikipedia community (which you can join) would like to take this year's Brooke Vibber Day to say "dankon" to Brooke for her decades of service to Wikipedia and its editors.

Option 6 - privacy-preserving pure gratitude version, resolves issues re consent and mentioning the current wiki drama

The idea is that we run it on Brooke Vibber day for the symbolic value to the community, but the readers wouldn't be familiar with that (and also for privacy reasons) so we don't frame it as that for them.

Community Announcement
Recently, several engineers and developers who were instrumental in maintaining and improving the software that powers Wikipedia, were laid off or terminated by the Wikimedia Foundation. You can find out more about the changes on this project page.
The Wikipedia community (which you can join) would like to thank these engineers and developers for the combined decades of service that they have dedicated to Wikipedia and its editors and readers. Their years of hard work developing software requested on the Community Wishlist was greatly appreciated.

Survey

[edit]
  • Oppose - Brooke is a genuine Wiki treasure, and I have no objection to using the main page to occasionally publicly celebrate some of the people who have made this project successful. I forget if we linked to e.g. Wikipedia:Magnus Manske Day or Wikipedia:Tim Starling Day from somewhere public in the past, but I'd support that kind of thing, too. What I'm opposed to is using the main page to get into these union busting allegations or to air other grievances about the WMF. We already know the vast majority of readers do not understand the differences between the WMF, its staff, administrators, editors, etc., and it just reads as a confusing advertisement of sloppy internal dysfunction, which does not seem in the best interest of the project IMO. — Rhododendrites talk \\ 12:56, 27 May 2026 (UTC)[reply]
    Thank you for your comment, and feedback in the Workshop phase as well (which informed Option 2). Would you support Option.2 then? Sorry, I really shouldn't have put the active RfC tag before putting the options in my comment. - In solidarity, MolecularPilot (talk) 13:06, 27 May 2026 (UTC)[reply]
    It says "pure gratitude", but as Robertsky points out below, it's not pure gratitude. I mean, even if it just linked to Brooke Vibber Day, it seems unlikely that page wouldn't have all the rest added to it. It's better than option 1, and I'll keep thinking about it, but I guess I wish we would express gratitude for major contributors even when it's not tied to active petitions and wikidrama. — Rhododendrites talk \\ 13:27, 27 May 2026 (UTC)[reply]
    Yes, I agree too! I didn’t even know some people had special days prior to all of this, and I think once the dust clears, we should seriously look into recognising all the other amazing days as well (as well as awesome contributors who don’t nessecarily have a day) in some way. I can definitely see how even wiki linking to “Brooke Vibber day” or the discussion still will likely contain info on the current drama, and respect whatever decision you make on what that means for your support / lack thereof. - In solidarity, MolecularPilot (talk) 13:38, 27 May 2026 (UTC)[reply]
  • Support both (prefer 1): I feel I have made my rationale sufficiently clear in the many discussions on Village Pump (WMF), am happy to expand upon at a later time if needed Gnomingstuff (talk) 13:40, 27 May 2026 (UTC)[reply]
  • Support both (prefer 1) 6, if consent is obtained then 4>1>3>2>5 Edited to prefer 6 per some convincing safety arguments raised by !voters. I think it is something nice to do to honour them, and is not really disruptive, as it is a small note, visible only for 24 hours, that does not otherwise obscure access to the page. A lot of feedback that was received in the workshop phase was that the initial drafts focused too much on union-busting allegations or grievances about the impact on the community and the wishlist. The current proposed version has been re-written to focus primarily on gratitude to Brooke and the CommTech team. - In solidarity, MolecularPilot (talk) 13:17, 27 May 2026 (UTC)[reply]
  • I am not opposing to any, but how is the second version "pure gratitude" when the controversy is mentioned? It shifts the context away from it being "pure gratitude". – robertsky (talk) 13:17, 27 May 2026 (UTC)[reply]
    Good point, I’ll rename it to “mostly gratitude, controversy only as link” - In solidarity, MolecularPilot (talk) 13:20, 27 May 2026 (UTC)[reply]
  • Support both, prefer option 1 6 and, if consent is obtained, 4>1>3>2 it is well within bounds for us to use the main page to celebrate Wikipedians, promote the community, and advocate for the community's needs. It does no one any good to pretend that there aren't rifts between the community and the WMF. If we really believe that the core role of the WMF is to support and enable the community then the community should be willing and able to publicly pressure the organization to serve the editing community's wants and needs. If we thought that the fundraising banners served no purpose for supporting the project, then we shouldn't have them; but we do think they serve the project, that's why we're ok with the WMF putting them up. Its the same here, putting pressure on the WMF to support the community serves the project in the long run even if it creates tension in the short term. We shouldn't underestimate the ability of readers to understand the issues at hand and we should be honest both with the WMF and our readers about what we want and need in order to improve the project. This banner, including the criticism of the WMF, serves those ends well and is in the best interests of the project. I'm convinced by the privacy issues brought up by Zzz Plant and agree with Toadspike below that consent for this needs to be affirmative. I hadn't thought about that being an issue yesterday when I wrote the support comment. Option 6 kind of serves the purpose I mentioned above and hopefully addresses other criticisms of the idea that I don't necessarily agree with. If consent can be obtained I prefer option 4. Edited twice, last at 07:49, 28 May 2026 (UTC) In solidarity, ScrubbedFalcon (talk) 13:18, 27 May 2026 (UTC)[reply]
  • Oppose. While I agree with many of the sentiments here, this would be hijacking the MP to make a political statement. RoySmith (talk) 13:21, 27 May 2026 (UTC)[reply]
    Can you explain why you think it's a political statement? --TheAuroraBorealis (she/they) 16:09, 27 May 2026 (UTC)[reply]
    One of the many definitions of "politics" in the dictionary: the relationships within a group or organization that allow particular people to have power over others. If one views the movement as a collective group, all these (here and elsewhere on wiki) are actions to hopefully achieve an realignment of relationships within the group/movement (therefore political). – robertsky (talk) 01:00, 28 May 2026 (UTC)[reply]
    To clarify, I am opposed to this being on the main page at all, no matter what the specific wording, including any possible future wordings. I also object to @MolecularPilot's attempt at spin. When I say "oppose", I mean "oppose". I don't need somebody else to analyze what they think I really meant, or what they hope they can convince other people I really meant or whether I'm still paying attention. RoySmith (talk) 14:04, 28 May 2026 (UTC)[reply]
    Please WP:AGF. Feeglgeef (talk) 14:15, 28 May 2026 (UTC)[reply]
  • Oppose option 1 and 4: While I disagree with the WMF's decision, I do not believe we should drag ordinary readers into internal drama, and, as mentioned above, this just seems like an attempt to stick it to the WMF. Nor should we promote or imply the allegations of union busting, for which there is little evidence. ARandomName123 (talk)Ping me! 13:24, 27 May 2026 (UTC) +4 ARandomName123 (talk)Ping me! 16:53, 27 May 2026 (UTC)[reply]
    Regardless of the result, Wikipedia:Brooke Vibber Day should be updated and expanded. It is too short right now, and it would be better for the readers to add some context and information on what Vibber has done. ARandomName123 (talk)Ping me! 13:30, 27 May 2026 (UTC)[reply]
    Absolutely agree, I've opened a discussion about it here. --Grnrchst (talk) 17:19, 27 May 2026 (UTC)[reply]
  • Support but... I'm torn between options 1 and 2 and would prefer a compromise with a shorter mention of the union and controversy. In particular, "separated with" might be misread as "Brooke walked out", and we should clarify that the WMF brought about the departures. Certes (talk) 13:29, 27 May 2026 (UTC)[reply]
    4 is a slight improvement but we should state that the WMF laid off the Community Tech Team (perhaps with a very brief description) rather than "developers attempting to unionise". I know AGF has limits, and I'm close to them, but we shouldn't suggest without evidence that union activity was the selection criterion for dismissal. Certes (talk) 19:28, 27 May 2026 (UTC)[reply]
  • Support 5>2 only. I feel that 1 makes too many assumptions. Linking to the VP discussion in 2 is sufficient at this point. (I'm not striking the previous, but I'd prefer 5 at this point over 2.) --SarekOfVulcan (talk) 13:29, 27 May 2026 (UTC)[reply]
  • Support both (prefer 1) 1>4>3>2. I wrote this wording, so my !vote might seem like a given here, but I'm actually a bit surprised to find myself in favor of putting anything on the Main Page relating to internal matters. It's nowhere near, say, the SOPA/PIPA blackout in terms of scope, but it is a rare action that would fall in the same category of blurring content and community matters. But, we are not categorically against such things. Wikipedia:Articles for deletion/Caesar DePaço closed with consensus for a statement from the community atop that article, which remains there, and compared to an actual article the Main Page already has a bit more leeway to drift from normal encyclopedic content. The question, then, is whether it should in this case. My !vote is informed by a few factors: First, Brooke Vibber Day has existed since 2004, and the idea of noting one of our internal holidays on the Main Page is not, on its own, that radical. Second, Brooke's firing is relevant to our readers, not just our editors. She is the person second-most-responsible for the software they read Wikipedia on (according to Special:Version), she was literally on the Reading team most recently at the WMF, and the WMF terminating her and other experienced developers is something that generally stands to harm our readers as well as our editors. Third, the related layoffs of CommTech lead to a situation where the WMF is no longer spending donor money on anything that donors would expect them to other than keeping the lights on. As long as our encyclopedic efforts are used to fundraise for donations, and as long as the WMF refuses to rehire the CommTech engineers, we are forced into being accessories to a lie. This banner, without being too aggressive or demanding any particular course of action from our readers and donors, lets them know about something they really ought to know. -- Tamzin[cetacean needed] (they|xe|🤷) 13:29, 27 May 2026 (UTC) ed. 14:27, 27 May 2026 (UTC)[reply]
  • Support both (prefer 1). I've long been a supporter of breaking the barrier between readers and editors, and of making Wikipedia's internal processes more transparent, as understanding those can only help our readers get involved more. Here, I don't think the banner makes the Wikipedia community look any more dysfunctional, but, to the contrary, shows it to be standing for what is just. Small detail: should "Community Announcement" be in sentence case to match the other boxes? Chaotic Enby (in solidarity · talk · contribs) 13:40, 27 May 2026 (UTC)[reply]
    Support option 4>1>3>2 per above. Chaotic Enby (in solidarity · talk · contribs) 14:14, 27 May 2026 (UTC)[reply]
  • Support Option 3>4>2>1, it celebrates Brooke, invites people to join the community (a flashpoint re banners where the WMF prioritises donations), and links to the discussion for journalists (it also has the most chance at gaining broad consensus at a time where we need unity). Sorry to say I’ve been swayed by the above !votes re option 1, the discussion linked to focuses heavily on the unionisation efforts so I think that link does more work than it may initially seem I think mentioning the unionisation dispassionately is more than due and reflective of the statement Brooke released. Option 3/2 is more classy for want of a better word, there will no doubt be more opportunities for greater escalation in the coming days Kowal2701 (talk, contribs) 13:44, 27 May 2026 (UTC)[reply]
    Add to the end of option 2 …, including encouraging unionisation efforts at the Foundation. Kowal2701 (talk, contribs) 13:54, 27 May 2026 (UTC)[reply]
    Nope, people have already voted on the existing wording. If you want to change it, propose an option 3. SarekOfVulcan (talk) 13:56, 27 May 2026 (UTC)[reply]
    Thanks, done :) Kowal2701 (talk, contribs) 14:06, 27 May 2026 (UTC)[reply]
  • Support both (prefer 1) —In solidarity with Wiki Workers United · ClaudineChionh (she/her · talk · email) 13:45, 27 May 2026 (UTC)[reply]
  • Support option 3 as it adds a little bit of extra context to option 2.FantasticWikiUser(Ts and Cs) 14:09, 27 May 2026 (UTC) Support 4 > 5 > 6 > 3 > 2 > 1 as a middleground. FantasticWikiUser(Ts and Cs) 14:23, 27 May 2026 (UTC)[reply]
  • Support both (prefer 1) Options 4>3>1>2 - (Summoned by bot) - per Chaotic Enby. I also believe that the Wikipedia community publicly taking a principled stance on this issue can only be a good thing. silviaASH (inquire within) 14:15, 27 May 2026 (UTC)[reply]
  • Oppose all ; I think (as often) Rhododendrites says it well. Article space is for readers, and that is especially true of the main page (I know it is probably a portal technically but ykwim). Wikipedia:Brooke Vibber Day is a community event, celebrating an immensely valued community member. Using it as a way to shoehorn a conflict between the community and the WMF into the main page does not serve any constructive purpose, and to the contrary would just be a massive showcase of dysfunction. How disruptive it would be is a matter of opinion, but WP:POINT certainly comes to mind here; no matter how important we think the point we are making is. Choucas 🐦‍⬛ 14:20, 27 May 2026 (UTC)[reply]
  • Support option 4>5>3>2>1. We definitely should be recognising Brooke and I think option 4 is the best proposal so far, followed by option 3; I think option 1 goes too hard for the front page banner and option 2 is too vague. --Grnrchst (talk) 14:46, 27 May 2026 (UTC)[reply]
    • Addendum to add second-choice support for 5. I'd prefer 4, as it gives to clearest context about everything that's happening, but I would much prefer Levevich's proposed version that keeps the focus on thanking Brooke over 2/3 (which are too vague) and 1 (which is too OTT for my liking). --Grnrchst (talk) 20:11, 27 May 2026 (UTC)[reply]
  • Support option 4>1>3>2. I think, especially at times like these, we have to realize that a lot of our readers actually do care about Wikipedia, and enjoy reading about it and the people behind it. I think this is a real heartfelt gesture, and it is important for the community to show our readers that we are not in fact mindless automatons. Echoing Tamzin and Grnrchst, I feel four is the best wording. Generalissima (talk) (it/she) 15:06, 27 May 2026 (UTC)[reply]
  • Oppose per Rhododendrites and Choucas. If it were ever appropriate to do something like this, it would be in response to an external attack that has caused direct harm to the community, the WMF, and the readers. Not to engage in infighting. Thebiguglyalien (talk) 15:15, 27 May 2026 (UTC)[reply]
    • Also, has anyone asked Brooke if she would be okay with this? It would be incredibly unethical, not to mention tacky, to support such a public use of her name to make a point without getting her go-ahead. Thebiguglyalien (talk) 15:15, 27 May 2026 (UTC)[reply]
      As I've discussed elsewhere, there isn't a way for anyone to satisfy this request without violating confidences, subjecting Brooke to legal risks, and violating WP:HARASS with respect to publicly disclosing private correspondence. What we can do is look to what she's said publicly while this discussion has been ongoing, which is that she supports WWU and encourages staff members to join it; she's also reacted positively to WP:WWUS' existence. And it is a matter of public record that she is aware of this discussion, as I pinged her in the linked thread. For so long as the WMF maintains its abusive practice of holding fired employees to non-disclosure and non-disparagement agreements, that combination of facts is the most we're going to get. -- Tamzin[cetacean needed] (they|xe|🤷) 15:29, 27 May 2026 (UTC)[reply]
  • Support only option 2 as the other options do not match established wikivoice. Kinopiko in solidarity with Esperanza 15:38, 27 May 2026 (UTC)[reply]
  • Support option 1. If not, 4 > 3 > 2. --TheAuroraBorealis (she/they) 16:10, 27 May 2026 (UTC)[reply]
    Just noted #5, wanted to say that I don't support it, it barely touches on the issue. --TheAuroraBorealis (she/they) 16:54, 27 May 2026 (UTC)[reply]
  • Support 5, oppose 1-4 and 6. I added Option 5, which include the thanks to Brooke, and links to Brooke's public statement on the mailing list, without mentioning the infighting/inside-baseball regarding CommTech and the union. As to why not 1-4, per Rhododendrites and Choucas0, and, similar to others, being generally uncomfortable with using Brooke's name/day to say anything beyond thanking her and linking to her own public statement (which invites WMF staff to join the union, but doesn't mention CommTech or the enwiki solidarity strike)--anything beyond using her own words would be putting words in her mouth IMO. I understand she may not be able to, or want to, speak publicly as frankly as she'd like. Until/unless that changes, we should err on the side of caution, and say no more than she's said publicly, by thanking her and linking to her public statement. Levivich (talk) 16:15, 27 May 2026 (UTC)[reply]
  • Comment why is our sentiment of thanks solely being delivered in an obscure Esperanto word? Surely on the list of things we want readers to take away from this, a synonym for "thank you" is last. 1brianm7 (talk) 16:20, 27 May 2026 (UTC)[reply]
    Agreed. I had to click the Wiktionary link to figure out what it meant. FantasticWikiUser(Ts and Cs) 16:57, 27 May 2026 (UTC)[reply]
    Have you checked WP:BROOKEDAY, or User:Brooke Vibber (and perhaps even eo:Uzantino:Brooke Vibber)? It may give you some pointers. Choucas 🐦‍⬛ 17:04, 27 May 2026 (UTC)[reply]
    @1brianm7: Please wee WP:BROOKEDAY. Jimbo's message notes "On [Brooke] Vibber day, Wikipedians everywhere greet each other in Esperanto", before saying "Dankon". -- Tamzin[cetacean needed] (they|xe|🤷) 17:04, 27 May 2026 (UTC)[reply]
    Ah, that is context I really should've checked. That makes sense. I still think it would be wise to say something like "dankon, thank you,", if only because the front page of English Wikipedia is really a much more impersonal context than a mailing list 22 years ago, or anything in projectspace for that matter. 1brianm7 (talk) 20:27, 27 May 2026 (UTC)[reply]
  • Support anything All of these look fine. Feeglgeef (talk) 16:23, 27 May 2026 (UTC)[reply]
  • Support 5>2, Oppose 1,3,4 I'm not happy with the WMF either, a state that is the default for me, and I'm not always nice about that, but going beyond the Wikipedia-specific issues of the encyclopedia itself to a possible employment dispute is I think a place that we should not be going. CoffeeCrumbs (talk) 17:05, 27 May 2026 (UTC)[reply]
  • Oppose per Rhododendrites & Choucas. Staraction (talk · contribs) 17:12, 27 May 2026 (UTC)[reply]
  • Support 4 > 1 > 3, oppose 2 and 5.
    I reject the "inside baseball" concerns about putting internal Wikipedia matters on the main page. We do regularly break our encyclopedic kayfabe with things like redlinks and maintenance tags as a tradeoff between improving the project versus presenting it. And to that end, I firmly believe one of the best ways we can convince readers to become editors is if we make it clear that we're not a bunch of faceless gargoyles wordlessly writing articles in total silence. Readers need to realize that the best way to support our project right now is not to throw money at the Foundation, but rather to get involved with our community and contribute. Making it apparent that we even have internal affairs and highly influential community members is going to be beneficial by drawing in editors, separate from what the internal affair in question is.
    Still, the reason to break kayfabe has to be a good one. WP:WWUGATE/WP:COMMTECHGATE is an important and self-evident enough fiasco for that purpose. Readers deserve to know what's going on.
    It's a bit before my time, but I can see why she would be considered such a treasured member of the community, and I have nothing but respect for Brooke and her contributions. However, not to be disrespectful, but I don't think that it's worth putting up a banner if all we're doing is celebrating Brooke's accomplishments.
    4 over 1, because I think it's more neutral and concise. 4 and 1 over 3 because 3's mention of these affairs, though sufficiently prevalent, feel MOS:EASTEREGGy. MEN KISSING (she/they) Talk to me, I don't bite! - Solidarity 17:26, 27 May 2026 (UTC)[reply]
  • Oppose - Bannering Brooke's name on one of the most highly trafficked home pages in the world risks opening her up to a massive amount of media scrutiny. I am not convinced that making one person the face of this controversy is the best way to support the affected workers or deliver justified criticism to the WMF. Zzz plant (talk) 17:49, 27 May 2026 (UTC)[reply]
    Addendum: option 6 was added after my !vote, but to clarify I do not believe it prudent to post any MP banner (regardless of phrasing) while the situation is still unfolding. Some of the affected workers may be re-hired in other departments and the union hasn't yet been recognized, let alone begun bargaining. I don't see why we should risk bungling a statement just to rush it out for June 1 symbolism (especially if Brooke isn't going to be mentioned). Also, I'd like to suggest that any further additions to the RFC such as "Note: If you are considering opposing on the grounds of privacy..." be timestamped or otherwise conveyed as newer. Zzz plant (talk) 20:05, 28 May 2026 (UTC)[reply]
    Note: I removed that note per WP:RFCNEUTRAL and it no longer applying to Option 6 since that option was updated. Levivich (talk) 20:13, 28 May 2026 (UTC)[reply]
  • Support 5 > 2 > Oppose all other wordings. First, less is more, longer messages here will cause more banner blindness and information overload. Second, per CoffeeCrumbs, we should stay focused the enwiki-specific issues. Third, I think that readers will be less inclined to conclude a political position is being advocated to them if they believe they're being presented "just the facts", on which they came to their own conclusion as to a position. Not saying 1/3/4 aren't factual, but I believe a reader would be more likely to conclude they're being told how to think. ~ A412 talk! 17:58, 27 May 2026 (UTC)[reply]
  • Option 5. If we're going to celebrate Brooke, then we should celebrate Brooke. Including information about the recent controversies is, in my opinion, not the best way to celebrate Brooke's legacy. The point of posting something like this on the main page is to honor Brooke, not to air grievances about the WMF. SuperPianoMan9167 (talk) 18:23, 27 May 2026 (UTC)[reply]
    Changing my !vote to oppose all because of privacy concerns. As others have said, we don't know if Brooke will be okay with the amount of scrutiny that comes from being featured on the main page, and if it isn't possible to obtain her consent, we shouldn't do it at all. If we do end up posting something, I still support option 5. SuperPianoMan9167 (talk) 23:17, 27 May 2026 (UTC)[reply]
  • Oppose all, for the same reasons as in the section above. The Main Page is not the appropriate place to discuss WMF staffing issues. If you want to complain about recent events, sign the petition, don't plaster them on the Main Page as a WP:POINT. Our readers don't know what the WMF is, let alone care about the internal controversies. This entire concept is misguided navel gazing. Modest Genius talk 19:07, 27 May 2026 (UTC)[reply]
  • Option 5 is fine; I don't like the rest. This would be sufficient to send a message to the WMF. I don't know the full facts of the case, but generally I think we should strive to make the front page neutral to uphold our reputation for objectivity. This is not an important or clear-cut enough issue for making an exception. JMCHutchinson (talk) 20:18, 27 May 2026 (UTC)[reply]
    Option 6 appeared later; I would still support only option 5. JMCHutchinson (talk) 12:37, 28 May 2026 (UTC)[reply]
  • Oppose all proposed options per others above; the main page is not for this.--Ymblanter (talk) 20:23, 27 May 2026 (UTC)[reply]
  • Oppose all if we want to take action to influence WMF decision making, which I am open to, we should do it in our name (the enwiki community), instead of using someone else's. NicheSports (talk) 20:27, 27 May 2026 (UTC)[reply]
  • Support 4>1>3>2. Wikimedia projects do not run on magic: WMF's firing of key software engineers, especially Brooke, is effectively an attack on the whole Wikimedia community, which justifies the exceptional nature of bringing this to attention on the main page. Boud (talk) 21:28, 27 May 2026 (UTC)[reply]
  • Support any - I'm completely fine with mentioning the controversy on the main page, but I primarily want to see a clean solid consensus, and any one of these statements on the main page and stable for the day. Tazerdadog (talk) 21:30, 27 May 2026 (UTC)[reply]
  • Support any, preferably 1. jp×g🗯️ 21:48, 27 May 2026 (UTC)[reply]
  • Support 1 (first choice), 4 (second choice), but any of those five however many banner options would work. Some1 (talk) 22:21, 27 May 2026 (UTC)[reply]
    If we're linking to the Village Pump WMF discussion in the banners, I suggest splitting that discussion ("WP:COMMTECHGATE") off to its own separate, standalone page before June 1. Some1 (talk) 10:56, 28 May 2026 (UTC)[reply]
  • Oppose all. With the right wording I could potentially support a banner thanking the CommTech employees and expressing concern about some of the WMF's recent choices, but I don't think tying it to a corny made-up holiday that celebrates one person only is going to come across as very credible to our readers. Extraordinary Writ (talk) 22:27, 27 May 2026 (UTC)[reply]
    Does #6 (added recently, which just thanks the employees with no mention of holiday) meet your criteria for "right wording"? I've tried to get it right and strike a good balance, with privacy considerations in mind as well. Always open to feedback on how to try and tweak it to be correct and something you'd support, and thank you for your existing feedback as well. - In solidarity, MolecularPilot (talk) 11:30, 28 May 2026 (UTC)[reply]
  • Comment: I've made some changes to the wording of the options to better comply with the Manual of Style. If anyone thinks any of my changes were bad or something feel free to rv. Feeglgeef (talk) 22:31, 27 May 2026 (UTC)[reply]
  • Oppose all; if I were forced to pick one, it would be #5. Among the many concerns raised above, my greatest worry is that this forces a massive violation of privacy on a person who has not confirmed whether she is okay with this. We need affirmative consent from the person who we will be exposing to the scrutiny of tens of thousands of people. The excuse that we should do this anyways because Brooke will not be able to consent due to external pressure/legal reasons/whatever else is laughable – I think we all know that's not how consent works. Toadspike [Talk] 22:40, 27 May 2026 (UTC)[reply]
    Why is it laughable to discern someone's wishes on a matter if they are legally barred from expressing them? Generalissima (talk) (it/she) 02:44, 28 May 2026 (UTC)[reply]
    I get all the arguments otherwise but it would be really, really, really, tremendously, crucially helpful to have even a secondhand “they’re ok with this” (or vice versa) statement, given that several oppose !votes kind of seem to assume they’re not (as in actively not, not just indifferent). Gnomingstuff (talk) 08:43, 28 May 2026 (UTC)[reply]
    Yeah. In the meantime (or in case that doesn’t happen), I’ve made option 6 (and thanks to those who helped c/e it) which doesn’t name anyone by name and just mentions “engineers” and I hope it can help sway over those who are (with quite good reason, as shown by some other !votes) conscious of privacy. - In solidarity, MolecularPilot (talk) 08:59, 28 May 2026 (UTC)[reply]
  • Support 1 and 4, no objection to 2 and 3. I understand the Brooke cannot express support directly. If she objects, then we should not go ahead. If we use 5, then its sending a message to WMF that readers won't get, but I think WMF will already be well aware of WP:WWUS and needs a stronger message which the press will pick up on.-Gadfium (talk) 22:42, 27 May 2026 (UTC)[reply]
  • If something receives media attention to a degree justifying its inclusion in the "In the news" box, it can be mentioned there. In my eyes, Wikipedia's main page is neither an acceptable place for political advocacy ("stop TTIP" or whatever) nor for broadcasting internal political views of a loud but small portion of the entire community. ~ ToBeFree (talk) 22:43, 27 May 2026 (UTC)[reply]
  • Oppose all: Recognising Brooke is one thing. What it seems to me, not so arguably (from a not so in-depth look), is an intentional disguise. The mostly gratitude addition (gratitude note) is overshadowed by the underlying drama. Be that as it may, supporting the past employees or the organizational efforts may or may not have an impact on Wikipedia editing, except for calls for an editing strike. While I have not followed the incident at all, and Florida is an "at-will" state, there are Federal as well as Florida state protection laws. Regardless of any editor's support or not, if the foundation's action violates the law, there will likely be consequences. Maybe a GoFundMe for those fired would be needed. The combined salary of the seven employees likely far exceeds $500,000.00 a year, so they are likely in a financial bind. There are probably far more important issues to be concerned about than Wikipedia hiring, firing, or possible union-busting practices. Apparently, a significant number of editors support the intended unionizing, but I feel the main page is not the place for this to play out in any form. -- Otr500 (talk) 23:18, 27 May 2026 (UTC)[reply]
    That is a very valid perspective which I can understand. Is option 5, which does not contain any elements of a "disguise" and does not mention at all (and is thus not overshadowed by) any current drama, and is (unlike the others) a purely gratitude note, acceptable to you? If not, what changes might you want? Thank you for your input. - In solidarity, MolecularPilot (talk) 01:10, 28 May 2026 (UTC)[reply]
    I have no opposition to accolades toward anyone the community views as an asset to Wikipedia. I feel we should just keep politics out. -- Otr500 (talk) 02:46, 28 May 2026 (UTC)[reply]
    Sorry, I don't really understand. So are you saying that the purely accolades and non-political #5 (and/or the work-in-progress privacy-perserving draft in my reply in S5A-0043) are thus acceptable to you? - In solidarity, MolecularPilot (talk) 02:49, 28 May 2026 (UTC)[reply]
  • Oppose all per above. Would probably cause more harm than good. Wizardman 00:44, 28 May 2026 (UTC)[reply]
  • Oppose per Toadspike. Also in consistency with my oppose at Watchlist-messages: Have we asked them if they want this?. – robertsky (talk) 01:18, 28 May 2026 (UTC)[reply]
  • Oppose all per many above. Call me old fashioned, I still believe the project should be nonpolitical.--Wehwalt (talk) 01:23, 28 May 2026 (UTC)[reply]
    To clarify that "Oppose all" includes opposing 6 and any others that may henceforth come. Wehwalt (talk) 12:18, 28 May 2026 (UTC)[reply]
  • Oppose all per the privacy concerns already mentioned above. I would support something similar to what Extraordinary Writ mentioned, but these are not it. S5A-0043🚎(Talk) 01:38, 28 May 2026 (UTC)[reply]
    Would this be something like what you are Extraordinary Wit are thinking is ideal, and also resolve the privacy issues? Just to clarify what you think would be best, so I can understand. If multiple people would prefer this, perhaps it can be added as an option (anyone reading this is welcome to boldy do it, you can modify my rough draft as well). The idea is that we run it on Brooke Vibber day for the symbolic value to the community, but the readers wouldn't be familiar with that (and also for privacy reasons) so we don't frame it as that for them. But I'm not too sure.
    Community Announcement
    Recently, several engineers and developers who were instrumental in maintaining and improving the software that powers Wikipedia, were laid off or terminated by the Wikimedia Foundation.
    The Wikipedia community (which you can join) would like to say thank you to for the combined decades of service that these engineers have dedicated Wikipedia and its editors, and for their years of hard work developing software listed on the Community Wishlist.
  • I have now added this as Option 6 to provide an alternative that those concerned about privacy or consent issues about naming Brooke can support. - In solidarity, MolecularPilot (talk) 03:10, 28 May 2026 (UTC)[reply]
    I get the gist behind this message but I feel like the phrasing is weird. Like, we say thank you to the workers, and then after that nothing? I feel like this particular phrasing doesn't express the gravity of the situation well, and also doesn't highlight the "expressing concern about some of the WMF's recent choices" part that EW mentioned. That being said I haven't really been eloquent in terms of expressing things myself so I can't say for certain how I would like it changed also, so I won't vote on this yet and see how it develops further. My opposition is primarily focused on the privacy concerns, so once that's out of the way I can reasonably support a message that addresses the recent situation. S5A-0043🚎(Talk) 03:35, 28 May 2026 (UTC)[reply]
    Thank you for your thoughts! Yes, I think that part is important as well. I am very bad at wording things so hopefully someone else can come along with fresh eyes and fix up the wording of it. As no-one has !voted on Option 6 yet, I give permission for it to be BOLDly changed by anyone who wishes, to reflect better wording and better address the concerns raised, or once it's been !voted on, encourage anyone to make a better new option, just wanted to get this privacy version out ASAP so any potential !voters could support it. - In solidarity, MolecularPilot (talk) 03:42, 28 May 2026 (UTC)[reply]
    I'm curious why we got five oppose votes in a short span, when there had been few before. Was this discussion linked somewhere? Generalissima (talk) (it/she) 02:47, 28 May 2026 (UTC)[reply]
    Well, first, it is a RfC and also on WP:CENT, in short, widely advertised as it could be on here. Second, it has been a day or so since it is opened and it gives people the time to evaluate further if they want to support or oppose or developed nuanced reasoning. Personally, I keep watch of this talk page primarily because of ITN. I suspect many admins do as well as they gravitate to the various main page sections. If you are thinking of canvassing, I am not aware of this discussion being shared in the offwiki communications I am in (even if others did, I wouldn't know as I don't monitor all communications like a hawk). – robertsky (talk) 04:28, 28 May 2026 (UTC)[reply]
  • Oppose with my entire being. Do you want the ongoing political attacks on enwiki to laser-focus on Brooke? Do you want Tucker Carlson going after her, or worse, Kiwifarms? This kind of attention gets people killed. Apocheir (talk) 02:52, 28 May 2026 (UTC)[reply]
    In response to the privacy concerns raised (thank you to everyone for raising them!), and this !vote, a new option, Option 6, has been added above which no longer mentions Brooke by name, as a potential compromise. - In solidarity, MolecularPilot (talk) 03:11, 28 May 2026 (UTC)[reply]
  • Support 6 in principle, oppose the rest per zzz plant and Toadspike. I have no problems with alluding to internal politics on the main page, but I'll admit that the privacy issues raised by the above editors concern me deeply. If the enwiki community wants to exercise the leverage it holds in Wikimedia affairs for a positive end, that's fine. Admirable, even. But I'm very uncomfortable doing so with a figurehead that has not/can not assent to such a major public display. DiscoursesonLivvy (talk · contribs) 03:41, 28 May 2026 (UTC)[reply]
    @DiscoursesonLivvy Note that I just reworded 6 per MolecularPilot's comment above on rewording. I fixed some grammatical issues and added a link to the VP page. In solidarity, ScrubbedFalcon (talk) 07:35, 28 May 2026 (UTC)[reply]
  • Oppose all, per above. Lets keep internal drama internal. Also, most of these are inaccurate; only Brooke has been laid off, the rest remain employed by the WMF - the main page is subject to our policies on WP:V, WP:NPOV, and WP:RS, and these proposed texts do not meet these policies. BilledMammal (talk) 04:33, 28 May 2026 (UTC)[reply]
    Huh? Has the Foundation since reversed its stance, I’m a bit confused. Can you please show where you got this info from? - In solidarity, MolecularPilot (talk) 04:55, 28 May 2026 (UTC)[reply]
    See this comment by a WMF employee. SuperPianoMan9167 (talk) 04:58, 28 May 2026 (UTC)[reply]
    Interesting. I (and also what seems to be the community consensus in the replies to that post) think they still meet the definition of being laid off according to RS, which is when “your employer ends your employment for reasons beyond your control”, which may “ include their salary for a period after they finish working” [3] Their current employment has undoubtedly ended, and just because they are being allowed to apply for new employment opportunity at the WMF and kept on payroll for one month, it doesn’t mean they aren’t laid off presently (the same website also notes “In particular situations, being laid off may be temporary, and you could be rehired” later, which supports they notion that in the current state the engineers are laid off by definition, which could change later but is unlikely as none of the open roles are core PHP MediaWiki work, and these engineers aren’t from data science etc.) - In solidarity, MolecularPilot (talk) 05:07, 28 May 2026 (UTC)[reply]
    There are multiple interpretations, but to state one on the main page, especially in wikivoice, would require clear sourcing in reliable sources. BilledMammal (talk) 05:16, 28 May 2026 (UTC)[reply]
    So they’re laid off in 30 days rather than 0 days; 30 days of security is certainly preferable to 0, but making anything more of it seems like splitting hairs (and also doesn’t dislodge the union busting allegations). Gnomingstuff (talk) 09:26, 28 May 2026 (UTC)[reply]
    WP:VPW#Response from WMF 24 May. They're still employed by the WMF, and are interviewing for new roles. If they fail to get new roles they will be laid off, but that hasn't happened yet and we shouldn't presume that it will. BilledMammal (talk) 05:01, 28 May 2026 (UTC)[reply]
    Thanks. As I detailed above, I personally think using RS definitions they are "laid off", but can understand your perspective. Perhaps to ensure 100% accuracy in all interpretations, we can say "positions were eliminated" rather than "laid off" if enough people would prefer that in the messages. I also just fixed up your comment above as I think you typed 5 tildes which will only add the date, not 4 which does the signature. - In solidarity, MolecularPilot (talk) 05:16, 28 May 2026 (UTC)[reply]
  • Support 6 or similar. Also, I support adding a link to any page that would give more context about this immediate issue that the community is dealing with. — Newslinger talk 05:22, 28 May 2026 (UTC)[reply]
    @Newslinger Note that I just reworded 6 per MolecularPilot's comment above on rewording. I fixed some grammatical issues and added a link to the VP page. In solidarity, ScrubbedFalcon (talk) 07:33, 28 May 2026 (UTC)[reply]
  • Support 6 I believe that specifically naming people can be a potentially detrimental violation of privacy without express permission. Nevertheless, what I have read regarding the situation troubles me. In this day and age, we should be hiring more people to work on the underlying tech, not firing them, whether due to misguided thinking that they can be replaced by vibe coding, attempts to bust unions, or both. A response from the community should be made so that this isn't just swept under the rug. ᴢxᴄᴠʙɴᴍ (ᴛ) 07:13, 28 May 2026 (UTC)[reply]
    @Zxcvbnm Note that I just reworded 6 per MolecularPilot's comment above on rewording. I fixed some grammatical issues and added a link to the VP page. In solidarity, ScrubbedFalcon (talk) 07:35, 28 May 2026 (UTC)[reply]
  • Support I don't know much about Vibber but can confirm that Magnus Manske impressed me as someone worth remembering and thanking for their foundational work on Wikipedia and we should make an effort to do this. A special banner might be be too much per banner blindness but note that we already have a place on the main page for listing special days: On this Day. An entry there would be easy and comparatively uncontroversial. Andrew🐉(talk) 07:45, 28 May 2026 (UTC)[reply]
  • Support 6, oppose everything else — per Apocheir. We don't want various criminals like Kiwifarms to have a person representing the community.--KEIT (talk) 08:49, 28 May 2026 (UTC)[reply]
  • Support 6 only as the only safe option. Layzner (Talk) 09:49, 28 May 2026 (UTC)[reply]
  • Support any of these - David Gerard (talk) 12:43, 28 May 2026 (UTC)[reply]
  • Oppose all. Both because of privacy issues, and because it would be inappropriate for Wikipedia to editorialize on its main page, especially about internal politics of little interest to readers. Sandstein 13:34, 28 May 2026 (UTC)[reply]
    My concern is that a certain owner of X will use this to push his "wikipedia is woke" narrative as proof Grokpedia is better. Let's not give him anymore fuel ... Oaktree b (talk) 15:21, 28 May 2026 (UTC)[reply]
    He could have all the fuel in the world and it wouldn't even come close. Forks rise and forks fall, but Wikipedia has always come out on top. Feeglgeef (talk) 15:51, 28 May 2026 (UTC)[reply]
  • Oppose all. I'm in agreement with ToBeFree. I've agreed with many open letters. I've disagreed with some too. I don't think the main page should be used in a way that implies an opinion is shared by more people than it is. Daniel Quinlan (talk) 13:39, 28 May 2026 (UTC)[reply]
    Thanks for your feedback. I tried to strip all opinions and implications in #6 (and Levivich tried the same with #5) to just say what happened without taking a side, but if there’s any implications left I’d appreciate knowing what so they can be improved to match better with their intention. - In solidarity, MolecularPilot (talk) 21:34, 28 May 2026 (UTC)[reply]
  • Oppose all, weak support for Option 6. Promo does not belong on the main page, this is better served in a Wikemedia website post somewhere. We don't wish Jimbo a happy birthday, or much mention his contribution anywhere in mainspace. I'd like to keep Wiki as neutral as possible. Oaktree b (talk) 15:18, 28 May 2026 (UTC)[reply]
    WP:NOTWIKI. Feeglgeef (talk) 15:53, 28 May 2026 (UTC)[reply]
    Oaktree has been there for more than 20 years, I don't think throwing the acronym of an old humorous essay at him is really warranted. Choucas 🐦‍⬛ 18:45, 28 May 2026 (UTC)[reply]
  • Oppose all. I am highly uncomfortable with the idea of using Brooke as a mascot for this message, which would be true even if she explicitly accepted it, and she hasn't. I also find it hard to support the new option 6 given that the water is muddy about the exact circumstances of these layoffs at the moment. —TechnoSquirrel69 (sigh) 16:38, 28 May 2026 (UTC)[reply]
    @MolecularPilot, @TechnoSquirrel69 For 6, thoughts on replacing were laid off or terminated with were made redundant. To my understanding this was the phrasing used by Selena and should accurately reflect the staffs current status. Sohom (talk) 17:39, 28 May 2026 (UTC)[reply]
    This is a gross corporate euphemism — note to scolders, the adjectives here apply to the noun “euphemism,” and a euphemism is not a person — that we should not legitimize. Gnomingstuff (talk) 18:48, 28 May 2026 (UTC)[reply]
    @Gnomingstuff I mean, I do plan to personally refer to it as a layoff until there is confirmation that all of the engineers were re-hired. But, I do think the Main Page is a different environment where we should try to use whatever term is legally correct and in this case "laid off" is not legally correct, even though socially (imo) the correct sentiment to have. Sohom (talk) 21:52, 28 May 2026 (UTC)[reply]
    Look, I don’t really like it, but if it’s what’s needed to remove ambiguity and get support I’m fine with that change I guess. - In solidarity, MolecularPilot (talk) 21:31, 28 May 2026 (UTC)[reply]
  • Support Option 6, oppose the rest. qcne (talk) 20:19, 28 May 2026 (UTC)[reply]

Comments

[edit]
  • Statistics - approx. 24 hours in
    While of course this is a !vote and consensus, not numbers, will decide the outcome, I still think statistics are important to understanding the emerging sentiment, so I thought I would do an analysis now that we are approaching the approximate 24 hour mark for my own interest. I didn't see any reason to keep my results private, so thought I would share them for everyone's context. Note that is my own best effort at a rough count, and might not be right. It includes everyone but Andrew Davidson (supporting, but raises OtD as a better option and potential banner blindness, so I don't think it's fair to call it a support of specific text versions in the context of my analysis) and ARandomName123 (opposing "harsher" versions but neutral on other versions), which were excluded as I don't think they cleanly mapped into a binary "oppose" or "support" (and it balances out anyway, as it's one arguable oppose and one arguable support).
    Of the 20 oppose !voters:
  • 11 (55%) were concerned that such a notice is not appropriate for Main page / is a vector for airing WMF grievances and allegations.
    • This is a fundamental issue and cannot really be addressed by any new versions.
    • I do note that some of these !votes focused around airing WMF grievances were made before the much softer wording of #5 and #6 was developed, and those versions may resolve some of these concerns, though it depends on the opinion of the !voters and if they return to the page to check, and I understand that even #5 and #6 still hint and link to ongoing issues.
  • 9 (45%) were isues with using Brooke’s name - privacy, consent, harassment, corny to use the holiday etc
    • All of these issues have now been fully addressed with the proposed #6 now, which was recently added. Again, it depends if they return to check, and some people might still not support it.
Of the 33 support !voters:
  • Note that for the purposes of this category, as not all options were present at the time of !voting for each person, I have roughly grouped versions into "softer" (2/5/6) and "harsher" (1/3/4) which matched up with most !votes anyway. 31 of the 33 !votes fitted into my classification system.
  • 10 (30%) preferred harsher versions, but would accept softer versions
  • 5 (15%) preferred softer versions, but would accept harsher versions
  • 11 (33%) preferred only softer versions
    • Of these 11, 5 (45% of the 11, 15% of the support !voters) supported only Option 6 over privacy concerns
    • 1 (Jmchutchinson) supported only Option 5
  • 2 (6%) supported only harsher versions
  • 3 (9%) would support "anything"
  • 2 (6%) did not fit into this classification system (i.e. ranking a "harsh" one, then a "soft" one, then another "harsh" one in their preferences)
Anyway hope this helps, I do love numbers, and sorry if there are any inaccuracies! - In solidarity, MolecularPilot (talk) 12:17, 28 May 2026 (UTC)[reply]
I think you should be careful about extrapolating supports and opposes based on prior votes and later options, because your 70/30 result as it is looks very contrived. Someone who opposed for stated reasons might agree with later ones mentioned specifically in opposition to new versions as well; the same goes for supports. It is not reasonable to expect participants to adjust their !votes and the associated reasoning just because people keep adding options. It takes only one person to add a new one, and that is why this RfC is becoming increasingly messy, now at 6 options when we started with only two. I saw that coming and that is why I said "oppose all", but I absolutely should not be expected to go edit my initial comment to add all the subsequent reasons to oppose all the subsequent options that did not exist at the time of my !vote. Choucas 🐦‍⬛ 12:39, 28 May 2026 (UTC)[reply]
Yes, it was just for curiosity and I have qualified it as not to be relied upon and may be (and probably is, for the reasons that we both raise) inaccurate. I guess the percentages maybe put too much emphasis on that section, so I will edit it to just the raw numbers as the more important thing is the actual analysis of current !votes and that is where I want the focus. - In solidarity, MolecularPilot (talk) 12:42, 28 May 2026 (UTC)[reply]
So you are leaving admittedly incorrect and at best speculative numbers in bold. Wehwalt (talk) 13:08, 28 May 2026 (UTC)[reply]
At this point, I didn't think they would cause so much drama, sorry, I thought the qualification with extrapolated is okay, but I will HAT now to make super clear. - In solidarity, MolecularPilot (talk) 13:11, 28 May 2026 (UTC)[reply]
Seems like an apt place to put a pet essay from a few years back: Wikipedia:No pre-close summaries, please. — Rhododendrites talk \\ 18:42, 28 May 2026 (UTC)[reply]

How do you remove a note on OSM?

[edit]

Users can resolve their own notes. Is this true if you don’t have an account? Because I erroneously reported something and can’t remove the note. MarbleMax (talk) 21:56, 27 May 2026 (UTC)[reply]

Hi @MarbleMax, you might be in the wrong place. Go to this link: WP:HELPDESK if you need help in general, or to this link: WP:TEAHOUSE if you need help with editing. MEN KISSING (she/they) Talk to me, I don't bite! - Solidarity 22:01, 27 May 2026 (UTC)[reply]
Thanks! MarbleMax (talk) 23:44, 27 May 2026 (UTC)[reply]
@MarbleMax: If you need help with OpenStreetMap, you can visit their documentation wiki at https://wiki.openstreetmap.org/ or their forum at https://community.openstreetmap.org/. (The OpenStreetMap and Wikipedia communities are friendly towards each other, but use different systems and infrastructure and are not formally affiliated.) —In solidarity with Wiki Workers United · ClaudineChionh (she/her · talk · email) 22:46, 27 May 2026 (UTC)[reply]
Thanks! MarbleMax (talk) 23:44, 27 May 2026 (UTC)[reply]

Hi friends, a question about articles

[edit]

if someone makes a spam article, how can i nominate it for deletion Monathephantom (talk) 13:56, 28 May 2026 (UTC)[reply]

You might want to ask for help at the helpdesk or the teahouse. You can also look into the Deletion process. In solidarity, ScrubbedFalcon (talk) 14:27, 28 May 2026 (UTC)[reply]