Wikitech-l December 2016

wikitech-l@lists.wikimedia.org

83 participants
79 discussions

Introduction for Gsoc 2017
by MAYANK JINDAL 10 Dec '16

10 Dec '16

Hi, My name is Mayank Jindal. I am third year undergraduate student currently studying at Indian Institute of Technology, Kharagpur. I want to take part in Gsoc-2017 from Wikimedia. I have knowledge of C, C++, JAVA, Python, Android app development and Web development and beginner in *Machine Learning, Artificial Intelligence.* I am very enthusiastic to learn new skills which would be required. Kindly guide me to proceed further. -- Kind Regards, Mayank Jindal, Third year undergraduate student, Indian Institute of Technology Kharagpur Mobile : +91- 7076670299 || 8875432718

4 5

Cancellation of January 2017 CREDIT showcase
by Adam Baso 09 Dec '16

09 Dec '16

Hi all - just a quick note we'll cancel the January 2017 CREDIT showcase <https://www.mediawiki.org/wiki/CREDIT_showcase> session. January is practically speaking really hard for ensuring that it works for most schedules. Meanwhile, be on the lookout for a survey for reflection on 2016's CREDIT. Thanks! -Adam

1 0

CREDIT in 37 minutes
by Adam Baso 09 Dec '16

09 Dec '16

Reminder, starting soon! On Wed, Nov 30, 2016 at 2:33 PM, Adam Baso <abaso(a)wikimedia.org> wrote: > Hello all - > > The next CREDIT showcase is a week from today - Wednesday, > 7-December-2016 at 1900 UTC (1100 San Francisco). > > https://www.mediawiki.org/wiki/CREDIT_showcase > > If you have a demo, please add it here: > > https://etherpad.wikimedia.org/p/CREDIT > > Last month there were demos on offline, IFTTT, and File properties search > & new WDQS visualizations. > > https://www.youtube.com/watch?v=NmfqtP3pr2Y&t=47 > > We welcome demos from Wikimedia community members and staff alike - from > polished features to something you just got working last night. Hope to see > you soon! > > If you would like to invite anyone to CREDIT, feel free to use this > template. > > *Hi <FNAME>* > > *I hope all is well with you! I wanted to let you know about CREDIT, a > monthly demo series that we’re running to showcase open source tech > projects from Wikimedia’s Community, Reading, Editing, Discovery, > Infrastructure and Technology teams. * > > *CREDIT is open to the public, and we welcome questions and discussion. > The next CREDIT will be held on December 7th at 11am PT / 2pm ET / 19:00 > UTC. * > > *There’s more info on MediaWiki > <https://www.mediawiki.org/wiki/CREDIT_showcase>, and on Etherpad > <https://etherpad.wikimedia.org/p/CREDIT>, which is where we take notes and > ask questions. You can also ask questions on IRC in the Freenode chatroom > #wikimedia-office (web-based access here > <https://webchat.freenode.net/?channels=%23wikimedia-office>). Links to > video will become available at these locations shortly before the event.* > > *Please feel free to pass this information along to any interested folks. > Our projects tend to focus on areas that might be of interest to folks > working across the open source tech community: language detection, > numerical sort, large data visualizations, maps, and all sorts of other > things.* > > *If you have any questions, please let me know! Thanks, and I hope to see > you at CREDIT.* > > > *-YOURNAME* >

3 4

Fwd: [Wikimedia-l] Statement by Wikimedia Board on Healthy Community Culture, Inclusivity, and Safe Spaces
by Pine W 09 Dec '16

09 Dec '16

This email might interest others who would like to know what next steps WMF is considering address this set of issues, in terms of policies, practices, and technical developments. Pine ---------- Forwarded message ---------- From: Patrick Earley <pearley(a)wikimedia.org> Date: Thu, Dec 8, 2016 at 12:30 PM Subject: Re: [Wikimedia-l] Statement by Wikimedia Board on Healthy Community Culture, Inclusivity, and Safe Spaces To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org> I want to thank the Board for this letter, and for their focus on this problem. What specific work should we be doing to make progress around this issue? Harassment is a complex problem, and there are no easy solutions. Nor is there likely to be a single solution; improvement will have to be made through a number of initiatives and coordinated approaches. Wikimedia volunteers have offered many different approaches to the problem, through consultations, workshops, the Inspire campaign, conference sessions, and discussion. The Support and Safety team has been collating these ideas, exploring the issue in the broader context of online communities, and delving into academic research on the topic. >From these conversations and research, we have identified some categories/areas for improvement: - Better blocking tools and detection - the Wikimedia community works hard on the front lines keeping our users safe from harassment, through monitoring noticeboards and recent changes for problems, investigating “sock” accounts used to abuse contributors, and placing blocks on problematic users. Improvements to blocking tools, and the ability to detect harassing comments sooner can empower contributors to be more effective at these tasks. - Reporting and evaluation tools - The current systems for reporting harassment are overburdened and can be unclear to users, and there are limited tools that admins and stewards can use to evaluate the cases and make good decisions. New tools, developed in collaboration with functionaries and communities, can improve the experience of reporting, investigating and managing harassment cases. - Training for better handling of both in-person and online harassment - Better training can give contributors the tools and skills to handle harassment situations quickly and empathetically, document cases, and provide good advice to targets of harassment. - Policy and enforcement - Wikimedia communities have developed a variety of processes, policies, and approaches to dealing with behavioural problems. As a movement, we need to identify which are working well, and share those successes. We also need to identify where our approaches are not working well, identify the problems, and try new solutions based on research and data. - Coordination with other platforms on harassment approaches and tools, and keeping up with current academic research - Our communities are not the only ones struggling with the problem of online harassment. We need to work more closely with other platforms, researchers, online communities, and experts to make sure we are aware of successful techniques, new research, and useful tools. The above areas are not the only areas where improvement can be made - right now, contributors are brainstorming other approaches through the Community Wishlist process.[1] We also encourage contributors to reach out to the Support and Safety team at ca(a)wikimedia.org with ideas, or contact me privately at pearley(a)wikimedia.org. [1] https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey On Thu, Dec 8, 2016 at 12:26 PM, Sydney Poore <sydney.poore(a)gmail.com> wrote: > Thank you Christophe and the rest of the Wikimedia Foundation trustees > for dedicating time and thought to this important topic. > > I'm optimistic that if we collaborate together as a community we can > make a difference in the level of harassment on Wikimedia projects and > maybe even other parts of the internet. > > Sydney > Sydney Poore > User:FloNight > > > > > > On Thu, Dec 8, 2016 at 3:18 PM, Christophe Henner <chenner(a)wikimedia.org> > wrote: > > Hello everyone, > > > > As many of you know, over the past couple of years the Wikimedia > Foundation > > has taken a focused look at community health—particularly in regards to > > harassment. The Foundation's Board has been monitoring and discussing > this > > issue over the past year with great interest. We have prepared a > statement > > offering our thoughts on this topic, and providing a clear mandate for > the > > Foundation’s leadership to fully engage on this issue. > > > > Our statement is below and has been posted on Meta-Wiki, where it is set > up > > for translation: > > https://meta.wikimedia.org/wiki/Wikimedia_Foundation_ > Board_noticeboard/November_2016_-_Statement_on_Healthy_Community_Culture,_ > Inclusivity,_and_Safe_Spaces > > > > Since the Foundation was established, we have been invested in building a > > positive community culture. As part of these efforts, we have monitored > the > > projects for instances of harassment, escalating our capacity to respond > in > > recent years. Thanks to the work of the Foundation's Support and Safety > > Team, we now have data in the form of the 2015 Harassment Survey[1] about > > the nature of the issue. This has enabled us to identify key areas of > > concern, and step up our response appropriately. This research shows that > > harassment has a negative impact on participation in our projects. This > has > > implications for our ability to collect, share, and disseminate free > > knowledge in support of the Wikimedia vision. Our statement speaks to the > > Board's duty to help the Foundation fulfill its mission. > > > > The Board is committed to making our communities safer and will not > accept > > harassment and toxic behavior on Wikimedia projects. We believe this > matter > > deserves the Foundation's attention and resources, and have confirmed > this > > responsibility at our latest Board meeting on November 13th. The > questions > > that lay before us all now are how to best address this threat, rather > than > > if we should attempt to do so. > > > > The Board especially appreciates and applauds the work being done to > > address this important issue by many community leaders across the > movement > > and teams within the Foundation. We look forward to seeing this > cooperative > > work not only continue, but expand. Finally, we encourage everyone who is > > interested in helping the Foundation address this threat to our vision > and > > mission to engage in the upcoming discussions around this issue. > > > > On behalf of the Wikimedia Foundation Board of Trustees, > > > > Christophe Henner, Board Chair > > > > María Sefidari, Board Vice Chair > > > > [1] https://meta.wikimedia.org/wiki/Research:Harassment_survey_2015 > > > > > > Statement by the Wikimedia Board on Healthy Community Culture, > Inclusivity, > > and Safe Spaces > > > > > > At our Board meeting on November 13, and in Board meetings in September > and > > June, we spent considerable time discussing the issues of harassment and > > hostility on the internet generally, and more specifically on the > Wikimedia > > projects. > > > > This is an important issue. Approximately 40% of internet users, and 70% > of > > women internet users, have personally experienced harassment.[1] Of > people > > who have reported experiencing harassment on Wikimedia projects, more > than > > 50% reported decreasing their participation in our community.[2] Based on > > this and other research, we conclude that harassment and toxic behavior > on > > the Wikimedia projects negatively impacts the ability of the Wikimedia > > projects to collect, share, and disseminate free knowledge. This behavior > > is contrary to our vision and mission. > > > > Our communities deserve safe spaces in which they can contribute > > productively and debate constructively. It is our belief that the > Wikimedia > > Foundation should be proactively engaged in eliminating harassment, > > promoting inclusivity, ensuring a healthier culture of discourse, and > > improving the safety of Wikimedia spaces. We request management to > dedicate > > appropriate resources to this end. > > > > We urge every member of the Wikimedia communities to collaborate in a way > > that models the Wikimedia values of openness and diversity, step forward > to > > do their part to stop hostile and toxic behavior, support people who have > > been targeted by such behavior, and help set clear expectations for all > > contributors. > > > > [1] 2014 Pew Research Center Study, found at: > > http://www.pewinternet.org/2014/10/22/online-harassment/ > > > > [2] 2015 WMF Harassment Survey, found at: > > https://upload.wikimedia.org/wikipedia/commons/5/52/ > Harassment_Survey_2015_-_Results_Report.pdf > > > > > > > > Christophe HENNER > > Chair of the board of trustees > > chenner(a)wikimedia.org > > +33650664739 > > > > twitter *@schiste* skype *christophe_henner* > > _______________________________________________ > > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/ > wiki/Mailing_lists/Guidelines > > New messages to: Wikimedia-l(a)lists.wikimedia.org > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe> > > _______________________________________________ > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/ > wiki/Mailing_lists/Guidelines > New messages to: Wikimedia-l(a)lists.wikimedia.org > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe> > -- Patrick Earley Senior Community Advocate Wikimedia Foundation pearley(a)wikimedia.org (1) 415 975 1874 _______________________________________________ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/ wiki/Mailing_lists/Guidelines New messages to: Wikimedia-l(a)lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>

1 0

Gerrit: login issues for some (hopefully only a few)
by Chad Horohoe 08 Dec '16

08 Dec '16

Hi, We upgraded to Gerrit 2.13.3 today from 2.12.2. However, a couple of users have reported being unable to login. Based on reports and investigation, I'm thinking/hoping this is only affecting 11 users. However, if you find yourself unable to login with the message "Cannot assign username <myname> to account <some number>; name already in use," please do chime in on Phab[0]. Thanks and have a good evening, [0] https://phabricator.wikimedia.org/T152640

1 0

2016-12-07 Scrum of Scrums meeting notes
by Grace Gellerman 07 Dec '16

07 Dec '16

https://www.mediawiki.org/wiki/Scrum_of_scrums/2016-12-07 = 2016-12-07 = == Product == === Reading === ==== iOS native app ==== * Last Week ** Shipped 5.3.1 with bug fixes ** Continued work on 5.3.2 - Dynamic text size, data layer update, performance enhancements * This week ** Finish work on 5.3.2, fix bugs from beta feedback ** Feature complete on 5.3.2 Friday 12/9 ==== Android native app ==== * Last week: ** Continuing Q2 goals for Wikidata descriptions ** New beta v2.4.182 *** Fundraising and survey cards now configurable remotely (beta) * Next week (https://phabricator.wikimedia.org/project/view/2352/): ** More Q2 goals for Wikidata descriptions (tutorial and polish) ==== Mobile Content Service (MCS) ==== * Remove obsolete mobile-summary endpoint (handled by RESTBase directly) * Moved to node template version 0.5.0, moved to ES2015 and eslint ==== Reading Web ==== * Current sprint: https://phabricator.wikimedia.org/project/view/2362/ * So far: ** ReadMore has been enabled on Japanese and Spanish wikis (mobile site) ** Wikidata Page banner has been enabled on Finnish Wikivoyage ** Wikidata page descriptions has been enabled on French and German wikipedias (mobile site) ** Lead image has been disabled from the mobile site, beta mode. * Until we meet the next time: ** Create importable test pages that can be used to test various Reading Web related changes ** Hovercards rewrite finish up ** Continue working on returning page images from the lead section only ==== Reading Infrastructure ==== * API i18n changes going out with next train: https://lists.wikimedia.org/pipermail/mediawiki-api-announce/2016-December/… ** you can use the new errorformat, errorlang, errorsuselocal paramers to get localized, parsed errors; if you don't, most API modules will behave the same as before. Exceptions: *** for query modules the error codes won't be prefixed anymore the way parameter names are; *** for a few modules (see announcement) which put errors in some non-default location in the response data, that location might change and/or the contents might change from a single error to an array of errors. * could use some advice from Performance or Language on dealing with huge JS data blobs: *https://phabricator.wikimedia.org/T32574#2836570* <https://phabricator.wikimedia.org/T32574#2836570> * MediaViewer tests failing, mw.language tests seem to be the cause: https://phabricator.wikimedia.org/T152476 === Editing === ==== Collaboration ==== * Working on new filter UI for Special:Recentchanges; a bunch of backend patches for this landed in MW core recently, more will land soon. Will be behind a hidden preference for the time being. * Converted Flow and Echo to extension.json. This has caused a few minor issues for Flow and may cause some for Echo as well. Also, if you have open patches, they'll probably conflict now. * Going to convert PageTriage next; and FlaggedRevs after we clear out the CR backlog a bit there ==== Parsing ==== * Blocked: Tim asked ops for someone to assist him with puppetizing HTML5Depurate for a pilot deployment to the production cluster for our Q2 goal. No response yet. ** See "[Ops] Need Html5Depurate playmate" mail from Tim dated 11/24 * Ongoing investigation of https://phabricator.wikimedia.org/T151702 and followups with Ops and Services * Parsoid deploy today after almost a month ( https://www.mediawiki.org/wiki/Parsoid/Deploymentswill be updated later today) ** Parsoid-native <gallery> rendering + a bunch of other changes going out today (Most interesting for MCS: heading ids now assigned that match core output). ** HTML version bump to 1.3.0; See https://www.mediawiki.org/wiki/Specs/HTML/1.3.0#Changes_since_Specs.2FHTML.… for changes since 1.2.1 * Tim is close to finishing the first version of remex-html ( https://github.com/tstarling/remex-html ) -- a HTML5 parser in PHP === Discovery === * No blockers * Started discussion on how to combine various models of user query enhancements/transformations to improve search results: https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/So_Many_Search_Optio… * Continuing work on crosswiki searches, load test successful * Published analysis of WDQS traffic to detect parallel connections: https://phabricator.wikimedia.org/T149963 * WDQS now limits parallel connections to 5 per IP. Working fine so far. == Technology == === Analytics === * Blocker -- None * Ongoing ** Wikistats 2.0 UI has kicked off with new contractor designer. ** RecentChanges via EventBus is on its way, we will soon have events flowing in Kafka. Purpose is later to turn off Redis based producer. ** Mediawiki history reconstruction is at final review stage (will be long, heavy code) -- Plans to communicate early next quarter ** Old logs on stat1002 have been *deleted*. More at https://phabricator.wikimedia.org/T84618. Now working on removing some old generation processes in the cluster. ** Cross team collaboration in migrating limn editor-engagement dashboards to dashiki === Release Engineering === * '''Blocking''': ** None? * '''Blocked''' ** None * '''Updates''' ** Reminder that deployments are weird between now and the New Year: https://lists.wikimedia.org/pipermail/wikitech-l/2016-November/086936.html ** Gerrit is updating, pretty much right now === Security === * Security Reviews ** Recommendations API continues from last week * Continuing work on CSRF protection for anonymous users ( https://phabricator.wikimedia.org/T40417) * Question for Parsing: Can we limit the amount of nesting in lists? ** https://phabricator.wikimedia.org/T151834 * Question for Reading: Should page requests containing invalid characters in title still result in 200 OK if curid is valid? ** https://phabricator.wikimedia.org/T144100 === Services === * Blockers: none * Updates: ** PDF render service and API endpoint deployed and completely operational: *** https://en.wikipedia.org/api/rest_v1/#!/Page_content/get_page_pdf_title ** Working on followups for the API cluster outage *** https://phabricator.wikimedia.org/T152074 === Technical Operations === * '''Blocked''': ** Community Tech *** https://phabricator.wikimedia.org/T152080 page_assessments creating duplicate key errors * '''Blocking''': ** None * Updates: ** Still working on API cluster failure. https://phabricator.wikimedia.org/T151702 ** new labsdbs are almost ready to start being used ** AB testing design still under discussion https://phabricator.wikimedia.org/T143694 ** Goals for next quarter being drafted, if you have any dependencies on Ops contact us == Wikidata == * I still can not join the Hangout when not being a WMF employee. I know multiple people already looked into this. Please forgive me when I'm not trying any more. I still find the information given in this Etherpad very helpful, and love sharing relevant bits via a WMDE mailing list. ** Grace to look into this ^ * Blocked on security reviews of: ** Cognate extension: https://phabricator.wikimedia.org/T149082 ** InterwikiSorting Extension: https://phabricator.wikimedia.org/T149083 == Fundraising Tech == * Investigating banner impression drop from 08:00-09:00 UTC on 12/1 and 12/2: https://phabricator.wikimedia.org/T152122 * Fixing CiviCRM reports & internal dashboard * Tweaking mailing list export * Planning for next year ** Estimating effort for next year's required payment processor integrations ** Potential extra-curricular work supporting ORES: https://www.mediawiki.org/wiki/User:Adamw/Study_abroad_proposal

1 0

Google Code-in 2016 achievements
by Andre Klapper 07 Dec '16

07 Dec '16

Google Code-in (GCI) has been running for 8 days and students have already resolved more than 50 tasks! Some highlights: * Several extension pages on mediawiki.org display screenshots (AbuseFilter, InputBox, Cite, MobileFrontend, …) * Kiwix ZIM files can now be opened from the Android file manager * Pywikibot received additional tests * The celery logging of the ORES service does not include TimeoutErrors * WikiEduDashboard does not allow to create programs with url-encoded spaces in the title * Wikidata has a special page to list all available badges * MediaWiki's Newsletter extension received numerous code fixes * All deprecated Linker::link() usage got replaced in MediaWiki core * html-metadata received support for Twitter cards metadata * Numerous MediaWiki extensions specify extension dependencies in their maintenance scripts * Translatable messages in several projects show $1 as an insertable * Huggle got support for Ukrainian and Russian language added * ConfirmEdit's system messages aren't CAPTCHA module specific anymore * action=checktoken in MediaWiki's API warns if the token ends in " \" * The MobileFrontend hooks documentation got updated * The PageImages API offers a "Help" link * VisualEditor's user guide has a new section about musical scores * …and many more. Congratulations to all our students and thanks to all our mentors! You also have an idea for a task you'd like to mentor? Read https://www.mediawiki.org/wiki/Google_Code-in_2016 Please contact us if you need help or have questions! Thanks, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/

