[support] proposed redesign for handling support requests#13
[support] proposed redesign for handling support requests#13iris-garden wants to merge 3 commits intohail-is:mainfrom
Conversation
| * `#hail-on-terra`, `#hail-single-cell`, `#hail-seqr-database`, | ||
| `#hail-lab-meeting`, `#hail-aou`, `#hail_joint_calling_200ukbb` | ||
| * how about these on the atgu slack? | ||
| * `#hail-announcements`, `#port_gnomad_methods_into_hail` |
There was a problem hiding this comment.
Keep #hail-announcements. That's how we communicate directly to our first-party users. These people pay our salaries and are the only users of our Hail Batch SaaS so they receive special, targeted announcements.
The gnomad thing is probably a gnomad thing, so ignore that.
|
|
||
| * are any of these broad slack channels still in use? | ||
| * `#hail-on-terra`, `#hail-single-cell`, `#hail-seqr-database`, | ||
| `#hail-lab-meeting`, `#hail-aou`, `#hail_joint_calling_200ukbb` |
There was a problem hiding this comment.
hail-on-terra and hail-aou are special purpose channels for collaborating with the Terra people and the Variants team (aka AoU joint calling) people. Keep those.
Hail-single-cell is a bit moribund, but leave that in Konrad's hands.
Hail-seqr-database is probably not relevant anymore, we can archive.
Archive hail-lab-meeting.
Archive hail_joint_calling_200ukb .
|
|
||
| ### open questions | ||
|
|
||
| * `#github`: does anyone currently use this instead of normal github notifs? |
| * `#workshop` | ||
| * use per-workshop channels like existing `#atgu welcome workshop 2022` instead |
There was a problem hiding this comment.
Can we not just use a thread in #workshop? one channel per workshop seems excessive and there might be useful history in the channel from year to year?
3 participants
No description provided.