On Wed, Jul 11, 2007 at 07:24:21AM +0000, Lucas Nussbaum wrote: > 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.
So, summarizing, we have 2 problems: visibility, machine-readability. I fully agree they are present issues which need to be solved. > (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 fail to see the advantage of this, especially wrt the two problems above. The wiki is easier to access than a VCS (you don't have to checkout) and it already handles history, I don't think full-fledged history management for the LowThresholdNMU page is something we actually need. > (2) the list should be machine-readable. We could use the following > format: Agreed, and I like the format you propose. Why can't we simply change the wiki page to match that format? The wiki page won't be more error prone than a VCS file using the same format. What we need to achieve this is just a volunteer which reviews the current page and converts the current human-readable sentences in machine-readable strings matching your format. The only issue I see with the wiki is security, as anyone can currently edit pages just after the registration, but for the page we are discussing it won't be worst than the present situation. > (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. Agreed, this can be done even in the current state. The PTS can download the raw version of the page, consider only the lines that match your format and ignore the remaining stuff. Besides, I think we can still do more to improve visibility, as neither the wiki solution, nor the VCS based one would increase it above the current status. I would like to see LowThresholdNMU mentioned in the developer's reference (a quick check I made today shown that it's not there, but I may be wrong), anyone up to writing a section and submit a patch? > Is anyone interested in working on that? I will have problems finding > the time in the near future I'm willing to patch the PTS for this, assuming there's an agreement on doing this "the wiki way" as I proposed above. Thanks for this proposal Lucas, Cheers. -- Stefano Zacchiroli -*- PhD in Computer Science ............... now what? [EMAIL PROTECTED],debian.org,bononia.it} -%- http://www.bononia.it/zack/ (15:56:48) Zack: e la demo dema ? /\ All one has to do is hit the (15:57:15) Bac: no, la demo scema \/ right keys at the right time
signature.asc
Description: Digital signature
