Admin here. Seems reasonable to me to try creating a canvas, no one here has done that as yet (or in any other slack group I'm in). Be aware that Slack gives us a free pro account, but that's not guaranteed to last forever and I suspect you'd lose your canvas if they decided to stop doing that. Alternately, feel free to make a channel for your project as long as it's not a name that'll clash with other stuff (eg #chip-project or any sort of #chip-foo would probably be a good name).

So if Slack pulls the Pro support, channels would still be around? I wonder what else might get heaved if they decide to drop sponsorship. Is there a Clojurians groups with fee-paying members somewhere? Again, thanks for your help.

My current understanding is that we'd keep all channels, would presumably lose Canvases, and -- this is the main downside in my view -- lose all history older than (IIRC) 90 days. There are definitely downsides to slack as a community venue, this just happened to turn out to be the Schelling point that the community settled on. > Is there a Clojurians groups with fee-paying members somewhere? Not that I'm aware of, but there are definitely other hubs for the community, notably Clojureverse and Zulip (moderately sure those are the biggest two these days other than slack).

& many channels are archived, I believe at https://clojurians-log.clojureverse.org/<channel-name>

Only 90 days of history would really hurt. So much for immutability.

I’ll use an appropriately-named channel unless my playing guinea pig with a Canvas would be helpful somehow.

Nah, I imagine someday someone will try one of those on some slack somewhere, no need for you to fall on that sword.

Thanks.

Brief update I created https://clojurians.slack.com/archives/C05P6UP4G2K. Thanks again. Turns out each channel has its own canvas. https://slack.com/features/canvas. It’s helpful for us. They are documents with conversations vs conversations with documents (standard Slack message). Quick summary, there’s 3 places for canvases: • Each channel (one per) • Each DM relationship (at least one per relationship — I’ll report back if more) • Personal canvases (many per person, shareable)

Maybe I have a protocol/conduct question. Maybe. From https://clojurians.slack.com/archives/C05P6UP4G2K/p1693604389262049 yesterday, our channel got more attention than I expected. People joined I didn’t expect. Concerns about over-notifying started to bubble up. Know what? That’s dumb. Yeah, real dumb. I respect everyone’s time. @U05476190 and @U3X7174KS joined because they are generous and thoughtful and somewhere saw something valuable to them. That’s not about me. What I owe the planet is living my life. Folks need to live theirs. That’s what they owe me and the rest of us. Aren’t we all glad Slack has channel “Mute” and “Leave” buttons. I want everyone to come and go as best serves them — me included. Onward. Never mind. Seems the issue worked itself out. Thanks again.

Returning to your "conduct" comment and a Q elsewhere about "leadership" / "bully pulpit": https://github.com/clojurians/community-development/blob/master/Code-of-Conduct.md -- the admin team is listed at the bottom of that. Re: Clojure leadership, Alex already answered you elsewhere. I just wanted to link you to this so you'd know how the community is supposed to work 🙂 Happy to answer any other Qs you may have about this community!