Wikitech-l June 2022

wikitech-l@lists.wikimedia.org

37 participants
34 discussions

by Siegfried Schmitt

Hello Everyone, I would like to propose two - probably new - features for MediaWiki. Since my native language is German, I would like to discuss these features with some developers from Germany, Austria, or Switzerland. My Englisch is really bad and therefore, I would prefer to discuss in German language. Please feel free to contact me via e-mail. Best regards, Siegfried -- Siegfried.Schmitt(a)web.de

1 year, 9 months

How to get Top 1000 contributors list?

by Shrinivasan T

Hello all, I like to get top 1000 contributors for ta.wikipedia.org based on their usercontribution metric. is there any code this or api? Please share. Thanks. -- Regards, T.Shrinivasan My Life with GNU/Linux : http://goinggnu.wordpress.com Free E-Magazine on Free Open Source Software in Tamil : http://kaniyam.com Get Free Tamil Ebooks for Android, iOS, Kindle, Computer : http://FreeTamilEbooks.com

1 year, 9 months

+2 nomination for Dreamy_Jazz in mediawiki/extensions/CheckUser

by Kunal Mehta

Hi, I have nominated Dreamy_Jazz for +2 rights in the CheckUser extension, please feel free to comment at <https://phabricator.wikimedia.org/T311331>. Thanks, -- Legoktm

1 year, 9 months

🚂🌈Summary of 1.39.0-wmf.16 train deployment

by Brennen Bearnes

This email is a summary of the Wikimedia production deployment of 1.39.0-wmf.16 * Conductor: Brennen Bearnes * Backup Conductor: Dan Duvall * Blocker Task: T308069 <https://phabricator.wikimedia.org/T308069> * Current Status <https://versions.toolforge.org> 📈 Numbers Sparklines comparing with the last 5 trains. * 212 Patches █▆▃▅▁ * 0 Rollbacks ▁▁▁█▁ * 0 Days of delay ▁▁▁█▁ * 4 Blockers █▁▁█▁ ✨ Trainbow Love 🥰 Thanks to folks who helped report or resolve blockers: * Seddon * Tim Starling * PleaseStand * Timo Tijhof * Aaron Schulz * Tyler Cipriani * Jon Robson * James D. Forrester Worth highlighting in particular: Krinkle's breakdown of increased Mcrouter requests <https://phabricator.wikimedia.org/T310532#8004500>. -- Brennen Bearnes Release Engineering Wikimedia Foundation

1 year, 9 months

No train the week of 2022-07-11

by Tyler Cipriani

Hi All There will be no train the week of 2022-07-11 (Mon, 11 Jul–Fri, 15 Jul)—this is the Wikimedia Foundation's Inspiration Week. There is a long-term calendar of upcoming deployment disruptions available on Wikitech: https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar Thanks! Tyler Cipriani (he/him) Engineering Manager, Release Engineering Wikimedia Foundation

1 year, 9 months

Matahariagung7@gmail.com

by Tomy Anggara

