Second iteration of the Technical Collaboration strategy
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	Qgil
	Apr 3 2016, 9:47 AM

Description

After T124021: Define the Technical Collaboration team strategy we have a first iteration of our team strategy at https://meta.wikimedia.org/wiki/Technical_Collaboration/Strategy

This strategy is the result of an eminently internal team discussion, design as such. Now we want to go through a second iteration based on feedback from our stakeholders and the teams we want to collaborate with.

Please leave your feedback at https://meta.wikimedia.org/wiki/Talk:Technical_Collaboration/Strategy -- this task is only for tracking purposes.

Related Objects
Search...

Status	Assigned	Task
Resolved	Qgil	T102790 Engineering Community quarterly review (as part of the Community Engagement review)
Resolved	Qgil	T93770 Engineering Community quarterly goals for April-June 2015
Resolved	• Rfarrand	T93584 Goal: Most welcoming and productive Wikimedia Hackathon
Resolved	Qgil	T153007 Technical Collaboration annual plan FY2017-18
Resolved	Keegan	T131689 Second iteration of the Technical Collaboration strategy
Resolved	Qgil	T108647 Two blog posts about Technical Collaboration's annual plan programs
Resolved	Qgil	T104343 Goal: Evolve Engineering Community team into Developer Relations team
Resolved	Qgil	T104385 Improvements to the Developer Relations plan
Declined	Qgil	T107438 Review the Engineering Community team workflows
		Unknown Object (Task)
Resolved	Qgil	T131687 A way for people interested in technical collaboration to stay in touch
Resolved	Qgil	T131471 WMF Technical Collaboration meet and greet
Resolved	Qgil	T144477 Onboard our new Developer Advocate
Resolved	Qgil	T137801 Hire a Developer Advocate for the Technical Collaboration team
Declined	None	T926 Engage with established technical communities
Declined	Qgil	T925 Connect Wikimedia groups, Google Developer Groups, and computer science university departments
Declined	Qgil	T76327 Promote GSoC and FOSS OPW in China
Declined	Qgil	T76328 Promote GSoC and FOSS OPW in Japan
Declined	• Drbug	T76326 Promote GSoC and FOSS OPW in Russia
Declined	Tgr	T89076 Promote GSoC and FOSS OPW in Hungary
Resolved	Qgil	T76325 Engage with established technical communities at the Wikimedia Hackathon 2015
Declined	AlexCella	T88274 Promote GSoC, FOSS OPW, and Wikimedia Hackathon in France
Resolved	• Deskana	T92272 Mobile Apps activities at the Wikimedia Hackathon 2015
Resolved	Lydia_Pintscher	T92270 Wikidata activities at the Wikimedia Hackathon 2015
Resolved	Lydia_Pintscher	T92505 Wikidata architecture review and feedback
Resolved	Qgil	T89392 Plan to bring newcomers to our hackathons and integrate them
Declined	Qgil	T94266 Goal: Collaboration with partners in events and outreach programs
Declined	Qgil	T96013 Identify Wikimedia's top technical partners
Resolved	Qgil	T97283 Plan to focus on the Developer audience
Resolved	bd808	T102079 Metrics about the use of the Wikimedia web APIs
Resolved	Tgr	T106457 Sample StatsD requests
Open	None	T108414 Load API request count and latency data from Hadoop to a dashboard
Resolved	ArielGlenn	T108417 stat1002 access for tgr
Resolved	bd808	T108618 Publish detailed Action API request information to Hadoop
Resolved	None	T114733 Determine proper encoding for structured log data sent to Kafka by MediaWiki
Resolved	Dzahn	T115548 Requesting access to analytics-privatedata-users for Bryan Davis
Resolved	bd808	T118592 Create user defined function to classify network origin of an IP address
Resolved	Joe	T125084 MediaWiki monolog doesn't handle Kafka failures gracefully
Resolved	Joe	T119637 Update HHVM package to recent release
Resolved	Joe	T129467 HHVM 3.12 has a race-condition when starting up
Resolved	JAllemandou	T129886 Create wmf_raw.ApiAction table
Resolved	Ottomata	T129889 Create mediawiki_ApiAction Kafka topic
Resolved	bd808	T113672 api.log does not indicate errors and exceptions
Resolved	bd808	T116065 Design aggregate tables to drive Action API reports
Open	None	T116658 Add Application errors for Mediawiki API to x-analytics
Declined	None	T122245 REST API entry point web request statistics at the Varnish level
Resolved	bd808	T132283 Determine which Action API parameters to whitelist/blacklist for action_param_hourly aggregate table
Open	None	T137321 Run ETL for wmf_raw.ActionApi into wmf.action_* aggregate tables
Declined	None	T154912 Is User-Agent data PII when associated with Action API requests?
Invalid	None	T85590 Maximize volunteer/staff engineer engagement in MediaWiki software projects
Resolved	Qgil	T116370 Community health survey for Wikimedia technical spaces
Declined	None	T85602 Reaching out to potential technical contributors among readers of Wikipedia et al
Declined	None	T85600 Who are the top 50 independent contributors and what do they need from the WMF?
Resolved	Aklapper	T64221 Key performance indicator: Top contributors: Find good Ranking algorithm fix bugs on page
Resolved	Lcanasdiaz	T117871 Many profiles on profile.html do not display identity's name though data is available
Resolved	Lcanasdiaz	T118169 Make GrimoireLib display one consistent name for one user
Resolved	Aklapper	T116285 Review/update mailing list repositories in korma
Resolved	Dicortazar	T56230 Tech metrics missing IRC channels
Declined	Aklapper	T125797 top-contributors.html is not sorted by rank anymore
Resolved	Lcanasdiaz	T123929 Mailing lists recently added to korma do not have "Top senders" data created (JSON file is 404)
Resolved	Lcanasdiaz	T128171 For some people, top-contributors.html displays three-digit numbers instead of names
Resolved	Lcanasdiaz	T129837 top-contributors.html only displays seven entries
Resolved	Aklapper	T112527 Correct affiliation for code review contributors of the past 30 days
Resolved	Aklapper	T132907 Fix incorrect mailing list activity of AKlapper (=Phabricator) in Technical Community Metrics user data
Resolved	Acs	T157898 Provide Hatstall to fix syncing / updating of identities on the wikimedia.biterg.io production instance
Resolved	Aklapper	T123643 Investigate why there is a mismatch between six names and certain email address in mediawiki-identities data
Resolved	Lcanasdiaz	T159229 "Email senders" widget empty though "Mailing Lists" widget states that there are email senders
Declined	None	T103057 Organize the participation of Wikimedia speakers in (non-Wikimedia) developer events
Declined	Qgil	T114082 Documenting thoughts on uptake of community software experiments
Resolved	bd808	T95155 Organize a (annual?) toollabs survey
Resolved	Qgil	T124021 Define the Technical Collaboration team strategy
Resolved	Lucie	T148598 Actions to grow the diversity of our technical community
Resolved	Qgil	T132499 Review KPIs, workflows, and scorecards of the Technical Collaboration team
Resolved	Aklapper	T160430 Have statistics which allow measuring success of a potential "Onboarding new developers" program
Resolved	Lcanasdiaz	T151161 Have "Last Attracted Developers" information for Gerrit automatically updated / Integrate new demography panels in GrimoireLab product
Declined	None	T156301 Create a developer documentation special interest group
Resolved	None	T164551 RfC: Adopt governance guidelines for Special Interest Groups (SIG)
Resolved	Quiddity	T174459 Community Liaison support for Cloud services SIG research

Event Timeline

Qgil created this task.Apr 3 2016, 9:47 AM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 3 2016, 9:47 AM

Qgil triaged this task as Low priority.Apr 3 2016, 9:49 AM

Qgil updated the task description. (Show Details)

Qgil mentioned this in T131471: WMF Technical Collaboration meet and greet.

Qgil added a subtask: T131471: WMF Technical Collaboration meet and greet.Apr 3 2016, 9:52 AM

Qgil moved this task from Backlog to Ready to Go on the Developer-Advocacy (Apr-Jun-2016) board.Apr 3 2016, 9:02 PM

Qgil moved this task from Backlog to Ready to Go on the Community-Relations-Support (Apr-Jun-2016) board.Apr 3 2016, 9:40 PM

• Elitre subscribed.Apr 13 2016, 2:35 PM

Qgil added a subtask: T108647: Two blog posts about Technical Collaboration's annual plan programs.Apr 25 2016, 9:30 AM

Qgil added a subtask: T926: Engage with established technical communities.Apr 26 2016, 7:29 AM

Qgil added a subtask: T85590: Maximize volunteer/staff engineer engagement in MediaWiki software projects.

Qgil added a subtask: T104286: Engage developer documentation task force.Apr 26 2016, 7:31 AM

