I think bot edits are most closely aligned with fully automated editing.
Perhaps semi-automated edit would work.
Pine
On Feb 12, 2015 10:34 AM, Marc A. Pelletier m...@uberbox.org wrote:
On 15-02-12 01:13 AM, Pine W wrote:
What would it take to implement a new tool edit flag userright
In
Hi does vendor have an api like the extension api which tells you name of the
extension and version. Because I have ask for WikiApriary to support vendor in
there tracking wiki site and they are asking for the api.
___
Wikitech-l mailing list
In general I'm in favor of more ad-hoc project-specific teams rather than
completely siloing every service to the Services group, or every mobile UI
to the Mobile group.=
Agreed, as long as everyone deploying services communicates through
services team so there is no duplication of solutions.
We
On 15-02-12 01:13 AM, Pine W wrote:
What would it take to implement a new tool edit flag userright
In the time-honored spirit of bikeshedding, I'd suggest that the right
name for this is automated edit rather than tool edit.
-- Marc
___
Bump.
On Monday, 9 February 2015, 19:34, Thomas Mulhall
thomasmulhall...@yahoo.com wrote:
Bump
On Monday, 9 February 2015, 19:34, Thomas Mulhall
thomasmulhall...@yahoo.com wrote:
Hi could I have some help to fix a problem that a user reported on the
extension talk
Bump.
On Thursday, 12 February 2015, 19:50, Thomas Mulhall
thomasmulhall...@yahoo.com wrote:
Hi does vendor have an api like the extension api which tells you name of the
extension and version. Because I have ask for WikiApriary to support vendor in
there tracking wiki site and
Bump.
On Tuesday, 10 February 2015, 14:02, Thomas Mulhall
thomasmulhall...@yahoo.com wrote:
Hi I am getting js script errors in Metrolook skin. The error is in
$(document).click(function(e) {
if (!$(e.target).closest('#'+openDiv).length) {
toggleDiv(openDiv);
}
});
and error
Thomas, just FYI, it is not good etiquette to Bump a thread,
especially on the same day,
and especially doing multiple threads at once.
(Some might even consider it to be very annoying, and/or spam-ish).
Instead, it is better to wait for at least a week for a reply (because many
devs only read
((Jump to the -- TL;DR -- if you just want to answer my question))
Hey guys, right now managing extensions is a complete mess for those of
us with a wiki running a dozens of extensions on a VPC.
Even if you use git to make things easier. You still need to batch
fetch/pull multiple git repos. And
I invite review of this preliminary proposal for a Google Summer of
Code project:
http://www.mediawiki.org/wiki/Accuracy_review
If you would like to co-mentor this project, please sign up. I've been
a GSoC mentor every year since 2010, and successfully mentored two
students in 2012 resulting in
In my opinion this is pretty easy to implement so to answer what
would it take: few hours of coding.
@Gerard: I would like to make this change to mediawiki core, so it
would work everywhere. Question now is:
* Do we want to implement tool edit?
* Do we want to use thing made by This that and
On 2/12/15, James Salsman jsals...@gmail.com wrote:
I invite review of this preliminary proposal for a Google Summer of
Code project:
http://www.mediawiki.org/wiki/Accuracy_review
If you would like to co-mentor this project, please sign up. I've been
a GSoC mentor every year since 2010, and
Hi Thomas,
i haven't installed your skin to see the error, because i think it's a
relatively easy thing you can track down by yourself. You give us 5 lines of
code where you think the error comes from (how have you tracked it down to
these 5 lines?). What, if you click on the error message in
On Wed, Feb 11, 2015 at 12:22 AM, David Gerard dger...@gmail.com wrote:
On 10 February 2015 at 23:19, Bryan Tong Minh bryan.tongm...@gmail.com
wrote:
In fact I would prefer to go to a less restrictive license, but that is
probably not worth the fight.
And is also infeasible. For a web
I do have a lot of respect towards the people who work on modularization
and librarizatin and vagrant and all that, but yes - I generally agree.
There's the API mailing list, and many emails on it are about breaking
changes, but it has relatively low traffic in general, so it's OK to mix
it.
Could you please tell me just if it's possible on wikimedia sites now? (Yes/No)
If yes, please tell me how.
On Thu, Feb 12, 2015 at 1:39 PM, Ricordisamoa
ricordisa...@openmailbox.org wrote:
The mechanism you described is controlled by $wgEnableScaryTranscluding
Hey folks,
I'd to modestly propose that we talk about managing/announcing breaking
changes to core MediaWiki architecture.
I want to have this chat because I spent an hour or two yesterday trying to
figure out why changing default configuration options for an extension in
MyExtension.php wasn't
OK Thanks
On Thu, Feb 12, 2015 at 1:43 PM, Quim Gil q...@wikimedia.org wrote:
On Thu, Feb 12, 2015 at 1:32 PM, Petr Bena benap...@gmail.com wrote:
Is it possible to use template from english wikipedia on a different
wiki (meta in this case)? Something like {{w:Template}}.
Not possible in
On Thu, Feb 12, 2015 at 1:32 PM, Petr Bena benap...@gmail.com wrote:
Is it possible to use template from english wikipedia on a different
wiki (meta in this case)? Something like {{w:Template}}.
Not possible in Wikimedia today.
See also
We need a common repository for Scribunto modules and
Hi,
Is it possible to use template from english wikipedia on a different
wiki (meta in this case)? Something like {{w:Template}}.
I couldn't find this anywhere. I don't want to export it, I want to be
able to change it on 1 wiki so that change gets everywhere else as
well.
The mechanism you described is controlled by $wgEnableScaryTranscluding
https://www.mediawiki.org/wiki/Manual:$wgEnableScaryTranscluding.
See https://phabricator.wikimedia.org/T52329 for a Wikimedia
implementation instead.
Il 12/02/2015 13:32, Petr Bena ha scritto:
Hi,
Is it possible to use
In addition to (even better than?) a breaking-changes list would be for
every piece of software we distribute to have a very prominent ChangeLog
(or RELEASE-NOTES) file, which is kept up to date. When you git pull and
see a change to ChangeLog, that should be a clue to check out whether you
need
There is the https://lists.wikimedia.org/mailman/listinfo/wikitech-announce
email list which perhaps could be used for emailing the weekly tech
newsletters and major changes.
Pine
On Feb 12, 2015 7:25 AM, C. Scott Ananian canan...@wikimedia.org wrote:
In addition to (even better than?) a
Regarding everyone loves JSON these days:
I truly, deeply, hate it.
On Thu, Feb 12, 2015 at 2:40 PM, Andrew Garrett agarr...@wikimedia.org wrote:
Hey folks,
I'd to modestly propose that we talk about managing/announcing breaking
changes to core MediaWiki architecture.
I want to have this
I don't think we need to announce every change that requires running
update.php-- that's pretty common, and (most importantly, imho) the
error messages you get when that happens make it pretty obvious what
you need to do.
But +1 for standardizing where breaking changes are announced. I hit
the
On Thu, Feb 12, 2015 at 6:08 PM, Chris Steipp cste...@wikimedia.org wrote:
* please fail in a way that tells the user what went wrong
This is my most important point.
I don't mind changing the code I write to conform to new (improved!) ways
of doing things. I think those who are writing
Please comment on
https://meta.wikimedia.org/wiki/Requests_for_comment/Abandoned_Labs_tools that
I created per https://phabricator.wikimedia.org/T87730 to create a process for
usurping or otherwise being added as a maintainer to existing tools which
appear to be abandoned. As Coren points
27 matches
Mail list logo
