3 ms·
> I also like when someone reminds me they're blocked by an issue. As a user, this feels weird to me. If I’m actually blocked by a bug you’ll receive a PR, not
by Aeolun 4y ago
> I also like when someone reminds me they're blocked by an issue.
As a user, this feels weird to me. If I’m actually blocked by a bug you’ll receive a PR, not a +1. If I have the leisure to +1 I’m clearly not blocked enough for you to consider it pressing.
- freedomben 4y agoI think this needs a big qualifier. I feel the same way, when it's a project I'm capable of doing the work for. For example, I recently needed a way to deal with Stripe early fraud warnings and the library I used didn't have those yet, so I added them over a weekend[1]. However, there are tons of dependencies that we use for all sorts of things that are highly complex where very few people would be able to send a PR (openssl for example). Things in highly complex codebases, or deeply unfamiliar languages, etc. I maintain a forked linux driver for a wireless card for example, and I don't expect there's more than a handful of people that could hack on it without introducing tears and devastation. For the projects I maintain, I would just say, "if you can, please consider a PR. If you're not sure it would be accepted I'm happy to be asked! If you can't send a PR, give as much info as you can and be polite. With that we're good. [1]: https://github.com/beam-community/stripity_stripe/pull/728 https://github.com/beam-community/stripity_stripe/pull/728
- rowanG077 4y agoWhile in theory this would be great some issues are really not feasible for a first time contributor to work on.