jan kili (Sep 27 2022 at 20:54): jan kili (Sep 27 2022 at 20:54):Broadly speaking, after creating a GitHub issue that would benefit from community feedback, when should we cross-post/discuss that issue in Zulip? I just made https://github.com/roc-lang/roc/issues/4120, and my first impulse was to come here to ask "What do y'all think?", but I feel bad downgrading the quality/thoroughness of public discussion in that issue as a result. Zulip history is much less searchable/accessible/available to the Roc community than GitHub issue history... but at the same time posting in Zulip generates much more discussion & thought than simply tagging some people in an issue and hoping the community stumbles across it to give their two cents.
Thoughts?
jan kili (Sep 27 2022 at 20:57):One approach I've seen in the past is to create a proposal/summary/something in a GitHub issue, tag a core contributor like Richard, then cross-post in Zulip after it's clear that the answer isn't obvious (or would benefit from crowdsourced validation). However, if that was the intended workflow, it seems like that could be inefficient and might not scale.
jan kili (Sep 27 2022 at 20:59):Regardless, when a conversation is routed to Zulip, it can be very opaque from a GitHub reader's perspective what discussion took place, or whether any happened at all. I don't see an easy fix for this, though we could try to somehow indicate that Zulip was involved in an issue/PR.
jan kili (Sep 27 2022 at 21:00):I love both discussion forums, so I simply want to better preserve our communal insights (without adding an unnecessary overlay of p r o c e s s) :smile:
Brian Hicks (Sep 29 2022 at 19:46):I think Zulips can be public. Maybe this is a way?
Brian Hicks (Sep 29 2022 at 19:46):(Gren is, for example, at least in one stream.)
Last updated: Jul 26 2025 at 12:14 UTC