Discussion: This is an interview of Wikimedia Foundation Chief Advancement Officer Lisa Seitz-Gruwell with questions submitted by User:The Land. The current link has the questions for this interview; the remainder of the content (answers) will be filled in before November 23, 2022.
@KStineRowe (WMF) and The Land: Note that EpicPupper has retired from both the Signpost and Wikipedia. JPxG is the sole current editor-in-chief.
I provided some initial feedback on the questions here.
Re-reading the first question just now it strikes me that it states as fact that the WMF uses "a large part of its funds for grantmaking".
Per the financial statements published earlier this month, "Awards and grants" amounted to just under $15 million in the 2021–2022 year just ended. This is less than 10% of revenue. I'd submit it is therefore a comparatively small part of WMF funds – especially when compared to the $88 million salary bill. In the interest of truthfulness, could we perhaps agree to just call it "a part" and name the amount?
@The Land: Thanks for organizing this interview. I support you in managing this however you will do it, and I appreciate your effort in this and in many other conversations related to Wikimedia community governance. I completely endorse your methods for this, but as you are doing this, I want to read the room and context here just in case anyone checks in on The Signpost editorial process. I am talking to myself and the ether here: I am making no requests of anyone and am just documenting thoughts.
This publication The Signpost is community organized and has no budget.
The Wikimedia Foundation is investing valuable resources in this discussion. With 4 board members personally commenting here, I can only imagine that the weight of the legal department, communication department, and grants department is behind them. When a group of people each of whom cost US$200,000/year get personally involved in an issue, they also appoint their staff to invest labor. It is hard for me to estimate the resources consumed by this discussion, but as my own guess, I will say that 4 groups of 5 people each discussed this issue for 10 hours. 4*5*10=200 labor hours * US$100/hour = $20,000 conversation minimum. I could be underestimating WMF investment, and perhaps by end of November 2022 $100,000 maximum investment could go into this if there are some 1-hour meetings of 5-10 paid staff people. I have never seen a response like this from the WMF in the past.
The core issue is conflict between the WMF and the Wikimedia community on how money is spent. There are many big social and ethical issues in play here. I will not list them or describe them. I think lots of people who are here experiencing this know the issues, but I know of no one who has summarized them as journalism.
Neither The Signpost nor the Wikimedia Community has any funding or financial resources to develop these conversations, produce journalism, or do research on these issues. The money is all on the WMF to build a narrative. There is an imbalance here.
While the Wikimedia community wanted a response to these financial questions, the WMF has responded much more than I think anyone expected.
I do not personally see anything pointed, controversial, or aggressive about the Wikimedia community asking questions. What I see are basic community demands for representation and access to information of the sort that no one ever imagined would be controversial.
User The Land: thanks for stepping up, thanks for doing this interview. You will do great. You are still just one volunteer talking to a corporation which is running responses from grants team to legal team to communications team and then through the board. I think you will do fine. Your interview is still a volunteer interview and does not represent the entirety of the Wikimedia community, although I do recognize you as a Wikimedia community "leader" (not that we have leaders) and that you are an active editor, well liked, in good standing for many reasons.
Thanks and if The Signpost can support you such as is possible from a volunteer newspaper, then ask. You definitely have encouragement to proceed as you have planned, and I hope that others find your effort as inspiring as I do. Bluerasberry (talk)20:11, 23 November 2022 (UTC)[reply]
Update: After conversations with user:MPaul (WMF) I have revised a couple of the questions to reflect the changed situation as a result of the RfC and the commitments made by the WMF during and after it. I've updated the submission page to reflect this. The Land (talk) 17:58, 25 November 2022 (UTC)[reply]
Discussion: In this statistical article, we will look at the results of whether Wikipedia administrators have a healthy attitude and whether they have enough rest or psychological distance for a healthy attitude. The text of article is in Slovak language. Dušan Kreheľ (talk) 21:36, 23 December 2022 (UTC)[reply]
@Dušan Kreheľ: This is acknowledging and thanking you for your submission. We're a little behind on reviewing this page, having just published a new issue and short-staffed as always. I'll bring this and other unreviewed submissions to the team's attention. ☆ Bri (talk) 04:23, 4 January 2023 (UTC)[reply]
This submission has a lot of issues. First, it's not in English, which could be considered a nonstarter (but I'll AGF that you could translate it by press time). Second, the methodology behind the article is lacking: you don't provide any relevant evidence for why editing once a day for a year is unhealthy, the focus on administrators seem arbitrary, and specifically calling out hundreds of editors by name and accusing them of unhealthy habits, which seems in poor taste and likely to get people mad at both The Signpost and you if published. There's maybe a human interest article in there somewhere, in the vein of "what percentage of editors edit every day", but this draft isn't it, and there's a good chance it would be deleted if taken to WP:MFD. signed, Rosguilltalk05:03, 4 January 2023 (UTC)[reply]
@Rosguill: The article was expends, please You look.
Administrators are public positions, so they should be able to handle a higher level of criticism. It may be expensive today, but if it is required on a regular annual basis, then later it may become a matter of course for administrators and become a certain critical standard.
The changes don't substantively address my criticisms regarding methodology (or language). Unless you can point to a WP:MEDRS-compliant source that backs up your assessments of what is and isn't healthy behavior, you shouldn't be making claims to that end. signed, Rosguilltalk18:48, 4 January 2023 (UTC)[reply]
Discussion: This piece is about a new tool, View it!, that will be launched in January. In the piece we talk about why it was created, how to access/install and use the tool. We also announce our launch, on January 12th. JamieF (talk) 18:14, 30 December 2022 (UTC)[reply]
@JamieF: thanks for submitting your piece. We were right on the verge of publishing the latest issue when this came in. We'll be sure to get it reviewed soon. ☆ Bri (talk) 04:20, 4 January 2023 (UTC)
Published. jp×g20:18, 31 January 2023 (UTC){{completed}}[reply]
The good old days, when lipograms roamed free in mainspace
Discussion: Opinions offered about the tendency of institutions to evolve over time to incorporate more and more inwardly-focused and rules-bound processes, case in point the rules around the article Gadsby. ☆ Bri (talk) 16:29, 11 January 2023 (UTC)[reply]
Discussion: Philosophical bridges and Wikipedians. Two bridges presented. One about a user who has edited for longer than the oldest person alive. The second about the milestone of 50,000 featured articles. Part of a larger series. FacetsOfNonStickPans (talk) 18:51, 13 January 2023 (UTC)[reply]
Discussion: Our research into a cultural gap in Wikimedia projects' coverage of visual art was published early this month. We briefly describe the problem and invite the community to help close the gap, which we are doing through editathons, a target article list, and outreach to cultural institutions. MartinPoulter (talk) 16:32, 26 January 2023 (UTC)[reply]
Discussion: We in the Ukranian wiki community have published several assortments of stories of Ukrainian Wikimedians during the war over the past year – one, two, three. Now that the world has marked an anniversary of the full-scale invasion, and the war still rages, we though we'd bring a new collection of stories. Aced (talk) 10:23, 2 March 2023 (UTC)[reply]
@Aced: IMHO this looks like it can be published with minor copyediting, but we'll see what the EIC @JPxG: says. There's also a potential problem with the request for donations. I personally don't see any reason that we can't include it, but I'm sure it will be controversial, so we'll have to discuss it among the staff. Smallbones(smalltalk)19:43, 11 March 2023 (UTC)[reply]
Looks like Op-ed to me. I'm not sure it's finished yet, seems a little short? I can provide more feedback if you like. Set status to In development/pending approval for now. ☆ Bri (talk) 16:13, 6 April 2023 (UTC)[reply]
@Lambiam: Can you add an "in conclusion" section or something like that? It doesn't have to be long, just to wrap up the thoughts presented in the first section and give the reader something to chew on. I think once that's done, I can move it to the Signpost draft area. ☆ Bri (talk) 18:48, 11 April 2023 (UTC)[reply]
I've added a section, not really a conclusion but nevertheless something readers can chew on. The final three sentences are OR – I hope that is allowed in the Wikipedia Signpost --Lambiam19:54, 11 April 2023 (UTC)[reply]
Discussion: "Signpost statistics between year 2005 and 2022" These are my statistics based on publicly available data at the time mentioned in the article. Dušan Kreheľ (talk) 13:00, 5 April 2023 (UTC)[reply]
Looks like In Focus to me. I like the tables you have created, we will need to beef up some text to explain what's being presented but either the original author or a Signpost staff member (maybe me) can do that. Maybe needs discussion about how we do that, prior to approval. ☆ Bri (talk) 16:11, 6 April 2023 (UTC)[reply]
@Dušan Kreheľ: I marked this "needs clarification" for text that is highlighted in the draft. I'm not sure that I correctly interpreted something you wrote about the "home wiki". ☆ Bri (talk) 23:09, 6 April 2023 (UTC)[reply]
Thank you. I've updated status to "needs review" which is the last step prior to approval for publication. It will of course also get a copyedit pass from other Signpost editors. ☆ Bri (talk) 16:48, 7 April 2023 (UTC)[reply]
Discussion: Two part series summarising the priorities for the Wikimedia Foundation next year including the staffing, budget and other changes and importantly will link through to the many ways people can share their inputs, thoughts, priorities and feedback. MPaul (WMF) (talk) 14:36, 6 April 2023 (UTC)[reply]
Hello Bri and @JPxG I have drafted this submission for the News from the WMF section. Thank you @Bri for the suggestion on the section. I hope you can review and consider it for the next Signpost issue. I'd like to come back for the Signpost issue after this one for the second part of this series. MPaul (WMF) (talk) 14:47, 14 April 2023 (UTC)[reply]
Discussion: The second article in a series describing the priorities and work of the Wikimedia Foundation. The article invites Wikimedians to collaborate with the Foundation.
Discussion: This is my view of what a wikipage parser should look like, which should have a new implementation and a new RFC about the Mediawiki wiki(page) language should come. Dušan Kreheľ (talk) 13:56, 3 December 2022 (UTC)[reply]
@Dušan Kreheľ: Some good thoughts there, but also some fundamental misunderstandings, in particular here: Even if the grammar of the wiki page is defined (it exists, but I can't find the link somehow), there is no RFC document that would specify the entire syntax and semantics of the wiki page, and especially how to deal with bad inputs.
The reason why you couldn't find the link to that parser grammar is that it doesn't exist, for various reasons that are explained e.g. in this 2013 blog post:
The only complete specification of Wikitext’s syntax and semantics is the MediaWiki PHP-based runtime implementation itself, which is still heavily based on regular expression driven text transformation. The multi-pass structure of this transformation combined with complex heuristics for constructs like italic and bold formatting make it impossible to use standard parser techniques based on context-free grammars to parse Wikitext. [...] No invalid Wikitext: Every possible Wikitext input has to be rendered as valid HTML – it is not possible to reject a user’s edit with a “syntax error” message. Many attempts to create an alternative parser for MediaWiki have tried to simplify the problem by declaring some inputs invalid, or modifying the syntax, but at Wikimedia we need to support the existing corpus created by our users over more than a decade [as of 2013, i.e. two decades by now].
Do wikitext constructs behave like DOM trees? No. * Wikitext has no spec and hence no formal semantics * Behavior emerges out of legacy PHP parser's implementation [etc.]
Proposals such as yours to reform and consolidate the wikitext syntax by making breaking changes had been made before, e.g. at the 2011 Berlin hackathon (Wikipedia:Wikipedia Signpost/2011-05-16/Technology report) by the Sweble team. Back then the Wikimedia Foundation was embarking on its Parsoid/VisualEditor work and rejected such proposals in favor of a more conservative approach (which still ended up causing thousands of small bugs and inconsistencies with the existing wikitext content and much community frustration).
A Signpost article about this topic that is ignorant of this background and the reasons behind the current state of affairs (cf. Chesterton's fence) will not be be very useful for our readers.
With this and your other recent Signpost drafts about technical topics, I would encourage you to first solicit feedback from experts before submitting them to the Signpost. You can do this by e.g. by posting on the Wikitech-l mailing list or by pinging knowledgeable folks directly (regarding parser matters, that might involve people from the WMF team that currently works on Parsoid, such as Subbu or Cscott).
I deleted the sentence "Even if the grammar …". It is not necessary.
Why to have this article:
If the dwiki project was successful, it could later influence the Wikimedia project. It would probably not be fair not to comment/notify now.
"Plan to throw one [version] away; you will, anyhow" (The Cathedral and the Bazaar) – History or other things can be good or bad. For example: OpenOffice vs LibreOffice, initd vs systemd and GCC vs EGCS.
I informed on wikitech-l@lists.wikimedia.org before: 1, 2 and 3.
if You do not consider the article suitable, I will accept the refusal of publication.
Thanks for the excellent summary of the current parser situation, @HaeB. Note that there is a good spec now for the *output* of the parser, at mw:Specs/HTML, which can be considered an Abstract syntax tree for the wikitext input. So I think there's still fertile ground for experimentation of alternative wikitext syntaxes using the DOM spec as an interchange format. As long as your new syntax can roundtrip to/from the standard DOM spec HTML, then you can interoperate with legacy wikitext. You can edit an article via "legacy wikitext" -> "MediaWiki DOM" (via Parsoid) -> "your own format" (via your own serializer) and then save it with a pipeline like "your own format" -> "MediaWiki DOM" (via your own parser) -> "legacy wikitext" (via Parsoid). If done properly, this won't leave dirty diffs. There's a thought experiment proposal of this sort at phab:T149659 (slides). We've also thought about eventually storing the HTML DOM representation directly in the database (phab:T112999), although no work in either of those direction is expected any time soon. But maybe this inspires you toward some ways a "new wikitext syntax" could interoperate with our current infrastructure. C. Scott Ananian (talk) 17:07, 28 February 2023 (UTC)[reply]
No invalid Wikitext: It's is none problem. Example, from 2024-01-01 is set the new wiki parser. So new politic:
the older version (before 2024-01-01) are parsing with the old parser,
the revision with __STANDART_WIKI_SYNTAX__ is with new parser
the revision in 2024-01-01 and later, are parser with new parser.
How is the problem, to have in MediaWiki the 2 parsers.
"The multi-pass structure of this transformation combined with complex heuristics for constructs like italic and bold formatting make it impossible to use standard parser techniques based on context-free grammars to parse Wikitext." For my one parser implementacion was none problem to create syntax abstract tree.
Don't have a standard? After all, if I want to create a syntax that will be used for the next 20 years from today, then it would be appropriate to standardize the syntax.
Isn't not having a defined syntax just putting off the problem for later?
{{completed}} I think that, given the concerns raised so far, it's unclear whether this would be worth covering (especially without an actual technical proposal having been opened anywhere). We may revisit this later, if such a proposal is opened and enjoys some support. jp×g22:03, 16 July 2023 (UTC)[reply]
Discussion: Hello, I'm submitting an obituary for Wikipedia editor Dthomsen8, who died in November 2022. This was brought to my attention on my talk page here. The piece is currently located at my talk sandbox, and I've added the submission template. I think it's ready but Signpost staff can edit it there if it's not quite suitable for publication. Best regards, Baffle☿gab02:25, 12 July 2023 (UTC)[reply]
Discussion: @JPxG: I would like to submit this article for consideration for the next Signpost given past interest in Foundation fundraising. Thank you JBrungs (WMF) (talk) 09:51, 14 July 2023 (UTC)[reply]
Discussion: This piece is about a dara investigation which looks at the importance of children of celebrities in the French cinema. PAC2 (talk) 21:14, 20 June 2023 (UTC)[reply]
@Lemonaka: I think this is an interesting piece, but it could do with a little work. It seems like the lede is kind of buried here: I had to read through it a few times to figure out the thrust (that sometimes a global ban doesn't fix the issue, and sometimes an LTA only stops when someone actually calls the irl police, and whether this is justified and some cases where this has happened). I think it would be good for this to be expanded on a little: is it good? Should it happen more? Less? Who should be taking action on this? You ask "is a global ban the last step?", which is an interesting question, so it would be good to explore this in a little more detail (why it ought to be, why it oughtn't to be, etc). jp×g18:17, 29 July 2023 (UTC)[reply]
I've added some content, adding the last paragraph for hoping less, adding the second and third paragraph on Maybe a solution? to describe " Who should be taking action on this?", hoping this will improve a little on this article.---Lemonaka11:08, 31 July 2023 (UTC)[reply]
Discussion: A piece I wrote in 2019 following several technical improvements to the Signpost's workflows. It could possibly be updated with whatever's been new since,like the previous/last navigation help for individual columns. Headbomb {t · c · p · b}13:57, 17 July 2023 (UTC)[reply]
I noticed this out in the doldrums. Based on my carousing through talk page archives, there was quite the drama over this one. I am not quite sure what the hell was going on there -- presumably some feud thirty years in the making whose only surviving chronicle requires me to use FidoNet, but all of that aside, it seems pretty decent to me. I see no issue with publishing this as-is, with appropriate notes to indicate what stuff is current and what stuff is outdated. This is from 2019, so I imagine that some of the publishing process and organizational schema has changed in the last four years; might it be appropriate to run it as a cobweb? jp×g08:14, 29 July 2023 (UTC)[reply]
Well that's what I suggested it for. I'll move to /cobwebs but I'll leave the mini intro to you, because I don't think I'll be able to put it in context without gnashing teeth. Headbomb {t · c · p · b}08:27, 29 July 2023 (UTC)[reply]
Can do. I think I am going to start calling these something a little more dignified than "cobwebs" -- that was only ever supposed to be a placeholder name lol -- maybe "apocrypha". jp×g18:18, 29 July 2023 (UTC)[reply]
Discussion: This article discusses the work Ocaasi and I did as part of a project with CUNY and the nonprofit organization Hacks/Hackers. Harej (talk) 16:13, 28 July 2023 (UTC)[reply]
Seems to be a good fit for the /Forum column. @Harej:, do you want me to set up the signpost draft in your sandbox directly (which will get moved upon acceptance/publication), or create a /Drafts subpage so you can put the relevant content in a preformatted article sandbox (so your sanbox doesn't get moved)? Headbomb {t · c · p · b}16:43, 28 July 2023 (UTC)[reply]
As described in the article, WP:VSAFE is the project created from this effort. It is necessary for us to include this because we were paid for this work. Harej (talk) 17:31, 28 July 2023 (UTC)[reply]
In the "What is the problem?" and later in the "The vision" sections, I'd like to see an acknowledgement of current efforts. I'm a bit biased there, but WP:CITEWATCH (Signpost coverage) is "centralized tracking of citations" (I presume you mean problematic ones), as is WP:JCW (Signpost coverage), if you mean a citations in general. I'm not really looking for praise here, but rather a discussion of strengths/weaknesses and how Credibility bot builds/improves upon this or supplements this, or whatever.
I am referring to literally all citations, not just problematic ones. CITEWATCH is good for what you are describing. Harej (talk) 18:12, 30 July 2023 (UTC)[reply]
Again, that's just citations that are formatted in a certain way. I am talking about a database of literally all references, formatted with a template or not. Harej (talk) 13:40, 31 July 2023 (UTC)[reply]
In the solutions section, you mention workspaces as a generic solution that scale up, that can work for WikiProjects or something. It would be good to have an example, possibly with an explanation/instructions of how to set things up. These explanations could be on a separate page, like WP:AALERTS/SUB.
The example is WP:Vaccine safety. At the moment there isn't really anything you can "set up" as it is all a work in progress, only working for vaccine safety at the moment.
So let's say I'm interested in setting up something like this for WP Physics. Where would I go, what would I need to have, and/or what would I need to do? Headbomb {t · c · p · b}18:06, 31 July 2023 (UTC)[reply]
In the "Our Vision" you write, "Tagging talk pages with WikiProject templates will no longer be necessary to get the benefit of automated reporting." This is a bit hard to believe/understand without the above example.
Could have gone a bit more into details, but at the same time it's your piece. As long as existing efforts are mentioned and discussed/contrasted with, I'm happy. Headbomb {t · c · p · b}17:18, 31 July 2023 (UTC)[reply]
@Harej: I have a couple concerns about this piece, which I am not sure can be addressed solely through me copyediting it. Basically, my understanding of this is that the bot gives reports and alerts on which articles have references to reliable, unreliable, and no-good very-bad sources. These reports are based on Wikipedia:Vaccine safety/Perennial sources. This looks to me like a project-specific and subject-focused analog of WP:RSP, made almost entirely by three users (Sj, Harej and Netha Hussain (WikiCred)). While there are citations for the individual table entries, these do not seem to support a high confidence in the ranking. The citation for Proto Thema being rated "mixed", for example, links to this archived RSN thread, which has literally no discussion at all: a single post, by Cinadon36, which was archived without anybody else having responded. Did anybody agree with this claim? Disagree? Was it just caught by the archive bot before anyone had seen it?
Now, I am not saying that Cinadon36 is an idiot or a liar. For all I know, Proto Thema is a huge pile of garbage and should never be trusted for anything. However, when we look at Wikipedia:Vaccine safety/Alerts, we see a bunch of domains listed with simple emoji indicators as "unreliable". There's no link to the RSN thread, or even to the perennial sources table -- and no indication that any of these things reflect actual consensus or policy or guidelines, as opposed to "one person in 2021 saying a website sucked". It is a bit strange to me that this bot is being operated, and these pages maintained, and the suggestion made that people use them to carry out article work, while no caveats are given (and no information is made easily available to its users) about the rather-sketchy provenance of the actual reliability indices themselves. If these resources were put together with grant money, was there no stage of the development process where these issues were raised? This is somewhat troubling to me. While there are some serious issues with WP:RSP being treated like Scripture based on (sometimes very partisan or very poorly-attended) noticeboard discussions, it seems to me like a tool such as this using a local-consensus fork of RSP has all of the same issues in greater form.
JPxG, that is valuable criticism of what has been built. In order for us to improve what we built, we need to do outreach. This piece is part of that outreach. Are projects required to be perfect before they're covered in The Signpost? Harej (talk) 20:57, 31 July 2023 (UTC)[reply]
I suppose my context for this is that in this same Signpost issue, we cover (in N&N) an article from Unherd, which alleges among other things that Wikipedia is serving as a conduit for "narrative control wizardry" by the hands of governments and NGOs who seek to supplant our editorial processes with blah blah blah blah. Ideally, we would be able to respond by saying that this is a big pot of nonsense, and our determinations of content are made on the exclusive basis of discussions with solid consensus among volunteer editors. While it's obviously not the case that this software is in itself sinister, the issue of sources being determined to be good or bad in an opaque way by people who've been paid by advocacy organizations (are they political? maybe -- some people, see above, seem to think they are) definitely seems like something that ought to be to addressed up front, without waiting for criticism. jp×g02:21, 1 August 2023 (UTC)[reply]
"Are projects required to be perfect before they're covered in The Signpost?" I would argue that that's not a requirement, but at the same time, it ought to be clear what the current limitations and caveats are. I would personally consider getting help from WP:RSN/WP:BOTN/WP:VPT people first, flesh out some of what needs to be done and get it to a state where a person that goes 'hey, what if I want to use this in WikiProject Foobar?' will have an answer.
It took me a while to get WP:CITEWATCH in a 'ready for mainstream editors' state, but once it was, it got heavy buy in from the community. And that's when a Signpost post can have maximal impact. If you just want technical people / citation people to chip in before it's ready for everyone, I would wait a bit before the signpost piece. I know I'm certainly interested to help. Headbomb {t · c · p · b}02:51, 1 August 2023 (UTC)[reply]
I agree with JPxG and Headbomb that this lack of integration with existing efforts (in particular WP:RSP) and potential for Wikiproject-based balkanization look like a major problem, and possibly not something that can be fixed retroactively with a "oh by the way everyone is welcome to use this bot too". (NB, I had similar concerns forming in my head a couple of days ago already after seeing this project promoted in the "Wikipedia Weekly" group on Facebook.)
That said, I think we should separate editorial judgment about such a Signpost draft article from assessment of the project overall, in particular if we are active in both spaces (Signpost and source/citation-focused bots).
What is needed though is a clear disclosure in or near the byline whether any of the authors were paid to work on this project. Regards, HaeB (talk) 03:37, 1 August 2023 (UTC)[reply]
I saw the footer, but that's not a disclosure - it does not inform the reader that the two writers of the article were paid for their work on the project that their article extolls (and presumably also for writing the article itself, assuming that the grant includes outreach work for the project). And yes, readers should be informed about this from the beginning. Regards, HaeB (talk) 04:02, 1 August 2023 (UTC)[reply]
Discussion: This piece is about the Wikipedia Library, which provides free access to research materials to make it easier to write content on Wikipedia for active editors with more than 500 edits. I hope JPxG it can be considered for the next Signpost issue. Udehb-WMF (talk) 09:49, 3 August 2023 (UTC)[reply]
In a column titled "News...", it might be useful to clarify the news angle (if any), in particular for the benefit of the many readers who are already aware of The Wikipedia Library, and possibly to inform scheduling. It doesn't seem that this is an announcement of new features or such? Or is it meant to be published on the occasion of an anniversary date (Eleven years ago)? Or is it to promote your August 18 Wikimania session? (There are a lot of those. From a reader perspective a more neutral and comprehensive overview might be preferable, even if limited to those offered by WMF.)
Thank you for your valuable feedback, HaeB. I appreciate your insights.
To clarify, the article is not specifically intended to promote the August 18 Wikimania session or any other event. When we were writing the piece, our intention was not to presume that every reader knew about the Wikipedia Library. Hence, we aimed to provide a comprehensive overview of the Wikipedia Library, its recent developments, and the benefits it offers to active editors with more than 500 edits. While some readers may already be familiar with the Wikipedia Library, it would be beneficial to ensure that those unfamiliar with it can have a better understanding through this article.
I will certainly consider your suggestion and collaborate with my colleagues to highlight any news angle better within the piece.
Discussion: This article is in part an announcement of the successful contribution of 335k images to Commons from the Columbus Metropolitan Library. It also documents some photographers' smaller image contributions that I view to have similarly strong importance. ɱ(talk)04:03, 8 August 2023 (UTC)[reply]