Re: [Wikitech-l] How to serve up subtitles
That has been discussed since 2012 at https://phabricator.wikimedia.org/T44790 Use language code subpages for subtitles to allow Translate extension usage. Enabling translation of subtitles via the Translate extension would be a huge boon. On Tue, Aug 18, 2015 at 2:18 AM, Derk-Jan Hartman d.j.hartman+wmf...@gmail.com wrote: Well we already have a namespace of course, and indeed I was already considering converting that to a ContentModel. The only thing that is somewhat problematic here is the multiple languages problem. Currently each language get it's own page and title. Do we switch the model to host all subtitles in the same 'page' ? That will require a lot of UI and flags etc. Current system: https://commons.wikimedia.org/wiki/File:Folgers.ogv https://commons.wikimedia.org/wiki/TimedText:Folgers.ogv https://commons.wikimedia.org/wiki/TimedText:Folgers.ogv.en.srt https://commons.wikimedia.org/wiki/TimedText:Folgers.ogv.de.srt DJ On Tue, Aug 18, 2015 at 9:04 AM, Ori Livneh o...@wikimedia.org wrote: On Mon, Aug 17, 2015 at 5:56 AM, Derk-Jan Hartman d.j.hartman+wmf...@gmail.com wrote: As part of Brion's and mine struggle for better A/V support on Wikipedia, I have concluded that our current support for subtitles is rather... improvised. Currently all our SRT files are referenced from HTML using action=raw. But then not actually used from action=raw, but instead served up as semi html using api.php. Which is ridiculous... If we want to move to more HTML5 compliancy, we also will want to switch from the SRT format to the VTT format. Ideally, I want to host multiple subtitle formats, and dynamically serve/convert them as either SRT or VTT. These can be directly referenced from a track element so that we are fully compatible. The question is now, how to best do this. The endpoint needs to be dynamic, cacheable, allow multiple content types etc. Ideas suggested have been: * Api.php * Restbase * New endpoint * ResourceLoader modules I'm listing the current problems, future requirements and discussing several ideas at: https://www.mediawiki.org/wiki/Extension:TimedMediaHandler/TimedTextRework?veaction=edit If you have any ideas or remarks, please contribute them ! I propose adding an additional associated namespace (like Talk:), except for subtitles. The namespace will be associated with File pages which represent videos, and it will be coupled to a ContentHandler class representing subtitle content. The ContentHandler class will be a natural place for validation logic and the specification of an alternate editing interface suitable for editing subtitles. ___ 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 -- Tilman Bayer Senior Analyst Wikimedia Foundation IRC (Freenode): HaeB ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Code of conduct committee
Hi, On Fri, Aug 21, 2015 at 11:49 AM, Steinsplitter Wiki steinsplitter-w...@live.com wrote: Some thoughts about https://www.mediawiki.org/wiki/Code_of_conduct_for_technical_spaces/Draft * I can't see community consensus (RFC) for this. This page is currently a draft. It is not ready yet for a wide call for comments. I'm not even sure that the RfC process is the right one for this. It is open for discussion. I just posted https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Next_steps * I see a lot (maybe 70%) staffer edits there. I also would like to see more edits from volunteers and other affiliations. Please jump in! Most WMF employees drafting and discussing there are doing so out of their personal interest, with no WMF directive and most likely on their own time. I'm basically the only exception. * It is complicated to understand the policy. This new draft is based on an existing Contributor Covenant used already by several free software projects. See https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Rewrite_based_on_Contributor_Covenant.3F We keep working on it, and you are welcome to join with ideas and edits. I have the feeling that only a few staffer building this. Please don't forget to involve the community! See above. The base text has been forked from an external effort shared by many projects. The page is open to edits and comments from anybody. The initiative has been announced and discussed here and in other channels. There is a proposal to offer an email alias to people willing to give feedback but preferring to do it privately. As you see, we are trying to get feedback from a wide variety of profiles. What else can we do to get more people involved? How you like to enforce this policy on irc? In the most effective way. :) What is your question, exactly? There is a lengthy discussion at https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#IRC What is the committee? A WMF super arbcom? We are discussing the committee right now. It's not a simple question. It needs to be staffed by people willing to be in that role, it needs to have community trust, and it needs to be effective. Your ideas are welcome. See https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Membership_of_the_committee_and_ECT.27s_role Moor transparency would be great, and to write it in simple english so that non native speakers can get involved. This exercise can be hardly more transparent. The fact that you can find so many open questions, some areas of dense language, and still not so many participants as we all would wish is due precisely to the fact that those interested are working openly in a pure wiki style since edit 1, and in fact since T87773. As a non-native English speaker myself, I'm also interested in making the text simpler and clearer for everybody. This becomes easier as soon as paragraphs enter testing or stable. Some areas are still in unstable and even experimental. :) Best and with concerns, Please keep converting your concerns into more feedback. Thank you! There is some discussion now about how the Code of Conduct Committee should be formed. See: * https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Membership_of_the_committee_and_ECT.27s_role and * https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Another_membership_proposal -- 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] Code of conduct committee
On 21 August 2015 at 06:43, Quim Gil q...@wikimedia.org wrote: Hi, On Fri, Aug 21, 2015 at 11:49 AM, Steinsplitter Wiki steinsplitter-w...@live.com wrote: Some thoughts about https://www.mediawiki.org/wiki/Code_of_conduct_for_technical_spaces/Draft * I can't see community consensus (RFC) for this. This page is currently a draft. It is not ready yet for a wide call for comments. I'm not even sure that the RfC process is the right one for this. It is open for discussion. I just posted https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Next_steps * I see a lot (maybe 70%) staffer edits there. I also would like to see more edits from volunteers and other affiliations. Please jump in! Most WMF employees drafting and discussing there are doing so out of their personal interest, with no WMF directive and most likely on their own time. I'm basically the only exception. Speaking as a WMF employee who is involved in the discussion, this is my personal opinion - hence my choice of accounts to comment with. I suspect that WMF employees probably make up a big proportion of the technical community itself (something this proposal will hopefully help change!) and so large amounts of WMF participation is not surprising. * It is complicated to understand the policy. This new draft is based on an existing Contributor Covenant used already by several free software projects. See https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Rewrite_based_on_Contributor_Covenant.3F We keep working on it, and you are welcome to join with ideas and edits. I have the feeling that only a few staffer building this. Please don't forget to involve the community! See above. The base text has been forked from an external effort shared by many projects. The page is open to edits and comments from anybody. The initiative has been announced and discussed here and in other channels. There is a proposal to offer an email alias to people willing to give feedback but preferring to do it privately. As you see, we are trying to get feedback from a wide variety of profiles. What else can we do to get more people involved? How you like to enforce this policy on irc? In the most effective way. :) What is your question, exactly? There is a lengthy discussion at https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#IRC What is the committee? A WMF super arbcom? We are discussing the committee right now. It's not a simple question. It needs to be staffed by people willing to be in that role, it needs to have community trust, and it needs to be effective. Your ideas are welcome. See https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Membership_of_the_committee_and_ECT.27s_role Moor transparency would be great, and to write it in simple english so that non native speakers can get involved. This exercise can be hardly more transparent. The fact that you can find so many open questions, some areas of dense language, and still not so many participants as we all would wish is due precisely to the fact that those interested are working openly in a pure wiki style since edit 1, and in fact since T87773. As a non-native English speaker myself, I'm also interested in making the text simpler and clearer for everybody. This becomes easier as soon as paragraphs enter testing or stable. Some areas are still in unstable and even experimental. :) Best and with concerns, Please keep converting your concerns into more feedback. Thank you! There is some discussion now about how the Code of Conduct Committee should be formed. See: * https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Membership_of_the_committee_and_ECT.27s_role and * https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Another_membership_proposal -- 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 -- Oliver Keyes Count Logula Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Page Curation for other wikis
Does Wikidata contain detailed information on the policies that apply, the categories of deletion available and the conditions under which deletion can be used in various categories? On 21 August 2015 at 10:50, Amir Ladsgroup ladsgr...@gmail.com wrote: Hmm, But since we have Wikidata now, Is it easier to do? For example catching notability template from Wikidata instead of hard-coding it make things easier. Best On Fri, Aug 21, 2015 at 7:10 PM Oliver Keyes oke...@wikimedia.org wrote: Adding localisation in the languages sense is not the blocker, here; the blocker is localising it to /each project/. The extension would need to be restructured to allow this and then rewritten for each wiki - that's a pretty big task. On 21 August 2015 at 05:56, Amir Ladsgroup ladsgr...@gmail.com wrote: I found this bug: https://phabricator.wikimedia.org/T50552 But it has lowest priority. Why? On Fri, Aug 21, 2015 at 1:10 PM jay...@gmail.com wrote: This could be a good GSoC project. On Fri, 21 Aug 2015 18:08 Amir Ladsgroup ladsgr...@gmail.com wrote: Hey, Page Curation [1][2][3] is a project funded by WMF but strangely the product is only available for English Wikipedia. This is surprising because this tool is useful for all Wikis and I don't think i18n would be very hard. Is there any plans to add i18n and rolling it out in other languages? If it's not funded anymore, Is anyone willing to help as volunteer to work? [1] https://en.wikipedia.org/wiki/Wikipedia:Page_Curation [2] https://www.mediawiki.org/wiki/Page_Curation [3] https://www.mediawiki.org/wiki/Extension:PageTriage Best ___ 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 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Oliver Keyes Count Logula Wikimedia Foundation ___ 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 -- Oliver Keyes Count Logula Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Page Curation for other wikis
Adding localisation in the languages sense is not the blocker, here; the blocker is localising it to /each project/. The extension would need to be restructured to allow this and then rewritten for each wiki - that's a pretty big task. On 21 August 2015 at 05:56, Amir Ladsgroup ladsgr...@gmail.com wrote: I found this bug: https://phabricator.wikimedia.org/T50552 But it has lowest priority. Why? On Fri, Aug 21, 2015 at 1:10 PM jay...@gmail.com wrote: This could be a good GSoC project. On Fri, 21 Aug 2015 18:08 Amir Ladsgroup ladsgr...@gmail.com wrote: Hey, Page Curation [1][2][3] is a project funded by WMF but strangely the product is only available for English Wikipedia. This is surprising because this tool is useful for all Wikis and I don't think i18n would be very hard. Is there any plans to add i18n and rolling it out in other languages? If it's not funded anymore, Is anyone willing to help as volunteer to work? [1] https://en.wikipedia.org/wiki/Wikipedia:Page_Curation [2] https://www.mediawiki.org/wiki/Page_Curation [3] https://www.mediawiki.org/wiki/Extension:PageTriage Best ___ 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 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Oliver Keyes Count Logula Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Page Curation for other wikis
Hmm, But since we have Wikidata now, Is it easier to do? For example catching notability template from Wikidata instead of hard-coding it make things easier. Best On Fri, Aug 21, 2015 at 7:10 PM Oliver Keyes oke...@wikimedia.org wrote: Adding localisation in the languages sense is not the blocker, here; the blocker is localising it to /each project/. The extension would need to be restructured to allow this and then rewritten for each wiki - that's a pretty big task. On 21 August 2015 at 05:56, Amir Ladsgroup ladsgr...@gmail.com wrote: I found this bug: https://phabricator.wikimedia.org/T50552 But it has lowest priority. Why? On Fri, Aug 21, 2015 at 1:10 PM jay...@gmail.com wrote: This could be a good GSoC project. On Fri, 21 Aug 2015 18:08 Amir Ladsgroup ladsgr...@gmail.com wrote: Hey, Page Curation [1][2][3] is a project funded by WMF but strangely the product is only available for English Wikipedia. This is surprising because this tool is useful for all Wikis and I don't think i18n would be very hard. Is there any plans to add i18n and rolling it out in other languages? If it's not funded anymore, Is anyone willing to help as volunteer to work? [1] https://en.wikipedia.org/wiki/Wikipedia:Page_Curation [2] https://www.mediawiki.org/wiki/Page_Curation [3] https://www.mediawiki.org/wiki/Extension:PageTriage Best ___ 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 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Oliver Keyes Count Logula Wikimedia Foundation ___ 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
[Wikitech-l] [Announcement] SQLite storage in RESTBase now available
TL;DR: Getting started with RESTBase is now easier thanks to a new SQLite3 backend Hello, The WMF Services team~[0] is proud to announce the initial release of the SQLite storage back-end~[1] for RESTBase~[2], the service that powers Wikimedia projects’ public REST API~[3]. Traditionally, RESTBase was limited to Cassandra persistence, which, while scalable, presented a weighty and difficult dependency for smaller installations and test environments. This new module allows RESTBase administrators to replace Cassandra with a lightweight, file-based persistence based on SQLite. This is an exciting milestone in RESTBase’s development. We expect the option to run RESTBase atop an SQLite database to significantly widen the target audience, allowing users with small installations and limited resources to take advantage of this valuable service. We are also hoping to attract more contributors by having a simpler, less resource-intensive alternative to Cassandra; SQLite is now the storage module of choice in MediaWiki-Vagrant~[6] installations with the restbase role enabled. Contributing is just a vagrant up away! The abstract storage interface~[7] we developed for RESTBase allows users to seamlessly switch between storage back-ends (Cassandra or SQLite). Due to data volumes we are facing in WMF, we are not using the SQLite back-end in production. However, we are testing each RESTBase changeset against both Cassandra and SQLite to ensure they are behaving as expected. Additionally, a 93% code coverage makes us confident to recommend it for production use. Bringing the SQLite storage module to a usable state represents a significant amount of team effort, but nevertheless we’d like to extend a special thank you to Petr Pchelko for his tireless efforts in driving this project home. Thanks Petr! This is only the first step in providing better third-party and developer support. One of the next challenges will be basing Parsoid~[8] on service-runner~[9,10], a general-purpose library for running and managing Node.JS services. Amongst other things, it enables bundling and running multiple services together. Packaging and distributing Parsoid and RESTBase together will simplify their installation, configuration and administration in small-setup and development environments. Best, Marko Obrovac, PhD Senior Services Engineer Wikimedia Foundation [0] https://www.mediawiki.org/wiki/Wikimedia_Services [1] https://github.com/wikimedia/restbase-mod-table-sqlite [2] https://www.mediawiki.org/wiki/RESTBase [3] https://en.wikipedia.org/api/rest_v1/?doc (for a complete list of supported domains go to https://rest.wikimedia.org/) [4] https://phabricator.wikimedia.org/tag/restbase/ [5] https://phabricator.wikimedia.org/tag/restbase-api/ [6] https://www.mediawiki.org/wiki/MediaWiki-Vagrant [7] https://github.com/wikimedia/restbase-mod-table-spec [8] https://www.mediawiki.org/wiki/Parsoid [9] https://github.com/wikimedia/service-runner [10] https://phabricator.wikimedia.org/T90668 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Page Curation for other wikis
As Oliver said, the only reason PageTriage isn't available for every language is because, like Twinkle, it is closely tied to wiki-specific workflows and templates. Our original plan with PageTriage was to make it configurable on-wiki and get volunteers to configure it for each wiki. The extension was architected with this in mind, and indeed, it is possible to configure much of it on-wiki already (although this isn't documented). Unfortunately, the engineers that were working on PageTriage (myself and Benny) were reassigned to build the Echo extension and never had time to finish the on-wiki configuration pieces. I don't have time to elaborate in this email, but I honestly think it would only take a few weeks of work to make PageTriage fully localizable to each wiki. I would really love to see the community request that the Community Tech team work on this as part of the upcoming Community Wishlist Survey ( https://www.mediawiki.org/wiki/Community_Tech_team/Community_Wishlist_Survey ). On Fri, Aug 21, 2015 at 8:03 AM, James Forrester jforres...@wikimedia.org wrote: On 21 August 2015 at 01:04, Amir Ladsgroup ladsgr...@gmail.com wrote: Hey, Page Curation [1][2][3] is a project funded by WMF Was. There have been no substantial commits to it since April 2013. [Snip] If it's not funded anymore, Is anyone willing to help as volunteer to work? If someone really wanted to work on it, we'd of course be happy to give some advice, but as Oliver points out, the code is built around a single wiki's way of working and generalising it probably isn't going to be very easy. It might be substantially easier and more efficient to consider how to build a new tool that could replace it and yet be configured by the community of each wiki on which it would be deployed. J. -- James D. Forrester Lead Product Manager, Editing Wikimedia Foundation, Inc. jforres...@wikimedia.org | @jdforrester ___ 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] Page Curation for other wikis
On 21 August 2015 at 01:04, Amir Ladsgroup ladsgr...@gmail.com wrote: Hey, Page Curation [1][2][3] is a project funded by WMF Was. There have been no substantial commits to it since April 2013. [Snip] If it's not funded anymore, Is anyone willing to help as volunteer to work? If someone really wanted to work on it, we'd of course be happy to give some advice, but as Oliver points out, the code is built around a single wiki's way of working and generalising it probably isn't going to be very easy. It might be substantially easier and more efficient to consider how to build a new tool that could replace it and yet be configured by the community of each wiki on which it would be deployed. J. -- James D. Forrester Lead Product Manager, Editing Wikimedia Foundation, Inc. jforres...@wikimedia.org | @jdforrester ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Tech Talk: ELK: Elasticsearch, Logstash and Kibana at Wikimedia
If you missed yesterday's talk and would like to view the recording, here is the link: https://www.youtube.com/watch?v=3VA3Zi1De6w It has been released under a creative commons license. Here is a link to the slides used in the presentation. https://commons.wikimedia.org/wiki/File:ELK_Tech_Talk_2015-08-20.pdf If you have any questions about today's talk please get in touch with Bryan Davis bd...@wikimedia.org ksm...@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 one, please add your suggestions here: https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event/TechTalks On Thu, Aug 20, 2015 at 9:29 AM, Rachel Farrand rfarr...@wikimedia.org wrote: Reminder: This tech talk starts in 1 hour! On Mon, Aug 10, 2015 at 12:47 PM, Rachel Farrand rfarr...@wikimedia.org wrote: Please join for the following tech talk: *Tech Talk**:* ELK: Elasticsearch, Logstash and Kibana at Wikimedia *Presenter:* Bryan Davis *Date:* August 20, 2015 *Time: *17:30 UTC http://www.timeanddate.com/worldclock/fixedtime.html?msg=Tech+Talk%3A+logstash%2Fkibanaiso=20150820T1730p1=1440ah=1 Link to live YouTube stream http://www.youtube.com/watch?v=3VA3Zi1De6w *IRC channel for questions/discussion:* #wikimedia-office Google+ page https://plus.google.com/u/0/b/103470172168784626509/events/coiq7cvuu5d5mih08pchc49rhpg, another place for questions *Summary: *Overview of the debug log collection and reporting infrastructure available on the WMF beta and production clusters. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Tech Talk: Let's talk about web performance: August 18th
If you missed Monday's talk and would like to view the recording, here is the link: *https://www.youtube.com/watch?v=acZ3SwbhsaM https://www.youtube.com/watch?v=acZ3SwbhsaM* It has been released under a creative commons license. If you have any questions about today's talk please get in touch with Peter Hedenskog pe...@wikimedia.org ksm...@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 one, please add your suggestions here: https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event/TechTalks On Mon, Aug 17, 2015 at 5:05 PM, Rachel Farrand rfarr...@wikimedia.org wrote: Remember: this tech talk is tomorrow. Hope you can join! On Mon, Aug 10, 2015 at 3:51 PM, Rachel Farrand rfarr...@wikimedia.org wrote: Please join for the following tech talk: *Tech Talk**:* Let's talk about web performance *Presenter:* Peter Hedenskog *Date:* August 18, 2015 *Time: *19:00 UTC http://www.timeanddate.com/worldclock/fixedtime.html?msg=Tech+Talk%3A+Let%27s+talk+about+web+performanceiso=20150818T19p1=%3Aah=1 Link to live YouTube stream http://www.youtube.com/watch?v=acZ3SwbhsaM *IRC channel for questions/discussion:* #wikimedia-office Google+ page https://plus.google.com/u/0/b/103470172168784626509/events/c8dmvqt3n4mjn3f787ikufruav0, another place for questions *Summary: * We want our pages to be fast but how do we know they are? Today I’ll go through the latest trends about what makes pages really super fast for the user and ways of measuring and really knowing they are. I'll talk about these things: - How the browser render and show the page for the user - What makes a web page fast and what tricks do people use? - Measuring: why, when and how? ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Issue with Gadget dependencies and ResourceLoader
On Fri, 21 Aug 2015 04:46:36 +0200, Huji Lee huji.h...@gmail.com wrote: Here is a final question: how long does it generally take for a change made in a script to be reflected in the output of RL? Is it in the order of minutes or hours? It should happen within five minutes, or immediately if you clear the browser cache. -- Bartosz Dziewoński ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Code of conduct committee
On 21/08/15 14:39, Oliver Keyes wrote: On 21 August 2015 at 06:43, Quim Gil q...@wikimedia.org wrote: Hi, On Fri, Aug 21, 2015 at 11:49 AM, Steinsplitter Wiki steinsplitter-w...@live.com wrote: * I see a lot (maybe 70%) staffer edits there. I also would like to see more edits from volunteers and other affiliations. Please jump in! Most WMF employees drafting and discussing there are doing so out of their personal interest, with no WMF directive and most likely on their own time. I'm basically the only exception. Speaking as a WMF employee who is involved in the discussion, this is my personal opinion - hence my choice of accounts to comment with. I suspect that WMF employees probably make up a big proportion of the technical community itself (something this proposal will hopefully help change!) and so large amounts of WMF participation is not surprising. If nothing else, WMF employees are likely the bulk of technical contributors with the spare time to actually talk meta about this stuff, since they're already spending their paid time making things. Imagine if you were doing all of this in your spare time, would you rather be using your limited time making things, or talking about some ephemeral proposed thing that may not ever even affect you even if it does become real? Having to make that choice could impact matters too. -I ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Engineering] Code of conduct
On Sun, Aug 16, 2015 at 6:24 PM, Oliver Keyes oke...@wikimedia.org wrote: On 16 August 2015 at 04:06, rupert THURNER rupert.thur...@gmail.com wrote: that is an impressive list, amir. WMF hast its terms of use: https://wikimediafoundation.org/wiki/Terms_of_Use (TOU) . admitted, an illegible monster compared to the simple statements below, like contributor covenant. i honestly do not think that an open movement like the wikimedia movement should invent any new terms, licenses, codes, but influence existing ones. by putting your stuff on the mediawiki.org site you and all contributors are bound to the TOU. and we already see that the many rules contradict each other in little areas, they cannot be updated fast enough without an army of persons. the terms of use e.g. suggest to use CC-BY-SA 3.0, which lead to a collection of law suites in germany, while CC-BY-SA 4.0 would have prevented at least some of them, see here: https://lists.wikimedia.org/pipermail/wikimedia-l/2015-July/078685.html . I don't understand how the terms of use or copyright license relate in any way to codes of conduct. If you mean we should be looking for good examples of existing enforcement mechanisms or language, I absolutely agree, and that is part of what the Code of Conduct is trying to do. i mean that we duplicate text in hundreds of slightly differing rules, guidelines, policies, terms, codes, in different languages. this inflation of texts is very special to the wikimedia movement. my personal expectation would be that movement paid persons do have as main task to reduce the complexity for volunteers, readers, writers, photographers, coders, etc. and as second task, they support innovative techniques. we should not forget it takes time to write stuff, and it takes exponentially more time to read it. if we make a wikimedia policy, it has the potential to be read by 1 billion people. reading policies and writing policies can be considered as waste because it is not the mission of wikipedia, not the mission of WMF :) coming back to the example terms of use, they state: *Civility* – You support a civil environment and do not harass other users. paragraph 4 vastly elaborates on it. a 90% duplicate of the code of conduct. brion, civility _is_ enforced already today by the terms of use, nothing new necessary. how does this relate to copyright license? directly not really, but i tried to hint that i would expect a technical solution from a technical person. as example where our written rules go wrong i cited the thread about licenses and reuse in commons, in two aspects. ONE, updating a lot of policies is a sisyphus task, and the WMF fails already today. the terms of use include still the old CC license, using the new one would prevent law suits in germany. TWO, you oliver, matt, quim and other technicians, would have the responsibility to come up with technical solutions to exactly this community problem, not paper. can we add metadata to images: https://lists.wikimedia.org/pipermail/wikimedia-l/2015-July/078782.html. problem would be solved by a technical implementation and maybe adapting the license. which, in my biased opinion, has a huge impact and solves the problem at source for 120 million german speaking persons, and probably in many other countries as well. best, rupert ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Code of conduct committee
On 08/21/2015 06:43 AM, Quim Gil wrote: I also would like to see more edits from volunteers and other affiliations. Please jump in! Most WMF employees drafting and discussing there are doing so out of their personal interest, with no WMF directive and most likely on their own time. I'm basically the only exception. It's important to remember that we're building this CoC because it is relevant to both our community and our work. I know that's why I'm participating, and I believe it's also why the volunteers are. Matt Flaschen ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Code of conduct committee
Some thoughts about https://www.mediawiki.org/wiki/Code_of_conduct_for_technical_spaces/Draft * I can't see community consensus (RFC) for this. * I see a lot (maybe 70%) staffer edits there. * It is complicated to understand the policy. I have the feeling that only a few staffer building this. Please don't forget to involve the community! How you like to enforce this policy on irc? What is the committee? A WMF super arbcom? Moor transparency would be great, and to write it in simple english so that non native speakers can get involved. Best and with concerns, Steinsplitter Date: Fri, 21 Aug 2015 00:27:22 -0400 From: mflasc...@wikimedia.org To: wikitech-l@lists.wikimedia.org Subject: [Wikitech-l] Code of conduct committee There is some discussion now about how the Code of Conduct Committee should be formed. See: * https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Membership_of_the_committee_and_ECT.27s_role and * https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Another_membership_proposal . Thanks, Matt Flaschen ___ 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] Page Curation for other wikis
I found this bug: https://phabricator.wikimedia.org/T50552 But it has lowest priority. Why? On Fri, Aug 21, 2015 at 1:10 PM jay...@gmail.com wrote: This could be a good GSoC project. On Fri, 21 Aug 2015 18:08 Amir Ladsgroup ladsgr...@gmail.com wrote: Hey, Page Curation [1][2][3] is a project funded by WMF but strangely the product is only available for English Wikipedia. This is surprising because this tool is useful for all Wikis and I don't think i18n would be very hard. Is there any plans to add i18n and rolling it out in other languages? If it's not funded anymore, Is anyone willing to help as volunteer to work? [1] https://en.wikipedia.org/wiki/Wikipedia:Page_Curation [2] https://www.mediawiki.org/wiki/Page_Curation [3] https://www.mediawiki.org/wiki/Extension:PageTriage Best ___ 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 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Call for Participation: SEMANTiCS 2015, 11th International Conference on Semantic Systems
== Apologies for Crossposting == Below you will find useful information and links about the program, our satellite events and registration opportunities for SEMANTiCS 2015 -- 11th International Conference on Semantic Systems 15-17 September 2015, Vienna / Austria http://www.semantics.cc/ // #semantics2015 // #semanticsconf *— Conference Scope ---* The annual SEMANTiCS conference is the meeting place for professionals who make semantic computing work, and understand its benefits and know its limitations. Every year, SEMANTiCS attracts information managers, IT-architects, software engineers, and researchers, from organisations ranging from NPOs, universities, public administrations to the largest companies in the world. *— Conference Program ---* The 2015 edition offers a rich program consisting of 5 keynotes, 24 scientific presentations, 30 industry talks, 38 posters and various workshops and social events. For details please visit our program page: http://www.semantics.cc/programme *— Keynote Speakers --- * ·Jeanne Holms -- Chief Knowledge Architect at NASA ·Peter Mika -- Director Semantic Lab at Yahoo ·Oscar Orcho -- Associate Professor for Artifical Intelligence, Universidad de Madrid ·Klaus Tochtermann -- Leibniz Information Center for Economics ·Sam Rehman -- CTO at EPAM Systems *— Workshops Satellite Events ---* *MeetUp: SMART DATA SOLUTIONS* An outlook into the world of data centric business, technologies and innovations: Data is everywhere these days and efficient data management is THE key factor for success in nearly all industries in the meantime. McKinsey lists data as a key factor for production alongside with labor and capital in one of their recent reports. Furthermore, Data is produced in huge amounts by sensors, social networks or mobile devices and the amounts of data available worldwide grow exponentially… Place: Haus der Ingenieure, Eschenbachgasse 9, 1010 Wien Date: 15.09.2015, Entrance: 18:30pm CET ; Start event: 19:30 - 22:30pm CET *2nd International Workshop on Geospatial Linked Data* In recent years, Semantic Web technologies have strengthened their position in the areas of data and knowledge management. Standards for organizing and querying semantic information, such as RDF(S) and SPARQL are adopted by large academic communities, while corporate vendors adopt semantic technologies to organize, expose, exchange and retrieve their datasets as Linked Data. Chairs: Alejandra Garcia-Rojas M. (Ontos AG), Robert Isele or Rene Pietzsch, Jens Lehmann (AKSW, University of Leipzig) Date: 15th of September 2015, 09.00 to 13.00 CEST *The SEMANTIC EXPERIENCE Coffee Cocktail LOUNGE* Sponsored Event: Enjoy semantic technology inspiration in a relaxed atmosphere. Refresh yourself with Viennese coffee or a cocktail and get in touch with semantic industry experts. Date: 15th of September 2015, 15.45 to 18.00 CEST Room: LC Club Room *Linked Data in Industry 4.0* The overall goal of the workshop is to identify challenges and limitations from the manufacturing engineering industry in the scope of the mentioned design principles, and bring them together with experts and solution approaches from the linked data community in the scope of Industry 4.0. Chairs: Thomas Moser (FH St. Pölten), Stefan Hupe (IoT Austria) Date: 15th of September 2015, 14.00 to 17.00 CEST *European Data Economy Workshop - Focus Data Value Chain Big and Open Data* This workshop is to overview the state of the art in Europe regarding Big and Open Data initiatives and its impact in the Europan economy and benefits for theEuropean society. Representatives from the Big Data Value Association, the annual European Data Forum and data related projects will participate during the first session of the workshop. Furthermore it gives information about the Austrian Big Data Study carried out in 2014 by AIT and IDC Chairs: Nelia Lasierra (STI Innsbruck), Martin Kaltenböck (Semantic Web Company) Date: 15th of September 2015, 09.00 to 13.00 CEST *1st Workshop on Data Science: Methods, Technology and Applications (DSci15)* This workshop is meant as an opportunity to bring together researchers and practitioners interested in data science to present their ideas and discuss the most important scientific, technical and socio-economical challenges of this emerging field. Chairs: Bernhard Haslhofer (AIT - Austrian Institute of Technology), Elena Simperl (Univ. Southampton), Rainer Stütz (AIT - Austrian Institute of Technology), Ingo Feinerer (FH Wiener Neustadt) Date: 15th of September 2015, 09.00 to 17.00 CEST *Workshop on Linked Data Strategies - Commercialisation of Interlinked Data* In this workshop, we will give several demos and concrete examples of how Linked Data can be used by enterprises in various industries. The workshop aims to give users and providers of Linked Data valuable methods and best practices at hand, which help them to make
[Wikitech-l] Page Curation for other wikis
Hey, Page Curation [1][2][3] is a project funded by WMF but strangely the product is only available for English Wikipedia. This is surprising because this tool is useful for all Wikis and I don't think i18n would be very hard. Is there any plans to add i18n and rolling it out in other languages? If it's not funded anymore, Is anyone willing to help as volunteer to work? [1] https://en.wikipedia.org/wiki/Wikipedia:Page_Curation [2] https://www.mediawiki.org/wiki/Page_Curation [3] https://www.mediawiki.org/wiki/Extension:PageTriage Best ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Page Curation for other wikis
This could be a good GSoC project. On Fri, 21 Aug 2015 18:08 Amir Ladsgroup ladsgr...@gmail.com wrote: Hey, Page Curation [1][2][3] is a project funded by WMF but strangely the product is only available for English Wikipedia. This is surprising because this tool is useful for all Wikis and I don't think i18n would be very hard. Is there any plans to add i18n and rolling it out in other languages? If it's not funded anymore, Is anyone willing to help as volunteer to work? [1] https://en.wikipedia.org/wiki/Wikipedia:Page_Curation [2] https://www.mediawiki.org/wiki/Page_Curation [3] https://www.mediawiki.org/wiki/Extension:PageTriage Best ___ 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
