-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
I've written an RfC to introduce a standardized and recommended way
for re-distributors and packagers of MediaWiki to be able to tune
DefaultSettings.php as appropriate.
You can read more details on-wiki[1], and discuss it on Phabricator[2].
[1]
https://www.mediawiki.org/wiki/Requests_for_comment/PlatformSettings.php
[2] https://phabricator.wikimedia.org/T182020
Thanks!
- -- Legoktm
-----BEGIN PGP SIGNATURE-----
iQJLBAEBCgA1FiEE+h6fmkHn9DUCyl1jUvyOe+23/KIFAlolpwQXHGxlZ29rdG1A
bWVtYmVyLmZzZi5vcmcACgkQUvyOe+23/KL43RAAld/PQ+KcmBks4lkaChAVK21o
7yTCBogPHQpLF73a4pNDIRn+XkHoO0jRmVkoGRIEsE4wTpvyFxxJo1cTbD2QAIKl
K0WKGBPQ8Lyyu4nFodiPwrvSGhhSi0iVvxMQPLq8K/FPF6bO8c331VAcLoJDQjyY
rfuQMnAnvBZ7kOzQPiXYgMkSpWgzFF1hn32h7HXyNuanK5KxjeRKl3ZTjmJj2iIk
zGoUhekJxipeIxgTb6ZT0H3YVMQdXyHuq4fvQFpOsX+KWgKspWOe4u7wbKTfCIN6
OCtRbIypHlSG4AgeQ1Bqcq3cPyvt2YuBaEaKn1ZMgByWKy65jcWt+x0KsVSe3aYm
jxzQI7gXBOIVvQeYHTezz91RSkL6bikI0wdBqg7Lsdr4Mb62CDQcfMmFSI1Iz8dD
ooz7Kcc7VTfU75VokJKNCPnVqdhux7dBgw5EhxBFGFIYfwUu6j8MayIxaZT8uyKj
OLCYOn8hslFEFeiOnSoMGtsS/6m6RR2YiTLC9r/+lGN2T/UeHm9RuCaBviZEaiQl
S9X9CAZlkaRg74zNyPO2e/E2v68F1shbpZDutzylal9QJfA0cEhBKbfQTEPlQwgN
qNxS7ajbb2G96HvF2Tyj8ai4YGENltmhp9M3/NzuJW6jj0fee+KNiNM7sRfMm7p4
nW7bXwXYkK4m4SuWxDM=
=PL+x
-----END PGP SIGNATURE-----
Hi,
Over the past few months, I've been working with LFaraone, Faidon, and
Moritz on updating the super old 1.19.x Debian package of MediaWiki to
use a more modern version (currently 1.25.x) and just generally improve
the quality of it. (Yes, it uses MySQL by default, not postgres!)
It's currently waiting in the "new" queue[1], but if you'd like to test
it out, I've uploaded the debs at [2]. If you find any bugs or have
feature requests, you can let me know or file a request in the
MediaWiki-Debian[3] Phabricator project. The debian/ files used to
create the package can be found in Gerrit in the mediawiki/debian
repository[4].
[1] https://ftp-master.debian.org/new.html
[2] https://people.wikimedia.org/~legoktm/debian/
[3] https://phabricator.wikimedia.org/tag/mediawiki-debian/
[4]
https://gerrit.wikimedia.org/r/#/projects/mediawiki/debian,dashboards/defau…
-- Legoktm
Hello!
The Wikimedia Developer Summit
<https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit> is the annual
meeting to push the evolution of MediaWiki and other technologies
supporting the Wikimedia movement. The next edition will be held in San
Francisco on January 9-11, 2017.
We welcome all Wikimedia technical contributors, third party developers,
and users of MediaWiki and the Wikimedia APIs. We specifically want to
increase the participation of volunteer developers and other contributors
dealing with extensions, apps, tools, bots, gadgets, and templates.
Important deadlines:
- Monday, October 24: This is the last day to request travel
sponsorship. Applying takes less than five minutes.
- Monday, October 31: This is the last day to propose an activity. Bring
the topics you care about!
Subscribe to weekly updates: https://www.mediawiki.org/
wiki/Topic:Td5wfd70vptn8eu4
Please feel free to forward this email to anyone who might be interested in
attending!
Thanks,
Srishti
--
Srishti Sethi
ssethi(a)wikimedia.org
Hi,
I am working on creating a Debian package (.deb file) for MediaWiki (MW)
1.25.1, for full details about my efforts to date see Ask Ubuntu
<http://askubuntu.com/q/629473/93125>. See the latest version of MW
that's available as a Debian package for Ubuntu at least is 1.19 which
is fairly out of date (so out of date it's no longer even supported), so
I felt I would update it. Keeping in mind, however, I am no expert
programmer or web developer, my understanding of programming and web
applications is that of a novice. I even had trouble getting MW to work
on Ubuntu without resorting to using the Bitnami stack. After I get MW
1.25.1 as a Debian package working I plan on developing MW 1.23 (as it's
the latest LTS release).
The biggest problem for me is that most guides (in fact all of them I've
come across, at least) for developing Debian packages are written for
packages that need to be built (usually using the `make` utility),
unlike MW which just needs to be set up and configured on an Apache server.
If it is relevant I am running on 32 bit Ubuntu 15.04, hence my package
needs to be built and able to work on this OS and platform.
Thanks for your time,
Brenton
The following RfC may be of interest to subscribers on this list,
comments appreciated!
Thanks,
-- Legoktm
-------- Forwarded Message --------
Subject: [RfC] Improving extension dependency management and versioning
Date: Sun, 25 Jan 2015 16:04:30 -0800
From: Legoktm <legoktm.wikipedia(a)gmail.com>
To: wikitech-l(a)lists.wikimedia.org
Hi!
I've written up an RfC[1] discussing the pain points for managing
extensions and suggestions on how to improve it.
Comments and feedback appreciated!
[1]
https://www.mediawiki.org/wiki/Requests_for_comment/Improving_extension_man…
-- Legoktm
Hi,
In MediaWiki 1.25 we've changed the way we manage external dependencies
on PHP libraries. In the past the libraries would just be copied into
our git repo, but we're now using composer[1] to manage these dependencies.
We plan[2] on including these dependencies inside the tarball, they'll
all be located inside the "vendor" directory.
Currently the following dependencies have been added:
* leafo/lessphp[3]: a less compiler (formerly bundled inside MediaWiki)
* psr/log[4]: Common interfaces for logging
* cssjanus/cssjanus[5]: Flips CSS for RTL languages (formerly bundled
inside MediaWiki)
* wikimedia/cdb[6]: Provides CDB fallback in pure PHP (formerly part of
MediaWiki)
* oojs/oojs-ui[7]: Library of widgets, layouts, and windows
1.25 is still in development, so it's possible that the list of
dependencies will change over the next few months. The current set of
dependencies can be found in our composer.json file[8] and on-wiki[9].
MediaWiki expects that there will be an autoloader at
"vendor/autoload.php" which will load these libraries.
Please let me know if you have any questions, or if we can do anything
to help out making packaging easier.
Thanks,
-- Legoktm
[1] https://getcomposer.org/
[2] https://phabricator.wikimedia.org/T74726
[3] http://leafo.net/lessphp/
[4] http://www.php-fig.org/psr/psr-3/
[5] https://github.com/cssjanus/php-cssjanus
[6] https://www.mediawiki.org/wiki/CDB
[7] https://www.mediawiki.org/wiki/OOjs_UI
[8] https://github.com/wikimedia/mediawiki/blob/master/composer.json
[9] https://www.mediawiki.org/wiki/MediaWiki_1.25#External_libraries
Hi everyone,
I can possibly work up to about four person-days within the
next four weeks on this, pending an OK from the project lead
of my current for-customer project on Monday. I’ve asked for
this since nobody else is apparently working on it, and we
use Mediawiki in our inhouse FusionForge installations anyway.
I expect we will have to update:
• src:mediawiki
• all extensions
– src:mediawiki-extensions
– maybe src:mediawiki-math
– maybe php-wikidiff2
• src:fusionforge
From the FusionForge weekly IRC meeting today, I expect to
see FusionForge 5.3 in Debian jessie. Roland and Sylvain,
please do not upload anything to Debian sid which you do
not want to see in jessie, from now, so I can work with
sid to make FusionForge match Mediawiki. (This means to
please not package FusionForge 5.4/6.0 for Debian until
this is finished, and to possibly help me with testing
and hacking the ff-plugin-mw integration.)
I’ll look at src:mediawiki-extensions, although I cannot
test all extensions. I’ll not look at php-wikidiff2.
This means that, once I prepare new packages (starting
in experimental, I think), I will need volunteer testing
and feedback, from admins as well as actual users. We
are on a very tight timeframe, and I wish to have this
all finished within the next 28 days, starting Monday.
Failure to do so will mean shipping Mediawiki 1.19 in
jessie, which is currently upstream’s oldstable and
fading LTS. Mediawiki 1.23 is upstream’s current LTS;
we have an agreement from upstream to support 1.19 for
the lifetime of wheezy, and I guess they’d be willing
to extend the same for 1.23 and jessie, but I’d not
want to ask them to do that for 1.19. The delivery of
the security updates from upstream to Debian (both
stable and unstable) has been good so far, with only
a few minor bumps on the road (releases come out when
I go to bed, roughly, and I do not always have time,
and certain people submit unwanted bugreports about
new versions nobody asked for), and no concerns from
the stable-security team so far, so it’s been productive.
Everyone who’s relying on Mediawiki in Debian should
consider agreeing to help test it and drop me an eMail
(to this my work address) stating so.
If anyone’s got a rough overview of what changed between
1.19 and 1.23 for/from a packager’s PoV, thank you for
pointing it out to me.
Let me reiterate a bit of what I normally test:
Mediawiki not stand-alone, but in a multi-site scenario,
with FusionForge replacing a bit of its theme (we use
Monobook) and about all of its auth mechanisms, and
PostgreSQL as the database, plus most of the extensions
from src:mediawiki-extensions, plus src:mediawiki-math.
I have no experience in setting up a standalone mediawiki
(and do not particularily wish to gain that), and I will
absolutely not touch MySQL, which is what upstream recommends
in lieu of a database. This means I test a very non-default
setup. Our inhouse FusionForge is 5.1-based, but for Debian
I’ll also test with the 5.3 from jessie/sid/experimental.
I’m not formally the maintainer of src:mediawiki (only of
src:mediawiki-extensions, and even then only a comaintainer),
but considering that one of them doesn’t do it either, and
the other’s got a bouncing eMail address, I’m willing to
step forward and do my share of the work.
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
> This means that, once I prepare new packages (starting in
> experimental, I think), I will need volunteer testing and feedback,
> from admins as well as actual users. We are on a very tight timeframe,
> and I wish to have this all finished within the next 28 days, starting
> Monday.
I'm willing to help test if it will help get MW 1.23 into Jessie.
> Failure to do so will mean shipping Mediawiki 1.19 in jessie, which is
> currently upstream’s oldstable and fading LTS. Mediawiki 1.23 is
> upstream’s current LTS; we have an agreement from upstream to support
> 1.19 for the lifetime of wheezy, and I guess they’d be willing to
> extend the same for 1.23 and jessie, but I’d not want to ask them to
> do that for 1.19.
Right. I wouldn't like to be stuck supporting 1.19 in Jessie. I don't
think that is something we can agree to.
> The delivery of the security updates from upstream to Debian (both
> stable and unstable) has been good so far, [...] so it’s been
> productive.
I'm glad to hear this.
> If anyone’s got a rough overview of what changed between
> 1.19 and 1.23 for/from a packager’s PoV, thank you for pointing it out
> to me.
I'll try to put together a list this week.
> I’m not formally the maintainer of src:mediawiki [but] I’m willing to
> step forward and do my share of the work.
Thank you!
--
Mark A. Hershberger
NicheWork LLC
717-271-1084