and it had a quite appropriate meaning: "A mixture of
different things; a disordered mixture" (English Wiktionary).
The first release announcement is quoted below.
-Niklas
ke 28. marrask. 2012 klo 12.17 Niklas Laxström (niklas.laxst...@gmail.com)
kirjoitti:
> The Wikimedia Langu
pe 28. lokak. 2022 klo 17.04 Lucas Werkmeister (
lucas.werkmeis...@wikimedia.de) kirjoitti:
> In my opinion, MediaWiki’s PHPCS ruleset feels largely rooted in an older
> version of PHP, where static type declarations (formerly known as “type
> hints”) did not exist. As we move towards more modern
ites, I wasn't sure from
> the final question in the email whether or not this is an outstanding
> technical gap.
>
> Regards,
> [[mw:User:Adamw]]
>
> [1]
> https://wikitech.wikimedia.org/wiki/Event_Platform/EventStreams#Historical_Consumption
>
> On 4/27/22 1:2
to 28. huhtik. 2022 klo 0.12 Tyler Cipriani (tcipri...@wikimedia.org) kirjoitti:
> On Wed, Apr 27, 2022 at 5:22 AM Niklas Laxström
> wrote:
> > Since the beginning of the year, the Wikimedia Language team has enabled
> > translation backports for MediaWiki core, extensions a
Since the beginning of the year, the Wikimedia Language team has enabled
translation backports for MediaWiki core, extensions and skins hosted on
Gerrit. On a weekly schedule compatible translations from master branch are
backpored to all the supported release branches. Currently supported
branches
Messages like "1movedto2" are preserved for compatibility reasons and
should not be used. Long time ago they were used on Special:Log (and the
non-special pages before them). The problem with them is that they are not
full sentences, so translating them into other languages correctly is not
possibl
I'll also add that I wrote an implementation plan (proposal, rather) for
translatable modules. I'd appreciate feedback for the open questions and in
general. Do note though that there isn't currently a timeline for the
implementation.
https://www.mediawiki.org/wiki/Translatable_modules/Technical_im
This is the weekly TechCom board review in preparation of our meeting on
Wednesday. If there are additional topics for TechCom to review, please let
us know by replying to this email. However, please keep discussion about
individual RFCs to the Phabricator tickets.
Activity since Tuesday 2020-12-0
This is the weekly TechCom board review in preparation of our meeting on
Wednesday. If there are additional topics for TechCom to review, please let
us know by replying to this email. However, please keep discussion about
individual RFCs to the Phabricator tickets.
Activity since Monday 2020-10-15
ma 14. syysk. 2020 klo 23.49 Tyler Cipriani (tcipri...@wikimedia.org) kirjoitti:
> The number of new tasks being created with this tag in a given week is
> outpacing the number of tasks being closed in a given week: this past
> week we added 41 tasks and only closed 22.
Majority of the recently cr
This is the weekly TechCom board review in preparation of our meeting
on Wednesday. If there are additional topics for TechCom to review,
please let us know by replying to this email. However, please keep
discussion about individual RFCs to the Phabricator tickets.
Activity since Monday 2020-08-31
The example below works, and I see it used in some extensions, but it
has no autocompletion and not catching typos.
Services.php:
class TranslateServices implements ContainerInterface {
public function getParsingPlaceholderFactory(): ParsingPlaceholderFactory {
return $this->container-
ke 27. marrask. 2019 klo 0.38 Egbe Eugene (agboreug...@gmail.com) kirjoitti:
>
> Hi All,
>
> Is there any documentation or Gadget I can have a quick look at yo be able
> to learn how to enable translation in gadgets?
The only example I know is
https://commons.wikimedia.org/wiki/Help:Gadget-ProveIt
la 6. lokak. 2018 klo 3.44 Paladox via Wikitech-l
(wikitech-l@lists.wikimedia.org) kirjoitti:
> We also have a license file for you to specify the license of your image at
> https://gerrit.wikimedia.org/r/plugins/gitiles/All-Avatars/+/refs/heads/master/LICENSE
> If none is specified then it defau
It's now possible to translate Phabricator in translatewiki.net thanks
to the Phabricator developers, Mukunda Modell, and many others who
participated in https://phabricator.wikimedia.org/T225
We are currently in an experimental phase, where these translations
are only used in https://phabricator.
2017-12-24 1:05 GMT+02:00 Mark A. Hershberger :
>
> This afternoon, while procrastinating by cleaning up my clone of
> gerrit's mediawiki extensions repository, I decided to make a meta
> repository for some non-WMF-hosted extensions. (Hopefully this will
> mean less need to clean up the clone in
The language engineering monthly reports for September, October and
November 2017 are ready.
**Highlights for these months**
* Lots of usability and design improvements to the Content Translation
dashboard.
* There is now a way to link directly to a particular message in
Special:Translate.
* Media
2017-11-07 7:58 GMT+02:00 Kunal Mehta :
>
> But sometimes people aren't familiar with the guidelines, or more likely
> we make a typo somewhere. Here's where the commit-message-validator[2]
> comes in handy!
>
Does the tool check for typos? Typos in commit messages get merged all the
time, includi
The language engineering monthly report for August 2017 is ready.
**Highlights for this month**
Language database is now an independent project to make reuse easier. It
used to be part of jquery.uls library. It contains over 500 entries
detailing basic information about languages, such as their au
The language engineering monthly report for July 2017 is ready.
*Highlights for this month*
Content Translation dashboard has received a major facelift that aligns it
with the Wikimedia style guide and makes it easier to use.
Translatewiki.net now imports new messages up to 9 times per day. New
m
Maybe related: having both SemanticMediaWiki and Visual Editor
installed will still reliably trigger this error.
This was filed as https://phabricator.wikimedia.org/T134562 (which
imho should be reopened).
-Niklas
___
Wikitech-l mailing list
Wikitech
I was reading http://stateofjs.com/2016/introduction/#sections and
could not avoid noticing that the frameworks or technologies we use
are not among the most popular or most liked among the participants of
this survey.
Examples:
* Frontend frameworks: We use jQuery and OOjs UI. The latter does not
2016-10-10 1:25 GMT+03:00 Chris Koerner :
> = Discussions =
>
> == Search ==
> * Translate extension updated to allow searches in a specific language
> (without translations) [3]
Actually it was CirrusSearch that was updated.
Translate already supports filtering the search results by language
whe
Many good and bad changes I can live with. One thing I will miss:
* Columns setting no longer wraps the diff lines. Horizontal scroll is
now unavoidable and cumbersome due to having to use either the mouse
or the arrow keys to move the cursor on the line.
Tips for others:
* I previously used 'r' t
The Wikimedia Language team has been assembling monthly reports about
language support activities for one year. You can read the latest
report at:
https://www.mediawiki.org/wiki/Wikimedia_Language_engineering/Reports/2016-May
Highlights for May include: Special:Translate got an edit summary
field
2016-06-01 9:32 GMT+03:00 Niklas Laxström :
> 2016-05-31 19:23 GMT+03:00 Grace Gellerman :
>> https://www.mediawiki.org/wiki/Scrum_of_scrums/2016-05-25
>> === Release Engineering ===
>> * '''Blocking''': ???
>> * '''Block
2016-05-31 19:23 GMT+03:00 Grace Gellerman :
> https://www.mediawiki.org/wiki/Scrum_of_scrums/2016-05-25
> === Release Engineering ===
> * '''Blocking''': ???
> * '''Blocked''': none
> * '''Updates''':
> ** wmf.3 is rolling forward this week
> ** rc.0 of 1.27 should be out this week
According to t
2016-05-25 2:58 GMT+03:00 Dan Garry :
> Hey Purodha,
>
> On 21 May 2016 at 05:13, Purodha Blissenbach
> wrote:
>
>> On the long run, I think, these portals and their texts should
>> be translatable. Browser settings determining the target language.
>> Looking forward to have them on translatewiki.
I realize no time is a good time for security releases, but this will
be Friday evening or even Saturday night in some parts of the world.
-Niklas
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/
I noticed that lots of extensions were recently updated to use
mediawiki-codesniffer 0.7.1 [1].
This has some implications I think are worth being aware of:
1) Many open patches will need manual rebasing and conflict resolution.
2) Those extensions will now depend on at least PHP 5.4 due to short
2016-04-12 14:01 GMT+03:00 Adrian Heine :
> Hi everyone,
>
> as some of you might know, I'm a software developer at Wikimedia
> Deutschland, working on Wikidata. I'm currently focusing on improving
> Wikidata's support for languages we as a team are not using on a daily
> basis. As part of my work
2016-04-05 8:51 GMT+03:00 Jon Robson :
> Special:Translate doesn't work [1] and the current plan is to make it
> redirect to desktop which is disappointing and I'd guess loses us lots of
> potential editors (myself included).
When we developed the new interface for Special:Translate (aka TUX) we
d
2016-04-04 17:02 GMT+03:00 Quim Gil :
> The first question to answer is what information are you looking for when
> you want to measure developers' "productivity". What would be the
> motivation of that estimation? What is the motivation behind this thread?
One reason comes to me mind. My gut feel
2016-04-04 16:00 GMT+03:00 Subramanya Sastry :
> Niklas and the language team: thanks for your efforts in enabling
> translation features. They are truly important and necessary.
And I want to thank you for your positive and constructive approach
for solving this issue.
> 1. Given the success of
To Brion and other people who think the page translation markup is
annoying and a usability issue: As the (then volunteer) developer who
created it, I can only agree.
The way page translations currently works, which is extensively
documented at [0], is the result of lots of experimenting with what
2016-04-03 11:29 GMT+03:00 Jon Robson :
> The Translate tag has always seemed like a hack that I've never quite
> understood.
I am happy to direct to our documentation [1] anyone who asks, or
explain if the documentation is not sufficient.
The word hack can have both positive and negative meaning
2015-11-13 4:22 GMT+02:00 Chad :
>
> Considering ~50% of subscribers weren't even using the list, and
> we only have 130 remaining subscribers between the two, who would
> be terribly upset at closing one or both of these lists?
It would break my workflow of following all merged commits. I have t
2015-09-22 13:37 GMT+03:00 Niharika Kohli :
> last but not the least, an awesome new search feature for TranslateWiki.
>
The new features are not only for translatewiki.net, they also work on all
Wikimedia sites (and other wikis) where Translate is installed.
For example, https://meta.wikimedia.
2015-08-11 0:54 GMT+03:00 Chad :
> I would like to announce the release of MediaWiki 1.25.2, 1.24.3, and
> 1.23.10.
>
Can "merge patches to master" be added to the release checklist so that
sites running form master, such as translatewiki.net, can update promptly,
please. This is not the first ti
2014-12-01 8:41 GMT+02:00 David Chamberlain :
> I run 5 wikis for a total of 6,000 pages and still use solr in 6 languages.
Thanks for the information, David. We will keep the code for Solr backend.
-Niklas
___
Wikitech-l mailing list
Wikitech-l@lists
MediaWiki is upgrading its plural rules to match CLDR version 26. The
updates include incompatible changes for plural forms in Russian,
Prussian, Tagalog, Manx and several languages that fall back to
Russian [1]. In addition there are minor changes for other languages.
In January 2014, CLDR 24 had
> mw.loader.using( 'ext.pollNY.lightBox', function() {
> LightBox.init();
> } );
>
> ((Any other code using LightBox.* should probably do the same thing,
> athough mw.loader.using is using jQuery's "promises" (I really want to
> call this something else, since jQuery doesn't implement prope
2014-08-27 1:53 GMT+03:00 Jon Robson :
> 2) We need a templating system in core. Trevor is going to do some
> research on server side templating systems. We hope that the
> templating RFC [1] can get resolved however we are getting to a point
> that we need one as soon as possible and do not want t
2014-05-30 0:57 GMT+03:00 Bryan Davis :
> I think bug 65188 [0] is the solution suggested by Ori that you are
> referring to. Would this alone be enough to fix the problems for
> translatewiki.net? More directly, is translatewiki.net using the top
> level composer.json file to manage anything other
2014-05-29 20:27 GMT+03:00 Bryan Davis :
> What use cases did I miss? What other concerns do we have for this process?
The email subject does not cover third party users, so apologies if
this is not the correct place for this.
Currently updating translatewiki.net codebase is annoying, as git does
2014-05-14 1:34 GMT+03:00 Jon Robson :
> During the Zurich hackathon, DJ Hartman, Aude and I knocked up a
> generic maps prototype extension [1]. We have noticed that many maps
> like extensions keep popping up and believed it was time we
> standardised on one that all these extensions could use so
Is there any way to deliver the deprecation messages to a server side
log? I'd rather not spend time inspecting all user scripts and gadgets
manually (I'm thinking of non-WMF sites).
-Niklas
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
h
2014-04-14 15:35 GMT+03:00 Adrian Lang :
> you are right, although I'm not using an older version of MediaWiki,
> I'm on 77bc489c2731827b1c61a6509177eed23193d694 from 2014-04-11.
Is something loading the i18n files manually then? Or is there a
missing $wgMessagesDirs definition matching $wgExtensi
I think technically easiest solution is to modify the i18n.php files:
-$GLOBALS['wgHooks']['LocalisationCacheRecache'][] = function (
$cache, $code, &$cachedData ) {
+$GLOBALS['wgHooks']['LocalisationCacheRecache'][__FILE__] = function
( $cache, $code, &$cachedData ) {
This makes it so that if th
The rewrite did happen, so what is actually left, like Nemo pointed
out, is converting the remaining places in the code using the old
logging code to the new one.
I tried to clarify that by changing the bug title and blockers.
PS: the new logging system also brings other benefits than better i18n
2014-04-03 16:53 GMT+03:00 Justin Folvarcik :
> Just a question: Are the messages still able to be accessed like they were
> before, or will new methods be introduced to gather them and decode the
> JSON?
There are no visible changes for developers using the messages api:
https://www.mediawiki.org
>> use tabs for indentation instead of spaces to be like the rest of
>> mediawiki?
>>
>
> I was going to say the same thing. Why wasn't that caught in code review?
Spaces were chosen because that is what we get with FormatJson::encode
and there is no way to change it except by post-processing. I'm
For UTF-8 adding ensure_ascii = False to json.dumps would fix it. For
HTML, there is no simple way as far as I know. With some searching you
can find some workarounds. Or you can consider using
https://github.com/simplejson/simplejson
I did point out this issue almost a week ago
https://gerrit.wik
I just want to clarify that I was highlighting the possibility of
considering webfonts for *typography*.
I expect everyone to know by now that tofu issue is not yet solved and
people are working on it.
-Niklas
___
Wikitech-l mailing list
Wikitech-l@l
There have recently been questions whether WMF is able to serve
webfonts. Some people think that because of the issues that led to
disabling webfonts by default in Universal Language Selector (ULS),
WMF is not ready to consider webfonts for typography.
I don't think that way. ULS is not a good com
2014-03-08 0:39 GMT+02:00 George Herbert :
> This is not disrespecting development, which is extremely important by any
> measure. But we're running a top-10 worldwide website, a key worldwide
> information resource for humanity as a whole. We cannot cripple
> development to try and maximize stab
2014-02-28 11:09 GMT+02:00 Roman Zaynetdinov :
> From which source gather the data?
>
> Wiktionary is the best candidate, it is an open source and it has a wide
> database. It also suits for growing your project by adding different
> languages.
It's not obvious why you have reached this conclusion
There is also param 'createonly' - Don't edit the page if it exists already
-Niklas
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On one of my wikifarms I only have one local patch to MediaWiki core
left. I'm hoping to have that merged as well, so let me bring this to
your attention: https://gerrit.wikimedia.org/r/#/c/98078/
On a related note, I'm using html templates and I am in need of a way
to deliver them with resource l
Do you know where I can find these hhvm-nightly packages if I want to
try them out on my own?
Last time I tested hhvm on translatewiki.net, there were fastcgi
parameter passing problems which blocked further testing there.
-Niklas
___
Wikitech-l maili
2013/12/27 Tyler Romeo
> If we want a comprehensive templating system in PHP core,
>
I want a templating system that can be used both in PHP and JavaScript and
fits in our way of doing i18n. And a bunny.
-Niklas
___
Wikitech-l mailing list
Wikitech-
Action tokens should give it:
https://en.wikipedia.org/w/api.php?action=tokens&type=patrol
-Niklas
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
days. I read from the linked bug that it is
currently not possible due to bug in PHP.
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
erg.
-Niklas
[1] https://gerrit.wikimedia.org/r/#/c/82116/
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
uld we just get rid of them? That should be easy, by either moving
stuff to the jobqueue or just executing the code immediately.
Or if they are useful for something, can we at least document the
*class* to reflect how it actually works and what it is useful for?
-Niklas
--
re engineer at Twitter.
>> http://www.mediawiki.org/wiki/Meetings/2013-06-27-midday
>
> The times listed at that link are confused, it says both 19:00 PDT and
> 12:30 PDT.
It also says Wednesday, but I assume Thursday is intended.
-Niklas
--
Niklas Laxström
__
https://www.mediawiki.org/wiki/Help:Extension:Translate/Hooks
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
from
svn to git and gerrit, it will need a lot of effort and can annoy
people, but in the end we will be better than before.
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
y a button on pages with math that would switch MathJax
> on (and possibly off via a cookie).
What is the state of MathJax i18n currently? Before we show it to lots
of users it should be translatable.
-Niklas
--
Niklas Laxström
___
Wi
o-date view of the remote master.
Fortunately we still had the workaround in our scripts at
translatewiki.net from last time, so l10n-bot is not affected.
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
htt
On 21 March 2013 20:11, Greg Grossmeier wrote:
> Tim rolled back wmf12 after a nasty bug last night:
> https://bugzilla.wikimedia.org/show_bug.cgi?id=46397
I assume this included all the extension as well.
-Niklas
___
Wikitech-l mailing list
Wikitech
hurt.
This situation seems completely unfair to me. WMF should be able to
communicate upcoming changes itself, not throw it to volunteers.
Volunteers can help, but they should not be responsible for this to
happen.
-Niklas
--
Niklas Laxström
___
Wikit
On 1 March 2013 23:46, Chad wrote:
> Bug: 1234
> Change-Id: Ia90.
> """
>
> So when you do this, you're able to search for "bug:1234" via Gerrit.
> By doing this, you're also removing it from the first line (which was
> our old habit, mostly from SVN days), providing you more space to
> be des
positories.
You can work around both of the above... but then we are again on the
"more than non-significant effort needed" path.
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
ith a tag in Gerrit, so there is
discoverability problem.
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
-Niklas
[1] this is the preferred way to write it
[2] patches welcome
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
ack or cleaned up after my mistakes.
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
n
> extension, but if you see an orphaned extension or just don't feel like
> maintaining one any more, please add {{Unmaintained extension}} to its
> page on MediaWiki.org.
Has any extension been adopted this way?
-Niklas
--
Niklas Laxström
_
ntly changing interfaces and
breaking existing extensions will annoy people depending how much we
will put effort into keeping backwards compatibility. Can't please
everyone.
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists
s something internal to MediaWiki) and hence I've
started calling it WebAPI to make it more explicit.
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
in my hook function?
>>
>> static public function showBacklinks($editpage, &$output){
>> return true;
>> }
OutputPage is a context source, so you can do $output->getRequest().
Less nicer way is $editpage->
to explain all the
"somes" above and make sure that all tests are re-enabled and passing
for all affected extensions.
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
t, in diff view click Preferences,
on the left bottom choose Whole File as context and click Update. It
is no good for copy-pasting though.
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
ne fatal error less
(and at least one remains), though I did spend two hours debugging
that issue.
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
;t know. I barely got working PHPUnit installed in the
first place (3.7.8 - see my other previous phpunit thread). I also
don't know why it occasionally segfaults.
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
h
to give some tender, love and care to our unit tests so that
I don't have to come up with even worse analogies.
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On 28 November 2012 23:54, Platonides wrote:
> On 28/11/12 12:28, Niklas Laxström wrote:
>> * Running of PHPUnit tests is currently broken
> Why?
Because of https://bugzilla.wikimedia.org/42529
There is also one test failure I don't know to fix. The test is marked
as databasel
st release, there can be some rough edges.
Please provide us a lot of feedback so that we can improve for the
next release.
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinf
On 26 October 2012 15:57, Tim Landscheidt wrote:
> Niklas Laxström wrote:
>
>> [...]
>>> All of this shouldn't be necessary, as PHPUnit 3.6.12's
>>> package.xml clearly declares a dependency on PHP_Timer
>>>>= 1.0.1 and <= 1.0.3. In other
too clearly apparently, I had this when installing invoker:
sudo pear install phpunit/PHP_Invoker
phpunit/phpunit requires package "phpunit/PHP_Invoker" (version >=
1.1.0, version <= 1.1.1), downloaded version is 1.1.2
Then I installed version 1.1.1.
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
efined function php_timer_autoload() in
/usr/share/php/PHPUnit/Util/GlobalState.php on line 381
make: *** [default] Error 255
Any ideas?
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
rrently. For reasons unknown to me, there is another
lock inside ->lock() ->unlock() which again fails and disables message
cache.
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
hots and stuff.
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
til someone added getHumanTimestamp which I guess should
be deprecated now.
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On 10 October 2012 16:52, Daniel Kinzler wrote:
> Hi!
>
> I could use some help looking over extensions.
What is the difference between "$content instanceof TextContent" and
"$title->getContentModel() === CONTENT_MODEL_WIKITEXT"
not addressed before the merge. For example MessagesEn.php (a
fix has been submitted by someone else) and MessageCache.php [2].
[1] https://gerrit.wikimedia.org/r/#/c/25736/1 (took me a while to
find that change anymore)
[2] I see now that I misunderstood the code, but at least
]
I don't have time to fix all these myself.
-Niklas
FAILURES!
Tests: 4685, Assertions: 320062, Failures: 62, Errors: 45, Incomplete:
5, Skipped: 6.
make: *** [safe] Error 2
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wiki
t)
> - /extensions (directory with clones of individual extensions or clone of
> mediawiki/extensions.git tracking repo)
In SVN time extensions were a subdir of mediawiki core and I doubt
that everyone has suddenly decided to change it. At least I haven't.
atic methods, I cannot store the users anywhere if I use those.
> Can you possibly send the code in Gerrit so we can have a look at it?
Yes.
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikime
t( 'trans1', __METHOD__, 0,
false, $user );
$this->user1 = $user;
-Niklas
--
Niklas Laxström
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
1 - 100 of 216 matches
Mail list logo