2 1

Page images API Incident report 12/01/2016
by Olga Vasileva 05 Dec '16

05 Dec '16

Hello everyone, Last Thursday, a change went live affecting the page images API, which cased images that previously were appearing in many Wikimedia projects including the Wikipedia apps, the Wikimedia portal and mobile web search results to disappear for about 3 hours. The full incident report can be found here <https://wikitech.wikimedia.org/wiki/Incident_documentation/20161202-2016120…>, the original bug report, here <https://phabricator.wikimedia.org/T152155>. This issue was temporarily fixed by allowing projects to display both free and non-free images by default for the short term. This will be reverted once a maintenance script creating the new list of images completes running, which should take a couple of weeks. After this, the default will change back to displaying free images only. We will send an update again once this is deployed. Thanks and sorry for the inconvenience and chaos! - Olga -- Olga Vasileva // Product Manager // Reading Web Team https://wikimediafoundation.org/

1 0

Google Code-in 2016 just started and we need your help!
by Andre Klapper 03 Dec '16

03 Dec '16

Google Code-in 2016 just started: https://www.mediawiki.org/wiki/Google_Code-in_2016 In the next seven weeks, many young people are going to make their first contributions to Wikimedia. Expect many questions on IRC and mailing lists by onboarding newcomers who have never used IRC or lists before. Your help and patience is welcome to provide a helping hand! Thanks to all mentors who have already registered & provided tasks! You have not become a mentor yet? Please do consider it. It is fun and we do need more tasks! :) * Think of easy tasks in your area that you could mentor. Areas are: Code, docs/training, outreach/research, quality assurance, and user interface. "Easy" means 2-3h to complete for you, or less technical ~30min "beginner tasks" for onboarding). * OR: provide an easy 'clonable' task (a task that is generic and could be repeated many times by different students). * Note that you commit to answer to students' questions and to evaluate their work within 36 hours (but the better your task description the less questions. No worries, we're here to help!) For the full info, please check out https://www.mediawiki.org/wiki/Google_Code-in_2016/Mentors and ask if something is unclear! Thank you again for giving young contributors the opportunity to learn about and work on all aspects of Free & Open Source Software projects! Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/

