Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's not at simple as that.

The patch author does the "initial" work. But then it's up to the team to learn the patch, understand it and keep maintaining it.

Every line of code is baggage.

If there is no demand for something at the time, it makes sense for maintainers to reject that. It's up to them to maintain that patch from now on.



There is another scenario, I submitted a Pull Request to a OSS project, the authors discussed it and rejected it and then implemented it in the exact same way as I did. That was hurtful.


I can't upvote your comment for some reason, but exactly this




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

Search: