For major projects it may work, but sometimes you're updating an old library to work with a newer version of a platform and get dead silence. It doesn't do anyone any good.
For major projects it may work, but sometimes you're updating an old library to work with a newer version of a platform and get dead silence. It doesn't do anyone any good.
But at least with github/bitbucket, most of this friction is reduced to a few simple clicks. It's certainly no worse.
If only things were that simple. A proper maintainer would have to:
a) decide whether what this patch claims to do with the code moves the code in a direction where the maintainers want it to move.
b) review the code for quality, security concerns and outright backdoors.
c) possibly: compare it to a zillion patches that (more or less) claim to do the same.
d) assuming the patch is perfect: check with collisions on other pending patches, recently committed changes, etc.
I do not know about this project, and have no real expertise as a maintainer, but I am fairly sure it is not "just laziness". If it were, all projects would have an email address that blindly applies each patch sent to it to the code base.
In my example case, it certainly is. There certainly aren't zillions of patches. The maintainers are just not "maintaining". Plain and simple.