Respected Sir/Madam,
I am Ayan Gupta, an open web developer ( javascript,python, CSS ,
angular.js) and I wish to contribute to the projects of your organization
Can you please suggest to me some open source projects to which I will
start contributing from now?
That would be great if you send some GitHub repo links to those projects so
that I can start off.
https://www.linkedin.com/in/ayan-gupta-924833201
Per T316078 <https://phabricator.wikimedia.org/T316078>, quibble tests
(PHPUnit, Selenium, etc.) now need to pass on PHP 8.1 for automatic
merges of changes in Gerrit.
Thanks to everyone who helped to make that happen.
PHP 8.1 support is a focus of the Wikimedia Performance Team. We want
to unblock the WMF production migration to PHP 8.1, which will be led
by Service Operations. Hopefully Service Operations will be able to
migrate WMF production to PHP 8.1 in the first half of next year.
PHP 8.1 will bring performance improvements which we would like our
users to benefit from. And bringing production closer to the upstream
master branch allows us to more effectively participate in PHP's
community-driven development process.
For the benefit of developers and third party users, I think we should
try to support the latest stable release of PHP. So now is a good time
to start thinking about PHP 8.2 support. General availability of PHP
8.2 is expected on around November 24, according to the PHP wiki
<https://wiki.php.net/todo/php82>. There is a migration guide
<https://www.php.net/manual/en/migration82.php>.
-- Tim Starling
Hi,
Over two years ago[1] I worked on redesigning the Codesearch UI to make
it easier to browse and filter. It didn't go anywhere for various
reasons[2], but in June Krinkle picked it up again and I've now deployed
his rewrite[3], please try it out:
https://codesearch-beta.wmcloud.org/
You can insert "-beta" into the URL of any normal codesearch result and
it should just work.
Here's an overview of the changes:
* Switching backends keeps the search query
* Sidebar for easy skipping of many results from one repo
* Implement fuzzysort and typeahead autocompletion for the
repo selector dropdown
* Generate a report in the format of a Phabricator checklist
* Add search query to the document title (browser tab)
* Implement a pulsating "placeholder" state
* Optimise fetching of "repos" config data by caching this server-side
* Fix advanced options being hidden by adblockers
And there's more, you can read Krinkle's commit message[3] for the full
list and links to tasks.
Please report bugs you find in the Codesearch Phabricator project[4] (or
submit a patch!). If all goes well I'd like to switch over the main
domain to the new interface near the end of the year.
[1]
https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/…
[2] lack of time and basing on top of experimental technology
[3] https://gerrit.wikimedia.org/r/c/labs/codesearch/+/804785/
[4] https://phabricator.wikimedia.org/project/view/3158/
Thanks,
-- Kunal / Legoktm
Hello everyone,
The last & final feedback session on the "Small wiki toolkits" (SWT)
workshop series is coming up - it will take place on Friday, October 28th,
at 16:00 UTC. You can find more details on the workshop and a link to join
here: <
https://meta.wikimedia.org/wiki/Small_wiki_toolkits/Workshops#Upcoming:_Fin…>
[1].
This workshop will gather feedback on the SWT workshop series around bots
and scripts development, ongoing since January 2022. There will be a
discussion around the following:
- Overall feedback on the workshop series
- Technical topics you would like to see the SWT team focus on by
running workshops or developing resources in 2023
- Your preferred learning formats
This session does not require attendance in previous workshops to
participate. We look forward to your participation!
Best,
Srishti
On behalf of the SWT Workshops Organization team
[1]
https://meta.wikimedia.org/wiki/Small_wiki_toolkits/Workshops#Upcoming:_Fin…
*Srishti Sethi*
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
Hello all!
The Search Platform Team usually holds an open meeting on the first
Wednesday of each month. Come talk to us about anything related to
Wikimedia search, Wikidata Query Service (WDQS), Wikimedia Commons Query
Service (WCQS), etc.!
Feel free to add your items to the Etherpad Agenda for the next meeting.
Details for our next meeting:
Date: Wednesday, November 2nd, 2022
Time: 15:00-16:00 UTC / 08:00 PDT / 11:00 EDT / 16:00 CEST / 19:00 GST
Etherpad: https://etherpad.wikimedia.org/p/Search_Platform_Office_Hours
Google Meet link: https://meet.google.com/vgj-bbeb-uyi
Join by phone: https://tel.meet/vgj-bbeb-uyi?pin=8118110806927
Have fun and see you soon!
Guillaume
--
*Guillaume Lederrey* (he/him)
Engineering Manager
Wikimedia Foundation <https://wikimediafoundation.org/>
Hello everyone,
In September, I submitted a proposal to the Technical Decision Making
Process called "Modern interfaces for all users" [1]. This proposal was
somewhat abstract, but it was about different ways we could render user
interfaces on the server, given that our server-side code is written in
PHP, but most UI code is written in JavaScript (including Codex[2], the new
library of shared UI components being developed by the Design Systems Team).
One solution that many people have been asking for for some time is Vue's
server-side rendering (SSR) feature[3]. Supporting Vue SSR in MediaWiki
will require in-depth architecture discussions, and I think that will
eventually be part of this TDMP too. However, there are also other
approaches for rendering UI components on the server which may be more
appropriate, depending on the situation. So before we delve into
architecture and implementation for Vue SSR, we should first discuss which
methods of rendering UIs on the server we want to use in which situations,
both to confirm that we really do need Vue SSR, and to inform the
architecture discussion.
To that end, I've started a discussion on a Phabricator task where I list
different server rendering methods and make a simple (probably too simple)
proposal for when to use which. If you're interested in this topic, please
go to https://phabricator.wikimedia.org/T322163 and participate in the
discussion there.
Roan Kattouw
Lead engineer on the Design Systems Team at the Wikimedia Foundation
[1] https://phabricator.wikimedia.org/T317270
[2] https://www.mediawiki.org/wiki/Codex
[3] https://vuejs.org/guide/scaling-up/ssr.html