On 01/15/2013 03:18 AM, Robert Vogel wrote:
Hi everybody!
I'm writing an extension that needs to replace/disable the build-in
suggestion feature of the search box. In earlier versions this could be
archived by setting $wgEnableMWSuggest
Hello,
My own preference would be to have this in the core for several reasons.
It seems that it makes some existing core code simpler. There's
already some code dealing with disambiguation in the core
(Special:Disambiguation, ...).
Several external tools, including my own WPCleaner [1], are
Hi everyone!
Can anyone recommends some blogs that describes tricks/tips/use cases
of wikis, especially MW/SMW? I'm running the blog myself and need some
inspiration.
Very truly yours,
Yury Katkov, WikiVote
___
Wikitech-l mailing list
Japanese RPG games does something interesting. When you get a quest
like Go to the house of MrTom and pick the toothnail the words
MrTom and toothnail are bolded. Something in the system (maybe is done
manually wen the quest text is written) acknowledge entities in the
system ( NPC characters,
2013/1/12 Cristian Consonni kikkocrist...@gmail.com:
Hi there,
(Not sure if this is the right place, but I can't figure of anywhere else)
this morning a bunch of users were automatically removed
from WikiIt-admins-l mailing list due to a blacklisting operated
from Tin/Interbusiness on
2013/1/16 Cristian Consonni kikkocrist...@gmail.com:
Currently there's should be no blocks on the domains
tin.it/alice.it=aliceposta.it che sono nel dominio di gestione Telecom
Italia IT.
(sorry, forgot to translate completely... yes, I'm a genius =P)... anyways:
Currently there's should be
Hey,
From a technical point of view it's nicer to have it as an extension as it
prevents feature bloat in core. OTOH the lack of extension distribution
mechanism is an argument against.
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
On Wed, Jan 16, 2013 at 7:09 AM, Tim Starling tstarl...@wikimedia.org wrote:
I am also concerned about demotivating people.
The motivation factor works with the two positions.
I felt a little demotivated after having read all these we don't care
about typos positions at the start of the thread
On Wed, Jan 16, 2013 at 8:06 AM, Sébastien Santoro
dereck...@espace-win.org wrote:
At the end, the direct commit message edit in the UI will offer an
acceptable solution: corrections will be more trivial than found again
my branch, amend the commit, resubmit as a new patchset. Meanwhile, we
Hello,
For some weeks now, the PHPUnit tests for MediaWiki core have been
randomly failing with an 'exit code 139' error. I did not bother
investigating it caused I had no clue about what would cause it and it
happened mostly in the 1.21wmf7 branch, not master.
The mighty Tim Starling found out
Hi again!
Put it another way: what is the right way of exporting/importing a
bunch of files from one MediaWiki to another?
Cheers,
Yury Katkov, WikiVote
On Mon, Dec 24, 2012 at 6:38 PM, Yury Katkov katkov.ju...@gmail.com wrote:
Hi everyone!
I want to move my wiki from one server (A) to
On Wed, Jan 16, 2013 at 8:27 AM, Antoine Musso hashar+...@free.fr wrote:
Hello,
For some weeks now, the PHPUnit tests for MediaWiki core have been
randomly failing with an 'exit code 139' error. I did not bother
investigating it caused I had no clue about what would cause it and it
happened
Thanks Tim for pitching in.
On 16.01.2013 07:09, Tim Starling wrote:
Giving a change -1 means that you are asking the developer to take
orders from you, under threat of having their work ignored forever. A
-1 status can cause a change to be ignored by other reviewers,
regardless of its merit.
Le 16/01/13 14:06, Sébastien Santoro a écrit :
Should it be a formality to expedite in
30 seconds or an informative valuable text describing the change,
crafted with care and proofread before submission or merge?
To me the commit summary introduce the patch to the reviewers and should
also
Le 16/01/13 02:58, Ryan Kaldari wrote:
Back in December, there was discussion about needing a better method of
identifying disambiguation pages programmatically (bug 6754). I wrote
some core code to accomplish this, but was informed that disambiguation
functions should reside in extensions
Hi Platonides
2013/1/15 Platonides platoni...@gmail.com:
I tried to get the content via getArticleID() ...
$titleObj=Title::newFromText(Existing page);
$articleID=$titleObj-getArticleID();
Article::newFromID($articleID)-fetchContent();
etc.
... but it returns $articleID=0 although the page
Hi Platonides
(sorry I posted from a wrong Email address, I try again with a proper
subject line to get the thread line correct on
http://news.gmane.org/gmane.science.linguistics.wikipedia.technical)
2013/1/15 Platonides platoni...@gmail.com:
I tried to get the content via getArticleID() ...
On Wed, Jan 16, 2013 at 2:11 AM, Jon Robson jdlrob...@gmail.com wrote:
To me disambiguation seems like a common problem of wikis and thus
should be a core feature.
On a wiki about people, people share the same name
On a wiki about cities, cities share the same name
etc etc you get the idea.
And finally, many wikis built their own custom features:
ProofreadPage on wikisource is of particular note here, e.g.
https://en.wikisource.org/w/index.php?title=Page:United_States_Statutes_at_Large_Volume_43_Part_2.djvu/15action=edit
-Chris
___
On 01/15/2013 02:08 PM, Rob Lanphier wrote:
Please join me in welcoming Ram!
Ram, welcome to Wikimedia. I look forward to working with you. Since
you have experience teaching computer science, we'll have to talk about
how we can be teaching and training our tech community better!
--
Sumana
Hi,
One of Tyler Romeo's suggested approach is to use
Article::newFromTitle($titleObj)
... but it does need a second argument of type IContextSource. I do
not know how to get it or how to instantiate it yet. At the moment it
does not retrieve the page content as well because of the missing
On Jan 15, 2013, at 9:18 AM, Robert Vogel vo...@hallowelt.biz wrote:
Hi everybody!
I'm writing an extension that needs to replace/disable the build-in
suggestion feature of the search box.
In case there may be a better approach to solve your problem, what is it you're
looking to add
Nicolas Vervelle nvervelle at gmail.com writes:
My own preference would be to have this in the core for several reasons.
[...]
Yes, the core code already handles disambiguation pages specially in some
ways (Special:Disambiguations, MediaWiki:Disambiguationspage). But it
treats them as
Hi, next week I will have a casual chat with Siko about the new
Wikimedia Individual Engagement Grants and how MediaWiki contributors
could theoretically benefit from them.
If you have specific questions or feedback there is nothing stopping you
from contact her directly, but maybe it's more
You could try RequestContext::getMain() to get the context source object.
Alex Monk
On 16/01/13 16:56, Andreas Plank wrote:
Hi,
One of Tyler Romeo's suggested approach is to use
Article::newFromTitle($titleObj)
... but it does need a second argument of type IContextSource. I do
not know how
- Original Message -
From: . oscar.vi...@gmail.com
It could be interesting (but I have no idea if is feasible), if git
recognize automatically elements in a commit text, and colorize it on
the terminal screen (or maybe bold it if the screen renders using
truetype fonts). This way, if
This is a ridiculous conversation and I can't believe it now spans +20 messages.
___Don't___ -1 a patchset for a typo. The result of that is far more
catastrophic. We put off volunteers and people end up wasting valuable
time doing rebases due to the time taken to find another code review.
Code
Op 15-1-2013 12:44, Jeroen De Dauw schreef:
bla
IMHO all commit messages should be green.
Maarten
*hides*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Tue, Jan 15, 2013 at 9:19 AM, Sébastien Santoro dereck...@espace-win.org
wrote:
Congratulations for your talk. It's nice to see a MediaWiki
involvement in this conference.
Thanks, I hope to see you there. :)
This is not the only MediaWiki talk, I think there will be two more[1].
Željko
If you have any questions about presenting at FOSDEM then let us know. Many
of us have presented about Wikimedia related projects at FOSDEM before.
--tomasz
On Wed, Jan 16, 2013 at 10:32 AM, Željko Filipin zfili...@wikimedia.orgwrote:
On Tue, Jan 15, 2013 at 9:19 AM, Sébastien Santoro
On Wed, Jan 16, 2013 at 7:26 PM, Jon Robson jdlrob...@gmail.com wrote:
This is a ridiculous conversation and I can't believe it now spans +20
messages.
Apparently you don't care, but other people do care. Please do not
disregard other people's opinions because you believe yours is correct.
To
On Wed, Jan 16, 2013 at 7:35 PM, Tomasz Finc tf...@wikimedia.org wrote:
If you have any questions about presenting at FOSDEM then let us know. Many
of us have presented about Wikimedia related projects at FOSDEM before.
I gave a similar talk (about a test automation project that I did for a
I don't mind getting dinged for typos. If I'm being sloppy it's fair to
point it out.
However, I think the social contract should be that after I fix the typos
you requested then you owe me a real code review where you look at the
merits of the code. Code review is an awesomely useful but time
Interesesting. Could this possibly work like gsoc but aimed at experianced
devs instead of newbies? For example if I (in theory) had an idea for a new
feature or extension that could have a large impact on how wikimedians use
mediawiki could I potentially get a grant to work on such an idea over
2013/1/16 Krenair kren...@gmail.com:
You could try RequestContext::getMain() to get the context source object.
Alex Monk
On 16/01/13 16:56, Andreas Plank wrote:
I tried many functions in various classes:
RequestContext
WikiPage
Title
Article
... but it is always the same I do not get the raw
On Fri, Jan 4, 2013 at 11:00 AM, Krinkle krinklem...@gmail.com wrote:
(...)
I've recently looked into a documentation generator for VisualEditor and
though I haven't stopped looking yet, I'm currently pausing rather long at
JSDuck. It is very well engineered and especially optimised for
It seems that I've found the way:
Export(in the FROM wiki directory): php maintainance/dumpBackup.php
--current --pagelist=tmp --uploads ~/dmp
Import(in the TO wiki directory) : php maintainance/importDump.php
~/dmp --uploads
Here dmp is the list of files.
On Wed, Jan 16, 2013 at 5:34 PM,
On 01/16/2013 11:16 AM, bawolff wrote:
Interesesting. Could this possibly work like gsoc but aimed at experianced
devs instead of newbies? For example if I (in theory) had an idea for a new
feature or extension that could have a large impact on how wikimedians use
mediawiki could I potentially
On 2013-01-16 3:07 PM, Luke Welling WMF lwell...@wikimedia.org wrote:
I don't mind getting dinged for typos. If I'm being sloppy it's fair to
point it out.
However, I think the social contract should be that after I fix the typos
you requested then you owe me a real code review where you
Hi, I'm writing a new extension and would like to get some code reviewers
(even 1 would be fantastic).
May I have any assistance?
Extension: http://www.mediawiki.org/wiki/Extension:NamespaceRelations
Current pending reviews:
Would it be possible/difficult to get something similar working for
gadgets on WMF wikis?
Helder
What would be really cool would be if the js content handler code detected
code doc comments and formatted them nicely. Something similar to how back
in the old days people used to have things
Thanks for the response, Rob (and I hope you're feeling better soon). I'm
terrified about using new tools to deploy on Thursday, but super excited to
be leaving scap behind \o/ Will there be git-deploy gurus on call or
generally available during upcoming deployment windows?
On Tue, Jan 15, 2013
There are ongoing separate discussions about the best way to organize
testing sprints and bug days. The more we talk and the more we delay the
beginning of continuous activities the more I believe the solution is
common for both:
Smaller activities and more frequent. Each one of them less
Hi everyone,
We attempted to deploy 1.21wmf8 using git-deploy[1], and ran into
enough problems that we decided the best course of action is to use
scap[2] today and for the foreseeable future.
The new plan is to implement scap/sync-file/sync-dir for Eqiad as a
temporary solution for next week
Do you want the files or not?
The first post sounds like you don't, in that case you'd need to truncate
the image/oldimage/archive tables. This will remove all registration of the
files. Clearing memcached (or whatever cache you use) might be needed to.
You can copy the files over with
On 17/01/13 00:14, Chad wrote:
Really, I think the whole thread is moot with the pending upgrade.
Typos should always be fixed before merging (I think we all agree?),
and the new abilities to fix these from the UI means we won't need
to mark people as -1 to do so.
I didn't mention commit
On Wed, Jan 16, 2013 at 6:07 PM, Tim Starling tstarl...@wikimedia.org wrote:
On 17/01/13 00:14, Chad wrote:
Really, I think the whole thread is moot with the pending upgrade.
Typos should always be fixed before merging (I think we all agree?),
and the new abilities to fix these from the UI
Some examples to illustrate.
On 01/16/2013 02:25 PM, Quim Gil wrote:
Smaller activities and more frequent. Each one of them less ambitious
but more precise. Not requiring by default the involvement of developer
teams. Especially not requiring the involvement of WMF dev teams.
...
Imagine
On Wed, Jan 16, 2013 at 10:28 PM, Paul Selitskas p.selits...@gmail.com wrote:
Hi, I'm writing a new extension and would like to get some code reviewers
(even 1 would be fantastic).
May I have any assistance?
Extension: http://www.mediawiki.org/wiki/Extension:NamespaceRelations
Current
On 2013-01-16 7:20 PM, Chad innocentkil...@gmail.com wrote:
On Wed, Jan 16, 2013 at 6:07 PM, Tim Starling tstarl...@wikimedia.org
wrote:
On 17/01/13 00:14, Chad wrote:
Really, I think the whole thread is moot with the pending upgrade.
Typos should always be fixed before merging (I think we
If we're talking nitpicks in general. Ive seen -1 for things like
someFunc($a, $b) instead of someFunc( $a, $b ) which I agree does more harm
than good.
I disagree. The entire purpose of code review is to make sure the code is
organized and styled properly. If code isn't written in
51 matches
Mail list logo
