Wikitech-l March 2012

wikitech-l@lists.wikimedia.org

155 participants
204 discussions

Start a nNew thread

Hackathon Berlin 2012
by Thomas Gries 24 Apr '12

24 Apr '12

Suggestion: git workshop and tutorial @ Hackathon Berlin 2012

7 8

Please register for the Berlin hackathon - June 1-3, 2012
by Sumana Harihareswara 19 Apr '12

19 Apr '12

I invite you to the yearly Berlin hackathon. It's 1-3 June and registration is now open. If you need financial assistance or help with hotel/hostel, just mention it in the registration form. https://wmberlin.eventbrite.com/ This is the premier event for the MediaWiki and Wikimedia technical community. We'll be hacking, designing, and socialising, primarily talking about Gadgets, the switch to Lua, Wikidata, and Wikimedia Labs. Our goals for the event are to bring 100-150 people together, with lots of people who have not attended such events before. User scripts, gadgets, API use, Toolserver, Wikimedia Labs, mobile, structured data, templates -- if you are into any of these things, we want you to come! Details: https://www.mediawiki.org/wiki/Berlin_Hackathon_2012 Thanks to Wikimedia Germany for hosting and coordinating this event. (Venue still to be determined.) -- Sumana Harihareswara Volunteer Development Coordinator Wikimedia Foundation

1 1

migration guide
by Stéphane ANCELOT 18 Apr '12

18 Apr '12

Hi ! I thank you all everybody for your nice job, mediawiki is a great platform. However, as you may know, we are some people to develop , contribute to some extensions, and every time I migrate my wiki setup to a new version, that looks like a nightmare !!! (mostly for the last 1.18.1). I have either to upgrade extensions or dive into php code to make it running with the new mediawiki release. But this time, with 1.18.1 I am worried, because I do not have an in deep knowledge of the mediawiki process. So, the next time, a release is delivered, please provide with it a migration guide for extensions !!!!! This will permit every developer to maintain in a fast and efficient way, most extensions !! And since we are all very good developers, I am pretty sure some people will be able to provide a helpful migrating utility (when only function name changes apply) .... Today, I am not able to participate or migrate the CKeditor to the 1.18.1 Release . Regards . S.Ancelot

3 2

MathJax scalable math rendering update for 1.19
by Brion Vibber 16 Apr '12

16 Apr '12

In the last few days I've updated the Math extension's experimental MathJax support to where it can actually be enabled by individual users. If all goes well with review I'd love to get this deployed soon so the math-heads can turn it on and check for lingering incompatibilities... MathJax [http://www.mathjax.org/] is a client-side JavaScript library for parsing TeX or MathML code and rendering it in just about any modern browser -- it even works back to IE 6! -- using webfonts and HTML/CSS, MathML, or SVG as available. Here's a sample page on a test wiki, copied from en.wikipedia: http://leuksman.com/mw/index.php/Alpha_compositing This update to the extension builds on Nageh's work setting up an earlier version of MathJax as a user script, plus some help from the MathJax devs on their mailing list. Thanks guys! Big advantages of this over our current server-side math rendering: * font size & baseline match up with surrounding text for inline equations! * subpixel antialiasing or high-dpi displays allow math to render more sharply at default size * scalable -- you can zoom in your browser and things stay sharp * printable -- printed output also stays sharp (some browsers have font issues with some modes; to be experimented with) * in-browser zoom & copy-paste helpers And of course: * a strong open-source community maintaining it, who are happy to help us with integration and any needed fixes * it's not ocaml ;) The additions to Math extension add a third 'MathJax' rendering mode which users can opt in to at Special:Preferences. This replaces the older HTML and MathML rendering modes that we already disabled in 1.19. In the future when we've worked out the kinks, we can turn that into the default, and continue to use it as a fallback renderer for non-JavaScript browsers. (A nicer math edit/preview tool would be awesome too, especially for confirming that things work in both renderers in the future!) Revs that'll need to be reviewed & deployed: https://www.mediawiki.org/wiki/Special:Code/MediaWiki/tag/mathjax WikiProject:Mathematics talk page section: https://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Mathematics#mathJa… -- brion

7 8

Run batch actions on gerrit changesets from the command line with DippyBird
by Arthur Richards 14 Apr '12

14 Apr '12

