-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As discussed in last week's meeting, I'm proposing myself as a trust seed for this team. Here's what that means, why me, and what it does for us. Full consensus requested, please: +1, +0, or -1 (latter with reasoning included.) We need to make the leap with this project and begin trusting each other enough to share root/sudo access on production servers[1]. By a "trust seed" I mean, a person who all others involved trust in deciding who else to trust. As a seed, it's a one time thing - once created, the initial trust circle will decide for itself how to perpetuate, i.e., how to add new people in to the trust circle. Regarding my qualifications for being trusted and extending trust, some supporting points: * Some of you have met me in person, at the initial oVirt workshop and other locations. * Demonstrated involvement in oVirt (presuming my wiki and GPG accounts are not compromised, I have commit and email history to show involvement.) * Trust in Red Hat can extend to me, based on my 10+ years employment, etc. * Presence and positions of trust in other open source projects, namely the Fedora Project. * Experience working in Fedora Infrastructure as part of a distance team of people who have never all met in person. * Handful of videos of me talking at conferences, identified by name, and so forth. I can provide references for the above, if requested. Thanks - Karsten [1] If we move to OpenShift (or similar), then the admin access is who has keys to update the app on OpenShift; ultimately the same trust issues need to be resolved. - -- Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFP+7Eb2ZIOBq0ODEERAtCNAJ4zM91Pk9LsItsYXG6eU2x+HZHspACeJ8hy NGj6y7NSOuHVcPqYsxX9UCI= =16JZ -----END PGP SIGNATURE-----
On 07/10/2012 12:35 AM, Karsten 'quaid' Wade wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
As discussed in last week's meeting, I'm proposing myself as a trust seed for this team. Here's what that means, why me, and what it does for us. Full consensus requested, please: +1, +0, or -1 (latter with reasoning included.)
We need to make the leap with this project and begin trusting each other enough to share root/sudo access on production servers[1]. By a "trust seed" I mean, a person who all others involved trust in deciding who else to trust. As a seed, it's a one time thing - once created, the initial trust circle will decide for itself how to perpetuate, i.e., how to add new people in to the trust circle.
Regarding my qualifications for being trusted and extending trust, some supporting points:
* Some of you have met me in person, at the initial oVirt workshop and other locations. * Demonstrated involvement in oVirt (presuming my wiki and GPG accounts are not compromised, I have commit and email history to show involvement.) * Trust in Red Hat can extend to me, based on my 10+ years employment, etc. * Presence and positions of trust in other open source projects, namely the Fedora Project. * Experience working in Fedora Infrastructure as part of a distance team of people who have never all met in person. * Handful of videos of me talking at conferences, identified by name, and so forth.
I can provide references for the above, if requested. +1
I personally believe the current team should be grandfathered in. I think moving forward is were we as a team need to be thinking about who gets added in. Thanks Robert
Thanks - Karsten
[1] If we move to OpenShift (or similar), then the admin access is who has keys to update the app on OpenShift; ultimately the same trust issues need to be resolved. - -- Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFP+7Eb2ZIOBq0ODEERAtCNAJ4zM91Pk9LsItsYXG6eU2x+HZHspACeJ8hy NGj6y7NSOuHVcPqYsxX9UCI= =16JZ -----END PGP SIGNATURE----- _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
On 07/10/2012 09:00 AM, Robert Middleswarth wrote:
On 07/10/2012 12:35 AM, Karsten 'quaid' Wade wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
As discussed in last week's meeting, I'm proposing myself as a trust seed for this team. Here's what that means, why me, and what it does for us. Full consensus requested, please: +1, +0, or -1 (latter with reasoning included.)
We need to make the leap with this project and begin trusting each other enough to share root/sudo access on production servers[1]. By a "trust seed" I mean, a person who all others involved trust in deciding who else to trust. As a seed, it's a one time thing - once created, the initial trust circle will decide for itself how to perpetuate, i.e., how to add new people in to the trust circle.
Regarding my qualifications for being trusted and extending trust, some supporting points:
* Some of you have met me in person, at the initial oVirt workshop and other locations. * Demonstrated involvement in oVirt (presuming my wiki and GPG accounts are not compromised, I have commit and email history to show involvement.) * Trust in Red Hat can extend to me, based on my 10+ years employment, etc. * Presence and positions of trust in other open source projects, namely the Fedora Project. * Experience working in Fedora Infrastructure as part of a distance team of people who have never all met in person. * Handful of videos of me talking at conferences, identified by name, and so forth.
I can provide references for the above, if requested. +1
I personally believe the current team should be grandfathered in. I think moving forward is were we as a team need to be thinking about who gets added in.
+1 to both
----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "Robert Middleswarth" <robert@middleswarth.net> Cc: "infra" <infra@ovirt.org> Sent: Tuesday, July 10, 2012 9:09:05 AM Subject: Re: Trust seed
On 07/10/2012 09:00 AM, Robert Middleswarth wrote:
On 07/10/2012 12:35 AM, Karsten 'quaid' Wade wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
As discussed in last week's meeting, I'm proposing myself as a trust seed for this team. Here's what that means, why me, and what it does for us. Full consensus requested, please: +1, +0, or -1 (latter with reasoning included.)
We need to make the leap with this project and begin trusting each other enough to share root/sudo access on production servers[1]. By a "trust seed" I mean, a person who all others involved trust in deciding who else to trust. As a seed, it's a one time thing - once created, the initial trust circle will decide for itself how to perpetuate, i.e., how to add new people in to the trust circle.
Regarding my qualifications for being trusted and extending trust, some supporting points:
* Some of you have met me in person, at the initial oVirt workshop and other locations. * Demonstrated involvement in oVirt (presuming my wiki and GPG accounts are not compromised, I have commit and email history to show involvement.) * Trust in Red Hat can extend to me, based on my 10+ years employment, etc. * Presence and positions of trust in other open source projects, namely the Fedora Project. * Experience working in Fedora Infrastructure as part of a distance team of people who have never all met in person. * Handful of videos of me talking at conferences, identified by name, and so forth.
I can provide references for the above, if requested. +1
I personally believe the current team should be grandfathered in. I think moving forward is were we as a team need to be thinking about who gets added in.
+1 to both
+1, looking forward to see the infra team & its resources grow and develop.
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Hi, On 07/10/2012 08:00 AM, Robert Middleswarth wrote:
On 07/10/2012 12:35 AM, Karsten 'quaid' Wade wrote:
As discussed in last week's meeting, I'm proposing myself as a trust seed for this team. Here's what that means, why me, and what it does for us. Full consensus requested, please: +1, +0, or -1 (latter with reasoning included.)
+1
I personally believe the current team should be grandfathered in. I think moving forward is were we as a team need to be thinking about who gets added in.
+1, and +1 also to seeding the team initially with the current ppl doing sysadmin work, as Robert suggests. Cheers, Dave. -- Dave Neary Community Action and Impact Open Source and Standards Team, Red Hat Phone: +33 9 50 71 55 62
On Tue, Jul 10, 2012 at 11:58:19AM +0200, Dave Neary wrote:
On 07/10/2012 08:00 AM, Robert Middleswarth wrote:
On 07/10/2012 12:35 AM, Karsten 'quaid' Wade wrote:
As discussed in last week's meeting, I'm proposing myself as a trust seed for this team. Here's what that means, why me, and what it does for us. Full consensus requested, please: +1, +0, or -1 (latter with reasoning included.)
+1
I personally believe the current team should be grandfathered in. I think moving forward is were we as a team need to be thinking about who gets added in.
+1, and +1 also to seeding the team initially with the current ppl doing sysadmin work, as Robert suggests.
+1, I think those already doing work have proven themselves and as we gradually move towards configs in git we can introduce more fine grained access.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/10/2012 03:03 AM, Ewoud Kohl van Wijngaarden wrote:
On Tue, Jul 10, 2012 at 11:58:19AM +0200, Dave Neary wrote:
On 07/10/2012 08:00 AM, Robert Middleswarth wrote:
On 07/10/2012 12:35 AM, Karsten 'quaid' Wade wrote:
As discussed in last week's meeting, I'm proposing myself as a trust seed for this team. Here's what that means, why me, and what it does for us. Full consensus requested, please: +1, +0, or -1 (latter with reasoning included.)
+1
I personally believe the current team should be grandfathered in. I think moving forward is were we as a team need to be thinking about who gets added in.
+1, and +1 also to seeding the team initially with the current ppl doing sysadmin work, as Robert suggests.
+1, I think those already doing work have proven themselves and as we gradually move towards configs in git we can introduce more fine grained access.
+1 Basically, that's my scheme - start with the current team who has been thinking and caring about Infra. My eye sees Ewoud Kohl van Wijngaarden, Mike Burns, Robert Middleswarth, Eyal Edri, Itamar Heim, and Moran Goldboim. Am I missing anyone? Someone doing Infrastructure work in Tel Aviv who needs to be included? Thanks - Karsten - -- Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFP/Elj2ZIOBq0ODEERAkMjAJ9VaQ8gbQ/KX/0oqhOBceKFgXk6zQCgl0or tOvp6Bbk1BIFYu9tatKIHQI= =KGAK -----END PGP SIGNATURE-----
On Tue, 2012-07-10 at 08:25 -0700, Karsten 'quaid' Wade wrote:
On 07/10/2012 03:03 AM, Ewoud Kohl van Wijngaarden wrote:
On Tue, Jul 10, 2012 at 11:58:19AM +0200, Dave Neary wrote:
On 07/10/2012 08:00 AM, Robert Middleswarth wrote:
On 07/10/2012 12:35 AM, Karsten 'quaid' Wade wrote:
As discussed in last week's meeting, I'm proposing myself as a trust seed for this team. Here's what that means, why me, and what it does for us. Full consensus requested, please: +1, +0, or -1 (latter with reasoning included.)
+1
I personally believe the current team should be grandfathered in. I think moving forward is were we as a team need to be thinking about who gets added in.
+1, and +1 also to seeding the team initially with the current ppl doing sysadmin work, as Robert suggests.
+1, I think those already doing work have proven themselves and as we gradually move towards configs in git we can introduce more fine grained access.
+1
Basically, that's my scheme - start with the current team who has been thinking and caring about Infra. My eye sees Ewoud Kohl van Wijngaarden, Mike Burns, Robert Middleswarth, Eyal Edri, Itamar Heim, and Moran Goldboim.
Ofer should be on this list too...
Am I missing anyone? Someone doing Infrastructure work in Tel Aviv who needs to be included?
Thanks - Karsten _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/10/2012 08:30 AM, Mike Burns wrote:
On Tue, 2012-07-10 at 08:25 -0700, Karsten 'quaid' Wade wrote:
Basically, that's my scheme - start with the current team who has been thinking and caring about Infra. My eye sees Ewoud Kohl van Wijngaarden, Mike Burns, Robert Middleswarth, Eyal Edri, Itamar Heim, and Moran Goldboim.
Ofer should be on this list too...
D'oh! Thanks, added. - - Karsten-- Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFP/Ew72ZIOBq0ODEERAopXAKCE3Ac6Iv35gmpnuAKVs46xIaWp1QCg2wgQ uPX/VMxM23CCcgALGm/QY1I= =QpyL -----END PGP SIGNATURE-----
On 07/10/2012 11:25 AM, Karsten 'quaid' Wade wrote:
Basically, that's my scheme - start with the current team who has been thinking and caring about Infra. My eye sees Ewoud Kohl van Wijngaarden, Mike Burns, Robert Middleswarth, Eyal Edri, Itamar Heim, and Moran Goldboim.
Am I missing anyone? Someone doing Infrastructure work in Tel Aviv who needs to be included?
I'm good with this, and please send a mail to the board@ once list is finalized for notification and ack. Carl.
On 07/10/2012 12:35 AM, Karsten 'quaid' Wade wrote: +1
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
As discussed in last week's meeting, I'm proposing myself as a trust seed for this team. Here's what that means, why me, and what it does for us. Full consensus requested, please: +1, +0, or -1 (latter with reasoning included.)
We need to make the leap with this project and begin trusting each other enough to share root/sudo access on production servers[1]. By a "trust seed" I mean, a person who all others involved trust in deciding who else to trust. As a seed, it's a one time thing - once created, the initial trust circle will decide for itself how to perpetuate, i.e., how to add new people in to the trust circle.
Regarding my qualifications for being trusted and extending trust, some supporting points:
* Some of you have met me in person, at the initial oVirt workshop and other locations. * Demonstrated involvement in oVirt (presuming my wiki and GPG accounts are not compromised, I have commit and email history to show involvement.) * Trust in Red Hat can extend to me, based on my 10+ years employment, etc. * Presence and positions of trust in other open source projects, namely the Fedora Project. * Experience working in Fedora Infrastructure as part of a distance team of people who have never all met in person. * Handful of videos of me talking at conferences, identified by name, and so forth.
I can provide references for the above, if requested.
Thanks - Karsten
[1] If we move to OpenShift (or similar), then the admin access is who has keys to update the app on OpenShift; ultimately the same trust issues need to be resolved. - -- Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFP+7Eb2ZIOBq0ODEERAtCNAJ4zM91Pk9LsItsYXG6eU2x+HZHspACeJ8hy NGj6y7NSOuHVcPqYsxX9UCI= =16JZ -----END PGP SIGNATURE----- _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- It's not my fault that I can't draw the human posterior with a mouse.
On 10/07/12 07:35, Karsten 'quaid' Wade wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
As discussed in last week's meeting, I'm proposing myself as a trust seed for this team. Here's what that means, why me, and what it does for us. Full consensus requested, please: +1, +0, or -1 (latter with reasoning included.)
We need to make the leap with this project and begin trusting each other enough to share root/sudo access on production servers[1]. By a "trust seed" I mean, a person who all others involved trust in deciding who else to trust. As a seed, it's a one time thing - once created, the initial trust circle will decide for itself how to perpetuate, i.e., how to add new people in to the trust circle.
Regarding my qualifications for being trusted and extending trust, some supporting points:
* Some of you have met me in person, at the initial oVirt workshop and other locations. * Demonstrated involvement in oVirt (presuming my wiki and GPG accounts are not compromised, I have commit and email history to show involvement.) * Trust in Red Hat can extend to me, based on my 10+ years employment, etc. * Presence and positions of trust in other open source projects, namely the Fedora Project. * Experience working in Fedora Infrastructure as part of a distance team of people who have never all met in person. * Handful of videos of me talking at conferences, identified by name, and so forth.
I can provide references for the above, if requested.
Thanks - Karsten
+1, Karsten I think you are doing a great work in ovirt in general and I wish you luck making the infra sub-project a successful one. I would like to suggest that Moran Goldboim would also be included in the trust seed of the infra project. I think Moran is doing a lot of work in oVirt, he is well familiar in the oVirt community and has a lot of knowledge to contribute to the infra sub-project. Livnat
[1] If we move to OpenShift (or similar), then the admin access is who has keys to update the app on OpenShift; ultimately the same trust issues need to be resolved. - -- Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFP+7Eb2ZIOBq0ODEERAtCNAJ4zM91Pk9LsItsYXG6eU2x+HZHspACeJ8hy NGj6y7NSOuHVcPqYsxX9UCI= =16JZ -----END PGP SIGNATURE----- _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
On Tue, 2012-07-10 at 15:52 +0300, Livnat Peer wrote:
On 10/07/12 07:35, Karsten 'quaid' Wade wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
As discussed in last week's meeting, I'm proposing myself as a trust seed for this team. Here's what that means, why me, and what it does for us. Full consensus requested, please: +1, +0, or -1 (latter with reasoning included.)
We need to make the leap with this project and begin trusting each other enough to share root/sudo access on production servers[1]. By a "trust seed" I mean, a person who all others involved trust in deciding who else to trust. As a seed, it's a one time thing - once created, the initial trust circle will decide for itself how to perpetuate, i.e., how to add new people in to the trust circle.
Regarding my qualifications for being trusted and extending trust, some supporting points:
* Some of you have met me in person, at the initial oVirt workshop and other locations. * Demonstrated involvement in oVirt (presuming my wiki and GPG accounts are not compromised, I have commit and email history to show involvement.) * Trust in Red Hat can extend to me, based on my 10+ years employment, etc. * Presence and positions of trust in other open source projects, namely the Fedora Project. * Experience working in Fedora Infrastructure as part of a distance team of people who have never all met in person. * Handful of videos of me talking at conferences, identified by name, and so forth.
I can provide references for the above, if requested.
Thanks - Karsten
+1, Karsten I think you are doing a great work in ovirt in general and I wish you luck making the infra sub-project a successful one.
+1 to Karsten being the initial seed and +1 to other infra members being grandfathered.
I would like to suggest that Moran Goldboim would also be included in the trust seed of the infra project.
I think Moran is doing a lot of work in oVirt, he is well familiar in the oVirt community and has a lot of knowledge to contribute to the infra sub-project.
My only question here is whether Moran has already done work in the infra team. There is certainly work done in other projects, but not much in the infra team that I recall. Perhaps add Moran as the first or second person through the process? Mike
Livnat
[1] If we move to OpenShift (or similar), then the admin access is who has keys to update the app on OpenShift; ultimately the same trust issues need to be resolved. - -- Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFP+7Eb2ZIOBq0ODEERAtCNAJ4zM91Pk9LsItsYXG6eU2x+HZHspACeJ8hy NGj6y7NSOuHVcPqYsxX9UCI= =16JZ -----END PGP SIGNATURE----- _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/10/2012 07:13 AM, Mike Burns wrote:
On 10/07/12 07:35, Karsten 'quaid' Wade wrote: As discussed in last week's meeting, I'm proposing myself as a
On Tue, 2012-07-10 at 15:52 +0300, Livnat Peer wrote: trust seed for this team. Here's what that means, why me, and what it does for us. Full consensus requested, please: +1, +0, or -1 (latter with reasoning included.)
We need to make the leap with this project and begin trusting each other enough to share root/sudo access on production servers[1]. By a "trust seed" I mean, a person who all others involved trust in deciding who else to trust. As a seed, it's a one time thing - once created, the initial trust circle will decide for itself how to perpetuate, i.e., how to add new people in to the trust circle.
Regarding my qualifications for being trusted and extending trust, some supporting points:
* Some of you have met me in person, at the initial oVirt workshop and other locations. * Demonstrated involvement in oVirt (presuming my wiki and GPG accounts are not compromised, I have commit and email history to show involvement.) * Trust in Red Hat can extend to me, based on my 10+ years employment, etc. * Presence and positions of trust in other open source projects, namely the Fedora Project. * Experience working in Fedora Infrastructure as part of a distance team of people who have never all met in person. * Handful of videos of me talking at conferences, identified by name, and so forth.
I can provide references for the above, if requested.
Thanks - Karsten
+1, Karsten I think you are doing a great work in ovirt in general and I wish you luck making the infra sub-project a successful one.
+1 to Karsten being the initial seed and +1 to other infra members being grandfathered.
I would like to suggest that Moran Goldboim would also be included in the trust seed of the infra project.
I think Moran is doing a lot of work in oVirt, he is well familiar in the oVirt community and has a lot of knowledge to contribute to the infra sub-project.
My only question here is whether Moran has already done work in the infra team. There is certainly work done in other projects, but not much in the infra team that I recall. Perhaps add Moran as the first or second person through the process?
I added Moran to my list just in case - I want to be sure we don't get in the way of work anyone is doing already, even if we aren't aware of it. By this I mean, some folks may be doing infrastructure work but haven't been making noise about that work; if that's happening, let's find a way to include such folks. Perhaps as you say, Moran and others could go through an Infra Team joining process, as long as that doesn't interfere with his ability to work? - - Karsten - -- Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFP/Eno2ZIOBq0ODEERAjfqAJ9SJRcQ8aHzxhqLqGhn/m0VMrWuZQCfR4Hb d0qUj6m1RY+6RXQvJNn+JS8= =a9sr -----END PGP SIGNATURE-----
On Tue, 2012-07-10 at 08:27 -0700, Karsten 'quaid' Wade wrote:
On 07/10/2012 07:13 AM, Mike Burns wrote:
On 10/07/12 07:35, Karsten 'quaid' Wade wrote: As discussed in last week's meeting, I'm proposing myself as a
On Tue, 2012-07-10 at 15:52 +0300, Livnat Peer wrote: trust seed for this team. Here's what that means, why me, and what it does for us. Full consensus requested, please: +1, +0, or -1 (latter with reasoning included.)
We need to make the leap with this project and begin trusting each other enough to share root/sudo access on production servers[1]. By a "trust seed" I mean, a person who all others involved trust in deciding who else to trust. As a seed, it's a one time thing - once created, the initial trust circle will decide for itself how to perpetuate, i.e., how to add new people in to the trust circle.
Regarding my qualifications for being trusted and extending trust, some supporting points:
* Some of you have met me in person, at the initial oVirt workshop and other locations. * Demonstrated involvement in oVirt (presuming my wiki and GPG accounts are not compromised, I have commit and email history to show involvement.) * Trust in Red Hat can extend to me, based on my 10+ years employment, etc. * Presence and positions of trust in other open source projects, namely the Fedora Project. * Experience working in Fedora Infrastructure as part of a distance team of people who have never all met in person. * Handful of videos of me talking at conferences, identified by name, and so forth.
I can provide references for the above, if requested.
Thanks - Karsten
+1, Karsten I think you are doing a great work in ovirt in general and I wish you luck making the infra sub-project a successful one.
+1 to Karsten being the initial seed and +1 to other infra members being grandfathered.
I would like to suggest that Moran Goldboim would also be included in the trust seed of the infra project.
I think Moran is doing a lot of work in oVirt, he is well familiar in the oVirt community and has a lot of knowledge to contribute to the infra sub-project.
My only question here is whether Moran has already done work in the infra team. There is certainly work done in other projects, but not much in the infra team that I recall. Perhaps add Moran as the first or second person through the process?
I added Moran to my list just in case - I want to be sure we don't get in the way of work anyone is doing already, even if we aren't aware of it. By this I mean, some folks may be doing infrastructure work but haven't been making noise about that work; if that's happening, let's find a way to include such folks. Perhaps as you say, Moran and others could go through an Infra Team joining process, as long as that doesn't interfere with his ability to work?
Sure, that's fine. Moran is pretty easy to accept anyway give the @redhat.com email address... Mike
- Karsten _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Hi, On 07/10/2012 05:30 PM, Mike Burns wrote:
Sure, that's fine. Moran is pretty easy to accept anyway give the @redhat.com email address...
...although of course we don't want to start setting a different bar for people with and without @redhat.com addresses. I'd suggest that Moran is easier to trust because he's endorsed by Livnat, who we know and trust, but I'd say it would be better to have him join the oVirt infra team at the point where not being part of the team prevents him from doing something useful. And of course, whatever bar we set for Moran, we should have the same bar for others (so, for example, if tomorrow RobertM proposes adding someone to the team who has not previously worked on infra, this situation would be a precedent). Cheers, Dave. -- Dave Neary Community Action and Impact Open Source and Standards Team, Red Hat Phone: +33 9 50 71 55 62
On 07/10/2012 07:20 PM, Dave Neary wrote:
Hi,
On 07/10/2012 05:30 PM, Mike Burns wrote:
Sure, that's fine. Moran is pretty easy to accept anyway give the @redhat.com email address...
...although of course we don't want to start setting a different bar for people with and without @redhat.com addresses.
I'd suggest that Moran is easier to trust because he's endorsed by Livnat, who we know and trust, but I'd say it would be better to have him join the oVirt infra team at the point where not being part of the team prevents him from doing something useful.
And of course, whatever bar we set for Moran, we should have the same bar for others (so, for example, if tomorrow RobertM proposes adding someone to the team who has not previously worked on infra, this situation would be a precedent).
Cheers, Dave.
great to see i'm used as a case study. true, I was a part of oVirt work on different aspects till now, less on the infra front directly. i would be happy to help on oVirt infra if the chance would be given to me.
Hi Moran, On 07/10/2012 07:55 PM, Moran Goldboim wrote:
great to see i'm used as a case study.
:) I hope you don't mind!
true, I was a part of oVirt work on different aspects till now, less on the infra front directly. i would be happy to help on oVirt infra if the chance would be given to me.
The idea, I hope, is that everyone has the opportunity to help on oVirt infra - our challenge is to figure out how to enable people to contribute without having root access to oVirt machines, and thus allow them to build the trust of the infra team. So whatever happens, you will have the chance to help on oVirt infra. Thank you for your offer! Cheers, Dave. -- Dave Neary Community Action and Impact Open Source and Standards Team, Red Hat Phone: +33 9 50 71 55 62
participants (11)
-
Carl Trieloff -
Dave Neary -
Ewoud Kohl van Wijngaarden -
Eyal Edri -
Itamar Heim -
Joseph B. Ottinger -
Karsten 'quaid' Wade -
Livnat Peer -
Mike Burns -
Moran Goldboim -
Robert Middleswarth