Page MenuHomePhabricator
Create Task
Maniphest T97283

Plan to focus on the Developer audience
Closed, ResolvedPublic
Actions

Description

The Wikimedia Foundation Engineering reorganization addresses several core audiences, but there is one that still needs a plan: developers. We need to plan the developer offering we envision for developers, and the team required to support them.

A quote that we shouldn't forget. Pasting it here for now:

What do we know about the developer community today? What do we know about their needs? What do we know about users of community-developed products/tools? Do we know how individuals work with each other to develop products? Basically, I'm wondering what kind of research do you need about the developer community to successfully move this project forward.

Related Objects
Search...

StatusSubtypeAssignedTask
 ResolvedQgilT153007 Technical Collaboration annual plan FY2017-18
 ResolvedKeeganT131689 Second iteration of the Technical Collaboration strategy
 DeclinedNoneT926 Engage with established technical communities
 ResolvedQgilT102790 Engineering Community quarterly review (as part of the Community Engagement review)
 ResolvedQgilT93770 Engineering Community quarterly goals for April-June 2015
 InvalidNoneT98348 Implement the Wikimedia Foundation Call to Action 2015
 InvalidNoneT98359 Create spaces for future community-led innovations and new knowledge creation
 ResolvedNoneT98361 Strengthen partnerships with organizations that use or contribute free content, or are aligned with the WMF in the free-knowledge movement
 DeclinedQgilT96013 Identify Wikimedia's top technical partners
 ResolvedQgilT97283 Plan to focus on the Developer audience
 Resolvedbd808T102079 Metrics about the use of the Wikimedia web APIs
 ResolvedTgrT106457 Sample StatsD requests
 OpenNoneT108414 Load API request count and latency data from Hadoop to a dashboard
 ResolvedArielGlennT108417 stat1002 access for tgr
 Resolvedbd808T108618 Publish detailed Action API request information to Hadoop
 ResolvedNoneT114733 Determine proper encoding for structured log data sent to Kafka by MediaWiki
 ResolvedDzahnT115548 Requesting access to analytics-privatedata-users for Bryan Davis
 Resolvedbd808T118592 Create user defined function to classify network origin of an IP address
 ResolvedJoeT125084 MediaWiki monolog doesn't handle Kafka failures gracefully
 ResolvedJoeT119637 Update HHVM package to recent release
 ResolvedJoeT129467 HHVM 3.12 has a race-condition when starting up
 ResolvedJAllemandouT129886 Create wmf_raw.ApiAction table
 ResolvedOttomataT129889 Create mediawiki_ApiAction Kafka topic
 Resolvedbd808T113672 api.log does not indicate errors and exceptions
 Resolvedbd808T116065 Design aggregate tables to drive Action API reports
 OpenNoneT116658 Add Application errors for Mediawiki API to x-analytics
DeclinedNoneT122245 REST API entry point web request statistics at the Varnish level
 Resolvedbd808T132283 Determine which Action API parameters to whitelist/blacklist for action_param_hourly aggregate table
 OpenNoneT137321 Run ETL for wmf_raw.ActionApi into wmf.action_* aggregate tables
 DeclinedNoneT154912 Is User-Agent data PII when associated with Action API requests?

Event Timeline

Qgil created this task.Apr 27 2015, 11:45 AM
Qgil claimed this task.
Qgil raised the priority of this task from to Medium.
Qgil updated the task description. (Show Details)
Qgil added a project: Developer-Advocacy.
Qgil subscribed.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 27 2015, 11:45 AM
Qgil added a project: ECT-May-2015.Apr 27 2015, 11:46 AM
Qgil added a parent task: T96013: Identify Wikimedia's top technical partners.Apr 29 2015, 1:54 PM
Qgil mentioned this in T96013: Identify Wikimedia's top technical partners.Apr 29 2015, 1:58 PM
Qgil mentioned this in T93770: Engineering Community quarterly goals for April-June 2015.Apr 29 2015, 3:19 PM
Qgil moved this task from Backlog to Doing on the ECT-May-2015 board.May 5 2015, 4:32 PM
Qgil raised the priority of this task from Medium to High.May 6 2015, 5:35 AM
Qgil mentioned this in T308: A single Developer Hub plan agreed and documented.May 21 2015, 8:32 AM
Daniel_Mietchen subscribed.May 27 2015, 11:56 AM
Qgil added a project: ECT-June-2015.May 29 2015, 7:26 AM
Qgil mentioned this in T101100: Engineering Community quarterly goals for July-September 2015.Jun 3 2015, 7:23 AM
Qgil added a subtask: T102079: Metrics about the use of the Wikimedia web APIs.Jun 11 2015, 6:35 AM
Qgil added a parent task: T93770: Engineering Community quarterly goals for April-June 2015.Jun 18 2015, 8:57 AM
Qgil added a parent task: T98359: Create spaces for future community-led innovations and new knowledge creation.Jun 18 2015, 9:00 AM
Qgil added a parent task: T98361: Strengthen partnerships with organizations that use or contribute free content, or are aligned with the WMF in the free-knowledge movement.
Qgil moved this task from Backlog to Doing on the ECT-June-2015 board.Jun 18 2015, 9:04 AM
Qgil updated the task description. (Show Details)Jun 18 2015, 9:05 PM
Qgil set Security to None.
• egalvezwmf subscribed.Jun 19 2015, 3:16 PM
Ricordisamoa subscribed.Jun 29 2015, 9:04 PM
Qgil closed this task as Resolved.Jun 29 2015, 9:39 PM

The plan has been published at https://www.mediawiki.org/wiki/Engineering_Community_Team/Developer_Relations_team

Announced in wikitech-l: https://lists.wikimedia.org/pipermail/wikitech-l/2015-June/082255.html

The implementation of this plan (probably fine tuned with the feedback received) will be one of my individual goals in the next quarter.

Resolving.

• BGerstle-WMF subscribed.Jun 30 2015, 5:30 PM

@Qgil very exciting! Is there any talk on how internal API users (e.g. Wikimedia app teams) can help with this?

• BGerstle-WMF added a comment.Jun 30 2015, 5:30 PM

@Qgil very exciting! Is there any talk on how internal API users (e.g. Wikimedia app teams) can help with this?

Qgil mentioned this in T104343: Goal: Evolve Engineering Community team into Developer Relations team.Jun 30 2015, 10:17 PM
• Spage subscribed.Aug 3 2015, 8:56 PM
In T97283#1414471, @BGerstle-WMF wrote:

@Qgil very exciting! Is there any talk on how internal API users (e.g. Wikimedia app teams) can help with this?

  • write cool features using the API and encourage showcase articles about them
  • or just share your pain points with the API
  • you can add the project Web-APIs-Hub to relevant phab tasks, though often the task will get closed before the information gets out

https://www.mediawiki.org/wiki/Web_APIs_hub/Contributing has more details.

• BGerstle-WMF added a comment.Aug 3 2015, 8:58 PM

@Spage k, thanks! will ping you if anything worthwhile gets picked up

bd808 closed subtask T102079: Metrics about the use of the Wikimedia web APIs as Resolved.Apr 2 2020, 5:12 PM
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL