GitLab Core Team meeting - July 2020

TL;DR

The core team discusses updates on the Advisory Council, proposes renaming "Contribute for Prize" to "Community Challenge," and considers the issue of the Slack workspace and potentially creating a separate public instance.

Transcript

okay welcome to the july edition of the core team meeting hopefully uh everybody's having a good summer so far uh let me advance the slide uh yeah i don't think there were any new suggestions for the agenda topic that was on the issue so we'll go over mostly three things uh uh david's gonna give us an update on the advisory council discussion we've... Read More

Key Insights

• 😚 Closing the Community Advisory Council is being considered due to potential stress and media exposure.
• 🛄 Renaming "Contribute for Prize" to "Community Challenge" aims to emphasize the importance of continuous community involvement.
• 🪡 The limitations of the Slack workspace, such as unequal access to channels, highlight the need for a solution that promotes better communication and inclusivity.

Questions & Answers

Q: Why is the core team considering closing the Community Advisory Council?

The team is concerned about the potential stress and media exposure that members may face, given past controversial discussions. They propose finding an alternative process to gather proactive feedback when needed.

Q: What is the proposed change to "Contribute for Prize"?

The team suggests renaming it to "Community Challenge" to shift the focus from the prize to the importance of encouraging community members to work on specific issues throughout the year.

Q: What are the limitations of the current Slack workspace?

There are unequal access levels to channels, leading to issues with communication and accessing necessary information. The team is exploring options, including potentially creating a separate public Slack instance.

Q: Are there concerns about opening a public Slack instance?

Yes, there are concerns about potential noise, spam, and unrelated questions from the community. Moderation would be necessary, as well as clear guidelines for gitlab team members regarding what can be posted publicly.

Key Insights:

• Closing the Community Advisory Council is being considered due to potential stress and media exposure.
• Renaming "Contribute for Prize" to "Community Challenge" aims to emphasize the importance of continuous community involvement.
• The limitations of the Slack workspace, such as unequal access to channels, highlight the need for a solution that promotes better communication and inclusivity.
• Creating a separate public Slack instance may help bridge the gap between the community and gitlab team members, but careful moderation and guidelines would be necessary.

Summary & Key Takeaways

• The core team discusses the possibility of closing the Community Advisory Council due to potential stress and media exposure for its members.

• They propose renaming "Contribute for Prize" to "Community Challenge" to emphasize the importance of working on specific issues throughout the year.

• The team discusses the limitations and concerns surrounding the Slack workspace, including unequal access to channels and the idea of creating a separate public instance.