3 ms·
If we are talking FOSS-project-with-a-single-maintainer there's no reason whatsoever to expect _anything_ from the maintainer. He may be on vacation. Or ill. O
by johncoltrane 9y ago
If we are talking FOSS-project-with-a-single-maintainer there's no reason whatsoever to expect _anything_ from the maintainer.
He may be on vacation. Or ill. Or busy doing other things. Or unable to dedicate 3 evenings to review your 2000 lines of code _right now_. He will eventually get back to you but until then it will certainly be a good idea to split your PR in several self-contained PRs, as suggested by LiamPa.
In the mean time, get in touch with the user who had the original issue and figure out together if your change actually fixes it without causing regression. This will certainly help the maintainer.
- aetherspawn 9y agoThere are some other PRs in a similar situation that have been ignored for months. I just wish the maintainer would answer. Then I would know that it’s more worth my while to do a hard fork than waste my time checking the thread every day. The issue is a feature request, and it is mainly resolved by just self contained boilerplate API modules. The user posted the feature request >6 mo ago and I don’t really know where they have gone, but I needed the same feature.