How to become a packager (was: Re: [Proposal] Ring-based Packaging Policies)

Ian Malone ibmalone at
Fri Feb 13 16:40:25 UTC 2015

On 13 February 2015 at 15:35, Michael Schwendt <mschwendt at> wrote:
> On Fri, 13 Feb 2015 14:00:07 +0000, Ian Malone wrote:
>> Actually, a question I have about this is how it will impact people
>> trying to become maintainers. When I last checked (it may have
>> changed) the only way to do that was to create a new package.
> That isn't the only way to become a packager. And it hasn't changed
> for a very long time:
>    ->
> Submitting a new package is just _one_ of multiple ways to find a sponsor,
> since it is an opportunity to demonstrate that you know packaging.

Thanks. I think when I'd looked at it I'd discounted the review and
comment on others' submissions process as it would seem to require you
to have a better idea of what you're doing than the person submitting
the package, and potentially just creating noise when other people are
looking at it too.
Yes, probably a good idea maintainers know how to package. :)

> Random fire'n'forget builds in a public Fedora repo would be something
> that would scare me.

This is sort of a situation we have by default, as it's simpler for
people to package into the SUSE public repo.


More information about the devel mailing list