On Sun, 2008-08-17 at 18:14 -0500, Dan McGee wrote:
On Sun, Aug 17, 2008 at 2:23 PM, Eduardo Romero <k3nsai@gmail.com> wrote:
2008/8/17 Thayer Williams <thayer@archlinux.org>:
On Sat, Aug 16, 2008 at 10:50 AM, Dusty Phillips <buchuki@gmail.com> wrote:
Esteemed ArchLinux Developers,
Partially because Aaron asked for it and thinks it is cool and partially because all those [signoff] e-mails in my inbox are kind of boring to me (as a non-packager), I have implemented a web based signoff mechanism into archweb_dev.
Nice work! I think this is a great idea too.
I only see one potential problem...what if someone accidentaly clicks signoff on the wrong package? For instance, I didn't really test the cracklib, but I couldn't resist the urge to click it!
I can easily add 'unsignoff' functionality, but I'm not sure its necessary; this isn't the general public we're talking about and an e-mail to the maintainer saying "Ignore my signoff on package x" might suffice.
But its up to you guys, its probably a matter of 10 minutes to add a view for removing a signoff.
Dusty Well, that would be a great addition, and also, packages from core are
On Sun, 2008-08-17 at 13:39 -0400, Dusty Phillips wrote: the only ones supposed to be put through the signoff proccess. I know this one might be a bit harder to implement, maybe not.
If it goes through testing, I don't think anyone is going to object to others signing off on it- if anything it will reassure them that everything went OK.
The rule is not "only core packages get signed off on", the rule is "core packages *must* get signed off on".
-Dan OK, got it, I think there is a lot of catching up I have to do.