On 2026-11-12 23:42:58, Francisco M Neto wrote:
        However, as Tobi points out, sponsors are always in high
demand. Getting more than one person to review and sponsor a package
may seem like a daunting task to some people.

I had found quite a few reviewers within relatively short time, as @wrar 
pointed out, there's a couple more people that are willing to review packages 
than sponsor them.

So the sponsorship is really the issue.

By the way, I really appreciate your inputs on the topic :)

(when i needed sponsorship, my  sponsor, made it clear to me that
they expect me to get more involved into Debian)

        Honestly, I don't think I would even need encouragement on
that; it used to be a goal of mine to become a DD.

Regarding that - I got "ready to submit a package" as uploader just about the time that the 
"how do we deal with slop contributions" discussion and vote was held in Debian, and I'm on the 
fence - a few years ago I would absolutely have said "yes, I would love to contribute to debian", 
which is why I started preparing my upstream so that it would be more compatible with a Debian package.

But as someone who strongly believes - no, who is actually convinced - that the 
use of large language models specifically (not machine learning), all impacts 
considered, is going to be a net negative for mankind, I am not so enthusiastic 
anymore since I've seen debian more or less embrace the slop to the point where 
some highly motivated maintainers left the project. So while I am still very 
much committed to my current upload and maintaining that in the future, I would 
rather see where this goes, while also being worried about my daily driver OS 
becoming slopified.

Just as an example, because reliable backups are of the highest order 
criticality: I froze rsync months ago when upstream started slopcoding, and I 
dread the day when I get a hard-dependency breaking system update and have to 
decide what to do about rsync.

Kind regards

    Lars

Reply via email to