rticle absent going to
> another site. So now those wars about content will have to go to two sites
> at once, one of which will be international. So that means users who have
> never logged into Wikipedia will have the ability to control the content of
> the project.
>
So? Y
ossibly deploy Wikidata, in theory.
>
Wikidata phase 2 is already live on 11 different wikis. (
http://blog.wikimedia.de/2013/03/27/you-can-have-all-the-data/)
>
> MZMcBride
>
>
> -- Legoktm
http://enwp.org/User:Legoktm
>
> ___
>
ge.
Thanks,
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
ays (P569).
>
This feature of Wikidata is still in progress, for the time being you can
use Magnus's tool[1] to generate a list that a bot could use.
[1] http://208.80.153.172/
--Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.o
have a bot automatically create a stub page
on mw.o when the change is merged, and then a human can fix it up.
-- Legoktm
[1] https://github.com/legoktm/mwhooks/blob/master/create_onwiki.py
[2] https://www.mediawiki.org/wiki/Manual:Hooks/GetLogTypesO
rrow's RFC review meeting.
Thanks,
-- Kunal Mehta (Legoktm)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
eta.wikimedia.org/wiki/Synchbot
[3] https://meta.wikimedia.org/wiki/SWMT
[4] https://meta.wikimedia.org/wiki/User:Snowolf/How_to_globally_Twinkle
[5] https://gerrit.wikimedia.org/r/#/c/94837
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedi
ove to
> rauth. But it seems to work and makes me feel fuzzier about using OAuth as
> pseudo authentication.
There is the flask-mwoauth[1] library created by valhallasw that the
gerrit-patch-uploader uses.
[1] https://github.com/valhallasw/flas
Hi,
Given that the Configuration cluster had the second most number of
votes in the poll, why was it left of the agenda entirely?
-- Legoktm
On Thu, Jan 16, 2014 at 10:47 AM, Diederik van Liere
wrote:
> Heya,
>
> The Program Committee for the Architecture Summit has published a
On Thu, Jan 16, 2014 at 2:52 PM, Rob Lanphier wrote:
> Let's put that number at 95% :-) I don't want to commit the group to
> anything; it's at the top of the short list, but you never know where
> people will want to take the conversation.
>
> Legoktm, the thin
erting the current implementation out of the release branch.
[3]: https://gerrit.wikimedia.org/r/#/c/109850/
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On 04/25/2014 09:10 PM, John wrote:
Looks the the wikibugs is having issues, and needs poked
The new wikibugs is now in #wikimedia-dev, and also in a few other channels.
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https
On 5/18/14, 7:36 AM, Yuvi Panda wrote:
Hello everyone!
I just merged a change into the new wikibugs that will help reduce
botspam on #wikimedia-dev. wikibugs will no longer report bugs on
#wikimedia-dev that have been reported in other channels, thus
reducing duplication. The previous behavior w
user talk pages should be marked as a bot since
the user will receive a notification regardless, but ones that are made
to Project (or other) namespaces, should not be flagged as bot so users
will see them in their watchlists.
-- Legoktm
___
Wikitech
n
loading extensions. We would no longer use the current method of
require_once "Foo.php";, but instead $wgEnableExtensions[] = 'foo';, and
MediaWiki would take care of the rest.
Please leave any comments or thoughts you might have on the talk page.
Thanks,
-- Legoktm
_
-1; it's
just waiting for someone to +2 it :)
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
trivial but just needed people to look at it.
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
er who has editbugs right now, or will
it also apply to those we give editbugs to in the future?
Thanks to Chad for the quick resolution on this, hopefully this will be a
positive change overall.
Thank you for finally getting this done! :)
On 5/23/14, 9:26 PM, Legoktm wrote:
On 4/29/14, 1:56 PM, Sumana Harihareswara wrote:
Looks like we are still working on merging the "Make abstract Config
class truly implementation-agnostic" changeset.[0]
[0] https://gerrit.wikimedia.org/r/#/c/109850/
The patch currently has
require the user to put a function
call in their configuration.
== Schema ==
I've written a basic JSON schema for extension.json files and put it up
at [2].
[1]
https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-05-30
[2]
https://www.mediawiki.org/wiki/Requests_for_
x27;t mean
autoloading in the sense of if the extension is present, MediaWiki will
automatically enable it. What I meant was, that if your configuration has:
$wgEnabledExtensions[] = 'Math';
You shouldn't *also* have to write:
wfLoadExtensions();
Just the first alone should
g?
> [2]
> https://commons.wikimedia.org/wiki/File:MediaWiki_Release_Request_For_Proposals_2014.pdf
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
JsonConfig, but I think at the architecture summit
people were fine with having it in core?
VisualEditor is a different beast, and can't be in core due to its
dependency upon Parsoid. Once Parsoid replaces the PHP parser, I see no
reason it can&
s the command-line
installer to prevent installation if it is enabled.
[1] http://www.php.net/manual/en/security.globals.php
[2] https://gerrit.wikimedia.org/r/144854
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists
So, "early next week" has already passed, and a week after that too. :(
Any update on when you'll be making an announcement?
-- Legoktm
On 6/27/14, 4:49 PM, Greg Grossmeier wrote:
> Hello all,
>
> We're in negotiations with one of applicants for the MediaWiki rele
bmitted in the last 15 months.
Probably not since I don't really know that much about tor, but I'm
willing to review Tyler's patches if he's unable to find other people.
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
in Bugzilla[4].
Additionally, I'd like to thank ^demon and YuviPanda for their help in
putting this service together.
-- Legoktm
[1] https://gerrit.wikimedia.org/r/#/c/149474/
[2] https://extdist.wmflabs.org/dist/
[3] https://bugzilla.wikimedia.org/show_bug.cgi?id=44022
[4]
on this a bit? For which extensions would this be
useful?
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Sorry about the super super late reply.
On 6/4/14, 2:12 AM, Daniel Friesen wrote:
> On 2014-06-04, 1:29 AM, Legoktm wrote:
>> A few more updates about the RfC after the IRC meeting. In case you
>> missed it, the logs are at [1].
>>
>> == Extension locations ==
>>
n the future, dependencies via composer. The entire
setup is puppetized however, so it should be feasible to move it into
production if we decide that we want to.
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia
On 8/7/14, 10:58 AM, David Gerard wrote:
>> but if you are a mobile developer using the REST API
> every day, you need some other term to specify api.php.
>
> Is "api.php" unsuitable for some reason?
I like "api.php" too, given that we refer to the
f Mark's comments in [1]: If a URL has "wmflabs.org"
in it...don't put anything, ANYTHING, important there.
Just use Bugzilla, most RfCs are already using it to track issues anyways.
-- Legoktm
[1] http://lists.wikimedia.org/pipermail/wikitech-l/2013-August/071442.html
>>
>
> Would it be possible to get the common directory out of core/skins/ as
> well?
That's <https://bugzilla.wikimedia.org/show_bug.cgi?id=69277>.
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
In honor of bug 1's 10th birthday today, take the time to fix some out
of date documentation or write some missing ones :)
https://bugzilla.wikimedia.org/show_bug.cgi?id=1
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
gets+branch:RL2,n,z>
shows the patches happening in the "RL2" branch. We've also been making
some changes to core in the process.
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
to implement a sane code review
process for these pages. I don't imagine it will happen anytime soon,
but now seems like a good time to start discussion about it.
[1]
https://szl.wikipedia.org/w/index.php?title=MediaWiki%3ACommon.js&diff=prev&oldid=208782
[2] https://bugzilla.wi
nf+status:open,n,z>!
Thanks,
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
t;3" on some external website, especially
>> without knowing that that "3" comes from a grand total of 1 person?
>>
>>
> Relevant: http://xkcd.com/1098/
>
> -Chad
Also: http://xkcd.com/937/
-- Legoktm
_
iaWiki versions, tests, etc. I don't
remember the etherpad link unfortunately, but I assume someone has the
notes.
IMO, that would be way more useful to me than arbitrary user ratings.
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikime
On 8/23/14, 6:38 PM, svetlana wrote:
> [...]
>
> Are there changes affecting only JavaScript, or also CSS?
>
> CSS is another beast that needs effort to support in browsers properly.
Just JavaScript, as the subject line indicates
ich I thought was going to be some CI automated
builds server from your email title :)
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
y release:
<https://gerrit.wikimedia.org/r/#/q/project:mediawiki/core+branch:REL1_19+status:merged,n,z>.
-- Legoktm
> On 27 August 2014 01:02, Markus Glaser wrote:
>> Hello everyone,
>>
>> this is a notice that on 27th August between 20:00-22:00 UTC we will release
&g
rocess>
for more details. The corresponding config change is
<https://gerrit.wikimedia.org/r/#/c/160158/>.
-- Kunal / Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
ase:
<https://bugzilla.wikimedia.org/buglist.cgi?action=wrap&list_id=345619&product=MediaWiki&resolution=---&target_milestone=1.24.0%20release>,
some have open patches awaiting review!
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedi
going to be
branched, meaning that master should be on "1.25alpha" already. Waiting
until late October to branch means that won't happen. The bump to 1.24
(<https://gerrit.wikimedia.org/r/#/c/125735/>), it was done right after
1.23wmf22 was branched, so
On 9/22/14 1:10 PM, Mark A. Hershberger wrote:
>
> In deference to the concerns raised by James Forrester, Markus and I
> have decided not to back out the REL1_24 branch.
Will you be creating the REL1_24 branches for extensions and skins, or
would you like me to do that?
-
t edits made via TOR.
The TorBlock extension already adds a "tor_exit_node" variable[1] to the
AbuseFilter, which is a simple boolean value whether the edit is being
made through tor or not.
[1]
https://github.com/wikimedia/mediawiki-extensions-TorBlock/blob/master/TorBlock.clas
On 10/1/14 8:02 AM, John wrote:
> Prior to TOR being enabled we need to be able to flag both logged in and
> logged out edits made via TOR.
There's a $wgTorTagChanges option which does exactly that, except it's
currently disabled in CommonSettings.
dropping 5.3.2 support? I've uploaded
[5] that actually increments the required version number.
Thanks,
-- Legoktm
[1] https://www.mediawiki.org/wiki/Library_infrastructure_for_MediaWiki
[2] https://github.com/cssjanus/php-cssjanus/blob/master/composer.json
[3] https://github.com/cssjanus
l I found [2], but it doesn't say which PHP version is being
used. Drupal 7 requires 5.2.5 (but recommends 5.3), and Drupal 8
requires 5.4.
-- Legoktm
[1] https://wordpress.org/about/stats/
[2] https://www.drupal.org/project/usage/drupal
___
Wiki
s better than docs split into zillions of html documents
If you scroll down a bit, there's a link that says "All help in one
page" and sends you to
<https://www.mediawiki.org/w/api.php?action=help&recursivesubmodules=1>.
-- Legoktm
___
l;dr:
$ composer install
OR
$ git clone https://gerrit.wikimedia.org/r/p/mediawiki/vendor.git
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
are you subscribed to the mediawiki-api-announce mailing list[2]?
It's useful if you want to be aware of what changes are
planned/happening for the API. For example, the tokens change was
announced[3] back in August.
-- Legoktm
[1] https://www.mediawiki.org/w/api.php?modules=rollb
Hi,
CSSJanus is now[1] included in MediaWiki core through composer, and
maintained as an external library on Github[2].
Running "composer update" will download and autoload the library, or if
you're using the mediawiki/vendor repository a simple "git pull" will wor
wiki MediaWiki:Common.* pages are used and the
> access restrictions on them, I think it is reasonable to allow JS and
> CSS from them while continuing to disallow individual's JS and CSS on
> the Special:Preferences and Special:Login page.
>
> Alexia filed a bug[2] and Kunal (
re flag so we could disable this on WMF wikis, but
> sites with robust auditing of their common.css can enable it.
I've amended <https://gerrit.wikimedia.org/r/#/c/165979/3> to be
controlled by a config setting.
-- Legoktm
___
Wikitech-l ma
loaded[3]
some changes to make them all validate. Reviews appreciated :)
-- Legoktm
[1] https://gerrit.wikimedia.org/r/#/c/173457/
[2] https://getcomposer.org/doc/03-cli.md#validate
[3]
https://gerrit.wikimedia.org/r/#/q/status:open+topic:composer-validate,n,z
ly after there have been so many
discussions about this that the "release team" themselves were involved in.
-- Legoktm
[1] https://gerrit.wikimedia.org/r/#/c/175453/
[2] https://gerrit.wikimedia.org/r/#/c/132788/
[3]
https://www.mail-archive.com/wikitech-l@lists.wikimedia.org/msg76217.html
[
d and Yuvi for helping with code review and the deployment!
-- Legoktm
[1] https://www.mediawiki.org/wiki/Special:SkinDistributor
[2] https://gerrit.wikimedia.org/r/#/c/174777/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
t; When we have VE-WordPress and VE-Drupal and VE-Joomla and whatever, we'll
> put them as… GVEW, GVED, GVEJ *etc.* and just hope we never have a first
> character clash on integrations?
I think we would set up VE as a prefix rather than dumping them under
general, so: VEWP, VEDP,
plan decided, I'll start working on updating
documentation and other fun stuff.
[1] https://gerrit.wikimedia.org/r/#/c/166705/
[2]
https://www.mediawiki.org/wiki/Requests_for_comment/Extension_registration
Thanks,
-- Legoktm
___
Wikitech-l mailing list
s[2]. In my experience it's extremely CPU
intensive and slow, so it's not something that is convenient to run
before every commit.
[1] https://integration.wikimedia.org/cover/mediawiki-core/master/php/
[2] https://tools.wmflabs.org/coverage/
-- Legoktm
_
tried getting update.php to run checkComposerLockUpToDate.php but it
was messy and didn't really work well, so I uploaded a patch[1] that
adjusts the intro text to recommend that you run
checkComposerLockUpToDate.php before running update.php.
[1] https://gerrit.wikimedia.org/r/#/c/185592
Hi!
I have nominated TTO for +2 in mediawiki/ repositories:
<https://www.mediawiki.org/wiki/Gerrit/Project_ownership#TTO_for_.2B2_in_mediawiki.2F>.
Please comment :)
Additionally, there are some other requests on that page that could use
some comments.
Thanks,
-- L
t able to attend.
We'll also have an IRC meeting sometime after the summit, specifics
still to be determined.
[1] https://phabricator.wikimedia.org/T87240
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On 01/21/2015 09:39 AM, Jeroen De Dauw wrote:
> Hey,
>
> Does the new syntax offer any advantage over the old one?
It's a little bit faster by cutting down one function call which adds up
when a lot of hooks are called.
-- Legoktm
odel"
right to just create a list. :/
[1] https://phabricator.wikimedia.org/T72592
[2] https://phabricator.wikimedia.org/T73163
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
::canBeUsedOn() in
individual content handlers.
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On 01/16/2015 05:52 PM, Legoktm wrote:
> I tried getting update.php to run checkComposerLockUpToDate.php but it
> was messy and didn't really work well, so I uploaded a patch[1] that
> adjusts the intro text to recommend that you run
> checkComposerLockUpToDate.php before r
version number history instead of waiting for a magical 2.0.
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
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_management
-- Le
On 01/25/2015 06:04 PM, Zack Weinberg wrote:
> On Sun, Jan 25, 2015 at 1:27 PM, Legoktm wrote:
>> On 01/15/2015 08:26 PM, Chad wrote:
>>> I've been saying for over a year now we should just drop the 1. from
>>> the 1.x.y release versions. So the next release
I developer, we
occasionally have to make breaking changes, and if we broke something
too fast, it would be nice to have feedback if that was the case so we
can improve in the future.
[1] https://phabricator.wikimedia.org/T75616
-- Legoktm
___
Wikitech-l mail
On 02/05/2015 04:51 PM, Pine W wrote:
> What is the naming convention for these data centers?
<https://wikitech.wikimedia.org/wiki/Infrastructure_naming_conventions#Datacenter_Sites>
-- Legoktm
___
Wikitech-l mailing list
W
[2] https://test.wikipedia.org/wiki/User:Legoktm
[3] https://www.mediawiki.org/wiki/Help:Extension:GlobalUserPage
[4]
https://phabricator.wikimedia.org/maniphest/task/create/?projects=PHID-PROJ-j536clyie42uptgjkft7
[5] https://phabricator.wikimedia.org/T72576
Thanks,
On 02/13/2015 02:14 PM, Max Semenik wrote:
> Sorry for all the trolling, but why instead of discussing how we need a
> responsive skin for MediaWiki and waiting for Winter to come don't we just
> do it:
> * Move Minerva out of MobileFrontend
https://phabricator.wikimedia.org/T
t shouldn't be too difficult.[2]
[1]
https://www.mediawiki.org/wiki/Requests_for_comment/Third-party_components
[2] https://phabricator.wikimedia.org/T88485
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hello!
Global user pages have now been deployed to all public wikis for users
with CentralAuth accounts. Documentation on the feature is available at
mediawiki.org[1], and if you notice any bugs please file them in
Phabricator[2].
Thanks to all the people who helped with the creation and dep
e, though I personally would prefer to ignore it.
[1] https://getcomposer.org/doc/02-libraries.md#lock-file
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
W currently supports and those it
should support in the future, without requiring tons of hooks or ugly hacks.
Please leave comments and feedback on the talk page :)
Thanks!
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedi
n what ways are -
> https://www.mediawiki.org/wiki/Requests_for_comment/AuthManager - and -
> https://phabricator.wikimedia.org/T89733 - anticipating adding additional
> languages? Thanks.
AuthManager is mainly an internal backend refactor that has nothing to
do
need updating,
file bugs that block T49918[1] and T69758[2].
[1] https://phabricator.wikimedia.org/T49918
[2] https://phabricator.wikimedia.org/T69758
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/ma
? We
already have IRC and mailing lists, so why do we need yet another
communication system? Are we going to be enabling Phriction next?
Please turn it off.
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia
d
implement that, please, write your own RfC!
> 3. In general, has enough research been done on the existing packaging
> and dependency ecosystem to see if we can leverage an existing system?
This was probably the most frustrating part of the entire meeting. If
people want to research debs/rp
verted! Stop by if you
want to work on converting an extension, learn about the new system, and
find out what's next! I'll also be working on improving the
documentation for sysamdins and developers at that time.
Phab task: https://phabricator.wikimedia.org/T9
dn't need to contain all those per-language modules. And
>would allow restyling the highlighted text easily and consistently.
This would be fantastic. Related bugs are
<https://phabricator.wikimedia.org/T85794> and
<https://phabricator.wikim
r the bug is in an extension like PageTriage which is only used on the
English Wikipedia, we have to: rush to make the 4pm SWAT window, deploy
on Friday, or wait until Monday; which from what I remember were similar
reasons from when we moved the train from Thursday to Wedn
or.wikimedia.org/T15299> to indicate that.
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
resources and work on it again?
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
uous_integration/Entry_points#PHP>
to configure your repository, and file a bug under
#Continuous-Integration-Config to have jenkins configured to run it on
patches.
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://
<https://phabricator.wikimedia.org/T41592>, which
contains a pretty good rationale of why we currently don't version the API.
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Do we have usage statistics on how many people are still using
old-bugzilla? I still use it frequently for searching for example.
Will old-bugzilla redirect to static-bugzilla?
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimed
Jenkins happy sucks and slightly clutters the commit history.
I would prefer this one.
[1] https://phabricator.wikimedia.org/T93812
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
ta)
I have submitted patches which bump the depdencies for extensions
<https://gerrit.wikimedia.org/r/#/q/status:open+topic:bump-dev-deps,n,z>,
however
some are failing due to the new sniffs. Please amend the patches to make
them pass and I can
as plans to
library-ize other global functions.
[1] http://packagist.org/packages/mediawiki/at-ease
[2] https://gerrit.wikimedia.org/r/#/c/217311/
[3] https://phabricator.wikimedia.org/T100922
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
that this is served via
>> CentralNotice?
No, it was a site notice:
https://en.wikipedia.org/w/index.php?title=MediaWiki:Sitenotice&oldid=669390461
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Filed an "Unbreak Now!" bug under MobileFrontend for this:
<https://phabricator.wikimedia.org/T104401>
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On 07/01/2015 11:29 AM, Grace Gellerman wrote:
> https://www.mediawiki.org/wiki/Scrum_of_scrums/2015-07-01
I noticed: "Yandex coming up soon!" under ContentTranslation. Are there
more details about what this means?
-- Legoktm
___
Wikit
On 07/01/2015 06:50 PM, Ricordisamoa wrote:
> Il 02/07/2015 03:28, Legoktm ha scritto:
>> I noticed: "Yandex coming up soon!" under ContentTranslation. Are there
>> more details about what this means?
>
> https://phabricator.wikimedia.org/T89844 I think
Thanks f
but not contain their content.
> If not, can you forecast when Flow will appear in the dumps?
I don't know when dumps of Flow will become available, but [3] is the
tracking ticket for it.
[1] https://phabricator.wikimedia.org/T92303
[2] https://phabricator.wikimedia.org/T93925
[3] htt
1 - 100 of 236 matches
Mail list logo