It's nice to be able to say thanks! https://saythanks.io/
Hmm... while I personally find constructive criticism more useful, I really like the precedent this sets for open source projects in general. And the badge will fit right in.
We now have a README badge linking to https://saythanks.io/to/drake-r-package-feedback.
I will add my own personal SayThanks.io mailbox as a temporary placeholder, but many more people deserve thanks for drake. I wonder if @ropensci would be willing to open an account. cc'ing @maelle, drake's @ropensci onboarding editor.
Happy to do this for you. Who should this email go to? I can set up [email protected] (I hope we don't hire Drake someday) to go to the authors/maintainers?
Thanks, @karthik. Your comment nudged me to take a closer look, and until https://github.com/kennethreitz/saythanks.io/issues/44 is solved, I actually think I can handle this with a separate gmail account and a specialized filter. I do appreciate the offer, though.
The README badge now links to https://saythanks.io/to/drake-r-package-feedback. To anyone connected with drake's development and/or @ropensci, just ping me and I will set up gmail forwarding from no-reply at saythanks dot io to your email account through drake.r.package.feedback at gmail dot com. cc'ing some possible takers.
In fact, I will add anyone who requests it. I see no reason to limit this to EDIT: see https://github.com/ropensci/drake/issues/638#issuecomment-451684076.drake developers.
maybe @stefaniebutland would like to see how such notes look like?
You should find some thanks in your inbox soon 馃檹
I saw, that's nice of you.
A couple more thoughts/updates:
DESCRIPTION file.
Most helpful comment
The README badge now links to https://saythanks.io/to/drake-r-package-feedback. To anyone connected with
drake's development and/or @ropensci, just ping me and I will set up gmail forwarding fromno-reply at saythanks dot ioto your email account throughdrake.r.package.feedback at gmail dot com. cc'ing some possible takers.