@nejch Thanks for tagging me on this issue!

We too were evaluating several options when we migrated, but we inherited the Community Discord from a community member who had started it up some time before. We took this as an opportunity to experiment which so far has been successful. We've seen a significant uptick in our engagement and activity on Discord. We've also significantly grown membership on the Discord over the last few months.

We have several regular events in our Discord server too, including weekly contributor pairing sessions. Would love to see if we could feature python-gitlab in any of these.

One of the concerns I read about in the article you linked above was the ability to link someone to another channel/community. In our case, the more of the wider GitLab community we can host in one space, the greater the ability for us to crosslink between those.

I'd love to grow our Discord to be one for the entire GitLab community - not just those using and building GitLab itself, but also those using/building the greater ecosystem of tooling around GitLab.

To answer your questions about migration:

We have recently collapsed the GitLab Terraform Provider and GitLab Cloud Seed discord servers into ours. Something to bear in mind, though, is that these migrations haven't brought any history over.
We have similarly moved our active focus from GitLab's Gitter channels into our discord. Those channels remain present, but we're regularly messaging in them to ensure the community knows where to find us. Again, with this there was no history migration, but simply a refocus of our efforts to where there was more activity.

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions