Skip to content

Inconsiderate behaviour #1084

Closed
pyrotechnick opened this Issue May 16, 2011 · 10 comments

7 participants

@pyrotechnick

Rails,

Let me start off by stating how much I despise the project and everything it stands for.

Nevertheless, that's not my issue. You see, I'm quite passionately opposed the manner in which you've chosen to import your tickets from lighthouse. It's ineffective. It's inefficient. It's disrupting. It's also really, really annoying.

I must say I'm not surprised though. It certainly has the "rails" feel to it.

The next time you convince yourselves something like this is a good idea, please, stop. Try something more proactive like getting in touch with the site owners, in this case GitHub, and negotiating a sane solution.

Honestly, how hard would it have been to give them a heads-up and have them disable notifications for rails whilst you make the "import".

P.S. I've attached a sample of the feed spamming for reference...

http://dl.dropbox.com/u/21084952/rails.png

http://dl.dropbox.com/u/21084952/rails.png

@jonleighton
Ruby on Rails member

trollface

@pwnall
pwnall commented May 16, 2011

Stating the obvious: sounds like a GitHub issue.

@dmathieu

@pyrotechnick you can fix this issue by yourself by clicking "unwatch" in the project page.

@jfhbrook

Let me start off by addressing a few asides:

Let me start off by stating how much I despise the project and everything it stands for.

Not gonna win you brownie points. More bees with honey and all that.

P.S. I've attached a sample of the feed spamming for reference...

Picture no worky for me.

But at any rate:

Nevertheless, that's not my issue. You see, I'm quite passionately opposed the manner in which you've chosen to
import your tickets from lighthouse. It's ineffective. It's inefficient. It's disrupting. It's also really, really annoying.

Just because the person commenting wasn't very nice about it, doesn't mean he's not right. While I wasn't witness to the issue (I don't follow Rails that closely; I just stumbled in as a bystander tbh) It sounds like over 9000 github issues were created for rails pretty much at once in a way where everyone following the project had to sift through all these notifications in order to hear about the other projects they're interested in. I'm personally following nearly 200 repositories, and if I missed important updates to projects I like because Rails herped the derp when importing their issues, I'd be pretty miffed too. So, shit like

*trollface* *close*

and:

you can fix this issue by yourself by clicking "unwatch" in the project page.

makes you guys sound like gigantic jerks that don't seem to understand that this actually pushes away people that might have otherwise taken an interest in Rails. I know I'm less likely to try Rails now after seeing how you guys dealt with this (probably legit) issue.

Remember when RoR was cool? *eyeroll*

@vijaydev
Ruby on Rails member

It sounds like over 9000 github issues were created for rails pretty much at once in a way where everyone following the project had to sift through all these notifications in order to hear about the other projects they're interested in.

You are way off mark here. The number of issues is around 500-600. Though, the number of feed items might be much more than that, because the import included files, comments etc too.

Can I do a shameless plug in here? :) To solve the feed problem, I wrote a Google Chrome extension for GitHub that I use to good effect - https://chrome.google.com/webstore/detail/jcpkhafkpnaljjbgdgbehajihicjalkc - This might solve your problem if you are following hundreds of repos.

Thanks!

@jfhbrook

You are way off mark here. The number of issues is around 500-600.

FWIW, I was making a Dragonball Z reference. That said, looks like a pretty nice extension!

@vijaydev
Ruby on Rails member

Obviously, I wasn't aware of that term :-) Thanks!

@jfhbrook

Any time, dudesky :D

@jonleighton
Ruby on Rails member

Just to insert some facts in here, the ticket import was as a result of the discussion here, not some evil conspiracy of Rails core. People were complaining that the LH tickets were inaccessible and somebody stepped up to fix that.

I have a lot of time for people who are seeking to constructively move this project forward, but the original ticket here was written in quite a ridiculous way. It also was not a bug in Rails, or something we could just "fix", hence I closed the ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.