Our great sponsors
-
hairpin-proxy
PROXY protocol support for internal-to-LoadBalancer traffic for Kubernetes Ingress users. If you've had problems with ingress-nginx, cert-manager, LetsEncrypt ACME HTTP01 self-check failures, and the PROXY protocol, read on.
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
It's a wonderful idea however it should be a nudge and not a requirement. A software with a SATA license as proposed there could not be redistributed by a Linux distro, because the distro could not enforce the SATA with the end user.
This is also tracked as an open issue:
https://github.com/zTrix/sata-license/issues/5#issuecomment-...
Here is one I received about a year ago: https://github.com/susam/uncap/issues/9 . It made my day! The GitHub user interface should encourage this as a feature.
I did the same a while ago with a really useful tool that had helped me save a lot of time [0].
I think it's a really good idea to provide thanks and gratitude like this because I know its very validating and motivational for someone to reach out like this.
This should be especially true for more niche projects that gather less recognition but you can still find very useful.
[0]: https://github.com/geoffreylitt/simple_recommender/issues/7
This inspired me so I will find more time to do this as well. Went ahead and started at one of my favorite projects that I use across several professional and personal projects :)
https://github.com/actionhero/node-resque/issues/496
[2] https://github.com/egordorichev/BurningKnight/issues/223
Not at all. I've been thanking Scott for making lumen every thanksgiving for several years now. https://github.com/sctb/lumen
I just close the issue immediately after opening it. :)
I think we've only had one 'thank you' GitHub issue for Matrix/Element (Riot) in 6 years, but it was hugely appreciated and continues to make folks smile when they make a coffee in the office (back when we had an office): https://github.com/vector-im/element-web/issues/8752
> Critics, on the other hand, are disproportionately loud.
I recently saw this comment and it kind of haunts me: https://github.com/ionic-team/capacitor/issues/2688#issuecom.... Wish there was some way to say to the maintainers: "please ignore this guy, thanks for all your effort".
This thread motivated me to add a new "kind words" category to the Tailwind CSS discussions area on GitHub — maybe other projects can do the same:
https://github.com/tailwindlabs/tailwindcss/discussions/cate...
Managing OSS stuff really is brutal, and the amount of negative stuff you hear is hugely disproportionate to the amount of positive stuff. Anything to encourage the happy users to speak up once in a while can go a long way toward preventing OSS maintainers from burning out.
1. https://github.com/konstantint/pyliftover
I used the discussions feature to express my thanks a few days ago. Might be better than opening an issue? https://github.com/TG9541/stm8ef/discussions/386
The restic issue template has a question about this:
> Did restic help you today? Did it make you happy in any way?
https://github.com/restic/restic/blob/master/.github/ISSUE_T...