On Mon, Jul 14, 2008 at 03:39:42PM +0300, Riku Voipio wrote: > 1) buildd maintainers not caring to send updates (see s390 n-f-u) > 2) maintainers frustrated due changes not happening timely > 3) p-a-s full of aging cruft.
I'm not sure that the "aging cruft" is in fact (1) aging, or (2) cruft. PaS gets used for builds of even oldstable, so aging things out early doesn't really help anything. Having the old history there doesn't hurt anything, other than maybe burning a few extra cycles on the wanna-build host. > Suggested improvements that could help the situation: > 1) Make p-a-s contact address mailing list, or handle requests via > BTS > - similar to removal requests against ftp.d.o An alias that expands to the PaS maintainer list would be a good thing, IMO. > 2) Provide a easy to merge default format for change requests > - if p-a-s were to be put in git, these could be patches in > form of git-format-patch 2a) Document the criteria for accepting patches. Many patches are simply someone's wishlist of things they think should change, absent any input from either the maintainer or the porting team for the affected architecture(s). > 3) Expand the group of people who can change the file > - ftp assistants? buildd admins? More chefs is not always the right answer. lamont -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
