Dear all,
this afternoon I was reading about the coming Flow extension. That's really great work. And I can't wait to work with it.
And there are so many other interesting projects: Visual Editor, Parsoid, Athena skin, Echo, Lua, Wiki Data and so on.
Despite of that MediaWiki you can see at Google Trends, that MediaWiki is still loosing attention. And in my opinion people just don't know, that MediaWiki is catching up. And they don't know, that it needs help.
But this is important for all of us, that developers see, that MediaWiki is no longer a software of the "zero" years.
So I suggest to publish more blog articles and social media posts about this new developments and if somebody has something nice to read, to discuss or to share gives a hint, so that the others can spread the news in their community.
Best regards,
Richard
Dr. Richard Heigl
Strategieberatung
Hallo Welt! - Medienwerkstatt GmbH
__________________________________
Residenzstraße 2
93047 Regensburg
Tel. +49 (0) 941 - 66 0 80-193
Fax +49 (0) 941 - 66 0 80-189
www.hallowelt.biz
heigl(a)hallowelt.biz
Sitz: Regensburg
Amtsgericht: Regensburg
Handelsregister: HRB 10467
E.USt.Nr.: DE 253050833
Geschäftsführer: Anja Ebersbach, Markus Glaser, Dr. Richard Heigl, Radovan Kubani
This is RC4 for 1.21.0 due to be released on May 15, 2013. The
patches included since RC3 are after the download instructions.
While testing this release candidate, I discovered a bug in the
installer (Bug #47489) which I would like to get fixed before a final
release.
I've changed the list of bugs I would like to see fixed in the next
couple of weeks before release to 3 installer-only bugs:
https://bugzilla.wikimedia.org/buglist.cgi?bug_id=47489%2C46802%2C43817https://bugzilla.wikimedia.org/43817
Include short descriptions for extensions bundled in the release
https://bugzilla.wikimedia.org/46802
Enabling extensions during install process displays empty readonly
textbox on status page
https://bugzilla.wikimedia.org/47489
white screen after no db selection
I'll take a stab at these, but I appreciate any help you guys can give.
Full release notes:
https://www.mediawiki.org/wiki/Release_notes/1.21
**********************************************************************
Download:
http://download.wikimedia.org/mediawiki/1.21/mediawiki-core-1.21.0rc4.tar.gzhttp://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc4.tar.gz
Patch to previous version (1.20.0), without interface text:
http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc4.patch.gz
Interface text changes:
http://download.wikimedia.org/mediawiki/1.21/mediawiki-i18n-1.21.0rc4.patch…
GPG signatures:
http://download.wikimedia.org/mediawiki/1.21/mediawiki-core-1.21.0rc4.tar.g…http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc4.tar.gz.sighttp://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc4.patch.gz.s…http://download.wikimedia.org/mediawiki/1.21/mediawiki-i18n-1.21.0rc4.patch…
Public keys:
https://secure.wikimedia.org/keys.html
Patches included since RC3:
commit 29d3243339f836ad13a722762e4b0f7056ee3764
Author: Brad Jorsch <bjorsch(a)wikimedia.org>
Date: Sun Mar 3 22:35:05 2013 -0500
Add parser method to call parser functions
There is currently no straightforward way for anything to call a
parser function and get the result. This abstracts out that portion
of braceSubstitution() to allow this.
The immediate motivation for this patch is to close bug 41769
against Scribunto, see I0138836654b0e34c5c23daaedcdf5d4f9d1c7ab2.
Bug: 41769
Change-Id: I339b882010dedd714e7965e25ad650ed8b8cd48f
commit c81f3673423021c92a8e08a207236b4d48b0bc46
Author: Timo Tijhof <ttijhof(a)wikimedia.org>
Date: Tue Mar 26 18:59:07 2013 +0100
mw.loader: Guard against odd setTimeout behaviour in old Firefox
Bug: 46575
Change-Id: I80af730daa815f0c273fe942c570d1f0144bbbb1
commit d43c43727c0273ab9a861b39a70609bfbe14a801
Author: PleaseStand <pleasestand(a)live.com>
Date: Wed Apr 17 13:49:50 2013 +0000
Revert "Remove link to Special:ActiveUsers from Special:Statistics"
Special:ActiveUsers still seems to be in REL1_21, and
there is a pending change set (Ib43b4205) to add back
the special page on the master branch.
This reverts commit 4b2c7373f2ab6f701cbd7f371ad4b95829e34e70
Change-Id: I5669477091ada36ea28c33de1232d2b7e9d0b413
commit c6528bb73b99de3ae6a5f3d8493e9dc8a1eb9120
Author: csteipp <csteipp(a)wikimedia.org>
Date: Mon Apr 15 13:42:02 2013 -0700
Sanitize $limitReport before outputting
Prevents possible injection of "-->" and other HTML by extensions
using the ParserLimitReport hook.
bug: 46084
Change-Id: Id97b6668da6df3e5e4c0acefffa00c82cac3c44a
(cherry picked from commit 69f96f65dd99e54b84e489e7d957b7526653474c)
commit 73f30041f2cf4f5cac08bb3b37a38fa80832bec3
Author: csteipp <csteipp(a)wikimedia.org>
Date: Mon Apr 15 13:44:23 2013 -0700
Disable external entities in XMLReader
Temporarily disable loading entities in XMLReader when calling
read() with libxml_disable_entity_loader(true).
bug: 46859
Change-Id: I0b2ef270f15c7b4da17edee680bf7e2410919915
(cherry picked from commit 1ed76385c31f44c589f6e5a99c9c56f1f3f76728)
commit 9c902fb78536566c3deb85cc1bfb033074520e22
Author: csteipp <csteipp(a)wikimedia.org>
Date: Mon Apr 15 13:47:10 2013 -0700
Disable external entities in Import
Temporarily disable loading entities in XMLReader when calling
read() during import.
(cherry picked from commit 77a8d576918b6a47b80a67a3653662a2d705d6c3)
bug: 47251
Change-Id: I0b39386e6cf4ec0244aab8ebc4095922511e2964
Hi!
Have you seen wikiapiary project? [1] Personally I'm fascinated by the
statistics of the extensions, and skins. For example here is the stats for
Semantic MediaWiki:
http://wikiapiary.com/wiki/Extension:Semantic%20MediaWiki
You can see the website where the extension is installed and the version
information.
Wikiapiary is quite new and I think is open to ideas. For example I think
it would be nice to allow people to judge the extensions by several
criteria. Maybe also add some code statistics will also be useful.
Please post your ideas here.
[1] http://wikiapiary.com
-----
Yury Katkov, WikiVote
Hi everyone!
Is there a way to configure email notifications and emails so that the
users of the wiki receive emails in html format? Or in text format
without wiki-markup. I haven't found any extension that can do that.
Cheers,
-----
Yury Katkov, WikiVote
Hi,
There is a Request for proposals / Statement of work for vendors
interested in being involved in the development of this project:
http://www.mediawiki.org/wiki/Requests_for_comment/Wikitech_contributors
We are still discussing the proposal in the community, but in any case
we need a better idea of the resources and budget needed. If you have
any questions please contact me.
By the way, the proposal might be interesting for other wikis with a
community of contributors. Your feedback in the wiki page e.g. based on
your own projects or your needs is welcome as well.
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
On 3 April 2013 07:41, <glaser(a)hallowelt.biz> wrote:
>
> Hi Johan,
>
>
>
> over the last five years, I developed an WYSIWYG editor based on TinyMCE
> which is part of BlueSpice [1]. You can try it in our demo [2] (User:
> Testuser, Pass: hallowelt). I’d say it’s pretty stable, we have a base of
> several thousand users in enterprise contexts. BlueSpice including the
> editor is GPLed and you’ll find a download link here: [3].
>
>
>
> Maybe this one could be a basis for your instance? If you find something
> that needs to be improved, me and my team will be ready to do so in a short
> time frame. In any case, I’d be curious about what you think of BlueSpice J
> and the editor.
>
>
>
> Best,
>
> Markus
>
>
>
> [1] http://www.mediawiki.org/wiki/Extension:BlueSpice
>
> [2] http://demo.blue-spice.org/index.php/Hauptseite
>
> [3] http://www.blue-spice.org/
>
Hi Markus,
Thanks a million, this seems like *exactly* the right thing - I don't see
how I've managed to miss it before...
We are evaluating right now.
Thanks and Best Regards,
Johan
---
Johan Ramm-Ericson
Hi,
As I've googled around a bit on the subject of a Rich Editor for MediaWiki,
I can see that there has been some discussion on this subject already. Just
let me quickly fill you in on my approach:
I work as a Linux sys admin and have been administrating a fairly large
MediaWiki server on the company Intranet for a while now. Recently there
has been *a lot* of internal discussion abut the availability of a Rich
Editor as the WYSIWYG extension became incompatible after upgrading from
MediaWiki 1.17.x to 1.19.x. Also, despite my adamant suggestions WikiEditor
gets little or no internal approval. By the way; no need to dive into a
discussion about why we upgraded despite knowing that the WYSIWYG extension
would not work.
I'm now trying to get internal support for putting up money to pay a
skillful programmer to finish whatever needs to be done to get a Rich
Editor out into a stable state for a given MediaWiki release. So here are
my questions to you:
* What is the state of Rich Editor extensions for MediaWiki - is Visual
Editor the main contender or are there other more suitable choices?
* How far from a stable release is each respective Rich Editor?
* What needs to be done to get it / them into a stable state? How many
hours would a programmer with relevant skills need to get it / them there?
* What are the relevant skills a programmer would need?
* Any recommendation for programmers that could do the job in a relatively
short time frame?
Hope I'm asking this in the right forum, if I'm not I'd appreciate if you
could point me in the right direction.
Thanks and Best Regards,
Johan
---
Johan Ramm-Ericson
Hi guys!
How do you deal with recent changes, notifications and history in
MediaWiki? Maybe anyone knows or develops the extensions that make those
things more flexible?
For example we've tried to simplify the recent changes page leaving only
the very nessesary things there and hiding the changes made by our
moderators and admins: http://i.imgur.com/oN1QYCI.png
We've also experimented with Semantic Watchlist extension: if you have
Semantic MediaWiki installed it allows you to see what property values have
been modified.
The last feature is the visual diff tool: I can say that sometimes it's
very helpful but when we're talking about formatting differences the
traditional two-side diff in better.
-----
Yury Katkov, WikiVote
On 03/31/2013 10:58 PM, Dmitrii Kouznetsov wrote:
> Should I install git ?
No, this is a complete, downloadable version.
> Should I install PHP ?
Yes, MediaWiki requires at least version 5.3.2 of PHP.
> Should I install MathJax ?
> Should I install C++?
> Suould I install Latex?
None of these is needed.
> What versions of the software above are required for and compatible with
> your version of wiki?
Note that this is a release candidate for MediaWiki 1.21.0 -- it is not
"my" version of the software as I've done nothing special with this. I
am the release manager for MediaWiki and this is a release candidate for
a normal release.
This may not be absolutely clear since I used my own server for the
release instead of download.wikimedia.org. I had the release ready and
didn't want to wait for someone to upload it to download.wm.o, so I put
it on my own server. The next release candidate will be on download.wm.o.
> Does your version of wiki support pictures in PDF and/or EPS format?
MediaWiki supports uploading PDF and EPS files with the right
configuration. I haven't tried uploading EPS files, but providing
thumbnails of these and the PDFs should work.
--
http://hexmode.com/
[We are] immortal ... because [we have] a soul, a spirit capable of
compassion and sacrifice and endurance.
-- William Faulker, Nobel Prize acceptance speech
