Skip to content

Community Team Meeting Minutes

Jump to bottom
Christian Luhmann edited this page Jan 6, 2022 · 7 revisions

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