Wikitech-l December 2016

wikitech-l@lists.wikimedia.org

83 participants
84 discussions

Discussion Platform
by MAYANK JINDAL 12 Dec '16

12 Dec '16

Hi, We are using IRC for discussion purpose. How will it be if we change our discussion platform? Many organizations have switched to gitter that have very user-friendly UI and very easy to use. Please give a view on my proposal. -- Kind Regards, Mayank Jindal, Third year undergraduate student, Indian Institute of Technology Kharagpur Mobile : +91- 7076670299 || 8875432718

11 13

Fwd: Readership metrics for the timespan until December 4, 2016
by Zareen Farooqui 12 Dec '16

12 Dec '16

Hi all, Please see below for the Readership metrics report for the timespan until December 4, 2016. Zareen Farooqui ---------- Forwarded message ---------- From: Zareen Farooqui <zareenf(a)gmail.com> Date: Mon, Dec 12, 2016 at 8:45 PM Subject: Readership metrics for the timespan until December 4, 2016 To: mobile-l(a)lists.wikimedia.org Cc: schang(a)wikimedia.org, slien(a)wikimedia.org, wikitech-l(a)lists.wikimedia.org, analytics(a)lists.wikimedia.org, fr-online(a)wikimedia.org Hi all, This resumes the usual look <https://www.mediawiki.org/wiki/Reading/Readership_metrics_reports> at our most important readership metrics. This time we can report that daily pageviews are up 4.8% (since the last report), with an interesting recent peak which meant that November’s pageviews surpassed those of November 2015 (coincidentally also) by 4.8%, after October had already seen a 2.1% year-over-year increase. The iOS Wikipedia app saw increased downloads, while the Android app’s install base has stopped its previous downward trend. As laid out earlier <https://lists.wikimedia.org/pipermail/mobile-l/2015-September/009773.html>, the main purpose is to raise awareness about how these metrics are developing, call out the impact of any unusual events, and facilitate thinking about core metrics in general. As always; feedback and discussion welcome. Week-over-week and month-over-month changes are now being recorded on the Product page <https://www.mediawiki.org/wiki/Wikimedia_Product#Reading> at MediaWiki.org. This edition of the report covers a timespan of eighteen weeks. Some other recent items of interest, in case they didn’t already catch your attention: - The WMF Reading team published its quarterly review presentation <https://commons.wikimedia.org/wiki/File:Reading_and_Comm_Tech_Quarterly_Rev…> for Q1 2016-17 (July-September), which includes lots of traffic and usage data. - At the Foundation’s August metrics meeting <https://commons.wikimedia.org/w/index.php?title=File%3AAugust_2016_Monthly_…>, the Reading team gave an update on longer-term traffic trends since 2013. (TL;DR: Overall pageviews have been flat to slightly declining, mobile has been steadily rising but recently slowed down, desktop has declining during these three years. However, total pageviews have been slightly increasing year-over-year in the last few months.) See the chart below, updated with data until November: [image: Wikimedia monthly pageviews (desktop+mobile), 2013-2016 (version December 2016).png] In particular, as mentioned, the number of total pageview saw year-over-year increases of +2.1% for October and +4.8% in November, in contrast to e.g. the -10.5% we had for May 2015-May 2016. Now to the usual data. (All numbers below are averages for August 1-December 4, 2016 unless otherwise noted.) Pageviews Total: 529 million/day (+4.76% from the previous report timeframe, with corrected numbers for anomalously high traffic on some main pages <https://phabricator.wikimedia.org/T141506>) Context (April 2015-December 2016): See also the Vital Signs dashboard <https://analytics.wikimedia.org/dashboards/vital-signs/#projects=all/metric…> (Small caveats: iOS app’s pageviews were undercounted by about 1.6 million/day from mid September to early November due to a bug <https://phabricator.wikimedia.org/T148663>.) Overall pageviews increased steadily during the timespan of this report aside from the week ending October 30th (right before Halloween) and the end of November. There appears to be a peak in pageviews in November. To facilitate our understanding of which traffic movements are seasonal and which may indicate lasting changes, here is a chart overlaying the total pageview numbers back to May 2013 (the earliest time for which we have data according to the current pageview definition): The blue line indicates a non-seasonal rise peaking around November 12. We checked whether this peak came from a particular country and were able to exclude that possibility. Wikimedia Daily Pageviews from US Pageviews in US do not show any drastic changes (even around the time of the US elections). Wikimedia Daily Pageviews from Mexico In Mexico, there seems to been a huge drop starting October 27th (perhaps some sort of local outage). Wikimedia Daily Pageviews from Ecuador Ecuador shows a huge spike on October 30th, followed by a drop for several days. Desktop: 54.1% (previous report: 54.1%) Mobile web: 44.8% (previous report: 44.6%) Apps: 1.1% (previous report: 1.3%) (missing some iOS pageviews, cf. above) Context (December 2015 - December 2016): Overall mobile percentage is similar to the last report, but we did see a small increase (besides one week in August) until late September. As a reminder, mobile already has a solid majority in terms of unique devices, cf. below. Global North ratio: 75.3% of total pageviews (previous report: 75.5%) Context (January - December 2016): There is a slight increase in Global North percentage in late October and November, but overall this number is relatively steady. NB: We are currently rethinking this metric and might replace it with a different country selection constructed as part of the work on the New Readers project. Unique devices See the announcement blog post <https://blog.wikimedia.org/2016/03/30/unique-devices-dataset/> from March for background and details on this recently introduced metric. These estimated numbers are provided for all Wikimedia language projects (separately for the desktop and mobile web version). Because of the instrumentation method, there is no global metric for all projects and all languages, but following some recent discussions it is now planned <https://phabricator.wikimedia.org/T138027> to extend it to a cross-language global metric per project at least. For now, we track the daily numbers of the English Wikipedia in this report. Daily unique devices estimate for English Wikipedia: - Mobile web: 33.9 million (previous report: 32.2 million) - Desktop: 24.1 million (previous report: 22.3 million) - Total: 57.9 million (previous report: 54.5 million) - Average mobile web ratio: 58.7% (previous report: 59.3%) Context (January- December 2016): This metric hasn’t existed long enough yet to get a good sense of what yearly seasonalities may exist, but since the last report time frame daily unique desktop devices show an increasing upward trend until early November, where there is a peak and then an apparent drop (which parallels the peak in pageviews). To understand the peak in daily unique devices, we plotted the ratio of daily pageviews to daily unique devices. There is a small bump in the mobile ratio in early November, but it is too small to fully explain the rise in pageviews around this time. New app installations Android: 19.9k/day (+1.21% from the previous report) Daily installs per device, from Google Play Context (last seven months): Download numbers increased in September and have sustained previous levels so far, possibly helped by the app’s inclusion on the Education category page <https://play.google.com/store/apps/category/EDUCATION> in Google’s Play Store. There was an additional bump in mid September (reason unknown). The number of daily uninstalls decreased slightly. During the timespan of the previous report, installs had markedly decreased (except for a so far unexplained bump during two weeks in July), which combined with the high uninstall numbers had caused the app’s install base to shrink from 15.5 million on March 31 to 15.1 million at the beginning of August. This trend has now been stopped, although the number was still at 15.1 million on November. (Google has since discontinued <https://support.google.com/googleplay/android-developer/answer/7003402#acti…> this “current installs” metric in favor of a new “installs on active devices" metric.) iOS: 6.35k/day (+99.9% from the previous report) Download numbers from App Annie Daily downloads (with the largest countries broken out): [image: Wikipedia iOS app daily downloads by country, Aug 1 ~ Dec 7, 2016 (App Annie).png] The iOS Wikipedia app was promoted on iTunes in September, with huge impact (twice as many downloads than resulted from a comparable promotion in September 2015). Total daily downloads remained on a higher level afterwards (4.8k/day during the last week of this report, Nov 28-Dec 4). Around October 24, downloads from the US spiked, possibly helped by some organic media coverage such as this <http://thetechbeard.com/best-free-ios-10-widgets/>. On November 11, we registered an extra 9000 downloads from Sweden, for unknown reasons (no app store promotions or media coverage that we are aware of). App user retention Android: 16.4% (previous report: 16.7%) (Ratio of app installs opened again 7 days after installation, among all installed one week before a date that falls within this report. 1:100 sample) Context (last seven months): As remarked in earlier reports, this data is a bit too noisy for drawing conclusions about whether retention changed significantly between different releases. Retention appears to have dropped somewhat in September after having gradually grown earlier during the timespan of the last report and after. iOS: N/A <https://phabricator.wikimedia.org/T126693> (We recently began measuring this on the iOS app - using the same method as on Android, restricted to users who opt-in to data collection - but there is not enough data yet.) Unique app users Android: 1.146 million / day (+0.0% from the previous report) Context (last six months): In September/October, there seems to be a very small growth in daily average users. iOS: N/A <https://phabricator.wikimedia.org/T130432> Zareen Farooqui, Data Analyst Intern, Wikimedia Foundation Tilman Bayer, Senior Analyst, Wikimedia Foundation Data sources For reference, the queries and source links used are listed below (access is needed for each). Unless otherwise noted, all content of this report is © Wikimedia Foundation and released under the CC BY-SA 3.0 <https://creativecommons.org/licenses/by-sa/3.0/> license. Most of the above charts are available on Commons, too. <https://commons.wikimedia.org/wiki/Category:Wikimedia_readership_metrics_re…> SELECT year, month, day, CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) as date, sum(IF(access_method <> 'desktop', view_count, null)) AS mobileviews, SUM(view_count) AS allviews FROM wmf.projectview_hourly WHERE year>0 AND agent_type = 'user' GROUP BY year, month, day ORDER BY year, month, day LIMIT 1000; SELECT LEFT(timestamp, 10) AS date, sum(IF(access_method <> 'desktop', pageviews, null)) AS mobileviews, SUM(pageviews) AS allviews FROM staging.pageviews05 WHERE is_spider = FALSE AND is_automata = FALSE GROUP BY date; Pivot URLs: United States <https://pivot.wikimedia.org/#pageviews-daily/line-chart/2/EQUQLgxg9AqgKgYWA…> Mexico <https://pivot.wikimedia.org/#pageviews-daily/line-chart/2/EQUQLgxg9AqgKgYWA…> Ecuador <https://pivot.wikimedia.org/#pageviews-daily/line-chart/2/EQUQLgxg9AqgKgYWA…> SELECT access_method, SUM(view_count)/(7*18) FROM wmf.projectview_hourly WHERE agent_type = 'user' AND CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) BETWEEN "2016-08-01" AND "2016-12-04" GROUP BY access_method; SELECT year, month, day, CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")), SUM(view_count) AS all, SUM(IF (FIND_IN_SET(country_code, 'AD,AL,AT,AX,BA,BE,BG,CH,CY,CZ,DE,DK,EE,ES,FI,FO,FR,FX,GB, GG,GI,GL,GR,HR,HU,IE,IL,IM,IS,IT,JE,LI,LU,LV,MC,MD,ME,MK,MT, NL,NO,PL,PT,RO,RS,RU,SE,SI,SJ,SK,SM,TR,VA,AU,CA,HK,MO,NZ,JP,SG,KR,TW,US') > 0, view_count, 0)) AS Global_North_views FROM wmf.projectview_hourly WHERE year > 0 AND agent_type='user' GROUP BY year, month, day ORDER BY year, month, day LIMIT 1000; SELECT year, month, day, CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) as date, SUM(IF(uri_host LIKE 'en.m.wikipedia%', uniques_estimate, 0)) AS enwiki_mobile_web FROM wmf.last_access_uniques_daily WHERE year=2016 GROUP BY year, month, day ORDER BY year, month, day LIMIT 1000; SELECT year, month, day, CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) as date, SUM(IF(uri_host LIKE 'en.wikipedia%', uniques_estimate, 0)) AS enwiki_desktop FROM wmf.last_access_uniques_daily WHERE year=2016 GROUP BY year, month, day ORDER BY year, month, day LIMIT 1000; SELECT year, month, day, CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) AS date, SUM(IF(access_method = 'mobile web', view_count, null)) AS mobilewebviews, SUM(IF(access_method = 'desktop', view_count, null)) AS desktopviews FROM wmf.projectview_hourly WHERE year=2016 AND agent_type = 'user' AND project = 'en.wikipedia' GROUP BY year, month, day ORDER BY year, month, day LIMIT 1000; SELECT LEFT(timestamp, 8) AS date, SUM(IF(event_appInstallAgeDays = 0, 1, 0)) AS day0_active, SUM(IF(event_appInstallAgeDays = 7, 1, 0)) AS day7_active FROM log.MobileWikiAppDailyStats_12637385 WHERE timestamp LIKE '201510%' AND userAgent LIKE '%-r-%' AND userAgent NOT LIKE '%Googlebot%' GROUP BY date ORDER BY DATE; (with the retention rate calculated as day7_active divided by day0_active from seven days earlier, of course) https://analytics.itunes.apple.com/#/retention?app=324715238 SELECT CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) as date, unique_count AS Android_DAU FROM wmf.mobile_apps_uniques_daily WHERE platform = 'Android'; https://console.developers.google.com/storage/browser/pubsite_prod_rev_ 02812522755211381933/stats/installs/ (“overview”) https://www.appannie.com/dashboard/252257/item/324715238/downloads/ (select “Total”) Zareen Farooqui

