On 2026-11-13 23:41 +0000, Francisco M Neto wrote:
The problem is that finding a sponsor is not a straightforward
process - it can be a breeze for some people, and a nightmare for
others. As I pointed out earlier, I do not have a proposal for what can
be done about it. But I can tell that this process need to be more
reliable - or, at the very least, a bit more stable.
Do we have any stats on what fraction of RFSes are eventually sponsored (and how long that period is?). I agree that not knowing if you are wasting your time packaging is unsatisfactory for new packagers, but I have assumed that most packages would get a sponsor eventually if they are done properly and of some use, but maybe lots are slipping through the net (or are quietly deemed 'not useful enough'). I just hang around here and very occasionally see something I am genuinely interested in, or just feel like helping out a random packager when I am putting off doing something else on my todo list :-) So I've not really followed how well the process is actually working in detail. On the original point of 'tidying' the list (and suspecting some RFS requesters are not fully understanding the expectations), there are lots of cases of software authors maintaining their own stuff in debian, and on the whole that's a good thing. It produces high-quality maintenance, timely updates, and often brings people into debian as wider contributors, so I don't see upstream=downstream as a problem indicatior per se. I don't know whether we need to tidy the RFS list periodically. On the one hand it would put some kind of known time period on how long to wait for a sponsorship, and would keep the list short. But 'keeping lists short' is not really the debian way. The ITP and RFP lists are also very long and full of old requests. But a 4yr ITP can still be very useful, so I guess the question is how old does an RFS have to get before the requester loses interest? For people who genuinely just want their software in the distro it doesn't really matter if a sponsor doesn't notice it till 2 years later (except that is may well need an update by then). I think talk of throwing stuff more than 3 or 4 months old out is too quick. I'd leave them for a year. Maybe sorting the RFS list into periods so that the older stuff does not get in the way of day-to-day activities would be helpful? So we have 'last 2 months' and 'older' or maybe an intermediate period too? Just some thoughts. It has been interesting to hear how this process looks from the other side. Wookey -- Principal hats: Wookware, Debian http://wookware.org/ Matrix: @wookey:matrix.org
signature.asc
Description: PGP signature

