Skip to content

Community Team Meeting Minutes

Jump to bottom
Christian Luhmann edited this page Mar 25, 2022 · 7 revisions

2022 March 25

ToDos from last time

Agenda & Notes

  • GOVERNANCE.md edits

  • Discourse Questions

    • Adding categories
      • only Admin, Community Team
    • Delete other peoples posts
      • only Admin, Community Team
    • Moving posts between categories
      • only Admin, Community Team, PyMC Core Team
    • Who can edit other people’s posts
      • Admin, Community Team, PyMC Core Team
    • Pinning posts
      • Admin, Community Team, PyMC Core Team
    • Announcements
      • Only Admin, Community Team, PyMC Core Team can post a new topic
      • Any person can add an new post to an existing topic
      • Subscribe by default for everyone
    • Tags who can add?
      • People in Trust Level 4 can add tags (users)
        • Make a more precise proposal
        • And if they answer things
      • Everyone in PyMC Team can edit tags
    • Who can edit posts?

  • Office hours?

    • Debrief from last time
      • Do NOT post to twitter
    • technical side (platform?)
    • Schedule going forward?
      • discuss on slack, ad hoc meets are possible, keep momentum

  • Status of v4 when answering questions (i.e., when do/don’t we recommend the beta?)

    • bring up at general meeting

  • Anything else going on to be aware of?

  • PyMCon 2022 https://docs.google.com/document/d/19jWCd4OmwTksdIuLP7K6RWSCLepPQcdj4SB5cWfIASM/edit#

2022 February 4

Agenda

  • Welcome Martin Ingram 🎉
  • Finish the team goals (plus update/fix the description and name in the governance)
  • Discourse
    • tags/topics
    • labeling questions as "solved"
    • how to ask a question
  • Office hours?
    • pre-sprint?
    • post-sprint?
    • ongoing?
    • technical side (platform?)
  • Feedback on the website? https://pymc-devs.github.io/pymc.io/
  • PyMCon 2022?

Notes

  • Governance document needs to be updated with the name of community team (currently refers to the "discourse" team) and the team mission
  • On discourse will begin to try and "nudge" towards marking solved topics as solved. If it is clearly solved, then feel free to go in and mark it. If it's unclear, we can ask.
  • Christian has started a "how to ask a question" document. Ultimately it can go in documentation under community.
  • We may be able to insert the how to ask a question link and other related information into the template discourse users see when creating a new topic (need to investigate).
  • With v4 coming, we may need a way to distinguish v3 vs. v4 discourse topics. Sub-categories? Just tags?
  • PyMCon 2022 planning to begin "next month"? So March? Check in with Ravin.
  • Office hours
    • Data umbrella often uses office hours to facilitate sprints
    • Pre-sprint (1 hour): answer questions if users have already tried some of the initial contribution steps (e.g., the sprint cheat sheet)
    • Post-sprint (1-hour): deal with open PRs, reviews, helping to finishing up/follow up, etc.
    • Pre-sprint office hours should be 1 week before sprint (next week)
    • Post-sprint office hours should be 1 week after sprint (otherwise it collides with other team meetings)
    • Poll to make sure people can staff office hours
    • After the sprint, we will try out recurring office hours
    • To retain momentum coming out of the sprint, we can keep the office hours contribution-focused in the short-term
    • After that we can broaden to other topics
    • e.g., we can have someone(s) give brief presentation(s) then open to Q&A
    • We could also have nominal topics for each meeting (e.g., time series, GPs, etc.) though we wouldn't have to stick to them if people have other things they want to discuss.

ToDos

  • Update governance document
  • Poll re: staffing of pre-/post- office hours
  • Explore discourse custom topic templates
  • Leftovers from last meeting
    • Initiate asynchronous discussion about 1 vs. 2 communities
    • Start a document about improving discourse management (Ravin)

2022 January 6

Agenda

  • What is the community team?
    • Discourse
    • What else?
    • PyMCon?
  • StackOverflow?
  • PyMCon
  • Discourse
    • Help desk (current discourse activity)
    • Recurring events/activities?
      • More entries in the "Sharing" topic (e.g., blog/notebook posts/discussions/breakdowns?)
      • Q&As?
  • Paid Discourse account?
  • Team procedures
    • Delegation of discourse questions to team members?
    • Elevation of discourse questions to github issues?
    • "sub-optimal" questions (see this pymc-examples issue)

Notes

  • What is the Community Team?
    • mission = grow the community
    • also "marketing" of pymc (e.g., twitter)
    • PyMCon seems like a community-related activity even if it involves people beyond the community team
    • The community team is primarily focused on discourse and answering user questions there
    • Community team is responsible for making sure discourse is functional, but isn't exclusively answering questions (others can answer questions, and team members have other responsibilities)
    • Get energy/momentum infused into the community generally and discourse specifically (e.g., get the community pitching in to answer questions, discuss, etc.)
    • Short-term goal seems to be to get discourse management "in order" (i.e., efficient)
    • Longer-term goals can incorporate other spaces and wider community
  • Improving the efficiency of discourse management:
    • We should probably start utilizing discourse tags/labels more/more optimally (e.g., liberally assign tags to posts)
    • first priority is that ever Q gets some sort of response (even if it's tagging someone)
    • tag/delegate questions to team members
  • Do we want one community or two?
    • Two is roughly developers and users
    • One is everyone
    • The answer to this question influences lots of other choices (e.g., do we use github discussions for development-related discussion or do we use discourse?)
    • Having the community see more developer "presence" on discourse might be good
    • github issues are sometimes more appropriate for discourse and certainly vice versa

ToDos

  • Solidify mission statement
  • Initiate asynchronous discussion about 1 vs. 2 communities
  • Start a document about improving discourse management (Ravin)

Relevant docs:

Clone this wiki locally