Wikitech-l July 2013

wikitech-l@lists.wikimedia.org

158 participants
166 discussions

Start a nNew thread

Varnish
by Jacobo Nájera 31 Jul '13

31 Jul '13

I am exploring around Varnish Cache, do you know some tools for test performance and benchmarking? Thanks, Jacobo

3 3

"You have new messages" glitch?
by scs＠eskimo.com 31 Jul '13

31 Jul '13

Today I'm noticing that if I visit someone else's user or talk page (this is on en.wp), I see a little orange box saying "Talk: you have new messages" even though I don't. Presumably that user does, or something.

2 1

Voting disabled in bugzilla for some products
by John Vandenberg 30 Jul '13

30 Jul '13

I may be mistaken, but I thought voting was enabled for the product VisualEditor, and now it is not. Could someone confirm this? It is currently disabled for: Commons App Huggle openZIM Parsoid (Spam) Tool Labs tools VisualEditor Wiki Loves Monuments WikiLoves Monuments Mobile Wikimedia Labs Wikipedia App Voting provides a way to watch a bug without sending any bugmail. It also lets people do a +1 without adding a comment. Is the reason for disabling voting because of perception that large numbers of votes magically creates new developers? If so, would it be re-enabled if the voting interface was relabelled and better documented. i.e. https://bugzilla.wikimedia.org/show_bug.cgi?id=34490 -- John Vandenberg

11 13

Re: [Wikitech-l] [Wiktionary-l] Listing missing words of wiktionnaries
by Mathieu Stumpf 30 Jul '13

30 Jul '13

