Developer Relations/Weekly summary/Next

2015-12-10
Help develop the next next summary.

DevRel focus
What keeps Developer Relations especially busy these days:


 * Google Code-in: program start
 * WikiDev16
 * finalizing logistics (contracts, video, transport, social events, and more)
 * "must have" sessions and keynotes
 * cordinate Collaboration area
 * Planning our quarterly goals for January - March 2016
 * Code of Conduct: implications and legal requirements of reports affecting Wikimedia Foundation employees

Check more details in #devrel-december-2015

Software

 * Survey: Understanding third-party use of Wikipedia content
 * Wikimedia IEG program will fund fourteen community-led projects (7 of them software based) (Wikimedia blog)
 * Batch Uploader for small GLAM projects
 * Pan Scandinavian Machine Assisted Content Translation
 * Wiki Needs Pictures
 * Wikimaps Warper 2.0
 * StrepHit: Wikidata Statements Validation via Reference
 * Semi-automatically generate Categories for Vietnamese Wikipedia
 * Proofreading semi-automatically the Catalan Wikipedia with LanguageTool
 * Selection of media coverage of the release of the Objective Revision Evaluation Service (ORES)
 * Artificial Intelligence and the Wisdom of the Crowd (HowStuffWorks, video)
 * Artificial Intelligence Aims to Make Wikipedia Friendlier and Better (MIT Technology Review)
 * Wikipedia launches edit-checking artificial intelligence (BBC News)
 * The Wikipedia app for Android, selected among Best Apps of 2015 in Google Play.

Past

 * 2015-12-09: RfC meeting minutes
 * 2015-12-09: Video of Tech Talk: Secure Coding For MediaWiki Developers

Upcoming

 * 2015-12-10: IRC office hour: Discussion about product development
 * 2015-12-14: Wikimedia Product showcase.
 * 2015-12-15: Tech Talk: How to integrate user behavior to get better designs
 * 2015-12-16: RfC meeting
 * 2015-12-22: Upcoming Lightning Talks. You can sign up or propose a talk
 * 2016-01-04/06 San Francisco: Wikimedia Developer Summit 2016
 * "must have" sessions are being discussed and pre-scheduled
 * Planning for the non-pre-scheduled tracks is about to start
 * 2016-03-30 / 2016-04-03 Jerusalem: Wikimedia Hackathon 2016

Documentation

 * New draft: Gadgets 2.0.

Outreach

 * Google Code-in 2015 started last Monday and will continue until 2016-01-27
 * Mentors and tasks are welcomed!
 * Open tasks
 * Outreachy round 11: community bonding completed for Easier categorization of pictures in Upload to Commons Android app (report)

Community health

 * Working together on the problem of online harassment in Wikimedia communities (Wikimedia blog)
 * Code of Conduct draft
 * The page about handling cases welcomes edits and feedback
 * Appeals
 * Removing detail in Code_of_Conduct/Draft#Responses_and_resolutions?

Project management

 * 2015 Community Wishlist Survey welcomes votes until Monday, December 14
 * Of Great Pyramids and agile software development: how and why we developed Phragile (Wikimedia blog)
 * Ideas for tech-related IdeaLab Campaigns?

Code review

 * Request for comment: Migrate code review and management to Phabricator from Gerrit.

Metrics

 * New metrics about downloads of extensions and skins via Extension Distributor

Gerrit
Key performance indicators


 * Median age of open changesets waiting for review: 49.3 days in November (was 39.3 in October, 63.8 a year ago)
 * MediaWiki core: 61.2 days (was 62, 80.5)


 * Number of open changesets waiting for review: 1175 (was 1097, 1098)
 * MediaWiki core: 239 (was 206, 266)


 * Number of new changesets submitted per month: 2369 (was 3367, 2863)
 * MediaWiki core: 531 (was 519, 524)


 * Number of code uploaders per month: 201 (was 211)
 * Number of code reviewers per month: 181 (was 192)
 * Number of code committers per month: 125 (was 131)

Code repositories with slowest code review:
 * 1) Wikistats: 535 days, 5 changesets
 * 2) BookManagerv2: 504 days, 19 changesets
 * 3) BayesianFilter: 416 days, 1 changeset
 * 4) TitleBlacklist: 367 days, 1 changeset
 * 5) Bootstrap: 341 days, 1 changeset

= Instructions =
 * In order to keep the email version in plaintext readable, add the links at the end of the text as full URLs. No words formatted as links, no internal links.

= Skeleton =

Don't add any information here, please.

YYYY-MM-DD
Help develop the next next summary.

DevRel focus
What keeps Developer Relations especially busy these days:



See below other activities in our radar.