Open main menu Wikimedia Meta-Wiki Search Ombuds commission Language Watch Edit Other languages: Bahasa Indonesia Cymraeg Deutsch Deutsch (Sie-Form) English Esperanto Lëtzebuergesch Nederlands Ripoarisch Scots Sunda Tiếng Việt Türkçe Zazaki asturianu català dansk español français hrvatski italiano lietuvių magyar occitan polski português português do Brasil română suomi svenska čeština български русский українська հայերեն עברית العربية سنڌي فارسی پښتو नेपाली বাংলা ગુજરાતી தமிழ் తెలుగు മലയാളം ไทย 中文日本語粵語 한국어 For legal and security reasons, the Wikimedia Foundation has decided to require two-factor authentication for this role. Ombuds Commission Wikimedia Ombuds logo.svg About the commission Discuss the ombuds Send a complaint Email the commission Activity reports 2013 2014 2015 2016 2017 2018 2019 2020 2021 The ombuds commission, on behalf of the Board of Trustees, investigates complaints about infringements of the Privacy Policy, the Access to nonpublic personal data policy, the CheckUser policy and the Oversight policy, on any Wikimedia project. They also investigate for the Board the compliance of local CheckUser or Oversight policies or guidelines with the global CheckUser and Oversight policies. Tasks In addition to official investigation, they will mediate between the complainant and the respondent (usually a CheckUser, oversighter, Bureaucrat, Administrator, or arbitration committee member). When legally necessary, the ombuds will assist the General Counsel, the Executive Director or the board in handling the case. When the case is litigious, the ombuds will be in charge of educating CheckUsers or others about the Foundation's privacy policy. When the Privacy Policy, Access to Nonpublic Information Policy, CheckUser Policy, or Oversight policy have been breached, the ombuds commission should report to the Executive Director or designated staff and recommend a course of action (such as removal of access to tools). Additionally, the commission might suggest suitable changes to policies or software. Neutrality An ombuds' investigation should be conducted in a manner determined by the ombuds to ensure fairness and impartiality. As a general guideline, it is best that ombuds avoid conflicts of interest as much as possible, particularly by avoiding routine use of CheckUser or oversight access and not processing complaints on the projects on which they are very active editors. However, matters that come before the commission are not clear-cut, and the language and culture of various projects may pose barriers to outsiders. As such, how the commission investigates complaints is left to the discretion of its appointed members. Membership Members of the ombuds commission are selected from the Wikimedia community by Wikimedia Foundation officials. A call for volunteers is issued each year in early December on the Wikimedia-L mailing list and on the talk page of this policy, as well as other project forums as appropriate. They are appointed (assuming they agree) for a period of approximately one year. A non-voting alternate member may be appointed to serve for one year, with an expectation for a seat as a full member the following year. Assigned rights Ombuds have the following rights globally, among others: Search deleted pages (browsearchive) Check users' IP addresses and other information (checkuser) View the checkuser log (checkuser-log) View deleted history entries, without their associated text (deletedhistory) View deleted text and changes between deleted revisions (deletedtext) View private logs (suppressionlog) View revisions hidden from any user (viewsuppressed) Current members User Home wiki(s) Language spoken IRC nick Ameisenigel (CA) dewiki, wikidatawiki de, en-4, nds-2, fr-1, tlh-1 Ameisenigel Érico (CA) ptwiki pt - Faendalimas (CA) wikispecies en, pt-3, it-2, fr-1 faendalimas Galahad (CA) eswikivoyage es, en-1 Galahad Infinite0694 (CA) jawiki ja, en-3, de-3, fr-2, it-1 - JJMC89 (CA) enwiki en JJMC89 Mykola7 (CA) ukwiki uk, ru-4, en-2, de-1 - Olugold (CA) enwiki, wikidatawiki, igwiki ig, en-5, Ha-4 Olugold Udehb (CA) wikidatawiki ig, en-5 - Zabe (CA) wikidatawiki, mediawikiwiki de, en-3, la-1 zabe See also automatically generated list (terms expire February 2023). For the prior membership, see here. Submission Complaints may be made to the ombuds commission through the following ways (preferably in a language spoken by one of the members): To use the form, access this link: Special:Contact/ombudscommission To write an email, access this link: Special:EmailUser/Ombuds commission Both ways will send message directly to OC mailing list. Please follow these guidelines when submitting an inquiry to the commission: Be concise. Lengthy emails with unnecessary information make it harder for the commission to process the case in a timely manner. Be objective. Avoid making inquiries based on speculations or subjective judgements. Provide evidence. Please provide us with diff links and/or permanent links when possible. Be specific. Specify what part of which policy has been violated. Please inform us if your wiki has an Arbitration Committee (or a similar committee) and if you have reached them (or used other dispute resolution procedure customary to your community) before reaching the ombuds commission. Provide a link to the relevant case page if appropriate. Processing/Reporting Cases brought to our attention will be processed the following way: Confirmation of the request: we will send a notice of confirmation to the requester, and if necessary ask for further information. Scope: if the request is within the scope of the ombuds commission, we will do the investigation, if not we will decline the request and try to direct the complainant to a better place to get help for his/her individual problem. Investigation: We do whatever is necessary to find out whether or not there was a breach of the policies or a non-compliance or conflict of local policies with the global ones. Result: We give the result of our investigation to the requester, and if there was indeed a breach of the privacy policy, we will inform the user who was investigated and if necessary inform the Board of Trustees and if necessary recommend removing OS, CU or steward rights from the user breaking the policy. Activity reports Activities: in 2013: February–June, July–December. in 2014: January–June, July–December. in 2015: January–June, July–December. in 2016: January–June, July–December. in 2017: January–June, July–December. in 2018: January–June, July–December. in 2019: January–June, July–September, October–December. 2020 Commission: January-March, April-January 2021. 2021 Commission: February-April, May-July, August-October, November-January 2022. 2022 Commission: February-April. See also Board resolutions: Ombudsperson Checkuser (July 2006) — Wikimedia Committees (minutes of presentation on Ombudsman Commission; January 2009) — Amending the Scope of the Ombudsman Commission (November 2015) Requests for comment: Scope of Ombudsman Commission (May—December 2013) Announcement Ombudsman commission wider scope (January 2016) New commission announcements: 2007 — 2009 — 2011 — 2012 — 2013 — 2014 — 2015 — 2016 — 2017 — 2018 —2019 — 2020 —2021 — 2022 Information on the ombuds global user group: Ombuds: global permission · global groups (toolforge) · member list · group changelog Special global permissions 2021 workflow updates Last edited 1 month ago by Ameisenigel Wikimedia Meta-Wiki Content is available under CC BY-SA 3.0 unless otherwise noted By Ai.A13(key)msg Privacy policy Terms of Use Desktop

