3 ms·
the whole post is interesting but if you're short on time jump to the end "Open Source" Then try to have a better attitude when leaving issues on github or wha
by greggman3 6y ago
the whole post is interesting but if you're short on time jump to the end "Open Source"
Then try to have a better attitude when leaving issues on github or whatever. Be thankful. Take responsibility if you want a change to make the change yourself. Offer it as a PR but don't expect it to be pulled. Others can grab the PR if they want it even if the maintainer doesn't feel it's a fit. If you have a suggestion offer it as a question like (would it be faster if this did X instead of Y? or would it be useful if feature A existed?)
I'm not good at this myself but I'm slowly getting better over the years.
Also also, I wish there was a better way to express thanks. In the article it was mentioned that thank yous are rare where as angry demands are common. But, there is no easy way to express thanks. Like opening an issue and saying "Thank you" is frowned on. Even leaving a comment under a tech blog post that just says "thanks" is considered by some to be unwanted noise. I don't have a solution here. Maybe you have some suggestions?
Also, if you feel it's appropriate, sponsor your favorite projects. I've wondered if there is a good way to promote sponsorship. I don't want to brag that I'm donating each month to various projects but I do want more people to consider sponsoring. Especially user oriented projects like say Blender, software that 100k to 1000k people are using which would normally probably cost $1500k-$3000k a year, maybe a coffee a month would be worth if you're using it often? Same for things like Kodi? Or VLC? both of which I've got 1000s of hours of usage out of.
- StavrosK 6y agoI've registered the domain www.osscoc.com and I keep planning to write something but never get the inspiration. I want it to be a reminder that people can easily link to, e.g. when someone is being belligerent, the CoC can remind them that everyone is on the same side, and lay out some scenarios like "my PR didn't get approved" and what to remember. Also, the best thanks are PRs, I think.
- aplaice 6y ago> Maybe you have some suggestions? I'm probably not the intended "you", but one idea would be a "testimonials"/thanks section in GitHub/GitLab/Gitea, in addition to the standard Issues and Pull/Merge requests. It'd allow users of the tool/library to express gratitude, give the developer feedback about their creation and possibly even provide inspiration to other users. People could set their own notification preferences, and the UI could make it clear to those thanking that they shouldn't necessarily expect a reply. The "testimonials/thanks template" could include a suggestion to donate if you've made a commercial product using the software or if you're just a happy end-user. GitHub is trying out "discussions", but that's far less targeted. From a personal point of view, I just try to express thanks whenever I otherwise have a substantive point to make (bug report, comment on an issue, but as you point out that doesn't allow for situations where you don't have anything else to say.