Wikitech-l February 2017

wikitech-l@lists.wikimedia.org

68 participants
73 discussions

Readership metrics for the timespan until February 5, 2017
by Zareen Farooqui 14 Feb '17

14 Feb '17

Link to PDF of report in Commons <https://commons.wikimedia.org/wiki/File:Wikimedia_Readership_metrics_for_th…> Hi all, Here is the usual look <https://www.mediawiki.org/wiki/Reading/Readership_metrics_reports> at our most important readership metrics. This time we see an overall rise in pageviews following the seasonal winter slump, examine the recent year-over-year growth in pageviews more closely, and introduce a new day-7 retention metric for the Wikipedia iOS app. 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 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 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 five weeks. You can also find lots of other traffic and usage data in the quarterly metrics presentation <https://commons.wikimedia.org/wiki/File:Wikimedia_Foundation_Reading_metric…> for Q2 2016-2017 (October - December) that was just published by the WMF Reading team. All numbers below are averages for January 2 - February 5, 2017 unless otherwise noted. Pageviews Total: 582 million/day (+10.14% from the previous report) Context (April 2015-February 2017): See also the Vital Signs dashboard <https://analytics.wikimedia.org/dashboards/vital-signs/#projects=all/metric…> After the seasonal winter slump, we see a rise in desktop pageviews, as expected. Mobile pageviews continue to remain at higher levels than before christmas. The previously mentioned iOS app’s pageview increase is still under investigation, and may turn out to be an anomaly <https://phabricator.wikimedia.org/T154735> inflating mobile pageviews by roughly 5 million views per day. This chart looks at long-term traffic trends from May 2013 - January 2017. This shows that over this timespan, the annual change in overall pageviews was -2%, desktop has been down 15%, and mobile (web + apps) has been trending upwards at a rate of 23% per year. However, the past few months have seen total pageviews increasing year-over-year (chart further below). 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): Total pageviews have continued rising and are now higher than before the winter holidays. The blue line shows that the increase in overall pageviews year-over-year remains (January 2017 is up 5% from January 2016). It is possible that a smaller part of this is due to unidentified bot traffic (e.g. we just updated <https://phabricator.wikimedia.org/T157528> the pageview definition to exclude a recently discovered bot that had been causing up to 0.9% of total pageviews). But overall it is starting to look like a small but sustained rise in real human pageviews. Here we see that the changed trend in recent months can be attributed to desktop pageviews, which have mostly stopped declining year-over-year. This chart also shows that the seasonal christmas dip in pageviews comes predominantly from desktop views. Most recently, January 2017 desktop pageviews are again down 1.8% from January 2016, but that is still much less than the aforementioned -15% yearly trend since 2013. Year-over-year mobile pageviews are still increasing at a notable rate, but slower than in 2013-15. January 2017 mobile pageviews are up 13% from January 2016, less than the yearly mobile growth of 23% in the overall 2013-17 timespan. We can see how mobile pageviews always increase around the winter holidays and maintain higher levels afterwards. Desktop: 50.9% (previous report: 51.5%) Mobile web: 46.7% (previous report: 46.8%) Apps: 2.4% (previous report: 1.7%) Mobile percentage dropped a bit following the christmas spike, but remains high at an average of 49% mobile views. The previously mentioned iOS app’s pageview increase is still under investigation, and may turn out to be an anomaly <https://phabricator.wikimedia.org/T154735> inflating this metric by about 1%. Global North ratio: 77.3% of total pageviews (previous report: 76.8%) Context (January 2016-February 2017): Although Global North pageview percentage fell following the winter spike, but overall this metric grew since the last report. Levels remain in the high 70 percentile range. 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 2016 for background and details on this 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 it is currently being extended <https://phabricator.wikimedia.org/T138027> to a cross-language global metric per project at least. For now, we track the daily numbers of English Wikipedia in this report. Daily unique devices estimate for English Wikipedia: - Mobile web: 36.3 million - Desktop: 24.3 million - Total: 60.6 million - Average mobile web ratio: 60.0% Context (January 2016- February 2017): Since the last report, both daily unique desktop devices and mobile devices grew. Mobile web daily uniques mirrors the daily pageviews chart - mobile web unique levels have remained higher than before the winter bump. January 2017 was the first month we could compare year-over-year changes in unique devices. While pageviews on English Wikipedia are up from January 2016, the number of monthly unique devices is down 16%. For this report timespan (Jan 2 - Feb 5), daily mobile web uniques are up 2.6%, while daily desktop uniques are down 8.2%. This is currently being investigated. While the number of daily unique desktop devices has grown overall, the ratio of pageviews to devices on desktop has steadily declined back to pre christmas levels. The small, but notable increase in daily views per device for mobile web which happened in November has held up. New app installations Android: 18.0k/day (-5.9% from the previous report) Daily installs per device, from Google Play Context (last nine months): The number of daily installs dropped after the christmas spike, but remains higher than the number of uninstalls (except for January 26). Overall, the number of daily installs has dropped nearly 6% and daily uninstalls dropped about 8% since the last report. iOS: 5.67k/day (+6.5% from the previous report) Download numbers from App Annie Context (last two months): [image: Wikipedia iOS app daily downloads by country, Dec 6, 2016 - Feb 5, 2017 (App Annie).png] Similar to other mobile metrics measured in this report, the iOS app download metric has remained higher than usual following the winter bump. During the timespan of this report, iOS app downloads remain fairly steady besides two large, unusual spikes at the end of January in the United Arab Emirates and the United States (which follow the spike from the Netherlands in December) which are likely anomalies. We are looking into filing a bug report with App Annie to investigate this. App user retention Android: 15.6% (previous report: 16.8%) (Ratio of app installs opened again 7 days after installation for all dates that fall within this report. 1:100 sample) Context (last six months): As remarked in earlier reports, this data is a bit too noisy for drawing conclusions about whether retention changed significantly between different releases. However, we can at least rule out the existence of major shifts during this timespan. There was a small spike in day 7 retention for installs on January 22nd. iOS: 19.2% (previous report: N/A <https://phabricator.wikimedia.org/T126693> ) (Ratio of app installs opened again 7 days after installation for all dates that fall within this report. 100:100 sample since iOS app only sends data when users opt-in so there is a small user base) Context (last two months): After a long break where we refrained from reporting iOS retention here due to data quality issues with the number provided by Apple, we are happy to report iOS app 7 day retention again, based on a new EventLogging instrumentation that parallels the one on Android. There doesn’t seem to have been any significant changes in retention levels during the timespan of this report, even after new releases of the app. Looking back at December though, it appears that there was a period of lower retention which roughly corresponds with stability issues (crashes) the app was having at this time, and which have since been fixed. Unique app users Android: 1.211 million / day (+2.7% from the previous report) Context (last eight months): Android daily average levels have remained higher following the christmas and new year’s bump. This matches the mobile pageviews and unique mobile devices metrics. 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, CONCAT(year,"-",LPAD(month,2,"0")) as yearmonth, SUM(view_count) AS allhuman, sum(IF(access_method = 'desktop', view_count, null)) AS desktophuman FROM wmf.projectview_hourly WHERE year = 2017 AND agent_type = 'user' GROUP BY year, month ORDER BY year, month LIMIT 1000; 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 = 2017 AND agent_type = 'user' GROUP BY year, month, day ORDER BY year, month, day LIMIT 1000; SELECT access_method, SUM(view_count)/(7*5) FROM wmf.projectview_hourly WHERE agent_type = 'user' AND CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) BETWEEN "2017-01-02" AND "2017-02-05" 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,I S,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 = 2017 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=2017 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=2017 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=2017 AND agent_type = 'user' AND project = 'en.wikipedia' GROUP BY year, month, day ORDER BY year, month, day LIMIT 1000; https://console.cloud.google.com/storage/browser/pubsite_prod_rev_028125227… https://www.appannie.com/dashboard/252257/item/324715238/downloads/ 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 '2017%' AND userAgent LIKE '%-r-%' AND userAgent NOT LIKE '%Googlebot%' GROUP BY date ORDER BY DATE; 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 userAgent LIKE '%iPhone%' OR userAgent LIKE '%iOS%' GROUP BY date ORDER BY DATE; 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 year = 2017 AND platform = 'Android'; Zareen Farooqui

1 0

Fwd: [Wikimedia-l] Open call for Project Grant proposals (Feb 13-Mar 14)
by Quim Gil 14 Feb '17

14 Feb '17

FYI ---------- Forwarded message ---------- From: Marti Johnson <mjohnson(a)wikimedia.org> Date: Tue, Feb 14, 2017 at 5:00 AM Subject: [Wikimedia-l] Open call for Project Grant proposals (Feb 13-Mar 14) To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org> Hi everyone, The Wikimedia Foundation Project Grants program launches its third open call today, February 13. We will be accepting proposals through March 14 for new ideas to improve Wikimedia projects. < https://meta.wikimedia.org/wiki/Grants:Project> Funds are available to support individuals, groups and organizations to implement new experiments and proven ideas, whether focused on building a new tool or gadget, organizing a better process on your wiki, researching an important issue, coordinating an editathon series or providing other support for community-building. Ideas from the current Inspire Campaign on developing outside knowledge networks are very welcome. < https://meta.wikimedia.org/wiki/Grants:IdeaLab/Inspire> We will be hosting weekly proposals clinics via Hangouts for real-time discussions about the Project Grants Open Call. Links for Hangouts will be posted by tomorrow here: < https://meta.wikimedia.org/wiki/Grants:Project#Upcoming_events> In addition, we have just launched our new tutorial videos to help guide applicants through key portions of the proposal writing process: < https://meta.wikimedia.org/wiki/Grants:Project/Tutorial> We are excited to see your grant ideas that will support our community and make an impact on the future of Wikimedia projects. Put your idea into motion, and submit your proposal between February 13 and March 14! < https://meta.wikimedia.org/wiki/Grants:Project/Apply> Please feel free to get in touch with me (mjohnson(a)wikimedia.org) or Alex Wang (awang(a)wikimedia.org) with questions about getting started with your project! Warm regards, Marti *Marti JohnsonProgram Officer* *Individual Grants* *Wikimedia Foundation <http://wikimediafoundation.org/wiki/Home>* +1 415-839-6885 Skype: Mjohnson_WMF Imagine a world in which every single human being can freely share <http://youtu.be/ci0Pihl2zXY> in the sum of all knowledge. Help us make it a reality! Support Wikimedia <https://donate.wikimedia.org/> _______________________________________________ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/ wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/ wiki/Wikimedia-l 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> -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil

1 0

Changes at Wikimedia Foundation
by Wes Moran 13 Feb '17

13 Feb '17

Hello everyone, After a great deal of consideration, I have decided that I need to take a different path for my life and I am moving on from the Wikimedia Foundation. I have struggled with this decision as I have great admiration for the mission and the people here. I have great appreciation for how we worked together over the past two years, and great pride in what we have accomplished. The wide range of experiences have been amazing, and it feels like many more years than just two. I am looking at a departure date of Feb 28th. Until that time, I will be supporting the Product teams through the first draft of Annual Planning. Katherine Maher, Victoria Coleman and I will work together with people across the Product and Technology departments, to develop a transition plan that is in the best interest of the teams I support, the Foundation, and our movement. Toby Negrin, currently the Head of Reading, will take over as acting leadership for Product on 2/28. He has been working closely with me on many of the key programs and initiatives our department has been planning. He and the rest of Product leadership will continue with our Annual Planning efforts and conclude the 2016-17 goals and programs. It has been such a deep honor to work with the folks in Technology and Product. I started here with Discovery, and have a special respect for what that team has accomplished as it evolved. The opportunity to lead Product, work with chapters like Wikimedia Deutschland, engage with the communities, and collaborate at the C-level was exciting and humbling. I was happy to work with the Product teams as they evolved into audiences and ultimately a Product organization focused on users and their needs. A testament to their excellent work is summarized in our 2016 Product summary <https://www.mediawiki.org/wiki/Wikimedia_Product/2016_Product_Summary> [1]. Working with the folks in Technology to find our CTO was exciting, challenging, and illuminating. It was a wonderful and unexpected path that would not have been possible without the great support of that team. There are so many partnerships both with teams and individuals across this organization and other organizations that I had the chance to engage and work together with. I have a great deal of respect and confidence in all of you to propel us through the Movement, Foundation and team strategies and goals in the next two years. Similarly I am proud of the stands we take and voices we lend as we all work to protect and project freedom, and the public availability of the sum of all knowledge. I hope to help support that as a volunteer in whatever way I can. Thank you, Wes Vice President of Product, Wikimedia Foundation [1] https://www.mediawiki.org/wiki/Wikimedia_Product/2016_Product_Summary

