Reminds me I have a ton of open patch contributions I need to review.
Sometimes all a maintainer needs is a “thank you”
11–20 of 67 posts
Re: Sometimes all a maintainer needs is a “thank you”
#12Thank yous do help a lot. And they help outweigh the nasty stuff many maintainers get (harassment, death threats, rape threats, doxing, etc).
Re: Sometimes all a maintainer needs is a “thank you”
#13Good care and feeding for vendors as well.
Re: Sometimes all a maintainer needs is a “thank you”
#14Gratitude has its place. Still, doesn't pay the bills. Perhaps Patreon and GitTip like solutions will prove more sustainable.
Re: Sometimes all a maintainer needs is a “thank you”
#15And on the other end of the scale, here's what not to say :) https://github.com/remy/nodemon/issues/824#issuecomment-2178...
Re: Sometimes all a maintainer needs is a “thank you”
#16Did you know Debian's reportbug has a feature in it that lets you send kudos instead of reporting an issue?
`reportbug -k` or `reportbug --kudos`!
Re: Sometimes all a maintainer needs is a “thank you”
#17I'm using ouicards[0] in my project (example: [1]). First thing i did was writing a 'thank you' email to the author. They saved me many hours and gave me a jump start with design, which is always the most difficult thing for me personally.
I did change many parts, but it was a breeze.
Based on this work i maintain a basic gun knowledge course, which sees more than 5k trainees a year. Now in Poland a lot more people can pass the official exam (it has two parts: theory, taken care of by my course, and shooting, which requires additional classes at a gun range), since learning is faster, simpler and more thorough.
Re: Sometimes all a maintainer needs is a “thank you”
#18I’d prefer a usage description in the form of “we’re using this software in X to do Y and it handles Z payload every day”. A simple thanks is just a distraction that you need to click through and acknowledge, zero useful.
Re: Sometimes all a maintainer needs is a “thank you”
#19It was so touching to read the thank you note and the response to it.
Re: Sometimes all a maintainer needs is a “thank you”
#20Idea: Let's create a Thank you day for all creators and maintainers by opening one issue for whatever we use. Let's star them and like them.
Or is it a bad idea for some reason?