Re: "Write a new package" culture instead of patches?

[Eli Zaretskii]

> Date: Sun, 17 May 2020 19:25:50 +0000
> From: ndame <address@hidden>
> 
> The obvious answer  is because they solved the problem, it works, available 
> to anyone and they can't be
> bothered with jumping through additional hoops (paperwork, following the core 
> rules for docs, code
> formatting, commit message, etc.).
> 
> For some people getting their code into the core is a source of pride. For 
> others it's a pointless excercise,
> because it's trivially available from MELPA which the majority of users use 
> anyway for other packages too.

But MELPA asks you to jump through a different set of hoops, which
seems to fly in the face of your theory.

IME, many people who "solved the problem" want others to enjoy their
solution, and that is what gives them the incentive to "jump through
hoops".