This is a follow-up to Rob's mail Wikidata change propogation. I feel that the
question of running periodic jobs on a large number of wikis is a more generic
one, and deserves a separate thread.
Here's what I think we need:
1) Only one process should be performing a given update job on a given
On Dec 28, 2012, at 5:05 AM, Matthew Flaschen mflasc...@wikimedia.org wrote:
We have all these JavaScript documentation comments, but we're not
actually generating docs. This has been talked about before, e.g.
http://www.gossamer-threads.com/lists/wiki/wikitech/208357?do=post_view_threaded,
Thanks Rob for starting the conversation about this.
I have explained our questions about how to run updates in the mail titled
Running periodic updates on a large number of wikis, because I feel that this
is a more general issue, and I'd like to decouple it a bit from the Wikidata
specifics.
On Fri, 04 Jan 2013 05:42:45 +0100, Lars Aronsson l...@aronsson.se wrote:
On 01/02/2013 06:11 PM, Matthew Flaschen wrote:
Every wiki has a different approach to bots. But for English Wikipedia,
that is not how the approval process
(https://en.wikipedia.org/wiki/Wikipedia:BOTAPPROVAL) works:
On the topic of whether allowing Tor users to edit is a concern, I believe
so. Because of Tor blocks, it is sometimes extremely difficult, or even
impossible altogether, to edit Wikipedia for some users. I believe we
should give these users the opportunity to contribute rather than have them
Would it be possible to adapt the Visual Editor to run under 1.19?
I have a couple of reasons for wanting that:
* 1.19 is our LTS release. Visual Editor looks awesome and I'd like to
provide people who are stuck on older versions of MediaWiki with a
persuasive reason to upgrade to 1.19 at
On 4 January 2013 17:02, Mark A. Hershberger m...@everybody.org wrote:
Is anyone else interested in helping to make this happen?
I have no coding ability but would LOVE this for our work 1.19
instances, and would be most pleased to test.
- d.
___
On Fri, Jan 4, 2013 at 10:04 AM, David Gerard dger...@gmail.com wrote:
On 4 January 2013 17:02, Mark A. Hershberger m...@everybody.org wrote:
Is anyone else interested in helping to make this happen?
I have no coding ability but would LOVE this for our work 1.19
instances, and would be
On 01/04/2013 09:02 AM, Mark A. Hershberger wrote:
There is a dependency on Parsoid and node.js, of course, that a
FCKeditor doesn't need, but I'm assuming right now that if MediaWiki
works with the extension, then the Parsoid instance will just run.
This should be the case. Parsoid only
On 01/04/2013 08:00 AM, Krinkle wrote:
Doxygen is indeed not meant for JavaScript. With some hacks it can be tricked
into reading comment blocks from javascript files, but that won't scale for
our code base, nor will it be enough to make a useful structure given the
dynamic way JavaScript
Am 04.01.2013 18:02, schrieb Mark A. Hershberger:
* FCKeditor is no longer supported for MediaWiki, but people are still
using it and, for some reason, like what it provides. If we can make
the Visual Editor available to them, I'm hoping the need for FCKeditor
will disappear.
Hi Mark,
and
On 01/04/2013 01:26 PM, Thomas Gries wrote:
I must warn users, because the FCKeditor as such has known security issues.
Even more reason for us to get VE working against 1.19. I saw that some
people have added instructions for FCKeditor on 1.19, but VE would be
much more compelling if we can
Am 04.01.2013 19:57, schrieb Mark A. Hershberger:
Even more reason for us to get VE working against 1.19. I saw that
some people have added instructions for FCKeditor on 1.19, but VE
would be much more compelling if we can get it working.
Yes!
Switching between MediaWiki Wiki syntax and the
I've sorted, linked, tagged, organized, and gardened our collection of QA
pages on mw.o to be more useful. Of course there is always more to do, so
comments, criticism, edits are welcome.
http://www.mediawiki.org/wiki/QA
-Chris
___
Wikitech-l mailing
On 11/21/2012 07:10 PM, Sumana Harihareswara wrote:
LevelUp is a mentorship program that will start in January 2013 and that
replaces the 20% time policy
https://www.mediawiki.org/wiki/Wikimedia_engineering_20%25_policy for
Wikimedia Foundation engineers. Technical contributors, volunteer or
On Fri, Jan 4, 2013 at 9:53 AM, Tyler Romeo tylerro...@gmail.com wrote:
[..]
As far as a solution goes, I have a complete codebase for
Extension:TokenAuth, which allows users to have MediaWiki sign a blinded
token, which can then be used to bypass a specific IP block in order to log
in and
On 4 January 2013 20:44, bawolff bawolff...@gmail.com wrote:
On Fri, Jan 4, 2013 at 9:53 AM, Tyler Romeo tylerro...@gmail.com wrote:
[..]
As far as a solution goes, I have a complete codebase for
Extension:TokenAuth, which allows users to have MediaWiki sign a blinded
token, which can
On Sat, Jan 5, 2013 at 4:27 AM, Risker risker...@gmail.com wrote:
Bawolff has it right, pretty much. For legitimate users, an IPBE can be
handed out. We have very limited human resources on the projects themselves
to address the issuing of tokens and IPBEs now.
For me, this is largely a
18 matches
Mail list logo