I whipped together a php script this afternoon that allows you to make arbitrary queries for Gerrit change sets, and then perform bulk actions on the resulting change sets from the command line. Currently it only supports doing a bulk 'submit' (with approve +2 and verify +1), but it won't take much to add in other things (like abandon, verify, approve, etc). Take a look and feel free to comment/make changes: http://svn.wikimedia.org/viewvc/mediawiki/trunk/tools/gerrit-dippybird/dipp… -- Arthur Richards Software Engineer, Mobile [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687

4 5

Gerrit bots notification
by Antoine Musso 13 Apr '12

13 Apr '12

Hello, Whenever an action is made in Gerrit, a notification is sent to some IRC channels. Previously we had to map each project to an IRC channel fall backing to #mediawiki. I have enhanced the python script to support wildcard when filtering on Gerrit project name. Leslie Carr has deployed the changes some minutes ago, and now: projects from: - analytics and integrations are sent to #wikimedia-dev - operations are sent to #wikimedia-operations - labs to #wikimedia-labs - mediawiki and mediawiki extensions to #mediawiki Default is still #mediawiki If someone need more specific rules, you should tweak the filenames dictionary in templates/gerrit/hookconfig.py.erb . As an example, we might want to send MobileFrontend notifications to #wikimedia-mobile . -- Antoine "hashar" Musso

5 7

Fwd: Chennai Unofficial Wikimedia Hackathon Report
by Yuvi Panda 12 Apr '12

12 Apr '12

Thought this would be interesting to wikitech-l. ---------- Forwarded message ---------- From: Yuvi Panda <yuvipanda(a)gmail.com> Date: Tue, Mar 27, 2012 at 1:47 PM Subject: Chennai Unofficial Wikimedia Hackathon Report To: "Discussion list on Indian language projects of Wikimedia." <wikimediaindia-l(a)lists.wikimedia.org> The Chennai Unofficial Wikimedia Hackathon Report TL;DR: 13 completed hacks, including 2 core mediawiki patches, 3 tawiki userscript updates and 2 new deployed tools. It was super awesome and super productive! The 'Unofficial' Chennai Wikimedia Hackathon(http://www.mediawiki.org/wiki/Chennai_Hackathon_March_2012) happened on Saturday, March 17 2012 at the Thoughtworks office in Chennai. It was a one day, 8 hour event focusing on getting people together to hack on stuff related to all Wikimedia projects - not just Mediawiki patches. The event started with us sailing past security reasonably easily, and getting setup with internet without a glitch. People trickled in and soon enough we had 21 people in there. Since this was a pure hackathon, there were no explicit tutorials or presentations. As people came in, we asked them what technologies/fields they are familiar with, and picked out an idea for them to work on from the Ideas List (http://www.mediawiki.org/wiki/Chennai_Hackathon_March_2012/Ideas). This took care of the biggest problem with hackathons with new people - half the day spent on figuring out what to work on, and when found, it is completely outside the domain of expertise of the people hacking on the idea. Talking together with them fast to pick an idea within 5 minutes that they can complete in the day fixed this problem and made sure people can concentrate on coding for the rest of the day. People started hacking, and just before lunch we made people come up and tell us what they were working on. We then broke for lunch and usual socialization happened over McDonalds burgers and Saravana Bhavan dosas. Hacking started soon after, and people were concentrating on getting their hacks done before the demo time. And we did have quite a few demos! Demos ===== Here's a short description of each of the demos, written purely in the order in which they were presented: 1. Wikiquotes via SMS By: @MadhuVishy and @YesKarthik What it does: Send a person name to a particular number, and you'll keep getting back quotes from that person. Works in similar semi-automated fashion as the DYKBot. Built on AppEngine + Python. Status: Deployed live! Send SMS '@wikiquote Gandhi' to 9243342000 to test it out! Has limited data right now, however. --- 2. API to Rotate Images (Mediawiki Core Patch) By: Vivek What it does: Adds an API method that can arbitrarily rotate images. Think of this as first step towards being able to rotate any image in commons with a single button instantly, without having to wait for a bot. Patch was attached to https://bugzilla.wikimedia.org/33186. Status: It was reviewed on that day itself (Thanks Reedy!). Vivek is now figuring out how to modify his patch so that it would be accepted into Mediawiki core. Vivek is also applying to work with Mediawiki for GSoC, so we will hopefully get a long term contributor :) --- 3. Find list of unique Tamil words in tawiki By: Shrinivasan T What it does: It took the entire tamil wikipedia dump and extracted all unique words out of it. About 1.3 million unique tamil words were extracted. Has multiple applications, including a tamil spell checker. Status: Code and the dataset live on github: https://github.com/tshrinivasan/tamil-wikipedia-word-list --- 4. Program to help record pronunciations for words in tawikt What it does: Simple python program that gives you a word, asks you to pronounce it and then uploads it to commons for being used in Wiktionary. Makes the process much more streamlined and faster. Status: Code available at: https://github.com/tshrinivasan/voice-recorder-for-tawictionary. Preliminary testing with his friends shows that easy to record 500 words in half an hour. Is currently blocked on figuring out a way to properly upload to commons --- 5. Translation of Gadgets/UserScripts to tawiki By: SuryaPrakash [[:ta:பயனர்:Surya_Prakash.S.A.]] What he did: Surya spent the day translating two gadgets into Tamil, so they can be used on tawiki. First is the 'Prove It' Reference addition tool (http://ta.wikipedia.org/wiki/Mediawiki:Gadget-ProveIt.js). The second one was the 'Speed Reader' extension that formats content into multiple columns for faster scanning (http://ta.wikipedia.org/wiki/Mediawiki:Gadget-TwoColumn.js). Last I checked, these are available for anyone with only tamil knowledge to use, so yay! (He also tried to localize Twinkle for Tamil, couldn't because of issues with the laptop he was using. --- 6. Structured database search over Wikipedia By: Ashwanth What it does: Built a tool that combined DBPedia and Wikipedia to allow you to search in a semantic way. We almost descended into madness with people searching for movies with Kamal and movies with Rajni (both provided accurate results, btw). Amazing search tool that made it super easy to query information in a natural way. Status: The code is available at https://github.com/ashwanthkumar/structured-wiki-search. Definitely would be awesome to see this deployed somewhere, so would be great if the community could come up with specific ideas on how to make this a specific cool tool. --- 7. Photo upload to commons by Email By: Ganesh What it does: Started with building a tool that will let you email a particular address with pictures + metadata in the body of the page, and it will be uploaded to commons. This was for the benefit of people with older outdated phones *cough*Logic*cough* who would like to use their phone's camera to contribute to commons, but can not due to technical limitations. Status: He wasn't able to get that to work during the hackathon - too many technical issues cropped up. However, he's *very* definitely interested in setting it up, and has made progress towards it. I hope someone from the community (perhaps people doing WLM?) should be able to get in touch with him to see if this tool could be developed further with a specific goal in mind. --- 8. Lightweight offline Wiki reader By: Feroze What it does: There is a project called qvido (http://projects.qi-hardware.com/index.php/p/qvido/) which was a 'lightweight' offline Wiki reader (compared to Kiwix, which is heavier). It has been abandoned for a while, however. Feroze took the time to revive the project, figure out how to build it (and wrote build instructions!) and also fixed a bug so that it can be used to demo showing offline Wiki navigation. He was able to demo it showing the Odiya Wikipedia dump offline, with working link navigation. Status: There exists a git repo (https://github.com/feroze/qvido) with the code + the build instructions. I hope that people interested in offline projects check this out and see if it can be made useful, and take this forward. --- 9. Patches to AssessmentBar By: gsathya What it does: AssessmentBar is a small widget/tool I'm building to make WP India assessments easier (at the request of User:AshLin. Stay tuned for an announcement in the next few days). Sathya spent time making the backend for it more scalable, so the same server can support multiple projects and concurrent users in a better way. Before that he was contemplating setting up a hidden Tor node for Wikipedia (he's a Tor core contributor) and then playing with data visualizations with WP data. Status: There is a pull request (https://github.com/yuvipanda/MadamHut/pull/2) that I need to merge :) --- 10. Parsing Movie data into a database By: Arunmozhi (Tecoholic) and Lavanya What it does: It scrapes the infoboxes of all movies from whatever category you give it and stores this into a database. This is harder than it sounds because parsing wikitext is similar to beating yourself up repeatedly in the head with a large trout. They managed to figure out a nice way to extract information from all Indian movie pages, and put it in a database for programmatic easy access later. Status: I've asked them to put the code up publicly somewhere, and since I believe Tecoholic is in this mailing list, he'll reply with the link :) These kinds of data scraping can be used to build very nice tools that show off how much information Wikipedia has, and perhaps also help people contribute back by editing information for their favorite movies. I hope the community comes up with a nice idea to utilize this, and takes this project forward to its ultimate destiny: A super sexy IMDB type site for Indian Movies with data sourced from Wikipedia (I can dream :D) --- 11. Random Good WP India article tool By: Shakti and Sharath What it does: It is a simple tool that shows you one B, A, GA or FA article every time you go there. The idea is to provide a usable service for people who want to accumulate lots of knowledge by randomly reading stuff, but only want good stuff (so stubs, etc are filtered out (unlike Special:Random)). I'll also note that neither of them had worked with any web service before the hackathon, nor with JSON, nor with the mediawiki API, yet were able to build and deploy this tool within the day. /me gives a virtual imaginary barnstar to either of them Status: It is currently deployed at http://srik.me/WPIndia. Everytime you hit that link, you'll get an article about India that the community has deemed 'good'. The source code is available (https://github.com/saki92/category-based-search). They are eager to do more hacks such as these, and I'm hoping that the community will find enough technical cool things for these enthusiastic volunteers to work on --- 12. Fix bugs on tawiki ShortURL gadget By: Bharath What it does: The short url service used in tawiki (tawp.in) is shown in the wiki via a gadget. It is not the most user friendly gadget - you need to right click and select copy. Bharath looked for a solution by which you could click it and it would copy to the clipboard, but did not find any that would work without flash. Hence he abandoned that and started figuring out easier ways of making that happen. He also fixed several bugs in the implementation of the gadget, and I expect it to get deployed soonish. Thanks to SrikanthLogic for helping him through the process. Status: Code is available at http://ta.wikipedia.org/wiki/%E0%AE%AA%E0%AE%AF%E0%AE%A9%E0%AE%B0%E0%AF%8D:…. He's still fixing things on the script. If the community needs people to come fix up their user scripts/gadgets, Bharath would be a willing (and awesome!) candidate! --- 13. Add 'My Uploads' to top bar along with My Contributions, etc (Mediawiki Core Patch) By: SrikanthLogic What it does: Not satisfied with being the organizer of the hackathon, Srikanth wanted to flex his programming muscles and spent time fixing a bug in core mediawiki (https://bugzilla.wikimedia.org/show_bug.cgi?id=30915). He spent a while digging around the proper way to do this, and managed to make a proper patch! Status: It has been committed in gerrit (currently unable to find a link). Should be merged in soon. Yay! Honorable Mentions =================== 1. WikiPronouncer By: Russel Nickson What it was supposed to do: Exactly like Shrini's tool to record word pronunciations and upload to commons, but written for Android so people could add prononciations on the go. Status: Code is available at https://github.com/russelnickson/pronouncer. He ran into technical issues with Android setup (it stops working completely if you look at it the wrong way), and was unable to complete this. I think this would still be a very useful tool, and hope someone from the community steps up to work with Russel and get this finished. --- 2. Wiktionary cross lingual statistics By: PranavRC What it was supposed to do: It was a statistical tool that generated statistics about how many words overlap between all indic languages in Wiktionary (as measured by interwiki links). Status: The code has been written (I've requested the author to put it up publicly, will update list when it is). It, however, requires a lot of time to be run. So validation by the community that such stats would be useful would, IMO, definitely give Pranav the impetus to finish it up and show us the pretty graphs :) So, in all, 13 demos were produced (+ 2 near misses). I think we can call this one a success, no? :) Next Steps ========== Where do we go from here? Random thoughts: 1. Geek retention - this is reasonably easy. If we keep feeding hackers interesting problems that affect a lot of people, they'll keep helping us out. Is it possible to have some sort of a 'tools required' or 'hacks required' or 'gadgets required' page/queue someplace where we can always direct hackers looking for interesting problems to? IMO Wikipedia is full of interesting technical problems, so this *should* be feasible. 2. Follow ups - this time, I am able to do this personally (small enough group). Clearly this will not scale. Do we have ideas/methods for following up with these people so that they stay with us? 3. More of these? This was pretty much a 'zero cost' event - stickers were the only 'cost'. A lot of places around the country would love to have their space used for a hackathon of sorts. Should we do more of these kind of 'Unofficial' hackathons? Thanks due (in random order) ============================ 1. Thoughtworks/BalajiDamodaran: He graciously hosted us at Thoughtworks. The biggest challenge for any hackathon is to find a nice place which understands what hackathons are, and provides what is considered the lifeblood of a hackathon - working WiFi. Balaji (@openbala) was incredibly awesome, and this entire thing would've not been possible at all without him and ThoughtWorks. 2. Dorai Thodla: He helped popularize the hackathon among the Chennai Geeks crowd, and acted as a sounding board at various important times. He also connected us with @openbala and enabled us to get the venue. Thanks! 3. Srikanth Lakshmanan: The hackathon was his idea, and he made sure it was executed in a nice way. He was the official 'organizer', and made sure that all logistics were taken care of. Once the event started, he was very helpful in helping people technically and in picking up ideas, while also hacking on his own patch. This event was, in essence, organized and run by him. He took an overnight trip from Hyderabad straight out of office just for this. Thanks for making this possible! 4. Shrini (aka the relentless forwarder): This event wouldn't have been as much a success without him either. Evangelism across multiple lists, adding a lot of ideas that could be done, helping the people there out technically at all times and writing two really good hacks - Thank you! I'm glad we get to keep you :) 5. Subhashish Panighrahi: For sending us stickers :D (And who all is involved in that logistical process too!) Most of all, this event was a success because of the quality and dedication of the people who turned up, giving up their Saturdays. Hope everyone who turned up had a nice time :) I am personally in touch with most of them, and I also have their email address, phone number *and* permission to contact them again. If anyone here thinks that they liked one of the hacks and want to take it further, please contact me (User:Yuvipanda on Mediawiki.org or yuvipanda(a)gmail.com) and I'll get you people in touch. If there is a more accepted, standard way of handling this type of private information, please let me know as well! Thanks! - Yuvi Panda T http://yuvi.in -- Yuvi Panda T http://yuvi.in/blog

3 2

first Wikidata office hour on IRC
by Lydia Pintscher 09 Apr '12

09 Apr '12

Hi everyone! Next week the Wikidata team will be complete and start working at full speed. Finally! \o/ I will be holding the first round of Wikidata office hours next week. You're all invited to ask questions and discuss. If you can't attend there will be logs. * 4. April, German, in #wikimedia-wikidata on freenode, 4:30pm UTC (see http://www.timeanddate.com/worldclock/fixedtime.html?msg=Wikidata+Office+Ho… for different time zones) * 5. April, English, in #wikimedia-wikidata on freenode, 4:30pm UTC (see http://www.timeanddate.com/worldclock/fixedtime.html?msg=Wikidata+Office+Ho… for different time zones) I plan to offer these regularly. My (virtual) door is open outside these office hours as well of course ;-) Cheers Lydia http://meta.wikimedia.org/wiki/Wikidata -- Lydia Pintscher - http://about.me/lydia.pintscher Community Communications for Wikidata Wikimedia Deutschland e.V. Eisenacher Straße 2 10777 Berlin www.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.

3 3

Localisation commits status update
by Niklas Laxström 08 Apr '12

08 Apr '12

Good $localtime from translatewiki.net. I have been working with Chad and Antoine to resume the daily translation updates from translatewiki.net after the partial git migration of MediaWiki. We now have scripts that enable twn staff to * create clones of mediawiki core (with four branches: master 1.19 1.18 1.17) * create clones or all mediawiki extensions (both from svn and git, git taking precedence over git) * update those to latest versions * export translations * commit exported translations TL;DR: repo [create|update|export|commit] [mediawiki|mediawiki-extensions|...] The commmits for git will use the l10n-bot commit account. Commits for svn will continue to happen with our personal accounts. As you know every extension is now a separate git repository, there will be LOTS of commits instead of just one in a day. There are few remaining issues: * automatic merging of translation commits [BLOCKER] * not spamming your inbox with translation update commits * pretty formatting of core message files [BLOCKER] Now the last issue is something I want your opinion on: Is it an issue if we drop pretty formatting of non-English message files? If it is an issue, I request your help to make the maintenance/language/rebuildLanguage.php script to support arbitrary location instead of just the current wiki installation. If it is not an issue, the first diffs will be big because of the change, but remaining ones will be small as usual. -Niklas -- Niklas Laxström

5 5

Growing our testing, bug reporting, & triaging community
by Sumana Harihareswara 07 Apr '12

07 Apr '12

Summary: Chris McMahon is following up on improving Labs as a testing environment, improving continuous integration, and learning from how mobile gets and uses bug reports. Alolita and I are gathering data about how our engineering teams currently take in bug reports from lots of communication media. A few of us just had a chat about some upcoming efforts to engage our community in systematic testing (QA) efforts -- see https://www.mediawiki.org/wiki/User_talk:Cmcmahon#Community_Testing.2FQA and http://www.mediawiki.org/wiki/Mobile_QA/Spec for the conversation-starter. I figured some folks on this list would be interested in some plans, ideas, and questions coming out of that. A non-comprehensive summary: * Chris thinks his biggest priority, to improve MediaWiki's testability overall, is to ensure Labs is a stable, robust, and consistent environment so it's reasonable to point a firehose of testing at the beta deployment cluster <http://labs.wikimedia.beta.wmflabs.org/> . Unless we ensure a consistent and clean environment, most of the bug reports will be the result of environment problems instead of the MediaWiki bugs we want to find. So that's what he's focusing most of his time on. (This limits the time he has available for manual testing of individual features, but he also makes time to work on editor engagement, Timed Media Handler testing, and a limited number of other key projects.) Of course automated testing is also key, so Chris is working with Antoine on deploying from Jenkins to the beta cluster -- see https://www.mediawiki.org/wiki/QA/testing and https://www.mediawiki.org/wiki/Thread:Talk:Continuous_integration/also_depl… . * Our mobile team has a pretty stable, if time-intensive, system set up to get tests of its apps. They release a new version of their app every 2 weeks. Several days beforehand, they release a beta. They email mobile-l, tweet, etc. to raise awareness, but the best way to actually get testers is to personalize the boilerplate email and send it personally to each of about 20 people who've shown interest in testing. It takes a few minutes to send those emails, and then 12-15 hours to respond to the feedback and dig into problems. Feedback and conversation usually comes from about 5 people out of that 20, and happens in IRC (so, it's not as easy to delegate, do asynchronously, point other people to, etc.). The mobile team also tries to cover some other feedback channels: https://www.mediawiki.org/wiki/User:Yuvipanda/Mobile_feedback_avenues Yuvi works on this 100% every release cycle, so it doesn't scale -- they couldn't really handle more testers if they came. Chris likes that the mobile team is clear and specific in directing its testers on what to test, and has reasonable constraints on time, number of testers, and test environment. For the next mobile release cycle (starting on April 6th) Chris will shadow Yuvi to see what he does and to start helping out. * The internationalisation/localisation team gets feedback (including bug reports and feature requests) through various channels (IRC, Village Pumps, Bugzilla, private email, Twitter, mailing lists, etc.), and it's time-intensive to gather, aggregate, triage, curate, and respond to it. Alolita is following up with the i18n team to get more details on that process -- how do they source feedback? Where do they get it, how do they aggregate it, and how much time does it take? I'll be following up with product managers to get similar step-by-step guides from other projects. That way we can figure out how much time it's taking, how to split up that workload among product managers and QA, and whether we can get some quick wins in systematizing this process and doing it smarter. (Separately from the feedback *aggregation* effort, various folks are investigating feedback *mechanisms* integrated into user-facing things. See https://www.mediawiki.org/wiki/Extension:MoodBar/Feedback for some thoughts on this.) * We really need help curating Bugzilla. Mark's Bug Squads can't come soon enough! :-) And we aim to grow testing leaders in the community. So if you're interested in stepping up and going from nitpicker to LEADER of nitpickers, we have some tasks ready for you. :D * Mozilla has a regular testing event https://quality.mozilla.org/category/events/month and lists bugs in an etherpad as they're reported: https://etherpad.mozilla.org/testday-20120329 . Time-limited test efforts like that are nice; if you can't constrain the number of channels people use to report things, you can at least constrain *time* and thus the amount of flow that comes through, so you can actually follow up more effectively! Chris doesn't think we quite have the social and technical infrastructure in place to properly support a testing event like this yet, but that's a goal. Thanks to Tomasz, Yuvi, Alolita, and Chris for contributing to this discussion. Additional reading: https://fedoraproject.org/wiki/User:Adamwill/It_boots_ship_it -- Sumana Harihareswara Volunteer Development Coordinator Wikimedia Foundation

1 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l March 2012