1 0

Discovery Weekly Update for the week starting 2016-12-05
by Chris Koerner 12 Dec '16

12 Dec '16

This is the weekly update for the week starting 05 December. As always, feedback and questions are welcome. ==Highlights== * Load tests for cross-project searching were completed successfully. [0] We are now testing how many results are produced for typical queries as a first step towards figuring out how relevant the results are. [1] * Released tabular and map data namespaces to Commons, after reviewing implementation, consulting legal, enabling shared geojson data storage, and adding metrics tracking. [2] [3] [4] [5] [6] [7] [8] [9] === Search === * We've put together a draft proposal for how to deal with the interaction of all the possible additional search options—suggestions, quote-stripping, "wrong keyboard", language ID, etc.—to have a more co-ordinated conversation about all this. Comments on the talk page there are welcome. [10] * Load tests for cross-project searching were completed successfully. [11] We are now testing how many results are produced for typical queries as a first step towards figuring out how relevant the results are. [12] * Upgraded to Java 8 in preparation for upgrading ElasticSearch next quarter. [13] * Performed some refactoring to improve interwiki searching. [14] * Improved handling of characters containing diacritics or accents. [15] [16] * Added support for minimum query length to detect the language of the query. When a minimum length is eventually chosen, this will solve edge cases where some very short queries and queries consisting just of numbers could produce unexpected results. [17] * Fixed an edge case where third-party users of CirrusSearch could get an exception when building a completion suggester index. [18] === Analysis === * Fixed an error with installing R package Boom (& bsts) on stat1002 (but can on stat1003) [19] === Portal === * Add node 6 compatibility to Portal build tasks [20] === Interactive === * Enhance Report Updater to be able to send data to graphite [21] * Increase user sampling rate [22] * Investigate ClearTables [23] * Bug fixed: Closing maps by going back doesn't always work [24] * Updated and adapted Tabular Data to match published formats [25] * Updated Legal wording update for tabular and map data release [26] * Added information on how to change error message [27] * Updated the logging for Kartotherian from info to warn [28] == Other Noteworthy Stuff == * Published Wikimedia Discovery's narrative and roadmap for FY 2016/17 (July 2016 - June 2017) [29] [0] https://phabricator.wikimedia.org/T149740 [1] https://phabricator.wikimedia.org/T151935 [2] https://phabricator.wikimedia.org/T148745 [3] https://www.mediawiki.org/wiki/Help:Tabular_Data [4] https://www.mediawiki.org/wiki/Help:Map_Data [5] https://www.mediawiki.org/wiki/Extension:JsonConfig/Tabular [6] https://phabricator.wikimedia.org/T134426 [7] https://phabricator.wikimedia.org/T152553 [8] https://phabricator.wikimedia.org/T137930 [9] https://phabricator.wikimedia.org/T152661 [10] https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/So_Many_Search_Optio… [11] https://phabricator.wikimedia.org/T149740 [12] https://phabricator.wikimedia.org/T151935 [13] https://phabricator.wikimedia.org/T151325 [14] https://phabricator.wikimedia.org/T141033 [15] https://phabricator.wikimedia.org/T137830 [16] https://phabricator.wikimedia.org/T146402 [17] https://phabricator.wikimedia.org/T149318 [18] https://phabricator.wikimedia.org/T150799 [19] https://phabricator.wikimedia.org/T147682: [20] https://phabricator.wikimedia.org/T150190 [21] https://phabricator.wikimedia.org/T150187 [22] https://phabricator.wikimedia.org/T152174 [23] https://phabricator.wikimedia.org/T141964 [24] https://phabricator.wikimedia.org/T151915 [25] https://phabricator.wikimedia.org/T152184 [26] https://phabricator.wikimedia.org/T152553 [27] https://phabricator.wikimedia.org/T152554 [28] https://phabricator.wikimedia.org/T148116 [29] https://www.mediawiki.org/wiki/File:Discovery_narrative_FY_2016-17.pdf ---- The full update, and archive of past updates, can be found on MediaWiki.org: https://www.mediawiki.org/wiki/Discovery/Status_updates Interested in getting involved? See tasks marked as Easy or Volunteer needed in Phabricator. [1] https://phabricator.wikimedia.org/maniphest/query/qW51XhCCd8.7/#R [2] https://phabricator.wikimedia.org/maniphest/query/5KEPuEJh9TPS/#R Yours, Chris Koerner Community Liaison - Discovery Wikimedia Foundation

