Q: Handling contributor patches

Hi,

thank you for running for DPL. I appreciate the time and effort it takes
to step forward for this role, and I found your focus on diversity and
encouraging new contributors particularly interesting.

I'd like to start with a question related to that topic.

Occasionally contributors submit bug reports that already contain a
patch intended to fix or improve something. Sometimes such reports
remain unanswered for many years, or the attached patch is rejected with
only a brief explanation. While maintainers clearly have the final say
over their packages and limited time, situations like this can be
discouraging for contributors who have already invested effort into
preparing a patch.

In one recent case I looked at, a bug with an attached patch from 2014
only received its first response more than a decade later.

How do you think Debian should balance maintainer autonomy with a
welcoming culture for contributors? Do you see a role for project
leadership in encouraging practices such as acknowledging patches,
giving constructive explanations, or setting expectations about how
contributions should be handled?

I would be interested in your thoughts on how Debian can remain open to
contributions while respecting the realities of volunteer maintenance.

Kind regards
    Andreas.