Strategy/Wikimedia movement/2018-20/Working Groups/Community Health/Minutes/2018-03-18

From Meta, a Wikimedia project coordination wiki

Discussion focused on the monthly Steering Group meeting update, Wikimedia Summit Preparations and the Scoping feedback

1. Summary of the Steering Committee meeting

Community Health members (Pavan, Philip) took part in the Steering Group meeting for all Working Group coordinators where next steps after scoping were shared: the Working Groups will energise, synchronize with other groups other, review the published scoping documents, and prepare for the Wikimedia Summit.

The Core Team offered to publish all WG calls’ summaries on Meta, and take this task off of the Working Group’s plate. Summaries will be created and share with the WG up to 48 hours after the call. If the CT does not hear any request for correction, deletion or any other kind of veto after 24 hours, the Core Team will publish the summaries.

2. WMSummit 2019 (schedule, plans and preparation)

Among activities that can be done before the Wikimedia Summit, Community Health Working Group is invited to determine linkages, overlaps, and liaisons, with other Working Groups and identify materials, glossaries, or any reading materials they would like to share with the  participants at the Wikimedia Summit.

  • Working Group members who have been selected by the group Working Group to represent the group at the summit are asked to attend all WG and plenary sessions in that role. Members who are representing their affiliates are encouraged to find a balance on which sessions to attend, but the schedule of the Summit will mostly avoid conflicting sessions anyway.
  • The Group has been encouraged to keep the two non-present members informed via email about important issues that come up at the summit.
  • There might be a need for Working Group members who are attending Summit to take decisions like inviting someone into Working group or giving away key questions from scoping documents based if decided to be in the scope of other WGs. The Core Team asked the group to request those who will not attend to give the group a mandate to take decisions at the event. (Action item for Pavan, done already)
  • WGs are asked to ensure that all important questions and results of their sessions are documented on sticky notes, flipcharts, or online. Content on paper will be digitised by support staff, harvesting at the plenary sessions will be organised by the design and facilitation team.
  • After the Summit, feedback from the summit participants and from the community conversations will be incorporated by the WGs into the final versions of the scoping documents.
    • Community conversations will already start this week, and will include channels like meta, different language wikis, a survey (also for anonymous feedback), facebook or telegram groups.
    • The Core Team will work with the CH group to see if it would make sense to design – aside from the general survey with 3 questions per WG – an additional survey focused only on community health. The results can then feed into the WG’s analysis.  

3. Feedback gathered about our scoping document (if any)

A Wikimedia Summit India session was held on 16-17 March to have people understand and provide feedback to the scoping documents, these were the responses;

  • The scoping terminology seemed hard for small communities to understand.
  • Suggestions might not be the real solutions to challenges, since they are answered by local communities.
  • The programmatic changes might happen before the structural changes.

These responses were expected from the community, and considered as helpful, which is the reason for having community liaisons to organise and get community feedback.