Wikitech-l July 2013

wikitech-l@lists.wikimedia.org

158 participants
166 discussions

Re: [Wikitech-l] Wikitech-l Digest, Vol 120, Issue 53
by Edmund 20 Jul '13

20 Jul '13

unsubscribe me On 19 July 2013 19:10, <wikitech-l-request(a)lists.wikimedia.org> wrote: > Send Wikitech-l mailing list submissions to > wikitech-l(a)lists.wikimedia.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > or, via email, send a message with subject or body 'help' to > wikitech-l-request(a)lists.wikimedia.org > > You can reach the person managing the list at > wikitech-l-owner(a)lists.wikimedia.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Wikitech-l digest..." > > > Today's Topics: > > 1. Re: Australia (was Re: conferences, Hacker School, Code for > America) (Quim Gil) > 2. Bugzilla: Tips and Best Practices (Andre Klapper) > 3. Re: Australia (was Re: conferences, Hacker School, Code for > America) (Luis Villa) > 4. Re: Request for Comments: New Search (Nikolas Everett) > 5. CSS: Make hlist class part of MediaWiki core (Jon Robson) > 6. Re: Australia (was Re: conferences, Hacker School, Code for > America) (Roan Kattouw) > 7. Re: CSS: Make hlist class part of MediaWiki core (MZMcBride) > 8. Re: CSS: Make hlist class part of MediaWiki core (Jon Robson) > 9. Git config trick. (Ori Livneh) > 10. MediaWiki extensions as core-like libraries: MediaWiki's fun > new landmine for admins (Ryan Lane) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 19 Jul 2013 14:54:07 +0200 > From: Quim Gil <qgil(a)wikimedia.org> > To: wikitech-l(a)lists.wikimedia.org > Subject: Re: [Wikitech-l] Australia (was Re: conferences, Hacker > School, Code for America) > Message-ID: <51E936EF.9070104(a)wikimedia.org> > Content-Type: text/plain; charset=UTF-8; format=flowed > > On 07/06/2013 04:30 PM, Quim Gil wrote: > > On 07/03/2013 09:22 AM, Sumana Harihareswara wrote: > >> The linux.conf.au call for talks closes July 6th, *Australian time*. > >> http://linux.conf.au/media/news/1 > > > > CFP Extension Announced linux.conf.au 2014 - linux.conf.au !!! > > Now it's July 20. > > http://linux.conf.au/media/news/27 > > ... and this is tomorrow. > > > > I also think that linux.conf.au could be a good chance to spread our > > word in Australia. You are encouraged to apply. > > I just did. :) > > >> If you submit a good talk that doesn't > >> get accepted, you may win a free ticket to attend LCA. > >> http://linux.conf.au/media/news/26 "This year, the papers committee is > >> going to be focused on Linux on the frontier and deep technical > >> content-- that might range from cybernetics and mobile operating > >> environments to large astronomy projects and big data projects." LCA is > >> 6-10 Jan 2014 in Perth, Australia. If you get a talk accepted, you > >> could get a travel subsidy: > >> https://meta.wikimedia.org/wiki/Participation:Support > > > -- > Quim Gil > Technical Contributor Coordinator @ Wikimedia Foundation > http://www.mediawiki.org/wiki/User:Qgil > > > > ------------------------------ > > Message: 2 > Date: Fri, 19 Jul 2013 16:17:52 +0200 > From: Andre Klapper <aklapper(a)wikimedia.org> > To: wikitech-l(a)lists.wikimedia.org > Subject: [Wikitech-l] Bugzilla: Tips and Best Practices > Message-ID: <1374243472.2060.25.camel@localhost> > Content-Type: text/plain; charset="UTF-8" > > This is a reminder that I've been regularly blogging about small & not > so easy to discover functionality in Wikimedia's bugtracker located at > https://bugzilla.wikimedia.org . > > Today's blogpost is about creating reports and tables in Bugzilla to get > a better overview of the bug reports that you are interested in. > The last episodes cover saving and sharing your Bugzilla searches with > others (e.g. your development team), and how to search for empty fields. > > You can find the blogposts on > http://blogs.gnome.org/aklapper/category/computer/bugzilla/ > > The full list of topics is at the bottom of > > https://www.mediawiki.org/wiki/Bug_management#Tricks_and_best_practices_in_… > > If you want to see a specific topic covered, or always wanted to know > how to do X in Bugzilla: Tell me, or add it to > https://www.mediawiki.org/wiki/Bug_management/Task_list ! > > Cheers, > andre > -- > Andre Klapper | Wikimedia Bugwrangler > http://blogs.gnome.org/aklapper/ > > > > > ------------------------------ > > Message: 3 > Date: Fri, 19 Jul 2013 08:35:47 -0700 > From: Luis Villa <lvilla(a)wikimedia.org> > To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> > Subject: Re: [Wikitech-l] Australia (was Re: conferences, Hacker > School, Code for America) > Message-ID: > < > CAM2wSz58wdZL_PBgedEEA4UNy4ojnPgAOJfs0Vn5CVE_i_v_uw(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On Sat, Jul 6, 2013 at 11:45 PM, Roan Kattouw <roan.kattouw(a)gmail.com > >wrote: > > > > > > I went to (and presented at) linux.conf.au in 2012, and I had an > > awesome time. The quality of the talks and the number of high-quality > > talks is amazing. I highly recommend it. > > > Historically they also treat speakers *really* well. The year I spoke I got > a hot air balloon ride. ;) > > Luis > > > -- > Luis Villa > Deputy General Counsel > Wikimedia Foundation > 415.839.6885 ext. 6810 > > NOTICE: *This message may be confidential or legally privileged. If you > have received it by accident, please delete it and let us know about the > mistake. As an attorney for the Wikimedia Foundation, for legal/ethical > reasons I cannot give legal advice to, or serve as a lawyer for, community > members, volunteers, or staff members in their personal capacity.* > > > ------------------------------ > > Message: 4 > Date: Fri, 19 Jul 2013 12:38:57 -0400 > From: Nikolas Everett <neverett(a)wikimedia.org> > To: engineering(a)lists.wikimedia.org, Wikimedia developers > <wikitech-l(a)lists.wikimedia.org> > Subject: Re: [Wikitech-l] Request for Comments: New Search > Message-ID: > < > CAP+xBbV6GPGB6LsOP3b72VxjaksnQt6-L+8XEc4ZvZJwDVyUrA(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Everyone, > > I'm reviving this old thread to update everyone on the status of the RFC: > > We've continued working on implementation and everything seems to be > proceeding smoothly. We evaluated Elasticsearch and were super impressed > and decided it was very likely to be worth switching from Solr4 to it. The > evaluation and the switch did cost some time but in my opinion doing it was > time well spent. > > Thanks so much for your comments a month ago when I first posted this. If > you are interested please give the page another look. Just to be helpful, > here is a link to what I changed: > > http://www.mediawiki.org/w/index.php?title=Requests_for_comment%2FCirrusSea… > > Nik Everett > > On Fri, Jun 14, 2013 at 4:21 PM, Nikolas Everett <neverett(a)wikimedia.org > >wrote: > > > So Chad and I feel like we've gotten far enough in our prototype of our > > new search backend for MediaWiki that we're ready to request comments. > So > > here is our format RFC: > > https://www.mediawiki.org/wiki/Requests_for_comment/CirrusSearch > > > > You'll note that the plugin is called CirrusSearch. SolrSearch seems to > > have been taken by an unrelated project so we had to pick a different > name. > > > > Please read and comment in whatever way is normal for these things. > > > > Thanks so much for your attention, > > > > Nik Everett > > > > > ------------------------------ > > Message: 5 > Date: Fri, 19 Jul 2013 09:47:11 -0700 > From: Jon Robson <jdlrobson(a)gmail.com> > To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> > Subject: [Wikitech-l] CSS: Make hlist class part of MediaWiki core > Message-ID: > <CALMndh=S=CUSNb_yRar8EsB= > Ff5bVkP0HKK0ec4W7CUiCHgTbg(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > One of the things mobile did early on in its lifetime was turn off all > modules by default to give modules the opportunity to sort out their > JavaScript/design (mostly the latter) to be mobile optimised and turn > themselves on. > > The result of this is various pages are badly styled on mobile as their > styles never show up on mobile. > > A common pattern I'm noticing /a lot/ is there are lots of lists which are > clearly meant to be horizontal lists that are not horizontal lists. > > This suggests to me that we have a heap of code debt where there are lots > and lots of rules that do the same - make a list horizontal. > > I'd like to propose that we make the .hlist class a part of core and go > through our extensions using it instead of custom rules where appropriate. > > Note that said I know that .hlist has more meaning in various projects - it > also introduces additional styling changes such as dots between lists in > certain contexts. That said I think we should be striving to reuse as much > as possible - and this to me suggests that the community (both wiki and > developer) needs to work together to get our css much more organised and > reusable. > > Thoughts? > > > ------------------------------ > > Message: 6 > Date: Fri, 19 Jul 2013 10:10:16 -0700 > From: Roan Kattouw <roan.kattouw(a)gmail.com> > To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> > Subject: Re: [Wikitech-l] Australia (was Re: conferences, Hacker > School, Code for America) > Message-ID: > <CALoQHwHfJ= > UQbhAYJxSR5VB5wMsGDTTg-GR87yczH6sE3qFKxw(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On Fri, Jul 19, 2013 at 5:54 AM, Quim Gil <qgil(a)wikimedia.org> wrote: > >> CFP Extension Announced linux.conf.au 2014 - linux.conf.au !!! > >> Now it's July 20. > >> http://linux.conf.au/media/news/27 > > > > > > ... and this is tomorrow. > > > Beware that because of Australia's far-east timezone, it's already > tomorrow there :) > > Roan > > > > ------------------------------ > > Message: 7 > Date: Fri, 19 Jul 2013 13:34:41 -0400 > From: MZMcBride <z(a)mzmcbride.com> > To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> > Subject: Re: [Wikitech-l] CSS: Make hlist class part of MediaWiki core > Message-ID: <CE0EEFB3.1D13D%z(a)mzmcbride.com> > Content-Type: text/plain; charset="UTF-8" > > Jon Robson wrote: > >Note that said I know that .hlist has more meaning in various projects - > >it also introduces additional styling changes such as dots between lists > >in certain contexts. That said I think we should be striving to reuse as > >much as possible - and this to me suggests that the community (both wiki > >and developer) needs to work together to get our css much more organised > >and reusable. > > > >Thoughts? > > Adding the "hlist" class to MediaWiki core seems reasonable to me. The > "wikitable" class had a similar migration path (copied to dozens and > dozens of wikis before finally being integrated into [the] core). > > I'd suggest filing a bug in Bugzilla to track this feature request. We may > want to consider whether to make the separator (if any) more easily > customizable on a per-wiki basis, if possible. > > MZMcBride > > > > > > ------------------------------ > > Message: 8 > Date: Fri, 19 Jul 2013 10:37:31 -0700 > From: Jon Robson <jdlrobson(a)gmail.com> > To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> > Subject: Re: [Wikitech-l] CSS: Make hlist class part of MediaWiki core > Message-ID: > < > CALMndhkYNeAhhgFWyK5HEQq__w3xFrmybcTxUd7HWJSWfmg-6w(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Done: https://bugzilla.wikimedia.org/show_bug.cgi?id=51692 > Just also noticed LiquidThreads would look a lot nicer on mobile if it made > use of it! :) > > > On Fri, Jul 19, 2013 at 9:47 AM, Jon Robson <jdlrobson(a)gmail.com> wrote: > > > One of the things mobile did early on in its lifetime was turn off all > > modules by default to give modules the opportunity to sort out their > > JavaScript/design (mostly the latter) to be mobile optimised and turn > > themselves on. > > > > The result of this is various pages are badly styled on mobile as their > > styles never show up on mobile. > > > > A common pattern I'm noticing /a lot/ is there are lots of lists which > are > > clearly meant to be horizontal lists that are not horizontal lists. > > > > This suggests to me that we have a heap of code debt where there are lots > > and lots of rules that do the same - make a list horizontal. > > > > I'd like to propose that we make the .hlist class a part of core and go > > through our extensions using it instead of custom rules where > appropriate. > > > > Note that said I know that .hlist has more meaning in various projects - > > it also introduces additional styling changes such as dots between lists > in > > certain contexts. That said I think we should be striving to reuse as > much > > as possible - and this to me suggests that the community (both wiki and > > developer) needs to work together to get our css much more organised and > > reusable. > > > > Thoughts? > > > > > > > -- > Jon Robson > http://jonrobson.me.uk > @rakugojon > > > ------------------------------ > > Message: 9 > Date: Fri, 19 Jul 2013 10:40:33 -0700 > From: Ori Livneh <ori(a)wikimedia.org> > To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> > Subject: [Wikitech-l] Git config trick. > Message-ID: > < > CAHXK4BwcWs6mJD2KeCd55bg9dFz0P9PcbuZxoAN2e-393EaAHg(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > In ~/.gitconfig, add: > > [url "ssh://your_username@gerrit.wikimedia.org:29418/mediawiki/extensions/ > "] > insteadOf = "ext:" > > Now you can: > > git clone ext:UploadWizard > > ! > > --- > Ori Livneh > ori(a)wikimedia.org > > > ------------------------------ > > Message: 10 > Date: Fri, 19 Jul 2013 11:10:27 -0700 > From: Ryan Lane <rlane32(a)gmail.com> > To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> > Subject: [Wikitech-l] MediaWiki extensions as core-like libraries: > MediaWiki's fun new landmine for admins > Message-ID: > < > CALKgCA0jqVuKPLa1V3FWzY_NO9XnZ470uayppYSyn73ELkM7mQ(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > I attempted to install Wikibase the other day and made a fun discovery. > Installing it properly requires the following (12) extensions: > > WikibaseClient > Wikibase DataModel > WikibaseLib > Wikibase Repository > DataValues > DataTypes > ValueParsers > ValueView > ValueValidators > ValueFormatters > Diff > Scribunto > > And the following optional (2) extensions: > > Universal Language Selector > Babel > > Soon it will also require at least the following (4) extensions: > > Ask > Wikibase Query > Wikibase Database > Wikibase QueryEngine > > To fully deploy wikibase in a way that will work like wikidata, it will > take at least 18 extensions, all of which are versioned differently, and > are broken out in this manner to be used as libraries. > > What this is subtly doing is adding another dependency chain into > MediaWiki: extension libraries. Since these extensions are meant to be used > as libraries, other extensions will eventually do so and admins will have > to worry about not only extension compatibility with MediaWiki (an already > nearly impossible task), but will also need to worry about extension > dependency with extension libraries. The compatibility matrix for this is > going to be terrible and exacerbates one of MediaWiki's biggest problems > for admins. > > Quite a few of these should be core functionality or if they can't properly > pass review they should be removed. For legitimate library-like extensions > I have no constructive alternative, but there must be some sane alternative > to this. > > - Ryan > > > ------------------------------ > > _______________________________________________ > Wikitech-l mailing list > Wikitech-l(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > > > End of Wikitech-l Digest, Vol 120, Issue 53 > ******************************************* >

