Community: Communication & Collaboration Platform Sprawl Assessment

Created on 4 Aug 2018 · 16Comments · Source: kubernetes/community

We've discussed the sprawl of kubernetes communication and collaboration platforms on several different mediums as being a problem for the community with pushing messaging and participating in conversations. Contribex has begun making small improvements that are low hanging fruit but in order to make larger more impactful change we need the following to continue:

1- Identify current state / inventory of all communication and collaboration platforms
This includes all platforms listed on communication.md and others. This will identify owners, audience/reach, engagement, etc. Also, will identify collaboration platforms and owners of calendar invites from sig meetings, etc. so we can potentially centralize those services.

2- Survey contributors to see what is working and what isn't for them according to their preferences. Granted we will not be able to appease everyone and meet them where they are but we can identify trends and problematic spaces for us.

From there, we can formally identify the gaps, research solutions, and make decisions. I'll continue to set issues to break down the work and will close this issue after the inventory and survey are complete.

The above docs can be accessed if you are a member of the contributor experience mailing list. They are work in progress and would very much appreciate comments/contributions.

arecommunity-management good first issue help wanted sicontributor-experience

Source

parispittman

👍6

All 16 comments

/area community-management

spiffxp on 4 Aug 2018

😄1

update - survey has been drafted and will go through review cycles this week on the ML and Weds update meeting.

parispittman on 14 Aug 2018

/good-first-issue

putting the good first issue label on. i will happily guide someone through the exercise for #1.

parispittman on 14 Aug 2018

@parispittman:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

putting the good first issue label on. i will happily guide someone through the exercise for #1.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

k8s-ci-robot on 14 Aug 2018

@parispittman can i be a volunteer?

ameukam on 5 Sep 2018

@ameukam most definitely. want to chat with me on k8s slack and we can either have a meeting there or get on a call? (slack id: paris)

parispittman on 6 Sep 2018

Update: survey was sent out on Tuesday (sept 11) and will be live for two weeks.

parispittman on 12 Sep 2018

Artifacts to come from this:

-an enhanced communication.md with complete roadmap of our channels, audience, owners, where/how/why to post

-either an addendum to the above, our mod guidelines, or completely separate doc on comms behavior (ie- GitHub etiquette, only @here in Slack for $reason, etc.)

parispittman on 12 Sep 2018

Update: survey data is in. In progress of awarding all swag to those who submitted an email address and then sanitizing the data for publicly posting it.

parispittman on 3 Oct 2018

@ameukam and I would love more help for the first listed task if you are reading this and would like to get more involved (or want to see this issue progress further)

parispittman on 3 Oct 2018

👍1

update: all 68 respondents who left their email have been sent codes for water bottles. 🎉 thanks again!

data sanitizing is done; preparing survey sheet for data fun. will post publicly in the contribex folder in the k/community repo.

the inventory and discovery doc can use some more eyes and hands. feel free to jump in for columns with green.

parispittman on 9 Oct 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale