Cross-posting from <#CUMUWQU66|ingestion> to see i...
# troubleshootb
big-ocean-9800
08/12/2022, 5:53 AMCross-posting from #ingestion to see if anyone has any ideas about this one: https://datahubspace.slack.com/archives/CUMUWQU66/p1660251283230179
i
incalculable-ocean-74010
08/12/2022, 8:41 AMHello Hunter,
Please do not cross-post it makes it harder for the core team to keep track of open issues.
Thank you
b
big-ocean-9800
08/12/2022, 6:47 PMHi Pedro, I believe this post is more of #troubleshoot issue. Would you rather I copy the whole message here instead?
big-ocean-9800
08/12/2022, 6:47 PMI’d like to follow the community’s guidelines for this kind of stuff.
big-ocean-9800
08/12/2022, 6:48 PMAlso, aren’t issues tracked in Github or their dedicated issue tracking system? Just want to understand how to best abide by the flow 🙂
i
incalculable-ocean-74010
08/16/2022, 9:33 AMThere are a couple of channels folks use, getting started, ui, ingestion, troubleshoot, all-things-deployment. The core is quite active on all those.
We ask that people only write their messages once so it is easier to track who is unanswered considered the considerable size of the community.
incalculable-ocean-74010
08/16/2022, 9:34 AMThese channels as the name imply are for different purposes. You have more information on the about section of each channel.
incalculable-ocean-74010
08/16/2022, 9:35 AMOur guidelines ask that slack question be generally used for quick things. GitHub issues are for known bugs that the team can then track more easily or where big discussions/PRs/RFCs happen
3 Views