Here we organize the work required to implement the #community-liaisons tasks supporting [[ https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Community_Engagement#Program_11:_Community_collaboration_in_product_development | Wikimedia Foundation Annual Plan FY2017-18 - Community Engagement - Program 11 Community collaboration in product development ]] (some parts not related to CL support have been removed):
> The goal is to increase the awareness and participation of Wikimedia communities in our product development projects. A higher quantity and diversity of participation through our planning and development process will result in a better common understanding, a better collaboration, and better products.
> A requirement to achieve this goal is to offer to our communities a simple and predictable way to stay informed about and to participate in our product development projects. For this, our current reliance on CL support will be increasingly complemented by harmonization of community engagement practices across Product and Technology teams.
> This shift will be based in these principles:
> * CLs will continue to be regularly involved in product planning, having resident specialists appointed to the different areas.
> * CLs will be directly involved in the most complex goals and tasks, as agreed on a regular basis with Product and Technology product owners.
> * All projects will take the TCG as a set of base recommendations to be adapted to their specific needs and circumstance
> * Outcome 1: P&T's most strategic goals get full support by CLs;
> ** Communities are a real partner, members are satisfied, more interested in technical collaboration activities and even proactive.
> ** Lack of community involvement and satisfaction is no longer a factor preventing smooth rollouts and goals' achievement;
> * Outcome 2: CL support scales better across Product and Technology, also in projects without CLs directly assigned, and by having information necessary to successfully do basic community outreach all Product and Technology teams will more easily be able to update communities directly on lightweight communications that do not require CL intervention.
> * Objective 2: Develop internal processes (for example, a protocol to request CL support) to clarify terms of engagement, roles and responsibilities, and for a smarter triage of incoming requests.
> * Target 1: CL coverage:
> ** At least one resident CL is allocated in every Product audience team, involved in product planning activities.
> ** Product and Technology management teams have one CL assigned each, involved in relevant planning activities.
> ** 100% of Product and Technology goals involving CL support developed through these co-planning activities are resourced.
> ** Beyond team goals, 100% of support requests submitted to CL by Product or Technology receive a response within a week.
> ** Beyond team goals, 80% of support requests accepted are resourced within three months.
> Zero unanticipated clashes with the communities related to goals or tasks where CL support has been committed, or where TCG best practices have been followed by the Foundation teams. CL will ensure that development teams are aware of potential and emerging points of conflict.
> At least three wiki projects requesting beta features and early deployments (where applicable).
> Top 25 wiki projects in terms of active contributors have at least one active tech ambassadors and one translator identified (could be the same person).
> * Target 2: Degree of satisfaction of teams receiving CL support or using TCG documentation is recorded via surveys and/or interviews as “Very satisfied”.
> * Target 3: Major community collaborations are rated as "good" by volunteers through surveys, to verify whether TCG expectations on best practices were met.