Greetings,
I am pleased to announce that nominations are now being accepted for the
2015 Wikimedia Foundation Elections. This year the Board and the FDC Staff
are looking for a diverse set of candidates from regions and projects that
are traditionally under-represented on the board and in the
Thanks for your work on this, Chris.
Forwarding to Wikitech-l.
Pine
On Apr 20, 2015 4:58 PM, Chris Steipp cste...@wikimedia.org wrote:
On Apr 20, 2015 4:13 PM, Andrew Sherman asher...@wikimedia.org wrote:
Hello Everyone,
We just published Improving the security of our users on
In relation to
Engage with established technical communities at the Wikimedia Hackathon
2015
https://phabricator.wikimedia.org/T76325
Are there any specific developers of any related communities that you would
like to invite to Lyon? We can talk about travel sponsorship if it's
reasonable.
I
I still think that we should provide a simple API clients for JS, PHP, and
python. JS version should support both Browser node.js. The libs should
handle the most rudimentary API functioning like logins, warnings,
continuation, in the way that API devs feel is best, but nothing specific
to any
Is there a phab task for that.. ? :-)
On Mon, Apr 20, 2015 at 10:21 AM, Brad Jorsch (Anomie)
bjor...@wikimedia.org wrote:
On Mon, Apr 20, 2015 at 1:19 PM, Jon Robson jdlrob...@gmail.com wrote:
I use mw.api so I suspect that to handle deprecation notices - does it
not? If not why not?
It would help to surface api deprecation notices into the JavaScript
console just like mw.deprecate does for more visibility.
I haven't got time to review every single API response for every
request mobile makes and I'm keen to help you be able to iterate on
the API quicker...
Jon
On Fri, Apr
I use mw.api so I suspect that to handle deprecation notices - does it
not? If not why not?
Basically I think these notices need to show up in php warning logs /
js console to get the attention they deserve.
On Mon, Apr 20, 2015 at 10:14 AM, Brad Jorsch (Anomie)
bjor...@wikimedia.org wrote:
On
On Mon, Apr 20, 2015 at 12:57 PM, Jon Robson jdlrob...@gmail.com wrote:
It would help to surface api deprecation notices into the JavaScript
console just like mw.deprecate does for more visibility.
The API can and does already report deprecation warnings, and the way that
happens is on my
On Mon, Apr 20, 2015 at 1:19 PM, Jon Robson jdlrob...@gmail.com wrote:
I use mw.api so I suspect that to handle deprecation notices - does it
not? If not why not?
Because no one coded it for that framework yet?
--
Brad Jorsch (Anomie)
Software Engineer
Wikimedia Foundation
Hi Everyone,
I'd like to welcome Madhu to the Analytics team. We are very excited about
bringing her skills and experience to the team. She'll be based in San
Francisco and sitting with the Analytics team on the third floor.
In her own words:
I grew up in India, for most part in Chennai, and
It doesn't seem like anyone's mentioned it yet, but it would be even nicer
IMHO to not even worry about this class of problems by versioning the API
itself. This way, you can provide an explicit upgrade path for
actively-developed clients while keeping old versions around for legacy
clients. As
On Mon, Apr 20, 2015 at 11:49 AM, Brian Gerstle bgers...@wikimedia.org wrote:
It doesn't seem like anyone's mentioned it yet, but it would be even nicer
IMHO to not even worry about this class of problems by versioning the API
itself. This way, you can provide an explicit upgrade path for
12 matches
Mail list logo
