| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 03/25/11 17:02, Mike Frysinger wrote: |
| 5 |
> once we move to git, the workflow for proxy maintainers is going to be |
| 6 |
> a lot smoother. the question is how to handle signing with proxy |
| 7 |
> maintainers. |
| 8 |
> |
| 9 |
> it would be nice if said proxied maintainers would sign things and |
| 10 |
> that would be preserved all the way to the push to the common server. |
| 11 |
> pros: |
| 12 |
> - Gentoo dev doing the proxy can pull, look at the commits, and then push |
| 13 |
> cons: |
| 14 |
> - proxied maintainers need to set up pgp too |
| 15 |
> - we need to have another list of keys to accept outside of the |
| 16 |
> existing Gentoo dev list |
| 17 |
> - easy to miss if commit was made through repoman, or on an older tree |
| 18 |
> |
| 19 |
> the other method would be that a Gentoo dev pulls the changesets and |
| 20 |
> then runs `repoman commit` himself. |
| 21 |
> pros: |
| 22 |
> - proxied maintainers need not think of pgp at all |
| 23 |
> - we only need the original Gentoo dev key list |
| 24 |
> - the Gentoo dev knows immediately if there's a repoman problem |
| 25 |
> cons: |
| 26 |
> - workflow not as smooth |
| 27 |
> |
| 28 |
> i thinking about this last bit, i wonder if that could simply be |
| 29 |
> addressed in repoman itself ? we could add a "repoman push" command |
| 30 |
> that compared the remote branch to the local one to find out all the |
| 31 |
> packages that have been updated, go into each one and rebuild just the |
| 32 |
> Manifest, and then do the `git push`. |
| 33 |
> -mike |
| 34 |
> |
| 35 |
|
| 36 |
- From my point of view, we should be using something close to the second |
| 37 |
one regardless. Dev's should be checking the works of proxy committers |
| 38 |
anyway, so running repoman should already be part of that workflow. |
| 39 |
|
| 40 |
Secondly, I like that last idea. Except I'd amend that it should run |
| 41 |
repoman full; warn if anything is wrong, then repoman manifest etc. |
| 42 |
|
| 43 |
- -- |
| 44 |
Dane Smith (c1pher) |
| 45 |
Gentoo Linux Developer -- QA / Crypto / Sunrise / x86 |
| 46 |
RSA Key: http://pgp.mit.edu:11371/pks/lookup?search=0x0C2E1531&op=index |
| 47 |
-----BEGIN PGP SIGNATURE----- |
| 48 |
Version: GnuPG v2.0.17 (GNU/Linux) |
| 49 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 50 |
|
| 51 |
iQIcBAEBAgAGBQJNjQkzAAoJEEsurZwMLhUxiSoP/1Gdxyo2Li43gcSU2piYZZJq |
| 52 |
4DJyujm9NypKrtmQTZuGxRnIsnikBqigKZHBBkDZB3Qw6xZ3vzXrudz7knsREP1H |
| 53 |
BCoinT0G/v8BdiauqIwt7e9kb0qW/NSalTZMd7wRs6oLqfL0UfK2dI0ubHUYw/ag |
| 54 |
bS3E5TfzoKY0KYYAWjXoztyXb5cHA1+H9O2kuWOqJDyHRmYijrnj55spTST0D4my |
| 55 |
n2gL3rpZMfnfQJskyvt6o/NUqLakekdITrJeCuiOY9fSEORgZYlsu5R9oTPCRv9p |
| 56 |
qnLzncwWgUhYh7g99xMMC+JkAPcItxe8nkcfP9GIf6zM8ai1pRbhV7iYqJbunTlA |
| 57 |
ZvsgCjk99tS+qkmTIZsMOcGQZg9D33Y+Yb0DGILmoCVybvse50HAMyGzir6rn+s2 |
| 58 |
UzKLtAkj2gHTYkEw6KwngUXRr7VtMfk8exzpu3OYwiOAsz1RP+wfExeXetcYU6wK |
| 59 |
fhfHbqXiBXOU5FbZ96MMnsl+Qs8A8So2+93JbHiG7oHdWZ85E/snI35Z6/WEUsvr |
| 60 |
jxZrTuzH+TTGu3cFSHjCt2Ugn6t9tF4Fi67W+MoHX5avgHyrE/WSe+QiRsquB5oh |
| 61 |
W411aMHAJAdyfDcH87WRMVKIRuUAy0tTT9qzAtiu7/tJnaKt9Chg0Awbk0meiFmz |
| 62 |
p1FBIzzv6bJATmFPF8Hd |
| 63 |
=ZUSv |
| 64 |
-----END PGP SIGNATURE----- |
Archives