After much delay, Gerrit 2.6 will be coming to our servers. This release
brings a *lot* of really cool features and fixes, but I'd like to outline a
couple of the major ones:
* A stable, documented RESTful api
* Plugin support:
** We'll be replacing Gitweb with Gitblit once the initial dust of the
** We've got a plugin to let us delete projects
** We're working on plugins for renaming projects, as well as providing
some Bugzilla integration
* IE9 & IE10 are now supported
* The code formatter got some updates, which should solve some of
the ArrayIndexOutOfBounds errors you saw in some diffs.
* Ability to leave comments on a whole file (instead of just a line in a
* Search suggestions
* More unicorns!
We're planning to do this on 1:00-2:00UTC on February 12th (that's
17:00-18:00 PST on February 11th) -- that's one week from today.
Any proofreaders here? I am having a little trouble finding a
triple-underscore, which is used in proofreading to indicate that a
letter should be capitlized.
I would also like to know if there is some way to have a letter appear
with an over printed slash ( / ), which is used in proofreading to
indicate that a letter should be lower cased.
Forwarding, since I guess many non-wikimedia users of mediawiki will be
very happy to see this
---------- Forwarded message ----------
From: Yuvi Panda <yuvipanda(a)gmail.com>
Date: Sat, Feb 9, 2013 at 3:07 AM
Subject: Bootstrap based theme for Mediawiki
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
https://github.com/OSAS/strapping-mediawiki looks pretty awesome! (Example
at http://www.ovirt.org/Home). This also makes bootstrap's classes /
layouting helpers available to content inside the wiki itself, which is
(thanks to Patrick Reilly on IRC)
Yuvi Panda T
Yuvi Panda T
I've read about the proposal to "rework" the documentation about the API
on the mailing list.
I think that write some technical documentation, is a very good
opportunity to "enter" such a big ecosystem like the Wikimedia one...
But I'm quite novice in this subject,
Yuri Astrakhan how can I help ?
Using MW 1.20.2, I've edited the TOOLBOX heading in MediaWiki:Sidebar with no effect whatsoever in the Vector skin or other skins. Is there a setting needed to enable this?
Placing common links to test like this:
** Special:Recentchanges|Recent changes
does not modify the Toolbox links at all.
As I have been talking to third-party MW users quite a lot recently, I
notice that one of the major issues they are facing is the lack of
visibility on MW.org. I have seen some previous work like that has been
reverted because WMF does not want to endorse any external parties on mw.org.
However, at the same time I see some pages featuring such users such as
http://www.mediawiki.org/wiki/MediaWiki_with_BitNami. So my question here
is how much is acceptable?
I think it would be helpful for both the third-party community and for MW
itself to give third-party users more visibility. It will help third-party
users know about each other and support each other, get more involved with
the community and possibly attract more business. At the same time having
some success stories visible is likely to attract more MediaWiki users,
while a thriving and engaged third-party community is likely to bring more
innovation to the software itself.
I have been working on some lists of wiki farms, consultants, developers,
hosting companies and interesting installations for my internship, which
you can see here. However, I am wondering if I could give the lists a
little more visibility with a disclaimer on top that WMF does not in any
way endorse the listed companies and guarantee for the quality of their
service. Also, I think updating and revitalizing the
http://www.mediawiki.org/wiki/MediaWiki_testimonials page is a good idea.
Another way to give some users visibility is having featured projects of
the month or something like that, which would require someone's consistent
How much do you think is acceptable?
we have a wiki  with ~30 sisters in different languages. All the
wikis run on the same server using the same the code, but have different
Keeping the interlanguage links using pywikipediabot (what we currently
do) is very inefficient, to link a single page in a single variant to
all its translations we need ~30 updates. I know Interlanguage extension
should help us with this issue, but its description says it will not be
used for Wikimedias wikis, but will be replaced by Wikibase extension,
that is more versatile.
The ideal state is that all pages from non-English wikis contain only a
link to English version (in some format), nobody has to add any other
links by hand and the symmetric and transitive closure of the links is
updated either fully automaticly or using simple maintenance script
(preferably runnable on the same server, without using API as
Pywikipedia bot does).
Is this goal realistic? Shall we use Interlanguage or Wikibase?