[Wikitech-l] Temporary accounts enabled in Wikimedia CI and deploying to testwiki next week
Greetings, This patch[0] sets the default configuration in Wikimedia CI to enable the temporary accounts feature.[1] This means: PHPUnit, Selenium, API-Testing, and QUnit tests run in an environment where temporary account autocreation is enabled. ## Why? Next week, the Trust and Safety Product team is deploying the temporary accounts feature to testwiki.[2] Later this year, we will move forward with deploying to other production wikis. By enabling temporary accounts in CI, we increase the likelihood that new code works smoothly with the temporary accounts feature. ## What do I need to do? This time, nothing. All MediaWiki core, extension and skins tests pass, whether temporary accounts are enabled or disabled.[3] For new PHPUnit tests, please make use of `TempUserTestTrait` to disable the temporary accounts feature for tests that make assertions specifically about anonymous IP editing. We also recommend that you enable temporary accounts in your local development environment by adding `$wgAutoCreateTempUser['enabled'] = true;` to your LocalSettings.php. ## Questions? Please contact us[4] or file a task on Phab and tag it with “#Temporary accounts”. [0] https://gerrit.wikimedia.org/r/c/mediawiki/core/+/980947 [1] https://www.mediawiki.org/wiki/Trust_and_Safety_Product/Temporary_Accounts/For_developers#How_should_I_update_my_code, https://www.mediawiki.org/wiki/Help:Temporary_accounts [2] https://phabricator.wikimedia.org/T348895 [3] https://phabricator.wikimedia.org/T355879 [4] https://www.mediawiki.org/wiki/Talk:Trust_and_Safety_Product/Temporary_Accounts Cheers, Kosta & Thalia, Trust and Safety Product and Szymon Grabarczuk (he/him) Lead Movement Communications Specialist (Product & Tech) Wikimedia Foundation <https://wikimediafoundation.org/> ___ Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
[Wikitech-l] Re: Article source code style guide
Kinda depends on whether you're asking for Wikimedia-specific rules or general MediaWiki rules. Speaking just about Wikimedia, each local wiki community may have different preferences. There is no process for enforcing global (meaning, cross-wiki) recommendations in this regard, so in practice, even if someone from the technical community came up with universal rules, no one would really need to stick to them, and if they did and their contribution was reverted, the argument from these rules could be ignored. Best, Szymon Grabarczuk (he/him) Lead Movement Communications Specialist (Product & Tech) Wikimedia Foundation <https://wikimediafoundation.org/> On Thu, Jun 27, 2024 at 11:34 AM Bináris wrote: > Hi, > > is there anywhere a $subject? > > My first question is: is it better to leave an empty line under section > titles or not? I would like to see pros and cons. Is there a consensus for > preferred way? > (I think source code style guides are primarily within the scope of > programmers and not in that of users without programming experience, that's > why I ask here.) > > -- > Bináris > ___ > Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org > To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org > https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/ ___ Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
[Wikitech-l] Update your tool's code to prepare for temporary accounts
(This message is about Wikimedia-specific changes. Nothing mentioned here is mandatory for the third-party MediaWiki users.) Hello everyone, I am reaching out on behalf of the Wikimedia Foundation Trust and Safety Product <https://www.mediawiki.org/wiki/Trust_and_Safety_Product> team, working on the Temporary Accounts <https://www.mediawiki.org/wiki/Trust_and_Safety_Product/Temporary_Accounts> project (formerly, IP Masking). We are making preparations for deployment on testwiki. We want to minimize the impact of temporary accounts on the ecosystem of tools and features. Before deployment, we'll ask for stewards' confirmation that critical workflows are not affected. Now, we would like to ask you to check the impact on code you maintain. There may be breaking changes! We do not have a firm deadline for deployment yet. We will let you know as soon as we do. We would like to ask you to consider updating your tool's code over the next weeks, if the tool works on any/all production cluster wiki. If it only works on selected wikis and testwiki is not one of them, you will have more time to update it. If you think it will take longer than that to update your code, please let us know on our talk page <https://www.mediawiki.org/wiki/Talk:Trust_and_Safety_Product/Temporary_Accounts>. For a full explanation of the technical change, please read our documentation <https://www.mediawiki.org/wiki/Trust_and_Safety_Product/Temporary_Accounts/For_developers>. In particular, the section on how your code might need to be updated <https://www.mediawiki.org/wiki/Trust_and_Safety_Product/Temporary_Accounts/For_developers#How_should_I_update_my_code?>. Some examples of ways code might be affected (not exhaustive): - A feature looks for the IP address in the user name (it will no longer be found). - A feature that relies on looking at the user’s ID to identify if the user is registered or unregistered. Temporary accounts will not have a user_id of 0. - A feature works differently for unregistered vs registered users. See more examples <https://www.mediawiki.org/wiki/Trust_and_Safety_Product/Temporary_Accounts/For_developers#How_should_I_update_my_code?>. We may have discovered your issue already and filed a Phabricator task using the #temporary-accounts tag. You may wish to file a subtask of T337012 <https://phabricator.wikimedia.org/T337012>. We hope that this task will help us all as the technical community coordinates on tools requiring updates. If you have any questions or would like to learn more about the project, take a look at our project page and reach out to us on the talk page <https://www.mediawiki.org/wiki/Talk:Trust_and_Safety_Product/Temporary_Accounts>. Thank you! Szymon Grabarczuk (he/him) Lead Movement Communications Specialist (Product & Tech) Wikimedia Foundation <https://wikimediafoundation.org/> ___ Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
[Wikitech-l] Re: March 2023 Datacenter Switchover
Hello everyone, Just as Clément wrote in the first message, on *Wednesday April 26*, there will be a switchover from our secondary data center in Texas back to the primary data center in Virginia. That day, starting at *14:00 UTC*, there will be a brief (just a few minutes) read-only period for all Foundation-hosted wikis. We have sent a message to all the wikis; there will also be a banner informing about the maintenance, displayed 30 minutes before this operation happens. If you're interested in the details about the switchover, scroll up to Clément's message :) Thanks, Szymon Grabarczuk (he/him) Senior Community Relations Specialist Wikimedia Foundation <https://wikimediafoundation.org/> On Wed, Mar 1, 2023 at 9:11 PM Igal Khitron wrote: > I see. Very well, I'll open a task. > Thank you. > Igal > > בתאריך יום ד׳, 1 במרץ 2023, 22:07, מאת Brian Wolff : > >> You should probably just file a bug. >> >> Its certainly plausible it had something to do with data center switch, >> but it could just as equally be unrelated. It requires someone to >> investigate what part of the system failed (job queue? Varnish? Swift?) >> which would then lead to a root cause. Its pretty impossible to say without >> further investigation, and speculating on list is probably not helpful. >> >> -- >> Bawolff >> >> On Wednesday, March 1, 2023, Igal Khitron wrote: >> >>> Hello. >>> Is the new files bug happening because of the database switch? And if it >>> is, do you fix it? >>> The story: If you reupload file, local or on commons, the new version >>> does not create thumb, and the old one is shown in articles. The only way >>> to see a new version is opening the file in media: namespace. I waited for >>> hours. So, you can't edit files any more. I read the commons reupload log a >>> bit, looks like it's not just my problem. The regular things, clear cache, >>> purge, null edit, do not help. >>> I think there should be a phab task created, but I'd like to know your >>> answer first. >>> Thank you. >>> Igal (user:IKhitron) >>> >>> >>> בתאריך יום ד׳, 1 במרץ 2023, 19:26, מאת Giuseppe Lavagetto < >>> glavage...@wikimedia.org>: >>> >>>> Specifically: >>>> >>>> if we measure read only time as "an editor can't start an edit because >>>> wikis are read only", then the read-only time is 119s; >>>> if we measure it by the last timestamp of an edit being saved, that's >>>> 94 seconds. >>>> >>>> As Amir explained, we leave some room for propagation of the MediaWiki >>>> read-only mode (about 10-15 seconds) and for in-flight edits (another 10 >>>> seconds) before we set the databases to read-only as well. >>>> >>>> I think 2 minutes of read-only for such a complex operation are the >>>> good balance between reasonable change safety and reduction of impact; we >>>> could reduce the read-only time by another 10-20 seconds with some more >>>> aggressive moves (like clearing the DNS recursor caches) but I don't think >>>> there's a big value there at this point. >>>> >>>> I'll add: if anyone is interested in knowing more and they're coming to >>>> the hackathon, I'll be happy to make an impromptu session about how we >>>> handle this procedure. >>>> >>>> Cheers, >>>> >>>> Giuseppe >>>> >>>> On Wed, Mar 1, 2023 at 6:16 PM Amir Sarabadani >>>> wrote: >>>> >>>>> It's a bit complicated. >>>>> When SRE sets the read-only mark, they start counting from that time >>>>> and it starts propagating which takes a while to be actually shown to all >>>>> users but some users might still see the RO error while some actual writes >>>>> are happening somewhere else because the cache is not invalidated yet (I >>>>> think it has a TTL of 5 seconds but I need to double check). We still >>>>> consider that as RO time because it's affecting users regardless. >>>>> >>>>> HTH >>>>> >>>>> >>>>> >>>>> Am Mi., 1. März 2023 um 18:06 Uhr schrieb Dušan Kreheľ < >>>>> dusankre...@gmail.com>: >>>>> >>>>>> Clément Goubert and everybody, >>>>>> >>>>>> I analyzed https://stream.wikimedia.org/v2/stream/r
[Wikitech-l] Re: [Wikimedia-l] Re: Re: Re: Re: Uplifting the multimedia stack (was: Community Wishlist Survery)
Hello, I'd like to refer to the original subject of the discussion - tomorrow is the last day for submitting proposals for the Community Wishlist Survey 2022. Apart from that, everyone is welcome to translate, promote, and discuss proposals: https://diff.wikimedia.org/2022/01/10/what-improvements-in-wikimedia-platforms-would-you-like-to-see-help-the-wikimedia-foundation-to-grant-the-communities-wishes/ Best wishes, Szymon Grabarczuk (he/him) Community Relations Specialist Wikimedia Foundation On Wed, Jan 12, 2022 at 2:43 PM Strainu wrote: > În mar., 11 ian. 2022 la 08:01, Kunal Mehta a scris: > > > > So I think the status quo can be changed by just about anyone who is > > motivated to do so, not by trying to convince the WMF to change its > > prioritization, but just by doing the work. We should be empowering > > those people rather than continuing to further entrench a WMF technical > > monopoly. > > > > Counterexample: > > https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/message/G2QTRJFAUKLE45SFTFUHOOTOBR6G3DP3/ > (this was the situation that I quoted in my first email on this thread > as the WMF refusing to even do reviews). > > Maybe it's just the multimedia part that it's in this desperate > situation, but I can totally see volunteer developers getting > discouraged quickly if their patches are outright ignored. > > Strainu > ___ > Wikimedia-l mailing list -- wikimedi...@lists.wikimedia.org, guidelines > at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and > https://meta.wikimedia.org/wiki/Wikimedia-l > Public archives at > https://lists.wikimedia.org/hyperkitty/list/wikimedi...@lists.wikimedia.org/message/DU6BEXDGDN3UZLCKPR6LN7KIV45MPRRH/ > To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org ___ Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
[Wikitech-l] Community Wishlist Survey 2021
We invite all registered users to vote on the 2021 Community Wishlist Survey[1]. You can vote until 21 December for as many different wishes as you want. In the Survey, wishes for new and improved tools for experienced editors are collected. After the voting, we will do our best to grant your wishes. We will start with the most popular ones. We, the Community Tech[2], are one of the Wikimedia Foundation[3] teams. We create and improve editing and wiki moderation tools. What we work on is decided based on results of the Community Wishlist Survey. Once a year, you can submit wishes. After two weeks, you can vote on the ones that you're most interested in. Next, we choose wishes from the survey to work on. Some of the wishes may be granted by volunteer developers or other teams. We are waiting for your votes. Thank you! [1] https://meta.wikimedia.org/wiki/Special:MyLanguage/Community_Wishlist_Survey_2021 [2] https://meta.wikimedia.org/wiki/Special:MyLanguage/Community_Tech [3] https://meta.wikimedia.org/wiki/Special:MyLanguage/Wikimedia_Foundation Kind regards, Szymon Grabarczuk (he/him) Community Relations Specialist Wikimedia Foundation <https://wikimediafoundation.org/> ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] 2021 Community Wishlist Survey
The 2021 Community Wishlist Survey[1] is now open! This survey is the process where communities decide what the Community Tech[2] team should work on over the next year. We encourage everyone to submit proposals until the deadline on 30 November, or comment on other proposals to help make them better. The communities will vote on the proposals between 8 December and 21 December. The Community Tech team is focused on tools for experienced Wikimedia editors. You can write proposals in any language, and we will translate them for you. Thank you, and we look forward to seeing your proposals! P.S. If the pages are not fully translated into your language, visit a dedicated page[3], be bold, and add the translations! [1] https://meta.wikimedia.org/wiki/Special:MyLanguage/Community_Wishlist_Survey_2021 [2] https://meta.wikimedia.org/wiki/Community_Tech [3] https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2021/Translation_hub Kind regards, Szymon Grabarczuk (he/him) Community Relations Specialist Wikimedia Foundation <https://wikimediafoundation.org/> ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia Strategy 2017
I'd like to invite you to participate in the Wikimedia Movement Strategy discussions[1], about our wider movement's overall goals, "What do we want to build or achieve together over the next 15 years?". It's currently in the first stage, of broad discussion. There are further details in the related MetaWiki pages[2] (incl. FAQ[3], calendar and process[4], list of other simultaneous communities' discussions[5], etc). Also, if you're interested in helping facilitate and summarize the discussions on MediaWiki.org, and to bring back the summaries of what the other communities are discussing, in the weeks ahead, please let me know. Thanks. [1] https://www.mediawiki.org/wiki/Project:Wikimedia_Strategy_2017 [2] https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2017 [3] https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2017/Frequently_asked_questions [4] https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2017/Process [5] https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2017/Outreach/List *Szymon Grabarczuk* MetaWiki Strategy Coordinator ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] New tutorial for interactive graphics on Wiki
Great! now, I think it should be marked for translation. On 31 December 2015 at 08:38, Pine W wrote: > The tutorial looks nice! I will take a look when I am less distracted by > finance reports. Thank you for working on this. > > Pine > On Dec 30, 2015 22:37, "Yuri Astrakhan" wrote: > > > I just finished writing a tutorial on how to build interactive Vega > graphs > > for Wikipedia. And yes, we could build video games this way too :) > > > > > https://www.mediawiki.org/wiki/Extension:Graph/Interactive_Graph_Tutorial > > ___ > > Wikitech-l mailing list > > Wikitech-l@lists.wikimedia.org > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > ___ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > -- *Szymon Grabarczuk* Free Knowledge Advocacy Group EU Head of Research & Development Group, Wikimedia Polska pl.wikimedia.org/wiki/User:Tar_Lócesilion <http://pl.wikimedia.org/wiki/User:Tar_L%C3%B3cesilion> ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
