It might be about time to refresh <#C018Q3T30LW|>,...
# administrivia
c
It might be about time to refresh #C018Q3T30LW, I'm getting about half of the pairings as no-shows. What are other people seeing?
i
I don't use it (doesn't fit with my lifestyle), so unfortunately I can't weigh in. There's only 41 people in the channel, so it might be worth advertising its existence a bit. Want me to do that?
c
I don't think #C018Q3T30LW is really mentioned a whole lot, if we refreshed, it would make sense to @ everyone to get eyes on it as a resource, and we can DM everyone in the channel to re-join if they didn't want to be removed
Yeah yeah 👍
That sounds great to me, @Ivan Reese
i
Not sure what you mean by "refreshed"
c
Clear everyone from the channel and ask everyone to rejoin
We can also rename the current channel, create a new #C018Q3T30LW , and at channel to say there's a new channel to join...
Then advertise that new channel a bit more
i
If someone does want to participate and didn't want to be removed, rejoining is easy enough. Any monkeying with the channel itself will require me to mess with the Donut config, which I'm reluctant to do. I'll just manually pull everyone out and put out a broadcast in #CGMJ7323Z
c
Just some thoughts. I'm not in a rush, so I'm happy to wait for others to weigh in, too! Maybe others have some good ideas of ways the channel could be improved.
👍 1
i
Pending any other clearly-actionable input from folks, I'll make this change early next week.
👍 3
c
Thanks!
j
I did not know this channel existed.
👀 1
i
For @jamii or any other folks wondering, see the channel descriptions here: https://futureofcoding.org/member-handbook
👍 1
w
I agree that a refresh is worth doing. I really like #C018Q3T30LW, but I too have been paired with no-shows with more frequency than I would like.
(I mean I'm a busy man, so an occasional no-show I hardly give a second thought to.)