Re: [Wikitech-l] wav support to Commons (was Re:Advice Needed)
On 11 April 2013 00:29, Quim Gil q...@wikimedia.org wrote: As of today this falls in the category of NO to projects depending on unconvinced maintainers. In this case the Commons maintainers. http://commons.wikimedia.org/wiki/Commons:Project_scope/Allowable_file_types If the Commons community is happy to take this format, fine. But we need to know before the deadline for accepting projects. Or you need to change your strategy. That's just a list of formats that are enabled in the software, that are free formats. There wasn't a vote on WebM, for example - it was more like finally! when it became technically feasible. - d. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] wav support to Commons (was Re:Advice Needed)
On Thu, Apr 11, 2013 at 4:59 AM, Quim Gil q...@wikimedia.org wrote: On 04/10/2013 03:16 PM, Rahul Maliakkal wrote: In my GSOC project , i plan on adding *.wav support* to commons As of today this falls in the category of NO to projects depending on unconvinced maintainers. In this case the Commons maintainers. http://commons.wikimedia.org/**wiki/Commons:Project_scope/** Allowable_file_typeshttp://commons.wikimedia.org/wiki/Commons:Project_scope/Allowable_file_types If the Commons community is happy to take this format, fine. But we need to know before the deadline for accepting projects. Or you need to change your strategy. Another question is of course how feasible is to include adding *.wav support* to commons in the scope of your project. In my extension i plan on adding 5 second recordings of words, 5 seconds of .wav would be at max 200 kb more than 5 seconds of .ogg(worst case).I dont see any harm in that. Is an exclusive permission possible ? Relevant: WAV audio support via TimedMediaHandler https://bugzilla.wikimedia.**org/show_bug.cgi?id=32135https://bugzilla.wikimedia.org/show_bug.cgi?id=32135 Good to see that mdale is already involved there. Micheal has been really helpful uptill now -- Quim Gil Technical Contributor Coordinator @ Wikimedia Foundation http://www.mediawiki.org/wiki/**User:Qgilhttp://www.mediawiki.org/wiki/User:Qgil __**_ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/**mailman/listinfo/wikitech-lhttps://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] wav support to Commons (was Re:Advice Needed)
On Thu, Apr 11, 2013 at 5:46 AM, Ryan Kaldari rkald...@wikimedia.orgwrote: On 4/10/13 4:29 PM, Quim Gil wrote: On 04/10/2013 03:16 PM, Rahul Maliakkal wrote: In my GSOC project , i plan on adding *.wav support* to commons I don't see any email on this list that includes that quote, nor does Ruhul's GSoC proposal mention anything about WAV. Could you provide some context by either quoting the entire message or pointing to where this discussion is actually taking place? Thanks! Ryan Kaldari I will be uploading my v2.0 of my gsoc proposal today ,you could see it then http://lists.wikimedia.org/pipermail/wikitech-l/2013-April/068336.html(Scroll down a littlle bit :P) __**_ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/**mailman/listinfo/wikitech-lhttps://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] Sort on category
One of the demo collections originally shown in pivot was wikipedia article's sorted by category. Though the collections are no longer up, you can see videos at: http://www.youtube.com/watch?v=BZuFUZpEZ-A?t=2m30s http://www.youtube.com/watch?v=vgxCvdoXpwM It was done before (albeit using a dedicated viewer which is now a silverlight control). So it can be done. -Small From: Brian Wolff bawo...@gmail.com To: Small M smallma...@yahoo.com; wikitech-l wikitech-l@lists.wikimedia.org Sent: Wednesday, April 10, 2013 6:42 PM Subject: Re: [Wikitech-l] Sort on category On 2013-04-10 10:25 PM, Small M smallma...@yahoo.com wrote: Hello, Are there any plans to have a tool that would allow to dynamically sort content based on category? Single category views, especially for large categories, aren't particularly helpful. Something similar to what Microsoft's pivot demo had? An HTML5 example at: http://pivot.lobsterpot.com.au/pass2012.htm -Small ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l No, there are no current plans for doing this. Interesting idea though. If I understand you correctly you want a category page where things are grouped by what other categories a page is a member of. I don't think such a thing can be done in an efficient manner for big categories given the way category membership is currently stored. -bawolff ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Sort on category
On Apr 11, 2013 10:56 AM, Small M smallma...@yahoo.com wrote: It was done before (albeit using a dedicated viewer which is now a silverlight control). So it can be done. First a warning: I can't imagine a MediaWiki feature ever being enabled on WMF wikis if it works only with silverlight. And you said HTML5 demo. One of the points of HTML5 is to move away from plugins. So this is confusing. Or maybe there are 2 unrelated demos (a silverlight and an HTML5) I believe Brian's point was: this sort of feature would require access to raw category data in a format that doesn't currently exist. (but can be generated from existing data) If you've seen it done then what you've seen is probably based on a snapshot in time (maybe from a dump) not from the live, current state of a WMF wiki. -Jeremy ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Sort on category
There's an article for Microsoft Pivot at [1] . Originally it was a standalone application (which is no longer supported), and now is a silverlight control (PivotViewer). HTML5 is usually preferred to plugins, so some made an HTML5 version at [2]. Sorry for the confusion. The collections used for Pivot were snapshots. Even with monthly/bi-monthly snapshots, this form of visualization would be better than the current one. Are there any current tools that allow for this type of category intersection/joining? [1] https://en.wikipedia.org/wiki/Microsoft_Live_Labs_Pivot [2] http://lobsterpothtml5pv.codeplex.com/ -Small From: Jeremy Baron jer...@tuxmachine.com To: Small M smallma...@yahoo.com Cc: Wikimedia developers wikitech-l@lists.wikimedia.org Sent: Thursday, April 11, 2013 8:07 AM Subject: Re: [Wikitech-l] Sort on category On Apr 11, 2013 10:56 AM, Small M smallma...@yahoo.com wrote: It was done before (albeit using a dedicated viewer which is now a silverlight control). So it can be done. First a warning: I can't imagine a MediaWiki feature ever being enabled on WMF wikis if it works only with silverlight. And you said HTML5 demo. One of the points of HTML5 is to move away from plugins. So this is confusing. Or maybe there are 2 unrelated demos (a silverlight and an HTML5) I believe Brian's point was: this sort of feature would require access to raw category data in a format that doesn't currently exist. (but can be generated from existing data) If you've seen it done then what you've seen is probably based on a snapshot in time (maybe from a dump) not from the live, current state of a WMF wiki. -Jeremy ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] wav support to Commons (was Re:Advice Needed)
On 04/11/2013 12:00 AM, David Gerard wrote: On 11 April 2013 00:29, Quim Gil q...@wikimedia.org wrote: As of today this falls in the category of NO to projects depending on unconvinced maintainers. In this case the Commons maintainers. http://commons.wikimedia.org/wiki/Commons:Project_scope/Allowable_file_types If the Commons community is happy to take this format, fine. But we need to know before the deadline for accepting projects. Or you need to change your strategy. That's just a list of formats that are enabled in the software, that are free formats. There wasn't a vote on WebM, for example - it was more like finally! when it became technically feasible. I'm just trying to be consistent: a GSOC project can't force the agenda of a Wikimedia project. Also conservative when it comes to manage GSOC students expectations. These bug reports have been open for years, and I don't want to guarantee to a GSOC student that they can count on seeing them fixed now. Bug 20252 - Support for WAV and AIFF by converting files to FLAC automatically https://bugzilla.wikimedia.org/show_bug.cgi?id=20252 Bug 32135 - WAV audio support via TimedMediaHandler https://bugzilla.wikimedia.org/show_bug.cgi?id=32135 Then again, a GSOC project can be a catalyst of change if you get a determined student and a qualified mentor to agree on something and push the agenda. We have the ingredients here, but sill you need to move fast to see if this is a missing feature just because, or if the Commons community has some strong opinion about it. I'm not the one to be convinced and probably wikitech-l is not the place to have a decision either. Please continue the discussion in the bug reports, making sure the Commons community is aware and involved. -- Quim Gil Technical Contributor Coordinator @ 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
[Wikitech-l] Sponsoring travel to Wikimedia Hackathon
Hi, you have probably heard about Wikimedia Hackathon 24-26 May in Amsterdam (Netherlands) http://www.mediawiki.org/wiki/Amsterdam_Hackathon_2013 There are about 100 participants registered, and we have some room for more. Registration is free but you need to sign up. There is also some travel sponsorship budget left after a first round of approvals. If your free software contributions and your Wikimedia love is more valuable than the money you have in the bank, you can just register and apply for scholarship. Please include public URLs where we can see your open source licensed contributions (code, pixels, wise words...). A CV alone won't cut it, no matter how many avatars appear to endorse your skills. Hurry up! The organizers are reviewing applications as they come. -- Quim Gil Technical Contributor Coordinator @ 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
[Wikitech-l] Motivation for working on a free software project
Hello, I'm a student of a master in free software in Spain. For performing a academic work, I ask for your cooperation by answering the following questions: 1. - In what ways began collaborating in an open source project? 2. - What is your motivation to participate in a free software project: social motivation, technological, economic, etc? 3. - In their collaborations, which is the project you found more motivated? 4. - What do you think is the main reason that generally has the other contributors? 5. - Do you think your participation in open source projects will help improve your future career? 6. - Do you think in the future continue to work on open source projects? or in Spanish: 1.- ¿De que manera comenzó a colaborar en un proyecto de software libre? 2.- ¿Cual es su motivacion para participar en un proyecto de software libre: motivacion social, tecnologica, economica, etc? 3.- Dentro de sus colaboraciones, ¿en que proyecto se ha encontrado más motivado? 4.- ¿Cual cree que es la principal motivación que en general tiene el resto de colaboradores? 5.- ¿Cree que su participación en proyectos de software libre le ayudara a mejorar su futuro profesional? 6.- ¿Piensa en un futuro seguir colaborando en proyectos de software libre? In advance, thank you very much. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] New git-review version revives year-old bug
I added the workaround and background to https://www.mediawiki.org/wiki/Gerrit/resolve_conflict , which also covers gerrit rebase failures. On Mon, Apr 8, 2013 at 2:54 PM, Roan Kattouw roan.katt...@gmail.com wrote: About a year ago, we were struggling with a git-review bug that caused lots of bogus warnings to appear. When running git review, you'd get a warning saying you're about to submit multiple commits, followed by a list of lots of other people's commits that have already been merged. I fixed this in https://review.openstack.org/#/c/6741/ last year. This bug is now back in the latest release of git-review that came out over the weekend. I complained about this at https://review.openstack.org/#/c/20450/ , which is the change that reintroduced the broken behavior. We are suffering from it disproportionately because we have defaultrebase=0 set on most of our projects, and the bug only triggers when rebasing is disabled (using either that setting or the -R flag). The workaround is the same as last year: if git-review complains and you see bogus commits in the list, respond no to abort, run git fetch gerrit, then rerun git-review. This will ensure git-review has an up-to-date view of the remote master. Roan ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- =S Page software engineer on E3 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] GSoC 2013: Improve support for book structures
Hi! Your proposal looks very good. I'll be very happy to help you as co-mentor on this project if is no GSoc project for Proofread Page. Some comments: 1. You should keep in mind that the extension will be used by Wikibook and Wikisource communities so these communities must be involve in the project. 2. For Wikisource, the extension should be nicely integrated with the current proofreading workflow managed by Proofread Page (this can be done in a second time but we should keep it in mind). 3. The extension should, I think, be able to manage metadata about books like the author(s) in order to be able to provide these information in the exported files. The metadata have sometime to be input by the contributors (like the author of a Wikisource book) or to be get from MediaWiki (like the authors of Wikibook books that are the contributors of the book pages) or maybe, in the future, even get from Wikidata. 4. The extension must be simple to use. I believe that one of the main goal is to simplify the edition workflow. So, new wikicode syntax to learn for basic users should be avoided as much as possible (this doesn't concern syntax that will only be used in templates). A good way to archive these goals is maybe be to make book main pages not wikitext based pages, but a page that store in a structured format (like JSON) metadata of the book, a table of content and some free text spaces, all of that edited via a clever form. For that, we can reuse some code written for the Wikidata project (storage with the Content handler, Diff system, DataValue library...). Working in that way will allow to get nice and well-formatted metadata that can be used to improve cataloging of books and avoid the need for people to learn new tags, templates or parser functions in order to create a new books. But this will require more development time. What do you think about it? Thomas (I CC the members of the Elaborate Wikisource strategic vision group) Date: Thu, 11 Apr 2013 12:16:44 -0400 From: gorillawarfarewikipe...@gmail.com To: wikitech-l@lists.wikimedia.org Subject: [Wikitech-l] GSoC 2013: Improve support for book structures Hi! I'm Molly White, or GorillaWarfare on the WMF projects. I'm planning to submit a proposal to the WMF for this summer's Google Summer of Code (and probably also the Outreach Program for Women) and was hoping to get some feedback. See my proposal at https://www.mediawiki.org/wiki/User:GorillaWarfare/Proposal. I would like to improve support for projects (like Wikisource and Wikibooks) that have content that's structured as a book and not as an article. I plan to do this by working on the existing BookManager extension. It's currently unstable and very much in development, so there's a lot of room for improvement. Do you have any feedback, concerns, suggestions, etc.? Do you think the project is feasible for GSoC? Thanks, Molly White ___ 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] GSoC 2013: Improve support for book structures
+1 mentor 2013/4/11 Thomas PT thoma...@hotmail.fr Hi! Your proposal looks very good. I'll be very happy to help you as co-mentor on this project if is no GSoc project for Proofread Page. Some comments: 1. You should keep in mind that the extension will be used by Wikibook and Wikisource communities so these communities must be involve in the project. 2. For Wikisource, the extension should be nicely integrated with the current proofreading workflow managed by Proofread Page (this can be done in a second time but we should keep it in mind). 3. The extension should, I think, be able to manage metadata about books like the author(s) in order to be able to provide these information in the exported files. The metadata have sometime to be input by the contributors (like the author of a Wikisource book) or to be get from MediaWiki (like the authors of Wikibook books that are the contributors of the book pages) or maybe, in the future, even get from Wikidata. 4. The extension must be simple to use. I believe that one of the main goal is to simplify the edition workflow. So, new wikicode syntax to learn for basic users should be avoided as much as possible (this doesn't concern syntax that will only be used in templates). A good way to archive these goals is maybe be to make book main pages not wikitext based pages, but a page that store in a structured format (like JSON) metadata of the book, a table of content and some free text spaces, all of that edited via a clever form. For that, we can reuse some code written for the Wikidata project (storage with the Content handler, Diff system, DataValue library...). Working in that way will allow to get nice and well-formatted metadata that can be used to improve cataloging of books and avoid the need for people to learn new tags, templates or parser functions in order to create a new books. But this will require more development time. What do you think about it? Thomas (I CC the members of the Elaborate Wikisource strategic vision group) Date: Thu, 11 Apr 2013 12:16:44 -0400 From: gorillawarfarewikipe...@gmail.com To: wikitech-l@lists.wikimedia.org Subject: [Wikitech-l] GSoC 2013: Improve support for book structures Hi! I'm Molly White, or GorillaWarfare on the WMF projects. I'm planning to submit a proposal to the WMF for this summer's Google Summer of Code (and probably also the Outreach Program for Women) and was hoping to get some feedback. See my proposal at https://www.mediawiki.org/wiki/User:GorillaWarfare/Proposal. I would like to improve support for projects (like Wikisource and Wikibooks) that have content that's structured as a book and not as an article. I plan to do this by working on the existing BookManager extension. It's currently unstable and very much in development, so there's a lot of room for improvement. Do you have any feedback, concerns, suggestions, etc.? Do you think the project is feasible for GSoC? Thanks, Molly White ___ 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
Re: [Wikitech-l] Clicktracking being phased out
On Wednesday, April 3, 2013 at 2:04 PM, Matthew Flaschen wrote: We are in the process of phasing out Clicktracking. An example of this is https://gerrit.wikimedia.org/r/#/c/46205/ . If you are relying on this for an extension, you should explore other options, such as https://www.mediawiki.org/wiki/Event_logging . Matt Flaschen Extension was dropped today. -- Ori Livneh ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] wav support to Commons (was Re:Advice Needed)
On 04/11/2013 10:48 AM, Quim Gil wrote: I'm just trying to be consistent: a GSOC project can't force the agenda of a Wikimedia project. Also conservative when it comes to manage GSOC students expectations. These bug reports have been open for years, and I don't want to guarantee to a GSOC student that they can count on seeing them fixed now. Bug 20252 - Support for WAV and AIFF by converting files to FLAC automatically https://bugzilla.wikimedia.org/show_bug.cgi?id=20252 Bug 32135 - WAV audio support via TimedMediaHandler https://bugzilla.wikimedia.org/show_bug.cgi?id=32135 Adding Wav to TMH is a pretty small technical addition. Audio transcoding was already added by Jan. Adding .wav support on top of that, is probably one of the easiest parts of the project. I don't think the project would be forcing an agenda on commons, its analogous work to add TIFF support a while back. Also this is mostly an intermediate solution while browsers can only capture and upload PCM wav data. Once browsers ship the full record api, we will be able to 'export out' the captured Opus audio and upload that. Then transcode from that Opus oga to additional formats that can be played in ( other ) browsers and devices. --michael ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Proposal for merging now: (bug 38783) add git HEAD date to Special:Version for core and extensions
RE: https://gerrit.wikimedia.org/r/#/c/54986/ code working live on http://openid-wiki.instance-proxy.wmflabs.org/wiki/Special:Version Ready for merge into core. Can some please merge, thanks. I invested a lot of efforts to fix (implement) add git HEAD commit date to Special:Version for core and extensions and deeply wish that I can stop my daily rebasing .. that it will become part of the core. Can someone please merge, thanks. The code fulfilly all requirements, and has now the correct code in Installer.php for testing the presence of git or git.exe, which is definitely required to obtain the correct commit date, which cannot otherwise fetched from the git objects. Tom signature.asc Description: OpenPGP digital signature ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Fwd: [WikimediaMobile] Developer guidance for MobileFrontend extension
Forwarding to wikitech-l, since I'm unsure how many people follow mobile-l -- Forwarded message -- From: Jon Robson jdlrob...@gmail.com Date: Fri, Apr 12, 2013 at 3:53 AM Subject: [WikimediaMobile] Developer guidance for MobileFrontend extension To: mobile-l mobil...@lists.wikimedia.org I was prompted by a MediaWiki discussion [1] to provide guidelines on developers making desktop modules mobile friendly [2] Please wade in with your thoughts on the subject. [1] http://www.mediawiki.org/w/index.php?title=Extension_talk:MobileFrontendoffset=20130410063927lqt_mustshow=26098#Is_JavaScript_filtered.3F_26098 [2] http://www.mediawiki.org/wiki/ResourceLoader/Writing_a_MobileFrontend_Friendly_ResourceLoader_module ___ Mobile-l mailing list mobil...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l -- Yuvi Panda T http://yuvi.in/blog ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Clicktracking being phased out
RIP Clicktracking. On Thu, Apr 11, 2013 at 2:08 PM, Ori Livneh o...@wikimedia.org wrote: On Wednesday, April 3, 2013 at 2:04 PM, Matthew Flaschen wrote: We are in the process of phasing out Clicktracking. An example of this is https://gerrit.wikimedia.org/r/#/c/46205/ . If you are relying on this for an extension, you should explore other options, such as https://www.mediawiki.org/wiki/Event_logging . Matt Flaschen Extension was dropped today. -- Ori Livneh ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Jon Robson http://jonrobson.me.uk @rakugojon ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Clicktracking being phased out
On Apr 11, 2013 6:54 PM, Lukas Benedix bene...@zedat.fu-berlin.de wrote: Can you tell me why this is going to be removed and what insights you got from it? I believe it's being deprecated in favor of the EventLogging extension. In any case the mediawikiwiki extension pages should be updated. -Jeremy ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Fwd: [WikimediaMobile] Developer guidance for MobileFrontend extension
On 04/11/2013 06:25 PM, Yuvi Panda wrote: Forwarding to wikitech-l, since I'm unsure how many people follow mobile-l https://www.mediawiki.org/wiki/ResourceLoader/Writing_a_MobileFrontend_Friendly_ResourceLoader_module mentions a efEnableMobileModules hook. The actual hook is EnableMobileModules. I've documented it on MW.org. See https://www.mediawiki.org/wiki/Extension_hook_registry and https://www.mediawiki.org/wiki/Extension:MobileFrontend/EnableMobileModules . Matt Flaschen ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Clicktracking being phased out
On 04/11/2013 06:54 PM, Lukas Benedix wrote: Can you tell me why this is going to be removed and what insights you got from it? It's being removed in favor of EventLogging, which we believe is technically better and more flexible. For some of the research these extensions make possible, see https://meta.wikimedia.org/wiki/Research Matt Flaschen ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Sort on category
On 04/11/2013 11:46 AM, Small M wrote: There's an article for Microsoft Pivot at [1] . Originally it was a standalone application (which is no longer supported), and now is a silverlight control (PivotViewer). HTML5 is usually preferred to plugins, so some made an HTML5 version at [2]. Sorry for the confusion. The collections used for Pivot were snapshots. Even with monthly/bi-monthly snapshots, this form of visualization would be better than the current one. Are there any current tools that allow for this type of category intersection/joining? See https://en.wikipedia.org/wiki/Wikipedia:CatScan Matt Flaschen ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Sort on category
On Apr 11, 2013 7:26 PM, Matthew Flaschen mflasc...@wikimedia.org wrote: On 04/11/2013 11:46 AM, Small M wrote: Are there any current tools that allow for this type of category intersection/joining? See https://en.wikipedia.org/wiki/Wikipedia:CatScan also, https://en.wikipedia.org/wiki/Wikipedia:Category_intersections ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Sort on category
It certainly can be done (and done without need for silverlight) on smallish categories (to pull numbers out of a hat, things with less than 1000 pages probably would be fine). I doubt the silverlight control would work with a category that has a million entries in it (and yes there are categories that big) -bawolff On 2013-04-11 11:56 AM, Small M smallma...@yahoo.com wrote: One of the demo collections originally shown in pivot was wikipedia article's sorted by category. Though the collections are no longer up, you can see videos at: http://www.youtube.com/watch?v=BZuFUZpEZ-A?t=2m30s http://www.youtube.com/watch?v=vgxCvdoXpwM It was done before (albeit using a dedicated viewer which is now a silverlight control). So it can be done. -Small From: Brian Wolff bawo...@gmail.com To: Small M smallma...@yahoo.com; wikitech-l wikitech-l@lists.wikimedia.org Sent: Wednesday, April 10, 2013 6:42 PM Subject: Re: [Wikitech-l] Sort on category On 2013-04-10 10:25 PM, Small M smallma...@yahoo.com wrote: Hello, Are there any plans to have a tool that would allow to dynamically sort content based on category? Single category views, especially for large categories, aren't particularly helpful. Something similar to what Microsoft's pivot demo had? An HTML5 example at: http://pivot.lobsterpot.com.au/pass2012.htm -Small ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l No, there are no current plans for doing this. Interesting idea though. If I understand you correctly you want a category page where things are grouped by what other categories a page is a member of. I don't think such a thing can be done in an efficient manner for big categories given the way category membership is currently stored. -bawolff ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] GSoC 2013: Improve support for book structures
Thomas PT thomaspt at hotmail.fr writes: Hi! Your proposal looks very good. I'll be very happy to help you as co-mentor on this project if is no GSoc project for Proofread Page. Some comments: 1. You should keep in mind that the extension will be used by Wikibook and Wikisource communities so these communities must be involve in the project. 2. For Wikisource, the extension should be nicely integrated with the current proofreading workflow managed by Proofread Page (this can be done in a second time but we should keep it in mind). 3. The extension should, I think, be able to manage metadata about books like the author(s) in order to be able to provide these information in the exported files. The metadata have sometime to be input by the contributors (like the author of a Wikisource book) or to be get from MediaWiki (like the authors of Wikibook books that are the contributors of the book pages) or maybe, in the future, even get from Wikidata. 4. The extension must be simple to use. I believe that one of the main goal is to simplify the edition workflow. So, new wikicode syntax to learn for basic users should be avoided as much as possible (this doesn't concern syntax that will only be used in templates). A good way to archive these goals is maybe be to make book main pages not wikitext based pages, but a page that store in a structured format (like JSON) metadata of the book, a table of content and some free text spaces, all of that edited via a clever form. For that, we can reuse some code written for the Wikidata project (storage with the Content handler, Diff system, DataValue library...). Working in that way will allow to get nice and well-formatted metadata that can be used to improve cataloging of books and avoid the need for people to learn new tags, templates or parser functions in order to create a new books. But this will require more development time. What do you think about it? Thomas (I CC the members of the Elaborate Wikisource strategic vision group) Date: Thu, 11 Apr 2013 12:16:44 -0400 From: gorillawarfarewikipedia at gmail.com To: wikitech-l at lists.wikimedia.org Subject: [Wikitech-l] GSoC 2013: Improve support for book structures Hi! I'm Molly White, or GorillaWarfare on the WMF projects. I'm planning to submit a proposal to the WMF for this summer's Google Summer of Code (and probably also the Outreach Program for Women) and was hoping to get some feedback. See my proposal at https://www.mediawiki.org/wiki/User:GorillaWarfare/Proposal. I would like to improve support for projects (like Wikisource and Wikibooks) that have content that's structured as a book and not as an article. I plan to do this by working on the existing BookManager extension. It's currently unstable and very much in development, so there's a lot of room for improvement. Do you have any feedback, concerns, suggestions, etc.? Do you think the project is feasible for GSoC? Thanks, Molly White ___ Wikitech-l mailing list Wikitech-l at lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l at lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l Wow, thank you so much for your detailed reply. I would love to have you as a co-mentor, assuming no one is available to work on the Proofread Page extension. Regarding your suggestions: I've posted on both English and Multilingual Wikisource regarding my ideas, but I will do so again when I have a more specific plan. I'll also communicate with the Wikibooks community. I'm sure both communities will have a lot of useful feedback. How do you envision this integrating with Proofread Page? The vision I had of this extension was as a somewhat separate process, but I think the more the process can be simplified, the better. I strongly agree about the metadata. I will be more specific in my proposal that I intend to include the ability to add that on the book organization page. I also like the idea of integrating it with WikiData. I had planned to use a form-type organization page, and not to try to organize it using wikitext. I really like the JSON idea, actually; I think that might be the perfect format for this. I will start looking at the WikiData code to get an idea of how they use it. Thanks so much, Molly White ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Fwd: [WikimediaMobile] Developer guidance for MobileFrontend extension
Thanks Matt ! Much appreciated :) On 11 Apr 2013 16:19, Matthew Flaschen mflasc...@wikimedia.org wrote: On 04/11/2013 06:25 PM, Yuvi Panda wrote: Forwarding to wikitech-l, since I'm unsure how many people follow mobile-l https://www.mediawiki.org/wiki/ResourceLoader/Writing_a_MobileFrontend_Friendly_ResourceLoader_module mentions a efEnableMobileModules hook. The actual hook is EnableMobileModules. I've documented it on MW.org. See https://www.mediawiki.org/wiki/Extension_hook_registry and https://www.mediawiki.org/wiki/Extension:MobileFrontend/EnableMobileModules . 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] HTML versioning information in skins?
On 04/07/2013 07:10 AM, Bartosz Dziewoński wrote: tl;dr: Let's add class=skintimestamp-MMDD to body in all skins, so we can make HTML+CSS changes without breaking the sites. [Resending as it doesn't seem to have gotten through the first time.] We need HTML versioning information needed in skins to be able to cleanly make incompatible CSS changes. In the Wikimedia setup generated page HTML is cached for ~30 days regardless of skin HTML changes, while CSSJS is purged at most a few minutes after a change is deployed. This is a highly suboptimal situation, as this means that in every change that modifies both the HTML and the CSS, the CSS must be backwards-compatible with old HTML. This requires a lot of care and additional awkward testing and causes major issues when not done carefully enough (e.g. bug 42452), and sometimes just isn't possible at all unless some transitional hacks are inserted (e.g. bug 46947). Luckily this isn't an issue for most third-party wikis, as `php update.php` after upgrade purges the cache entirely. I'm proposing adding another class to body, skintimestamp-MMDD, where MMDD is the year, month and day of the time that given skin's HTML was last modified in an incompatible way. Day should be enough granularity to avoid conflicts while keeping the class name short enough. This can be easily done using the addToBodyAttributes() method of the Skin class. The timestamp would be updated manually by whoever is making those changes, and the class could be used in the CSS to only apply new styles to newly generated HTML. Older styles could be simply left intact, and then removed after enough time has passed. If multiple incompatible changes are ever done in overlapping time periods, the successive ones would include updates to the old new styles to use both the new and old class. Thoughts? [Bug for this is https://bugzilla.wikimedia.org/show_bug.cgi?id=46956 , but let's keep the discussion here, please.] Thanks, Bartosz, for clearly and collegially stating this problem and your proposed solution! The problem sounds like a real problem. I don't see any particular blockers in your proposed solution, but I do want to watch out for one implementation detail. The timestamp would be updated manually by whoever is making those changes -- could we introduce some clever automation to propose an update every time a relevant file is touched or a particular automated test breaks? Otherwise we have to thoroughly educate authors and reviewers to always update this, which sounds tedious. Thanks again. -- Sumana Harihareswara Engineering Community Manager Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