Qgil added a subtask: T116370: Community health survey for Wikimedia technical spaces.

Qgil added a subtask: T85602: Reaching out to potential technical contributors among readers of Wikipedia et al.

Qgil added a subtask: T85600: Who are the top 50 independent contributors and what do they need from the WMF?.Apr 26 2016, 7:35 AM

Qgil added a subtask: T103057: Organize the participation of Wikimedia speakers in (non-Wikimedia) developer events.Apr 26 2016, 7:43 AM

Qgil added a subtask: T653: Refresh the mediawiki.org homepage.

Sorry for the noise with notifications. All these tasks are not actual blockers of the next strategy round, but ideas that we had over time that are all loose in our backlog, and that now could inform our strategy. And the other way around, a team strategy defined in more detail can help us determining the current relevance and priority of these tasks.

Qgil added a subtask: T114082: Documenting thoughts on uptake of community software experiments.Apr 29 2016, 12:02 PM

Qgil mentioned this in T114082: Documenting thoughts on uptake of community software experiments.Apr 29 2016, 12:13 PM

Qgil closed subtask T114082: Documenting thoughts on uptake of community software experiments as Declined.

Also relevant:

Qgil added a subtask: T95155: Organize a (annual?) toollabs survey.May 5 2016, 9:53 AM

I will not have time to focus on this task or its blockers during this month. I'm pushing it to the next quarter.

Qgil mentioned this in T131915: Technical Collaboration quarterly goals for July - September 2016.Jun 7 2016, 12:32 PM

Qgil added a subtask: T124021: Define the Technical Collaboration team strategy.Jun 7 2016, 12:50 PM

Qgil moved this task from Backlog to Ready to Go on the Developer-Advocacy (Jul-Sep-2016) board.Jul 5 2016, 9:06 PM

Qgil moved this task from Backlog to Ready to Go on the Community-Relations-Support (Jul-Sep-2016) board.Jul 7 2016, 9:24 PM

Qgil closed subtask T116370: Community health survey for Wikimedia technical spaces as Resolved.Aug 25 2016, 1:30 PM

At this point, I'd rather wait until the new developer advocate joins the team (T137801) with a fresh perspective.

Qgil added a subtask: T137801: Hire a Developer Advocate for the Technical Collaboration team.Aug 30 2016, 9:28 AM

Qgil closed subtask T137801: Hire a Developer Advocate for the Technical Collaboration team as Resolved.Sep 1 2016, 9:48 AM

Qgil edited subtasks, added: T144477: Onboard our new Developer Advocate; removed: T137801: Hire a Developer Advocate for the Technical Collaboration team.

On a second or third thought... The current version of the strategy is good enough to inform our next steps, and there is an upcoming Wikimedia Strategy starting on January 2017. This means that there will be enough strategic discussions from January onward, and we could sync the next iteration on our team strategy to that bigger process.

Qgil mentioned this in T926: Engage with established technical communities.Oct 5 2016, 8:28 PM

Qgil added a subtask: T148598: Actions to grow the diversity of our technical community.Oct 25 2016, 2:26 PM

Qgil mentioned this in T149372: MediaWiki Documentation.Nov 30 2016, 9:24 AM

Qgil closed subtask T144477: Onboard our new Developer Advocate as Resolved.Dec 19 2016, 8:30 PM

Qgil moved this task from Backlog to Ready to Go on the Developer-Advocacy (Jan-Mar-2017) board.Dec 20 2016, 2:46 PM

Qgil moved this task from Backlog to Ready to Go on the Community-Relations-Support (Jan-Mar 2017) board.Dec 20 2016, 2:53 PM

Qgil mentioned this in T150658: Technical Collaboration quarterly check in for January – March 2017.Dec 21 2016, 10:27 AM

Qgil added a parent task: T153007: Technical Collaboration annual plan FY2017-18.

Xephyr826 subscribed.Jan 24 2017, 12:12 AM

Aklapper changed the status of subtask T85600: Who are the top 50 independent contributors and what do they need from the WMF? from Open to Stalled.Feb 12 2017, 3:57 PM

Qgil mentioned this in T132499: Review KPIs, workflows, and scorecards of the Technical Collaboration team.Feb 20 2017, 10:21 AM

Qgil added a subtask: T132499: Review KPIs, workflows, and scorecards of the Technical Collaboration team.Feb 20 2017, 10:25 AM

Qgil edited subtasks, added: T156301: Create a developer documentation special interest group; removed: T104286: Engage developer documentation task force.Feb 20 2017, 10:27 AM

Quiddity subscribed.Mar 14 2017, 6:27 PM

Keegan claimed this task.Mar 14 2017, 7:13 PM

Keegan edited projects, added Community-Relations-Support (Apr-Jun 2017); removed Community-Relations-Support (Jan-Mar 2017).

@Keegan has volunteered to take this task. Thank you!

Qgil moved this task from Backlog to Ready to Go on the Developer-Advocacy (Apr-Jun 2017) board.Mar 27 2017, 10:28 AM

Qgil moved this task from Backlog to Ready to Go on the Community-Relations-Support (Apr-Jun 2017) board.Apr 19 2017, 3:11 PM

Qgil mentioned this in T163441: Technical Collaboration quarterly check in for April - June 2017.Apr 20 2017, 12:57 PM

Aklapper changed the status of subtask T85600: Who are the top 50 independent contributors and what do they need from the WMF? from Stalled to Open.May 10 2017, 2:23 PM

Qgil closed subtask T148598: Actions to grow the diversity of our technical community as Resolved.Jun 27 2017, 8:31 AM

Qgil closed subtask T132499: Review KPIs, workflows, and scorecards of the Technical Collaboration team as Resolved.Jun 27 2017, 8:37 AM

As I discussed with Quim, this task ended up stalled this quarter because of demands on the team's time. To do this properly, we need:

Everyone on the team read, know, and understand the current strategy
Everyone on the team take the time to develop their own thoughts on the subject before coming into the meeting
Everyone be available for the meeting

Not sure about everywhere else, but here that's quite the time commitment. I think we can do it last week of July, I'll start prepping the team when I get back from vacation.

Keegan edited projects, added Community-Relations-Support (Jul-Sep 2017), Developer-Advocacy (Jul-Sep 2017); removed Developer-Advocacy (Apr-Jun 2017), Community-Relations-Support (Apr-Jun 2017).Jun 30 2017, 5:00 PM

Qgil moved this task from Backlog to Ready to Go on the Developer-Advocacy (Jul-Sep 2017) board.Jul 11 2017, 9:38 PM

Maybe resetting to open reflects reality better? Internal review has happened.

In T131689#3516156, @Elitre wrote:

Maybe resetting to open reflects reality better? Internal review has happened.

This task is currently open, but stalled by time constraints.

Which internal review is this?

I think I mixed up tasks/concepts.

Keegan changed the task status from Stalled to Open.Sep 5 2017, 5:02 PM

Keegan raised the priority of this task from Low to Medium.

Qgil moved this task from August to September on the Community-Relations-Support (Jul-Sep 2017) board.Sep 5 2017, 8:07 PM

Qgil moved this task from Ready to Go to September on the Developer-Advocacy (Jul-Sep 2017) board.

Qgil closed subtask T926: Engage with established technical communities as Declined.Sep 12 2017, 9:57 AM

Aklapper closed subtask T85600: Who are the top 50 independent contributors and what do they need from the WMF? as Declined.Sep 12 2017, 1:06 PM

Members of the TC team met to discuss the team strategy, now that we're about 18 months into its existence. Notes are here: https://etherpad.wikimedia.org/p/tc_strategy_2017

Key points:

Overall, the team thinks the strategy has not changed in a significant way
Overall, the team is okay with the strategy page
The page needs updates to bring it into current WMF practices (remove PDP mentions, for example), remove jargon, provide nutshells and basic section summaries
Some of these updates have already been done, the rest can happen at any time.

Qgil awarded a token.Sep 15 2017, 8:44 AM

Qgil closed subtask T108647: Two blog posts about Technical Collaboration's annual plan programs as Resolved.Dec 7 2017, 11:58 AM

Xephyr826 closed subtask T156301: Create a developer documentation special interest group as Declined.Mar 17 2018, 9:32 PM

Aklapper removed a subtask: T653: Refresh the mediawiki.org homepage.Apr 14 2019, 12:13 AM

Aklapper closed subtask T85602: Reaching out to potential technical contributors among readers of Wikipedia et al as Declined.Aug 22 2019, 9:55 AM

Aklapper closed subtask T103057: Organize the participation of Wikimedia speakers in (non-Wikimedia) developer events as Declined.Sep 14 2019, 5:15 PM

Aklapper closed subtask T85590: Maximize volunteer/staff engineer engagement in MediaWiki software projects as Invalid.Oct 5 2020, 11:10 AM