Hacker Newsnew | past | comments | ask | show | jobs | submit | shouldbeworking's commentslogin

This is a bad idea. You have to have a plan if you have a for-profit open source product. You need to give contributors something so they don't feel like they're being taken advantage of. It's complicated. It isn't as easy as just open sourcing it and asking for contributions.


> You have to have a plan if

This is a moot argument. Of course s/he has to have a plan if s/he wants to be in business. What was asked was suggestions, not detailed strategy deliverables.


This other retailer's page is about the same except for that one entry: http://www.neimanmarcus.com/robots.txt


Pull requests aren't the only way to do code review.

> Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer. This functionality enables a more centralized usage of Git.

https://code.google.com/p/gerrit/


In my group we actually go old school, sit around at a table with printouts for a lot of things (not the trivial stuff). It gets a lot of raised eyebrows from other groups in the company and I was skeptical when I joined but I've come to really appreciate it.

I've found two things happening:

1) People are often more engaged in the actual review than in other groups I've been in which are doing online reviews. And here I'm talking more about a back and forth and not necessarily "everyone says their one thing". Because of this, I believe our group's thinking of stuff has evolved more rapidly than it otherwise would have. Which leads me to ...

2) It's been better for ramping new members up to speed as it's a great place for them to ask questions, not to mention listen in to the debates happening.

I hadn't done an old style code review like that for at least 10 years, but I have to say that I've enjoyed it.


Not really unfortunate. Unlike with money, inflation of version numbers doesn't cause that much trouble. It just takes some getting used to. I've gotten used to the high version numbers in Chrome and Firefox, and I'm sure I'll get used to them in projects that use semver the right way as well.



I hope this site, and others, serve to convince the community that Node isn't going to work, and to move forward with iojs instead. Even if the Node project fixed everything, I would still prefer iojs.


Can you expand on that? Why would you still prefer io.js?


I agree with the grandparent post. Joyent has been so flippant, and specifically when Bryan Cantrill made that post, I just totally lost all respect for Joyent. I spent the winter writing Go, so had lost touch with node-forward, and came back to the pleasant surprise of io.js v1.0.x. I think at this point, it would be a step backwards (and a mistake) to give Joyent even a meter of ground that's been gained with the io.js fork.


gah...I lost my appetite. central obesity is no joke http://en.wikipedia.org/wiki/Abdominal_obesity


In case anyone didn't get the joke in the title: http://knowyourmeme.com/memes/im-going-to-build-my-own-theme... haha, very funny


    function parseJson(str) {
      try {
        return JSON.parse(str);
      } catch (err) {
        if (err instanceof SyntaxError) {
          return undefined;
        } else {
          throw err;
        }
      }
    }


Top comment on the page:

> can there be legislation for airbnb to get a new logo?

http://techcrunch.com/2014/10/07/san-francisco-airbnb/?fb_co...


Is that some joke or reference that I'm not getting?


This has zero relevance to the topic but, yes, there is a reference you're missing. When AirBnB redesigned their logo, there was an internet uproar (read: slow news week and some tweets about it) about how ugly the new logo was/is.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: