Github resume blames you if it can't load your profile • Hacker News Board

Re: Github resume blames you if it can't load your profile

#21

Post by beezee » Mon, Sep 03, 2012, 1:29 AM UTC

paulgb wrote: post #3

I agree, but is this really something that needs to be a blog post? You could have easily commented it on the HN post or sent the author an email. This brings to mind the recent discussions of negativity on HN.

Additionally to directly address your reference to "negativity on HN" - as someone who submits their side projects here I'm all about fostering a supportive environment, however I don't think the same rules apply if your website includes a profile for me that I did not create and is effectively misrepresenting me. Wouldn't you say so?

Re: Github resume blames you if it can't load your profile

#22

Post by crcastle » Mon, Sep 03, 2012, 6:41 PM UTC

beezee wrote: post #19

crcastle wrote: post #13

Even better than making this blog post would have been to make a pull request to the public repo that runs the site ( https://github.com/resume/resume.github.com ). It's written in JavaScript. Seeing as you're ( http://resume.github.com/?beezee ) not only an experienced github user but also an experience javascripter, I would guess that it's well within your capabilities. See a problem in the world? Fix it. Especiall…

All about this but when I see 2 year old issues on a repo with code attached that have not been answered, I generally don't hold out high enough hopes of getting a response to justify forking cloning editing pushing and opening a pull request. At least with the blog post I had a chance to rally enough attention to make it the maintainers best interest to fix.

Good point regarding the chance to rally attention, but it would have been awesome to do both. It's probably 5-10 minutes of work to do the pull request!

Re: Github resume blames you if it can't load your profile

#23

Post by beezee » Mon, Sep 03, 2012, 9:49 PM UTC

crcastle wrote: post #22

beezee wrote: post #19

Earlier quoted context omitted.

All about this but when I see 2 year old issues on a repo with code attached that have not been answered, I generally don't hold out high enough hopes of getting a response to justify forking cloning editing pushing and opening a pull request. At least with the blog post I had a chance to rally enough attention to make it the maintainers best interest to fix.

Good point regarding the chance to rally attention, but it would have been awesome to do both. It's probably 5-10 minutes of work to do the pull request!

I can't disagree with you there - while I did spend some time in the Chrome debugger to see if I could find some clues, at the end of the day I'm stingy with my time when it comes to pull requests, largely based on the # of open issues on the repo. Maybe I'm jaded but after losing a few hours to pull requests that never went answered and reading multiple different takes on github etiquette, I tend to play that safely.