-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sat, Jul 26, 2008 at 9:34 PM, Jonathan Marsden <[EMAIL PROTECTED]> wrote: Michael Casadevall wrote: > As we al know, REVU historically has required you to join > revu-uploaders, and then hunt down an admin to get your key synced or > updated, which I always felt was klunky, and rather clumsy way to do > things. Now that REVU uses Launchpad IDs, it also grabs and > imports/updates GPG keys as needed on each login from the individual > users page, which I find is a much sleeker solution. Definitely :-) Sleeker still would be to also do the import/update of GPG key upon an upload using dput, so that attempted uploads from newcomers "just work" rather than being rejected with no clear notification to the uploader. See LP: #250164 . More generally, making it easier for newcomers who want to contribute to the bug fixing and packaging process like this is IMO well worth the effort; current barriers to entry are somewhat high. There isn't a way I know to get the key from a fingerprint in the changes file. If there is we could look into implementing that. As for silent rejections, that will hopefully be fixed once REVU actually has some concept of a mailing system and learns how to send mails > It was pointed out to me though that having revu-uploaders though > allows people to see how you have to be a member of a special group > to commit to the archive. Could the REVU login code query LP to determine "is this person a member of revu-uploaders", and if the answer is no, display something to the user who is attempting to log in, asking them to please subscribe to that group (maybe include a direct subscribe link to it, even)? This way, you would get the best of both worlds: only one login to manage, no manual keyring sync delays, *and* a "special group" for REVU uploaders, for those who feel that has value. I thought about it, but the only official query to query Launchpad about a group is to read its RDF page, which in the case of revu-uploadres is slightly under a megabyte. Downloading aside, parsing that monster would probably bring spooky to its knees. > This skin is still a work in progress (and a tan option will be made > available soon wish). The colour is less critical (to me) than the overall layout and information being presented. I think the new skin is a useful improvement; I also think you'll meet resistance unless you soon give people a way to set a preference for their REVU skin (theme) of choice. There are plans for that in the work, but I just needed to debrownify it; I felt my life slowly being drowned away in brown. Good work! Jonathan - -- Ubuntu-motu mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: http://getfiregpg.org iD8DBQFIi9SVpblTBJ2i2psRAtCYAJ9GHaru0QhoCgpqIqRdApBF4yYNxwCeIKAY fLqqm5JdfJQW9wF/+Pjb2fY= =8gIC -----END PGP SIGNATURE-----
-- Ubuntu-motu mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
