gmane.org.wikimedia.mediawiki.enterprise

Request for proposals: MediaWiki releasemanagement

Greg Grossmeier — 2013-05-21T17:54:01

Hello all,

I'm excited to share that we just opened an RFP for the Release
Management of MediaWiki! More information below.


The announcement blog post: 
https://blog.wikimedia.org/2013/05/21/request-for-proposals-mediawiki-release-management/

The RFP (PDF):
https://upload.wikimedia.org/wikipedia/commons/a/a1/RFP-MediaWikiReleaseManagement.pdf

The central MediaWiki.org wiki page where proposals will be submitted
and reviewed:
https://www.mediawiki.org/wiki/Release_Management_RFP


Let me and/or Rob Lanphier (robla< at >wikimedia.org) know if you have any
questions.

Best,

Greg

MediaWiki 1.21 delayed

Mark A. Hershberger — 2013-05-18T15:24:27

I have to delay the release of MediaWiki 1.21 again because of a
logistics problem.

I am used to hearing logistics in the context of shipping physical
objects -- in the American trucking industry, for example -- so I can't
help but feel a little strange saying "logistics".  I had to go look up
the term and found this definition:

    The detailed coordination of a complex operation involving many
    people, facilities, or supplies.

That is about right.

I apologize for the confusion.

1.21rc5 -- final release candidate beforerelease on May 15

Mark A. Hershberger — 2013-05-13T19:12:36

The final release candidate for MediaWiki 1.21 (rc5) is available for
download.  See the end of this email for details.  There are a number of
bug fixes in this release that were not in rc4.  Please test this
version and report any problems.  Barring any show-stoppers, the final
release will be on May 15 will be the same as this with just a change to
the version number and updated release notes.

Changes since rc4:

* Changes to JS/JSON value encoding were backed out.
* API: Fix parameter validation in setnotificationtimestamp
commit 18eb39ecb5b89518c3d4a6cc79834a2c121477ff
Author: Brad Jorsch <bjorsch< at >wikimedia.org>
Date:   Fri Mar 15 14:03:19 2013 -0400

* (bug 47271) $wgContentHandlerUseDB should be set to false during the
upgrade
* (bug 47489) Installer now automatically selects the next-best database
type if
 the PHP mysql extension is not loaded, preventing fatal errors in some
cases.
* (bug 47202) wikibits: FF2Fixes.css should not be loaded in Firefox 20.
* (bug 46590) 'AbortChangePassword' hook added/documented (find bug)
* (bug 46848) toggleLinkPremade added linksPassthru
* (bug 47950) Fix IndexPager detection of "is first" state
* (bug 47304) added safeXmlEncodings to UploadBase for svg uploads
* (bug 46608) CoreParserFunctions::anchorencode should return a string


* Full release notes:
https://www.mediawiki.org/wiki/Release_notes/1.21


**********************************************************************
Download:
http://download.wikimedia.org/mediawiki/1.21/mediawiki-core-1.21.0rc5.tar.gz
http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc5.tar.gz

Patch to previous version (1.20.0), without interface text:
http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc5.patch.gz
Interface text changes:
http://download.wikimedia.org/mediawiki/1.21/mediawiki-i18n-1.21.0rc5.patch.gz

GPG signatures:
http://download.wikimedia.org/mediawiki/1.21/mediawiki-core-1.21.0rc5.tar.gz.sig
http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc5.tar.gz.sig
http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc5.patch.gz.sig
http://download.wikimedia.org/mediawiki/1.21/mediawiki-i18n-1.21.0rc5.patch.gz.sig

Public keys:
https://secure.wikimedia.org/keys.html


_______________________________________________
Mediawiki-enterprise mailing list
Mediawiki-enterprise< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise

1.21.0rc4 -- another week, another RC

Mark A. Hershberger — 2013-04-22T16:37:09

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%2C43817

https://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.gz
http://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.gz

GPG signatures:
http://download.wikimedia.org/mediawiki/1.21/mediawiki-core-1.21.0rc4.tar.gz.sig
http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc4.tar.gz.sig
http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc4.patch.gz.sig
http://download.wikimedia.org/mediawiki/1.21/mediawiki-i18n-1.21.0rc4.patch.gz.sig

Public keys:
https://secure.wikimedia.org/keys.html

Patches included since RC3:

commit 29d3243339f836ad13a722762e4b0f7056ee3764
Author: Brad Jorsch <bjorsch< at >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< at >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< at >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< at >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< at >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< at >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

_______________________________________________
Mediawiki-enterprise mailing list
Mediawiki-enterprise< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise

Wikiapiary - a useful project for MWdevelopers

Yury Katkov — 2013-04-17T16:36:40

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
_______________________________________________
Mediawiki-enterprise mailing list
Mediawiki-enterprise< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise

1.21.0rc3 -- more bug fixes and testing

Mark A. Hershberger — 2013-04-16T16:32:08

It is time again for a new MediaWiki release candidate. Download links
at the end of this email. Note that I've include a "core-only" tarball
this week as well.

Since last week, the following fixes were included in the tarball:

  * https://gerrit.wikimedia.org/r/58418/
    backport changes in Collation from master
  * https://gerrit.wikimedia.org/r/58462/
    Cleared ResourceLoader blob store after update.php finishes.
  * https://gerrit.wikimedia.org/r/59102/
    PHP Fatal error: Call to a member function isLocal() on non-object
    in Title.php
  * https://gerrit.wikimedia.org/r/59265/
    Combine JavaScript and JSON encoding logic
  * https://gerrit.wikimedia.org/r/59328/
    Fix pretty JSON when strings end with backslashes
  * https://gerrit.wikimedia.org/r/59329/
    FormatJson: microoptimizations for UTF8_OK mode

Fixes in queue:

  * https://gerrit.wikimedia.org/r/59369/
    Disable $wgContentHandlerUseDB during upgrade where fields don't exist.
  * https://gerrit.wikimedia.org/r/59375/
    Sanitize $limitReport before outputting
  * https://gerrit.wikimedia.org/r/59376/
    Disable external entities in XMLReader
  * https://gerrit.wikimedia.org/r/59377/
    Disable external entities in Import

And, finally, if you want to pitch in, it isn't too late. Here is a list
of bugs I'd like to get fixed before the final release:
https://bugzilla.wikimedia.org/buglist.cgi?bug_id=46802,46401,44907,44568,44294,43817
<https://bugzilla.wikimedia.org/buglist.cgi?bug_id=46802,46401,44907,44568,44524,43817>


  * http://bugzilla.wikimedia.org/43817
    Include short descriptions for extensions bundled in the release
  * http://bugzilla.wikimedia.org/44294
    MWException error - Error: invalid magic word 'speciale'
  * http://bugzilla.wikimedia.org/44568
    bin/ulimit5.sh isn't UNIX compliant
  * http://bugzilla.wikimedia.org/44907
    ResourceLoader: Invalid argument supplied for foreach
  * http://bugzilla.wikimedia.org/46401
    [Regression] mw.loader: Code should execute after styles being
    loaded (wait for async cssText buffering)
  * http://bugzilla.wikimedia.org/46802
    Enabling extensions during install process displays empty readonly
    textbox on status page

Full release notes:
https://www.mediawiki.org/wiki/Release_notes/1.21

********************************************************************************************************************
Download:
http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc3.tar.gz <http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc2.tar.gz>
http://download.wikimedia.org/mediawiki/1.21/mediawiki-core-1.21.0rc3.tar.gz

Patch to previous version (1.20.0), without interface text:
http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc3.patch.gz <http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc2.patch.gz>
Interface text changes:
http://download.wikimedia.org/mediawiki/1.21/mediawiki-i18n-1.21.0rc3.patch.gz <http://download.wikimedia.org/mediawiki/1.21/mediawiki-i18n-1.21.0rc2.patch.gz>

GPG signatures:
http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc3.tar.gz.sig <http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc2.tar.gz.sig>
http://download.wikimedia.org/mediawiki/1.21/mediawiki-core-1.21.0rc3.tar.gz.sig <http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc2.tar.gz.sig>
http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc3.patch.gz.sig <http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0rc2.patch.gz.sig>
http://download.wikimedia.org/mediawiki/1.21/mediawiki-i18n-1.21.0rc3.patch.gz.sig <http://download.wikimedia.org/mediawiki/1.21/mediawiki-i18n-1.21.0rc2.patch.gz.sig>

Public keys:
https://secure.wikimedia.org/keys.html


_______________________________________________
Mediawiki-enterprise mailing list
Mediawiki-enterprise< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise

emails in html or in nicely formatted plaintext?

Yury Katkov — 2013-04-14T18:04:54

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

_______________________________________________
Mediawiki-enterprise mailing list
Mediawiki-enterprise< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise

Technical Contributors project - looking fora vendor

Quim Gil — 2013-04-04T05:05:08

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.

better history,recent changes and notification

Yury Katkov — 2013-04-03T06:54:52

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
_______________________________________________
Mediawiki-enterprise mailing list
Mediawiki-enterprise< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise

Rich Editor for MediaWiki {stable} release -status and steps forward

Johan Ramm-Ericson — 2013-04-02T20:31:11

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
_______________________________________________
Mediawiki-enterprise mailing list
Mediawiki-enterprise< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise

MediaWiki 1.21.0rc1 -- Help test 1.21 andupdate the announcement

Mark A. Hershberger — 2013-03-31T23:49:09

I've just finished preparing the first release candidate for MediaWiki
1.21 and I'd like your help testing it before the final release.

Please download the release candidate and test it.  If you find any bugs
please report them on Bugzilla[1] and make sure I am added as a CC so
that we can fix any show-stoppers before the final release.

Finally, if you could also look over
https://www.mediawiki.org/wiki/MediaWiki_1.21, I'll be using an edited
version of that to make the final announcement.  If you spot problems or
areas that could use clarification, your help in improving it would be
appreciated.

[1]
https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWiki&cc=mah< at >everybody.org&version=1.21-git

Full release notes:
https://www.mediawiki.org/wiki/Release_notes/1.21


**********************************************************************
Download:
http://mah.everybody.org/mediawiki/1.21/mediawiki-1.21.0rc1.tar.gz

Patch to previous version (1.20.0), without interface text:
http://mah.everybody.org/mediawiki/1.21/mediawiki-1.21.0rc1.patch.gz
Interface text changes:
http://mah.everybody.org/mediawiki/1.21/mediawiki-i18n-1.21.0rc1.patch.gz

GPG signatures:
http://mah.everybody.org/mediawiki/1.21/mediawiki-1.21.0rc1.tar.gz.sig
http://mah.everybody.org/mediawiki/1.21/mediawiki-1.21.0rc1.patch.gz.sig
http://mah.everybody.org/mediawiki/1.21/mediawiki-i18n-1.21.0rc1.patch.gz.sig

Public keys:
https://secure.wikimedia.org/keys.html

_______________________________________________
Mediawiki-enterprise mailing list
Mediawiki-enterprise< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise

New Developments. Let's talk about it

Richard Heigl — 2013-03-29T16:54:27

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< at >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



_______________________________________________
Mediawiki-enterprise mailing list
Mediawiki-enterprise< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise

Setting up a MediaWiki installation in 1 big step - and livestream for SMWCon

Sumana Harihareswara — 2013-03-22T15:19:39

I'm at SMWCon right now
http://semantic-mediawiki.org/wiki/SMWCon_Spring_2013 and Mike Cariaso
is right now presenting his work on "Automating SMW install and data
loading."
http://semantic-mediawiki.org/wiki/SMWCon_Spring_2013/Automating_SMW_install_and_data_loading
 I bet a lot of the administrators on mediawiki-l and
mediawiki-enterprise would be interested in reusing his work to automate
their MediaWiki installation work.

I think you'll be interested in this and in some other SMWCon
presentations today -- you can watch live at
http://www.ustream.tv/channel/13510010 and read Cariaso's slides at
https://tinyurl.com/smw-nyc2013 (also
https://docs.google.com/presentation/d/1L-DC4VWtjokLvfip2oQ4k7u3lwdBbXI-1WBa85HCV6s/
).

