2021-08-04 Meeting Notes

4 views
Skip to first unread message

Bob Killen

unread,
Aug 4, 2021, 7:59:42 PM8/4/21
to kubernetes-sig-contribex

Events:

  • Office hours [POP/Rawkode]
    • Seems to be going well?
  • Community Meeting [Laura]
    • August is going to be the release retro
    • There was another discussion about whether the community meeting is worth persisting with the current model. Do we want to discuss that here?
      • Biggest problem is updating people’s calendars
      • We can export k-dev now! So should make a managed account easier to avoid the API limits :) We’re working on that. Comms is now the big thing. We need to define a plan for cutover. Laura will talk with comms to figure that plan out.
  • Contributor Summit(s) [Bob]
    • Going well!
    • Reg form is live. Comms and Website updates are incoming
    • Original plan/idea is still being followed.
    • Next big decision: Where to host social
    • Separate meeting on Mondays (you will get the invite if you’re on the contribex mailing list--join to get it added, or ask in the Slack channel)
    • SIG meet and greet spaces are available on Wednesday at some point.
  • Steering Election [Josh]
    • SC Elections: need EC members (first step)
      • Normally 3-person election committee, all from different employers
      • Josh: tech implementation
        • Using Electo
      • ??: Voter management
        • Maintaining list
      • ??: Comms
        • Sending out messages
        • Will reach out to the marketing team and ask (note can’t be Broberg or Short because they work at the same company as Josh)
      • If you’re interested in joining the committee, let Josh and Bob know
  • Other/Discussion: 
    • N/A
Mentoring:
  • Meet Our Contributors [Paris]
    • Now have Streamyard :tada:
    • Still need calendars to get figured out, like with the community meeting
  • Playground, gsoc, outreachy, LFX Mentorship Program [Ihor]
  • New Contributor Workshop Course [Alison]
    • Good chat about everything on Monday
    • Potentially getting tech writers from budget from Google (yay help!)
    • Still need to set up page layout, then need to translate current stuff to guide format (currently in talks and slides format)
    • There are a bunch of open issues in GitHub (prefix: NCW2). Jump on in! Mentoring meeting is on the SIG Contribex calendar.
    • This upcoming Summit in North America isn’t running a New Contributor Workshop, as a side note (and likely won’t do one at KubeCon again due to low usefulness/amount of people actually sticking around. Seems to be better with local Meetups).
    • As a replacement, see SIG Meet & Greet above in the contributor summit section.
Community-management:
  • Need to Know Chairs/TLs email [Bob/Alison]
    • Several things on the docket:
      • Contributor Summit stuff
      • Steering election reminder
      • General discussion around making tech leads mandatory along with terms and term limits
      • K-dev migration! Send it to *everything*
        • We need to set a timeframe. Set it to after the steering election? But calendar issues are acute right now.
        • If we do it now, we would need to start comms right now and do the cutover in August
        • We’d do a straight cutover. And we can remove bouncing emails, thankfully.
        • Elections wouldn’t be too affected *other than* permissions on Google Docs.
        • Moderation queues would be a big deal to get started. Every single new person posting would need to be approved, which would be everyone on a new Google Group.
        • Need a minimum of 5-6 people
        • We’d also need to block posting to that list at some point to help move over to the new list.
        • Biggest thing is coordinating the comms. We’re migrating, and k-dev will be first.
        • We can create the list now and start moving over docs and all while still in the initial comms phase.
        • How about migrating sig-contribex first? Or having a starting list to move to catch things...
        • Note that this migration is the Google Workspace Automation issue on GitHub
        • We also can do it for any list; the person who exports the list has to have admin access to the list.
        • Offer: k8s-infra as a guinea pig. Especially since the working group is becoming a SIG.
        • TODO: Recruit Team
        • TODO: Draft comms
        • TODO: Test with k8s-infra/contribex
        • TODO: Consolidate to one GitHub issue
Devstats [Lauri]
  • No updates
Marketing [Matt/Kaslin]
  • Discussion/Update
  • Quite a bit of work coming up!
  • Lots of asks moved over to the marketing agenda (thanks, Kaslin!)
  • Couple of articles in progress (SIG-Node and Contributor Summit)
  • Comms for registration and contributor summit stuff
  • Bart Farrell is doing great work with a video series from contributors
  • If you need help, ping the group at contributor-comms on Slack, join the meetings, or ping Kaslin!
Contributor-documentation:
  • Contributor Guide [Bob]
    • No updates
  • Developer Guide [Erik/Joel]
    • No updates
  • Contributor Site [Bob]
    • No updates
GitHub-management [Bob/Nikhita/Christoph]:
  • EasyCLA Migration
    • Biggest thing. We still want to try for next week, but the PR to add the support to the CI is still open. Has not been tested yet. A lot of back and forth going on.
  • Recently, there are a lot of good first issues, but a lot of people aren’t giving enough context to make them good first issues. So a lot of people who pick up an issue are stuck and need help. Madhav has been trying to help and pinging authors for context. Has there been any discussion to have better prompts or otherwise encourage better context on the good-first-issue labels (versus just tagging it and not having enough context)?
    • Not really yet, but good question.
    • Anyone can tag. Probably would be good to send a reminder out.
    • Probably no better way to do it than the one at a time situation, unfortunately. The original author or someone with strong knowledge of the code needs to do it.
    • If you do it, feel free to note that you’re doing it on behalf of SIG Contributor Experience. And feel free to add the context if you already know. Be sure to ping on GitHub and Slack both.
    • What about a good-first-issue template? Checklists and everything. Might be hard to create across all of the repos, but yes
    • Note that a lot of issues start out as regular issues and then get flagged later.
    • A comment from a bot would probably help.
    • Contributor comms would be helpful here, too :) Kaslin added to the marketing agenda
Slack-infra [Jeefy]:
  • Discussion/Update
    • Huddles are awful. The end.
    • Josh disabled a bunch and is working through them all.
Open Mic/Discussion
  • [arnaud] domain validation for Search Console.
    • Last year, we were talking about this. Did we do this, or is it still needed?
    • Project was to improve the SEO of the .io website.
    • Arnaud has access to the console now (yay)
    • ~Probably need to reach out to docs~
    • We actually mean the shortcut links, so ignore some of the above comments. We’re talking about k8s.io
    • There is a problem here since we use so many short links
    • We can add text records in the management stuff.
    • Arnaud’s got this :) No big rush, though.
Reply all
Reply to author
Forward
0 new messages