You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi everyone,
Lately, we have received a number of inquiries about how to start a new interest collection (industry group, group of customers, etc) on this site. There are a number of complexities to the decision to launch a collection, which can be thought of as a type of “micro-community”. These are largely the same things that community managers think through when considering whether to start a new "macro-community" (or even language community) as well.
Seemingly, number 1 and number 2 are at odds with each other - we say that decisions shouldn’t be driven by the loudest voices, but also say that there should be people willing to take the lead. And they’re both correct.
Different communities handle this different ways. We’re still trying to figure out the best system to design that meets all of these requirements, and I want to ask our Community Advisory Board to weigh in on this important question as well.
So, for now, I’m putting into place an interim process for documenting the desire for new interest communities. (Marketplace vendors, we’re aware of your interest in collections for your apps, and we’re figuring out how to scale that up as well.)
Thank you!
pb