3 ms·
Can this apply for submitting new packages as well? The process (at least the old process) as dissuaded me from doing just that.
by chungy 8y ago
Can this apply for submitting new packages as well? The process (at least the old process) as dissuaded me from doing just that.
- jkaplowitz 8y agoMostly yes. For new packages, an existing Debian developer has to do the initial upload, after reviewing your work. Once the package is in the archive and they're confident enough with your work, you can receive package-specific permission for subsequent uploads. There is a bit of bureaucracy the first time you want package-specific upload permission, but mainly to vouch for you in a lightweight way, to validate your identity, and to agree to Debian's various policies. https://wiki.debian.org/DebianMaintainer https://wiki.debian.org/DebianMaintainer But proposing merge requests via salsa can happen without any of that even if your contributions will end up in new packages.
- geofft 8y agoYou can't do the upload yourself, but it's pretty straightforward to prepare a package and ask someone to upload it. (It is not too different in theory from, say, needing a Homebrew maintainer to hit "merge" on GitHub; it's a little more work on the sponsor's side than just hitting a button, but not much more, and the bulk of the work in either case is reviewing the new package.)