how do you store and modify your platformcode?

Yury Katkov — 2013-03-12T13:33:55

Hi guys!

We have about 30 extensions in our platform and we really try hard not to
modify MediaWiki and the extensions that weren't made by us. Unfortunately
sometimes we have to modify them and even more regretfully we don't send
the patches to vendors immediately.
The result is obvious and sad - the vendors continue to develop their
extensions and at one inevitable moment we have to deal with upgrading and
merging. :-(

We're using git to store all the code and it doesn't allow the nested .git
directories to be presented in the same project.

How do you deal with that? Do you use git submodules, separate repositories
for the patched extensions or some fancy policy and documentation?

-----
Yury Katkov, WikiVote
_______________________________________________
Mediawiki-enterprise mailing list
Mediawiki-enterprise< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise

Submit a talk to Open Source Bridge by Mar23rd, get WMF subsidy

Sumana Harihareswara — 2013-03-11T20:50:47

This year, consider speaking at Open Source Bridge
<http://opensourcebridge.org/> in Portland, Oregon, USA, June 18-21.
OSB is tech talks & hack sessions with hands-on technologists we want,
for Foundation staff recruiting and for volunteer recruiting and
collaboration.  Good talks, clueful people, great food. :-)

If you submit a talk and it gets accepted, you can request subsidy from
Wikimedia Foundation
<https://meta.wikimedia.org/wiki/Participation:Support> for your travel
and hotel.

Call for talks:
<http://opensourcebridge.org/blog/2013/03/were-extending-our-call-for-proposals/>
 They especially encourage inexperienced speakers.

We already have proposals from or featuring Brandon Harris, Andre
Klapper, Trevor & Roan, me, Priyanka Nag, Quim Gil, Alolita Sharma, and
Noopur Raval.

Please forward.

BlueSpice presentation summary ( some very interesting features for the enterprise and not only)

Maria Miteva — 2013-02-27T13:00:52

*Hi everybody,

Richard Heigl and Markus Glaser from Hallo Welt! presented their
MediaWiki-based enterprise distribution
BlueSpice<http://www.blue-spice.org/>yesterday. Around 6-7 people
attended the online meeting, but I believe
some of those who were unable to will be interested in the cool features
Richard and Markus showed us, so I am sharing a summary below. Please read
on :)

BlueSpice was developed over the last 6 years. It is installed on top of
vanilla MediaWiki and offers a bundle of extensions, some MediaWiki-native
and some proprietary to BlueSpice. Customers get assurance of the
compatibility of the bundle with given MediaWiki versions as well as a
roadmap of future releases. The basic BlueSpice distribution comes for
free, while support, training, special packages, etc. are paid for.

Hallo Welt! are planning to move to Git in the next few months and open up
BlueSpice to the MediaWiki community. The code is currently available for
anyone to look at and reuse.  However, If you want to submit a patch, you
have to email them. This will change soon. Also, documentation in English
is limited but they are working on translating all materials/docs/demos in
the next several months.

BlueSpice offers the following features catering to the enterprise user :

WYSIWYG editor

   - might be replaced by VisualEditor soon but was a major advantage of
   BlueSpice so far



   - easy creation of tables
   - easy upload of photos and files
   - interface for insertion of magic words
   - easy insertions of links within the wiki with a drop down menu of
   articles
   - still need to use wikicode a little

Improved search

   - advanced options
   - filter (by namespace, etc.)
   - suggestions as you type
   - search file names


Advanced administration panel

   - user management
      - manage email, rights, passwords
      - connects to LDAP, allows single signon



   - extensions management for BlueSpice extensions
      - list of extensions with status (stable, beta)
      - automatic testing of extensions
      - in the next release it will show you when a newer version of an
      extension exists and what kind of update it is (security, feature)
      - in the future they hope to have a common repository for BlueSpice
      and other MediaWiki extensions with the ability to switch
extensions on/off
      and update from the UI
   - permission manager - assign permissions to users
   - namespace manager -  no need to touch the config files
      - add, edit properties
      - merge namespaces
      - delete namespaces and backup pages in them


