Lis ton message de Nganguem Victor avant qu'il ne soit effacé!
Pour lire ton message, suis simplement ce lien:
http://eu1.badoo.com/chatnoirxx/in/p4hxwt052ok/?lang_id=6
D'autres personnes sont aussi présentes:
Oded (Tel Aviv, Israël)
Priya (Udaipur, Inde)
RajaYogi BK (Udaipur, Inde)
Karuna (Udaipur, Inde)
Chika Reginald Onyia (Pnompen', Cambodge)
...Qui d'autre?
http://eu1.badoo.com/chatnoirxx/in/p4hxwt052ok/?lang_id=6
Les liens ne fonctionnent pas dans ce message? Copie les dans la barre d'adresse de ton navigateur.
Tu as reçu cet email suite à un message envoyé par Nganguem Victor de notre système. S'il s'agit d'une erreur, ignore simplement cet email. La requête sera alors effacée du système.
Amuse-toi bien !
L'équipe Badoo
Courrier automatique de Badoo suite à l'envoi d'un message à ton attention sur Badoo. Les réponses ne sont ni stockées, ni traitées. Si tu ne veux plus recevoir de message de Badoo, fais-le nous savoir:
http://eu1.badoo.com/impersonation.phtml?lang_id=6&mail_code=65&email=media…
Hi Everyone,
During a Mediawiki 1.34.3 to Mediawiki 1.34.4 upgrade... When updating
vendor components using 'php -d extension=phar.so composer.phar
update':
Package wikimedia/password-blacklist is abandoned, you should avoid
using it. Use wikimedia/common-passwords instead.
Package jakub-onderka/php-parallel-lint is abandoned, you should avoid
using it. Use php-parallel-lint/php-parallel-lint instead.
Package jakub-onderka/php-console-color is abandoned, you should avoid
using it. Use php-parallel-lint/php-console-color instead.
Package jakub-onderka/php-console-highlighter is abandoned, you should
avoid using it. Use php-parallel-lint/php-console-highlighter instead.
Package phpunit/php-token-stream is abandoned, you should avoid using
it. No replacement was suggested.
Package phpunit/phpunit-mock-objects is abandoned, you should avoid
using it. No replacement was suggested.
I don't add things to vendor/, and I did not install packages like
password-blacklist or php-parallel-lint. It looks like these are part
of a Mediawiki installation.
/var/www/html/wiki# find . -name password-blacklist
./vendor/wikimedia/password-blacklist
/var/www/html/wiki# find . -name php-parallel-lint
./vendor/jakub-onderka/php-parallel-lint
Jeff
Hello,
The committee has finished selecting new members and the new committee
candidates are (In alphabetical order):
- Amir Sarabadani
- Kunal Mehta
- Martin Urbanec
- MusikAnimal
- Tony Thomas
And auxiliary members will be (Also in alphabetical order):
- Ariel Glenn
- Effie Mouzeli
- Huji
- Jayprakash12345
- Nuria Ruiz
You can read more about the members in the mediawiki.org page
<https://www.mediawiki.org/wiki/Code_of_Conduct/Committee/Members/Candidates>
.
The changes compared to last term are:
- Kunal Mehta is joining the main CoC committee
- Ariel Glenn is coming back to auxiliary committee
- Effie Mouzeli is joining auxiliary committee for the first time
- Tonina Zhelyazkova is leaving the committee
- Matanya and Tpt are leaving the auxiliary committee
- I won't run for the chair this year.
This is not the final structure. According to the CoC
<https://www.mediawiki.org/wiki/Code_of_Conduct/Committee#Selection_of_new_m…>,
the current committee publishes the new members and calls for public
feedback for *six weeks* and after that, the current committee might apply
changes to the structure based on public feedback.
Please let the committee know if you have any concern regarding the members
and its structure until *26 May 2021* and after that, the new committee
will be in effect and will serve for a year.
Amir, On behalf of the Code of Conduct committee
Best
Hello all,
As the 2021 WMF Board elections have been announced, I have proposed to
reconsider the eligibility criteria for “developers” and technical
contributors, as the previous criteria do not make sense any longer and
exclude several groups of contributors.
A discussion has been started at https://phabricator.wikimedia.org/T281977
and
https://meta.wikimedia.org/wiki/Talk:Wikimedia_Foundation_elections/2021#Re…
.
Please share your thoughts and feedback.
Regards
Jay Prakash (he/him)
Volunteer Developer, Wikimedia
Hi Everyone,
We recently updated to Mediawiki 1.36. I'm testing some of our
installed skins under it.
Use of Minerva Neue is causing this warning to be printed on the top
of each page. I can't tell if it is a Minerva Neue issue, HitCounter
issue, or HookContainer issue.
Deprecated: Use of SkinTemplateOutputPageBeforeExec hook (used in
HitCounters\Hooks::onSkinTemplateOutputPageBeforeExec) was deprecated
in MediaWiki 1.35. [Called from
MediaWiki\HookContainer\HookContainer::run in
/var/www/html/w/includes/HookContainer/HookContainer.php at line 137]
in /var/www/html/w/includes/debug/MWDebug.php on line 376
I have no idea why we are running debug code on a production server.
That looks like a separate issue. I'll have to check what I have
mis-configured.
Our mediawiki information can be found at
https://www.cryptopp.com/wiki/Special:Version.
Just an FYI for any devs on the list:
I just upgraded my 1.35.2 MW to 1.36.0 via a tarball release and received
several "premature access" deprecation warnings from PHP in the process.
No fatal errors were thrown, so the upgrade completed successfully. Still,
this might be something to look into.
OS Fedora 34
Apache 2.4.46
PHP 7.4.19 (fpm-fcgi)
MariaDB 10.5.10
The following warnings we thrown at the start of running "php update.php":
PHP Deprecated: Premature access to service container [Called from
Maintenance::finalSetup in
/var/www/gpf/mediawiki-1.36.0/maintenance/includes/Maintenance.php at line
1221] in /var/www/gpf/mediawiki-1.36.0/includes/debug/MWDebug.php on line
376
PHP Deprecated: Premature access to service 'HookContainer' [Called from
MediaWiki\MediaWikiServices::getInstance in
/var/www/gpf/mediawiki-1.36.0/includes/MediaWikiServices.php at line 252]
in /var/www/gpf/mediawiki-1.36.0/includes/debug/MWDebug.php on line 376
PHP Deprecated: Premature access to service 'ObjectFactory' [Called from
Wikimedia\Services\ServiceContainer::{closure} in
/var/www/gpf/mediawiki-1.36.0/includes/ServiceWiring.php at line 535] in
/var/www/gpf/mediawiki-1.36.0/includes/debug/MWDebug.php on line 376
Hope this helps...
Jeffrey T. Darlington
General Protection Fault
https://www.gpf-comics.com/
Hello,
If you missed the previous updates, there's the first
<https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/…>and
the second
<https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/…>one.
This is the last one I'm sending but in a good way.
We now finished migrating all 57 core tables to abstract schema. Now tables.sql
is empty for MySQL
<https://gerrit.wikimedia.org/g/mediawiki/core/+/c60ccf4e6d4932dddc2efd72a8a…>.
We will soon remove the tables.sql files and links to them.
We have also cleaned more than hundreds of old schema change files.
<https://phabricator.wikimedia.org/T272199> That enabled us to actually
look for unused sql files and drop tens of unused ones that have not been
used since 2002 <https://gerrit.wikimedia.org/r/c/mediawiki/core/+/668552>,
2004 <https://gerrit.wikimedia.org/r/c/mediawiki/core/+/668761>, or 2005
<https://gerrit.wikimedia.org/r/c/mediawiki/core/+/670176> (and much more)
and they got lost in the sheer number of our sql patch files.
The next update is exciting for me. With abstraction in place, we can now
have a proper tracking of drifts between schema in paper and our production
(This is a follow up from a major incident in 2018). Now we have
https://drift-tracker.toolforge.org/ that keeps track of these drifts. Our
schema has been around for more than twenty years and we have hundreds of
database hosts, making sure everything is using the right database schema
(and stays correct) is impossible manually and we have been finding and
fixing these drifts since 2018, see this comment onwards
<https://phabricator.wikimedia.org/T104459#4314828>.). Of course more work
in improving the tracker is welcome (here's the list
<https://phabricator.wikimedia.org/project/board/5350/>)
If you want to enjoy the benefits of abstract schema [1] in extension(s)
you or your team maintains, Please abstract the schema of your extension.
There's a long list of WMF deployed extensions that are not using abstract
schema <https://phabricator.wikimedia.org/T261912> and some even already
have a patch that only needs reviewing. Once that's done, we can add that
to drift tracking and have a more comprehensive list of potential issues.
If you need help with the abstraction work, just ping me.
This also helped us resolve several long-standing tickets like T104459
<https://phabricator.wikimedia.org/T104459> (5.5 years old), T62962
<https://phabricator.wikimedia.org/T62962> (7 years old), and T42626
<https://phabricator.wikimedia.org/T42626> (soon reaching its ninth
birthday) and will help us to address even more tech debt in future.
There is more to be done, improving the abstract schema *change* system,
finding a home of schema documentation, improving the drift tracker and
making it more automated, so much more. But the biggest chunk of work is
now finally done.
I really would like to thank Ammarpad for great work on abstracting the
tables and handling all sorts of edge cases, James Forrester and Tgr for
their reviews which without them this wouldn't be possible and Sam Reed who
wrote a script to speed up migration
<https://github.com/Ladsgroup/db-analyzor-tools/blob/master/db_abstractor.py>.
This was a team work to its core.
[1] In more details, by abstracting you will have automated checks for
dirfits of the schema of extension(s) you maintain and production. You will
have Postgres support for free. Also, you can have automated documentation
generation, ability to test the schema itself, and have better consistency
of your data types (like one datatype for timestamps).
Until the next adventure.
--
Amir (he/him)
TL;DR:
* The #mediawiki IRC support channel is moving from Freenode to Libera.Chat.
* Register an account on Libera.Chat and join us there!
There has been a lot of activity over the last 2-3 days related to
staffing changes on the Freenode IRC network [0]. The Wikimedia IRC
Group Contacts (GCs) [1] evaluated the situation and decided that
moving the Wikimedia IRC channels from Freenode to the brand new
Libera.Chat IRC network [2] would be the best course of action [3].
So, we are moving!
A new #mediawiki channel has been created on irc.libera.chat for
handling MediaWiki support requests and general discussion. The old
channel on Freenode still exists and will be maintained at least until
we can get all the bots moved, our documentation updated on
mediawiki.org, and we see more folks on the Libera channel than the
Freenode one. We have a bot bridging both channels so messages to the
channel in either IRC network will be seen on the other network.
There is a new subpage on Meta-Wiki [4] for information on how to create
a new account for yourself on Libera.Chat and other related information.
There is also a tracking task [5] that you can look at to see various
activities that the community hopes to take action on to complete the
migration.
One last thing: The #wmhack Freenode channel is bridged to
#wikimedia-hackathon on Libera.Chat. The new channel name will make it
easier for the GCs to help manage spam and other issues that come up
occasionally on IRC. Don't miss the fun of our 2021 virtual hackathon
from Friday, May 21st to Sunday, May 23rd! [6]
[0]: https://www.kline.sh/
[1]: https://meta.wikimedia.org/wiki/IRC/Group_Contacts
[2]: https://libera.chat/
[3]: https://meta.wikimedia.org/w/index.php?diff=21476411
[4]: https://meta.wikimedia.org/wiki/IRC/Migrating_to_Libera_Chat
[5]: https://phabricator.wikimedia.org/T283247
[6]: https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2021
-- Legoktm
Hi all!
At Vikidia, the Children Encyclopedia, we are looking for paid contractors
(and volunteers) to help us improve our Mediawiki farm in different ways.
For those who don't know us yet, at Vikidia, we help children get
encyclopedic articles they can understand. We're numerous contributors all
over the world, like Wikipedia, writing the articles under free licence.
Vikidia association is based in France, and is available in different
languages like Spanish, Italian...
Now, Vikidia is very big (more than 8 million pageviews per month), the
tech architecture is now more and more complex and hard to maintain by
simple volunteers. We are looking for experts for specific tasks. Can you
help?
Here is a call for proposals:
https://fr.vikidia.org/wiki/Vikidia:Tech/Call_for_proposals
Can you please forward this email to anyone/list who may help us?
Thanks!
Plyd, for Vikidia
https://www.vikidia.org