Re: [Wikitech-l] H.264
Maybe you want to read this article: http://xiphmont.livejournal.com/61927.html lbenedix m Do 31.10.2013 10:26, schrieb Brion Vibber: We're churning through some internal discussion with legal on if and how how this affects our potential options... Note that the specific thing announced there doesn't include a licensed AAC *audio* codec which would be required to generate audio and video+audio files playable on current browsers from Apple and Microsoft... so while an interesting development in the codec wars, we don't expect it to immediately change much for us. -- brion On Thu, Oct 31, 2013 at 2:10 AM, Magnus Manske magnusman...@googlemail.comwrote: http://gigaom.com/2013/10/30/mozilla-will-add-h-264-to-firefox-as-cisco-makes-eleventh-hour-push-for-webrtcs-future/?t=t So, should we support this format now? (not advocating, just curious) ___ 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] History of User rights and groups
Hi, is there an api-endpoint for this: http://en.wikipedia.org/w/index.php?title=Special%3ALogtype=rightsuser=page=User%3AX!year=month=-1tagfilter= Or is scraping this site the only way to get the history of user rights and groups? Lukas Benedix ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Hackathon idea: How about a live bug triage and code review hour ?
This is an excellent idea! My Extension got a lot of attention for about one week before it disappeared below radar level… https://gerrit.wikimedia.org/r/#/c/50004 LB Am Di 21.05.2013 22:28, schrieb Derk-Jan Hartman: I was thinking about the past hackathons and I realized that the interaction with eachother is often the best way to learn during these events, it's so much quicker than using gerrit/bugzilla/email/IRC. I also remember that a lot of the time, we do a lot of informal review and assessment of problems during these events. This time we have a very nice How to get your code deployed on Wikimedia workshop. Perhaps in addition to that, it might be a nice idea to do a live office hour dedicated to bug assessment and code review ? People could submit bug reports and gerrit changesets (etherpad?) and then we pick one hour, where a group of us simply try to help people with these issues in any form. We'd have multiple disciplines and areas of expertise being able to chip in, which should be great for the attendees with why does no one pay attention to my bugreport/patch-issues. Does anyone else think something like that might be a nice idea ? We'd need to find a timeslot though, that's probably gonna be the hardest part. I'm guessing that many WMF folks will have quite a few meetings again. DJ ___ 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] How to get permission to view deleted revision information via API?
The researcher group has this right, too. Maybe this is an option for us.
I'm not sure about the procedure and requirements to become a member of
this group, so I copied Dario Taraborelli in this mail.
https://en.wikipedia.org/wiki/Special:ListGroupRights#researcher
https://en.wikipedia.org/wiki/Wikipedia:Researchers#Researcher
Lukas
Am Mi 08.05.2013 15:46, schrieb Chad:
On Wed, May 8, 2013 at 9:35 AM, Claudia Müller-Birn
c...@inf.fu-berlin.de wrote:
Hi all,
I don't know whether this is the correct mailing list to ask such question but
it is the one I am reading regularly…
Does anyone know about the adequate procedure to get permission to request
deleted revision information from the MediaWiki API?
I just stumbled over this problem...
{
servedby: mw1140,
error: {
code: drpermissiondenied,
info: You don't have permission to view deleted revision
information
}
}
For a personal wiki, this means you need the 'deletedhistory' and 'deletedtext'
permissions (which is by default assigned to the admin group).
On WMF wikis, this requires being an administrator (although I think there's
some exception for researchers handed out via Meta).
-Chad
___
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] Extensions History in enwiki
Hi,
I'm looking for the history of extension usage in enwiki. I asked for
that in the IRC and was told that all the information can be found in
the two files: CommonSettings.php and InitialiseSettings.php.
One of my main problems is that there are so many ways extensions get
included in the CommonSettings.php…
for example:
include( $IP . '/extensions/Renameuser/Renameuser.php' );
include( $IP/extensions/AntiBot/AntiBot.php );
include $IP . '/extensions/AntiSpoof/AntiSpoof.php';
include $IP/extensions/WikimediaMessages/WikimediaMessages.php;
require( $IP/extensions/Oversight/HideRevision.php );
require_once( $IP/extensions/LocalisationUpdate/LocalisationUpdate.php );
require $IP/extensions/UserDailyContribs/UserDailyContribs.php;
(I don't think this list is complete)
The next problem is that I have to look at the InitialiseSettings.php
for a lot of extensions:
CommonSettings:
if ( $wmgUserDailyContribs ) {
require $IP/extensions/UserDailyContribs/UserDailyContribs.php;
}
InitialiseSettings:
'wmgUserDailyContribs' = array(
'default' = true,
),
The other problem is getting all versions of these two files and
correlate them to figure out which extensions were live in enwiki.
Another idea was to look at the History of Special:Version
http://web.archive.org/web/20120126235208*/http://en.wikipedia.org/wiki/Special:Version
but I don't think the history there is complete (there is a big gap in
2007).
Can anyone help me creating a list like this for enwiki:
EXTENSION_NAME; DEPLOYMENT_DATE; REMOVAL_DATE;
kind regards,
Lukas
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Deploying alpha of VisualEditor to non-English Wikipedias
Am Mo 29.04.2013 10:09, schrieb Mathieu Stumpf: We should care because we care about all potential contributors, and we don't want to make discrimination based on gender, sexual orientation nor the browser available to them. SCNR: The VisualEditor is not working in IE6, which is used by 25%* of the chinese internet user… * [http://www.ie6countdown.com/] ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] GSoC proposals: Wikidata language fallback and conversion ( + one backup: category redirects )
What exactly is uselang=qqx doing? http://www.wikidata.org/wiki/Q567?uselang=qqx looks like this: http://lbenedix.monoceres.uberspace.de/screenshots/oojp8u26nl_(2013-04-28_17.13.54).png http://lbenedix.monoceres.uberspace.de/screenshots/oojp8u26nl_%282013-04-28_17.13.54%29.png Lukas Am So 28.04.2013 04:03, schrieb Daniel Friesen: We already have a way to handle that kind of thing with normal language fallbacks. uselang=qqx. Wikidata should be able to do something similar trivially. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] GSoC proposals: Wikidata language fallback and conversion ( + one backup: category redirects )
Okay… So uselang is not usable for Liangents proposal. An item could have the label only in en and the description only in en-ca... uselang=en would miss the one and uselang=en-ca the other… his solution would display en as well as en-ca for both (with the missing language highlighted in a not yet defined way) I still think that a gadget would be the best for his proposal… users could easily turn it off and modify it for their own needs. Lukas Am So 28.04.2013 18:11, schrieb Matthew Flaschen: On 04/28/2013 11:15 AM, Lukas Benedix wrote: What exactly is uselang=qqx doing? http://www.wikidata.org/wiki/Q567?uselang=qqx looks like this: http://lbenedix.monoceres.uberspace.de/screenshots/oojp8u26nl_(2013-04-28_17.13.54).png http://lbenedix.monoceres.uberspace.de/screenshots/oojp8u26nl_%282013-04-28_17.13.54%29.png uselang in general lets you temporarily display an interface with a different language. You can use it with regular languages (uselang=es, uselang=zh, etc.). However, uselang=qqx is special. It shows the keys (identifiers for a message) of the MW messages (https://www.mediawiki.org/wiki/Manual:System_messages) used in the page. 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] Deploying alpha of VisualEditor to non-English Wikipedias
I'm pretty sure the feedback is stored nowhere... I just made a test: http://www.youtube.com/watch?v=Zzt_2CBfTNI You can share your feedback on https://www.mediawiki.org/wiki/Project:VisualEditor/Feedback but 'visual editor' - 'review and save' - 'something is wrong' - 'report problem' is not working for me. Lukas Am Do 25.04.2013 19:27, schrieb Claudia Müller-Birn: Hi James, Great news! Is the already given feedback publicly available? If yes, where. Thank you. Claudia On Apr 25, 2013, at 7:09 PM, James Forrester jforres...@wikimedia.org wrote: On 18 April 2013 17:32, James Forrester jforres...@wikimedia.org wrote: TL;DR: VisualEditor will be deployed on 14 new Wikipedias next week as an opt-in alpha. Your assitance is requested to inform your wikis about this and help get the software translated. This is now done (for de, nl, fr, it, ru, es, sv, pl, ja, ar, he, hi, ko, and zh). Grateful for feedback, bug reports and suggestions of how we can improve the VisualEditor for you. Yours, -- James D. Forrester Product Manager, VisualEditor 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 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Deploying alpha of VisualEditor to non-English Wikipedias
I'm not a non-tech-user, but I don't like using bugzilla. here is the new bug: https://bugzilla.wikimedia.org/47755 btw: While testing the black-hole feedback-mechanism I found another issue with VisualEditor. There are lines marked as changed in the diff that I never touched: http://lbenedix.monoceres.uberspace.de/screenshots/tlv5b64zcj_(2013-04-26_23.41.46).png http://lbenedix.monoceres.uberspace.de/screenshots/tlv5b64zcj_%282013-04-26_23.41.46%29.png Is this a (known) bug? LB Am Fr 26.04.2013 20:49, schrieb Claudia Müller-Birn: On Apr 26, 2013, at 4:42 PM, K. Peachey p858sn...@gmail.com wrote: On Fri, Apr 26, 2013 at 11:23 PM, Lukas Benedix bene...@zedat.fu-berlin.de wrote: ... You can share your feedback on https://www.mediawiki.org/wiki/Project:VisualEditor/Feedback but 'visual editor' - 'review and save' - 'something is wrong' - 'report problem' is not working for me. You can report it straight into Bugzilla, As mentioned at the top of that page. Here is the direct link https://bugzilla.wikimedia.org/enter_bug.cgi?product=VisualEditorcomponent=General Well, that is correct. But my major concern are the non-tech-users and getting their opinion on the visual editor. As a non-experienced user I might click the link… and then I most likely have to create an account. Even though I take the time doing so, I have to understand the various drop-down menus in Bugzilla - challenging. I guess, I would be stressed out and give up before sending the feedback, which is a pity. Don't get me wrong, I think the visual editor is great. I am just thinking aloud and wondering about this and that... Anyway, Bugzilla works great for me :) ___ 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] Gadget-Reviews
Hi, Is there any written policy about the review-process for Gadgets? For Extensions I found a document, that says an Extension should: get a design review, be internationalized, get a code review and finally get a deployment review. [https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment] I can't find any rules like this for Gadgets, but I see lot's of Gadgets set default in several Wikis. I think Gadgets can be designed badly and have security flaws as well as Extensions… so there shouldn't there exists some review process? best regards, Lukas ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Gadget-Reviews
Am Mo 15.04.2013 13:38, schrieb Bartosz Dziewoński: On Mon, 15 Apr 2013 13:31:13 +0200, Lukas Benedix bene...@zedat.fu-berlin.de wrote: I can't find any rules like this for Gadgets, but I see lot's of Gadgets set default in several Wikis. I think Gadgets can be designed badly and have security flaws as well as Extensions… so there shouldn't there exists some review process? There should. But it's impossible in practice, as the gadgets are written by volunteers for other volunteers, who often have very limited free time, and who often couldn't care less whether the code is nice or not if it works. I fully agree on that. There are to many Gadgets to review all of them, but I think there should be a design- and codereview at least before a Gadget is set to default. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Clicktracking being phased out
to cut out this defect of webkit with css: https://github.com/madrobby/blink Lukas Am Fr 12.04.2013 14:12, schrieb Chad: On Fri, Apr 12, 2013 at 8:03 AM, Brian Wolff bawo...@gmail.com wrote: I took the liberty of adding a note to the extension page to say use the other extension instead. For the record, if anyone ever uses blink (or the equivalent code that actually gets through Sanitizer.php) on MW.org, a unicorn kills a kitten :P Think of the kittens, don't blink ;) Webkit doesn't support blink. Looks like Gecko may follow: http://developers.slashdot.org/story/13/04/09/1445233/gecko-may-drop-the-blink-tag So many kittens can now grow up ;-) -Chad ___ 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] UIFeedback extension
Hi, Thank you all for the comments in gerrit. I worked on all of them and I think the extension is much better by now. It would be great if you could have a second look on the extension to get it deployable sometime. I realized, that the time was too short for a whole review and changed the plans for my thesis, I removed the real-world testings from the study design. I really want to see a convenient feedback mechanism for future mediawiki developments. I hope that my extension could be a good start. There are some unanswered questions, such as the anonymous upload of the rendered screen shots, and room for improvement especially at the customizability of the feedback forms and the special page with all given feedback. kind regards Lukas Benedix Am Mi 13.03.2013 01:28, schrieb Sumana Harihareswara: On 03/12/2013 07:37 PM, Lukas Benedix wrote: Hi there! I am Lukas Benedix, a student of computer science at the Freie Universität Berlin in Germany. In cooperation with the Wikidata developer team, I’m currently working on my bachelor thesis about usability testing in open source software projects and I’d like to provide the Wikidata community my developed feedback mechanisms (only as a test). Wikidata is a very active, emerging project which is why I think it’s a great platform for my project. And now here's the problem: The deadline of my bachelor thesis is approaching soon. The test is designed to run for two weeks and I unfortunately underestimated how much time it needs to get a review for my extension before deployment. Is it possible to accelerate that review process somehow? The extension is in gerrit (https://gerrit.wikimedia.org/r/#/c/50004) Do you have any advice what I can do? For further information about my project: Here's a little description I wrote for the Wikidata community: http://www.wikidata.org/wiki/User:Lbenedix/UIFeedback Best regards, Lukas Benedix Lukas, can you give more specifics regarding your deadline? A variety of people would have to help you get through all the steps of https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment and so it might not be feasible to get all these things done in time. :( In that case you should possibly consider setting up a Wikidata variant in Wikimedia Labs -- https://wikitech.wikimedia.org/ . ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Using the File-Upload-Api - Followup to: A new feedback extension - review urgently needed
Hi, with the help from User:Hoo_man, User:Danwe and other great people in the IRC I solved this problem. the upload is done completely in Javascript now; sending the request to the FileuploadApi. One Problem is that the extension should give users the option to send their feedback privately. But the FileuploadApi requires an edittoken, so each upload can be correlated with the uploading user. Do you have any idea how to solve this problem? I thougt about creating a fake-user only for the fileupload. best regards Lukas Am Do 14.03.2013 12:31, schrieb Lukas Benedix: Hi, Thanks for the many comments on my extensions in gerrit. By now I handled most of them, but I have a big problem with the image-upload when creting the API module that should replace my shabby SpecialPage API. I think that I could use mediawikis fileupload api (http://www.mediawiki.org/wiki/API:Upload). The problem is, that I have no idea how to start. I need the connection between the given feedback and the screenshot. By now the rendered screenshot is inside the POST-Request as base64 encoded binary data and written to the same table as the feedback. best regards, Lukas Am Mi 13.03.2013 00:37, schrieb Lukas Benedix: Hi there! I am Lukas Benedix, a student of computer science at the Freie Universität Berlin in Germany. In cooperation with the Wikidata developer team, I’m currently working on my bachelor thesis about usability testing in open source software projects and I’d like to provide the Wikidata community my developed feedback mechanisms (only as a test). Wikidata is a very active, emerging project which is why I think it’s a great platform for my project. And now here's the problem: The deadline of my bachelor thesis is approaching soon. The test is designed to run for two weeks and I unfortunately underestimated how much time it needs to get a review for my extension before deployment. Is it possible to accelerate that review process somehow? The extension is in gerrit (https://gerrit.wikimedia.org/r/#/c/50004) Do you have any advice what I can do? For further information about my project: Here's a little description I wrote for the Wikidata community: http://www.wikidata.org/wiki/User:Lbenedix/UIFeedback Best regards, Lukas Benedix ___ 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] Using the File-Upload-Api - Followup to: A new feedback extension - review urgently needed
Hi, Thanks for the many comments on my extensions in gerrit. By now I handled most of them, but I have a big problem with the image-upload when creting the API module that should replace my shabby SpecialPage API. I think that I could use mediawikis fileupload api (http://www.mediawiki.org/wiki/API:Upload). The problem is, that I have no idea how to start. I need the connection between the given feedback and the screenshot. By now the rendered screenshot is inside the POST-Request as base64 encoded binary data and written to the same table as the feedback. best regards, Lukas Am Mi 13.03.2013 00:37, schrieb Lukas Benedix: Hi there! I am Lukas Benedix, a student of computer science at the Freie Universität Berlin in Germany. In cooperation with the Wikidata developer team, I’m currently working on my bachelor thesis about usability testing in open source software projects and I’d like to provide the Wikidata community my developed feedback mechanisms (only as a test). Wikidata is a very active, emerging project which is why I think it’s a great platform for my project. And now here's the problem: The deadline of my bachelor thesis is approaching soon. The test is designed to run for two weeks and I unfortunately underestimated how much time it needs to get a review for my extension before deployment. Is it possible to accelerate that review process somehow? The extension is in gerrit (https://gerrit.wikimedia.org/r/#/c/50004) Do you have any advice what I can do? For further information about my project: Here's a little description I wrote for the Wikidata community: http://www.wikidata.org/wiki/User:Lbenedix/UIFeedback Best regards, Lukas Benedix ___ 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] A new feedback extension - review urgently needed
Hi there! I am Lukas Benedix, a student of computer science at the Freie Universität Berlin in Germany. In cooperation with the Wikidata developer team, I’m currently working on my bachelor thesis about usability testing in open source software projects and I’d like to provide the Wikidata community my developed feedback mechanisms (only as a test). Wikidata is a very active, emerging project which is why I think it’s a great platform for my project. And now here's the problem: The deadline of my bachelor thesis is approaching soon. The test is designed to run for two weeks and I unfortunately underestimated how much time it needs to get a review for my extension before deployment. Is it possible to accelerate that review process somehow? The extension is in gerrit (https://gerrit.wikimedia.org/r/#/c/50004) Do you have any advice what I can do? For further information about my project: Here's a little description I wrote for the Wikidata community: http://www.wikidata.org/wiki/User:Lbenedix/UIFeedback Best regards, Lukas Benedix ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Tablepager
Hi, i have several questions about the TablePager-Class: * is it possible to change the styling of the tables? * * The default-style is blue (http://commons.wikimedia.org/wiki/File:Tablepager.PNG) * * all other Tables are grey (http://commons.wikimedia.org/wiki/File:Version.PNG) * is it possible to change the sort-order in a sortable tablepager-table? * * with function getDefaultSort() I can only sort in ascending order * is there some more documentation than: http://svn.wikimedia.org/doc/classTablePager.html ? LB ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
