[go: nahoru, domu]

Page MenuHomePhabricator

Finalize CL toolkit within Product development
Closed, DuplicatePublic

Description

Current process proposal for product development is here.

Most recent draft is here.

Related Objects

StatusSubtypeAssignedTask
DuplicateNone
DuplicateNone
DuplicateQgil
Resolved Elitre
Resolved Elitre
DeclinedNone
DeclinedKeegan
ResolvedKeegan
DeclinedNone
ResolvedPginer-WMF
ResolvedKeegan
DeclinedNone
Resolved Moushira
Resolved Elitre
DeclinedNone
ResolvedQgil
ResolvedKeegan
ResolvedKeegan
Resolved Elitre
Resolved Moushira

Event Timeline

Rdicerb raised the priority of this task from to Needs Triage.
Rdicerb updated the task description. (Show Details)
Rdicerb moved this task to Dec on the Community-Relations-Support board.
Rdicerb subscribed.
Rdicerb added a parent task: Unknown Object (Task).Nov 4 2015, 11:11 PM

Is there more information about this task? Like a definition of the CL toolkit, the problems it aims to solve, and the current status of this work.

Qgil mentioned this in Unknown Object (Task).Dec 1 2015, 8:35 AM
Qgil mentioned this in Unknown Object (Task).Dec 1 2015, 9:22 AM

Current thinking: this looks more like an instruction manual than a toolkit.

Qgil removed Rdicerb as the assignee of this task.EditedMay 10 2016, 10:48 AM

We need to refocus this task. I think the work done by @Rdicerb is useful, but currently this task lacks a bit its north and its short term use. Here is one idea.

Currently we are working on the Technical Collaboration Guideline, which consists on a set of recommendations.

What if... we would compile a Technical Collaboration Toolkit, where we would document instructions and best practices to actually run the processes recommended in the Guideline?

Real examples:

  • Developer team has a new feature ready to be deployed in projects, but they need help from local volunteers to translate X to their language. How to reach out to volunteers?
  • Developer team has a feature in Beta and they are thinking of graduating it. How to organize a simple consultation to identify potential blockers by the communities?
Qgil lowered the priority of this task from High to Medium.May 10 2016, 10:48 AM
Qgil added subscribers: Keegan, Elitre.

What if... we would compile a Technical Collaboration Toolkit, where we would document instructions and best practices to actually run the processes recommended in the Guideline?

After a conversation with @Keegan, we agree that the TCG would improve with links to howtos and examples, but that doesn't need to become a formal collection of docs as I was initially proposing.

I am lowering the priority of this task while we clarify the blockers.

Real examples:

  • Developer team has a new feature ready to be deployed in projects, but they need help from local volunteers to translate X to their language. How to reach out to volunteers?
  • Developer team has a feature in Beta and they are thinking of graduating it. How to organize a simple consultation to identify potential blockers by the communities?

Looking at https://meta.wikimedia.org/wiki/User:Rdicerb_%28WMF%29/sandbox/CL_Toolkit#Definition_of_CL_Toolkit:, the CL toolkit is defined as

The different tools/functions used by Community Liaisons to engage communities in product development. These can be a type of communication or engagement, whether. Ideally each toolkit specifies individual steps in a workflow.

Nowadays this is the role of the Technical-Collaboration-Guidance and a lot of work is going on there. I am reflecting this evolution in our plans by merging this task to T138339: Create a systematic approach to community engagement for product development teams.