5 Matching Annotations
- Sep 2024
-
blog.nodejitsu.com blog.nodejitsu.com
-
Did you actually fix a known issue? Let the author know about it.
-
Developers want to improve their project. If you find an issue, bring it up. If it's a valid concern, the author will probably want to have it fixed. In many cases, the author will consider it a valid issue, but simply not have the personal time or need to address it immediately. This is where open-source is great. Just fork the project and fix it
-
Not everyone has time to adhere to the specific coding styles for a project, so if you can't do a full blown pull-request, there is NOTHING wrong with opening a pull-request that only has the intention of showing the author how you solved the problem.
-
On behalf of all open-source developers and project maintainers, I ask you try and be polite the next time you ask for support. Try to remember that there is a real human being on the other side of the screen, and they actually want to help you.
-
If you feel there has been an oversight, it's okay to not give up. As long as you are being logical and open to other people's views, you will find that you might learn something new, or even teach something to the maintainer.
Tags
- help them help you
- maintainer: limited time
- maintainer: wants to improve software/project
- gratitude for people's time
- respect
- be helpful
- courtesy
- create merge request: even something unfinished or proof of concept is better than nothing
- communicating with author/maintainer
- fix it yourself
- waiting for someone else to fix it
- something is better than nothing
- let them know
- maintainer: not enough time to do/fix everything they would like
Annotators
URL
-