1 0

CSS: Make hlist class part of MediaWiki core
by Jon Robson 19 Jul '13

19 Jul '13

One of the things mobile did early on in its lifetime was turn off all modules by default to give modules the opportunity to sort out their JavaScript/design (mostly the latter) to be mobile optimised and turn themselves on. The result of this is various pages are badly styled on mobile as their styles never show up on mobile. A common pattern I'm noticing /a lot/ is there are lots of lists which are clearly meant to be horizontal lists that are not horizontal lists. This suggests to me that we have a heap of code debt where there are lots and lots of rules that do the same - make a list horizontal. I'd like to propose that we make the .hlist class a part of core and go through our extensions using it instead of custom rules where appropriate. Note that said I know that .hlist has more meaning in various projects - it also introduces additional styling changes such as dots between lists in certain contexts. That said I think we should be striving to reuse as much as possible - and this to me suggests that the community (both wiki and developer) needs to work together to get our css much more organised and reusable. Thoughts?

2 2

conferences, Hacker School, Code for America
by Sumana Harihareswara 19 Jul '13

19 Jul '13

Bundling together some notices. Conferences: The linux.conf.au call for talks closes July 6th, *Australian time*. http://linux.conf.au/media/news/1 If you submit a good talk that doesn't get accepted, you may win a free ticket to attend LCA. http://linux.conf.au/media/news/26 "This year, the papers committee is going to be focused on Linux on the frontier and deep technical content-- that might range from cybernetics and mobile operating environments to large astronomy projects and big data projects." LCA is 6-10 Jan 2014 in Perth, Australia. If you get a talk accepted, you could get a travel subsidy: https://meta.wikimedia.org/wiki/Participation:Support If you're coming to Wikimania in Hong Kong next month, and you're coming to the DevCamp August 7-8, please list yourself at https://wikimania2013.wikimedia.org/wiki/DevCamp and add to https://wikimania2013.wikimedia.org/wiki/DevCamp/Brainstorming . August 14-16 in Washington, DC is the USENIX Security Symposium which "brings together researchers, practitioners, system administrators, system programmers, and others interested in the latest advances in the security of computer systems and networks." https://www.usenix.org/conference/usenixsecurity13 July 15th is the deadline for students to apply for a grant to pay for travel, accommodations, and registration fees: https://www.usenix.org/conference/usenixsecurity13/students Circumvention Tech Summit IV will be September 29-October 1 in Berlin. http://www.openitp.org/openitp/circumvention-tech-summit.html "CTS events are designed to increase dialog and cooperation between privacy tool developers, community activists, journalists and other stakeholders interested in improving the tools and training available for circumventing internet censorship and surveillance." The deadline to submit an application is August 15. Travel grants are available if you apply by August 4th. Hacker School: "Hacker School is a three-month, full-time school in New York for becoming a better programmer. We're free as in beer, and provide space, a little structure, time to focus, and a friendly community of smart builders dedicated to self-improvement. "We value free software, beautiful code, personal growth, and shipping. Applications are now open for our fall 2013 batch, which begins September 30." https://www.hackerschool.com/faq has more. Apply by August 1st to be guaranteed a decision by August 30th. Code for America: "If you’re a developer, designer, researcher, data enthusiast, urban planner, or entrepreneur who wants to make a difference, this is your opportunity." CfA is an 11-month paid program that provides mentorship, training, and more. http://codeforamerica.org/fellows/apply/ has more. Deadline: July 31st. -- Sumana Harihareswara Engineering Community Manager Wikimedia Foundation

