[csw-maintainers] Non-Maintainer Uploads (NMUs)

Maciej (Matchek) Bliziński maciej at opencsw.org
Sun Aug 11 13:56:40 CEST 2013

2013/8/11 Peter FELECAN <pfelecan at opencsw.org>:
> "Maciej (Matchek) Bliziński" <maciej at opencsw.org> writes:
>> 2013/8/11 Peter FELECAN <pfelecan at opencsw.org>:
>>> To come back to my proposition, in which part of the code is the
>>> association made, i.e. uploader becomes maintainer? Answering this
>>> question can simplify my life instead of wandering all the surface of
>>> the system.
>> The starting point is here:
>> http://sourceforge.net/apps/trac/gar/browser/csw/mgar/gar/v2/gar.pkg.mk#L716
>> Every other bits of infrastructure read this pkginfo field.
> This I know. What I wish is to inhibit this, when supplying --nmu to
> csw-upload-pkg for an existing package. Where is this code situated?

When you're running csw-upload-pkg, it's too late. All such
information must be inside the package, and that means it has to be
done in GAR. Probably as a field in pkginfo.

>> I want to ask this question. It might sound like a rhetorical one, but
>> it's not: it's one of the central questions to the discussion:
>> Do you become the owner of the package because you are willing to take
>> on the owner's duties, or do you take on the owner's duties because
>> you've become the package owner?
> Neither when I'm doing a NMU.
> Now, let me ask a pragmatical question: what is the reason for which my
> proposition is not worthy of implementation?

But it is! We only need to talk about some details.

I think I understand the idea: you want to be able to contribute
without taking on other associated burden, right? This is definitely
worth implementing.

IIUC, the problem you're addressing is this:

1. When you upload a package, you become the package owner/maintainer.
2. A package owner/maintainer is responsible for everything that's
associated with the package, e.g. any current and future bugs.
3. You have a small contribution to make.
4. The benefit of the contribution does not outweigh the burden.
5. Therefore, you do not make the contribution.

You think that #2 is fine and you want to fix #1.

I think that #1 is fine and I want to fix #2.


More information about the maintainers mailing list