Hi @dgilman. I think you bring up some good points, tbh.
I haven’t really discussed this in great detail with anyone else, so I can only speak for myself, not the community at large, but I don’t entirely disagree with the sentiment. I worry that the two mediums risk splitting the attention of the community. I worry that by splitting the community, rather than having an abundance and perhaps redundant conversation, we’re actually confusing our community and reducing conversation If that were true, it would indeed be a loss.
I think the MO of this group thus far is to try many things and see what sticks; in some cases, the thought is, if it doesn’t work, we can always walk it back. But I believe we are beginning to see some growing pains that are arguably a result of this slapdash approach. And I think it is partly for this reason that we are endeavoring to define some roles and bring some literal structure and organization to the group.
If I could say one thing in defense of the idea, it is that I agree that we need some sort of solution to capture a lot of the discussion that is had on Slack for posterity. I had the idea that possibly the issue is that we haven’t really set any guidelines for people to know when to post where. That it was an issue of integration. But maybe the issue is deeper? I don’t know. I think at this point it has become a foregone conclusion.
Which is why I suggested on Slack that we would be open to discussion. I don’t think anybody suggested (at least not publicly) a more technical solution. Which sort of leads me to my next point…
CLT Devs is kind of the wild west right now; it’s exciting to be apart of something that could be (and already has been) great for the community. But it’s also pretty rough around the edges. We don’t have everything figured out. Actually, we don’t have much figured out. We’re trying to fix that. You can help us.
What would the solution to the temporary nature of Slack discussions be, in your mind, if we got rid of Discourse? A Google Doc feels a bit unwieldy, and also doesn’t solve the problem that sometimes it isn’t until later that you realize what a touchstone a certain conversation was for the group. It could be gone by the time you realize (especially as we grow).
One option I thought of is having a “#discussion” channel or something on Slack. Every week or so, we set the description of the channel to a certain item of discussion related to the group, and that channel is expressly for discussing that thing. I’m still not sure how we would archive it, but it would be a lot easier to sort through, as only things related to that discussion would be set there.
Not sure if it’s a good idea or not, but it’s just an idea. Discuss!
We’re not asking you to solve our problems, but we are, after all, a group of developers; over-thinking and over-engineering things comes with the territory. If there’s a really obvious solution to this or any other problem that we simply aren’t seeing, by all means, I do think I can speak for the whole group when I say we would love to hear it.