1 0

ArchCom RFC Meeting W51: Deprecation policy for PHP code in MediaWiki (2016-12-14, #wikimedia-office)
by Daniel Kinzler 12 Dec '16

12 Dec '16

Hi all! At the ArchCom RFC meeting on Wednesday [E412], we will talk about defining an official deprecation policy [T146965][DP]. I think it would be quite useful to discuss the different modes and methods of deprecation we have, and what they mean for MediaWiki core, and for extension developers. To me, one of the interesting questions is what happens if a deprecated function is still used in an extension that is not actively maintained. We can provide a patch - but who can review it? And if nobody reviews it, can we still remove the deprecated method? The meeting will be at the usual time (Wednesday 21 UTC, 14 PDT, 23 CET) and place (#wikimedia-office). For an overview of ArchCom activity, see [ArchComStatus]. -- Daniel [E412]: <https://phabricator.wikimedia.org/E412> [T146965]: <https://phabricator.wikimedia.org/T146965> [DP]: <https://www.mediawiki.org/wiki/Requests_for_comment/Deprecation_policy> [ArchComStatus]: <https://www.mediawiki.org/wiki/ArchComStatus> -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V.

1 0

Deploying the Linter extension to Wikimedia wikis
by Legoktm 10 Dec '16

10 Dec '16

Hi, Arlo and myself have been working on a new MediaWiki extension to expose Parsoid's "lint errors" to users. A little bit of background, Parsoid has a linter that identifies some issues in wikitext that while may not result in user-facing errors, are still not wanted in wikitext. An example might be [[File:Example.png|foo|bar|baz]]. In this case, "foo" and "bar" are ignored, and "baz" is the actual caption - but the bogus image options should be removed. Other errors include missing end tags, obsolete HTML tags, fostered content, etc. The main advantage of this over tracking categories is that we know the location in the wikitext so it should be easier to identify the error and fix it, as well as knowing whether the issue was caused via a template or not. The main ticket tracking deployment is <https://phabricator.wikimedia.org/T148609>. -- Legoktm

4 5

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 08 Dec '16

08 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 07 Dec '16

07 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

← Newer
1
2
3
4
5
6
7
8
9
Older →

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 December 2016