1 year, 10 months

Matahariagung7@gmail.com

by Tomy Anggara

Language Watch Edit Other languages: Bahasa Indonesia Deutsch English Lëtzebuergesch Nederlands Tiếng Việt Türkçe dansk español français hrvatski italiano magyar polski português português do Brasil sicilianu suomi čeština Ελληνικά русский українська العربية روچ کپتین بلوچی فارسی پښتو नेपाली বাংলা മലയാളം ไทย 中文日本語 한국어 Users who are given the ipblock-exempt flag ('ipblock-exempt' user group) are not affected by autoblocks, blocks of IP addresses and rangeblocks (both global and local). They are also exempt from proxy blocks and Tor blocks. This right is automatically assigned to administrators, however the flag must be added separately for non-administrators to enable editing from IP addresses affected by IP or IP range blocks. The ipblock-exempt flag cannot be granted to editors who do not use an account. There is also a global group to override IP blocks globally. See Global block exemptions for more information. Historically, administrators would "softblock" IP's allowing named editors to continue to edit, while disallowing any anonymous editing and user registrations. With this flag, this is no longer required. How to get this flag Edit To get this flag and become IP block exempt on a specific project one must ask an administrator of that project. The information on who should or should not get this userright can be found on the no open proxies page. However every project may have its own IP block exemption policy. For specific information about IP block exemption on Meta, see Meta:IP block exemption To get a global exemption from global blocks one must make a request to stewards at Steward requests/Global permissions. Note: that an exemption granted by a steward will only circumvent a global block placed by stewards. An global exemption will not circumvent a local block placed at a wiki by a local administrator. Blocks at wikis (local blocks and local exemptions) override global actions for that wiki. Interactions of local and global block exemptions Edit Blocks and exemptions work differently depending on where they are imposed, and by whom they are imposed. Local blocks Edit A local block only works at the one wiki. Local blocks are applied by local administrators. A local block exemption only overrides the block at the one wiki, and it exempts all blocks placed. Global blocks Edit A global block works on all centralised wikis, with the exception of metawiki (this wiki) Global blocks are typically only placed by stewards. Global IP block exemptions override global blocks only, it has no impact on local blocks. Local administrators can override (whitelist) for their wiki a steward's global block through that wiki's Special:GlobalBlockWhitelist page Comparison of local/global blocks and local/global exemptions. Block imposed by Local administrator (local block) Steward (global block) Type of exemption Local IP block exemption unblocked unblocked Global IP block exemption blocked unblocked No exemption blocked blocked See also Edit Blocked user Global IP block exemption Policy on Meta

1 year, 10 months

Production Excellence #44: May 2022

by Krinkle