3 2

Discovery Weekly Update for the week starting 2017-02-06
by Chris Koerner 12 Feb '17

12 Feb '17

Hello again, This week saw a few updates from around the department. The big highlight is a first look at cross-wiki search. == Highlights == * Inter-wiki search is here! An A/B test of a new search results page which includes inter-wiki search results was deployed to Persian, Italian, Catalan and Polish Wikipedias. Take a look and give us feedback! [0] [1] == Discussions == === Search === * Inter-wiki search is here! An A/B test of a new search results page which includes inter-wiki search results was deployed to Persian, Italian, Catalan and Polish Wikipedias. Take a look and give us feedback! [0] [1] * TextCat (language ID) improvements for German, English, Spanish, French, Italian, Japanese, Portuguese, and Russian Wikipedias have been deployed. [2] In general, more languages are available to be detected, and detection accuracy is higher. [3] * TextCat has also been enabled on the Dutch Wikipedia. [4] * A warning is now displayed if a user runs an advanced search query which only returns partial results due to a query timeout. [5] * Our initial analysis of the Stempel Polish analyzer is done. [6] Overall it works well, but has some rare but bizarre stemming bugs. [7] There’s a live demo with the Polish Wikipedia index in labs. [8] Feedback on the Phab ticket (T154517) or talk page of the write up is very welcome. [9] [10] [0] https://ca.wikipedia.org/wiki/?fulltext=1&search=Illa+d%27Irlanda&cirrusUse… [1] https://phabricator.wikimedia.org/T149806 [2] https://phabricator.wikimedia.org/T149324 [3] https://www.mediawiki.org/w/index.php?title=User:TJones_(WMF)/Notes/TextCat… [4] https://phabricator.wikimedia.org/T142140 [5] https://phabricator.wikimedia.org/T149142 [6] https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/Stempel_Analyzer_Ana… [7] https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/Stempel_Analyzer_Ana… [8] http://pl-wp-stempel-relforge.wmflabs.org/w/index.php?title=Specjalna:Szukaj [9] https://phabricator.wikimedia.org/T154517 [10] https://www.mediawiki.org/w/index.php?title=User_talk:TJones_(WMF)/Notes/St… ---- The archive of all 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

Multilingual maps: how to pick each feature language?
by Yuri Astrakhan 10 Feb '17

10 Feb '17

TLDR: if browsing a map for French wiki, and a city only has a Russian and Chinese name, which one should be shown? Should the city name have different rules from a store or a street name? ... I have been hacking to add unlimited multilingual support to Wikipedia maps, and have language fallback question: given a list of arbitrary languages for each map feature, what is the best choice for a given language? I know Mediawiki has language fallbacks, but they are very simple (e.g. for "ru", if "ru" is not there, try "en"). Some things to consider: * Unlike Wikipedia, where readers go for "meaning", in maps we mostly need "readability". * Alphabets: Latin alphabet is probably the most universally understood, followed by...? Per target language? * Politics: places like Crimea tend to have both Russian and Ukrainian names defined, but if drawing map in Ukrainian, and some feature has Russian and English names, but not Ukrainian, should it be shown with the Russian or Ukrainian name? * When viewing a map of China in English, should Chinese (local) name be shown together with the English name? Should it be shown for all types of features (city name, street name, name of the church, ...?) Thanks!

4 3

ArchCom Status & Meeting Minutes, WD6
by Daniel Kinzler 10 Feb '17

