[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Improving the visibility of LowThresholdNMU



Lucas Nussbaum <lucas@lucas-nussbaum.net> writes:

> Hi,
>
> The LowThresholdNMU wiki page[0] lists maintainers (and packages) for
> which NMUs are welcomed. However, in it's current form, it's quite
> useless: it's very difficult to check if a given package is
> NMU-friendly, since the page is not machine-parseable. Also, since it's
> not very useful and visible, it doesn't provide an incentive for
> maintainers to add themselves to the list: there are probably some
> NMU-friendly maintainers who aren't in that list.
>
> [0] http://wiki.debian.org/LowThresholdNmu
>
> I think that we should improve that:
>
> (1) the list should move to a text file in a VCS. For example, we could
> use a special directory in the collab-maint alioth project, or simply a
> repository writable by all DDs on svn.d.o. This would improve the way
> history is kept too.

I feat that having 'simply a repository writable by all DDs' is not
simple at all. What about non-DD maintainers?

> (2) the list should be machine-readable. 

http://wiki.debian.org/LowThresholdNmu?action=raw is close to machine
readable. Perhaps we can make it that?

> We could use the following
> format:
>   maintainer_email [!]package1, [!]package2, [!]package3
> So we would simply list which packages are NMU-friendly, and use a
> special package '*' to indicate that all packages are NMU-friendly. '!'
> would indicate that a package has to be excluded from the list.
> Example:
>   joe@debian.org *, !bash, !dash
> means that all of joe's packages are NMU-friendly, except bash and dash.
> This format could be extended later: we could use regexps, and maybe add
> comments, like:
>   joe@debian.org *, !/lib.*-perl$/ [those are team-maintained, please
> talk with the pkg-perl team], bash [only for important & RC issues]

Perhaps we could invent a syntax which is able to express the above and
fits in Moin? In doubt, we can make the list preformatted, and put
markers at the beginning and the end.

> (3) make the state visible on the PTS (see #429883). For each package,
> we could have an icon indicating if the package is NMU-friendly or not.
> All packages would have an icon, so having the "NMU-hostile" icon by
> default could help maintainers remember to add themselves to the list.

That's a good idea, perhaps the PTS maintainers could comment what the
best way of integrating the information there would be? Would inventing
a header called 'XS-NMUs-Welcome: yes' in debian/control help here? Does
it make sense otherwise to expose this information in Sources.gz?


-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4

Attachment: pgpiGK9nqi6k7.pgp
Description: PGP signature


Reply to: