Hi!
I access as a system root.
I have loaded 1.23 in /wiki
I have symlinked it in my /home/wiki-site/www directories. It works
without problem. However, when I try
> "php maintenance/sqlite.php (or other .php files) --conf
/home/wiki-site/www/LocalSettings.php (or without this -conf addition)
I get the same response:
Warning: require_once(__DIR__/Maintenance.php): failed to open
stream: No such file or directory in /wiki/maintenance/sqlite.php on line 24
Fatal error: require_once(): Failed opening required
'__DIR__/Maintenance.php' (include_path='.:/usr/local/php5/lib/php')
in /wiki/maintenance/sqlite.php on line 24
-
I also installed some wikis without sysmlink.
I such a case if I enter
> php maintenance/dumpBackup.php --full > xxxx.xml
I get:
Access denied for user 'root'@'localhost' (using password: NO)
The same if I enter
> php maintenance/dumpBackup.php --dbuser user --dbpass
pass --full > xxxx.xml
Thank you for the help.
jefsey
While dragging a little bit into canvas, I successfully upload into a
canvas a cropped clip of the image of a djvu page into it.source, just to
crash into a DOM exception "The canvas has been tainted by cross-origin
data" while attempting do access to pixel data with both getImageData()
and toDataURL() methods.
Again, it seems a CORS issue.
Am I wrong? Is there some doc about this issue?
Alex brollo
If you want to propose a session for the main room of the MediaWiki
Developer Summit, then make sure it is fit to compete for a slot at
https://phabricator.wikimedia.org/T85632
RobLa and I are coordinating this exercise and we want to have the main
room fully pre-scheduled by the end of next Monday, Jan 12.
The rest of the schedule is open, meaning that anybody can book a slot as
long as it is available.
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Just a note to say that on January 1 a first Phabricator monthly statistics
report was generated. If you want to improve it, suggestions are welcome at
https://phabricator.wikimedia.org/T1003 or in a new task.
Now we need a way to store and visualize this data, a topic that is being
discussed at https://phabricator.wikimedia.org/T28
---------- Forwarded message ----------
From: <communitymetrics(a)wikimedia.org>
Date: Thu, Jan 1, 2015 at 1:00 AM
Subject: Phabricator monthly statistics - 2014-12
To: communitymetrics(a)wikimedia.org
Hi Community Metrics team,
this is your automatic monthly Phabricator statistics mail.
Number of accounts created in (2014-12): 395
Number of active users (any activity) in (2014-12): 619
Number of task authors in (2014-12): 384
Number of users who have closed tasks in (2014-12): 213
Number of tasks created in (2014-12): 3424
Number of tasks closed in (2014-12): 2529
Number of tasks in the shell project closed as resolved,fixed in (2014-12):
12
Number of open and stalled tasks in total: 18125
Median age in days of open tasks by priority:
Unbreak now: 115
Needs Triage: 147
High: 199
Normal: 437
Low: 686
Needs Volunteer: 536
TODO: Numbers which refer to closed tasks might not be correct, as
described in T1003.
Yours sincerely,
Fab Rick Aytor
(via community_metrics.sh on iridium at Thu Jan 1 00:00:05 UTC 2015)
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hello,
Huggle is an open source anti-vandalism tool for MediaWiki based
sites. See https://en.wikipedia.org/wiki/Wikipedia:Huggle for more.
We are in desperate need for more release managers - eg. people who
manage releases of huggle for following platforms:
* MS Windows (currently getting all stable releases and even some beta
releases) - more beta releases needed
* MacOS (currently getting some stable releases only) - stable and
beta releases needed
* Linux Ubuntu (currently getting all stable releases) - beta releases needed
* Linux Debian (currently not getting any releases) - both needed
Nightly builds for all platforms would be cool. (I can do that for
ubuntu only right now, using wikimedia labs).
Requirements:
* Heavily trusted thorough wikimedia project (release managers make
binary packages of huggle which are then installed on hundreds of
computers by our users - we need to make sure they will not contain
any viruses, malware or corrupt builds that would compromise
credentials of users).
* Intermediate knowledge of programming
* Ability to compile C++ source code for one or more of those platforms
* Ability to create standard packages for one or more of those
platforms (NSI for windows, DMG for MacOS, DEB for linux)
* Intermediate knowledge of git
If you meet those ^ and want to help us with the development of
huggle, please let us know! For beginning you would be responsible for
packaging of beta versions, so there is not much to break :) so if you
don't feel confident in any of required areas, don't worry.
NOTE: Huggle is open source project - we are all volunteers and this
is not a job offer for a paid position. So please, don't send me CV's
etc (it actually happened once to me when I sent a similar mail in
past). If you would like to help us with this task - just reply to
this thread, or send me a private mail.
Many thanks on behalf of huggle team :)
A draft version of the MediaWiki Developer Summit 2015 (San Francisco,
January 26-27) is available at
https://www.mediawiki.org/wiki/MediaWiki_Developer_Summit_2015#Schedule
You will see some slots pre-scheduled for three main topics: Mobile,
Editing, and Service Oriented Architecture. There are some pre-scheduled
sessions proposed by the Architecture Committee and the Product team, plus
the opening and wrap-up sessions.
There are many slots available, and at this point almost everything is
flexible and negotiable. To book your session, check
https://www.mediawiki.org/wiki/MediaWiki_Developer_Summit_2015#How_to_sched…
As an experiment, we are linking all sessions to a corresponding
Phabricator task. The goal is to ease documentation and discussion before
and after the summit, linking each session to related tasks and projects.
This is also a way to add the preparation of the session to your personal
and team backlogs.
Allocate time to prepare your sessions, and encourage discussion and
collaboration before and after the event. Let's make the most out of this
unique MediaWiki gathering!
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
In the next RFC meeting we would like to discuss the following RFC:
* Hierator
<https://www.mediawiki.org/wiki/Requests_for_comment/Hierator>
The meeting will be on the IRC channel #wikimedia-office on
irc.freenode.org at the following time:
* UTC: Wednesday 21:00
* US PST: Wednesday 13:00
* Europe CET: Wednesday 22:00
* Australia AEDT: Thursday 08:00
-- Tim Starling
If you missed the talk and would like to view the recording, here is the
link: *https://www.youtube.com/watch?v=hz__duVeaWY
<https://www.youtube.com/watch?v=hz__duVeaWY>*
It has been released under a creative commons license.
If you have any questions about API Client Libraries please feel free to
get in touch with Frances *fhocutt(a)wikimedia.org <fhocutt(a)wikimedia.org> *
You can check out past tech talk recordings at the MediaWiki YouTube page
here: http://www.youtube.com/channel/UCg4wlhlN8RjP6_e_vMC4CTA
If you have an idea for a future tech talk that you would like to nominate
(or see what we have coming up), please add your suggestions here:
https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event/Te…
Please feel free to email me with your ideas as well. :)
On Tue, Jan 6, 2015 at 9:35 AM, Rachel Farrand <rfarrand(a)wikimedia.org>
wrote:
> This Tech Talk will be starting in 55 min!
>
> On Tue, Dec 16, 2014 at 5:47 PM, Rachel Farrand <rfarrand(a)wikimedia.org>
> wrote:
>
>> Please join us for the following tech talk:
>>
>> *Tech Talk**:* A developer's-eye view of API client libraries: how to
>> choose them, how to make them, how to make them better
>> *Presenter:* Frances Hocutt
>> *Date:* January 6
>> *Time:* 1830 UTC
>> <http://www.timeanddate.com/worldclock/fixedtime.html?msg=tech+talk%3A+API+c…>
>> Link to live YouTube stream <http://www.youtube.com/watch?v=hz__duVeaWY>
>> *IRC channel for questions/discussion:* #wikimedia-office
>> Google+ page
>> <https://plus.google.com/u/0/b/103470172168784626509/events/c8fnclmkeam2gbrn…>, another
>> place for questions
>>
>> *Talk description: *This talk will cover why developers do (and don't)
>> use any of the
>> wide variety of client libraries available to get and post data
>> through the MediaWiki API. We'll talk about writing tools with an eye
>> to developer experience, go through the "gold standard" for MediaWiki
>> API client libraries
>> (https://www.mediawiki.org/wiki/API:Client_code/Gold_standard) and the
>> thinking behind it, and share some of the resources available for both
>> library writers and library users.
>>
>> If you write or maintain an API client library, you'll learn about
>> what you can do to help your library get out of the way and let
>> developers who work with it spend their mental energy on putting
>> together exciting projects, not on fighting with tools. If you work
>> with the MediaWiki API (write bots, do research, maintain wikis),
>> you'll learn what to consider when you're choosing a framework for
>> your project. Either way, you'll start to appreciate all the factors
>> beyond a library's code that make the difference between fun and easy
>> development and a frustrating slog.
>>
>
>