4 5

Bugzilla: Tips and Best Practices
by Andre Klapper 19 Jul '13

19 Jul '13

This is a reminder that I've been regularly blogging about small & not so easy to discover functionality in Wikimedia's bugtracker located at https://bugzilla.wikimedia.org . Today's blogpost is about creating reports and tables in Bugzilla to get a better overview of the bug reports that you are interested in. The last episodes cover saving and sharing your Bugzilla searches with others (e.g. your development team), and how to search for empty fields. You can find the blogposts on http://blogs.gnome.org/aklapper/category/computer/bugzilla/ The full list of topics is at the bottom of https://www.mediawiki.org/wiki/Bug_management#Tricks_and_best_practices_in_… If you want to see a specific topic covered, or always wanted to know how to do X in Bugzilla: Tell me, or add it to https://www.mediawiki.org/wiki/Bug_management/Task_list ! Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/

1 0

Why isn't hotcat an extension?
by Yuvi Panda 19 Jul '13

19 Jul '13

It's universally liked, is there almost on every wiki, and provides a much needed functionality. Why isn't this deployed as an extension, or better yet - part of core, than as a gadget? Just a matter of someone to do the work? -- Yuvi Panda T http://yuvi.in/blog

17 37

RFC: Scoping site CSS
by Juliusz Gonera 19 Jul '13

19 Jul '13

I wrote an RFC about scoping Common.css and Mobile.css: https://www.mediawiki.org/wiki/Requests_for_comment/Scoping_site_CSS In short: this could help us separate CSS rules added by administrators from the core UI rules of MediaWiki. What we would get: * UI (chrome) CSS more predictable and broken less often * no crazy UI styling as seen at https://nv.wikipedia.org Please share your thoughts. -- Juliusz

8 8

Status of MediaWiki Release Management RFP
by MZMcBride 18 Jul '13

18 Jul '13

Hi. Is there a status update regarding the MediaWiki Release Management RFP? <https://www.mediawiki.org/wiki/Release_Management_RFP#Timeline> indicates that the goal for an announcement was the second week of July. Apologies in advance if I've simply overlooked an update (I briefly checked my mail archives, but could only find a reference to July 8). MZMcBride

2 1

Bugzilla administrator rights policy
by Andre Klapper 18 Jul '13

18 Jul '13

Better late than never: Recently, I've worked on a document to describe when it is necessary for a user to have administrator rights in bugzilla.wikimedia.org. It affects a small number of Bugzilla users (less than 30) who were contacted via email while drafting the policy. The policy can be found at https://wikimediafoundation.org/wiki/Bugzilla_administrator_rights_policy It was written in order to explain why a specific user needs to be an administrator (or why it might not be needed). Following the principle of least privilege, Bugzilla administrator rights are only required for a small number of rather uncommon tasks, with the one exception being editing Bugzilla user rights (if you want to know more: these tasks are also listed in the policy). A combination of other, more specific Bugzilla rights very often allows executing the same tasks, so nobody will lose any ability to perform tasks in Bugzilla that s/he could also perform before. As usual, a list of current Bugzilla administrators can be found at https://meta.wikimedia.org/wiki/System_administrators#List I'm happy to answer any questions that may arise (and that were not already answered in http://lists.wikimedia.org/pipermail/wikitech-l/2013-June/070062.html ). Thanks, andre -- Andre Klapper | ak-47(a)gmx.net http://blogs.gnome.org/aklapper/

1 0

Gerrit downtime - Thursday, July 18th
by Chad 18 Jul '13

18 Jul '13

Hi everyone, So, we've got a bad disk on the Gerrit box that needs to be swapped out. This is going to cause a little bit of downtime while we fix things up. Therefore, Gerrit will be unavailable on Thursday, July 18th (that's 2 days from now) starting at 14:00 UTC (10am EST, 7am PST) and going for 1 hour (until 15:00 UTC). Hopefully it won't take the full hour, but I'd like to be cautious :) If you have any questions, please feel free to ask them here or e-mail me privately. Thanks for your understanding! -Chad

