[Wikitech-l] Nominations being accepted for 2015 Wikimedia Foundation elections
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 movement as well as candidates with experience in technology, product or finance. To this end they have published letters https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections_2015/Call_for_candidates describing what they think is needed and, recognizing that those who know the community the best are the community themselves, the election committee is accepting nominations https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections_2015#Information_for_nominators for community members you think should run and will reach out to those nominated to provide them with information about the job and the election process. This year, elections are being held for the following roles: *Board of Trustees* The Board of Trustees is the decision-making body that is ultimately responsible for the long term sustainability of the Foundation, so we value wide input into its selection. There are three positions being filled. More information about this role can be found at https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections_2015/Board_elections/2015. *Funds Dissemination Committee (FDC)* The Funds Dissemination Committee (FDC) makes recommendations about how to allocate Wikimedia movement funds to eligible entities. There are five positions being filled. More information about this role can be found at https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections_2015/FDC_elections/2015 . *Funds Dissemination Committee (FDC) Ombud* The FDC Ombud receives complaints and feedback about the FDC process, investigates complaints at the request of the Board of Trustees, and summarizes the investigations and feedback for the Board of Trustees on an annual basis. One position is being filled. More information about this role can be found at https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections_2015/FDC_Ombudsperson_elections/2015 . The candidacy submission phase lasts from 00:00 UTC April 20 to 23:59 UTC May 5 for the Board and from 00:00 UTCApril 20 to 23:59 UTC April 30 for the FDC and FDC Ombudsperson. This year, we are accepting both self-nominations and nominations of others. More information on this election and the nomination process can be found at https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections_2015. Please feel free to post a note about the election on your project's village pump. Any questions related to the election can be posted on the talk page on Meta, or sent to the election committee's mailing list, board-electi...@wikimedia.org On behalf of the Elections Committee, -Gregory Varnum (User:Varnent) Coordinator, 2015 Wikimedia Foundation Elections Committee ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Social-media] Improving the security of our users on Wikimedia sites
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 Wikimedia sites to the blog. URL: https://blog.wikimedia.org/2015/04/20/improving-security-for-our-users/ Thanks to Chris for writing and helping us edit this post. Below are some proposed social media messages. Tweak as needed. Twitter We teamed up with @iSECPartners and @OpenTechFund to assess the security of our sites. Check out the report here [link] FB/G+ We teamed up with iSEC Partners to assess the security of our sites and protect the privacy of our users. Their engineers developed attacks against the current version of MediaWiki to identify security flaws, in a new report sponsored by the Open Technology Fund. [link] Maybe just MediaWiki instead of the current version of MediaWiki, since we did a release to specifically fix issues that they found. Might confuse some people as is. Thanks, -- Andrew Sherman Digital Communications | Wikimedia Foundation E: asher...@wikimedia.org WMF: ASherman (WMF) ___ Social-media mailing list social-me...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/social-media ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Inviting developers from other communities to the Wikimedia Hackathon
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 have asked directly to the owners of the main areas of the event [1] in the related tasks. If you have good proposals in relation to other projects planned, please share them as well at https://phabricator.wikimedia.org/T76325 The sooner the better, since there is not much time left. [1] https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2015#Main_areas -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Reminder: Breaking change to API continuation planned for 1.26
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 of the modules (e.g. it should not have a separate function to get a list of all pages). On Mon, Apr 20, 2015 at 8:38 PM, Jon Robson jdlrob...@gmail.com wrote: 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? Because no one coded it for that framework yet? -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Jon Robson * http://jonrobson.me.uk * https://www.facebook.com/jonrobson * @rakugojon ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Reminder: Breaking change to API continuation planned for 1.26
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? Because no one coded it for that framework yet? -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Jon Robson * http://jonrobson.me.uk * https://www.facebook.com/jonrobson * @rakugojon ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Reminder: Breaking change to API continuation planned for 1.26
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 17, 2015 at 7:58 AM, Brad Jorsch (Anomie) bjor...@wikimedia.org wrote: Previous announcement: https://lists.wikimedia.org/pipermail/mediawiki-api-announce/2014-September/69.html During the 1.25 development cycle, the API has been warning you if you're specifying neither the continue nor rawcontinue parameters to action=query. Recently this warning was targeted more specifically to queries that actually return continuation data. The time is coming soon for making this change, so please check your bots, bot frameworks, scripts, and so on to ensure that you won't be broken when this change is made. If you want to continue using your existing continuation code unchanged, all you need to do is add the rawcontinue parameter to your action=query queries. If you'd rather change to the easier-to-get-right new style, add an empty continue parameter to your initial action=query queries. See https://www.mediawiki.org/wiki/API:Query#Continuing_queries for details on the new mechanism. If you do nothing, sometime in the next few months your code will likely start thinking that no queries ever need continuation when the default is changed to return the new 'continue' node rather than the old 'query-continue'. I'll send an announcement when the specific date is decided, but I don't promise more than a week's notice. -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Jon Robson * http://jonrobson.me.uk * https://www.facebook.com/jonrobson * @rakugojon ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Reminder: Breaking change to API continuation planned for 1.26
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 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 long list of stuff to improve. And it can log on the server too (see api-feature-usage.log on fluorine). And once logstash gets working it'll even be externally queryable by user agent. But like mw.deprecate doesn't make sense any further than that. It's up to your API-accessing code (e.g. whatever framework you're using to query the API) to log the warnings it receives in some manner you'd find useful. -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Jon Robson * http://jonrobson.me.uk * https://www.facebook.com/jonrobson * @rakugojon ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Reminder: Breaking change to API continuation planned for 1.26
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 long list of stuff to improve. And it can log on the server too (see api-feature-usage.log on fluorine). And once logstash gets working it'll even be externally queryable by user agent. But like mw.deprecate doesn't make sense any further than that. It's up to your API-accessing code (e.g. whatever framework you're using to query the API) to log the warnings it receives in some manner you'd find useful. -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Reminder: Breaking change to API continuation planned for 1.26
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 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Welcome Madhu Viswanathan
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 finished my undergrad in IT 3 years back. I was always into computers and programming but had not had much exposure. During college I met the legendary Yuvi Panda and other folks in the Chennai Geek community, who introduced me to linux, open source software, the Google Summer of Code program and got me started. I started by participating the GSoC program for Gnome, moved on to work for a company in the US, remote, for 2 years. I spent all my free time learning Python, doing hobby projects, organizing hackathons, meetups in the tech community in my city, etc. Last year, I quit to go to Hacker School in New York, which I did twice! Post Hacker School, I started looking for work, applied to the foundation, and 7 interviews and 3 months of visa wait later, here I am :) Super excited to be here! Welcome Madhu! -Toby ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Reminder: Breaking change to API continuation planned for 1.26
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 a result, marking an old (or previously deprecated) API (version) obsolete will only effect clients who haven't upgraded to the new version. On Mon, Apr 20, 2015 at 1:51 PM, Yuri Astrakhan yastrak...@wikimedia.org wrote: 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 of the modules (e.g. it should not have a separate function to get a list of all pages). On Mon, Apr 20, 2015 at 8:38 PM, Jon Robson jdlrob...@gmail.com wrote: 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? Because no one coded it for that framework yet? -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Jon Robson * http://jonrobson.me.uk * https://www.facebook.com/jonrobson * @rakugojon ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- EN Wikipedia user page: https://en.wikipedia.org/wiki/User:Brian.gerstle IRC: bgerstle ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Reminder: Breaking change to API continuation planned for 1.26
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 actively-developed clients while keeping old versions around for legacy clients. As a result, marking an old (or previously deprecated) API (version) obsolete will only effect clients who haven't upgraded to the new version. Hmppf You're not alone - https://phabricator.wikimedia.org/T41592 (this bug was closed as declined) On Mon, Apr 20, 2015 at 1:51 PM, Yuri Astrakhan yastrak...@wikimedia.org wrote: 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 of the modules (e.g. it should not have a separate function to get a list of all pages). On Mon, Apr 20, 2015 at 8:38 PM, Jon Robson jdlrob...@gmail.com wrote: 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? Because no one coded it for that framework yet? -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Jon Robson * http://jonrobson.me.uk * https://www.facebook.com/jonrobson * @rakugojon ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- EN Wikipedia user page: https://en.wikipedia.org/wiki/User:Brian.gerstle IRC: bgerstle ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Jon Robson * http://jonrobson.me.uk * https://www.facebook.com/jonrobson * @rakugojon ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
