@RueNahcMohr @dos

You were told earlier today, in this thread.

https://social.gl-como.it/display/3e3ce0df-156a-820f-9c4b-a0c112038808

What more do you want?

@lproven @dos no no, I was just told that was all gibberish folklore. and I dont think people socially hype-up a package and create a ruccas about it on *mailing lists* to get it inducted into debian.

@RueNahcMohr @dos 😡

@lproven @dos

ok, what is the last project you helped induct into debian?

@RueNahcMohr @lproven Many years ago I got my own unknown project packaged in Debian. All it took (aside of technical work) was to find a sponsor among Debian Developers to review and upload it. I got some feedback, applied it and into Debian it went. I've also contributed several patches to existing packages - the maintainer reviewed them, merged them and they're in Debian. It's really no different to any other respectable project out there, nobody gets full commit rights just because they ask.

@dos @lproven How did you find the sponsor?

@RueNahcMohr @lproven I have uploaded my package to https://mentors.debian.net/ and stated that I'm seeking one.

@dos @lproven ah!!! ok, THAT is what I needed to know about!!!!!

I will take a project and work on making it into a debian package, submit it and see what happens!

@RueNahcMohr @lproven What you described in your initial post was a path to become a trusted person with direct upload rights to the distribution archive, *not* a requirement to contribute. Debian Maintainers can upload new versions of packages they maintain without having a sponsor, Debian Developers can upload anything. You need to have already contributed for a while in order to become any of them, and I think you'll agree that it's a reasonable requirement.

@dos @lproven sure, but I'm just a guy with main.c and no interest in certifying myself as a maintainer of the whole debian distribution.

so how did you find a sponsor?

@RueNahcMohr @dos @lproven no, they don't “create a ruccas”. they send *one* email to a mailing list (actually a ticket tracker than works via email, and then it's forwarded to a mailing list), and then they will have to read and react appropriately to some technical feedback.

And in case there is a generational misunderstanding at work here: “mailing list” doesn't mean “asymmetrical place where one person writes more or less marketing material so that a lot of people will read it”, but has the old meaning of “a place for asynchronous communication for a somewhat big community of more or less peers”.

@valhalla @dos @lproven ok, not a public mailing list then.

"submit it to mentors (a platform and a mailing list)"

in this text, "mentors" and "platform" imply winding up a group of people on social media about how great your program is and that debian would be hopeless without it.

These are the challenges I had trying to figure out the process, which quickly spiraled into being a debian developer because nowhere did anyone just say "submit your package to this email address"

@RueNahcMohr @dos @lproven technically the mailing list (and ticket tracker) are both public, with online archives that can be browsed to see what kind of messages are expected lists.debian.org/debian-mentor…

but it's not a place read by the general public, but by Debian Developers who are looking for package that require sponsors, and (hopefully) by people who are looking for a sponsor for their package.

mentors is also a platform as in “a website that provides a service” (I'm not a native English speaker, so maybe that's not the word you expected?): mentors.debian.net/ and it has documentation on how to use it to put your work somewhere where interested people can look at it, and on the process in general: mentors.debian.net/intro-maint…

Note that you will have to *describe* the package, but not to write marketing copy for it (with the amount of Debian developers who are on the spectrum that's not likely to receive good reactions :) )