https://gitlab.com/gitlab-org/gitlab-ce/issues/29667
We need to do something about this very soon, so please keep an eye on that issue.
We're going to be doing some more work on settings pages, hopefully in 9.2 and make them a lot better.
416 karma · joined January 18, 2010
https://gitlab.com/gitlab-org/gitlab-ce/issues/29667
We need to do something about this very soon, so please keep an eye on that issue.
We're going to be doing some more work on settings pages, hopefully in 9.2 and make them a lot better.
Given the aggregators exist (in the UK, Zoopla & RightMove are our Zillow) that's where all the eyeballs are and how people find properties. You can then list your own property there.
Before I started Gitter, I nearly went into exactly this space, but there are a few negatives:
1. People are generally bad at sales 2. People are generally bad at negotiating 3. People are generally afraid of complex paperwork
Sure, the system can help with these things and maybe nobody has nailed this yet because there are a few companies trying in this space and nobody seems to be coming out on top.
Sure it can do similar things to Slack/MatterMost, but that's not the intention of what we're trying to do with it.
http://w3c.github.io/push-api/
https://developers.google.com/web/updates/2015/03/push-notif...
This should be fixed very shortly. Thanks for taking the time to point it out and help others with your blog post.
Anyhoo, they do wildcard for starting at 120,00 € excl. VAT/year.
In fact chats for private repos is a completely separate matter and we allow users to upgrade their access to GitHub's repo scope if they want access to private repos.
Otherwise we'd have to do: * signup (only public repos) * upgrade permissions -> org chats * upgrade permissions -> repo chats
And so then users need to understand three levels of permissions and scope and I don't want to burden people with that level of cognitive overload. It's hard enough to explain to people that they need to elevate privileges to get private repo access.
Whilst a few people share your view, we've had nearly 10,000 grant us this access in a very short space of time and so it's not massively affecting our product right now and we have confidence in the future that GitHub will change their permissions and introduce a read-only permission that we will then switch to.
It would be exceptionally difficult for us to add/delete an SSH key by a bug, because we don't ever call or reference keys anywhere and there's really not much else we do other than GET items.
Let us know you get along with it: https://gitter.im/gitterHQ/gitter http://support.gitter.im
Mike
I've answered this numerous times in this thread, but I'll say it again, very loudly and very definitively: WE DO NOT WRITE TO YOUR SSH KEYS, EVER. EVER. EVER. We don't even read them.
Unfortunately, as beautiful as GitHub's API is, they've got their scopes for permissions completely wrong and we know they are working to fix this.
Short answer: https://gitter.zendesk.com/hc/en-us/articles/200178961-Why-d...
Long answer: https://gitter.zendesk.com/hc/en-us/articles/200176672-Authe...
Mike
We don't read, not write anything to do with your SSH keys. In fact, we don't write anything to your profile at all. This is a limitation of GitHub's API scope.
Short answer: https://gitter.zendesk.com/hc/en-us/articles/200178961-Why-d...
Long answer:https://gitter.zendesk.com/hc/en-us/articles/200176672-Authe...
PS, your SSH keys are 100% public: https://api.github.com/users/masom/keys
Mike
So we hope for more to come for other areas of the API.
We don't use those permissions, unfortunately as good as GitHub's API is, their scopes are very limited.
short answer: https://gitter.zendesk.com/hc/en-us/articles/200178961-Why-d...
long answer: https://gitter.zendesk.com/hc/en-us/articles/200176672-Authe...
We don't ever write anything to your profile. As explained in the link below, this is a standard GitHub permission.
PS your SSH keys are 100% public: https://api.github.com/users/mikexstudios/keys
Mike
Short answer: https://gitter.zendesk.com/hc/en-us/articles/200178961-Why-d...
Long answer: https://gitter.zendesk.com/hc/en-us/articles/200176672-Authe...
I know a lot of this audience are pretty bullish on IRC and so we're also busy testing an IRC bridge for Gitter. Once you've signed up, feel free to go to https://irc.gitter.im and give it a whirl.
Feel free to leave any feedback on Gitter here or get in touch with us via our chat room: https://gitter.im/gitterHQ/gitter or http://support.gitter.im
always interested in this position though. it's far more feature rich than IRC, in our opinion a better experience.
we provide a much deeper level of integration with GitHub, and also have integrations with Travis, Jenkins, Trello and are working on more. our issue mentioning and markdown are two really great features built for developers.
there are a few other advantages, for one we handle both free open source projects as well as private conversations. so you can have all of your chat in one place.
for people adopting a new chat programme, inheriting your "social graph" in the form of your org members and repos you belong to/watch/star also means that getting up and running with gitter is really fast and simple.
For more information: http://blog.gitter.im/gitter-public-beta/
Please don't hesitate to get in touch with us with comments/feedback.