On 2026-11-13 at 11:20, Erik Huelsmann wrote:

> Hi,
> 
> On Fri, Nov 13, 2026 at 8:35 AM Maytham Alsudany <[email protected]>
> wrote:

>> The problem is that many people treat Debian like a PPA, where
>> they either attempt to upload some low-quality program, or will do
>> a great work packaging but then disappear off the radar, leaving
>> teams like MIA to clean up after them after a long, long time.
>> There is no way to tell this just by looking at an RFS, other than
>> the contributor's previous history.
> 
> How is a prospect supposed to get that previous history? I mean: a
> first contribution will *always* be without previous history, after
> all...
> 
> Now, for the record, I'm not a DM or DD. I *have* tried contribute
> on several occasions, but the packaging rules around JavaScript
> dependencies for the web applications I was trying to package were
> both insufficiently clear and - if taken literally - too daunting
> and generally unworkable. So, I'm saying this as a long-time
> (absolutely grateful!) user and wannabe
> contributor-without-much-success. (one or two package updates did go
> through, though)

There may be multiple answers to that, and the one I am about to give is
certainly not definitive - I've never even made a packaging-related
contribution (that I recall) myself, much less become DM or DD, although
I have done some work with those systems for local purposes.

That said, one way for a prospect to establish history and develop
enough of a reputation for reliability for people to be comfortable
sponsoring packages where that prospect is upstream is - if my reading
of the situation is correct - by contributing assistance with *existing*
packages, whether in appropriate coordination with those packages'
maintainers, or by volunteering to adopt orphaned packages (of
sufficiently low complexity that such an adoption attempt would be able
to find sponsors). The trust threshold for something like that seems, in
my experience observing these mailing lists and related areas, to be
significantly lower than the trust threshold for contributing a package
for which one is also the upstream maintainer - but it gives the
opportunity to show both one's packaging skills (which can also be
improved in the sponsorship review process) and one's reliability (in
continuing to contribute to whichever packages are involved over time).

I think I've also seen it happen that someone files an ITP and a RFS,
gets no response or at least no sponsorship, and just *keeps updating
the RFS as new versions come out*, maintaining consistently good
packaging quality over time, and that itself becomes visible history
that leads someone to decide the contributor seems reliable enough for
sponsoring such an upstream=downstream package to be appropriate. That's
less common, IIRC, but it might be another possible avenue.

Neither of those is necessarily a guaranteed path, nor are they
necessarily the only paths. But they are the ones which my time spent
observing has suggested to me are probably the most accessible, in the
absence of establishing a we-know-each-other trust relationship with a
Debian Developer in other contexts first.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to