PDF export

   - you can organize your contents in a hierarchical navigation menu (like
   a book with chapters and articles) and you can export a chapter as pdf (
   soon openoffice and Word doc as well )
   - you export to predefined templates
   - you get all linked attachments in the pdf as well
   - excellent for creating up-to-date manuals and technical documentation
   with a click

Improved navigation

   - status bar on top of article - last updated, by whom, responsible
   editor
   - every user has a personal navigation bar depending on his preferences


Article feedback

   - you can assign responsible editors for articles
   - article review tool - you can ask certain people to review a draft
   article, define a review period, etc.

Statistics

   - improved statistics with visualization, diagrams, etc.
   - you can look at history of searchers with counts
   - RSS feeds


Skins

   - they offer a few skins but want to improve on that


SMW + BlueSpice?

   - theere are several examples that use both and it works without
   conflicts
   - there are some conflicts in terms of user experience (Semantic Forms
   vs BlueSpice editor) but no conflicts
   - there is no integration between the two yet, even though there is
   potential for that


Release Cycle

   - once or twice a year - releases - patch releases more often
   - trying to follow MW release cycle since download rate went up 3 times
   as they released a version supporting newer MW versions recently


Richard and Markus can correct me or add more detail. For technical
details, ask Markus Glaser.

Mariya
*
_______________________________________________
Mediawiki-enterprise mailing list
Mediawiki-enterprise< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise

DB2 users?

Mark A. Hershberger — 2013-02-25T15:50:24

Support for DB2 is in MediaWiki, but it is pretty much unmaintained.

Is there anyone on this mailing list who is using it for their MediaWiki
installation?

It seems like a good candidate to drop from support.

other wiki to MediaWiki and vice versaconversion. Who has done it?

Maria Miteva — 2013-02-21T16:48:54

Hi ,

No one brought this up as an issues but I was wondering if converting from
another wiki to MediaWiki or the other way around is a problem for people
and new tools to do that would be useful. How often is it needed and how is
it currently done? I see mostly old posts and tools around. From lookng at
http://www.richardcarterconsultancy.com/2011/12/twiki-to-mediawiki-conversion/
and
http://www.mwusers.com/forums/showthread.php?8098-Moving-to-MediaWiki-from-ConfluenceI
infer it's not an easy task.

Also, it doesn't seem (from my humble observation) to be done often. Is
that because its not needed or because of the lack of friendly tools?

Thank you.

Mariya
_______________________________________________
Mediawiki-enterprise mailing list
Mediawiki-enterprise< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise

Presentation of BlueSpice on Feb 26

Maria Miteva — 2013-02-19T11:29:03

Hi everyone,

Richard Heigl and Markus Glaser from Hallo Welt! in Germany will present
their MediaWiki enterprise distribution
BlueSpice<http://www.blue-spice.org/> on
Feb 26 at 6PM UTC.

The meeting will be held via Netviewer. To  participants just follow the
link below and you will be prompted to download a client software for the
session.
*https://get.netviewer.com/meet/join.php?sinr=953388244&sipw=nv64*<https://get.netviewer.com/meet/join.php?sinr=953388244&sipw=nv64>

I will send a reminder before the meeting.

Mariya
_______________________________________________
Mediawiki-enterprise mailing list
Mediawiki-enterprise< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise

(no subject)

Maria Miteva — 2013-02-15T15:40:54

Hi all,

I have moved the "third-party user" lists I have been working on from
http://www.mediawiki.org/wiki/Third-party_MediaWiki_users_discussion/Contacted_by_Mitevam
to
the following more formal and visible locations :

http://www.mediawiki.org/wiki/Professional_development_and_consulting
http://www.mediawiki.org/wiki/Hosting_services
And some additions to http://www.mediawiki.org/wiki/Software_bundles

I linked to them from some locations that seemed appropriate but feel free
to suggest other ones. Also, if you think you should be on any of the lists
or know of anoher developer or company that belongs there, email me or add
them. If you want to edit the information about your or your company, you
are welcome to but keep it within reason, avoiding anything that can be
interpreted as advertisement or spam.

Cheers,

Mariya


