Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Hubot, “the hardest working GitHubber”

wired.com

Post reply on HN
Print view View original

21–30 of 40 posts

Re: Hubot, “the hardest working GitHubber”

#21

Post by jon-wood »

dmihal wrote: post #11
ultramancool wrote: post #10

Earlier quoted context omitted.

Having a botnet with all your servers really isn't a bad idea. I mean, easy admin access, live monitoring, the ability to query everything and have all interested ops people examine the output... pretty handy. Seems like it'd beat a lot of these monitoring services and tools people pay for these days.

Do you mean having a bot? I can't see how having a botnet would be relevant or helpful.

It may not be malicious, but its definitely a botnet, especially given most botnets tend to use IRC for command and control.

Re: Hubot, “the hardest working GitHubber”

#22

Post by civilian »

Bluestrike2 wrote: post #13
kefka wrote: post #2

That's an old picture, as in before January 24, 2014. Why do I know? Because the "United Meritocracy of Github" carpet shown was removed after feminists threw a fit and got them to remove it. Because "Meritocracy is masculine and evil." (Read; the women GH hired can't cut it. Mainly GitHub's Julie Ann Horvath) Source: http://readwrite.com/2014/01/24/github-meritocracy-rug

Genuine meritocracy would ideally see women in positions roughly commensurate to their percentage of the population (~50.8%). There are a lot of reasons why we don't see that, and those reasons shape choices made by, available to, and expected of women well before they ever get to the point where they're applying for a position at Github or any other tech company. I think a lot of the criticism of Github's rug went f…

It's not yet decided whether our brains are wired differently: http://www.the-scientist.com/?articles.view/articleNo/41919/...

Re: Hubot, “the hardest working GitHubber”

#23

Post by adekok »

Bluestrike2 wrote: post #13
kefka wrote: post #2

That's an old picture, as in before January 24, 2014. Why do I know? Because the "United Meritocracy of Github" carpet shown was removed after feminists threw a fit and got them to remove it. Because "Meritocracy is masculine and evil." (Read; the women GH hired can't cut it. Mainly GitHub's Julie Ann Horvath) Source: http://readwrite.com/2014/01/24/github-meritocracy-rug

Genuine meritocracy would ideally see women in positions roughly commensurate to their percentage of the population (~50.8%). There are a lot of reasons why we don't see that, and those reasons shape choices made by, available to, and expected of women well before they ever get to the point where they're applying for a position at Github or any other tech company. I think a lot of the criticism of Github's rug went f…

> Genuine meritocracy would ideally see women in positions roughly commensurate to their percentage of the population

i.e. meritocracy means having people in positions based on their incidence in the general population... not on their merits.

Are you sure you understand the meaning of the word "meritocracy" ?

> a lot of those earlier factors that push far too many women away from math, science, and technology while they're still just developing children

Because women have different interests from men? I can easily name 10 male friends who obsessed about science and technology starting from 12 years old. 30 years later, they're all in computers making good money. I can think of maybe 2 female friends who came close. And even they didn't have the same level of obsession as the guys.

> I don't think most feminists have an issue with meritocracies as ideals:

If a meritocracy means hiring people on their incidence in the general population (not on their merits), then yes, that statement is true.

> Their brains aren't "different,"

Yes, they are.

https://www.psychologytoday.com/blog/hope-relationships/2014...

> This is setting aside questions of pay, culture, and other gender issues in the workplace.

If you believe the American Association of University women, they "wage gap" is about 6%. Not 77% like it's widely (and falsely) reported.

http://www.aauw.org/research/the-simple-truth-about-the-gend...

Re: Hubot, “the hardest working GitHubber”

#27

Post by listenrightmeow »

Domenic_S wrote: post #24

I love the tech, but hate how heroku-centric it all is. If you want to spin up your own hubot+heaven instance somewhere not-heroku, glhf.

https://github.com/listenrightmeow/dbot

http://pgarbe.github.io/blog/2015/03/24/how-to-run-hubot-in-...

There are a couple articles/repos out there with detailed steps on running Hubot on AWS. While the ease and simplicity of deploying Hubot outside of Heroku is not a tenth as easy, there are a couple of options out there.

Re: Hubot, “the hardest working GitHubber”

#28

Post by ultramancool »

dmihal wrote: post #11
ultramancool wrote: post #10

Earlier quoted context omitted.

Having a botnet with all your servers really isn't a bad idea. I mean, easy admin access, live monitoring, the ability to query everything and have all interested ops people examine the output... pretty handy. Seems like it'd beat a lot of these monitoring services and tools people pay for these days.

Do you mean having a bot? I can't see how having a botnet would be relevant or helpful.

No, I'm referring to a botnet. In the OP case we've got just a single bot which controls things, I'm more thinking 1 bot per server sort of thing so you can administer individual servers simply by directing messages at them.

Server goes down? You see it quit on IRC or send an alert message nickalerting relevant admins when a service halts. Need live information on just about anything, just direct a message to a given server. Could even direct logs to a separate IRC channel for each type of service, relevant admins can join and set alerts up just based on message content and keep track of small logs via IRC logging too.

You can make a lot of low visibility processes very visible using such a setup. Of course, it wouldn't be appropriate for a giant company, but for a small to medium sized one I think it could work quite well. For devops types who are already comfortable with IRC at least.

Re: Hubot, “the hardest working GitHubber”

#29

Post by Domenic_S »

listenrightmeow wrote: post #27
Domenic_S wrote: post #24

I love the tech, but hate how heroku-centric it all is. If you want to spin up your own hubot+heaven instance somewhere not-heroku, glhf.

https://github.com/listenrightmeow/dbot http://pgarbe.github.io/blog/2015/03/24/how-to-run-hubot-in-... There are a couple articles/repos out there with detailed steps on running Hubot on AWS. While the ease and simplicity of deploying Hubot outside of Heroku is not a tenth as easy, there are a couple of options out there.

I guess I'm lazy and want an apt-get/yum/brew recipe. What if I have to install it on iron behind a corporate firewall?

Re: Hubot, “the hardest working GitHubber”

#30

Post by jarek »

Domenic_S wrote: post #29
listenrightmeow wrote: post #27

Earlier quoted context omitted.

https://github.com/listenrightmeow/dbot http://pgarbe.github.io/blog/2015/03/24/how-to-run-hubot-in-... There are a couple articles/repos out there with detailed steps on running Hubot on AWS. While the ease and simplicity of deploying Hubot outside of Heroku is not a tenth as easy, there are a couple of options out there.

I guess I'm lazy and want an apt-get/yum/brew recipe. What if I have to install it on iron behind a corporate firewall?

There's always Supybot which runs basically anywhere :)
Post reply on HN