Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Communication & Collaboration Platform Sprawl Assessment #2466

Closed
parispittman opened this issue Aug 3, 2018 · 16 comments
Closed

Communication & Collaboration Platform Sprawl Assessment #2466

parispittman opened this issue Aug 3, 2018 · 16 comments
Assignees
Labels
area/community-management good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience.

Comments

@parispittman
Copy link
Contributor

parispittman commented Aug 3, 2018

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.

@parispittman parispittman added the sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. label Aug 3, 2018
@parispittman parispittman self-assigned this Aug 3, 2018
@spiffxp
Copy link
Member

spiffxp commented Aug 3, 2018

/area community-management

@parispittman parispittman added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Aug 10, 2018
@parispittman
Copy link
Contributor Author

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

@parispittman
Copy link
Contributor Author

/good-first-issue

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

@k8s-ci-robot
Copy link
Contributor

@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 k8s-ci-robot added the good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. label Aug 14, 2018
@parispittman parispittman added this to Backlog in Contributor Experience via automation Aug 22, 2018
@parispittman parispittman moved this from Backlog to In Progress in Contributor Experience Aug 23, 2018
@ameukam
Copy link
Member

ameukam commented Sep 5, 2018

@parispittman can i be a volunteer?

@parispittman parispittman moved this from In Progress to Blocked in Contributor Experience Sep 6, 2018
@parispittman
Copy link
Contributor Author

@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
Copy link
Contributor Author

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

@parispittman
Copy link
Contributor Author

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
Copy link
Contributor Author

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
Copy link
Contributor Author

@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
Copy link
Contributor Author

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.

@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 7, 2019
@mrbobbytables
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 7, 2019
@Phillels Phillels moved this from In Progress to Blocked in Contributor Experience Mar 6, 2019
@nikhita nikhita removed this from Blocked in Contributor Experience Mar 20, 2019
@parispittman
Copy link
Contributor Author

inventory is complete and linked above. survey went out and results are here

Blog post is starting-> https://docs.google.com/document/d/1U6tgPVsOVlDcsxCSXz7lBFyQc8KIdglTRrk2uuf-PG0/edit?usp=sharing

@parispittman
Copy link
Contributor Author

/close

@k8s-ci-robot
Copy link
Contributor

@parispittman: Closing this issue.

In response to this:

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/community-management good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience.
Development

No branches or pull requests

6 participants