Re: [Wikitech-l] Simple Wikimedia tech timeline
Hello, On Mon, Jun 13, 2016 at 4:20 AM, Johan Jönsson <jjons...@wikimedia.org> wrote: > > Something I've been looking for, and eventually realized doesn't > exist, is a simple timeline of technology on Wikimedia wikis. I think > it'd be very useful to have a simple list, to give editors a chance to > understand how the wikis have developed over the years. > > I've started one here: > https://meta.wikimedia.org/wiki/User:Johan_(WMF)/Timeline As with many things in the Wikiverse, the problem is rarely that something doesn't exist, but that we have multiple (outdated) versions of it :) On Mon, Jun 13, 2016 at 7:09 AM, Bahodir Mansurov <bmansu...@wikimedia.org> wrote: > Here is some info http://www.aosabook.org/en/mediawiki.html Nice to see this being useful! In addition, see also: * https://meta.wikimedia.org/wiki/MediaWiki_timeline * https://meta.wikimedia.org/wiki/Site_operations_timeline which I started putting together a few years ago as part of https://commons.wikimedia.org/wiki/File:WikipediaTimeline.png . Some day™ I'll make an updated version, but in the meantime help is certainly welcome to curate the timeline content. -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] mattermost.org (open source Slack alternative)
Hi, On Thu, Oct 22, 2015 at 7:20 AM, Brian Gerstle <bgers...@wikimedia.org> wrote: > Mattermost.org > I'm curious what others about it as a potential chat client* and as an open > source project in general. On the subject of "open-source Slack alternatives" someone also mentioned Zulip recently: https://www.zulip.org/ https://zulip.com/integrations/ -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering report, December 2014
Hi, The report covering Wikimedia engineering activities in December 2014 is now available: https://www.mediawiki.org/wiki/Wikimedia_Engineering/Report/2014/December Also, note that the format of the report is changing. Consistently with the WMF-wide switch to quarterly reviews announced a few months ago ( https://lists.wikimedia.org/pipermail/wikimediaannounce-l/2014-November/001005.html ), Engineering and Product staff will now be reporting on a quarterly basis. To get more frequent updates, you can follow ongoing work by watching the master roadmap in Phabricator, where all major work is organized: https://phabricator.wikimedia.org/tag/roadmap/ (To watch or subscribe, see https://phabricator.wikimedia.org/project/profile/1109/ ) The roadmap links to specific tasks and projects that you can also subscribe to in Phabricator if you don't want to watch the whole roadmap. Anyone should feel free to request an update about a task by adding a comment there. Remember that you are also encouraged to subscribe to the weekly technical newsletter, to get a high-level summary of technical changes that may impact your experience: https://meta.wikimedia.org/wiki/Tech/News I hope that this new process will allow you to follow engineering and product work more closely and in more timely manner. Let me know if you have any questions. -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Who moved my cheese?
Hi, On Thu, Feb 12, 2015 at 7:24 AM, C. Scott Ananian canan...@wikimedia.org wrote: In addition to (even better than?) a breaking-changes list would be for every piece of software we distribute to have a very prominent ChangeLog (or RELEASE-NOTES) file, which is kept up to date. When you git pull and see a change to ChangeLog, that should be a clue to check out whether you need to update.php/npm install/composer update/etc. Mediawiki core is pretty good about this, but almost too much so -- the RELEASE-NOTES gets so big it's hard to see the latest thing that broke. For most projects it's best if the very top of the ChangeLog has the most recent breaking changes. We're currently having a discussion about how to better surface changes with noteworthy user impact, and we're considering using a Phabricator tag / project for this purpose. The same system could be adopted for changes with noteworthy developer impact: https://phabricator.wikimedia.org/T88468#1037411 -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Why there is no authentication mechanism for desktop applications
Hello, Le mercredi 11 février 2015, 16:59:45 Petr Bena a écrit : We have OAuth for browser based programs. But nothing for desktop applications that are being used by users. (Like AWB etc). It sounds pretty simple to me, so why we don't have anything like that? The reason currently given at https://www.mediawiki.org/wiki/OAuth/For_Developers#Intended_Users is: … not… Desktop applications (the Consumer Secret needs to be secret!) -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Tweet of site outage
Hi, Le jeudi 5 février 2015, 09:58:01 George Herbert a écrit : I saw a WMF tweet of a site outage (network?) around 9:30am Pacific time, by the time I could check now things seem ok on en Sites are mostly back up but there are still issues with login, so the Ops team hasn't had time to write a postmortem yet. -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering report, November 2014
Hi, The report covering Wikimedia engineering activities in November 2014 is now available: https://www.mediawiki.org/wiki/Wikimedia_Engineering/Report/2014/November -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering report, September 2014
appropriate hardware to handle the remaining wikis. We also implemented out significantly improved wikitext Regular Expression search. In October we've begun rolling out the wikitext Regular Expression search and received some of the hardware we need to finish cutting over the remaining wikis. We believe we'll get it all installed in October and cut the remaining wikis over in November. *SUL finalisation https://www.mediawiki.org/wiki/SUL_finalisation* [edit https://www.mediawiki.org/w/index.php?title=SUL_finalisation/statusveaction=edit ] In September, the team wrapped up the feature development for SUL finalisation. One part of the work (the steward end of the rename request form) is outstanding and will be finished in October. In October, the team is planning to proceed into deployment and testing of the features. *Security auditing and response https://www.mediawiki.org/wiki/Security_auditing_and_response* [edit https://www.mediawiki.org/w/index.php?title=Security_auditing_and_response/statusveaction=edit ] We published the 1.23.4 security release, and completed review for the Graph and Imagemetrics extensions. Multimedia[edit https://www.mediawiki.org/w/index.php?title=Wikimedia_Engineering/Report/2014/Septemberveaction=editvesection=14 | edit source https://www.mediawiki.org/w/index.php?title=Wikimedia_Engineering/Report/2014/Septemberaction=editsection=14 ] *Multimedia https://www.mediawiki.org/wiki/Multimedia* [edit https://www.mediawiki.org/w/index.php?title=Multimedia/statusveaction=edit ] https://www.mediawiki.org/wiki/File:Media_Viewer_-_New_Design_-_Default_Lightbox.png Media Viewer's new user interface, with a 'More details' button. In September, the multimedia team developed and released a first round of new improvements https://www.mediawiki.org/wiki/Multimedia/Media_Viewer/Improvements to Media Viewer, based on feedback from our recent community consultation https://meta.wikimedia.org/wiki/Community_Engagement_(Product)/Media_Viewer_consultation and ongoing user research https://www.mediawiki.org/wiki/Media_Viewer_Research_Round_2_(August_2014) . These improvements aim to make Media Viewer easier to use by readers and casual editors, with these features: a more prominent More Details button https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/830, linking to the File: page; separate icons for Download https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/841 and Share or Embed https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/834 features; and an easier way to enlarge images by clicking on them https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/831. Next, we plan to work on an easier way to disable Media Viewer for personal use https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/836 and a caption or description right below the image https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/589. We would like to thank all the community members who suggested these improvements. Our research suggests that they offer a better user experience, that is both clearer and simpler. This month, we also ramped up the Structured Data https://commons.wikimedia.org/wiki/Commons:Structured_data project, in collaboration with community members and the Wikidata team https://www.wikidata.org/wiki/: in October, we will start developing a first prototype for a high-end API that can read and write machine-readable data on Wikimedia Commons, to be followed by a wider deployment in coming months. In parallel, the foundation is also launching a file metadata cleanup drive https://meta.wikimedia.org/wiki/File_metadata_cleanup_drive to add machine-readable attributions and licenses on files that lack them, spearheaded by Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillaume_(WMF). To learn more, join our Structured Data QA https://commons.wikimedia.org/wiki/Commons:Structured_data#Discussions on Thursday, October 16 at 18:00 UTC http://www.timeanddate.com/worldclock/fixedtime.html?msg=Structured+Data+IRC+discussioniso=20141016T18ah=1, for an office hours https://meta.wikimedia.org/wiki/IRC_office_hours#Upcoming_office_hours chat on #wikimedia-office irc://irc.freenode.net/wikimedia-officeconnect http://webchat.freenode.net/?channels=#wikimedia-office(Freenode IRC). We also continued our code refactoring for the UploadWizard https://www.mediawiki.org/wiki/UploadWizard, and started to collect metrics for an upload funnel analysis https://www.mediawiki.org/wiki/UploadWizard/Funnel_analysis, to find out how many users drop out at each step of the upload and where failure is occurring, so we can prioritize bug fixes. For more information about our work, join the multimedia mailing list https://lists.wikimedia.org/mailman/listinfo/multimedia. Engineering Community Team https://www.mediawiki.org/wiki/Engineering_Community_Team[edit https://www.mediawiki.org/w/index.php?title=Wikimedia_Engineering/Report/2014
[Wikitech-l] Wikimedia engineering report, October 2014
Hi, The report covering Wikimedia engineering activities in October 2014 is now available: https://www.mediawiki.org/wiki/Wikimedia_Engineering/Report/2014/October -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering report, August 2014
programs https://www.mediawiki.org/wiki/Mentorship_programs* All Google Summer of Code https://www.mediawiki.org/wiki/Google_Summer_of_Code_2014 and FOSS Outreach Program for Women https://www.mediawiki.org/wiki/FOSS_Outreach_Program_for_Women/Round_8were evaluated by their mentors as PASSED, although many were still waiting for completion, code reviews and merges. We hosted a wrap-up IRC meeting https://meta.wikimedia.org/wiki/GSoC_%26_FOSS_OPW_wrap-up_meeting with the participation of all teams except one. We are still waiting for some final reports from the interns. In the meantime, you can check their weekly reports: - Tools for mass migration of legacy translated wiki content https://www.mediawiki.org/wiki/Extension:Translate/Mass_migration_tools/Project_updates - Wikidata annotation tool https://www.mediawiki.org/wiki/Wikidata_annotation_tool/updates - Email bounce handling to MediaWiki with VERP https://www.mediawiki.org/wiki/VERP/GSOC_Progress_Rerport - Google Books, Internet Archive, Commons upload cycle https://www.mediawiki.org/wiki/Google_Books,_Internet_Archive,_Commons_upload_cycle/Progress - UniversalLanguageSelector fonts for Chinese wikis https://www.mediawiki.org/wiki/Extension:UniversalLanguageSelector/Fonts_for_Chinese_wikis#Weekly_Report - MassMessage page input list improvements https://www.mediawiki.org/wiki/Extension:MassMessage/Page_input_list_improvements/Progress_reports - Book management in Wikibooks/Wikisource https://meta.wikimedia.org/wiki/Book_management_2014/Progress - Parsoid-based online-detection of broken wikitext https://www.mediawiki.org/wiki/User:Hardik95/GSoC_2014_Progress_Report - Usability improvements for the Translate extension https://www.mediawiki.org/wiki/User:Kunalgrover05/Progress_Report - A modern, scalable and attractive skin for MediaWiki https://www.mediawiki.org/wiki/User:Jack_Phoenix/GSoC_2014 - Automatic cross-language screenshots for user documentation https://www.mediawiki.org/wiki/Automatic_cross-language_screenshots/progress - Separating skins from core MediaWiki https://www.mediawiki.org/wiki/Separating_skins_from_core_MediaWiki/Progress - Chemical Markup support for Wikimedia Commons https://www.mediawiki.org/wiki/Chemical_Markup_support_for_Wikimedia_Commons/Internship_Report - Improving URL citations on Wikimedia https://www.mediawiki.org/wiki/User:Mvolz/Weekly_Reports - Historical OpenStreetMap https://www.mediawiki.org/wiki/User:JaimeLyn/Weekly_Reports - Welcoming new contributors to Wikimedia Labs and Tool Labs https://www.mediawiki.org/wiki/Welcome_to_labs/Progress_Reports - Evaluating, documenting, and improving MediaWiki web API client libraries https://www.mediawiki.org/wiki/Evaluating_and_Improving_MediaWiki_web_API_client_libraries/Progress_Reports - Feed the Gnomes – Wikidata Outreach https://www.mediawiki.org/wiki/User:Thepwnco/OPW_Reporting - Template Matching for RDFIO https://www.mediawiki.org/wiki/Extension:RDFIO/Template_matching_for_RDFIO/Reports - Switching Semantic Forms Autocompletion to Select2 https://www.mediawiki.org/wiki/Extension:Semantic_Forms/Select2_for_autocompletion/Progress_Report - Catalogue for Mediawiki Extensions https://www.mediawiki.org/wiki/User:Adi.iiita/Gsoc2014/Report#Weekly_Report - Generic, efficient localisation update service https://www.mediawiki.org/wiki/Extension:LocalisationUpdate/LUv2/Updates . *Technical communications https://www.mediawiki.org/wiki/Technical_communications* In August, Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillaume_(WMF) attended the Wikimania conference and the associated hackathon. He gave a talk https://wikimania2014.wikimedia.org/wiki/Submissions/Tech_news about Tech News https://meta.wikimedia.org/wiki/Tech/News (video available on YouTube https://www.youtube.com/watch?v=rqGDTNkVgLIlist=UURXe4cgJPTVHcDH6ZGwOT3A#t=9m15s) and created a poster summarizing the talk. He also continued to write and distribute Tech News every week, and started to contribute to the Structured data https://commons.wikimedia.org/wiki/Commons:Structured_data project. *Volunteer coordination and outreach https://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach* We ran the Wikimania Hackathon https://wikimania2014.wikimedia.org/wiki/Hackathon in an unconference manner together with the Wikimania organizers. The event went well in a unique venue, and we are compiling a list of lessons learned to be applied in future events. Together with other former organizers of hackathons, we decided that the next Wikimedia Hackathon in Europe will be organized by Wikimedia France (details coming soon). Also at Wikimania, Quim Gil gave a talk about The Wikimedia Open Source Project and You https://wikimania2014.wikimedia.org/wiki/Submissions/The_Wikimedia_open_source_project_and_you (video https://www.youtube.com/watch?v=c5tJdQCnGWQlist
Re: [Wikitech-l] [Wikimedia-l] Invitation to beta-test HHVM
Hello, On Sat, Sep 20, 2014 at 9:32 PM, Rand McRanderson therands...@gmail.com wrote: Here is one idea. A dashboard of top level Wikimedia projects with statuses, estimates, and a key to terms. Or does this exist? There is https://www.mediawiki.org/wiki/Wikimedia_Engineering/Dashboard It doesn't have everything you mentioned, but we can build on it and improve it. -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering report, July 2014
/wiki/Welcome_to_labs/Progress_Reports - Evaluating, documenting, and improving MediaWiki web API client libraries https://www.mediawiki.org/wiki/Evaluating_and_Improving_MediaWiki_web_API_client_libraries/Progress_Reports - Feed the Gnomes – Wikidata Outreach https://www.mediawiki.org/wiki/User:Thepwnco/OPW_Reporting - Template Matching for RDFIO https://www.mediawiki.org/wiki/Extension:RDFIO/Template_matching_for_RDFIO/Reports - Switching Semantic Forms Autocompletion to Select2 https://www.mediawiki.org/wiki/Extension:Semantic_Forms/Select2_for_autocompletion/Progress_Report - Catalogue for Mediawiki Extensions https://www.mediawiki.org/wiki/User:Adi.iiita/Gsoc2014/Report#Weekly_Report - Generic, efficient localisation update service https://www.mediawiki.org/wiki/Extension:LocalisationUpdate/LUv2/Updates . *Technical communications https://www.mediawiki.org/wiki/Technical_communications* https://commons.wikimedia.org/wiki/File:Flesch_reading_ease_chart_for_Tech_News.svg Chart showing historical Flesch reading ease https://en.wikipedia.org/wiki/Flesch%E2%80%93Kincaid_readability_tests data for Tech News, a measure of the newsletter’s readability https://meta.wikimedia.org/wiki/Tech/News/Readability. Higher scores indicate material that is easier to read. A score of 60–70 corresponds to content easily understood by 13- to 15-year-old students. Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom collaborated with authors of the Education newsletter https://outreach.wikimedia.org/wiki/Education/Newsto set it up https://outreach.wikimedia.org/wiki/Education/Newsletter/Newsroom/Multilingual_message for multilingual delivery, using a script https://meta.wikimedia.org/wiki/Module:Assemble_multilingual_message similar to the one used for Tech News https://meta.wikimedia.org/wiki/Tech/News. He also wrote adetailed how-to https://meta.wikimedia.org/wiki/Newsletters/Translation to accompany the script for people who want to send a multilingual message across wikis. In preparation for the Wikimania session https://wikimania2014.wikimedia.org/wiki/Submissions/Tech_news about Tech News, he updated the readability https://meta.wikimedia.org/wiki/Tech/News/Readability andsubscribers https://meta.wikimedia.org/wiki/Tech/News/Subscribers metrics. He also continued to provide ongoing communications support https://www.mediawiki.org/wiki/Technical_communications/Tech_blog_activity for the engineering staff, and to prepare and distribute Tech News every week. *Volunteer coordination and outreach https://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach* We focused on the preparation of the Wikimania Hackathon https://wikimania2014.wikimedia.org/wiki/Hackathon, encouraging all registered participants to propose topics and sign up to interesting sessions. We also organized a QA session https://plus.google.com/events/c0fgci542f8cn58o606gng6avio with potential organizers of the Wikimedia Hackathon 2015. We organized two Tech Talks: *Hadoop and Beyond. An overview of Analytics infrastructure* https://plus.google.com/u/0/b/103470172168784626509/events/c53ho5esd0luccd09a1c30rlrmg and*HHVM in production: what that means for Wikimedia developers* https://plus.google.com/events/cp5mjf6jrihevtdje8lmu5hvm1k. More activities hosted in July can be found at Project:Calendar/2014/07 https://www.mediawiki.org/wiki/Project:Calendar/2014/07. *Architecture and Requests for comment process https://www.mediawiki.org/wiki/Architecture_process* Developers finished the security architecture guidelines https://www.mediawiki.org/wiki/Security_for_developers/Architecture, and discussed several requests for comment https://www.mediawiki.org/wiki/Requests_for_comment in online architecture meetings https://www.mediawiki.org/wiki/Architecture_meetings: - 2014-07-10 — Frontend standardization discussion https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-07-10 focusing onRequests for comment/Redo skin framework https://www.mediawiki.org/wiki/Requests_for_comment/Redo_skin_framework ; - 2014-07-16 — RfC discussion https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-07-16 focusing on Requests for comment/Vertical writing support https://www.mediawiki.org/wiki/Requests_for_comment/Vertical_writing_support ; - 2014-07-23 — RfC discussion https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-07-23 focusing on Requests for comment/Composer managed libraries for use on WMF cluster https://www.mediawiki.org/wiki/Requests_for_comment/Composer_managed_libraries_for_use_on_WMF_cluster, in which the architecture committee approved the RfC; - 2014-07-30 — RfC discussion https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-07-30 focusing on Requests for comment/CentralNotice Caching Overhaul – Frontend Proxy https://www.mediawiki.org/wiki/Requests_for_comment
Re: [Wikitech-l] Wikimedia engineering report, July 2014
On Tue, Aug 26, 2014 at 6:55 PM, Arthur Richards aricha...@wikimedia.org wrote: Not sure what the problem is but the report on mw.o is borked. See screenshot: This should now be fixed; Thank you for the bug report, and my apologies for the inconvenience :) -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering report, June 2014
support for Wikimedia Commons https://www.mediawiki.org/wiki/Chemical_Markup_support_for_Wikimedia_Commons/Internship_Report - Improving URL citations on Wikimedia https://www.mediawiki.org/wiki/User:Mvolz/Weekly_Reports - Historical OpenStreetMap https://www.mediawiki.org/wiki/User:JaimeLyn/Weekly_Reports - Welcoming new contributors to Wikimedia Labs and Tool Labs https://www.mediawiki.org/wiki/Welcome_to_labs/Progress_Reports - Evaluating, documenting, and improving MediaWiki web API client libraries https://www.mediawiki.org/wiki/Evaluating_and_Improving_MediaWiki_web_API_client_libraries/Progress_Reports - Feed the Gnomes – Wikidata Outreach https://www.mediawiki.org/wiki/User:Thepwnco/OPW_Reporting - Template Matching for RDFIO https://www.mediawiki.org/wiki/Extension:RDFIO/Template_matching_for_RDFIO/Reports - Switching Semantic Forms Autocompletion to Select2 https://www.mediawiki.org/wiki/Extension:Semantic_Forms/Select2_for_autocompletion/Progress_Report - Catalogue for Mediawiki Extensions https://www.mediawiki.org/wiki/User:Adi.iiita/Gsoc2014/Report#Weekly_Report - Generic, efficient localisation update service https://www.mediawiki.org/wiki/Extension:LocalisationUpdate/LUv2/Updates . *Technical communications https://www.mediawiki.org/wiki/Technical_communications* In addition to ongoing communications support https://www.mediawiki.org/wiki/Technical_communications/Tech_blog_activity for the engineering staff, Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom focused on information architecture of Wikimedia engineering activities. This notably involved reorganizing the Wikimedia Engineering https://www.mediawiki.org/wiki/Wikimedia_Engineering portal (now linked from mediawiki.org’s sidebar) and creating a status dashboard https://www.mediawiki.org/wiki/Wikimedia_Engineering/Dashboard that lists the status of all current activities hosted on mediawiki.org. The portal is now also cross-linked with the other main tech spaces (like Tech https://meta.wikimedia.org/wiki/Tech and Tech News https://meta.wikimedia.org/wiki/Tech/News) and team hubs. *Volunteer coordination and outreach https://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach* Volunteers and staff are beginning to add or express interest in topics for the 2014 Wikimania Hackathon in London. The WMUK team is working hard to finalize venue logistics so that we can schedule talks and sessions in specific rooms. Everything is on track for a successful (and very large!) Hackathon. Tech Talks held in June:*How, What, Why of WikiFont* https://plus.google.com/events/chpgv8usjd6dn38on07njjk28hg on June 12 and *A Few Python Tips* https://www.mediawiki.org/wiki/Meetings/2014-06-19 on June 19. A new process has been set up forvolunteers needing to sign an NDA https://wikitech.wikimedia.org/wiki/Volunteer_NDA in order to be granted special permissions in Wikimedia servers. On a similar note, we have started a project to implement a Trusted User Tool http://fab.wmflabs.org/project/view/40/ in Phabricator, in order to register editors of Wikimedia projects that have been granted special permissions after signing a community agreement. *Architecture and Requests for comment process https://www.mediawiki.org/wiki/Architecture_process* Developers had several meetings https://www.mediawiki.org/wiki/Architecture_meetings on IRC about architectural issues or Requests for comment https://www.mediawiki.org/wiki/Requests_for_comment: - 2014-06-02 — Discussion https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-06-02 of Requests for comment/Grid system https://www.mediawiki.org/wiki/Requests_for_comment/Grid_system; - 2014-06-11 — Discussion https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-06-11 of several RfCs (lightning round); - 2014-06-13 — Discussion https://www.mediawiki.org/wiki/Architecture_meetings/Security_guidelines_discussion_2014-06-13 of security guidelines draft https://www.mediawiki.org/wiki/Security_for_developers/Architecture; - 2014-06-20 — Discussion https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-06-20 of revamping MediaWiki’s skin systems: Trevor Parscal’s “Redo skin framework” https://www.mediawiki.org/wiki/Requests_for_comment/Redo_skin_framework and Bartosz Dziewoński’s “Separating skins from core MediaWiki” work https://bugzilla.wikimedia.org/show_bug.cgi?id=65748; - 2014-06-25 — Discussion http://lists.wikimedia.org/pipermail/wikitech-l/2014-June/077227.html of front-end and UX standardization https://www.mediawiki.org/wiki/UX_standardization. Analytics https://www.mediawiki.org/wiki/Analytics *Wikimetrics https://www.mediawiki.org/wiki/Analytics/Wikimetrics* To support Editor Engagement Vital Signs, the team has implemented a new metric: Newly Registered User. There is also a new backup system to preserve user’s
[Wikitech-l] Wikimedia engineering report, May 2014
,_Commons_upload_cycle/Progress - UniversalLanguageSelector fonts for Chinese wikis https://www.mediawiki.org/wiki/Extension:UniversalLanguageSelector/Fonts_for_Chinese_wikis#Weekly_Report - MassMessage page input list improvements https://www.mediawiki.org/wiki/Extension:MassMessage/Page_input_list_improvements/Progress_reports - Book management in Wikibooks/Wikisource https://meta.wikimedia.org/wiki/Book_management_2014/Progress - Parsoid-based online-detection of broken wikitext https://www.mediawiki.org/wiki/User:Hardik95/GSoC_2014_Progress_Report - Usability improvements for the Translate extension https://www.mediawiki.org/wiki/User:Kunalgrover05/Progress_Report - A modern, scalable and attractive skin for MediaWiki https://www.mediawiki.org/wiki/User:Jack_Phoenix/GSoC_2014 - Automatic cross-language screenshots for user documentation https://www.mediawiki.org/wiki/Automatic_cross-language_screenshots/progress - Separating skins from core MediaWiki https://www.mediawiki.org/wiki/Separating_skins_from_core_MediaWiki/Progress - Chemical Markup support for Wikimedia Commons https://www.mediawiki.org/wiki/Chemical_Markup_support_for_Wikimedia_Commons/Internship_Report - Improving URL citations on Wikimedia https://www.mediawiki.org/wiki/User:Mvolz/Weekly_Reports - Historical OpenStreetMap https://www.mediawiki.org/wiki/User:JaimeLyn/Weekly_Reports - Welcoming new contributors to Wikimedia Labs and Tool Labs https://www.mediawiki.org/wiki/Welcome_to_labs/Progress_Reports - Evaluating, documenting, and improving MediaWiki web API client libraries https://www.mediawiki.org/wiki/Evaluating_and_Improving_MediaWiki_web_API_client_libraries/Progress_Reports - Feed the Gnomes – Wikidata Outreach https://www.mediawiki.org/wiki/User:Thepwnco/OPW_Reporting - Template Matching for RDFIO https://www.mediawiki.org/wiki/Extension:RDFIO/Template_matching_for_RDFIO/Reports - Switching Semantic Forms Autocompletion to Select2 https://www.mediawiki.org/wiki/Extension:Semantic_Forms/Select2_for_autocompletion/Progress_Report - Catalogue for Mediawiki Extensions https://www.mediawiki.org/wiki/User:Adi.iiita/Gsoc2014/Report#Weekly_Report - Generic, efficient localisation update service https://www.mediawiki.org/wiki/Extension:LocalisationUpdate/LUv2/Updates . *Technical communications https://www.mediawiki.org/wiki/Technical_communications* In addition to ongoing communications support https://www.mediawiki.org/wiki/Technical_communications/Tech_blog_activity for the engineering staff, Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom mostly focused on improvements to the system of scripts and templates https://www.mediawiki.org/wiki/Category:Wikimedia_engineering_templates used to document Wikimedia engineering activities on mediawiki.org. Active and inactive projects can now be queried separately, which means that the list of projects that appears in the drop-down of the status helper gadget https://www.mediawiki.org/wiki/MediaWiki:Gadget-WmfProjectStatusHelper.js is much shorter, now only listing active projects. Guillaume also wrote a dedicated Lua module https://www.mediawiki.org/wiki/Module:Wikimedia_engineering to manipulate engineering activities automatically, in particular for theWikimedia Engineering https://www.mediawiki.org/wiki/Wikimedia_Engineering portal. It is now possible to query activities from a given team, and display them on any page in various formats. Using the module, the ever-outdated list of “current” activities on the portal was replaced by an automatically-generated list based on projects listed on team hubs. The module also allows to feature a random engineering activity on the portal. Other additions to the portal include the latest issue of Tech News https://meta.wikimedia.org/wiki/Tech/News(transcluded and automatically updated every week), as well as the first paragraph of the latest monthly engineering report (manually updated for now). Future improvements of the portal are expected to be mostly aesthetic. *Volunteer coordination and outreach https://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach* The Wikimedia Hackathon in Zürich https://www.mediawiki.org/wiki/Z%C3%BCrich_Hackathon_2014 was a success according to ad hoc feedback from the participants. A deeper review is expected to be published in July, after compiling the results of the survey. The main merit goes to Wikimedia CH for an efficient, warm, and flexible organization. We also announced a process to request the organization of Hackathons https://www.mediawiki.org/wiki/Hackathons. We had an intense calendar of events in May https://www.mediawiki.org/wiki/Project:Calendar/2014/05, including a Tech Talk about Elasticsearch https://plus.google.com/b/103470172168784626509/events/cokipb2senmmvkvdjif7aq55kac and a meetup in San Francisco on *Making Wikipedia Fast* https://plus.google.com/events
[Wikitech-l] Wikimedia engineering report, April 2014
and future Wikimedia engineering efforts. -- *This article was written collaboratively by Wikimedia engineers and managers. See revision history https://www.mediawiki.org/w/index.php?title=Wikimedia_engineering_report/2014/Aprilaction=history and associated status pages. A wiki version https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2014/April is also available.* -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [teampractices] RfC on Product Management Tools and Development Toolchain
Hi, On Tue, Apr 15, 2014 at 2:02 AM, Andre Klapper aklap...@wikimedia.org wrote: as previously announced [1], we've been facilitating a collective review of Wikimedia's current product management tools and development toolchain. https://www.mediawiki.org/wiki/Requests_for_comment/Phabricator The initial deadline for the RFC was yesterday. We now have a choice to make between closing the RFC, or leaving it open for another week to get more input. Imho it wouldn't hurt to extend the deadline by a week, but if you disagree, please comment on the talk page: https://www.mediawiki.org/wiki/Talk:Requests_for_comment/Phabricator#Shouldn.27t_we_close_this.3F Thanks! -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Wikitech-ambassadors] Subscribe to Tech News via a web feed
Hi, On Fri, Apr 18, 2014 at 4:17 PM, Tomasz W. Kozłowski twkozlow...@gmail.com wrote: Just dropping a short note that it is now finally possible to subscribe to the weekly Tech News bulletin[1] via a web feed to ensure a smooth, hassle-free delivery of every issue to a news aggregator of your choice. \o/ This is fantastic. Thank you so much, again :) You can subscribe to an Atom[2] or RSS[3] feed, which should deliver a new issue at 00:00 UTC every Monday. Small correction: the link for the Atom feed is https://meta.wikimedia.org/w/api.php?action=featuredfeedfeed=technewsfeedformat=atom -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [teampractices] RfC on Product Management Tools and Development Toolchain
Reminder: The next IRC discussion on this topic will be in 1 hour from now in #wikimedia-office on freenode. On Tue, Apr 15, 2014 at 2:02 AM, Andre Klapper aklap...@wikimedia.org wrote: Hi, as previously announced [1], we've been facilitating a collective review of Wikimedia's current product management tools and development toolchain. The most popular idea at the moment is to consolidate Wikimedia's product management and infrastructure tools (such as Bugzilla, Gerrit, RT, Mingle, Trello) into all-in-one Phabricator. We have therefore put together a Request for comment to bring this up for wider discussion. This discussion affects anyone who deals with bug reports, feature requests and code changes in Wikimedia, so it's critical that you test Phabricator for your own use and make your voice heard in the RFC: https://www.mediawiki.org/wiki/Requests_for_comment/Phabricator We're compiling a list of Frequently asked questions at https://www.mediawiki.org/wiki/Requests_for_comment/Phabricator/FAQ ; You're welcome to add more and help answer them :) We'll host a few IRC discussions while the RFC is running to help answer questions, etc. Our tentative times and dates are at https://www.mediawiki.org/wiki/Talk:Requests_for_comment/Phabricator#IRC_discussions -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] IRC Office Hour on Project Management Tools Review: Friday 28th, 17:00UTC
A quick reminder: This will take place in 30 minutes in #wikimedia-office . If all goes well, we'll even have Phabricator's lead developer around to help answer questions :) On Mon, Mar 24, 2014 at 6:53 PM, Andre Klapper aklap...@wikimedia.org wrote: Hi, Guillaume and I will be hosting an IRC office hour on March 28, 2014 (Friday) at 17:00 UTC / 10:00 PDT in #wikimedia-office on irc.freenode.net. We will quickly present the progress and status of the ongoing Project management tools review [1] and after that we are happy to answer your questions! See you at the IRC office hour! Thanks, andre [1] https://www.mediawiki.org/wiki/Project_management_tools/Review -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] IRC Office Hour on Project Management Tools Review: Friday 28th, 17:00UTC
Hi, On Mon, Mar 24, 2014 at 7:04 PM, Alolita Sharma asha...@wikimedia.org wrote: Are you planning to do a walkthrough of your findings on Phabricator in this review. I am interested in the tool's project management and roadmap functionality if any :-) The IRC discussion will be mostly that: a discussion. We'll briefly provide some context about the project management tools review, but we won't be doing a demo or walkthrough of Phabricator. Our goal is to raise awareness about the tools review, to make sure as many people as possible can look at the options, test them and provide feedback. Another goal will be to polish the upcoming RfC that we're drafting. If you'd like to learn more about Phabricator's project management and roadmap functionality, I invite you to test it live on the test instance at http://fab.wmflabs.org/ . Alternatively, you can also peruse http://phabricator.org/ and http://phabricator.org/tour/ . I strongly encourage everyone to do so before the IRC discussion, so we can all have a more informed chat about Phabricator and the other options currently under consideration. Also how long does this irc session run? 1 hour? We'll be there for an hour at least, yes, although the session may end before that if there are no more questions/comments. If we need to go longer, we'll address that then :) -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Fwd: Project management tools review: Help shorten the list of candidates
Hi all, If you haven't followed the teampractices@ list, here's an update on the Project management tools review that was started a couple months ago. We're still in the pre-RFC preparatory work, but if you're interested in this topic, we'd gladly welcome your help :) We're also happy to answer your questions. -- Forwarded message -- From: Guillaume Paumier gpaum...@wikimedia.org Date: Tue, Mar 4, 2014 at 9:35 AM Subject: Project management tools review: Help shorten the list of candidates To: A mailing list to discuss team practices in Wikimedia organizations teampracti...@lists.wikimedia.org Hi all, Thanks again for providing so much input during the consultation period ( https://www.mediawiki.org/wiki/Talk:Project_management_tools/Review ). It's been extremely useful to understand your respective needs and workflows. We've summarized all this input into consolidated requirements. The goal was to group similar needs to make it easier to identify the features we need across teams and individuals: https://www.mediawiki.org/wiki/Project_management_tools/Review/Requirements Some requirements are conflicting with each other and will require further discussion later, but overall we're pretty much in agreement regarding what we want (even if that's a five-legged unicorn). We've been diligent in including everything that was provided during the consultation. Nonetheless, please take a look at the list of requirements if you have a moment, to make sure we haven't missed anything important. We've also assembled a list of options, i.e. the possible outcomes of this review process. The options go from keeping the status quo to changing a single tool, to consolidating most tools into one. It's still very much a draft and nothing's final. If we've missed anything in that table, please be bold and edit it: https://www.mediawiki.org/wiki/Project_management_tools/Review/Options We've tried to keep the list inclusive, but now we'd like to shorten the list of options, so that the upcoming RFC can focus on the options that actually have a shot. If you're interested in helping with this, please take a look at the list of options and discuss them on the talk page: https://www.mediawiki.org/wiki/Talk:Project_management_tools/Review/Options#Discuss_options Basically, we want to move items from the Options under consideration section to the Unlikely options one. Ideally, we should keep no more than 2 or 3 candidates, to make the RFC easier. If you think an option is unavoidable (e.g. We absolutely must discuss replacing Trello by Pivotal Tracker), then say so on the talk page in the relevant section. Conversely, if you think there's no way we're using iceScrum, leave a comment on the talk page. We'll assess consensus collaboratively and hopefully get rid of unlikely options. This is a collaborative process: we need your help so others don't make decisions on your behalf. Please take a few minutes to review the options and give your opinion. It's Notavote; think of it as a sane version of RfD (you must be new around here?). Let us know if you have any questions and we'll do our best to answer :) Andre and Guillaume -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] February '14 appreciation thread
Greetings, On Wed, Feb 12, 2014 at 8:45 PM, Tomasz W. Kozlowski tom...@twkozlowski.net wrote: So, if you'd like to thank someone, now is a good time and opportunity to do so! I'd like to thank: * Tomasz Kozlowski / odder for all his amazing work on Tech News (OMG appreciation loop!); * Kunal Mehta / Legoktm for developing MassMessage, and MZMcBride for maintaining EdwardsBot before that; * Translators who relentlessly translate Tech news into a dozen languages every week-end; * Niklas Laxström and Siebrand Mazeland for developing the Translate extension, which has made content translation so much easier; * Community liaisons, tech ambassadors and LCA staff for voluntarily serving as 2-way lightning rods between users and developers; * Everyone who has ever added an item to Tech news; * Last but not least, Wikimedia employees for patiently enduring my monthly poking every time the engineering report needs to be put together. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering report, January 2014
on this!”https://bugzilla.wikimedia.org/show_bug.cgi?id=57648to be more descriptive. The link to the guided bug entry form at the top of the standard bug entry form now sets the already chosen product directlyhttps://bugzilla.wikimedia.org/show_bug.cgi?id=59886, saving you two clicks when you switch to the guided form. Work continued on preparing the Bugzilla 4.4 upgrade: Andre Klapper’s patches for porting custom changes from 4.2 to 4.4 were deployed on the Bugzilla test instance on Zirconium and tested, and Daniel Zahn fixed a problem with Bugzilla’s collectstats.pl https://bugzilla.wikimedia.org/show_bug.cgi?id=29203, so the 4.4 upgrade and server move will take place in February. Bug management documentation related, Andre added a “Situation specific information” section to the Triage guidehttps://www.mediawiki.org/wiki/Bug_management/How_to_triagedocumentation about purging and profiling. *Project management tools review https://www.mediawiki.org/wiki/Project_management_tools/Review* Andre Klapper reached out to the teampracticeshttps://lists.wikimedia.org/mailman/listinfo/teampracticesmailing list as well as individual stakeholders, asking users to share their workflow and needshttps://www.mediawiki.org/wiki/Talk:Project_management_tools/Reviewregarding project management and tracking tools. Guillaume Paumier summarized all that content into consolidated requirementshttps://www.mediawiki.org/wiki/Project_management_tools/Review/Requirements; those are now in the process of being compared to features offered by available tools, in order to assemble a shortlist of candidates for community discussion. *Mentorship programs https://www.mediawiki.org/wiki/Mentorship_programs* [image: Google Code-in 2013, the Wikimedia debut.pdf]https://commons.wikimedia.org/wiki/File:Google_Code-in_2013,_the_Wikimedia_debut.pdf https://commons.wikimedia.org/wiki/File:Google_Code-in_2013,_the_Wikimedia_debut.pdf Wikimedia’s first participation in the Google Code-Inhttps://www.mediawiki.org/wiki/Google_Code-Inprogram ended up with great success: 273 tasks completed by 46 students with the help of about 30 mentors. Theo Patt and Mateusz Maćkowski were selected winners for Wikimediahttp://google-opensource.blogspot.com/2014/01/google-code-in-2013-drumroll-please.html, and we sent a special mention to Mayank Madan. Round 7 of the FOSS Outreach Program for Womenhttps://www.mediawiki.org/wiki/Outreach_Program_for_Women/Round_7started and all projects are on track so far: - Compacting interlanguage linkshttps://www.mediawiki.org/wiki/User:Niharika/Project_Progress_Report#January_2014 - MediaWiki Homepage Redesignhttps://www.mediawiki.org/wiki/User:Monteirobrena/MediaWiki_Homepage_Redesign/Monthly_Reports#January - Complete the MediaWiki API development course on Codecademyhttps://www.mediawiki.org/wiki/User:Diwanshipandey/OPW_January_Report - Clean up Parsoid round-trip testing UIhttps://www.mediawiki.org/wiki/User:5xbe/OPW_Monthly_Progress_Reports#January - Clean up tracing/debugging/logging inside Parsoidhttps://www.mediawiki.org/wiki/User:Mariapacana/OPW_Progress_Report#January_2014 - UploadWizard: OSM Embeddinghttps://www.mediawiki.org/wiki/User:Inchikutty/OPW_Internship_Report#January Facebook Open Academy https://www.mediawiki.org/wiki/Facebook_Open_Academy‘s warm-up period saw a slow progress in the beginning of the projects. At the end it seemed that everybody was waiting for the official start at the kick-off in Facebook headquarters on February 7−9. *Technical communications https://www.mediawiki.org/wiki/Technical_communications* In January, Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillomwrapped up work on mentoring Google Code-in https://www.mediawiki.org/wiki/Google_Code-in students and continued to provide ongoing communications supporthttps://www.mediawiki.org/wiki/Technical_communications/Tech_blog_activityfor the engineering staff. He contributed to writing, simplifying, publishing and distributing the weekly technical newsletterhttps://meta.wikimedia.org/wiki/Tech/News, and published an in-depth articlehttps://blog.wikimedia.org/2014/01/07/tech-news-fighting-technical-information-overload-for-wikimedians/explaining the process by which the newsletter is put together every week. *Volunteer coordination and outreach https://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach* We helped organizing the Architecture Summit 2014https://www.mediawiki.org/wiki/Architecture_Summit_2014in San Francisco (January 23−24) and we got everything ready for FOSDEM https://www.mediawiki.org/wiki/Events/FOSDEM in Brussels (February 1−2). We continued working with the tech community metricshttps://www.mediawiki.org/wiki/Community_metricsaround two key performance indicators: who contributes codehttp://korma.wmflabs.org/browser/who_contributes_code.html, and the Gerrit review queuehttp://korma.wmflabs.org/browser/gerrit_review_queue.html . Analytics https://www.mediawiki.org/wiki/Analytics
[Wikitech-l] Wikimedia engineering report, December 2013
Bugzilla puppet code into a puppet modulehttps://gerrit.wikimedia.org/r/#/q/project:operations/puppet+topic:bugzilla+owner:dzahn+status:merged,n,zand automatically generating documentation on doc.wikimedia.orghttps://doc.wikimedia.org/puppet/classes/bugzilla/bugzilla.html. As part of this preparation, Daniel and Andre also eliminated nearly all Perl CPAN modules (in Bugzilla’s /lib subfolder) on the new server by using default distribution packages instead. Furthermore, Andre worked on a preliminary patch https://bugzilla.wikimedia.org/show_bug.cgi?id=22170#c27 to display some common queries on the Bugzilla front page. *Project management tools review https://www.mediawiki.org/wiki/Project_management_tools/Review* Andre Klapper and Guillaume Paumier kicked off an evaluation of Wikimedia’s project management toolshttps://www.mediawiki.org/wiki/Project_management_tools/Review. Guillaume prepared a consultation pagehttps://www.mediawiki.org/wiki/Talk:Project_management_tools/Reviewwith topics for stakeholders and improved it together with Andre. It will initially be sent to the teampracticeshttps://lists.wikimedia.org/mailman/listinfo/teampracticesmailing list and individual stakeholders. To facilitate getting input, talking to individual stakeholders via Hangouts and holding an IRC discussion https://meta.wikimedia.org/wiki/IRC_office_hours are also considered. *Mentorship programs https://www.mediawiki.org/wiki/Mentorship_programs* Wikimedia’s first participation in the Google Code-Inhttps://www.mediawiki.org/wiki/Google_Code-Inprogram required a lot of dedication from the ECT members, and about a dozen of mentors and other contributors helping creating and reviewing tasks. Students completed about 200 tasks. The GCI inertia and the lessons learned will help us organize a better gateway for new contributors, which was a main reason for us to join this program. We also believe that the experience acquired will help us make future editions as successful with less work. Round 7 of the FOSS Outreach Program for Womenhttps://www.mediawiki.org/wiki/Outreach_Program_for_Women/Round_7started and all projects and on track so far: - Compacting interlanguage linkshttps://www.mediawiki.org/wiki/User:Niharika/Project_Progress_Report#December_2013 . - MediaWiki Homepage Redesignhttps://www.mediawiki.org/wiki/User:Monteirobrena/MediaWiki_Homepage_Redesign/Monthly_Reports#December . - Complete mediawiki API development course on codecademyhttps://www.mediawiki.org/wiki/User:Diwanshipandey/OPW_Internship_Report#December_2013 . - Clean up Parsoid round-trip testing UIhttps://www.mediawiki.org/wiki/User:5xbe/OPW_Monthly_Progress_Reports#December_10th_-_31st_.28three_weeks.29 . - Clean up tracing/debugging/logging inside Parsoidhttps://www.mediawiki.org/wiki/User:Mariapacana/OPW_Progress_Report#December_2013 . - UploadWizard :OSM Embeddinghttps://www.mediawiki.org/wiki/User:Inchikutty/OPW_Internship_Report#December We joined Facebook Open Academyhttps://www.mediawiki.org/wiki/Facebook_Open_Academyalmost at the last minute thanks to a reminder from developer Tyler Romeo. Six projects were accepted, which will be developed by teams of university students during the first half of 2014: - Distributed cron replacementhttps://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Distributed_cron_replacement— Coren https://www.mediawiki.org/wiki/User:Coren - Cassandra backend for distributed round-trip test serverhttps://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Cassandra_backend_for_distributed_round-trip_test_server— Gabriel Wicke https://www.mediawiki.org/wiki/User:GWicke, Marc Ordinas i Llopishttps://www.mediawiki.org/wiki/User:Marcoil - Flow Right-To-Left language supporthttps://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Flow_Right-To-Left_language_support— S Page (WMF) https://www.mediawiki.org/wiki/User:S_Page_%28WMF%29 and Werdna https://www.mediawiki.org/wiki/User:Werdna - Flow Edit Filter integrationhttps://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Flow_Edit_Filter_integration— S Page (WMF) https://www.mediawiki.org/wiki/User:S_Page_%28WMF%29 and Werdna https://www.mediawiki.org/wiki/User:Werdna - OpenBadges https://www.mediawiki.org/wiki/OpenBadges and Personahttps://www.mediawiki.org/wiki/Extension:Personasupport for MediaWiki — Parent5446 https://www.mediawiki.org/wiki/User:Parent5446 and Qgilhttps://www.mediawiki.org/wiki/User:Qgil *Technical communications https://www.mediawiki.org/wiki/Technical_communications* In December, Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom‘s primary focus was on creating and assigning tasks for the Google Code-inhttps://www.mediawiki.org/wiki/Google_Code-inprogram, mentoring students and reviewing their work. They worked on writing discovery reportshttps://www.mediawiki.org/wiki/Category:Discovery_reports, adding TemplateData https
Re: [Wikitech-l] Wikimedia engineering report, December 2013
On Tue, Jan 21, 2014 at 12:07 PM, Guillaume Paumier gpaum...@wikimedia.org wrote: The report covering Wikimedia engineering activities in November 2013 is now available. s/November/December , obviously :) -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Please use sitenotice when a new version of software is deployed
Hi, On Fri, Dec 6, 2013 at 8:53 AM, Guillaume Paumier gpaum...@wikimedia.org wrote: I think the Tech news page makes it simple enough to get involved and contribute: https://meta.wikimedia.org/wiki/Tech/News#contribute ; We also have a reasonably-stable schedule, so now we just need more people to give a hand. I'm actually drafting an overview of how Tech news works behind the scenes; I'll share it on this list when it's out. As promised, here's the link to that post: https://blog.wikimedia.org/2014/01/07/tech-news-fighting-technical-information-overload-for-wikimedians/ -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering report, November 2013
in Google Code-In https://www.mediawiki.org/wiki/Google_Code-in. This includes supporting mentors and students by writing documentation and importing tasks. Code-related, Andre cleaned up Wikimedia Bugzilla's custom CSS by removing 16 CSS fileshttps://bugzilla.wikimedia.org/show_bug.cgi?id=54823with 6 lefthttps://git.wikimedia.org/tree/wikimedia%2Fbugzilla%2Fmodifications.git/HEAD/skins%2Fcontrib%2FWikimediato stay, prepared and tested patches for upgrading Wikimedia Bugzilla https://bugzilla.wikimedia.org/show_bug.cgi?id=49597#c5from version 4.2 to 4.4, updated the Greasemonkey triagescriptshttps://git.wikimedia.org/log/wikimedia%2Fbugzilla%2Ftriagescripts(e.g. stock answers to ping assignees), and sync'ed the WeeklyReport Bugzilla extension code https://gerrit.wikimedia.org/r/#/c/96479/ with upstream. WMF's Operations team installed new SSL certificateshttps://rt.wikimedia.org/Ticket/Display.html?id=5011for bugzilla.wikimedia.org. The shellpolicy keyword in Bugzilla was renamedhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49494to community-consensus-needed and the wikidata keyword was removed https://bugzilla.wikimedia.org/show_bug.cgi?id=56417. Furthermore, Andre created a draft for a Bugzilla etiquettehttps://www.mediawiki.org/wiki/Bug_management/Bugzilla_etiquette . *Mentorship programs https://www.mediawiki.org/wiki/Mentorship_programs* We started successfully Wikimedia's first participation in Google Code-Inhttps://www.mediawiki.org/wiki/Google_Code-In. Six candidates were selected as new interns at the FOSS Outreach Program for Women - Round 7https://www.mediawiki.org/wiki/Outreach_Program_for_Women/Round_7: - Anu G Enchackal https://www.mediawiki.org/wiki/User:Inchikutty - UploadWizard:OSM Map Embeddinghttps://www.mediawiki.org/wiki/User:Inchikutty/UploadWizard_OSM_Map_Embedding(mentored by Gergő Tisza https://www.mediawiki.org/wiki/User:Tgr) - Diwanshi Pandey https://www.mediawiki.org/wiki/User:Diwanshipandey - Complete the MediaWiki development course at Codecademyhttps://www.mediawiki.org/wiki/User:Diwanshipandey/OPW(Yuri Astrakhan https://www.mediawiki.org/wiki/User:Yurik) - Brena Monteiro https://www.mediawiki.org/wiki/User:Monteirobrena - mediawiki.org homepage redesign https://www.mediawiki.org/wiki/User:Monteirobrena/OPW(Heather Walls https://www.mediawiki.org/wiki/User:Heatherawalls and Quim Gilhttps://www.mediawiki.org/wiki/User:Qgil) - Be Birchall https://www.mediawiki.org/wiki/User:5xbe - Clean up Parsoid round-trip testing UI, including using a templating systemhttps://www.mediawiki.org/wiki/User:5xbe/Proposal(Marc Ordinas https://www.mediawiki.org/wiki/User:Marcoil and Subramanya Sastry https://www.mediawiki.org/wiki/User:Ssastry) - Maria Pacana https://www.mediawiki.org/wiki/User:Mariapacana - Clean up tracing/debugging/logging inside Parsoidhttps://www.mediawiki.org/wiki/User:Mariapacana/Application(Subramanya Sastry https://www.mediawiki.org/wiki/User:Ssastry and Arlo Breaulthttps://www.mediawiki.org/wiki/User:Arlolra) - Niharika Kohli https://www.mediawiki.org/wiki/User:Niharika - Compact interlanguage links as a beta featurehttps://www.mediawiki.org/wiki/User:Niharika/Compacted_Interlanguage_Links_as_a_beta_feature(Sucheta Ghoshal and Pau Giner) We also confirmed the participation of Wikimedia in the Facebook Open Academy https://www.mediawiki.org/wiki/Facebook_Open_Academy program. *Technical communications https://www.mediawiki.org/wiki/Technical_communications* In November, Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom's primary focus was on preparing for the Google Code-inhttps://www.mediawiki.org/wiki/Google_Code-inprogram, and mentoring students once the program started. In 2 weeks, 18 studentshttps://www.mediawiki.org/wiki/Technical_communications/Code-in/2013worked on writing discovery reports https://www.mediawiki.org/wiki/Category:Discovery_reports (candid essays from the perspective of newcomers to the Wikimedia technical community); among them, seven completed their task successfully. Guillaume also assembled and published the weekly technical newsletterhttps://meta.wikimedia.org/wiki/Tech/Newsand provided ongoing communications supporthttps://www.mediawiki.org/wiki/Technical_communications/Tech_blog_activityfor the engineering staff. *Volunteer coordination and outreach https://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach* Erik Moeller's talk The Wikipedia stack was accepted for the main track session at FOSDEM https://www.mediawiki.org/wiki/Events/FOSDEM. The call for proposals for the Wikis devroom at FOSDEMhttps://www.mediawiki.org/wiki/Events/FOSDEMwas extended until December 15. Wikimedia applied for a stand. A Request for Proposals for a technical writer contractorhttp://lists.wikimedia.org/pipermail/wikitech-l/2013-November/073077.htmlwas also sent. Last, we helped establishing a routine around Architecture meetings https://www.mediawiki.org/wiki/Architecture_meetings
Re: [Wikitech-l] Please use sitenotice when a new version of software is deployed
On Fri, Dec 6, 2013 at 9:31 AM, Amir E. Aharoni amir.ahar...@mail.huji.ac.il wrote: * How to get developers not to forget to write that. Quim, Guillaume - ideas on how to improve it? There's already a reminder at the top of https://wikitech.wikimedia.org/wiki/Deployments , and Greg does a great job at highlighting the major changes that are going to be deployed every week (which are then included into tech news). Maybe we should add a similar one to the code review checklist? https://www.mediawiki.org/wiki/Gerrit/Code_review#Review_checklist I'm open to other suggestions. -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Please use sitenotice when a new version of software is deployed
On Fri, Dec 6, 2013 at 9:30 AM, John Vandenberg jay...@gmail.com wrote: How true. Alex asked because of a major upgrade problem on Wikisource which interrupted almost everyone. See wikisource-l for details. I think there are times when a community would like a mass notice of some sort, and it will differ based on the project and community size and the likely impact of the upgrade. Agreed; while Tech news can help communicate general technical news to Wikimedians, it isn't supposed to be a substitute for targeted communication with specific wikis or language communities. Ultimately, it's the responsibility of the developer (or their product manager / community liaison if they're lucky enough to have one) to make sure users are properly informed of a major technical change they've made. I'm also available to support developers who need help disseminating such information, but I can't do that unless someone asks :) -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Please use sitenotice when a new version of software is deployed
Hi, On Thu, Dec 5, 2013 at 10:22 PM, Brian Wolff bawo...@gmail.com wrote: As it stands we don't really summarize changes very well, which is a prerequisite for telling people about changes. Occasionally changes make it to Tech/news, but that seems sporadic. snip I think the best way forward would be to more accurately describe upcoming changes on tech/news. Once we actually have a user-readable summary of actual changes that are happening, then we could have a more reasonable discussion about how to get the information into people who care's hands, without spamming people who don't. Of course maintaining tech/news would probably require more effort being put towards it then is currently done, which requires someone (or multiple someones) to actually do so. Yep. Most of the limitations of Tech News stem from the fact that it's largely a one-man effort, which means (among other things) that things get missed. As for the accurate description part, it's a difficult balance to strike between tech-savvy readers who would understand accurate (but complex terms), and readers without deep technical expertise who need things to be explained more simply (and maybe slightly inaccurately). On top of that, we also need to facilitate the work of translators by avoiding colloquialisms, etc. I think the Tech news page makes it simple enough to get involved and contribute: https://meta.wikimedia.org/wiki/Tech/News#contribute ; We also have a reasonably-stable schedule, so now we just need more people to give a hand. I'm actually drafting an overview of how Tech news works behind the scenes; I'll share it on this list when it's out. Developers would be ideally-placed to help identify noteworthy changes that will affect Wikimedia users, but most find that activity about as interesting as writing documentation, which says something :) Earlier this year, in a discussion about Gerrit keywords, I suggested that we could use them to tag noteworthy changes, in order to make it easier for developers to identify noteworthy changes, while reducing overhead. Unfortunately, the discussion apparently died: http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/68183/focus=68292 In the meantime, sending a short message to the wikitech-ambassadors list, or dumping a gerrit/bugzilla link at https://meta.wikimedia.org/wiki/Tech/News/Next is the best way to make sure something is communicated to Wikimedians who have subscribed to be informed of tech-related changes likely to affect them. I have ideas on how to improve things in the long term, but I'm open to other suggestions to improve things in the shorter term as well. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering report, October 2013
for VisualEditor, Flow, gadgets, Language features, MobileFrontend, and more. Engineering community team *Bug management https://www.mediawiki.org/wiki/Bug_management* Bugzilla now offers a new guided bug entry formhttps://bugzilla.wikimedia.org/enter_bug.cgi?product=Wikimediacomponent=Bugzillaformat=guidedwhich will make creating good bug reports easier for newcomers. Bugzilla now also displays metadata changeshttps://bugzilla.wikimedia.org/show_bug.cgi?id=47256#c11of a bug report inline for all logged-in users, so they can see in the comments who changed a value of a field (without clicking on History). Daniel Zahn upgraded Wikimedia Bugzilla to latest version 4.2.7http://www.bugzilla.org/releases/4.2.7/release-notes.html. Legoktm mass-imported about 400 Pywikibot ticketshttps://bugzilla.wikimedia.org/show_bug.cgi?id=52692from Sourceforge to Bugzilla. On a related note, Amir ran a PyWikibot Bug Triage https://www.mediawiki.org/wiki/Bug_management/Triage/20131024resulting in nearly 100 tickets receiving updates. Furthermore, Andre Klapper investigated Wikimedia Bugzilla's customizations in CSS and code in order to clean up and sync with the upstream code base, to simplify current maintenance and also make a potential future upgrade of Wikimedia Bugzilla from version 4.2 to 4.4 easier. *Mentorship programs https://www.mediawiki.org/wiki/Mentorship_programs* We presented the summary of GSoC 2013 and FOSS OPW round 6https://commons.wikimedia.org/wiki/File:GSoC_2013_%26_FOSS_OPW_Round_6.pdfat the Wikimedia Metrics Meeting. The document about lessons learned in mentorship programshttps://www.mediawiki.org/wiki/Mentorship_programs/Lessons_learnedwas updated. Wikimedia applied to Google Code-In https://www.mediawiki.org/wiki/Google_Code-In and was successfully accepted on November 1. We opened the call for candidates for FOSS Outreach Program for Women - Round 7https://www.mediawiki.org/wiki/FOSS_Outreach_Program_for_Women . *Technical communications https://www.mediawiki.org/wiki/Technical_communications* Besides ongoing communications support for the engineering staff, Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom published three issues of the Tech newsletter https://meta.wikimedia.org/wiki/Tech/Newsin October, and started a list of open taskshttps://www.mediawiki.org/wiki/Technical_communications/What_you_can_dorelated to technical communications, available for anyone to work on, primarily in preparation for Google Code-Inhttps://www.mediawiki.org/wiki/Google_Code-In . *Volunteer coordination and outreach https://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach* Our proposal for a Wiki devroom at FOSDEMhttps://www.mediawiki.org/wiki/Events/FOSDEMwas accepted and we launched the Call for participationhttps://lists.fosdem.org/pipermail/wikis-devroom/2013-October/00.html. On tech community metrics https://www.mediawiki.org/wiki/Community_metrics, we obtained first results of the *Community metrics: Who contributes code*https://www.mediawiki.org/wiki/Community_metrics#Who_contributes_codekey progress indicator. We facilitated the MediaWiki 1.22 Release Plan tech talkhttps://www.mediawiki.org/wiki/Meetings/2013-10-09and the Flow UX Workshop http://www.meetup.com/wikimedia-tech/events/141845782/meet-up. The list of participants of the Architecture Summit 2014 https://www.mediawiki.org/wiki/Architecture_Summit_2014 was published. We also experimented with a monthly cycle of Engineering Community Team meetingshttps://www.mediawiki.org/wiki/Engineering_Community_Team/Meetings . Multimedia *Multimedia https://www.mediawiki.org/wiki/Multimedia* In October, we continued to expand our multimedia teamhttps://www.mediawiki.org/wiki/Multimediaand hired Gergő Tisza https://meta.wikimedia.org/wiki/User:Tgr as software engineer. Mark Holmquist worked with Gergő to develop a first beta version of the Media Viewer https://www.mediawiki.org/wiki/Multimedia/About_Media_Viewer, which displays images in larger size or full screen; this work was based on designs by Pau Giner, May Tee-Galloway and Jared Zimmerman. We also completed development on the Beta Featureshttps://www.mediawiki.org/wiki/About_Beta_Featuresprogram, which invites users to try out new features before they are released for everyone. A first version of both products is now ready for testing by logged in users on MediaWiki.orghttps://www.mediawiki.org/wiki/Special:Preferences#mw-prefsection-betafeatures(to try new features, click on the small 'Beta' link next to your 'Preferences'). We plan to release the Beta Features program in coming days to Wikimedia Commons and Meta-Wiki, then to all wikis worldwidehttps://www.mediawiki.org/wiki/Beta_Features/Release_Planat the end of November. Fabrice Florin managed the development of both projects, and updated our multimedia plans to prepare for roundtable discussions https://meta.wikimedia.org/wiki/Roundtables with community members next month. Bryan Davis started work on improving
Re: [Wikitech-l] Google Code-in: are you in?
Hi, On Thu, Oct 10, 2013 at 7:51 PM, Quim Gil q...@wikimedia.org wrote: But of course this will only work if many projects want to step in with a task and a mentor for it. So what do you think? This was the perfect opportunity to create the long-overdue task list around tech communications: https://www.mediawiki.org/wiki/Technical_communications/What_you_can_do According to what has been said in this thread, the Translation bit may not work for Code-in, but I expect the rest to be in scope. I'll be available as a mentor for all those tasks and I can be responsive over week-ends and holidays (timezone permitting). If others see possible tasks on this topic that I didn't include or think of, edit the page liberally and we'll [[WP:BRD]] if needed. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering report, September 2013
Outreach Program for Womenhttps://www.mediawiki.org/wiki/Outreach_Program_for_Women/Round_6project (read our announcementhttp://lists.wikimedia.org/pipermail/wikitech-l/2013-September/072081.htmland blog posthttp://blog.wikimedia.org/2013/09/30/foss-outreach-program-for-women-success-and-new-round/). These numbers are unprecedented and we have to ensure that they are not just occasional results but a trend. Wrap-up reports from the projects: - Browser test automation for Visual Editorhttp://bleededge.blogspot.com/2013/09/wrap-up-of-my-outreach-program-for.html - Internationalization and Right-To-Left Support in VisualEditorhttp://moriel.smarterthanthat.com/tips/google-summer-of-code-2013-summary/ - Improve support for book structureshttp://www.mollywhite.net/blog/?p=104 - Section handling in Semantic Formshttp://lists.wikimedia.org/pipermail/wikitech-l/2013-October/072133.html - Prototyping inline comments http://richajain-annotator.blogspot.in/ - jQuery.IME extensions for Firefox and Chromehttp://blog.praveensingh.in/articles/gsoc-wrap-up/ *Technical communicationshttps://www.mediawiki.org/wiki/Technical_communications * Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom wrapped up work on supporting the deployment of VisualEditor, and resumed regular activities like preparing the Tech newsletterhttps://meta.wikimedia.org/wiki/Tech/Newsand ongoing communications support for the engineering staff. *Volunteer coordination and outreachhttps://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach * Together with XWiki http://www.xwiki.org/ and Tiki https://tiki.org/, we submitted a Wiki devroomhttps://www.mediawiki.org/wiki/Events/FOSDEM#Devroom_proposalproposal for FOSDEM http://fosdem.org, the biggest open source source conference in Europe. We are also preparing a proposal for a stand, lead by volunteers at the nascent Wikimedia Belgium chapter. The overall goal is to achieve a good MediaWiki Wikimedia tech gathering in Brussels next February. We are also supporting the organization of the MediaWiki Architecture Summithttps://www.mediawiki.org/wiki/Architecture_guidelines/Meetings/Architecture_Summit_2014in San Francisco on 23-24 January, 2014. Analytics https://www.mediawiki.org/wiki/Analytics The team has been focused on smaller but more important work items this month, including enhancement to Wikimetrics, Grantmaking and Program Developments graphing infrastructure and fixing some long-standing Limn bugs. On the infrastructure side, our collaboration with Ops has the Kafka middleware project moving along nicely. The all-staff meeting and travel schedules definitely impacted our throughput this month.Two notable accomplishments should be called out: our Hadoop environment is now 100% free software, as we swapped out a proprietary JDK for OpenJDK 7. We also spent a lot of time on our engagement processes and planning for our first combined quarterly review in October, and made significant process on our hiring goals. *Research and datahttps://www.mediawiki.org/wiki/Analytics/Research_and_Data * This month, Aaron Halfakerhttps://en.wikipedia.org/wiki/User:Halfak_%28WMF%29joined the research team as a full-time employee. We started to reorganize the team structure and engagement model in coordination with the Analytics developers. We performed a survival analysis of new editorshttps://meta.wikimedia.org/wiki/Research:Newcomer_survival_modelsin preparation for new experiments led by the Growth https://meta.wikimedia.org/wiki/Growth team, and worked with the team to iron out the data collection and experimental design for the fortcoming iterationhttps://meta.wikimedia.org/wiki/Research:Onboarding_new_Wikipedians/OB6of *GettingStarted*. We worked with product owners to determine the initial research strategy for features with key releases scheduled for the next two quarters (Mobile Web https://www.mediawiki.org/wiki/Mobile_web/Team, Beta Featureshttps://www.mediawiki.org/wiki/Beta_Features, Multimedia https://www.mediawiki.org/wiki/Multimedia, Flowhttps://www.mediawiki.org/wiki/Flow, Universal Language Selectorhttps://www.mediawiki.org/wiki/Universal_Language_Selector, Content translation https://www.mediawiki.org/wiki/Content_translation). We started a cohort analysis of conversion rates for mobile vs desktop account registrations; the results will be publishedhttps://meta.wikimedia.org/wiki/R:Mobile_editor_engagementon Meta shortly. We drafted a proposal to host tabular datasetshttps://meta.wikimedia.org/wiki/DataNamespacein a dedicated namespace and solicited feedback from interested parties (particularly the Wikidata community). We also started fleshing out the Labs 2 https://meta.wikimedia.org/wiki/Research:Labs2proposal, an outreach program for academic researchers and community members, launched at Wikimania 2013 in Hong Kong. We co-hosted the second IRC research office hours and prepared for the first Wikimedia research hackathonhttps://meta.wikimedia.org
[Wikitech-l] Wikimedia engineering August 2013 report
://www.mediawiki.org/wiki/User:Orsagi/GSoC_2013_proposal#Monthly_Report:_August_2013 - Mobilizing Wikidatahttps://www.mediawiki.org/wiki/User:Pragunbhutani/GSoC_2013_Updates#Monthly_Report:_August_2013 - Improve support for book structureshttps://meta.wikimedia.org/wiki/Book_management/Progress#August - Incremental data dumpshttps://www.mediawiki.org/wiki/User:Svick/Incremental_dumps#August_report - Language Coverage Matrix Dashboardhttps://www.mediawiki.org/wiki/User:Harsh4101991/GSoC_2013#August - Internationalization and Right-To-Left Support in VisualEditorhttps://www.mediawiki.org/wiki/User:Mooeypoo/GSOC_2013_Proposal:_RTL_Support_in_VisualEditor#Monthly_Report:_August_2013 - Browser test automation for Visual Editorhttps://www.mediawiki.org/wiki/User:Rachel99/proposal1#August - VisualEditor plugin for source codehttps://www.mediawiki.org/wiki/User:Beanixster#August - UploadWizard: Book upload customizationhttps://www.mediawiki.org/wiki/User:Rasel160/GSoC2013/Status#2013-08-monthly - Prototyping inline commentshttps://www.mediawiki.org/wiki/User:Rjain/Gsoc2013/Project_Updates#August - Improvement of glossary toolshttps://www.mediawiki.org/wiki/GSOC_2013_Improvement_of_glossary_tools#August - Incremental updates for Kiwixhttps://www.mediawiki.org/wiki/User:Kiran_mathew_1993/ZIM_incremental_updates_for_Kiwix#Reports - Pronunciation Recording Toolhttps://www.mediawiki.org/wiki/User:Rahul21/Gsoc2013/Project_Updates#August - Bayesian Spam Filterhttps://www.mediawiki.org/wiki/User:Anubhav_iitr/Bayesan_spam_filter/Project_updates - Wikidata language fallback and conversionhttps://www.mediawiki.org/wiki/User:Liangent/wb-lang/updates#August *Technical communicationshttps://www.mediawiki.org/wiki/Technical_communications * Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom continued to focus on the VisualEditor deployment effort, working on communications, documentation and liaising with the French Wikipedia. Work on technical communications mostly focused on perennial activities like Tech newshttps://meta.wikimedia.org/wiki/Tech/Newsand ongoing communications support to the engineering staff. *Volunteer coordination and outreachhttps://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach * We had a team presentation at Wikimania: Transparency and collaboration in Wikimedia engineeringhttp://wikimania2013.wikimedia.org/wiki/Talk:Submissions/Transparency_and_collaboration_in_Wikimedia_engineering, explaining how volunteers can make a difference. Following the work on Community metrics https://www.mediawiki.org/wiki/Community_metrics, the five key performance indicatorshttps://www.mediawiki.org/wiki/Community_metrics#Key_performance_indicators(KPIs) were discussed and agreed upon. We are focusing on the first one: who contributes codehttps://www.mediawiki.org/wiki/Community_metrics#Who_contributes_code. A list of Key Wikimedia software projectshttps://wikitech.wikimedia.org/wiki/Key_Wikimedia_software_projectshas been created to define the scope of these KPIs. Recruiting automated browser testers keeps being our top priority. We are organizing the next workshop in San Francisco and online on September 18: Epic fail: figuring out Selenium test resultshttp://www.meetup.com/wikimedia-tech/events/137381022/ . Analytics https://www.mediawiki.org/wiki/Analytics *Analytics infrastructurehttps://www.mediawiki.org/wiki/Analytics/Infrastructure * We continue to pursue the initiatives listed in our planning document. We've had one analyst accept a job offer (welcome Aaronhttps://en.wikipedia.org/wiki/User:EpochFail!) and are in discussions with a software engineer. We continue to have a solid pipeline and are spending a lot of time interviewing. Wikimetrics is on target for an early September release and we've made good progress against our hadoop infrastructure goals. In co-operation with Ops, we've completed our reinstall of the Hadoop cluster and run several days of reliability testing over the labor day weekend. We are currently investigating replacing the Oracle JDK with the Open JDK to be in line with our goals of using open source whenever possible. Our project to replace udp2log with Kafka is making steadily progress. Varnishkafka, which will replace varnishncsa, has been debianizedhttps://gerrit.wikimedia.org/r/#/c/78782/and the first performance tests of compressing the message sets are very encouraging. We created a test environment in Labs to test Kafka failover modes and we have been prototyping with Camushttps://github.com/linkedin/camusto consume the data from a broker and write it to HDFS. We are right now thinking about how to set up Kafka in a multi data-center environment. The Zookeepers have been reinstalled through Puppet as well. *Analytics Visualization, Reporting Applicationshttps://www.mediawiki.org/wiki/Analytics/Visualization,_Reporting_%26_Applications * In close collaboration with Dario, Jaime and Jessie, we have worked on new features
[Wikitech-l] Veracity check for Tech news #34
Hi, It would be great if a few pairs of eyes could take a look at https://meta.wikimedia.org/wiki/Tech/News/2013/34 before I send it to translators, to check that I haven't missed anything super-important or misunderstood what the commits are about. The tech newsletter is aimed at non-expert Wikimedians whose knowledge of English may be limited, so the language may seem vague or naive to developers. If you see factual errors, please correct them (or let me know directly), but please keep the language simple :) Many thanks for your help. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering July 2013 report
://www.mediawiki.org/wiki/Roadmap#Wikidata_deployment. Coveralls.io support https://coveralls.io/r/wikimedia has been added to most of our components. Since the first deployment of Phase1 to Wikipedia, about 240 million interwikilinks (5GB text) have been removed from articles (2012http://simia.net/languagelinks/index.htmlvs 2013 http://simia.net/languagelinks/2013.html analysis). In other news, the AAAI Feigenbaum Prize for Watson was donated to the Wikimedia Foundation by IBM research to support work, especially on Wikidatahttps://blog.wikimedia.org/2013/07/16/ibm-research-watson-aaai-prize-wikimedia-foundation/ . Denny Vrandečić explainshttp://lists.wikimedia.org/pipermail/wikidata-l/2013-July/002518.htmlwhy Wikidata items are identified with a Q. Future The engineering management team continues to update the *Deploymentshttps://wikitech.wikimedia.org/wiki/Deployments * page weekly, providing up-to-date information on the upcoming deployments to Wikimedia sites, as well as the *engineering roadmaphttps://www.mediawiki.org/wiki/Roadmap *, listing ongoing and future Wikimedia engineering efforts. *Annual goals*https://www.mediawiki.org/wiki/Wikimedia_Engineering/2013-14_Goalsfor the 2013–2014 fiscal year are being drafted by some teams and have been finalized by others. * This article was written collaboratively by Wikimedia engineers and managers, and assembled by Sumana Harihareswara. See revision historyhttps://www.mediawiki.org/w/index.php?title=Wikimedia_engineering_report/2013/Julyaction=historyand associated status pages. A wiki versionhttps://www.mediawiki.org/wiki/Wikimedia_engineering_report/2013/Julyis also available. * -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering June 2013 report
was the deployment of the geocoordinate datatype. This makes it possible, for example, to indicate the location of a city. Geocoordinates that are already in Wikidata can be seen on this maphttps://dl.dropboxusercontent.com/u/172199972/map.png(huge version https://dl.dropboxusercontent.com/u/172199972/map_huge.png, updated daily). In a blog entryhttp://blog.wikimedia.de/2013/06/04/on-truths-and-lies/, Denny Vrandečić explained his understanding of the relation of Wikidata and the truth. In other news, further development of Wikidata has been supported through a large donation by the search engine company Yandexhttp://blog.wikimedia.de/2013/06/05/grosspende-fur-wikidata/ . Future The engineering management team continues to update the * Deployments https://wikitech.wikimedia.org/wiki/Deployments* page weekly, providing up-to-date information on the upcoming deployments to Wikimedia sites, as well as the *engineering roadmaphttps://www.mediawiki.org/wiki/Roadmap *, listing ongoing and future Wikimedia engineering efforts. *Annual goals*https://www.mediawiki.org/wiki/Wikimedia_Engineering/2013-14_Goalsfor the 2013–2014 fiscal year are currently being drafted. -- This report was reviewed and proofread using VisualEditor. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering May 2013 report
of his investigation, Andre documentedhttp://blogs.gnome.org/aklapper/2013/05/28/understanding-bugzilla-groups-and-admin-rights/the meaning of Bugzilla admin rights. *Mentorship programs https://www.mediawiki.org/wiki/Mentorship_programs* We selected 20 Google Summer of Codehttps://www.mediawiki.org/wiki/Summer_of_Code_2013and 2 Outreach Program for Womenhttps://www.mediawiki.org/wiki/Outreach_Program_for_Women/Round_6projects that will be mentored by a total of 32 volunteers. This represents more than double the amount of projects we had last year. We received 69 applications from 60 students for Google Summer of Code 2013, from which 9 were also applying to OPW, and 4 OPW-only individual applications. Google allocated the 21 slots we requested, but we decided to give one back in order to keep a standard on project feasibility. *Technical communicationshttps://www.mediawiki.org/wiki/Technical_communications * In May, Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom's major focus was on supporting Tech ambassadorshttps://meta.wikimedia.org/wiki/Tech/Ambassadorsand setting up Tech news https://meta.wikimedia.org/wiki/Tech/News, an initiative aiming to collaboratively monitor recent software changes likely to impact Wikimedians, and distribute a weekly summary, free of technical jargon, to subscribers on their talk page. Two issues of this weekly summary were published this month; starting with the second issue, the content is now distributed in several languages if translations are available. Guillaume also continued to review technical blog posts, and executed the move of the Mobile documentationhttps://www.mediawiki.org/wiki/Technical_communications/Mobile_documentation_consolidationfrom Meta-Wiki to mediawiki.org. *Volunteer coordination and outreachhttps://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach * Quim Gil https://www.mediawiki.org/wiki/User:Qgil has been preparing a proposal to get automated community metricshttps://www.mediawiki.org/wiki/Community_metricsbased on vizGrimoire http://vizgrimoire.bitergia.org/ and provided by their maintainers, Bitergia http://bitergia.com/. It is currently being discussed with Sumana Harihareswarahttps://www.mediawiki.org/wiki/User:Sharihareswara_%28WMF%29and Rob Lanphier https://www.mediawiki.org/wiki/User:RobLa-WMF for budget approval. Quim also worked on a user-friendly template for the landing page of the wikitech-announcehttps://lists.wikimedia.org/mailman/listinfo/wikitech-announcemailing list that can be used for other Wikimedia lists (source code https://www.mediawiki.org/wiki/User:Qgil/wikitech-announce). He also created a landing page for organizationshttps://www.mediawiki.org/wiki/Mentorship_programs/Organizationswilling to collaborate with Wikimedia to co-organize technical activities. Kiwix http://www.kiwix.org *The Kiwix project is funded and executed by Wikimedia CHhttps://meta.wikimedia.org/wiki/Wikimedia_CH .* With openZIM http://www.openzim.org, we have finally released the first version of its standard implementation code: the zimlibhttp://www.openzim.org/wiki/Zimlib. Kiwix was introduced in Debian testinghttp://packages.debian.org/search?suite=allarch=anysearchon=nameskeywords=kiwix. A new release of Kiwix for Androidhttps://play.google.com/store/apps/details?id=org.kiwix.kiwixmobile, with a few bug fixes and improvements, was released. Our first GSoC project (ZIM incremental updates for Kiwixhttps://www.mediawiki.org/wiki/User:Kiran_mathew_1993/ZIM_incremental_updates_for_Kiwix) was prepared and accepted; work has already started with Kiranhttps://www.mediawiki.org/wiki/User:Kiran_mathew_1993, the Indian student responsible for this project. Wikidatahttps://meta.wikimedia.org/wiki/Wikidata *The Wikidata project is funded and executed by Wikimedia Deutschlandhttps://meta.wikimedia.org/wiki/Wikimedia_Deutschland/en .* The Wikidata team worked on 2 major topics in May: the ability to access data from Wikidata in a Wikipedia article by its label and not just its ID, and the ability to enter points in time into Wikidatahttps://www.wikidata.org/wiki/Wikidata:Project_chat#Time_datatype_available_and_short_overview_of_next_steps, which for example now makes it possible to enter the date of birth of a person. Magnus Manske blogged about the tool ecosystemhttp://blog.wikimedia.de/2013/05/06/the-wikidata-tool-ecosystem/that is building around Wikidata. During the next 3 months, the team will be workinghttp://lists.wikimedia.org/pipermail/wikidata-l/2013-May/002293.htmlwith 3 Google Summer of Code students, and 2 other students will be working with other organizations on Wikidata-related projects. The codebase has been reviewedhttp://lists.wikimedia.org/pipermail/wikidata-tech/2013-May/06.htmlby Qafoo. Wikidata-tech https://lists.wikimedia.org/mailman/listinfo/wikidata-tech, a new mailing list for discussions related to the development around Wikidata, was created. Additionally, the team attended the hackathon
Re: [Wikitech-l] Feasibility question: Posting mailing list notifications to a wiki page
Hi, On Thu, May 9, 2013 at 7:41 PM, Arthur Richards aricha...@wikimedia.org wrote: This might be something that would be better suited for Echo rather than talk page notifications. I agree; the problem is that such notifications are currently not planned in Echo/Notifications. Quoting from my post on WP:VP/T: It seems to me that this noticeboard would be yet another suboptimal workaround to a proper channel for topical notifications. Echo/Notifications was once presented as the solution to this problem, but public announcements are currently listed as out of scope https://www.mediawiki.org/wiki/Echo#Scope . I don't know what the timeline is (if any) for the support of topical public announcements in Echo. And earlier in this thread: In the longer term, the Notifications system will hopefully end up solving the issue in a better way, but if a quick bot hack can be a good interim alternative, I think it's worth a shot. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Feasibility question: Posting mailing list notifications to a wiki page
Hi, There's currently a proposal on the English Wikipedia about creating a Developer's noticeboard so that people can stay informed about technical announcements outside of the noisy Village Pump/Technical: https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28proposals%29#Developer.27s_Noticeboard The main argument (as I understand it) is that existing venues (like the wikitech-ambassadors mailing list, currently used for this purpose) don't meet the needs of users who want to be notified on their wiki, in their watchlist. Rather than creating yet another (enwiki-only) venue for technical announcements, I'd prefer to find a way to use the current venues, and augment them to mitigate their limitations. What I currently have in mind is a bot subscribed to the wikitech-ambassadors list, that would post every first message of a thread to the talk page of people who have signed up (like https://meta.wikimedia.org/wiki/Global_message_delivery/Targets/Tech_ambassadors ) or to a noticeboard (that would then be mostly automated). The bot would create a new section, using the email's subject line as the section title, and its body as the message. It would ideally link back to the gmane archive for that thread, so that users can read follow-up messages there. Messages could be trimmed if they're too long. The system could possibly also be used for other mailing lists later. My intuition is that this wouldn't be exceptionally hard to implement, but I'd like a more informed opinion. Does anyone have experience with a similar tool? Would someone be interested in giving it a try? In the longer term, the Notifications system will hopefully end up solving the issue in a better way, but if a quick bot hack can be a good interim alternative, I think it's worth a shot. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Feasibility question: Posting mailing list notifications to a wiki page
On Thu, May 9, 2013 at 6:11 PM, Greg Grossmeier g...@wikimedia.org wrote: I think the only way to address that is to have those on -ambassadors translate/localize (in more than just which language is being used) and post it on their local project's VPT (or equivalent). I completely agree, and theoretically, that's how the ambassadors list is intended to work. But in practice, my impression is that only some of the subscribers relay the information to their local wiki. Perhaps using email subjects starting with Please relay: foo would be a first step, but I don't expect it to be enough. I'm open to suggestions about how to increase that ratio :) -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Feasibility question: Posting mailing list notifications to a wiki page
On Thu, May 9, 2013 at 6:20 PM, Guillaume Paumier gpaum...@wikimedia.org wrote: Perhaps using email subjects starting with Please relay: foo would be a first step, but I don't expect it to be enough. I'm open to suggestions about how to increase that ratio :) Another possibility would be (if we set up that mailing-list-to-wiki bot) to test whether people who get the message on their talk page relay it more than people who get it via email. (My intuition would be yes, because they're already in the wiki activity and not in the email one, but perhaps I'm just projecting my own personal processes here.) -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Global watchlist and watchlist wishlist
Hi, A discussion has started on-wiki about a global watchlist, and other related improvements to the watchlist feature. A few people have started to organize the various bug reports about watchlists, but there is still much to do before we have a clear prioritized vision of what the watchlist feature should become. Improving a feature as used and central as the watchlist has the potential of drastically improving the users' experience, but is also likely to cause an outcry if proper research isn't done in advance, given that everyone has their own workflow. One comment that came up during the discussion was that people didn't want to spend time working on research, specifications prioritization of features unless they had some sort of guarantee that their work wouldn't just be ignored and rot in a corner because nobody's interested in actually implementing the changes. I think this is a fair and understandable request: nobody wants their hard work to go to waste. Therefore, if a few developers could declare their interest in tackling the watchlist issue in the foreseeable future, it would help arouse interest and enthusiasm from users, and motivate them to organize user research in order to design a better watchlist feature. I don't think we need a formal pledge or commitment; a simple declaration of interest would imho be enough to get started. The specifics can be ironed out later. So, I have two questions: * Does this make sense? * Are you interested in improving the watchlist feature within, say, the next 6 months? More information: Discussion: https://www.mediawiki.org/wiki/Talk:Watchlist_wishlist Draft product page: https://www.mediawiki.org/wiki/Watchlist_wishlist -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Starter kit ?
Hi, On Mon, May 6, 2013 at 2:28 PM, Mathieu Stumpf psychosl...@culture-libre.org wrote: Reading [1], I'm wondering if we couldn't have a wiki version of this page that could be updated along the road. For example the text talk about MySQL and but doesn't talk about the MariaDB migration. [1] http://www.aosabook.org/en/mediawiki.html That chapter was actually written on mediawiki.org, as part of this project: https://www.mediawiki.org/wiki/MediaWiki_architecture_document The content of the chapter lives in 2 wiki pages: * https://www.mediawiki.org/wiki/MediaWiki_history * https://www.mediawiki.org/wiki/Manual:MediaWiki_architecture You're encouraged to update what needs updating :) By the way the two The Architecture of Open Source Applications books may find there place on Wikisource, don't you think? But Wikisource isn't the place for books you want to update, may be Wikibooks may be a good place, what do you think? Wikisource could host static versions of the books. Or Wikibooks could host live versions of the books. I'm not sure that we'd see many updates to the books outside of the MediaWiki chapter, so right now I'd rather encourage people to edit the content on mediawiki.org. -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Replacement for tagging in Gerrit
Hi, On Sun, Mar 10, 2013 at 2:11 AM, Rob Lanphier ro...@wikimedia.org wrote: Short version: This mail is fishing for feedback on proposed work on Gerrit-Bugzilla integration to replace code review tags. I was wondering: has a decision been made regarding this? I'm resuming work on (notably) identifying/marking noteworthy changes, and I'm interested to know if the tagging system is something that we could possibly take advantage of for this (and if so, what a rough timeline would be :). -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering April 2013 report
://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach * Quim Gil https://www.mediawiki.org/wiki/User:Qgil refactored the radica *Wikitech contributors* proposal into the more gradual Project:New contributorshttps://www.mediawiki.org/wiki/Project:New_contributorsbased on the feedback received. He supported QA and bug management events, organized a tech talk for 3 tech projects receiving Wikimedia grantshttps://www.mediawiki.org/wiki/Meetings/2013-04-18, and completed the survey about best times for volunteeringhttp://www.doodle.com/minqnd6ngz9npfdv(which got 33 answers). He spoke at the Bay Area Linux User Group http://balug.org with Daniel Zahn, Rob Lanphier and Brian Wolff, and requested a proposal from Bitergia http://bitergia.comto automate the generation of Community metrics https://www.mediawiki.org/wiki/Community_metrics. Kiwix http://www.kiwix.org *The Kiwix project is funded and executed by Wikimedia CHhttps://meta.wikimedia.org/wiki/Wikimedia_CH .* In April, we releasedhttps://blog.wikimedia.org/2013/04/17/carry-the-entirety-of-wikipedia-in-your-pocket-with-kiwix-for-android/for the first time Kiwix for Androidhttps://play.google.com/store/apps/details?id=org.kiwix.kiwixmobile. This version doesn't provide as many features as the desktop app, but it works well with all ZIM files. Two Kiwix developers will attend Wikimania and have started preparing http://www.kiwix.org/wiki/Wikimania_2013 for a a small hackathon, two presentations and a permanent booth. Wikidatahttps://meta.wikimedia.org/wiki/Wikidata *The Wikidata project is funded and executed by Wikimedia Deutschlandhttps://meta.wikimedia.org/wiki/Wikimedia_Deutschland/en .* The team hit a big milestone with the deployment of the first iteration of phase 2 of Wikidata on all remaininghttp://blog.wikimedia.de/2013/04/22/and-that-makes-12/ Wikipediashttp://blog.wikimedia.de/2013/04/24/wikidata-all-around-the-world/(it had been enabled on 11 Wikipedias previously). Qualifiershttps://meta.wikimedia.org/wiki/Wikidata/Notes/Data_model_primer#Qualifierswere also enabled on Wikidata, making it possible to add additional information to certain data. Wikipedians are now able to make use of the data available on Wikidata in articles, allowing the data to be collaboratively collected, curated and used by all Wikipedias.The team also fixed a few issues to make it possible to use Wikidata with Internet Explorer 8, and worked on the time datatype. Together with bot owners, they massively improved the time it takes for Wikidata changes to show up in the recent changes and watchlists on Wikipedia sites. The code and architecture got an external professional review; the reviewers were quite happy with the quality of the code base and gave useful tips for improvements. Future The engineering management team continues to update the *Deploymentshttps://wikitech.wikimedia.org/wiki/Deployments * page weekly, providing up-to-date information on the upcoming deployments to Wikimedia sites, as well as the *engineering roadmaphttps://www.mediawiki.org/wiki/Roadmap *, listing ongoing and future Wikimedia engineering efforts. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Glossary vs. Glossaries
Hi, On Fri, Mar 22, 2013 at 2:27 PM, Guillaume Paumier gpaum...@wikimedia.org wrote: * Google custom search: Waldir recently used Google Custom Search to created a search tool to find technical information across many pages and sites where information is currently fragmented: http://lists.wikimedia.org/pipermail/wikitech-l/2013-March/067450.html . We could set up a similar tool (or a floss alternative) that would include all glossaries. By advertising the tool prominently on existing glossary pages (so that users know it exists), this could allow us to curate more specific glossaries, while keeping them all searchable with one tool. Just a quick note to let people know that this is now up and running: https://www.google.com/cse/home?cx=015296225943515200682:ds3sfewbbrw (Note to Ghostery users: you'll have to enable Google AJAX Search API to see search results.) I'm slightly annoyed that this is a third-party tool and I'd much prefer a floss alternative running on Tool Labs or something, but until that happens, we have a working tool we can use to search a term across scattered Wikimedia-related glossaries. I'd like to find people to help maintain the URL list (right now there's a version at https://meta.wikimedia.org/w/index.php?oldid=5406259 ) so if you'd like to help, contact me offlist and I'll give you access. The next step is to better organize the glossaries, and actually add definitions; I'll start another thread later about this. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] WMF Engineering Roadmap Update - 20130417
Hi, On Fri, Apr 19, 2013 at 5:29 PM, Greg Grossmeier g...@wikimedia.org wrote: Mostly it is the function of multiple people editing the document together at the same time in the same room. Until that problem can be solved on wiki, then a big wiki table probably won't be functional, at least in the current form that we've taken for this. But, I also don't know the full capabilities of what could be done, here, so if someone has a suggestion on how to work this on wiki that allows easy multi-user simultaneous editing, please do let me know. Off the top of my head, and without thinking too much about it: Solution #1: All the content lives in [[Projectname/Roadmap]] pages, in monthly sections labeled with Labeled Section Transclusion. They can be transcluded into other pages (like a big all-encompassing Roadmap page, or smaller roadmaps per team / subdepartment). A JavaScript gadget allows for easy editing of roadmap items (i.e. cells) directly from the Roadmap page (and other transclusion pages) using a modal overlay, like the StatusHelper does ( https://www.mediawiki.org/wiki/MediaWiki:Gadget-WmfProjectStatusHelper.js ) Pros: * Everything is and stays on wiki. * The roadmap for each project can be maintained by the project's team more easily, because it's closer to the project page. * The JavaScript template hackery needed to make this work is probably not too complicated and can be inspired by the existing StatusHelper. * No edit conflicts, since people are editing different pages. Cons: * People can't simultaneously edit the same roadmap item (cell for a given month and a given project). * People need to refresh the page to see edits made by other people with the gadget. * Some template / LST / JavaScript dev work is required. Based on my understanding of how the roadmap is currently updated (each Tech director updates the roadmap for the projects that fall under their supervision), the cons don't seem unsurmountable. * Solution #2: All the content lives in a big table at [[Roadmap]] that can be edited simultaneously by users using a yet-to-be-developed round-tripping tool to an ethercalc instance in labs. Someone opens the page for editing in ethercalc, everyone makes their edits, and the content is saved back to the wiki page. Pros: * Everything lives on wiki. * People can simultaneously edit all parts of the document, including the same cells, and immediately see each other's changes Cons: * This requires significant dev work, probably not trivial considering the difficulties encountered when we tried to integrate regular etherpad with wikipage editing a few years back. * How do we handle edit conflicts? * This poses other questions like who is attributed for the edits, etc. An alternative to #2: the round-tripping is done manually by copy/paste or similar (as it used to be done when tech directors updated the roadmap in etherpad) if the conversion between formats isn't too lossy; This avoids having to develop an integrated round-tripping tool. Solution #3: A combination of #1 and #2: for example, the content lives in a big table at [[Roadmap]], and there's a round-tripping tool to an ethercalc instance in labs for collaborative editing, but there's also a JavaScript gadget to edit individual cells of the table. Note: LST can probably be replaced by Semantic MediaWiki if it's available on the wiki we're talking about. In a nutshell: I understand that the way the roadmap is currently updated (in a meeting of all tech directors each updating their sections) requires simultaneous editing of the /page/, but I'm not sure concurrent editing of /each cell/ is as crucial, so compromising on that may greatly simplify the problem. HTH, -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Missing project ideas for GSOC
Hi, On Thu, Mar 21, 2013 at 12:43 AM, Quim Gil q...@wikimedia.org wrote: Many of the ideas listed there are too generic (Write an extension), improvements of existing features (Improve Extension:CSS) This may sound naive, but why are improvements of existing features discarded? My thinking was that, if the student didn't have to start from scratch, they would have more time to polish their work and make it fit with our strict standards, hence making it more likely for their work to be merged and deployed. (Of course, the existing code needs to be good enough not to require a complete rewrite, but that could be decided on a case-by-case basis.) -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Glossary vs. Glossaries
Hi, Last November, I started to clean up on the Glossary page on meta, as an attempt to revive it and expand it to include many technical terms, notably related to Wikimedia Engineering (see e-mail below). There were (and are) already many glossaries spread around the wikis: * one for MediaWiki: https://www.mediawiki.org/wiki/Manual:Glossary * one for Wikidata: https://www.wikidata.org/wiki/Wikidata:Glossary * one for Labs: https://wikitech.wikimedia.org/wiki/Help:Terminology * two for the English Wikipedia: https://en.wikipedia.org/wiki/Wikipedia:Glossary https://en.wikipedia.org/wiki/Wikipedia:WikiSpeak * etc. My thinking at the time was that it would be better to include tech terms in meta's glossary, because fragmentation isn't a good thing for glossaries: The user probably doesn't want to search a term through a dozen glossaries (that they know of), and it would be easier if they could just search in one place. The fact is, though, that we're not going to merge all the existing glossaries into one anytime soon, so overlap and duplication will remain anyway. Also, it feels weird to have tech content on meta, and the glossary is getting very long (and possibly more difficult to maintain). Therefore, I'm now reconsidering the decision of mixing tech terms and general movement terms on meta. Below are the current solutions I'm seeing to move forward; I'd love to get some feedback as to what people think would be the best way to proceed. * Status quo: We keep the current glossaries as they are, even if they overlap and duplicate work. We'll manage. * Wikidata: If Wikidata could be used to host terms and definitions (in various languages), and wikis could pull this data using templates/Lua, it would be a sane way to reduce duplication, while still allowing local wikis to complement it with their own terms. For example, administrator is a generic term across Wikimedia sites (even MediaWiki sites), so it would go into the general glossary repository on Wikidata; but DYK could be local to the English Wikipedia. With proper templates, the integration between remote and local terms could be seamless. It seems to me, however, that this would require significant development work. * Google custom search: Waldir recently used Google Custom Search to created a search tool to find technical information across many pages and sites where information is currently fragmented: http://lists.wikimedia.org/pipermail/wikitech-l/2013-March/067450.html . We could set up a similar tool (or a floss alternative) that would include all glossaries. By advertising the tool prominently on existing glossary pages (so that users know it exists), this could allow us to curate more specific glossaries, while keeping them all searchable with one tool. Right now, I'm inclined to go with the custom search solution, because it looks like the easiest and fastest to implement, while reducing maintenance costs and remaining flexible. That said, I'd love to hear feedback and opinions about this before implementing anything. Thanks, guillaume On Tue, Nov 20, 2012 at 7:55 PM, Guillaume Paumier gpaum...@wikimedia.org wrote: Hi, The use of jargon, acronyms and other abbreviations throughout the Wikimedia movement is a major source of communication issues, and barriers to comprehension and involvement. The recent thread on this list about What is Product? is an example of this, as are initialisms that have long been known to be a barrier for Wikipedia newcomers. A way to bridge people and communities with different vocabularies is to write and maintain a glossary that explains jargon in plain English terms. We've been lacking a good and up-to-date glossary for Wikimedia stuff (Foundation, chapter, movement, technology, etc.). Therefore, I've started to clean up and expand the outdated Glossary on meta, but it's a lot of work, and I don't have all the answers myself either. I'll continue to work on it, but I'd love to get some help on this and to make it a collaborative effort. If you have a few minutes to spare, please consider helping your (current and future) fellow Wikimedians by writing a few definitions if there are terms that you can explain in plain English. Additions of new terms are much welcome as well: https://meta.wikimedia.org/wiki/Glossary Some caveats: * As part of my work, I'm mostly interested in a glossary from a technical perspective, so the list currently has a technical bias. I'm hoping that by sending this message to a wider audience, people from the whole movement will contribute to the glossary and balance it out. * Also, I've started to clean up the glossary, but it still contains dated terms and definitions from a few years ago (like the FundCom), so boldly edit/remove obsolete content. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l
[Wikitech-l] Reminder: Lua/Scribunto IRC office hours today
Hi,
Just a quick reminder that we'll be holding IRC office hours in about
50 minutes. If you have questions about how to use Lua, or issues
you'd like help with, join us in #wikimedia-office on Freenode.
More information about how to connect to IRC is available at
https://meta.wikimedia.org/wiki/IRC_office_hours
On Wed, Mar 13, 2013 at 7:38 PM, Guillaume Paumier
gpaum...@wikimedia.org wrote:
Greetings,
As you might have seen on the Wikimedia tech blog (article included below)
or the tech ambassadors list, a new functionality called Lua is being
enabled on all Wikimedia sites today. Lua is a scripting language that
enables Wikimedia editors to write faster and more powerful MediaWiki
templates.
If you have questions about how to convert existing templates to Lua (or how
to create new ones), we'll be holding two support sessions on IRC next week:
one on Wednesday (for Oceania, Asia America) and one on Friday (for
Europe, Africa America); see m:IRC office hours for details. If you can't
make it, you can also get help at mw:Talk:Lua scripting.
If you'd like to learn about this kind of events earlier in advance,
consider becoming a Tech ambassador by subscribing to the mailing list.
=
New Lua templates bring faster, more flexible pages to your wiki
Posted by Sumana Harihareswara on March 11th, 2013
Starting Wednesday, March 13th, you’ll be able to make wiki pages even more
useful, no matter what language you speak: we’re adding Lua as a templating
language. This will make it easier for you to create and change infoboxes,
tables, and other useful MediaWiki templates. We’ve already started to
deploy Scribunto (the MediaWiki extension that enables this); it’s on
several of the sites, including English Wikipedia, right now.
You’ll find this useful for performing more complex tasks for which
templates are too complex or slow — common examples include numeric
computations, string manipulation and parsing, and decision trees. Even if
you don’t write templates, you’ll enjoy seeing pages load faster and with
more interesting ways to present information.
Background
MediaWiki developers introduced templates and parser functions years ago to
allow end-users of MediaWiki to replicate content easily and build tools
using basic logic. Along the way, we found that we were turning wikitext
into a limited programming language. Complex templates have caused
performance issues and bottlenecks, and it’s difficult for users to write
and understand templates. Therefore, the Lua scripting project aims to make
it possible for MediaWiki end-users to use a proper scripting language that
will be more powerful and efficient than ad-hoc, parser functions-based
logic. The example of Lua’s use in World of Warcraft is promising; even
novices with no programming experience have been able to make large changes
to their graphical experiences by quickly learning some Lua.
Lua on your wiki
As of March 13th, you’ll be able to use Lua on your home wiki (if it’s not
already enabled). Lua code can be embedded into wiki templates by employing
the {{#invoke:}} parser function provided by the Scribunto MediaWiki
extension. The Lua source code is stored in pages called modules (e.g.,
Module:Bananas). These individual modules are then invoked on template
pages. The example: Template:Lua hello world uses the code
{{#invoke:Bananas|hello}} to print the text “Hello, world!”. So, if you
start seeing edits in the Module namespace, that’s what’s going on.
Getting started
Check out the basic “hello, world!” instructions, then look at Brad Jorsch’s
short presentation for a basic example of how to convert a wikitext template
into a Lua module. After that, try Tim Starling’s tutorial.
To help you preview and test a converted template, try
Special:TemplateSandbox on your wiki. With it, you can preview a page using
sandboxed versions of templates and modules, allowing for easy testing
before you make the sandbox code live.
Where to start? If you use pywikipedia, try parsercountfunction.py by
Bináris, which helps you find wikitext templates that currently parse slowly
and thus would be worth converting to Lua. Try fulfilling open requests for
conversion on English Wikipedia, possibly using Anomie’s Greasemonkey script
to help you see the performance gains. On English Wikipedia, some of the
templates have already been converted — feel free to reuse them on your
wiki.
The Lua hub on mediawiki.org has more information; please add to it. And
enjoy your faster, more flexible templates!
Sumana Harihareswara, Engineering Community Manager
=
--
Guillaume Paumier
Technical Communications Manager — Wikimedia Foundation
https://donate.wikimedia.org
--
Guillaume Paumier
Technical Communications Manager — Wikimedia Foundation
https://donate.wikimedia.org
___
Wikitech-l
Re: [Wikitech-l] Replacement for tagging in Gerrit
Hi, On Sun, Mar 10, 2013 at 2:11 AM, Rob Lanphier ro...@wikimedia.org wrote: Hi folks, Short version: This mail is fishing for feedback on proposed work on Gerrit-Bugzilla integration to replace code review tags. I preferred that if we were going to have our own hacky solution, it should at least be implemented as a Gerrit plugin, so that it would at least stand a chance of becoming a well-integrated solution. A Bugzilla-based solution would be an ideal replacement for fixme, since fixmes are basically bugs anyway. It would work reasonably well for scaptrap, since they generally imply something that needs to be done prior to deployment. It would be an awkward replacement for backcompat and others. Thank you for this detailed e-mail. One thing I think I'm missing is why the bugzilla-based solution is better than the gerrit plugin one. It seems to me that if the tagging functionality was developed as a gerrit plugin, it would have all the advantages of the bugzilla-based solution (good integration, etc.) without its drawbacks (awkwardness for non-bugs tags, e-mail addresses mismatches, dependency on bugzilla). Admittedly, I'm not a primary user of gerrit, but I've been pondering the idea of using tags in order to surface noteworthy changes, so they can be easily listed and communicated about to our users. This would make it much easier to identify the most important changes on pages like https://www.mediawiki.org/wiki/MediaWiki_1.21/wmf7 , and could also perhaps be used for release notes summaries. A bugzilla-based tagging system seems too restrictive for this kind of use, but perhaps I'm just not seeing how it would work. It's difficult to predict the kinds of tags people will come up with in the future, and I feel it would be a pity to develop a tagging solution that restricts the type of tags you can use with it. Just my $0.02 data point. -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Developer Hub update
Hi, On Sun, Feb 10, 2013 at 8:51 PM, MZMcBride z...@mzmcbride.com wrote: The issue, as I understand it, is that there's a good amount of non-MediaWiki-related technical documentation that people are now trying to shoehorn into mediawiki.org, as there isn't a better place for it. A sizable source of these pages is Wikimedia Foundation engineering-related documentation, some of which clearly belong on mediawiki.org, but some of which clearly do not. This is how I understand the issue as well. There was a proposal (in 2012, I think) to expand a Wikitech wiki, but it seems to have died fairly quickly. I'm not sure why. The reasons as I recall them were: * Expanding the scope of wikitech would require to open it up (it's been a fishbowl wiki for years), which would open it to vandalism, including subtle ones. A way to mitigate this could be to use a flavor of FlaggedRevs, but that thought made people shiver. * Usernames / SUL: Wikitech needs to stay separate from the cluster, because the Ops team needs to be able to use it during an outage. This means no SUL and no benefiting from the help of stewards and their nifty tools to handle less-subtle-and-more-disruptive vandalism. A way to mitigate this could be to have wikitech on the cluster, and a read-only copy outside the cluster. * Their was also a wish to merge the content of wikitech and that of labsconsole, because there's some redundancy (and because it makes sense, as Labs is a staging area for production, labsconsole documents Labs, and wikitech documents production). The best way to do that was thought to be to merge wikitech's content into labsconsole, and maybe rename labconsole to wikitech afterwards. But there's a lot of crap on wikitech, and it should be cleaned up before a merged is attempted. The Ops team is already convinced that wikitech's content needs to be cleaned up, but they have more pressing work. Somebody add to this / correct me if I'm wrong. If I remember more, I'll send a follow-up. A generic developer hub would logically be placed at Meta-Wiki. However, if the reality is that the developer hub is focused primarily at MediaWiki, having a page at Meta-Wiki where every link points back to mediawiki.org is a bit silly. A lot of this could use more thought, but nobody really seems willing to plan this out and then execute the plan. Work on this has indeed been deprioritized in favor of other activities like Tech ambassadors and volunteer product managers. If someone's interested, I can probably find a few draft plans that were discussed last year, and publish them somewhere public. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering January 2013 report
the MediaWiki Group Bug Squadhttps://www.mediawiki.org/wiki/Groups/Proposals/Bug_Squad. Furthermore, some problems due to data center migrationhttps://blog.wikimedia.org/2013/01/19/wikimedia-sites-move-to-primary-data-center-in-ashburn-virginia/were investigated, and it was discussed how to improve interaction on Bugzilla tickets that need handling by the Operations team (who mostly prefers to use the RT https://rt.wikimedia.org/ bugtracker instead). *Mentorship programs https://www.mediawiki.org/wiki/Mentorship_programs* Six Outreach Program for Womenhttps://www.mediawiki.org/wiki/Outreach_Program_for_Womeninterns started on January 3rd and will work full time until April. Mariya https://www.mediawiki.org/wiki/User:Mitevam is working on a discussion among third-party MediaWiki usershttps://www.mediawiki.org/wiki/Third-party_MediaWiki_users_discussion. Valerie https://www.mediawiki.org/wiki/User:Valeriej has completed the Bug Squad group proposalhttps://www.mediawiki.org/wiki/Groups/Proposals/Bug_Squadand a first Bug Day. Priyanka https://www.mediawiki.org/wiki/User:Priyanka_Nag created a scripthttps://www.mediawiki.org/wiki/User:Priyanka_Nag/common.jsand plans to move to Git https://www.mediawiki.org/wiki/Git. Suchetahttps://www.mediawiki.org/wiki/User:Sucheta_Ghoshalis on schedule following her project planhttps://www.mediawiki.org/wiki/User:Sucheta_Ghoshal/OPW-EtherEditor#Plans_and_Estimated_Timeline. Kim https://www.mediawiki.org/wiki/User:Isarra is learning about Flowhttps://www.mediawiki.org/wiki/Flowand the basics of interactive design as indicated by her mentor. Teresa https://www.mediawiki.org/wiki/User:Chot has completed a solid basehttps://gerrit.wikimedia.org/r/#/q/owner:tcho708%2540gmail.com,n,zfor her extension and is working on the main functionality. She hit a snag with her work environment this week, but is still on track with her proposed timeline. The Google Summer of Code 2013https://www.mediawiki.org/wiki/Summer_of_Code_2013page was created, a pre-planning discussionhttp://lists.wikimedia.org/pipermail/wikitech-l/2013-January/065771.htmlstarted on wikitech-l, and LevelUp https://www.mediawiki.org/wiki/Mentorship_programs/LevelUpmatchmaking for the first quarter of 2013 is nearly done. *Technical communicationshttps://www.mediawiki.org/wiki/Technical_communications * Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom provided communications supporthttps://www.mediawiki.org/wiki/Technical_communications/Tech_blog_activityto the engineering team, notably around the data center migrationhttps://blog.wikimedia.org/2013/01/19/wikimedia-sites-move-to-primary-data-center-in-ashburn-virginia/and associated bannershttps://meta.wikimedia.org/wiki/CentralNotice/Generic_maintenance_notice, noticeshttps://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Spamoldid=5081391 translationshttp://lists.wikimedia.org/pipermail/translators-l/2013-January/002199.html. He started to organize and clean up the MediaWiki version pages (like MediaWiki 1.21/wmf7 https://www.mediawiki.org/wiki/MediaWiki_1.21/wmf7) to make them more useful for tech ambassadorshttps://meta.wikimedia.org/wiki/Tech/Ambassadors, by highlighting the most important changes, improving translatability and adding navigation. He also prepared and organized translations for the *How to report a bug https://www.mediawiki.org/wiki/How_to_report_a_bug* and *How to contribute https://www.mediawiki.org/wiki/How_to_contribute* pages, to facilitate the involvement of volunteers who don't necessarily communicate in English. Last, he created a Project:Calendarhttps://www.mediawiki.org/wiki/Project:Calendarto consolidate and centralize announcements for all events https://www.mediawiki.org/wiki/Template:Event, to make opportunities for participation more visible. Events around a particular topic (like QA, testing and bugshttps://www.mediawiki.org/wiki/QA/Weekly_goals) can still be selectively transcluded, using Labeled Section Transclusionhttps://www.mediawiki.org/wiki/Extension:Labeled_Section_Transclusion . *Volunteer coordination and outreachhttps://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach * The MediaWiki groups https://www.mediawiki.org/wiki/Groups for Promotionhttps://www.mediawiki.org/wiki/Groups/Promotionand San Francisco https://www.mediawiki.org/wiki/Groups/San_Francisco were officially approved by the Wikimedia Affiliations Committeehttps://meta.wikimedia.org/wiki/Affiliations_Committee, and are the first Wikimedia User Groupshttps://meta.wikimedia.org/wiki/Wikimedia_User_Groups#Approved_user_groupscreated. We helped the Editor Engagement https://www.mediawiki.org/wiki/Editor_Engagement team organize a sprint to test Echo https://www.mediawiki.org/wiki/Echo/Testing, but our plans to collaborate further with the Editor Engagement and Mobilehttps://www.mediawiki.org/wiki/Mobileteams were delayed; Quim Gil proposed a different approachhttp://lists.wikimedia.org/pipermail/wikitech-l/2013-January/065758
[Wikitech-l] Project calendar
Hi, On Fri, Jan 18, 2013 at 3:24 PM, Guillaume Paumier gpaum...@wikimedia.org wrote: More generally, and to follow up on our discussion yesterday about better coordination, I think I'd like to integrate that kind of announcements into a central page on mw.o that would also list Tech chats, tech-related IRC office hours, QA testing sessions, upcoming deployments, etc. The goal would be both for us and for contributors to have a clearer view of what's coming up. I may take a stab at a [[mw:Project:Calendar]] next week and transclude part of it into [[mw:How to contribute]]. So, I've done this: https://www.mediawiki.org/wiki/User:Guillom/sandbox For now, it only contains content taken from [[Events]] and the testing/bugs wheel. I'm fairly happy with functionality and looks, and I think we can start using it and adding more events. The information is centralized on that page, but using LST, it's also possible to selectively pull information from it to display on topic-specific pages. See https://www.mediawiki.org/wiki/User:Guillom/sandbox2 for examples. There is probably room for improvement; feel free to add to the talk page or the #Todo section. If [[wikia:uncyclopedia:Nobody cares]], I'll move this to the proper place and I'll start transcluding its content. PS: For those interested, there's some doc at https://www.mediawiki.org/wiki/Template:Event -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Project calendar
On Fri, Jan 25, 2013 at 1:27 PM, Guillaume Paumier gpaum...@wikimedia.org wrote: So, I've done this: https://www.mediawiki.org/wiki/User:Guillom/sandbox On second thought, it's probably better to use permalinks for the list archives: https://www.mediawiki.org/w/index.php?oldid=634498 The information is centralized on that page, but using LST, it's also possible to selectively pull information from it to display on topic-specific pages. See https://www.mediawiki.org/wiki/User:Guillom/sandbox2 for examples. https://www.mediawiki.org/w/index.php?oldid=634501 -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia sites to move to primary data center in Ashburn, Virginia. Disruption expected.
currently operates a total of about 885 servers, and serves about 20 billion page views a month, on a non-profit budget that relies almost entirely on donations from readers. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Next bugday: Jan 29, 17:00-23:00UTC
Hi, On Fri, Jan 18, 2013 at 2:15 PM, Andre Klapper aklap...@wikimedia.org wrote: Hi everybody, I am happy to announce and invite you to the next Wikimedia Bugday: Tuesday, January 29th, 17:00-23:00 UTC [1] [1] Timezone converter: http://www.timeanddate.com/worldclock/converter.html Pro tip: If you use the event announcer, you can link directly to that date time :) http://www.timeanddate.com/worldclock/fixedtime.html?msg=Wikimedia%2FMediaWiki+bugdayiso=20130129T17ah=6 More generally, and to follow up on our discussion yesterday about better coordination, I think I'd like to integrate that kind of announcements into a central page on mw.o that would also list Tech chats, tech-related IRC office hours, QA testing sessions, upcoming deployments, etc. The goal would be both for us and for contributors to have a clearer view of what's coming up. I may take a stab at a [[mw:Project:Calendar]] next week and transclude part of it into [[mw:How to contribute]]. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Update on Ashburn data center switchover / migration – target date is week of 1/22/13
Hi, On Fri, Jan 11, 2013 at 10:48 PM, Jay Ashworth j...@baylink.com wrote: I have forwarded this to the Outages mailing list, so that people who want to know/get complaints about such things have advance warning. Thank you :) For those, like me, who upon reading that message wondered if there was an outages-l among the gazillion Wikimedia mailing lists, Jay is referring to a third-party mailing list: https://puck.nether.net/mailman/listinfo/outages -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering December 2012 report
://www.mediawiki.org/wiki/Outreach_Program_for_Women(OPW). 4 of them are funded by the Wikimedia Foundation and 2 by Google through an agreement with the GNOME Foundation, organizers of the program. They will work as full-time interns under the supervision of MediaWiki mentors between January and March 2013. We got 10 submissions from about 25 people interested. The rather open and participatory selection processhttps://www.mediawiki.org/wiki/Mentorship_programs/Selection_processwe have defined for OPW will be used as a basis for future mentoring programs. We've also started matchmaking for the LevelUphttps://www.mediawiki.org/wiki/Mentorship_programs/LevelUpmentorships for the coming quarter. *Technical communicationshttps://www.mediawiki.org/wiki/Technical_communications * [edithttps://www.mediawiki.org/w/index.php?title=Technical_communications/statusaction=edit ] Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom published a project plan and timelinehttps://www.mediawiki.org/wiki/Technical_communications/Fall_2012_consultationfor the consultation process started in October about how to improve 2-way communication between the technical and editing communities. He summarizedhttps://www.mediawiki.org/wiki/Technical_communications/Fall_2012_consultation#Phase_2:_Summary_and_wider_outreachthe results of the first phase and reached out to the wikitech-ambassadors listhttp://lists.wikimedia.org/pipermail/wikitech-ambassadors/2012-December/000105.htmlto widen the consultation process by proxy. After consolidation and prioritization of the results, the most feasible solution appeared to be to grow a network of ambassadorshttps://meta.wikimedia.org/wiki/Tech/Ambassadors, which he started to organize on meta. Unrelatedly, Guillaume made a list of 2012 tech blog postshttps://www.mediawiki.org/wiki/Technical_communications/Tech_blog_activityto map tech blog activity by month subdepartment (with priority activities listed separately). Work on setting up a Volunteer product managerhttps://blog.wikimedia.org/2012/11/21/lead-development-process-product-adviser-manager/program is also underway. Quim Gil https://www.mediawiki.org/wiki/User:Qgil sorted out Social mediahttps://www.mediawiki.org/wiki/Social_mediachannels, and we now have @MediaWiki handles for identi.ca http://identi.ca/mediawiki, Twitterhttps://twitter.com/#%21/MediaWiki, Facebook https://www.facebook.com/MediaWikiProject and Google+https://plus.google.com/u/0/b/103470172168784626509/103470172168784626509/posts. He published the community metrics November reporthttps://www.mediawiki.org/wiki/Community_metrics/November_2012and a blog posthttps://blog.wikimedia.org/2012/12/10/introducing-mediawiki-community-metrics/introducing this new activity. *Volunteer coordination and outreachhttps://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach * [edithttps://www.mediawiki.org/w/index.php?title=Volunteer_coordination_and_outreach/statusaction=edit ] MediaWiki Groups https://www.mediawiki.org/wiki/Groups became official and the first proposals https://www.mediawiki.org/wiki/Groups/Proposalsare going through the approval process. As a side effect, a process for requesting regional mediawiki-themed mailing listshttps://www.mediawiki.org/wiki/Groups#Local_vs_regionalhas been created with mediawiki-indiahttps://lists.wikimedia.org/mailman/listinfo/mediawiki-indiaas the first case. At least three Wikimedia-related talks have been accepted at FOSDEM https://www.mediawiki.org/wiki/Events/FOSDEM. Language engineeringhttps://www.mediawiki.org/wiki/Wikimedia_Language_engineering *Language tools https://www.mediawiki.org/wiki/Language_tools* [edithttps://www.mediawiki.org/w/index.php?title=Language_tools/statusaction=edit ] Development of the new user interface for Translate, as well as the translation editor functionality, continued at full pace throughout the month of December, with iterative feature development and user experience improvements. Santhosh Thottingal and Niklas Laxström are leading development and Pau Giner is focusing on optimizing user experience elements. The team also released the latest version of the MediaWiki Language Extension Bundle. Increased support for language variants, alternate language codes were added to the Universal Language Selector. Alolita Sharma continued to work with Red Hat's localization and internationalization teams to evaluate localization data, translation tools and internationalization tools and technologies. *Milkshake https://www.mediawiki.org/wiki/Milkshake* [edithttps://www.mediawiki.org/w/index.php?title=Milkshake/statusaction=edit ] More language input methods contributed by language communities were added to the jquery.ime library. Other newsPau Giner and Amir Aharoni participated in the Open Tech Chat this month to talk about best practices in multilingual user testing and internationalization. Amir Aharoni also participated in mentoring OPWhttps://www.mediawiki.org/wiki/Outreach_Program_for_Womencandidate
Re: [Wikitech-l] Updated schedule for ResourceLoader, Lua, etc.
Hi, On Wed, Jan 2, 2013 at 9:16 AM, John Erling Blad jeb...@gmail.com wrote: What I would like is really something simple that says when something is to be made available, and what would be the visible feature. At least what is to be expected for the next 2-3 months, preferable with something about which roll-out cycle and a last date to give a go (or stop) on the planned roll-out. Besides the Annual goals page linked to by MZMcBride, https://www.mediawiki.org/wiki/Roadmap attempts to give a visibility over the next few months. It indicates, for example, that in December 2012, ResourceLoader2 was in the list of other projects on radar (although I'm not sure it's comforting, considering that the other item there is LQT3, which was ended on June 30th) As for Lua, it's also on the Roadmap page, and the activity page gives a few milestones: https://www.mediawiki.org/wiki/Lua_scripting#Milestones_by_quarter . Full deployment of Lua to the production cluster is scheduled for January-March 2013. For a visibility over the next few days, http://wikitech.wikimedia.org/view/Deployments provides a schedule of deployments (although it lists slots more than what changes are actually deployed). HTH, -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering November 2012 report
Gilhttps://www.mediawiki.org/wiki/User:Qgil, the new technical contributor coordinator who started working with the Wikimedia foundation in November. They continued to follow up on contacts (such as those gained at October's Grace Hopper Celebration of Women in Computing), recruit new contributors to the Wikimedia tech community, and mentor newer contributors. The weekly online tech chatshttps://www.mediawiki.org/wiki/Meetingscontinued on Thursdays. Sumana and others continued to grant developer access https://www.mediawiki.org/wiki/Developer_access and work on Gerrit project ownership requestshttps://www.mediawiki.org/wiki/Git/Gerrit_project_ownership . Language engineeringhttps://www.mediawiki.org/wiki/Wikimedia_Language_engineering *Language tools https://www.mediawiki.org/wiki/Language_tools* [edithttps://www.mediawiki.org/w/index.php?title=Language_tools/statusaction=edit ] In November 2012, the Language Engineering team travelled to India for 10 days together with the Mobile team for 6 events in total: the two-day Language Summit https://www.mediawiki.org/wiki/Pune_LanguageSummit_November_2012at the Red Hat offices in Pune, a Language Engineering Community Meetup in Punehttps://www.mediawiki.org/wiki/Pune_Language_Engineering_Meetup_November_2012, the three-day DevCamp 2012 Bangalorehttps://www.mediawiki.org/wiki/Bangalore_DevCamp_November_2012, a Language Engineering Community Meetup in Bangalorehttps://www.mediawiki.org/wiki/Bangalore_Language_Engineering_Meetup_November_2012, a presentation by Erik Moellerhttps://www.mediawiki.org/wiki/User:Eloquenceon the current state of tech in the Wikimedia Foundation, and *Coffee with Arky*, a meetup of Mozilla users. The rest of the month, development time was spent on completing the Universal Language Selector, and getting it to a state where it could be put in maintenance mode for a few months. In April 2013, phase two of the ULS will start, will consist of adding content language selection. The Language Engineering designers completed the design for the Translation UX https://www.mediawiki.org/wiki/Translation_UX project, for which development has commenced end of November, and will continue for 8 sprints of a fortnighthttps://mingle.corp.wikimedia.org/projects/internationalization/cards/1962, until mid-March 2013. *Milkshake https://www.mediawiki.org/wiki/Milkshake* [edithttps://www.mediawiki.org/w/index.php?title=Milkshake/statusaction=edit ] The first phase of the Universal Language Selectorhttps://www.mediawiki.org/wiki/Universal_Language_Selector(ULS) was completed in November. The jQuery modules jQuery.ULS https://github.com/wikimedia/jquery.uls, jQuery.IMEhttps://github.com/wikimedia/jquery.uls, jQuery Webfonts https://github.com/wikimedia/jquery.webfonts and jQuery i18n https://github.com/wikimedia/jquery.i18n have had their first stable version. The Universal Language Selectorhttps://www.mediawiki.org/wiki/Extension:UniversalLanguageSelectorMediaWiki extension is now being used on Wikidata https://en.wikidata.org/wiki/. During the DevCamp in Bangalorehttps://www.mediawiki.org/wiki/Bangalore_DevCamp_November_2012, experimentations were done with ULS in Android, a Chrome extension was created to make jQuery.IME usable in the Chrome web browser, and an extension for Firefox implementing the input methods is underway. The first contributions by non-Wikimedia developers have been made, which indicates that the jQuery extensions are getting some attention. The Wikimedia Language Engineering team will now put the modules and MediaWiki extension in maintenance mode until April 2013. Wikidata https://meta.wikimedia.org/wiki/Wikidata *The Wikidata project is funded and executed by Wikimedia Deutschlandhttps://meta.wikimedia.org/wiki/Wikimedia_Deutschland/en .* The repository side of Wikidata has been launchedhttps://en.wikipedia.org/wiki//Wikipedia:Wikipedia_Signpost/2012-10-29/Technology_reporton http://www.wikidata.org. It contains the results of phase 1 (language links) and has already attracted a community to maintain the wiki. Meanwhile, the Wikidata team has continued work on Phase 2 of Wikidata (Infoboxes) to add statements with values to the items in the Wikidata repository. The team improved the propagation of changes from the repository to the client and the messaging in Recent Changes. There is a constant exchange with Wikimedia Foundation engineers about the upcoming deployment cycle. Feedback and questions are welcome on the mailing listhttps://lists.wikimedia.org/mailman/listinfo/wikidata-land on meta https://meta.wikimedia.org/wiki/Talk:Wikidata. Future The engineering management team continues to update the *Software deploymentshttp://wikitech.wikimedia.org/view/Software_deployments * page weekly, providing up-to-date information on the upcoming deployments to Wikimedia sites, as well as the *engineering roadmaphttps://www.mediawiki.org/wiki/Roadmap *, listing ongoing and future Wikimedia engineering efforts. -- Guillaume Paumier
Re: [Wikitech-l] LabeledSectionTransclusion performance problems
On Fri, Nov 30, 2012 at 10:07 AM, Merlijn van Deen valhall...@arctus.nl wrote: After the new version of LabeledSectionTransclusion (LST) was deployed on itwikisource, performance issues popped up. itwikisource's main page makes heavy use of LST, and the new version is clearly heavier than the old one. As a sidenote: because of the performance issues, the most recent changes to the LST extension will probably be reverted today (Friday, November 30). If you made changes to articles or templates to accommodate the new version or benefit from new features, you may want to revert those changes temporarily. -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Help needed to complete and expand the Wikimedia glossary
Hi, The use of jargon, acronyms and other abbreviations throughout the Wikimedia movement is a major source of communication issues, and barriers to comprehension and involvement. The recent thread on this list about What is Product? is an example of this, as are initialisms that have long been known to be a barrier for Wikipedia newcomers. A way to bridge people and communities with different vocabularies is to write and maintain a glossary that explains jargon in plain English terms. We've been lacking a good and up-to-date glossary for Wikimedia stuff (Foundation, chapter, movement, technology, etc.). Therefore, I've started to clean up and expand the outdated Glossary on meta, but it's a lot of work, and I don't have all the answers myself either. I'll continue to work on it, but I'd love to get some help on this and to make it a collaborative effort. If you have a few minutes to spare, please consider helping your (current and future) fellow Wikimedians by writing a few definitions if there are terms that you can explain in plain English. Additions of new terms are much welcome as well: https://meta.wikimedia.org/wiki/Glossary Some caveats: * As part of my work, I'm mostly interested in a glossary from a technical perspective, so the list currently has a technical bias. I'm hoping that by sending this message to a wider audience, people from the whole movement will contribute to the glossary and balance it out. * Also, I've started to clean up the glossary, but it still contains dated terms and definitions from a few years ago (like the FundCom), so boldly edit/remove obsolete content. Thank you, -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Help needed to complete and expand the Wikimedia glossary
On Tue, Nov 20, 2012 at 8:23 PM, K. Peachey p858sn...@gmail.com wrote: On Wed, Nov 21, 2012 at 4:55 AM, Guillaume Paumier gpaum...@wikimedia.org wrote: * Also, I've started to clean up the glossary, but it still contains dated terms and definitions from a few years ago (like the FundCom), so boldly edit/remove obsolete content. I don't believe these ever become onsolete, The wording still exists and will be helpful to whomever vists older historical pages and wants to look up the terms. If something must be done with them, Mark them as obsolete but defiantly don't remove them. Yes, when I said remove obsolete content, I meant remove obsolete definitions, not remove historical terms. For instance, Officers links to https://meta.wikimedia.org/wiki/Official_positions , which aren't used any more. So, Officers should still be there, and it should still link to that page, but it should be clear that such positions aren't held any more. Sorry if I wasn't clear before. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering October 2012 report
, and deployed a new banner impression filter. Engineering community team *Bug management https://www.mediawiki.org/wiki/Bug_management* [edithttps://www.mediawiki.org/w/index.php?title=Bug_management/statusaction=edit ] New Bug Wrangler Andre Klapperhttps://www.mediawiki.org/wiki/User:Malyackohad many discussions with different stakeholders to get a better impression of how work is done, how people interact with the bug tracker, what the expectations are and what policies might be needed. He investigated the product/component organization within bugzilla, started triaging incoming and older reports, and did maintenance work (creation and partial cleanup of products and components). bugzilla.wikimedia.org was upgraded to 4.0.8 with the help of Daniel Zahn, and investigations started to determine how urgent an upgrade to 4.2 was with regard to functionality improvements. Plans for the next month include improving documentation on bug management and bug triaging, and describing interactions between the bug wrangler and the different teams. *Summer of Code 2012https://www.mediawiki.org/wiki/Summer_of_Code_2012/management * [edithttps://www.mediawiki.org/w/index.php?title=Summer_of_Code_2012/management/statusaction=edit ] The Wikimedia engineering community continues to help the 2012 GSoC students improve their projects towards the goal of release and deployment. Sumana Harihareswara aims to lead a postmortem discussion in November. Rob Lanphier and Sumana attended a GSoC Mentors' Summit in October, and discussed mentor recruitment http://etherpad.osuosl.org/veFnJ0z05K, community metrics http://gsoc-wiki.osuosl.org/index.php/Community_Metrics, how to be more effective mentors, student selection strategieshttp://gsoc-wiki.osuosl.org/index.php/Ideas_an_techniques_to_improves_student_selection_phase, PHP http://gsoc-wiki.osuosl.org/index.php/PHP and code review tools, and other related topics. As a follow-up to Summer of Code, the MediaWiki community is discussing whether to participate in Google Code-Inhttps://www.mediawiki.org/wiki/Google_Code-In . *Technical communicationshttps://www.mediawiki.org/wiki/Technical_communications * [edithttps://www.mediawiki.org/w/index.php?title=Technical_communications/statusaction=edit ] This activity was revived as its scope was expanded to include not only on-wiki engineering project documentation, but more generally the improvement of communications between Wikimedia contributors and the technical community (MediaWiki developers, Operations engineers, etc.). Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom prepared and started a wide and open discussion with editors on some local wikis to identify issues and discussion possible solutions. Management is currently reviewing options to determine the direction this activity will follow in future months. *Volunteer coordination and outreachhttps://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach * [edithttps://www.mediawiki.org/w/index.php?title=Volunteer_coordination_and_outreach/statusaction=edit ] Sumana Harihareswara https://www.mediawiki.org/wiki/User:Sumanahcontinued to follow up on contacts (such as those gained at October's Grace Hopper Celebration of Women in Computing), recruit new contributors to the Wikimedia tech community, and mentor newer contributors. She granted developer access https://www.mediawiki.org/wiki/Developer_access and Gerrit project ownership requestshttps://www.mediawiki.org/wiki/Git/Gerrit_project_ownership, and worked on getting more volunteer developers +2https://www.mediawiki.org/wiki/%2B2status in MediaWiki core: 8 volunteers now have MediaWiki core maintainership. Sumana also published a retrospective of the 2012 Berlin Hackathonhttps://www.mediawiki.org/wiki/Berlin_Hackathon_2012/Retrospectiveand updated the list of towards a better understanding of which parts of the codebase are maintained, and by whom. Hiring for a Volunteer Engineering Coordinator to work on volunteer coordination and outreach is almost finished. Wikidata https://meta.wikimedia.org/wiki/Wikidata *The Wikidata project is funded and executed by Wikimedia Deutschlandhttps://meta.wikimedia.org/wiki/Wikimedia_Deutschland/en .* The Wikidata team has worked on initial parts of Phase 2 of Wikidata (Infoboxes) and worked together with the WMF to get Wikidata deployed on http://www.wikidata.org. A big step towards this deployment was the merge of the content handler branchhttps://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2012-10-15/Technology_reportinto MediaWiki core. This allows MediaWiki to handle other content types besides just wikitext. In addition, the team is looking for help with the initial design of the Main Pagehttp://lists.wikimedia.org/pipermail/wikidata-l/2012-October/001104.htmlof wikidata.org. A draft was also published by the team discussing how the propagation of changes from a repository to the clientshttps://meta.wikimedia.org/wiki/Wikidata/Notes/Change_propagationshould work
[Wikitech-l] Wikimedia engineering September 2012 report
Hi, The report covering Wikimedia engineering activities in September 2012 is now available. Wiki version: https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2012/September Blog version: https://blog.wikimedia.org/2012/10/03/engineering-september-2012-report/ -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering August 2012 report
Hi, The report covering Wikimedia engineering activities in August 2012 is now available. Wiki version: https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2012/August Blog version: https://blog.wikimedia.org/2012/09/04/engineering-august-2012-report/ -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Code review statistics and trends
Hi, On Thu, Aug 23, 2012 at 3:37 AM, Rob Lanphier ro...@wikimedia.org wrote: Our Analytics crew have worked out how to generate a graph that gives us a view into our code review backlog: http://gerrit-stats.wmflabs.org/graphs/mediawiki There seems to be a 10-day lag (no data after August 21st). Is this a bug or a feature? -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Mailman archives broken?
Hi, On Sat, Aug 18, 2012 at 12:42 AM, Daniel Zahn dz...@wikimedia.org wrote: Alright, so inserted the exact number of messages i deleted on Aug. 2 in the same places/dates, that should bring message numbering and links back to the same state before i deleted that thread. As others have mentioned before there have been other inconsistencies in it before though, so you can most likely still find other issues but to the best of my knowledge they should be unrelated. Especially anything that is older than April 2012 should not have been affected by my recent change. Thanks for your efforts, Daniel. It doesn't appear that they've been entirely successful from what I can see (details below), but I appreciate that you've gone out of your way to try to fix this. == Examples == After April 2012: The link http://lists.wikimedia.org/pipermail/wikitech-l/2012-July/061691.html was posted on meta to reference a message of mine from July 2012. That ID (061691) had to be changed to 061614 after the rebuild from 2 weeks ago (i.e. a translation of -77). After yesterday's rebuild, it's now at ID 061621 (a translation of +7 consistent with the 7 empty messages you've reinserted). Before April 2012: The link http://lists.wikimedia.org/pipermail/wikitech-l/2004-February/008418.html was posted recently on wiki to reference the 2004 server move from San Diego to Tampa. That link now points to an unrelated message. I've tried a translation of -77 but I don't think that's the original message either (there are several messages from Feb. 2004 about the server move). So, it appears that the archives have been corrupted inconsistently besides the simple translations of -77 or -7. Someone can probably verify that with other links (e.g. from the Signpost pages). This is also consistent with the fact, pointed out by MZMcBride, that the August 2012 archive page contains several No subject messages that clearly don't belong there They've had their headers removed, and they have IDs like 001363 or 004210 (that would roughly put them around November 2002 and May 2003 respectively). The conclusion is that the archives have probably been irrevocably corrupted and that we'll have to fix all links manually (we can't use a bot since there is no consistent translation of IDs). -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Mailman archives broken?
Hi, On Thu, Aug 16, 2012 at 7:07 PM, Daniel Zahn dz...@wikimedia.org wrote: the last time we had to rebuild archives was about 2 weeks ago. Unfortunately this is a major drawback of removing messages from archives as you pointed out and we are aware of it. We had a thread there though that contained private information and we also did not want to refuse the request of the person affected to remove their data. A subsequent request that followed shortly after was actually rejected for this very reason. In the future such requests will more likely rejected and if unavoidable we will just XXX out information instead of removing complete threads to avoid this from happening again. Everybody on this list please be extra careful about posting private information to a public list you might regret in the future. Sorry for breaking links, we are aware URLs should never change if at all possible. Thank you for the explanation, Daniel. -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Mailman archives broken?
Hi, On Fri, Aug 17, 2012 at 12:38 PM, Federico Leva (Nemo) nemow...@gmail.com wrote: I doubt fixing this requires rewriting mailman. It only requires dummy messages to be reinserted where they've been deleted and the archives to be rebuilt after this I've added your suggestion to a new RT ticket to Attempt to fix mailman/pipermail permalinks, and let the list know if it's not possible. -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Mailman archives broken?
Hi, I was told yesterday that the mailman/pipermail archives were broken, in that permalinks were no longer linking to the messages they used to link to (therefore not being permalinks at all). I know this happened at least once in the past, when the archives were rebuilt. Retroactively fixing permalinks on-wiki and elsewhere is a nightmare (particularly for old messages used to source early Wikimedia history), and we're still finding tons of obsolete links today. I'm hoping that whatever caused the permalinks to be changed again can be swiftly reverted, so that we don't end up with another huge pile of obsolete links. Does anyone have any more information about what happened this time, and if there's any chance links will be returned to their previous state? I haven't been able to find a thread or recent bug about this issue. Thanks, -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering July 2012 report
Hi, The report covering Wikimedia engineering activities in July 2012 is now available. Wiki version: https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2012/July Blog version: https://blog.wikimedia.org/2012/08/02/engineering-july-2012-report/ -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] New, lower traffic, announcements only email list for Wikimedia developers
Hi, [cc:ing wikimedia-l because this message is also for Wikimedia users.] I've been asked to weigh in on this topic, because this is going to be an area of focus for me over the coming year. I've been tasked with improving the 2-way communication between users developers, possibly using the wikitech-ambassadors list as a medium. A few people have already explained the scope of the different lists, but here's my understanding: * wikitech-l: A high-traffic, unapologetically technical, discussion list for developers talking to developers * wikitech-announce: A low-traffic, plain English, announce-only list for developers talking to Wikimedia users * wikitech-ambassadors: A (currently) low-traffic, mostly-announce list for developers talking to Wikimedia users * mediawiki-announce: A low-traffic, announce-only list for developers talking to (mostly 3rd-party) MediaWiki users * wikimediaannounce: A low-traffic, plain English, announce-only list for general Wikimedia usues. And the possible change would be for wikitech-ambassadors to become a medium-to-high-traffic, plain English, list for discussion between developers and Wikimedia users, to report issues, share ideas and provide feedback in unapologetically layman terms. The Ambassadors part also means that users who are on that list will have a role in disseminating information to their local communities, and reporting back issues possibly raised on local wikis. FYI, if you're at Wikimania this week, this 2-way communication channel between developers and users will be a main focus of the Transparency discussion with Sumana, Rob and myself on Saturday 14 at 10:30 in Room 310: https://wikimania2012.wikimedia.org/wiki/Submissions/Transparency_and_collaboration_in_Wikimedia_engineering I've also just noticed that there are two other talks related to this topic: * Oliver's Engaging the Community: What We've Tried and Where We're Going (Thursday July 12, 11:40, Room 310) https://wikimania2012.wikimedia.org/wiki/Submissions/Engaging_the_Community:_What_We%27ve_Tried_and_Where_We%27re_Going * Tilman and Max's Movement Broadcasting - 'Stop Spamming' vs. 'Nobody Told Me (Thursday, July 12, 14:00, Room 302) https://wikimania2012.wikimedia.org/wiki/Submissions/Movement_Broadcasting_-_%27Stop_Spamming%27_vs._%27Nobody_Told_Me%27 If you can't attend any of those sessions, but you want to discuss / rant / share ideas about (mis)communication between MediaWiki developers and Wikimedia users, please come to me at any time during the hackathon or the conference (If we don't already know each other, my photo is on https://wikimediafoundation.org/wiki/Staff_and_contractors ) And if you're not at Wikimania, feel free to drop me an e-mail with your thoughts on the subject. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Merge of wikitech and labsconsole
Hi, On Mon, Jun 18, 2012 at 2:38 PM, Chad innocentkil...@gmail.com wrote: Awesome :) Probably also worth adding a quick box to suggest a rename of the page when it's imported. Added. I think doing it this way is kind of neat, especially if there's an easy way to see all the content that's not been tagged yet. I've been thinking about this, and I can't think of a way to have an automated list that would basically be the difference between Special:Allpages and Special:Whatlinkshere/Template:Foo Unless someone comes up with a better solution (or wants to quickly set up a bot to maintain the list, which seems overkill), having a list of all pages, going through them alphabetically, and s-ing or removing the pages done might be the simplest solution. If someone wants to take a look, the script is currently at: https://www.mediawiki.org/wiki/User:Robmoen/fixmeGadget.js I've tested it on mw.o and it seems to work great, except for an annoying bug (if someone with JS knowledge wants to fix it): https://www.mediawiki.org/wiki/User_talk:Robmoen/fixmeGadget.js I haven't yet been able to make it work on wikitech.wm.o (are userscripts enabled there?) If this makes sense, I can create the evaluation template and we can get going. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Merge of wikitech and labsconsole
Hi, On Mon, Jun 4, 2012 at 2:03 PM, Chad innocentkil...@gmail.com wrote: On Mon, Jun 4, 2012 at 7:59 AM, Ryan Lane rlan...@gmail.com wrote: We need to identify which documentation should and should not be migrated over when it occurs, as there is a lot of documentation that is old/inaccurate and should be deleted. We'd love to have some community support for this, if anyone wants to help out. If we enabled wikitech as an import source for labsconsole, this process could get underway. I'd suggest making some new category on wikitech Stuff to be moved to Labsconsole that pages can be put in once they've been vetted. Rob Moen has been working on a simple JS tool that facilitates the tagging process. Basically, instead of manually tagging the pages with a different template for each action (archive, delete, keep), there's a simple box that shows up at the top of the page, and you can tag the page with a few clicks. The goal of this tool is to allow people with expertise and/or authority to quickly tag the content. Once the content has been tagged, other people can deal with the actual move. So far the possible actions are: * archive * delete * keep and (optionally) expand and/or update The actions use radio buttons, and the options checkboxes. This list is just a start; if you see other or better qualifiers, we can change them. Do you think this would be useful, or do you prefer to stick to manual templating/categorizing? Also, the gadgets extension isn't currently installed on wikitech.wm.o. I'm not sure it's worth going through the trouble of installing it (would it even be compatible with the 1.17 MediaWiki that's running it?). Perhaps it would be simpler to just add the code snippet to [[MediaWiki:Vector.js]] for the duration of the cleanup? -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering May 2012 report
Hi, The report covering Wikimedia engineering activities in May 2012 is now available. Wiki version: https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2012/May Blog version: https://blog.wikimedia.org/2012/06/13/engineering-may-2012-report/ -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Architecture of Open Source Applications book is out
Hi, You may have seen the announcement on the Wikimedia blog last week, but someone (rightfully) noticed that we hadn't announced it on the lists: https://blog.wikimedia.org/2012/05/11/book-architecture-mediawiki-open-source-applications/ -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering report for April 2012
Hi, The report covering Wikimedia engineering activities in April 2012 is now available. Wiki version: https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2012/April Blog version: https://blog.wikimedia.org/2012/05/04/engineering-april-2012-report/ -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation http://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering report for March 2012
Hi, The report covering Wikimedia engineering activities in March 2012 is now available. Wiki version: https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2012/March Blog version: https://blog.wikimedia.org/2012/04/05/engineering-march-2012-report/ -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation http://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering report for February 2012
Hi, The report covering Wikimedia engineering activities in February 2012 is now available. Wiki version: https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2012/February Blog version: https://blog.wikimedia.org/2012/03/07/engineering-february-2012-report/ -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation http://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Upcoming deployment of MediaWiki 1.19 to Wikimedia sites.
Greetings, The Wikimedia Foundation is planning to upgrade MediaWiki, the software powering Wikipedia and its sister sites, to its latest version. The upgrade will happen in several stages over the month, starting this week. You can still help to test it before it is enabled, to avoid disruption and breakage. More information: * Announcement on the Wikimedia blog: https://blog.wikimedia.org/2012/02/11/mediawiki-1-19-deployment/ * The announcement in other languages: https://www.mediawiki.org/wiki/MediaWiki_1.19/Deployment_announcement Thank you for your understanding. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] RFC Complete Rewrite of Mobile Frontend Rename MobileFrontend2
On Sun, Feb 12, 2012 at 3:01 PM, Chad innocentkil...@gmail.com wrote: On Sun, Feb 12, 2012 at 9:00 AM, Yaron Koren ya...@wikiworks.com wrote: If you're looking for an extension name, here are some possibilities: MobileAccess MobileDisplay MobileView Mobilize (a little play on words there) All good colors to paint our bike shed :) Also I'll throw MobileUI out there for consideration. I'll see your MobileUI, and raise you a MobileFrontendSkinDeluxe, and a MobileFrontendProfessionalEdition. -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Common photo management plugins for MediaWiki
Hi, On Fri, Feb 10, 2012 at 7:01 PM, lakmal padmakumara lakmalpadmakum...@gmail.com wrote: After going through the suggested idea list from the community ,I developed a good interest in the above mentioned project where the final outcome would be set of plugins for MediaWiki to communicate with common photo management APIs ( Etc ,iPhoto ,Lightroom ..) . I would be grateful if one of you can fill me up with the current status of this project idea . In the sense I would like to know whether someone is already working on this or this is sill open for an enthusiast to start working on :) . FYI, there's also a group of French students working on a (partially developed) export plugin to Wikimedia Commons from digiKam ( http://www.digikam.org ), and they may also create an export plugin for Shotwell too ( http://yorba.org/shotwell/ ), depending on their progress. There may be some common feature list front-end choices that you can reuse for your plugins. Unfortunately, I've never gotten around to consolidating the documentation. Tell me if you want me to send a list of pointers to the scattered doc. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Common photo management plugins for MediaWiki
Hi, On Sun, Feb 12, 2012 at 3:49 PM, lakmal padmakumara lakmalpadmakum...@gmail.com wrote: Great to hear ,I think I should take their progress in to my consideration in order to define the scope of my contribution as there is no point of reinventing the wheel.Thanks a lot for letting me know about this and if you have please send me any links that I can refer to their on going works. On Sun, Feb 12, 2012 at 4:03 PM, Mike Dupont jamesmikedup...@googlemail.com wrote: Thats great news! Any code to find? digikam is great, but also huge. I am using shotwell all the time. Here's a quick summary: Last year, I worked with a group of university students on a Qt library to interface with the MediaWiki API. They didn't implement the whole API, but enough for a proof-of-concept editor, and a prototype of export plugin to Wikimedia Commons. The plugin was developed as a component of the KIPI plugins. The export plugin wasn't released because, although it worked, it didn't implement features specific to Wikimedia Commons, e.g. proper support for descriptions, licenses, categories, etc. See https://bugs.kde.org/show_bug.cgi?id=206842#c11 for a summary of where the plugin's currently at. The university program ended this year, which means there was no new group of students to complete the project. Fortunately, Jean-Frédéric, a friend of mine from the French chapter (Cc:ed) had the opportunity to propose this project as part of another student program. As far as I know, they haven't started to work on it yet. There's some basic documentation (in French) at https://www.mediawiki.org/wiki/User:Jean-Fr%C3%A9d%C3%A9ric/digiKam Unordered list of other links to scattered documentation as promised: * http://www.gpaumier.org/blog/297_digikam-the-perfect-tool-for-wikimedia-commons-photographers/ — What started the whole thing. * https://meta.wikimedia.org/wiki/MediaWiki-Silk_student_project_report — More context on the original student project. Unfortunately, I never really got around to writing the report. * http://community.kde.org/IUP_ISI/MediaWiki-Silk — The former student team's hub; might contain some useful information. * https://bugs.kde.org/show_bug.cgi?id=206842 — Tracking bug for the export plugin in KDE's bug tracker. * http://youtu.be/Cc8quyp2XBA?t=53m51s — A short presentation of the library the export plugin at Wikimania 2011 * https://projects.kde.org/projects/extragear/libs/libmediawiki/repository — The library's code in the KDE code repository * http://techbase.kde.org/Development/Tutorials/Libmediawiki — A tutorial on how to use the library * https://projects.kde.org/projects/extragear/graphics/kipi-plugins/repository/revisions/master/show/mediawiki — The current export plugin's code in the KDE code repository I think that's pretty much it. Feel free to ping me and Jean-Frédéric if you want to coordinate further, or if you need more information. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering report for January 2012
Hi, The report covering Wikimedia engineering activities in January 2012 is now available. Wiki version: https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2012/January Blog version: https://blog.wikimedia.org/2012/02/08/engineering-january-2012-report/ -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Call for Participation - Wikimania 2012 - deadline March 18th
Hi, On Sat, Jan 28, 2012 at 12:04 AM, Brion Vibber br...@pobox.com wrote: Just to confirm, is the abstract meant to be no less than 300 words as it says in the template or no more than 300 words? I'm a little short on mine if it's meant to be no less than 300. :) It actually is no less than 300 words; I think it's supposed to be a high-pass filter for submissions, to weed out proposals that aren't serious. That said, in some cases, 250 words are largely enough to describe a serious submission, so I wouldn't worry too much about reaching exactly 300 words. If a proposal is strong, it shouldn't matter (much). -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation http://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering report for December 2011
Hi, The report covering Wikimedia engineering activities in December 2011 is now available. Wiki version: https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2011/December Blog version: https://blog.wikimedia.org/2012/01/07/engineering-december-2011-report/ -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation http://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Multilingual Wordpress
Salut Sébastien, On Wed, Dec 28, 2011 at 11:44 AM, Seb35 seb35wikipe...@gmail.com wrote: I tried last days to mass-translate blog posts of the Foundation’s blog, aiming at building a parallel blog in French with the same posts, translated [1]. Some people are interested in regularly translating blog posts. So my question is: is it possible to make the Foundation’s blog multilingual? The specific plug-in you linked to is described as pure alpha, so I wouldn't necessarily be comfortable enabling it on our production blog (at least not yet). In principle, I'm personally not opposed to having a multilingual setup on the Wikimedia blog, though. I think it's a great idea, at least worth trying out. And as far as I know, other Communications people also find the idea interesting. I researched the topic a few weeks ago following a discussion we had, and the best bet back then was the WPML plugin: http://wpml.org ; it's a commercial plugin but it's not too expensive, and they have a fee-waiving program for nonprofits. The plugin includes a translation workflow, but I haven't tried it out. So: possible? difficult? thoughts? I'd say: possible, probably desirable, and possibly not too difficult. The real trick is going to be the choice of the tool, since we want something that works, stays maintained and doesn't overly complicate our own setup. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation http://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Who actually reads @wikimediatech ?
Hi all, We've had @wikimediatech accounts on twitter identica for some time now: * http://identi.ca/wikimediatech * https://twitter.com/#!/wikimediatech that basically broadcast every single action that is logged to the server admin log: * http://wikitech.wikimedia.org/view/Server_admin_log The account has 78 followers on identica and 430 on twitter (probably counting the spammers). I'm wondering if there are actually people reading all the stuff that's pushed through these channels. My gut feeling is that the few people reading these feeds are also those that would know to check the SLA if they encountered an issue, or know how to use the RSS feed of the SLA page if they really wanted the information in real time. Meanwhile, we don't really have social media channels dedicated to Wikimedia tech stuff, i.e. channels where we can actually post stuff, links, blog posts, outage info, etc and engage with a larger community of people interested in our tech operations. I feel that the accounts would be much more useful if we reduced the amount of semi-random information we post there. So, I'm basically proposing to repurpose the @wikimediatech accounts for this. Thoughts? Good idea? Bad idea? You don't care? -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation http://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Who actually reads @wikimediatech ?
On Tue, Nov 29, 2011 at 8:38 PM, Arthur Richards aricha...@wikimedia.org wrote: I read it, I like it, and I find it useful - particularly when I'm in transit. I agree it would be neat to be able to use twitter/identica for actual humans to post stuff, but I don't think these need to be mutually exclusive goals. Would it be silly to have separate accounts? One specifically for bot logging and one specifically for actual human communication? Not silly at all. As a matter of fact, while you were writing that, I was registering @wikitechlog on both services, which I think is a better alternative for automated notifications. So, unless there are serious concerns, we'll be switching the automated notifications to @wikitechlog, and we'll repurpose @wikimediatech for the human stuff. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation http://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Who actually reads @wikimediatech ?
On Tue, Nov 29, 2011 at 8:48 PM, Brandon Harris bhar...@wikimedia.org wrote: Do we *have* to rename the feeds? We rename *everything*. I'm unsure why we can't just create a different account for people, rather than subvert the existing one. WikimediaTechNews, maybe. I don't know. wikimediatech is shorter (which facilitates manual retweets) and frankly it's the name I would consider canonical for an account about wikimedia tech stuff (@wikitech is someone else). Plus, we get to leverage the existing readership, while at the same time offering the possibility to subscribe to the automated log notifications for people who still want to read them. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Who actually reads @wikimediatech ?
On Tue, Nov 29, 2011 at 8:57 PM, Brandon Harris bhar...@wikimedia.org wrote: There's only 78 followers. Most of them are staff. That's not a lot of people to leverage, so I'm not sure that's a valid point. 78 on identica, 430 on twitter Why not wmftech ? Because initialisms are plain Evil, and Wikimedia != WMF. If there is any other reason that you think should prevent us from doing the switch (besides personal comfort), I'm happy to hear them (on or off-list). -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation http://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Final mobile switch-over
Hi, On Fri, Nov 25, 2011 at 1:47 PM, Thomas Dalton thomas.dal...@gmail.com wrote: On 23 November 2011 19:13, Philip Chang pch...@wikimedia.org wrote: We are suggesting that a home page customized for mobile viewing is perhaps more suitable, but I also understand the point you are making and will take that into consideration. I don't think anyone disagrees with that. The question is over whether no home page at all (just a search bar) is better than a home page that hasn't been customised for mobile users. I'm not sure that it is. Conversely, one could argue that the question is over whether a working (but simplistic) home page is better than a home page full of content (but broken). I guess the correct way to answer the question is to determine what mobile users are most interested in when they load the main page: featured content, or a way to access specific content they're looking for using the search box. I don't have any data on this (perhaps Philip does), but intuitively (and based on my personal use) I'd think it's the latter. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation http://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering report for October 2011
Hi, The report covering Wikimedia engineering activities in October 2011 is now available. Wiki version: https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2011/October Blog version: http://blog.wikimedia.org/2011/11/03/wikimedia-engineering-october-2011-report/ -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation http://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Please review: MediaWiki architecture document
Hi, On Thu, Oct 27, 2011 at 6:54 PM, Jay Ashworth j...@baylink.com wrote: We'll submit the final draft to the book's editors in about a week, but before that I'd like to ask you guys to review the document. Mostly for accuracy (we don't want to publish something that contains factual errors), but other comments are encouraged as well. Guilliaume: Are you interested in style edits on this as well? And if so, is it still open? Yes, please, by all means. I'll be doing a final round of edits on Monday, which is when we'll submit the final draft. Thanks, -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation http://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Please review: MediaWiki architecture document
Hi, As you may know from previous postings to this list and the Wikimedia Blog, I've been working on a document presenting MediaWiki's architecture. The document will be integrated as a chapter in the second volume of the Architecture of open-source applications book. The reason the Wikimedia Foundation agreed to do this, besides the book, was because we thought that such a document would also prove useful for new developers who want to familiarize themselves with how MediaWiki works. See [1] for more context. I just finished most of the write-up, based on the input provided by developers, on the documentation on mw.o, on the doxygen doc, and on deep dives into the code. We'll submit the final draft to the book's editors in about a week, but before that I'd like to ask you guys to review the document. Mostly for accuracy (we don't want to publish something that contains factual errors), but other comments are encouraged as well. Please try to centralize the feedback on the document's talk page to avoid duplication between the mailing list and the talk page. You don't have to review everything; if you want to focus on a specific section, that's fine, and I'll be grateful for any help that you provide. Also, if you find the document useful, please say so on the talk page; it's really difficult to assess the impact of this kind of work, so any feedback will help us determine if we should attempt similar endeavors in the future. The document is at: https://www.mediawiki.org/wiki/MediaWiki_architecture_document/text ; be bold and feel free to edit the page directly, unless the changes are likely to be very disruptive. Many thanks in advance for your help; I'm available to answer any question on- or offlist. [1] https://www.mediawiki.org/wiki/MediaWiki_architecture_document -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation http://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikipedia Android app – Support Wikipedia version
Hi, 2011/10/7 Steven Walling steven.wall...@gmail.com: I think rather than have two identical versions in the Market, which would no doubt confuse a great many people [...] I'm not sure about this confusion thing. It's pretty common to have two identical versions of the same app, with one called Wikipedia (donation version) for example. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation http://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