3 2

Re: [Wikitech-l] [Xmldatadumps-l] Wikipedia page IDs
by John 03 Dec '16

03 Dec '16

It looks like the page was deleted/restored thus giving it a new page ID. Originally when pages where deleted the page_id was not kept, which caused a new page_id to be issued when it was restored. This phenomenon has since been fixed, and should no longer happen. On Sat, Dec 3, 2016 at 8:47 AM, Renato Stoffalette Joao <joao(a)l3s.de> wrote: > Hi all. > > Firstly, apologies for eventual duplicates or posting the question in the > wrong mailing list. > > Secondly, could anybody kindly explain to me if some Wikipedia pages > changed their IDs from the past ? Or if so point to me where this might be > documented ? > I have Wikipedia pages-articles XML dumps from the years 2006 and 2008 > and when I was parsing those dumps I ran across some situations > such as the following one. In the dumps from 2006 and 2008 I found that > the South Africa page has the ID 68854, while in the most current Wikipedia > pages-articles XML dump (i.e. 2016) the same article has the ID 17416221. > I am trying to match some Wiki pages by IDs across time, but the example > above is not helping. > > Much appreciated in advance for any help. > > -- > Renato Stoffalette Joao > - PhD Student - > L3S Research Center / Leibniz Uni. > 15th Floor, Room:1519 > Appelstraße 9a > 30167 Hannover, Germany > +49.511.762-17759 > > > _______________________________________________ > Xmldatadumps-l mailing list > Xmldatadumps-l(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/xmldatadumps-l >

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l December 2016