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…
Hello,
The current logo of MediaWiki was adapted slightly more than fifteen years
ago and hasn’t changed since. This logo despite having the nice concept of
sunflower, is old. The sunflower represents the diversity, the constant
growth and also the wildness.
Among its biggest issues I can point out that it’s a bitmap picture so it’s
unusable in large sizes (like large posters) and it’s too realistic making
it unusable in small sizes.
Most, virtually all, software products use a simpler and more abstract
form. For example, docker, kubernetes, Ubuntu, VueJs, React, Apache Kafka,
and many more. It’s a good time for MediaWiki to follow suit.
My request is for changing the logo of MediaWiki and I have no plans or
interest in changing logo of any other project.
Please show your support, oppose or your comments in the discussion page.
You can also add more suggestions.
The discussion page:
https://www.mediawiki.org/wiki/Project:Proposal_for_changing_logo_of_mediaw…
Best
--
Amir (he/him)
On March 30, we announced that we were temporarily pushing back the release
of MediaWiki 1.35 due to uncertainty resulting from the COVID-19 pandemic.
We are now ready to begin the process of moving forward with the release.
The first step is cutting the release branch, REL1_35, which will occur on
Monday, July 13.
We will then be in "pencils down" mode: developers will stop targeting
MediaWiki 1.35 for new features. Instead, any new features would continue
to be applied to master and would target MediaWiki 1.36 or later. The only
work that would continue towards MediaWIki 1.35 would be blockers -
critical bug fixes or features close to completion that need to make it
into the release. This would happen by merging those patches into master
and then backporting them to the REL1_35 branch.
We anticipate that MediaWiki 1.35 will be released at the beginning of
August.
We appreciate your patience in these difficult times. Wishing you safety
and health,
Cindy
Hi everyone,
I'm pleased to announce a new extension: Page Exchange (PX). This extension
serves as a sort of "package manager" (like yum or apt, if you've heard of
those), but where the "packages" are collections of wiki pages and files
(such as images). Packages are defined in JSON files, so that anyone can
publish a package by just creating a file in the relevant JSON syntax and
putting it online (plus putting online the wikitext and files that it
includes). Then, any wiki that has PX installed can download such a package
by just adding the URL for that package file to LocalSettings.php.
Once downloaded, a package can then be updated (if there have been changes
to the remote package definition), or deleted.
There's another interesting feature of Page Exchange, which is that, if you
install a package containing file(s) named "MediaWiki:XXX.js" or
"MediaWiki:XXX.css" (assuming you have the necessary permissions to do so),
any such file will get automatically loaded on every page view for that
wiki - which means that a package can add its own JavaScript and CSS
functionality to the wiki.
Page Exchange can have a variety of uses, from providing a pre-generated
data structure for wikis to use, to allowing for easy copying of text and
images from one wiki to another - to even enabling lightweight alternatives
to extensions, or even skins.
You can read more about the extension, and download it here:
https://www.mediawiki.org/wiki/Extension:Page_Exchange
-Yaron
--
WikiWorks · MediaWiki Consulting · http://wikiworks.com
Greetings-
With the security/maintenance release of MediaWiki 1.31.8/1.33.4/1.34.2
[0], we would also like to provide this supplementary announcement of
MediaWiki extensions and skins with now-public Phabricator tasks, security
patches and backports [1]:
== CentralAuth ==
+ (T250594, CVE-2020-12051) - globaluserinfo api allows access to
information about hidden users
<
https://gerrit.wikimedia.org/r/#/q/I3c80641dc1202df7428714f0ca44717a51ff6021
>
The Wikimedia Security Team recommends updating these extensions and/or
skins to the current master branch or relevant, supported release branch
[2] as soon as possible. Some of the referenced Phabricator tasks above
_may_ still be private. Unfortunately, when security issues are reported,
sometimes sensitive information is exposed and since Phabricator is
historical, we cannot make these tasks public without exposing this
sensitive information. If you have any additional questions or concerns
regarding this update, please feel free to contact security(a)wikimedia.org
or file a security task within Phabricator [3].
[0]
https://lists.wikimedia.org/pipermail/mediawiki-announce/2020-June/000252.h…
[1] https://phabricator.wikimedia.org/T248542
[2] https://www.mediawiki.org/wiki/Version_lifecycle
[3] https://www.mediawiki.org/wiki/Reporting_security_bugs
--
Scott Bassett
sbassett(a)wikimedia.org
Hi Everyone,
I upgraded to Mediawiki 1.34.2 on a CentOS 7 x86_64 server.
The composer update produced some noise:
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/phpunit-mock-objects is abandoned, you should avoid
using it. No replacement was suggested.
The server information is located at
https://www.cryptopp.com/wiki/Special:Version.
Jeff
As per the MediaWiki version lifecycle [1], I would like to announce the
formal end of life (EOL) of MediaWiki 1.33 as of next week, Tuesday June
30, 2020.
This means that MediaWiki 1.33 will no longer receive maintenance or
security backports (barring an unforseen issues with the 1.33.4 release
today). It is therefore strongly discouraged that you continue to use it.
It is recommended to upgrade to MediaWiki 1.34 (due to become EOL in
November 2020). The current Long Term Support (LTS) version of MediaWiki,
MediaWiki 1.31, is however older (and downgrading is not supported. The
delayed next LTS (MediaWiki 1.35) is currently due to be released in early
August 2020, and will be supported until at least June 2023.
MediaWiki 1.34 bumps the required PHP version from 7.0 in 1.33 (which is
unsupported upstream), to PHP 7.2.9 or later.
Thanks!
Sam Reed
[1] https://www.mediawiki.org/wiki/Version_lifecycle
Hi everyone,
There's a new episode out of the MediaWiki podcast "Between the Brackets":
this one is an interview with Tom O'Neill, who runs the U.S. Department of
Energy's internal wiki, Powerpedia. He also runs "MediaWiki in Government",
the informal group/mailing list for MediaWiki users and enthusiasts within
the U.S. government. You can listen to the episode here:
https://betweenthebrackets.libsyn.com/episode-63-tom-oneill
-Yaron
--
WikiWorks · MediaWiki Consulting · http://wikiworks.com
[To all Wikimedia projects, minus mailing lists with an active
discussion already.]
On August 2020, the Wikimedia Foundation board of trustees may decide a
rename to "Wikipedia Foundation" and various other things.
<https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Board_noticeboard/Boar…>
Following a community meeting, a proposed open letter was written:
<https://meta.wikimedia.org/wiki/Community_open_letter_on_renaming>
«We ask the Wikimedia Foundation to pause or stop its current movement
renaming activities, due to persistent shortcomings in the current
rebranding process. Future work should be restarted only in a way that
ensures equitable decision-making.»
(Sorry for the crossposting. When replying, be mindful of cc. Do
consider forwarding to language-specific discussion venues with a short
translated introduction, or translate the pages on Meta.)
Cheers,
Federico aka Nemo