<http://www.mediawiki.org/wiki/Third-party_MediaWiki_users_discussion/Contacted_by_Mitevam>
_______________________________________________
Mediawiki-enterprise mailing list
Mediawiki-enterprise< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise

Fwd: BlueSpice Demo? DOODLE

Maria Miteva — 2013-02-12T15:15:15

Hi everyone.

As per the conversation below, I am working on setting up a presentation of
BlueSpice by Richard Heigl from Hallo Welt!, which is a free open-source MW
enterprise distribution. Richard will present soem BlueSpice features and
how people can reuse them.

Please fill out the doodle below BY THE END OF THE WEEK if you are willing
to participate. I have tried to accomodate the widest range of time zones
in the given choices. I will do my best to post a video for those unable to
attend.

http://doodle.com/tvty9fymwk65fdf8

Also, if you are willing to present something you have developed internally
as well, please contact me and I can help with the organization. It would
be great to have as many of these presentation as possible.

Thank you.

Mariya

---------- Forwarded message ----------
From: Richard Heigl <heigl< at >hallowelt.biz>
Date: Fri, Feb 8, 2013 at 8:23 PM
Subject: Re: [Mediawiki-enterprise] BlueSpice Demo?
To: MediaWiki for enterprises <mediawiki-enterprise< at >lists.wikimedia.org>


 Hi Mariya,****

** **

let‘s Doodle J****

** **

Normally it takes about 45 to 60 minutes to give people a good overview.
And maybe half an hour for questions and discussions? Or as long as the
participants want to stay. I don’t mind. ****

** **

In the next three weeks there is plenty of time. Please feel free to
suggest any dates that are convenient for you J****

** **

Richard****

** **

** **

Dr. Richard Heigl****

Social Web Strategien****

Konzeption****

** **

Hallo Welt! - Medienwerkstatt GmbH****

______________________________****

** **

Residenzstraße 2****

93047 Regensburg****

** **

Tel.  +49 (0) 941 – 66080-193****

Fax. +49 (0) 941 – 66080-189****

** **

www.hallowelt.biz****

heigl< at >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****

** **

*Von:* mediawiki-enterprise-bounces< at >lists.wikimedia.org [mailto:
mediawiki-enterprise-bounces< at >lists.wikimedia.org] *Im Auftrag von *Maria
Miteva
*Gesendet:* Freitag, 8. Februar 2013 19:11
*An:* MediaWiki for enterprises
*Betreff:* Re: [Mediawiki-enterprise] BlueSpice Demo?****

** **

Hi Richard, ****

** **

This is very nice of you to offer and I think it's a great idea. If you
have an idea of how long such a meeting would take and about when would be
a good time I can do a Google Doodle to find a good time and see how much
interest there is. Let me know if I should help with that. ****

** **

Mariya****

On Fri, Feb 8, 2013 at 8:05 PM, Yury Katkov <katkov.juriy< at >gmail.com> wrote:*
***

I'd love to know more about BlueSpice. Markus Glasser have described
the basic on SMWCon Fall 2012:
http://www.youtube.com/watch?v=UDZGH6LMbBY

But still I really interested to see more and will try to go to meeting.
-----
Yury Katkov, WikiVote****




On Fri, Feb 8, 2013 at 9:46 PM, Richard Heigl <heigl< at >hallowelt.biz> wrote:
BlueSpice project.
and we could discuss, how you can use it, if you want.
developments. And also possible is a webshop for extensions, themes, skins
and modules, which everybody can use.
mediawiki-enterprise-bounces< at >lists.wikimedia.org] Im Auftrag von Mark A.
Hershberger
my map.
can fix it!" but the enterprise mindset that we're talking about here just
wants to have a nice package that takes care of it already.
enterprise uptake?"
to have it developed, they'd probably get it.  But that leaves us with a
chicken and egg problem.

_______________________________________________
Mediawiki-enterprise mailing list
Mediawiki-enterprise< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise****

** **

_______________________________________________
Mediawiki-enterprise mailing list
Mediawiki-enterprise< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise
_______________________________________________
Mediawiki-enterprise mailing list
Mediawiki-enterprise< at >lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise