3 ms·

So, first things first: Get yourself a domain name. Second, why do you need Write access to anything? You're team chat, with some notification power. Giving yo

So, first things first: Get yourself a domain name. Second, why do you need Write access to anything? You're team chat, with some notification power. Giving you access to write on not just my repos, but the repos of my organizations, is a pretty big "Hell no" without there being a company there, some names, or(and no offense here, Ross), someone I can properly sue if the shit really hits the fan. This isn't so much a question of trust as much as just me trying to cover my ass. Right now we're using Campfire, and personally, I'm not a huge fan- yeah it's been integrated with everything under the sun, but interacting with it from a phone is no fun, it's hard to notice anything being said on it without a window constantly open on it, and the styling makes reading Github notifications particularly awful. This is a longwinded way of me saying I want to give you a shot, but you either need some extremely strong justification, or you need to pull back on those requests. Edit: I'm seeing that apparently Github doesn't separate the permissions out very much? That's pretty worrying.

lennykhazan 13y ago
We definitely plan on getting a domain once the hackathon is over and we have some time to relax and really plan this out :) As I mentioned earlier, you have nothing to worry about - we don't touch your repos! Unfortunately the read permissions we need are classified as "write" (or at least we couldn't find a way to specify them as "read" in our very limited time). Once everything settles down we are going to think about ways to make it easier for people to use and trust the service so that they don't need to worry about permissions or anything like that. Thanks so much for your input, we'll definitely take it into account!
- pbiggar 13y ago
  > or at least we couldn't find a way to specify them as "read" in our very limited time You didn't miss anything - GitHub repo permissions are pretty much all-or-nothing. We've been putting up with this for two years at CircleCI :( [For others, to read from a private repo, you need to request the "repo" scope, which actually gives read+write access to every repo in every org that you have access to. See https://circleci.com/docs/github-permissions https://circleci.com/docs/github-permissions for more details.]

lennykhazan 13y ago

We definitely plan on getting a domain once the hackathon is over and we have some time to relax and really plan this out :) As I mentioned earlier, you have nothing to worry about - we don't touch your repos! Unfortunately the read permissions we need are classified as "write" (or at least we couldn't find a way to specify them as "read" in our very limited time). Once everything settles down we are going to think about ways to make it easier for people to use and trust the service so that they don't need to worry about permissions or anything like that. Thanks so much for your input, we'll definitely take it into account!

pbiggar 13y ago
> or at least we couldn't find a way to specify them as "read" in our very limited time You didn't miss anything - GitHub repo permissions are pretty much all-or-nothing. We've been putting up with this for two years at CircleCI :( [For others, to read from a private repo, you need to request the "repo" scope, which actually gives read+write access to every repo in every org that you have access to. See https://circleci.com/docs/github-permissions https://circleci.com/docs/github-permissions for more details.]