search

GSA-TTS / tts-tech-operations

TTS Technology Operations
https://handbook.tts.gsa.gov/tech-operations/
Other
6 stars 0 forks source link

determine process for new shared Slack channels #122

Closed afeld closed 4 years ago

afeld commented 5 years ago

Background information

OSC expressed concern over shared Slack channels (between workspaces) getting created—when they have to field questions, they don't want to be caught by surprise that we have these communication channels in place. They asked to be involved in reviewing new ones.

Acceptance criteria

Waiting on response from GSA IT. Email thread is shared Slack channels.

adunkman commented 4 years ago

I’m just rolling off a project with NOAA’s Office of Water Prediction and it would have been preferable to use a shared Slack channel instead of inviting them to our Slack as guest accounts (as they use Slack daily).

My previous project was with NIH’s National Center for Advancing Translational Sciences, who also use Slack, and invited us as guest users to a channel in their Slack. Again, a shared channel would have worked better.

The project before that I was working with Army Research Labs, who don’t have a Slack, but I was collaborating with the Defense Digital Services who do, and it would have been helpful to have a shared channel there as well.

Just a few data points in case it helps! 😄

mgwalker commented 4 years ago

CMS has started using Slack, and a shared channel would be a great way for us to have one-off conversations with folks at CMS without having to give them guest accounts in our Slack or resort to email. I don't know if we can have multiple shared channels with the same partner, but if so, having shared channels for each CMS project (eAPD, MACPro, oversight) would be really great because it'd allow the partner to retain everything in the Slack conversations after we left and it'd make it much easier to have new people from the CMS side jump into channels as-needed and could even be used to make this work more visible within CMS.

mheadd commented 4 years ago

We've started to work more closely with the Defense Digital Service as part of the National Security & Intelligence portfolio work and they are regular Slack users. It would be beneficial if we had a shared channel with them so that we can coordinate on projects if mutual interest.

afeld commented 4 years ago

Sent a nudge to Security to ask for the green light.

afeld commented 4 years ago

Meeting set for 1/22.

cjhskippy commented 4 years ago

Appreciate the efforts on this front. Sharing the way our project is impacted in case it's any help:

We are coming to the end of our engagement with the Department of State Operations Center, and we have just kicked off work with a contractor. The contractor invited us to a shared slack channel that would serve as the primary communication method for the duration of their contract between 18F, Ops (our partner), and the contractor.

We already have a -partners slack channel for this engagement. If our only option is to add the contractors to this channel, it serves us poorly in the following ways:

*A different possible solution to these two problems would be to allow our government partners to be dual-channel guests. One channel would be 18F+partners, and the other channel would be 18F+partners+contractors. Unfortunately, current policy does not allow us to invite guests to more than one channel.

its-a-lisa-at-work commented 4 years ago

Closing based on the decision made on 4/21/20 to close anything that wasn't a Major current Initiative or Notable mention from the Tech Portfolio Sprint Planning 2020-04-20 radiated intent in slack and open for discussion on reopening.

mgwalker commented 4 years ago

I think this is very valuable but also recognize it's not really up to the tech portfolio to decide. Would it be okay to revisit this in a month or two and see if anything has changed upstream at GSA? I'll volunteer to set the reminder.

its-a-lisa-at-work commented 4 years ago

Works for me!

On Thu, Apr 23, 2020 at 10:18 AM Greg Walker notifications@github.com wrote:

I think this is very valuable but also recognize it's not really up to the tech portfolio to decide. Would it be okay to revisit this in a month or two and see if anything has changed upstream at GSA? I'll volunteer to set the reminder.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/18F/tts-tech-portfolio/issues/122#issuecomment-618420947, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHPQBHV3JSD2YZRFJ7ETN4DROBEZPANCNFSM4I7PKPNA .

-- Alyssa Feola Cybersecurity Advisor Technology Portfolio GSA | FAS | TTS | QQ3 alyssa.feola@gsa.gov cell: 202-322-8267

afeld commented 4 years ago

Reopening this as a (hopefully) lower-effort alternative to https://github.com/18F/tts-tech-portfolio/issues/518, as with more Shared Channels in place:

its-a-lisa-at-work commented 4 years ago

Great idea!!

On Fri, Sep 4, 2020 at 11:08 AM Aidan Feldman notifications@github.com wrote:

Reopening this as a (hopefully) lower-effort alternative to #518 https://github.com/18F/tts-tech-portfolio/issues/518, as with more Shared Channels in place:

  • Some existing single-channel users could be deactivated in favor of using their existing Slack accounts in their own workspace, making room for other single-channel users
  • Shouldn't require any code
  • Less user management for the Slack admins

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/18F/tts-tech-portfolio/issues/122#issuecomment-687208143, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHPQBHUVNXOXDYK7CLNXSFTSED7F3ANCNFSM4I7PKPNA .

-- Alyssa Feola Cybersecurity Advisor Technology Portfolio GSA | FAS | TTS | QQ3 alyssa.feola@gsa.gov cell: 202-322-8267

afeld commented 4 years ago
afeld commented 4 years ago

Wrote a letter to send to the Slack admins and OSC. Would love feedback from folks looking to use shared channels!

mchelen-gov commented 4 years ago

If it's a helpful example, I am a gov't agency (VA) user who has been added to TTS slack as a single channel guest because we are using Federalist. There is already a VA slack with all the stakeholders, each of whom needs to communicate with TTS either as single channel guests or with a shared channel.

afeld commented 4 years ago

Talked through with CTO and Corporate IT, and updated our guidance.

afeld commented 4 years ago

Email scheduled for Monday morning. There will be follow-up work to convert channels, hopefully mostly handled by the admins. Considering this done!