1 1

Re: [Wikitech-l] Suggestion for solving the disambiguation problem
by Lee Worden 18 Jul '13

18 Jul '13

Maybe it could be done with just the Referer field on the second request, without needing to log two different page requests and correlate them. > Date: Tue, 16 Jul 2013 14:14:42 -0400 > From: David Cuenca<dacuetu(a)gmail.com> > > Good idea, it could also help to know which are the links more used in a > disambiguation page to sort them by importance. > > Micru > > On Tue, Jul 16, 2013 at 2:03 PM, Nicolas Vervelle<nvervelle(a)gmail.com>wrote: > >> >Interesting idea... >> > >> > >> >On Mon, Jul 15, 2013 at 11:41 PM, Jon Robson<jdlrobson(a)gmail.com> wrote: >> > >>> > >I understand there is an issue that needs solving where various pages >>> > >link to disambiguation pages. These need fixing to point at the >>> > >appropriate thing. >>> > > >>> > >I had a thought on how this might be done using a variant of >>> > >EventLogging... >>> > > >>> > >When a user clicks on a link that is a disambiguation page and then >>> > >clicks on a link on that page we log an event that contains >>> > > >>> > >* page user was on before >>> > >* page user is on now >>> > > >>> > >If we were to collect this data it would allow us to statistically >>> > >suggest what the correct disambiguation page might be. >>> > > >>> > >To take a more concrete theoretical example: >>> > >* If I am on the Wiki page for William Blake and click on London I am >>> > >taken tohttps://en.wikipedia.org/wiki/London_(disambiguation) >>> > >* I look through and see London (poem) and click on it >>> > >* An event is fired that links London (poem) to William Blake. >>> > > >>> > >Obviously this won't always be accurate but I'd expect generally this >>> > >would work (obviously we'd need to filter out bots) >>> > > >>> > >Then when editing William Blake say that disambiguation links are >>> > >surfaced. If I go to fix one it might prompt me that 80% of visitors >>> > >go from William Blake to London (poem). >>> > > >>> > > >>> > >Have we done anything like this in the past? (Collecting data from >>> > >readers and informing editors) >>> > > >>> > >I can imagine applying this sort of pattern could have various other >>> > >uses... >>> > > >>> > > >>> > > >>> > > >>> > >-- >>> > >Jon Robson >>> > >http://jonrobson.me.uk >>> > >@rakugojon >>> > >

6 11

← Newer
1
...
7
8
9
10
11
12
13
...
17
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l July 2013