How’d we do in our strive for operational excellence last month? Read on to find out! Incidents By golly, we've had quite the month! 10 documented incidents, which is more than three times the two-year median of 3. The last time we experienced ten or more incidents in one month, was June 2019 when we had eleven (Incident graphs <https://codepen.io/Krinkle/full/wbYMZK>, Excellence monthly of June 2019 <https://phabricator.wikimedia.org/phame/post/view/163/production_excellence…>). I'd like to draw your attention to something positive. As you read the below, take note of incidents that did *not* impact public services, and did *not* have lasting impact or data loss. For example, the Apache incident <https://wikitech.wikimedia.org/wiki/Incidents/2022-05-24_Failed_Apache_rest…> benefited from PyBal's automatic health-based depooling. The deployment server incident <https://wikitech.wikimedia.org/wiki/Incidents/2022-05-02_deployment> recovered without loss thanks to Bacula. The Etcd incident <https://wikitech.wikimedia.org/wiki/Incidents/2022-05-01_etcd> impact was limited by serving stale data. And, the Hadoop incident <https://wikitech.wikimedia.org/wiki/Incidents/2022-05-31_Analytics_Data_Lak…> recovered by resuming from Kafka right where it left off. 2022-05-01 etcd <https://wikitech.wikimedia.org/wiki/Incidents/2022-05-01_etcd> Impact: For 2 hours, Conftool could not sync Etcd data between our core data centers. Puppet and some other internal services were unavailable or out of sync. The issue was isolated, with no impact on public services. 2022-05-02 deployment server <https://wikitech.wikimedia.org/wiki/Incidents/2022-05-02_deployment> Impact: For 4 hours, we could not update or deploy MediaWiki and other services, due to corruption on the active deployment server. No impact on public services. 2022-05-05 site outage <https://wikitech.wikimedia.org/wiki/Incidents/2022-05-05_Wikimedia_full_sit…> Impact: For 20 minutes, all wikis were unreachable for logged-in users and non-cached pages. This was due to a GlobalBlocks schema change causing significant slowdown in a frequent database query. 2022-05-09 Codfw confctl <https://wikitech.wikimedia.org/wiki/Incidents/2022-05-09_confctl> Impact: For 5 minutes, all web traffic routed to Codfw received error responses. This affected central USA and South America (local time after midnight). The cause was human error and lack of CLI parameter validation. 2022-05-09 exim-bdat-errors <https://wikitech.wikimedia.org/wiki/Incidents/2022-05-09_exim-bdat-errors> Impact: During five days, about 14,000 incoming emails from Gmail users to wikimedia.org were rejected and returned to sender. 2022-05-21 varnish cache busting <https://wikitech.wikimedia.org/wiki/Incidents/2022-05-21_varnish_cache_bust…> Impact: For 2 minutes, all wikis and services behind our CDN were unavailable to all users. 2022-05-24 failed Apache restart <https://wikitech.wikimedia.org/wiki/Incidents/2022-05-24_Failed_Apache_rest…> Impact: For 35 minutes, numerous internal services that use Apache on the backend were down. This included Kibana (logstash) and Matomo (piwik). For 20 of those minutes, there was also reduced MediaWiki server capacity, but no measurable end-user impact for wiki traffic. 2022-05-25 de.wikipedia.org <https://wikitech.wikimedia.org/wiki/Incidents/2022-05-25_de.wikipedia.org> Impact: For 6 minutes, a portion of logged-in users and non-cached pages experienced a slower response or an error. This was due to increased load on one of the databases. 2022-05-26 m1 database hardware <https://wikitech.wikimedia.org/wiki/Incidents/2022-05-26_Database_hardware_…> Impact: For 12 minutes, internal services hosted on the m1 database (e.g. Etherpad) were unavailable or at reduced capacity. 2022-05-31 Analytics Hadoop failure <https://wikitech.wikimedia.org/wiki/Incidents/2022-05-31_Analytics_Data_Lak…> Impact: For 1 hour, all HDFS writes and reads were failing. After recovery, ingestion from Kafka resumed and caught up. No data loss or other lasting impact on the Data Lake. Incident follow-up Recently completed incident follow-up: Invalid confctl selector should either error out or select nothing <https://phabricator.wikimedia.org/T308100> Filed by Amir (@Ladsgroup <https://phabricator.wikimedia.org/p/Ladsgroup/>) after the confctl incident this past month. Giuseppe (@Joe <https://phabricator.wikimedia.org/p/Joe/>) implemented CLI parameter validation to prevent human error from causing a similar outage in the future. Backup opensearch dashboards data <https://phabricator.wikimedia.org/T237224> Filed back in 2019 by Filippo (@fgiunchedi <https://phabricator.wikimedia.org/p/fgiunchedi/>). The OpenSearch homepage dashboard (at logstash.wikimedia.org) was accidentally deleted last month. Bryan (@bd808 <https://phabricator.wikimedia.org/p/bd808/>) tracked down its content and re-created it. Cole (@colewhite <https://phabricator.wikimedia.org/p/colewhite/>) and Jaime (@jcrespo <https://phabricator.wikimedia.org/p/jcrespo/>) worked out a strategy and set up automated backups going forward. Remember to review and schedule Incident Follow-up work <https://phabricator.wikimedia.org/project/view/4758/> in Phabricator! These are preventive measures and tech debt mitigations written down after an incident is concluded. Read more about past incidents at Incident status on Wikitech. 💡*Did you know?*: The form on the *Incident status <https://wikitech.wikimedia.org/wiki/Incident_status>* page now includes a date, to more easily create backdated reports. Trends In May we discovered 28 new production errors <https://phabricator.wikimedia.org/maniphest/query/z7vLwJdXtLu2/#R>, of which 20 remain unresolved and have come with us to June. Last month the workboard totalled 292 tasks still open from prior months. Since the last edition, we completed 11 tasks from previous months, gained 11 additional errors from May (some of May was counted in last month), and have 7 fresh errors in the current month of June. As of today, the workboard houses 299 open production error tasks (spreadsheet and graph <https://docs.google.com/spreadsheets/d/e/2PACX-1vTrUCAI10hIroYDU-i5_8s7pony…>, phab report <https://phabricator.wikimedia.org/project/reports/1055/>). Take a look at the workboard and look for tasks that could use your help. → https://phabricator.wikimedia.org/tag/wikimedia-production-error/ Thanks! Thank you to everyone who helped by reporting, investigating, or resolving problems in Wikimedia production. Thanks! Until next time, – Timo Tijhof 🔗 Share or read later via https://phabricator.wikimedia.org/phame/post/view/285/

