Secure Information Store

[david-driscoll]

This came up in today's meeting, what is the best way to manage access to secure pieces of information related to the OmniSharp org itself?

Things that should eventually go in this store house:

• OmniSharp Twitter credentials
• OmniSharp Bot credentials
• Any other OmniSharp related credentials?
  In the future this might include things like telemetry credentials.

@Mpdreamz said for editorconfig they used a shared gmail account.

For my passwords I use KeePass it has the ability to be secured via a key file / password combination. I don't know of a good way to share changes to that file without a central component like OneDrive.

I don't know what the "correct" solution is, does anyone else have any experience with how other OSS projects handle this. Specifically such that it's all distributed and/or stored?

[david-driscoll]

One interesting idea might be to explore creating a simple application that just authenticates you through Github and makes sure you're an Owner on the OmniSharp repo.

That could be a fun weekend project, lol.

[Mpdreamz]

@sayedihashimi you were right scotth is the omnisharp twitter team admin, I can still tweet from the omnisharp handle using tweetdeck using but I have no way to add other members.

[david-driscoll]

@shanselman happen to have the twitter information to share. Though obviously not on this public channel, lol.

[willl]

I think 1Password for Teams would be one solution. It's currently still in beta, so it's free. The pricing page says it'll be $4.99 per user after that though.

[dmccaffery]

If you're still looking into this, I like the Github login idea the best -- I've got some time opening up in my schedule (finally), so maybe a weekend warrior project with a few people can get it out the door. Lets chat about it sometime soon, if you're up for it! :)

[david-driscoll]

Going to have a meeting this week I need to modify the issue now that I think about it...