Le 2013-07-26 20:26, Amgine a écrit : > The request is to create a web-based text corpus[1] from which to > derive > frequencies and then compare with existing wiktionaries. Not a light > undertaking, but one which has been proposed and implemented > previously > (e.g. Connel's Gutenberg project[2]) > > Generically speaking, someone would need to determine the appropriate > size of the corpus sample, it's temporal currency, and the method of > creating and maintaining it. This isn't easy to do, and having no > strictures results in unwieldy and mostly irrelevant products like > Google's n-grams[3] (on the other hand, if someone can figure out how > to > filter n-grams usefully it would mean we don't have to build our > own.) Actually, I think it would be interesting to have a trend history of words usage over centuries (current trend would also be interesting but probably harder to implement). Wikisource may be used in order to achieve that. > > Amgine > > [1] https://en.wikipedia.org/wiki/Linguistic_corpus > [2] https://en.wiktionary.org/wiki/User:Connel_MacKenzie/Gutenberg > [3] http://storage.googleapis.com/books/ngrams/books/datasetsv2.html > > > On 26/07/13 09:18, Lars Aronsson wrote: >> On 07/23/2013 11:23 AM, Mathieu Stumpf wrote: >>> Here is what I would like to do : generating reports which give, >>> for >>> a given language, a list of words which are used on the web with a >>> number evaluating its occurencies, but which are not in a given >>> wiktionary. >>> >>> How would you recommand to implemente that within the wikimedia >>> infrastructure? >> >> Some years back, I undertook to add entries for >> Swedish words in the English Wiktionary. You can >> follow my diary at http://en.wiktionary.org/wiki/User:LA2 >> >> Among the things I did was to extract a list of all >> Swedish words that already had entries. The best >> way was to use CatScan to list entries in categories >> for Swedish words. Even if there is a page called >> "men", this doesn't mean the Swedish word "men" >> has an entry, because it could be the English word >> "men" that is in that page. >> >> Then I extracted all words from some known texts, >> e.g. novels, the Bible, government reports, and the >> Swedish Wikipedia, counting the number of >> occurrencies of each word. Case significance is >> a bit tricky. There should not be an entry for >> lower-case stockholm, so you can't just convert >> everything to lower case. But if a sentence begins >> with a capital letter, that word should not have >> a capitalized entry. Another tricky issue is >> abbreviations, which should keep the period, >> for example "i.e." rather than "i" and "e". But >> the period that ends a sentence should be removed. >> When splitting a text into words, I decided to keep >> all periods and initial capital letters, even if this >> leads to some false words. >> >> When you have word frequency statistics for a text, >> and a list of existing entries from Wiktionary, you >> can compute the coverage, and I wrote a little >> script for this. I found that English Wiktionary already >> had Swedish entries covering 72% of the words in the >> Bible, and when I started to add entries for the most >> common of the missing words, I was able to increase >> this to 87% in just a single month (September 2010). >> >> Many of the common words that were missing when >> I started were adverbs such as "thereof", "herein", >> which occur frequently in any text but are not very >> exciting to write entries about. This statistics-based >> approach gave me a reason to add those entries. >> >> It is interesting to contrast a given text to a given >> dictionary in this way. The Swedish entries in the >> English Wiktionary is a different dictionary than the >> Swedish entries in the German or Danish Wiktionary. >> The kinds of words found in the Bible are different >> from those found in Wikipedia or in legal texts. >> There is not a single, universal text corpus that we >> can aim to cover. Google has released its ngram >> dataset. I'm not sure if it covers Swedish, but even >> if it does, it must differ from the corpus frequencies >> published by the Swedish Academy. >> >> It is relatively easy to extract a list of existing entries >> from Wiktionary. But to prepare a given text corpus >> for frequency and coverage analysis needs more >> preparation. > > > _______________________________________________ > Wiktionary-l mailing list > Wiktionary-l(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wiktionary-l -- Association Culture-Libre http://www.culture-libre.org/

1 0

Replication to the toolserver stopped
by Silke Meyer 30 Jul '13

30 Jul '13

Hi wikitech-l! The db replication of s5 and s6 stopped on the toolserver. Merlissimo searched for information and found that you stopped some of your slaves that toolserver is using as master. Is there an ETA when they will be back? Please provide some information! Thanks und cheers, Silke -- Silke Meyer Internes IT-Management und Projektmanagement Toolserver Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin Tel. (030) 219 158 260 http://wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.

3 2

Re: [Wikitech-l] [Wikimania-l] Wikimania DevCamp
by aude 30 Jul '13

30 Jul '13

On Tue, Jul 30, 2013 at 8:02 AM, Lodewijk <lodewijk(a)effeietsanders.org>wrote: > > 2013/7/30 Deryck Chan <deryckchan(a)gmail.com> > >> Actually you do. Registering for Wikimania will be highly appreciated. >> > > OK, but to clarify: if you are already registered for Wikimania (as most > people who are on this mailing list and will be in Hong Kong) there is > nothing else you'd have to do? > Exactly! There is no additional registration process for DevCamp Cheers, Katie > > Thanks, > Lodewijk > > _______________________________________________ > Wikimania-l mailing list > Wikimania-l(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikimania-l > > -- @wikimediadc / @wikidata

1 0

Re: [Wikitech-l] no TLS 1.1 and 1.2 support
by Greg Grossmeier 30 Jul '13

30 Jul '13

Hi 0x0000, <quote name="0x0000" date="2013-07-28" time="23:35:19 +0200"> > hi, > recently i tested several sites who are using https, most of them > communicate with my chromium-webbrowser over TLS 1.1, but > wikipedia/wikimedia still is using TLS 1.0. > ssllabs (see link below) shows a warning notice that you should > upgrade to the newer version, i dont think there is a urgent > security reason for this but even if its only preventive upgarding > wouldn't be wrong, right? > > example: > https://encrypted.google.com/ TLS 1.1 > https://mega.co.nz/ TLS 1.1 > https://www.ixquick.com/ TLS 1.1 > https://btc-e.com/ TLS 1.1 > https://www.wsws.org/ TLS 1.1 > https://linksunten.indymedia.org/ TLS 1.1 > https://en.wikipedia.org TLS 1.0 > https://commons.wikimedia.org/ TLS 1.0 > https://www.taz.de/ TLS 1.0 > https://duckduckgo.com/ TLS 1.0 > > > https://www.ssllabs.com/ssltest/analyze.html?d=https://en.wikipedia.org > > > hopefully at the right mailinglist, greetings 0x0000(a)anche.no In this reply I just included wikitech-l(a)lists.wikimedia.org, which is probably a better place than the Wikidata specific mailing list. Best, Greg -- | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |

8 15

New Senior Software Engineer: Bryan Davis
by Rob Lanphier 30 Jul '13

30 Jul '13

Hi everyone, I'm pleased to welcome Bryan Davis to Wikimedia Foundation's Platform Engineering team. Bryan joins us from Keynetics in Boise, Idaho, where he was the senior programmer and architect on a team responsible for new product development, building the Kount fraud control system. Bryan joins Platform Engineering as a Senior Software Engineer working generally on backend software issues. His first job will be in improving the robustness of media infrastructure, such as improving large file uploads, but he'll probably also get mixed up in the usual Platform-y kinds of stuff that other developers in Platform Engineering frequently get involved in. Bryan will be working remotely from Boise. Rob

4 3

Git migration: complete
by Chad 30 Jul '13

30 Jul '13

With the moving of pywikibot to Gerrit today, the last projects actively using SVN have been moved over to Git. As such, SVN is now a read-only service and the migration is done (of course any old SVN projects can always be migrated to Git/Gerrit, that's easy). Thanks to everyone for your patience, help, bug reports, blood, sweat, tears, firstborn children...whatever you gave to this monumental effort over the past year and a half. I'm thinking of switching to Source Safe next year because migrations are so fun ;-) -Chad

12 14

Uninstall UploadBlacklist extension from Wikimedia wikis (bug 52056)
by MZMcBride 30 Jul '13

30 Jul '13

Hi. https://bugzilla.wikimedia.org/show_bug.cgi?id=52056 I've proposed uninstalling the UploadBlacklist extension from Wikimedia wikis. My reasoning: * it's a very small extension whose configured blacklist, as far as I'm aware, hasn't been updated in years; * the AbuseFilter now supports blocking uploads based on SHA-1 hash; * I don't consider the blacklist particularly effective as it's trivial to bypass (intentionally or accidentally); and * uninstalling the extension will help reduce, ever-so-slightly, some technical debt. On the relevant bug, Andre suggested that this needed further discussion. Please comment on the bug or on this mailing list if you have any objections or foresee any issues with uninstalling the UploadBlacklist extension from Wikimedia wikis. Otherwise, it's a largely painless procedure to uninstall the extension that I'm hoping we can move forward with in the next few weeks. MZMcBride

2 1

← Newer
1
2
3
4
5
6
7
...
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