I agree with this. As a new contributor, it was a bit demoralizing to look at all the open PR's and wonder whether when I sent a patch it would just be left to sit in the ether.
In other projects I'm involved with, more typically the maintainers go through periodically and close old PR's that will never be merged. I know at this point it's an intimidating amount of work, but I still think it'd be useful to cut down this backlog. Maybe at the SF Kafka summit sprint have a group that does this? It's a decent task for n00bs who want to help but don't know where to start to ask them to help identify PR's that are ancient and should be closed as they will never be merged. On Tue, May 23, 2017 at 4:59 AM, <marc.schle...@sdv-it.de> wrote: > Hello everyone > > I am wondering how pull-requests are handled for Kafka? There is currently > a huge amount of PRs on Github and most of them are not getting any > attention. > > If the maintainers only have a look at PR which passed the CI (which makes > sense due to the amount), then there is a problem, because the CI-pipeline > is not stable. I've submitted a PR myself which adds OSGi-metadata to the > kafka-clients artifact (see 2882). The pipeline fails randomly even though > the change only adds some entries to the manifest. > The next issue I have is, that people submitting PRs cannot have a look at > the failing CI job. So with regards to my PR, I dont have a clue what went > wrong. > If I am missing something in the process please let me know. > Regarding PR 2882, please consider merging because it would safe the > osgi-community the effort of wrapping the kafka artifact and deploy it > with different coordinates on maven central (which can confuse users) > regards > Marc >
