[csw-maintainers] Non-Maintainer Uploads (NMUs)
yann at pleiades.fr.eu.org
Mon Aug 12 16:20:16 CEST 2013
Yes I agree, but if (2 != 3), I think 2 is more important than 3.
So I am just saying that it's better to work on storing 2 rather than 3 and
it's better to embed the information in the package itself.
Currently, I think pretty much everything in the database can be retrieved
from the content of a package (Maciej, do you confirm ?) and I think it's
more reliable that way.
Also if we set some rules one day related to NMU (like updating a
changelog), it would be easier to check them if the information is stored
in the package.
BTW, I also think we should debate on point #2 raised by Maciej before
"2. A package owner/maintainer is responsible for everything that's associated
with the package, e.g. any current and future bugs."
Because depending on the outcome, we may not need at all to implement what
you are trying to do.
2013/8/12 Peter FELECAN <pfelecan at opencsw.org>
> Yann Rouillard <yann at pleiades.fr.eu.org> writes:
> > I am not sure using the http protocol is the best way here.
> We are trying to solve the blocking issue which can make the proposed
> modification easy. So, it's a way. Probably not unique or best.
> > I think we don't really care about the uploader, we rather care about who
> > rebuilt the package.
> > Because he's the one who knows what modification was made.
> > So I think it makes more sense to put that information in the package (in
> > pkginfo) at package build time, rather that trying to find it at upload
> > time from the authorization layer (even if usually uploader = last
> > builder).
> This is another solution if it doesn't change the ownership of the
> From my point of view, there are 4 user related information:
> 1. the user who modified the recipe
> 2. the user who built the package
> 3. the user who uploaded the package
> 4. the user who owns the package, from Mantis stand point
> Most of the time 1 == 2 == 3 == 4 (nice isn't it?)
> Sometimes 1 != 2 == 3 != 4
> And other combinations...
> Now, I'm not saying the we must collect all this. What I'm saying is
> that the values can be different and not always inferred from each other.
> With the exception of 3, all the values can be contained by the
> package. And exactly 3 is the NMU finalization.
> maintainers mailing list
> maintainers at lists.opencsw.org
> .:: This mailing list's archive is public. ::.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the maintainers