10 Feb '17

Hi all! Here are the minutes from this week's ArchCom meeting. You can also find the minutes at <https://www.mediawiki.org/wiki/Architecture_committee/2017-02-08>. See also the ArchCom status page at <https://www.mediawiki.org/wiki/Architecture_committee/Status> and the RFC board <https://phabricator.wikimedia.org/tag/mediawiki-rfcs/>. Here are the minutes, for your convenience: * ArchCom plans to take part in Scrum of Scrums in the future * IRC discussion about database schema improvements next week, pending confirmation. This is a follow-up to [[phab:T149534]]. * [[phab:T66214]]: Define an official thumb API: Gergö concerned about third party install efficiency. * [[phab:T122942]]: Support language variants in the REST API: Current discussion is primarily about path prefix vs. Accept-Language header. * [[phab:T155813]]: Decide on storage and delivery method for TemplateStyles CSS: Lively discussion, pinged Parsing team. * [[phab:T107561]]: MediaWiki support for Composer equivalent for JavaScript packages was selected for the developer whishlist. There has been some discussion in the last week, but more input is needed. One open topic is how this relats to ResourceLoader. * [[phab:T129842]]: Launch the Wikimedia "Code Review Special Interest Group" has gained some tracktion. Quim is looking for participants! * Schema migration for the oldimage table pending implementation: [[phab:T28741]] -- Daniel Kinzler Principal Platform Engineer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V.

1 0

Slight CI disruption overnight (solved)
by Antoine Musso 10 Feb '17

10 Feb '17

Hello, We had a short downtime of CI between roughly 3am and 9am UTC that caused roughly 2/3 of triggered jobs to fail cloning. The reason is we deployed additional zuul-merger instances (which takes your patches, merge it on tip of branch and then expose the result to jobs) but the git-daemon exposing the repositories was not started. I respawned the git-daemon and it all works properly now. I am doing a recheck and CR+2 again all patches that got affected. Reference: https://phabricator.wikimedia.org/T157785 cheers, -- Antoine "hashar" Musso

1 0

Video transcode prioritization changes in progress
by Brion Vibber 09 Feb '17

09 Feb '17

We're in progress of deploying a small change to the video scalers[1], which should improve availability of newly uploaded video and audio files. The queue will now be split in two, one which covers low-resolution conversions for relatively short files, and one which covers long files and high-resolution conversions. When there's a flood of large uploads, other new files should still go through the high-priority queue while the large uploads and HD conversions may back up on the low-priority queue. The queue-runner side is updated now (done during the 'puppet SWAT' deployment window), with the MediaWiki side ready to roll around 19:00 UTC (11am Pacific time, regular SWAT deployment window). [1] https://gerrit.wikimedia.org/r/#/c/336846/ -- brion

2 4

Mediawiki core has reached to its 400th contributor
by Amir Ladsgroup 09 Feb '17

09 Feb '17

Hey, Today I was checking mediawiki/core in github: https://github.com/wikimedia/mediawiki And number of contributors is now 400. It might be a little more if we count SVN era. To me, it's an important milestone. More important than number of commits or releases. It's about people not numbers or lines of code. Best

7 6

Please review "Amendments" section of the Code of Conduct
by Matthew Flaschen 08 Feb '17

08 Feb '17

Please take this as a final opportunity to do review/suggest changes/etc. to the Amendments section of the draft Code of Conduct. This text has been up for a while, but I recently put in a small proposed change to make it harder for the Committee to veto amendments. This is the last section. After it's approved, the Code of Conduct will become policy, and the Amendments section will specify how future changes to the policy work. * Current text: https://www.mediawiki.org/w/index.php?title=Code_of_Conduct/Draft&oldid=238… (under "Page: Code of Conduct/Amendments") * Discussion: https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#New_proposal_for_… The approval discussion hasn't started yet. It will be next and I will send out a separate email. Thanks, Matt Flaschen P.S. You can still participate in deciding whether to approve "Creation and renewal of the Committee" at https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Finalize_.22Creat… .

2 1

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 February 2017