5 ms·

Setting up the system you describe above to work as well as say, Hipchat, with notifications by email and push notifications to iOS and Android clients, @mentio

by swombat 12y ago

Setting up the system you describe above to work as well as say, Hipchat, with notifications by email and push notifications to iOS and Android clients, @mentions, reliability, etc, is certainly doable. If you have someone who's basically a competent geek, they can probably do that in a few days to get it all working perfectly. Once set up this sort of stuff tends to be fairly robust, so it probably won't take more than 1 days a month to maintain, deal with inevitable issues, etc. If you have absolutely nothing better to do with your time, it's a great idea to do this yourself. For the rest of us who are actually trying to grow businesses rather than set up IRC servers, there's HipChat and Slack.

davidw 12y ago
> For the rest of us who are actually trying to grow businesses rather than set up IRC servers, there's HipChat and Slack For something purely internal for a company, that makes sense to me. It's the public, 'general interest' kinds of things where I'd avoid building on something proprietary if possible. Seems like a good place to mention, on Freenode: * #startups - pretty informal and sometimes a lot of noise with little signal, but occasionally something good, too. * #bootstrappers - a channel I'm trying to get going. Not much there yet!
Uberphallus 12y ago
That phrase is heavily dangerous. > For the rest of us who are actually trying to grow businesses rather than set up IRC servers, there's HipChat and Slack. For the rest of us who are actually trying to grow businesses rather than set up <insert company IT infrastructure> there's this <insert proprietary platform>. I've heard that before from people who don't blink to have their own Gitlab/Bugzilla/Jenkins/Whatever. It's overly short sighted to dedicate resources for development support IT infrastructure, but consider resources for development communication a waste of time.
- detaro 12y ago
  I agree on the dangers, but I don't think they are easily comparable. GitLab/Jenkins/... are a match for the hosted alternatives, whereas I couldn't name a system that matches Hipchat or Slack without spending a lot more time on setup and customization.
  - Uberphallus 12y ago
    At least you can deploy a HipChat server in your own boxes, Slack is a no-go for many environments, yet still used because of a good client interface combined with a cult-like following. I've found Openfire + Spark IM to be a reasonable alternative sitting between the customizable and the convenient, and it's open source.
- s73v3r 12y ago
  They're not considering resources for communication a waste of time. They just feel there's a better use for them, considering there is Slack and HipChat which do everything they want and are very simple to set up.
  - kedean 12y ago
    This is also a different case than jenkins/gitlab/etc, because communication of this sort doesn't need to be permanent. Unless some dev wants to use a different client, there's not really any limitations from using a proprietary platform. It's not like a few years down the road you'll want the 2014 chat logs, and even so it's not like IRC would give that to you.
EGreg 12y ago
So why not just start a company that sets it up once and maintains it for tons of companies? Like github. Less lock-in with IRC, since it's all can be standard protocols and open source. The company can then move it in-house later. For that matter I always wondered why someone can't do the same with git and watching files, instead of proprietary clients like dropbox.
- Uberphallus 12y ago
  > For that matter I always wondered why someone can't do the same with git and watching files, instead of proprietary clients like dropbox. You might want to have a look at git-annex (assistant or otherwise, I use both) http://git-annex.branchable.com/ http://git-annex.branchable.com/

by swombat 12y ago

davidw 12y ago

> For the rest of us who are actually trying to grow businesses rather than set up IRC servers, there's HipChat and Slack For something purely internal for a company, that makes sense to me. It's the public, 'general interest' kinds of things where I'd avoid building on something proprietary if possible. Seems like a good place to mention, on Freenode: * #startups - pretty informal and sometimes a lot of noise with little signal, but occasionally something good, too. * #bootstrappers - a channel I'm trying to get going. Not much there yet!

Uberphallus 12y ago

That phrase is heavily dangerous. > For the rest of us who are actually trying to grow businesses rather than set up IRC servers, there's HipChat and Slack. For the rest of us who are actually trying to grow businesses rather than set up <insert company IT infrastructure> there's this <insert proprietary platform>. I've heard that before from people who don't blink to have their own Gitlab/Bugzilla/Jenkins/Whatever. It's overly short sighted to dedicate resources for development support IT infrastructure, but consider resources for development communication a waste of time.

detaro 12y ago
I agree on the dangers, but I don't think they are easily comparable. GitLab/Jenkins/... are a match for the hosted alternatives, whereas I couldn't name a system that matches Hipchat or Slack without spending a lot more time on setup and customization.
- Uberphallus 12y ago
  At least you can deploy a HipChat server in your own boxes, Slack is a no-go for many environments, yet still used because of a good client interface combined with a cult-like following. I've found Openfire + Spark IM to be a reasonable alternative sitting between the customizable and the convenient, and it's open source.
s73v3r 12y ago
They're not considering resources for communication a waste of time. They just feel there's a better use for them, considering there is Slack and HipChat which do everything they want and are very simple to set up.
- kedean 12y ago
  This is also a different case than jenkins/gitlab/etc, because communication of this sort doesn't need to be permanent. Unless some dev wants to use a different client, there's not really any limitations from using a proprietary platform. It's not like a few years down the road you'll want the 2014 chat logs, and even so it's not like IRC would give that to you.

EGreg 12y ago

So why not just start a company that sets it up once and maintains it for tons of companies? Like github. Less lock-in with IRC, since it's all can be standard protocols and open source. The company can then move it in-house later. For that matter I always wondered why someone can't do the same with git and watching files, instead of proprietary clients like dropbox.

Uberphallus 12y ago
> For that matter I always wondered why someone can't do the same with git and watching files, instead of proprietary clients like dropbox. You might want to have a look at git-annex (assistant or otherwise, I use both) http://git-annex.branchable.com/ http://git-annex.branchable.com/