1 year, 10 months

Phabricator maintenance tomorrow 15:00 UTC (08:00 PDT)

by Tyler Cipriani

Phabricator (phabricator.wikimedia.org) will be down tomorrow sometime during the 15:00–17:00 UTC[0] maintenance window[1]. We're deploying updates during that time, and we'll stop Phabricator briefly to run database migrations. I'm sorry if the timing of the upgrade window is inconvenient for anyone. But having more folks around at the time of the upgrade mitigates some of the risks, too. Thank you! Tyler Cipriani (he/him) Engineering Manager, Release Engineering Wikimedia Foundation [0]: <https://zonestamp.toolforge.org/1655305257> [1]: <https://wikitech.wikimedia.org/wiki/Deployments#deploycal-item-20220615T1500>

1 year, 10 months

Developer Portal is launched! Discover Wikimedia’s technical areas and how to contribute

by Birgit Müller

Hi All, We are happy to announce the launch of the Wikimedia Developer Portal <https://developer.wikimedia.org/> - a centralized entry point for finding technical documentation and community resources across Wikimedia’s key technical areas. The Developer Portal project <https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal> is part of a broader initiative to improve the discoverability and overall quality of key technical documentation. Work on this project began in July 2020 and included research and feedback rounds <https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal/History>, designing a content strategy <https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal/Content_…> and user journeys <https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal?tableofc…> to help people navigate and achieve their tasks, technical implementation <https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal/Implemen…> of the portal, developing a documentation review process <https://www.mediawiki.org/wiki/Documentation/Review_template>, and updating key documents. Wikimedia’s technical documentation spans a wide range of technologies, is distributed (and often duplicated) across mediawiki <https://www.mediawiki.org/wiki/MediaWiki>, wikitech <https://wikitech.wikimedia.org>, code repositories or other places, might or might not be up-to-date, and serves multiple audiences. This complex landscape can make it hard to find the information you need. The goal of the Developer Portal is to make it easier for developers and other technical contributors to: - Find the key documentation they need for common developer tasks. - Discover available tools and technologies. - Learn how to get started in Wikimedia technical areas. At its core, the Developer Portal is a navigation tool. It is an index of categorized links to key sources of technical information. These sources are hosted primarily on wikis—the portal itself contains no actual documentation. A major part of this project includes reviewing and updating the documents linked from the Developer Portal - the actual documentation (examples: Localisation <https://www.mediawiki.org/wiki/Localisation>, Communication <https://www.mediawiki.org/wiki/Communication>, Cloud Services introduction <https://wikitech.wikimedia.org/wiki/Help:Cloud_Services_introduction>). This work will continue over the next year while also investigating how to improve and scale the process. The Developer Portal is a project by the Developer Advocacy team within the Technical Engagement group at the Wikimedia Foundation and has been developed by a project team of technical writers, engineers, and developer advocates (Alex <https://meta.wikimedia.org/wiki/User:APaskulin_(WMF)>, Andre <https://meta.wikimedia.org/wiki/User:AKlapper_(WMF)>, Bryan <https://meta.wikimedia.org/wiki/User:BDavis_(WMF)>, Sarah R <https://meta.wikimedia.org/wiki/User:SRodlund_(WMF)>, Tricia <https://meta.wikimedia.org/wiki/User:TBurmeister_(WMF)>). The long term goal is to step-by-step move towards a future where Wikimedia’s technical documentation is discoverable, accurate, standardized, and continuously updated. Yes, this is big :-) — and yes, it will take a while. Hope you join us in realizing this collective effort of making it easier for people to contribute to the code and technical spaces. Thank you <3 This project would not have been possible without the support, knowledge, ideas and feedback of many! A huge thanks to: - the members of WMF and WMDE engineering teams who participated in exploratory interviews early in the process, - everyone who provided feedback at Hackathon 2021 & 2022, via private messages, on the Project page <https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal/Content_…> or gave input or help on Phabricator tasks <https://phabricator.wikimedia.org/project/board/4941/query/all/> - Developers and community members who participated in multiple rounds of user testing <https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal/History#…> - the Design Strategy team <https://design.wikimedia.org/strategy/index.html> at the Foundation for helping us with designing a research study and recruiting a diverse group of users to test the final version of the site - people who helped with key doc improvements and content reviews: Haley <https://meta.wikimedia.org/wiki/User:HLepp_(WMF)>, Kamil <https://meta.wikimedia.org/wiki/User:KBach-WMF>, Komla <https://meta.wikimedia.org/wiki/User:SSapaty_(WMF)>, Nick <https://meta.wikimedia.org/wiki/User:Quiddity_(WMF)>, Srishti <https://meta.wikimedia.org/wiki/User:SSethi_(WMF)> - translators and translatewiki.net community, especially Abijeet <https://meta.wikimedia.org/wiki/User:APatro_(WMF)>, Niklas <https://meta.wikimedia.org/wiki/User:Nlaxstrom-WMF>, and Verdy_p <https://translatewiki.net/wiki/User:Verdy_p> - People who helped us with steps towards production and deployment: Alexandros <https://meta.wikimedia.org/wiki/User:AKosiaris_(WMF)>, Andrew <https://meta.wikimedia.org/wiki/User:AndrewBogott_(WMF)>, Brian <https://meta.wikimedia.org/wiki/User:BKing_(WMF)>, Ryan <https://meta.wikimedia.org/wiki/User:RKemper_(WMF)>, Valentin <https://meta.wikimedia.org/wiki/User:VGuti%C3%A9rrez_(WMF)> We hope that this new resource will be fun to explore and ultimately be useful for your work. If you are interested in learning more about the thinking behind the user journey design for the Developer Portal, please see the blog post on Diff <https://diff.wikimedia.org/2022/06/15/illuminating-pathways-to-technical-do…>. For more information about the technical implementation and design principles, please see the corresponding post on the techblog <https://techblog.wikimedia.org/2022/06/15/new-discovery-tool-for-technical-…>. All key information is also available on the project page <https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal> of the Developer Portal. Feedback, ideas and questions are more than welcome on the talk page of the project <https://www.mediawiki.org/wiki/Talk:Developer_Advocacy/Developer_Portal>. Let's keep discussions in one place. :-) Birgit & the Developer Portal project team -- Birgit Müller (she/her) Director of Technical Engagement Wikimedia Foundation <https://wikimediafoundation.org/>

1 year, 10 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l June 2022