i.org/wiki/MediaWiki_Stakeholders%27_Group/Fantastic_MediaWikis_CfP#How_to_submit
All the best,
Markus (User:Mglaser)
MediaWiki Stakeholders' Group
-Ursprüngliche Nachricht-
Von: Wikitech-l [mailto:wikitech-l-boun...@lists.wikimedia.org] Im Auftrag von
Markus Glaser
Gesendet: Montag, 20. März
It's so great to see this happen! The formation of the platform team clearly
adds emphasis to the fact that MediaWiki is not only underlying Wikipedia and
its sister projects, but is also widely used by thousands of sites on the
internet and therefore a product of the Foundation in itself.
Hello everyone,
"Fantastic MediaWikis and How to Maintain Them" is a one-day conference track
designed for people who work with the open source software MediaWiki in their
organisation, company or business [1]. The conference track is curated by the
MediaWiki Stakeholders Group and hosted by
This update will definitely improve our experience with git. As others have
said before, the inline editing will greatly speed up the review process and
improve code quality. This is especially true for the extensions, as you now do
not have to clone a repo or reject the commit just to fix a
Hello everyone,
On 19/01/15 06:47, Tim Starling wrote:
As long as there are no actual reasons for dropping pure-PHP core
functionality,
the idea of WMF versus shared hosting is a false dichotomy.
I kind of agree. Instead of seeing things in black and white, aka shared
hosting or not, we
/1.19/mediawiki-1.19.23.tar.gz.sig
https://releases.wikimedia.org/mediawiki/1.19/mediawiki-1.19.23.patch.gz.sig
Markus Glaser
(Wiki Release Team)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo
://www.mediawiki.org/keys/keys.html
Mark Hershberger and Markus Glaser
(Wiki Release Team)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
/mediawiki-1.19.22.tar.gz.sig
https://releases.wikimedia.org/mediawiki/1.19/mediawiki-1.19.22.patch.gz.sig
Mark Hershberger and Markus Glaser
(Wiki Release Team)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman
) or 1.23.7 (legacy and LTS version).
MediaWiki 1.19 LTS will continue to be supported until May, 2015.
Best,
Mark Hershberger and Markus Glaser
(Wiki Release Team)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman
Hello everyone,
next week on October, 29th, there will be another set of security and
maintenance releases for MediaWiki. There are still some unresolved bugs and
changes that are wating to be +2'ed. So if you feel like improving MediaWiki
tarball releases in the upcoming days, you could have
Hi Željko, hi all,
we are still meeting, in roughly 2.5 hours from now. Here's the current link:
https://plus.google.com/events/cf7ajegl3357ukcc946vnm1j9b8
Obviously, there was a battle between two apps on how to best synchronize a
calender, which led to repeated cancellation of that event.
/mediawiki-1.19.20.tar.gz.sig
https://releases.wikimedia.org/mediawiki/1.19/mediawiki-1.19.20.patch.gz.sig
Note:
There is no i18n patch as there are no changes in translation.
Markus Glaser
(Wiki Release Team)
___
Wikitech-l mailing list
Wikitech-l
Hi Greg,
actually, the WikiReleaseTeam/Release process [1] is my attempt to rewrite the
release checklist [2], with more specific information about responsibilites and
timeframes. I will take this opportunity to continue working on this.
[1]
https://releases.wikimedia.org/mediawiki/1.19/mediawiki-1.19.19.tar.gz.sig
https://releases.wikimedia.org/mediawiki/1.19/mediawiki-1.19.19.patch.gz.sig
Note:
There is no i18n patch as there are no changes in translation.
Markus Glaser
(Wiki Release Team
Hi Isarra,
Why is this ahead of schedule? Two months before release
seems pretty reasonable to me;
You don't want to rush this stuff, especially when
balancing with breaking changes in the next release.
It's ahead of the planned release schedule [1] by a few weeks. The real issues
is,
Hi Brian,
on mediawiki-enterprise-l, Derric Atzrott suggested we use the respective
WikiData item for up-to-date MediaWiki version information:
https://www.wikidata.org/wiki/Q83
It's machine readable, could easily be queried and probably converted into
other formats as needed. It is also very
Hello everyone,
next week on September, 24th, there will be another set of security and
maintenance releases for MediaWiki. There are still some unresolved bugs and
changes that are wating to be +2'ed. So if you feel like improving MediaWiki
tarball releases in the upcoming days, you could
Hi Lewis,
yes, there will be at least one security fix. The respective bugs will be made
public with the releases.
Best,
Markus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Are there security fixes due to go in this release?
- -- Lewis Cawte
On 17/09/14 14:56, Markus Glaser wrote:
Hello
Dear Wikitech-l Readers,
spreading open knowledge is not just about content, but also about tools.
That's the reason we provide MediaWiki as an open source product. Fortunately,
MediaWiki is used widely outside the Wikimedia world, so the mission is
fulfilled, right? Well, not quite... Third
Hey Sumana,
this is really sad news. You know, you were one of my very first contacts in
the international MediaWiki world! It's hard for me to imagine this world
without Sumana. The way you draw people into the community is really
exceptional!
I wish you all the best for your future and I
-1.22.10.tar.gz.sig
https://releases.wikimedia.org/mediawiki/1.22/mediawiki-1.22.10.tar.gz.sig
https://releases.wikimedia.org/mediawiki/1.22/mediawiki-1.22.10.patch.gz.sig
Note:
There is no i18n patch as there are no changes in translation.
Markus Glaser
(Wiki Release Team
Hello everyone,
this is a notice that on 27th August between 20:00-22:00 UTC we will release
maintenance updates for current and legacy branches of the MediaWiki software.
Downloads and patches will be available at that time.
Best,
Markus
Wiki Release Team
Hello everyone,
next week on August, 27th, there will be another set of maintenance releases
for MediaWiki. There are still some unresolved bugs and changes that are wating
to be +2'ed. So if you feel like improving MediaWiki tarball releases in the
upcoming days, you could have a look at
, extension dependencies, and packaging, just to name a few.
Our mission, far from being complete, is just beginning. With your help and
involvement we can make an impact to improve MediaWiki for the third party
community.
Best,
Mark Hershberger and Markus Glaser
Wiki Release Team
[1] http
.tar.gz.sig
https://releases.wikimedia.org/mediawiki/1.19/mediawiki-1.19.18.patch.gz.sig
Note:
There is no i18n patch as there are no changes in translation.
Markus Glaser
(Release Management Team)
P.S.: If you are interested in shaping the future of MediaWiki, come join our
session about
Hello everyone,
next week on July, 30th, there will be another set of maintenance releases for
MediaWiki. There are still some unresolved bugs and changes that are wating to
be +2'ed. So if you feel like improving MediaWiki tarball releases in the
upcoming days, you could have a look at these
Hello everyone,
Mark Hershberger and I submitted a proposal for the next year of release
management:
https://www.mediawiki.org/wiki/Release_Management_RFP/2014/Mark_y_Markus_LLC
In the upcoming year, we want to focus on creating a user group as a central
hub for all third party related issues
://www.mediawiki.org/keys/keys.html
Markus Glaser
(Release Team)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
://download.wikimedia.org/mediawiki/1.23/mediawiki-core-1.23.0-rc.3.tar.gz.sig
http://download.wikimedia.org/mediawiki/1.23/mediawiki-1.23.0-rc.3.tar.gz.sig
Public keys:
https://www.mediawiki.org/keys/keys.html
Markus Glaser
(Release Team)
___
Wikitech-l mailing
/1.19/mediawiki-core-1.19.16.tar.gz.sig
http://releases.wikimedia.org/mediawiki/1.19/mediawiki-1.19.16.tar.gz.sig
http://releases.wikimedia.org/mediawiki/1.19/mediawiki-1.19.16.patch.gz.sig
Note:
There is no i18n patch as there are no changes in translation.
Markus Glaser
(Release Team
Hi everyone,
due to a blocking bug in the installer of the latest release candidate, MW
1.23.0-rc.2, we decided to release another RC before the final version as soon
as a patch is available and merged. This also means, the actual release of MW
1.23.0 will be delayed by one week. New release
/mediawiki-1.23.0-rc.2.tar.gz
GPG signatures:
http://download.wikimedia.org/mediawiki/1.23/mediawiki-core-1.23.0-rc.2.tar.gz.sig
http://download.wikimedia.org/mediawiki/1.23/mediawiki-1.23.0-rc.2.tar.gz.sig
Public keys:
https://www.mediawiki.org/keys/keys.html
Markus Glaser
(Release Team
-1.21.9.tar.gz.sig
http://releases.wikimedia.org/mediawiki/1.21/mediawiki-1.21.9.tar.gz.sig
http://releases.wikimedia.org/mediawiki/1.21/mediawiki-1.21.9.patch.gz.sig
Note:
There is no i18n patch as there are no changes in translation.
Markus Glaser
(Release Management Team
/mediawiki/1.23/mediawiki-1.23.0rc0.tar.gz.sig
Public keys:
https://www.mediawiki.org/keys/keys.html
Markus Glaser
(Release Management Team)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hello everyone,
this is to announce the REL1_23 branch for the upcoming MediaWiki 1.23.0
release was created. The release is scheduled for 6 weeks from now, no
later than May 29th.
In order to facilitate this, please make sure anything you want in 1.23
is ready within a week. The first release
.tar.gz.sig
http://releases.wikimedia.org/mediawiki/1.19/mediawiki-1.19.15.tar.gz.sig
http://releases.wikimedia.org/mediawiki/1.19/mediawiki-1.19.15.patch.gz.sig
Notice:
There is no patch file for i18n changes as there are no changes to the
previous version.
Markus Glaser
(Release Management Team
Hello everyone,
Florence asked me to forward this request to the list, which I am happy to do
:)
Markus
Original Message
Subject:Tablet skin design
Date: Mon, 31 Mar 2014 21:25:31 +0200
From: Florence Devouard anthe...@yahoo.com
Newsgroups:
/mediawiki-core-1.19.14.tar.gz.sig
http://releases.wikimedia.org/mediawiki/1.19/mediawiki-1.19.14.tar.gz.sig
http://releases.wikimedia.org/mediawiki/1.19/mediawiki-1.19.14.patch.gz.sig
Markus Glaser
(Release Management Team)
___
Wikitech-l mailing list
Wikitech-l
Hello everyone,
I would like to announce the release of MediaWiki 1.22.3, 1.21.6 and 1.19.12.
These releases fix a number of security related bugs that could affect users
of MediaWiki. In addition, MediaWiki 1.22.3 is a maintenance release. It fixes
several bugs. You can consult the
Hello list,
there is a scheduled maintenance release of MediaWiki on Thursday, 27th of
February. I would like to take the opportunity to point you to the list of
known issues [1]. Maybe we can get a few of those fixed until mid of the week?
Best,
Markus
[1]
We should strongly consider ensuring that the latest stable releases of
Ubuntu and probably RHEL (or maybe fedora) can run MediaWiki.
- Ryan
Kind of agree ;)
I'd like to see the next MediaWiki LTS version (1.23) to support PHP 5.3.
MW1.23LTS has a scheduled release date at end of April (we
Dear all,
I am happy to announce the availability of the first stable release of the new
MediaWiki 1.22 release series.
MediaWiki 1.22 is a large release that contains many new features and
bug fixes. This is a summary of the major changes of interest to users.
You can consult the
on the blog:
http://blog.wikimedia.org/2013/07/26/future-third-party-releases-media
wiki/
Today, the Wikimedia Foundation is pleased to announce that we have
contracted with two long-time members of the MediaWiki community–Mark
Hershberger and Markus Glaser–to manage and drive forward third
Hi Yury,
some time ago you proposed a SMW webinar for developers [1], which I find is a
really great idea! But it seems no date has been set yet. As there are a number
of interested participants, I think we’re ready to take this one step further J
and find a time slot. Shall we use the talk
Hi Moriel,
I like that idea very much. In the use case I have in mind, though, I do have
actual releases. Do you think it's possible for your extension to also consider
tags? I am thinking of something like a tagging convention, e.g. RELEASE
v1.20. ExtensionStatus could then parse the tag and
Hi Yury,
we experimented with MediaWiki as a Facebook-App. Basically this is using MW in
an iFrame and passing through the Facebook authentication. Articles can be
liked and commented via FB. When you edit something, it publishes that to the
user's stream.
Here's a prototype, in German
Thank you Sumana! I know a lot more about searching in gerrit now, which helps
a lot in general :)
Cheers,
Markus
-Ursprüngliche Nachricht-
Von: Sumana Harihareswara [mailto:suma...@wikimedia.org]
Gesendet: Donnerstag, 6. September 2012 19:18
An: Wikimedia developers
Cc: Markus Glaser
Hi all,
I am trying to find a (any) html file in gerrit (trying to find out whether it
is displayed as HTML in a browser, but that is not the issue here…). When I
enter “html” in the search box, it apparently searches commit messages for html
(?). When I try the search syntax as described here
Hi Uwe,
the BlueSpice Extension [1] uses Solr to search MediaWiki.
Cheers,
Markus (mglaser)
[1] http://www.mediawiki.org/wiki/Extension:Blue_spice
-Ursprüngliche Nachricht-
Von: wikitech-l-boun...@lists.wikimedia.org
[mailto:wikitech-l-boun...@lists.wikimedia.org] Im Auftrag von Uwe
Definitely interested! I have just finished some packaging for the Web App
Gallery and would like to see (and add) some more flexibility to the installer.
Also, at SF Hackathon, we had some discussion about the use of MediaWiki by
outside parties, their issues and how to make their lives easier
Also, at SF
Hackathon, we had some discussion about the use of MediaWiki by outside
parties, their issues and how to make their lives easier ;)
What did your discussions conclude?
Actually, it was even earlier...;) Discussion notes can be found at
Some time ago some people from the test framework team started working on a
Selenium Framework for MediaWiki [1], in PHP and with Selenium 1.0. One of the
reasons the project discontinued was that there was no clear case of when
Selenium would be useful as opposed to unit tests, esp. using
+1
mglaser
-Ursprüngliche Nachricht-
Von: wikitech-l-boun...@lists.wikimedia.org
[mailto:wikitech-l-boun...@lists.wikimedia.org] Im Auftrag von Thomas Gries
Gesendet: Donnerstag, 29. März 2012 22:58
An: Wikimedia developers; Nicole Ebber
Betreff: [Wikitech-l] Hackathon Berlin 2012
Thanks, Mark! You were one of my first contacts in the wmdev community and made
me feel very welcome here.
Cheers, Markus
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hi all,
I am trying to profile the JavaScript bit of an extension I maintain. Is there
any recommended method similar to wfProfileIn/Out in MediaWiki? How do you do
profiling on ResourceLoader?
Cheers, Markus
___
Wikitech-l mailing list
:52
An: Wikimedia developers
Betreff: Re: [Wikitech-l] JavaScript profiling
On Tue, Jan 31, 2012 at 8:38 AM, Roan Kattouw roan.katt...@gmail.com wrote:
On Tue, Jan 31, 2012 at 2:18 PM, Markus Glaser gla...@hallowelt.biz wrote:
Hi all,
I am trying to profile the JavaScript bit of an extension I
Hi Robert,
glad to see you around!
Cheers,
Markus
-Ursprüngliche Nachricht-
Von: wikitech-l-boun...@lists.wikimedia.org
[mailto:wikitech-l-boun...@lists.wikimedia.org] Im Auftrag von Sumana
Harihareswara
Gesendet: Mittwoch, 11. Januar 2012 02:26
An: Wikimedia developers
Betreff:
Hi DJ Bauch,
I had some trouble with TortoiseSVN and pageant recently after updating SVN to
1.7 (and the new svn format) on Win7. The solution for me was to update pageant
to a current version (I think it was 0.62). Maybe this helps you as well?
Regards,
Markus
-Ursprüngliche
Alexander Gesinn (planetenxin) now has extensions access.
Hi Alex, nice to see you around!
Markus
(mglaser)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Wed, Nov 2, 2011 at 10:08 PM, Rob Lanphier ro...@wikimedia.org wrote:
Step 1: Deploy VipsScaler extension, but only use it for PNGs over
12.5MP and/or TIFFs (which currently generate errors). Let this sit
in production a while, fixing any bugs we find with this
configuration.
I should
and they will be picked up by the unit
tests if it is desired.
I think working on unit testing code is a lot of fun, so I look forward to
getting this in to core.
- Jeremy
On Mon, Sep 19, 2011 at 3:27 PM, Markus Glaser gla...@hallowelt.biz wrote:
Hi Jeremy,
I am quite interested in your work
to the pixel.
The question is, do we have the need for testing screen layout?
Cheers,
Markus
P.S.: CCing wikitech, since this might be of broader interest.
-Ursprüngliche Nachricht-
Von: Sumana Harihareswara [mailto:suma...@wikimedia.org]
Gesendet: Dienstag, 30. August 2011 14:02
An: Markus
Hi Jeremy,
I am quite interested in your work, since I wrote part of the core Selenium
support [1], which is now on hold. So, how does your code relate to the
SeleniumFramework? What are the main differences? I still think there is a big
chance in Selenium tests for extension programmers:
that searing for
something in Google returns a search result - the results change
constantly, how would you test that? I think it's a cool tool, and we
should consider it when testing, but not go out of our way to use it.
- Trevor
On Mon, Sep 19, 2011 at 7:30 AM, Markus Glaser gla...@hallowelt.biz
.
-- Markus (mglaser)
On Mon, Sep 19, 2011 at 7:30 AM, Markus Glaser gla...@hallowelt.biz wrote:
Hi,
while I don't like the idea of introducing more and more testing
tools, I can still see an interesting use case here: as of now, we
have no way to test whether a given layout (HTML, JS, CSS
would be very interested to hear their thoughts
on that.
Cheers,
Markus (mglaser)
Von: Jack Phoenix [mailto:j...@countervandalism.net]
Gesendet: Mittwoch, 17. August 2011 20:07
An: Wikimedia developers; Sean Colombo; Jack Herrick; reu...@wikihow.com;
joachim.b...@twoonix.com; Markus Glaser
Hello everybody,
that's also the way I see it. Selenium tests do test the application as a
whole. While I agree that a lot of things that are currently tested with
Selenium can be substituted with QUnit or similar, I still think that selenium
tests should be used to check more complex
Hello,
What would be nice for a first take would be if, from translatewiki,
one could click a link that would take one to a list of screens that
show the message in question, with the text highlighted even.
Even if the only thing we had to work from was a display of the English
language
Hi Benedict,
one way to make tests more structured and easier to maintain would be to
provide a standard set of operations within the Selenium Framework. A list of
suggestions can already be found at
http://www.mediawiki.org/wiki/SeleniumFramework#Notes_and_further_improvements.
However, this
Hello,
The right way to do it is to have a test suite: A document that walks
the translator through all the use cases of the feature so that all
possible messages permutations and combinations appear.
Possibly, Selenium tests could be helpful. A Selenium test basically acts as a
remote
Hello everybody,
for the Selenium Framework I have a very specific database related issue which
is hard for me to decide. This is the problem:
In order to have a fresh state for every test, we agreed to have a test
database (and image folder, but this is a sidetrack now) for every test suite
Hi Benedict,
at the moment, the framework is still work in progress, so it is not shipped
with any current releases (afaik). Also, using it requires some changes in the
includes folder as well as the new maintenance class, which is not available
until MW 1.16. But there is hope for you, I know
Hi,
I think it can be removed safely.
Great to hear!
Although in this case I would just run mysqldump with --skip-extended-insert
so that it doesn't create such long lines.
Yes, I tried that. But there are tables like l10ncache or objectcache that
store serialized objects which produce long
Although in this case I would just run mysqldump with
--skip-extended-insert so that it doesn't create such long lines.
Yes, I tried that. But there are tables like l10ncache or objectcache that
store serialized objects which produce long lines even in that case. Still,
I think that should
Hi all,
concerning the selenium part of the tests, I suggest to treat functional tests
and regression tests differently:
* The framework and test runner should remain in maintenance/tests, since it
provides a testing infrastructure for MW
* We are working on a MediaWiki smoke test which makes
the ressources for that id
I would be very happy about comments and thoughts. Are we heading in the right
direction?
Cheers,
Markus
-Ursprüngliche Nachricht-
Von: wikitech-l-boun...@lists.wikimedia.org
[mailto:wikitech-l-boun...@lists.wikimedia.org] Im Auftrag von Markus Glaser
Hi,
since the wiki under test is not neccessarily the wiki running the test, it
might be useful to visualize that (I have numbered the individual steps to make
reference to them easier in the discussion):
testrunner wiki under test
--
Hi,
here are my thoughts about phpunit and selenium testing.
The wiki under test is set up with a master database consisting of a single
objectcache table.
The entries of this table specify a test run identifier as primary key
and temporary resource identifiers as dependent fields.
If I
the tests in
extensions/EXTENSION/tests/selenium
Regards,
Markus
Markus Glaser
Social Web Technologien
Leiter Softwareentwicklung
Hallo Welt! - Medienwerkstatt GmbH
__
Untere Bachgasse 15
93047 Regensburg
Tel. +49 (0) 941 - 56 95 94 92
Fax. +49 (0) 941 - 50 27 58 13
to fill the settings from
globals (as is) or ini files (as Mark propses). Those who use the framework,
however, would not have to rewrite their code.
Regards,
Markus
Markus Glaser
Social Web Technologien
Leiter Softwareentwicklung
Hallo Welt! - Medienwerkstatt GmbH
Hello everybody,
in order to further develop the selenium framework [1], I need to make a few
design decisions, especially on coding conventions, which I'd like to discuss
on this list, since they affect the way of how extension- and core developers
write their tests.
1) Where are the tests
-l] Selenium testing framework
On Sun, 02 May 2010 02:20:06 +0200, Markus Glaser wrote:
Hi everybody,
at the Wkimedia Developers' Workshop, I introduced a Selenium testing
framework for MediaWiki. Since it has now been promoted to
maintenance/tests, I have provided some initial
Hi Dan,
I had these error messages once when I used Firefox 3.6 for testing. Until
recently, Selenium did not support this browser. Apparently now they do, but I
did not have a chance to test this yet. So the solution for me was to point
Selenium to a Firefox 3.5.
Cheers,
Markus
Hi Dan,
the test fails at checking the prerequisites. It tries to load the image page
and looks for a specific div element which is not present if the image was not
uploaded correctly (id=filetoc). This might have changed across the versions of
MediaWiki.
Did you install the PagedTiffHandler
comments and ideas for further improvement. Also, if you intend to use the
framework for your tests, please let me know. I will be happy to assist.
Regards,
Markus Glaser
__
Social Web Technologien
Leiter Softwareentwicklung
Hallo Welt! - Medienwerkstatt GmbH
85 matches
Mail list logo