--- tags: chris, matrix --- OK I just linked a bunch of the Slack channels to Matrix channels. This is what I have coverage of / the mappings. Some Matrix channels don't have a Slack equivalent, and I didn't map some Slack channels over because they were specific to a point in time (like coursework that is long over.) Here's the full bridge mapping so far: # BRIDGED CHANNELS ## Matrix => Slack * BU Team / #chris-bu-team:fedora.im => #bu_team * ChRIS Backend / #chris-backend:fedora.im => #chris_backend * ChRIS Backend Design / #chris-backend-design:fedora.im => #chris_backend_design * ChRIS Frontend / #chris-frontend:fedora.im => #chris_frontend * ChRIS General / #chris-general:fedora.im => #general * ChRIS Store / #chris-store:fedora.im => #chris_store_frontend * COVID-Net / #chris-covidnet:fedora.im => #covidnet-frontend * Dev Help / #chris-devhelp:fedora.im => #dev-help * DevOps / #chris-devops:fedora.im => #devops * Docs / #chris-docs:fedora.im => #docs * DROPPED => #medical_compute-fall21 * Meeting Minutes / #chris-minutes:fedora.im => #meeting-minutes * Outreachy / #chris-outreachy:fedora.im => Not mapped to slack. Could map to #onboarding ? * PACS Integration / #chris-pacs:fedora.im => #pacs_integration * Papers / #chris-papers:fedora.im => #papers * Plugin Chat / #chris-plugin:fedora.im => Not mapped to slack. Was thinking this could be a place for plugin devs to talk. * Random / #chris-random:fedora.im => #random * Red Hat Volunteers / #chris-redhat-volunteers:fedora.im => #redhat-hackathon-oct2021 * Team-19 / #chris-team19:fedora.im => #team19 * Users / #chris-users:fedora.im => Not mapped to slack. * UX & Design / #chris-design:fedora.im => #design * Website / #chris-website:fedora.im => #website # UNBRIDGED CHANNELS ## Slack channels I have access to that I didn't map Happy to if it makes sense, let me know. (Some of them are plugin specific and I thought those convos could go to the Plugin Chat room.) * #ami (ami has its own slack I think now?) * #brainspec (not sure what this is) * #chris-e2 (not sure about this?) * #dev => Would it make sense to re-implement this on the Matrix side? Have it show the git commits, we can do that natively in Matrix, and name it commits or something? * #folding_at_home (general plugin channel?) * #ge-workflow (not sure if this is active?) * #moc-ancillary-services (not sure what this is?) * #mpc_plugin (could go to general plugin channel?) * #mri_scans (not sure what this is) * #mri_team (not sure about this one) * #onboarding (was thinking of mapping to an Outreachy specific channel. Or we can keep it generic. What do you think?) * #testchannel (not sure if this is needed?) * #twist (not sure what this is) * #usermarketresearch (would be fine in the design channel) * #ux-testing (should be fine in the design channel) ## Course channels I didn't map * #ccc-spring2019 * #bu2020senioruidesign * #bu_team_s20 * #cloudcomputing-2020spring-power9 * #cloudcomputing-ai * #cloudcomputing-power9 * #containerizing_neural_network_apps_group * #cs410-2021 * #cs410-spring2020 * #medical_compute-fall21 * #moc-2021-neu