-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gitter chat room? #39
Comments
@bevacqua Someone took the gitter room and locked it as private. Afaik we're not sure who. |
Do you have the room URL? |
Sorry, I should have been more specific and was busy editing my comment. That room doesn't exist in Gitter at all, so was wondering if perhaps somebody created it as a channel with a different name? |
I really have no idea, but it would be useful if we could have the open repo one @mydigitalself. :) |
Can't you just query the DB and find the room associated with this repo or something? @mydigitalself |
@Fishrock123 in order to protect people's namespaces, you have to have push access to a repo in order to create the room on Gitter. I'm guessing you have push access to the website, because I see this: https://gitter.im/iojs/iojs.github.io, which is probably not ideal. If you have push access to iojs/io.js just click on Create a room (bottom left), choose Repository and you can filter down to io.js in there. If not, you need to get someone with push access to do it. |
cc @mikeal |
Fishrock123 16 hours ago
mikeal 15 hours ago |
I'm an owner of the org and I can't get in to the room, I don't understand this :( |
@mikeal It's because the room is not created yet. It is not private it just doesn't exist. Go to http://gitter.im and click on Create a room to create it. It's bad UI but that's how it works. Or just click this link: https://gitter.im/#confirm/iojs/io.js :D |
Shouldn't it just be "This room doesn't exist yet, create it?" type of UX? It'd be pretty neat if GitHub did that as well, come think of it |
@finnp when i tried that in gitter it said it was already created, I'll try again. |
@finnp "You cannot create a channel with this name as a repo with the same name already exists." |
Paradox |
oh i see! there is a different workflow for rooms that are bound to repos. :) |
Going to have a massive rethink over this, we haven't experienced this confusion before, but clearly we are not doing something correctly here. @mikeal Channels are arbitrary rooms, when you click .... YES! :) |
such shame |
Sorry for all the confusion folks, going to revisit this whole flow and simplify it. |
@mydigitalself the easiest thing would be to just modify the error message I was getting to offer creating the room as a repo room instead :) |
Yeah, just need to figure out the use case where the room does exist but you don't have permission, because that would effectively break if you tried to create the room and ruin GitHub's whole policy around non-disclosure of inaccessible resources - that's basically what causes all the heartache. |
To make the project more welcoming I think it'd make sense to have a gitter chat room and a badge in the README. Thoughts?
The text was updated successfully, but these errors were encountered: