Hi, My name is Douglas Schilling Landgraf, I work for Red Hat to provide improvements for VDSM/oVirt. I have noticed that jenkins vdsm_unit_tests project failed because of a package dependency. If possible, can I have access to jenkins slaves to help maintain this VDSM test project? Thanks! -- Cheers Douglas
Hi Douglas, If any dependency is missing you can always send an email to infra@ovirt.org and request to install it. As for getting access to Jenkins slaves in ovirt -> that requires being a member of the infra team and approval of its memebers/trust seeds. If you feel you want to contribute to the oVirt infra team, please send a request to infra@ovirt.org with some background (team, project, redhat exp,etc...). for now, please provide the missing rpms you know are failing the tests and i'll look into fixing it. thanks, Eyal Edri ----- Original Message -----
From: "Douglas Landgraf" <dougsland@redhat.com> To: infra@ovirt.org Cc: "Barak Azulay" <bazulay@redhat.com> Sent: Monday, July 9, 2012 5:29:37 PM Subject: jenkins slaves
Hi,
My name is Douglas Schilling Landgraf, I work for Red Hat to provide improvements for VDSM/oVirt. I have noticed that jenkins vdsm_unit_tests project failed because of a package dependency. If possible, can I have access to jenkins slaves to help maintain this VDSM test project?
Thanks!
-- Cheers Douglas
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Hi Eyal, On 07/10/2012 02:53 AM, Eyal Edri wrote:
Hi Douglas,
If any dependency is missing you can always send an email to infra@ovirt.org and request to install it. ok As for getting access to Jenkins slaves in ovirt -> that requires being a member of the infra team and approval of its memebers/trust seeds.
If you feel you want to contribute to the oVirt infra team, please send a request to infra@ovirt.org with some background (team, project, redhat exp,etc...). hum, could you please provide a detailed example?
for now, please provide the missing rpms you know are failing the tests and i'll look into fixing it.
Can you please confirm if cherrypy (and all dependencies) is installed? (As Dan pointed)
thanks,
Eyal Edri
Thanks!
----- Original Message -----
From: "Douglas Landgraf"<dougsland@redhat.com> To: infra@ovirt.org Cc: "Barak Azulay"<bazulay@redhat.com> Sent: Monday, July 9, 2012 5:29:37 PM Subject: jenkins slaves
Hi,
My name is Douglas Schilling Landgraf, I work for Red Hat to provide improvements for VDSM/oVirt. I have noticed that jenkins vdsm_unit_tests project failed because of a package dependency. If possible, can I have access to jenkins slaves to help maintain this VDSM test project?
Thanks!
-- Cheers Douglas
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Cheers Douglas
----- Original Message -----
From: "Douglas Landgraf" <dougsland@redhat.com> To: "Eyal Edri" <eedri@redhat.com> Cc: "Barak Azulay" <bazulay@redhat.com>, infra@ovirt.org Sent: Wednesday, July 11, 2012 8:41:04 AM Subject: Re: jenkins slaves
Hi Eyal,
On 07/10/2012 02:53 AM, Eyal Edri wrote:
Hi Douglas,
If any dependency is missing you can always send an email to infra@ovirt.org and request to install it. ok As for getting access to Jenkins slaves in ovirt -> that requires being a member of the infra team and approval of its memebers/trust seeds.
If you feel you want to contribute to the oVirt infra team, please send a request to infra@ovirt.org with some background (team, project, redhat exp,etc...). hum, could you please provide a detailed example?
Guys, do we have a formal way of accepting new people to the infra team? what should the do, what kind of background the need to provide? is it enough if they work in one the supporting companies?
for now, please provide the missing rpms you know are failing the tests and i'll look into fixing it.
Can you please confirm if cherrypy (and all dependencies) is installed? (As Dan pointed)
thanks,
Eyal Edri
Thanks!
----- Original Message -----
From: "Douglas Landgraf"<dougsland@redhat.com> To: infra@ovirt.org Cc: "Barak Azulay"<bazulay@redhat.com> Sent: Monday, July 9, 2012 5:29:37 PM Subject: jenkins slaves
Hi,
My name is Douglas Schilling Landgraf, I work for Red Hat to provide improvements for VDSM/oVirt. I have noticed that jenkins vdsm_unit_tests project failed because of a package dependency. If possible, can I have access to jenkins slaves to help maintain this VDSM test project?
Thanks!
-- Cheers Douglas
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Cheers Douglas
Hi, On 07/11/2012 09:58 AM, Eyal Edri wrote:
Guys, do we have a formal way of accepting new people to the infra team? what should the do, what kind of background the need to provide? is it enough if they work in one the supporting companies?
That's what Karsten, Robert, Mike, Itamar, you and others are working on at the moment (between the mission statement, the "trust seed", managing configs with Puppet, and we still need to figure out how we can graduate involvement and trust so that people not on the team can make positive contributions and thus build reputation and join the team. Cheers, Dave. -- Dave Neary Community Action and Impact Open Source and Standards Team, Red Hat Phone: +33 9 50 71 55 62
----- Original Message -----
From: "Dave Neary" <dneary@redhat.com> To: infra@ovirt.org Sent: Wednesday, July 11, 2012 11:45:12 AM Subject: Re: jenkins slaves
Hi,
On 07/11/2012 09:58 AM, Eyal Edri wrote:
Guys, do we have a formal way of accepting new people to the infra team? what should the do, what kind of background the need to provide? is it enough if they work in one the supporting companies?
That's what Karsten, Robert, Mike, Itamar, you and others are working on at the moment (between the mission statement, the "trust seed", managing configs with Puppet, and we still need to figure out how we can graduate involvement and trust so that people not on the team can make positive contributions and thus build reputation and join the team.
So what should i answer Douglas in meantime until we'll figure this out? so he won't run away, and we'll have another infra member contributing :)
Cheers, Dave.
-- Dave Neary Community Action and Impact Open Source and Standards Team, Red Hat Phone: +33 9 50 71 55 62
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/11/2012 01:49 AM, Eyal Edri wrote:
----- Original Message -----
From: "Dave Neary" <dneary@redhat.com> To: infra@ovirt.org Sent: Wednesday, July 11, 2012 11:45:12 AM Subject: Re: jenkins slaves
Hi,
On 07/11/2012 09:58 AM, Eyal Edri wrote:
Guys, do we have a formal way of accepting new people to the infra team? what should the do, what kind of background the need to provide? is it enough if they work in one the supporting companies?
That's what Karsten, Robert, Mike, Itamar, you and others are working on at the moment (between the mission statement, the "trust seed", managing configs with Puppet, and we still need to figure out how we can graduate involvement and trust so that people not on the team can make positive contributions and thus build reputation and join the team.
So what should i answer Douglas in meantime until we'll figure this out? so he won't run away, and we'll have another infra member contributing :)
I tried to tackle that in a reply to him. Basically, he's arrived while we are figuring stuff out, but anything he can do to help without sudo access is a way of contributing. Thus, just asking the initial question is a good step, and if he sticks with the problem until it's resolved, that's another good step. Do that repeatedly on multiple issues, and you are gaining merit. - - Karsten
Cheers, Dave.
-- Dave Neary Community Action and Impact Open Source and Standards Team, Red Hat Phone: +33 9 50 71 55 62
_______________________________________________ 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
- -- 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/Y8l2ZIOBq0ODEERAolfAKC8Wybd7x9qfqDXPDAGztV89rPXuwCfYzSc 5CJbZBzxSBiEovfMFNU3if4= =HnR0 -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/11/2012 01:45 AM, Dave Neary wrote:
Hi,
On 07/11/2012 09:58 AM, Eyal Edri wrote:
Guys, do we have a formal way of accepting new people to the infra team? what should the do, what kind of background the need to provide? is it enough if they work in one the supporting companies?
My vote is that who your employer is shouldn't provide additional merit. Currently, the Board is arranged that way - you can come in as a supporting company and gain a Board set. I understand and generally agree with things for that level, but here where we get things done :) we want to base maintainer status on actual merit.
That's what Karsten, Robert, Mike, Itamar, you and others are working on at the moment (between the mission statement, the "trust seed", managing configs with Puppet, and we still need to figure out how we can graduate involvement and trust so that people not on the team can make positive contributions and thus build reputation and join the team.
Exactly. Checking the 'Trust seed' thread, my proposal was to accept me making up the first list of project maintainers, and then it's up to the maintainers to decide how to accept new maintainers. As part of that, we're full of ideas on splitting systems up a bit so we can give out sudo in one space without having it spill over to other services. - - 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/Y/b2ZIOBq0ODEERAkxgAKCqBb+54PwwWAVvcw75C9OpilCACQCfZrnD N4afndIlHXOXq10NUJT0tww= =f0rT -----END PGP SIGNATURE-----
Hi Douglas, On 07/11/2012 07:41 AM, Douglas Landgraf wrote:
On 07/10/2012 02:53 AM, Eyal Edri wrote:
If you feel you want to contribute to the oVirt infra team, please send a request to infra@ovirt.org with some background (team, project, redhat exp,etc...).
hum, could you please provide a detailed example?
The infrastructure team is working on better enabling people outside the team to join at the moment (see "Trust seed" and mission statement threads for more detail) - the general plan is to have the configuration for all of oVirt's infrastructure managed by Puppet, and to liberally provide access to interested people (like yourself) who have shown an ability to correctly identify, characterise and propose a fix for infra issues. One example relative to me (although I have no desire to be on the infra team at the moment) is my proposal to modify how we sign people up for new accounts in the wiki - the current method is to have existing wiki users add new user accounts, but if you don't know anyone in the project that doesn't really work. My proposal is to have requests for new wiki accounts added to a moderation queue - I sourced the module and would be prepared to check it out on a local instance of MediaWiki, and document any configuration options we need to do to get it enabled. Basically, do all the ground work for the sysadmin who will install it. In your case, you helped by pointing out the failing module, and characterising the problem (missing cherry-py dependency) which made it easier to fix the problem. From there, it's a small step to have someone say "look good, please go ahead and fix that - here's how to connect to (whatever resource)". At least, I hope so!
for now, please provide the missing rpms you know are failing the tests and i'll look into fixing it.
Can you please confirm if cherrypy (and all dependencies) is installed? (As Dan pointed)
I just checked http://jenkins.ovirt.org/job/vdsm_unit_tests/ and it looks like the dependency issue was taken care of a day or two ago. Can you confirm that all is well now? Thanks, Dave. -- Dave Neary Community Action and Impact Open Source and Standards Team, Red Hat Phone: +33 9 50 71 55 62
On 07/11/2012 05:24 AM, Dave Neary wrote:
Hi Douglas,
On 07/11/2012 07:41 AM, Douglas Landgraf wrote:
On 07/10/2012 02:53 AM, Eyal Edri wrote:
If you feel you want to contribute to the oVirt infra team, please send a request to infra@ovirt.org with some background (team, project, redhat exp,etc...).
hum, could you please provide a detailed example?
The infrastructure team is working on better enabling people outside the team to join at the moment (see "Trust seed" and mission statement threads for more detail) - the general plan is to have the configuration for all of oVirt's infrastructure managed by Puppet, and to liberally provide access to interested people (like yourself) who have shown an ability to correctly identify, characterise and propose a fix for infra issues.
One example relative to me (although I have no desire to be on the infra team at the moment) is my proposal to modify how we sign people up for new accounts in the wiki - the current method is to have existing wiki users add new user accounts, but if you don't know anyone in the project that doesn't really work.
Agreed
My proposal is to have requests for new wiki accounts added to a moderation queue - I sourced the module and would be prepared to check it out on a local instance of MediaWiki, and document any configuration options we need to do to get it enabled. Basically, do all the ground work for the sysadmin who will install it.
In your case, you helped by pointing out the failing module, and characterising the problem (missing cherry-py dependency) which made it easier to fix the problem.
From there, it's a small step to have someone say "look good, please go ahead and fix that - here's how to connect to (whatever resource)". At least, I hope so!
Sure, I will wait the definition, thanks for your feedback! -- Cheers Douglas
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/10/2012 10:41 PM, Douglas Landgraf wrote:
Hi Eyal,
On 07/10/2012 02:53 AM, Eyal Edri wrote:
Hi Douglas,
If any dependency is missing you can always send an email to infra@ovirt.org and request to install it. ok
As for getting access to Jenkins slaves in ovirt -> that requires being a member of the infra team and approval of its memebers/trust seeds.
If you feel you want to contribute to the oVirt infra team, please send a request to infra@ovirt.org with some background (team, project, redhat exp,etc...). hum, could you please provide a detailed example?
Douglas, sorry, you happened to arrive just as we are more formally creating the Infra team, which means we are just figuring out how to give out access, and so forth. Your question is a good one, we need to get that up on our wiki page so it's clear what we mean by contributing to get involved. In the meantime, if we cannot be your eyes-in-the-shell for you ... I'm wondering if you could diagnose with basic user ssh access? I.e., without sudo. Then another of us can do the actual fix, etc. (That also would be an example of contributing, and similar to how we're looking to set things up with limited ssh, Puppet, configs in git, etc.) - - Karsten
for now, please provide the missing rpms you know are failing the tests and i'll look into fixing it.
Can you please confirm if cherrypy (and all dependencies) is installed? (As Dan pointed)
thanks,
Eyal Edri
Thanks!
----- Original Message -----
From: "Douglas Landgraf"<dougsland@redhat.com> To: infra@ovirt.org Cc: "Barak Azulay"<bazulay@redhat.com> Sent: Monday, July 9, 2012 5:29:37 PM Subject: jenkins slaves
Hi,
My name is Douglas Schilling Landgraf, I work for Red Hat to provide improvements for VDSM/oVirt. I have noticed that jenkins vdsm_unit_tests project failed because of a package dependency. If possible, can I have access to jenkins slaves to help maintain this VDSM test project?
Thanks!
-- Cheers Douglas
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
- -- 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/Y0Y2ZIOBq0ODEERAl7YAJ4k8aZk7HAo/zFC9qtmEEAaNBpNhwCfcaUD jlnb7tUTT9bgPKHRpWIq7Ds= =KcM3 -----END PGP SIGNATURE-----
Hi Karsten, On 07/11/2012 10:26 AM, Karsten 'quaid' Wade wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/10/2012 10:41 PM, Douglas Landgraf wrote:
Hi Eyal,
On 07/10/2012 02:53 AM, Eyal Edri wrote:
Hi Douglas,
If any dependency is missing you can always send an email to infra@ovirt.org and request to install it. ok As for getting access to Jenkins slaves in ovirt -> that requires being a member of the infra team and approval of its memebers/trust seeds.
If you feel you want to contribute to the oVirt infra team, please send a request to infra@ovirt.org with some background (team, project, redhat exp,etc...). hum, could you please provide a detailed example? Douglas, sorry, you happened to arrive just as we are more formally creating the Infra team, which means we are just figuring out how to give out access, and so forth. Your question is a good one, we need to get that up on our wiki page so it's clear what we mean by contributing to get involved. Thanks for the feedback. If I could suggest a possible evaluation for cases like mine (which require shell access):
* This person contain contributions in the upstream project? (git log, wiki, QA, documentation, etc. Could help to determine) * The upstream maintainer of project [agree/trust] with that? (need to contact maintainer)
In the meantime, if we cannot be your eyes-in-the-shell for you ... I'm wondering if you could diagnose with basic user ssh access? I.e., without sudo. Then another of us can do the actual fix, etc. (That also would be an example of contributing, and similar to how we're looking to set things up with limited ssh, Puppet, configs in git, etc.)
It could be a good start. However, still require contact additional people (not good for quick fixes). Thanks!
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/11/2012 10:08 AM, Douglas Landgraf wrote:
Hi Karsten,
On 07/11/2012 10:26 AM, Karsten 'quaid' Wade wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Eyal,
On 07/10/2012 02:53 AM, Eyal Edri wrote:
Hi Douglas,
If any dependency is missing you can always send an email to infra@ovirt.org and request to install it. ok As for getting access to Jenkins slaves in ovirt -> that requires being a member of the infra team and approval of its memebers/trust seeds.
If you feel you want to contribute to the oVirt infra team, please send a request to infra@ovirt.org with some background (team, project, redhat exp,etc...). hum, could you please provide a detailed example? Douglas, sorry, you happened to arrive just as we are more
On 07/10/2012 10:41 PM, Douglas Landgraf wrote: formally creating the Infra team, which means we are just figuring out how to give out access, and so forth. Your question is a good one, we need to get that up on our wiki page so it's clear what we mean by contributing to get involved. Thanks for the feedback. If I could suggest a possible evaluation for cases like mine (which require shell access):
* This person contain contributions in the upstream project? (git log, wiki, QA, documentation, etc. Could help to determine) * The upstream maintainer of project [agree/trust] with that? (need to contact maintainer)
Agreed those are valuable. Question is, would that same criteria help get me commit access to ovirt-engine?
In the meantime, if we cannot be your eyes-in-the-shell for you ... I'm wondering if you could diagnose with basic user ssh access? I.e., without sudo. Then another of us can do the actual fix, etc. (That also would be an example of contributing, and similar to how we're looking to set things up with limited ssh, Puppet, configs in git, etc.)
It could be a good start. However, still require contact additional people (not good for quick fixes).
Part of what we are doing is looking for the balance that lets us keep services at a professional sysadmin level. We don't want to bog ourselves down with process, but we want some consistency in what to do and how to do it (a process) so those with sudo access are coordinated. Basically, this means Infra needs to provide training materials to people. - - 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/adM2ZIOBq0ODEERApEyAJ9hjCiDV1chcezGzWHWRUzL+RkluwCglr3k /tIHwZ39OXYJc/umENFuoiQ= =LWte -----END PGP SIGNATURE-----
Hi Karsten, On 07/11/2012 12:18 PM, Karsten 'quaid' Wade wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/11/2012 10:08 AM, Douglas Landgraf wrote:
Hi Karsten,
On 07/11/2012 10:26 AM, Karsten 'quaid' Wade wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Eyal,
On 07/10/2012 02:53 AM, Eyal Edri wrote:
Hi Douglas,
If any dependency is missing you can always send an email to infra@ovirt.org and request to install it. ok As for getting access to Jenkins slaves in ovirt -> that requires being a member of the infra team and approval of its memebers/trust seeds.
If you feel you want to contribute to the oVirt infra team, please send a request to infra@ovirt.org with some background (team, project, redhat exp,etc...). hum, could you please provide a detailed example? Douglas, sorry, you happened to arrive just as we are more
On 07/10/2012 10:41 PM, Douglas Landgraf wrote: formally creating the Infra team, which means we are just figuring out how to give out access, and so forth. Your question is a good one, we need to get that up on our wiki page so it's clear what we mean by contributing to get involved. Thanks for the feedback. If I could suggest a possible evaluation for cases like mine (which require shell access):
* This person contain contributions in the upstream project? (git log, wiki, QA, documentation, etc. Could help to determine) * The upstream maintainer of project [agree/trust] with that? (need to contact maintainer) Agreed those are valuable. Question is, would that same criteria help get me commit access to ovirt-engine? I am not the right person to answer that question but from my point of view should apply to the same/similar criteria. However, I see your point of view. :-) Upstream maintainers (ovirt-engine, vdsm) could help to resolve this puzzle.
In the meantime, if we cannot be your eyes-in-the-shell for you ... I'm wondering if you could diagnose with basic user ssh access? I.e., without sudo. Then another of us can do the actual fix, etc. (That also would be an example of contributing, and similar to how we're looking to set things up with limited ssh, Puppet, configs in git, etc.) It could be a good start. However, still require contact additional people (not good for quick fixes). Part of what we are doing is looking for the balance that lets us keep services at a professional sysadmin level. We don't want to bog ourselves down with process, but we want some consistency in what to do and how to do it (a process) so those with sudo access are coordinated.
Basically, this means Infra needs to provide training materials to people. Sure, great. Thanks for your feedback.
-- Cheers Douglas
On Wed, Jul 11, 2012 at 02:45:44PM -0400, Douglas Landgraf wrote:
Hi Karsten,
On 07/11/2012 12:18 PM, Karsten 'quaid' Wade wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/11/2012 10:08 AM, Douglas Landgraf wrote:
Hi Karsten,
On 07/11/2012 10:26 AM, Karsten 'quaid' Wade wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Eyal,
On 07/10/2012 02:53 AM, Eyal Edri wrote:
Hi Douglas,
If any dependency is missing you can always send an email to infra@ovirt.org and request to install it. ok As for getting access to Jenkins slaves in ovirt -> that requires being a member of the infra team and approval of its memebers/trust seeds.
If you feel you want to contribute to the oVirt infra team, please send a request to infra@ovirt.org with some background (team, project, redhat exp,etc...). hum, could you please provide a detailed example? Douglas, sorry, you happened to arrive just as we are more
On 07/10/2012 10:41 PM, Douglas Landgraf wrote: formally creating the Infra team, which means we are just figuring out how to give out access, and so forth. Your question is a good one, we need to get that up on our wiki page so it's clear what we mean by contributing to get involved. Thanks for the feedback. If I could suggest a possible evaluation for cases like mine (which require shell access):
* This person contain contributions in the upstream project? (git log, wiki, QA, documentation, etc. Could help to determine) * The upstream maintainer of project [agree/trust] with that? (need to contact maintainer) Agreed those are valuable. Question is, would that same criteria help get me commit access to ovirt-engine? I am not the right person to answer that question but from my point of view should apply to the same/similar criteria. However, I see your point of view. :-) Upstream maintainers (ovirt-engine, vdsm) could help to resolve this puzzle.
I'm not sure I understand the puzzle. Technically speaking, a host administer can do everything he wants. We *trust* him not do use his powers unecessarily. Preferably, there should be various levels of permissions - being able to setup Jenkins slaves should not mean automatically being able to `git rm` our repo. Since I've known Douglas for a year or so now, I trust him to never abuse his admin rights. I'm looking forward to see him in the infra team, being able to quickly fix infrastructural problems in our testing framework. Regrads, Dan.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/12/2012 02:44 AM, Dan Kenigsberg wrote:
On Wed, Jul 11, 2012 at 02:45:44PM -0400, Douglas Landgraf wrote:
Hi Karsten,
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/11/2012 10:08 AM, Douglas Landgraf wrote:
Hi Karsten,
On 07/11/2012 10:26 AM, Karsten 'quaid' Wade wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Eyal,
On 07/10/2012 02:53 AM, Eyal Edri wrote: > Hi Douglas, > > If any dependency is missing you can always send an > email to infra@ovirt.org and request to install it. ok > As for getting access to Jenkins slaves in ovirt -> > that requires being a member of the infra team and > approval of its memebers/trust seeds. > > If you feel you want to contribute to the oVirt infra > team, please send a request to infra@ovirt.org with > some background (team, project, redhat exp,etc...). hum, could you please provide a detailed example? Douglas, sorry, you happened to arrive just as we are more
On 07/10/2012 10:41 PM, Douglas Landgraf wrote: formally creating the Infra team, which means we are just figuring out how to give out access, and so forth. Your question is a good one, we need to get that up on our wiki page so it's clear what we mean by contributing to get involved. Thanks for the feedback. If I could suggest a possible evaluation for cases like mine (which require shell access):
* This person contain contributions in the upstream project? (git log, wiki, QA, documentation, etc. Could help to determine) * The upstream maintainer of project [agree/trust] with that? (need to contact maintainer) Agreed those are valuable. Question is, would that same criteria help get me commit access to ovirt-engine? I am not the right person to answer that question but from my
On 07/11/2012 12:18 PM, Karsten 'quaid' Wade wrote: point of view should apply to the same/similar criteria. However, I see your point of view. :-) Upstream maintainers (ovirt-engine, vdsm) could help to resolve this puzzle.
I'm not sure I understand the puzzle. Technically speaking, a host administer can do everything he wants. We *trust* him not do use his powers unecessarily.
Preferably, there should be various levels of permissions - being able to setup Jenkins slaves should not mean automatically being able to `git rm` our repo.
Since I've known Douglas for a year or so now, I trust him to never abuse his admin rights. I'm looking forward to see him in the infra team, being able to quickly fix infrastructural problems in our testing framework.
Any puzzle here is merely a matter of timing. We just happen to be forming the initial maintainers of the Infra team project. Those maintainers need to figure out how to add other maintainers. I think the considerations Douglas suggested are good ones to consider in accepting a new maintainer, but I don't think they are the only ones. Just as you would expect me to submit patches to e.g. ovirt-engine before you would give me more commit/control access, we're creating the same kind of thing for the Infra team. That means using Puppet, configurations stored in Gerrit, distributed Jenkins admins, and so forth - ways for people to get things done. Getting things done is at the core of merit-based governance. At the moment, the only way to get things done directly is to run a set of Jenkins slaves, or be given ssh+sudo to one of the existing production hosts. But we can look at giving out limited ssh access, if that helps people like Douglas start getting things done in Infra so he can get the merit with the existing maintainers. - - 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/u9u2ZIOBq0ODEERAphIAKDInY5NuabMOztGFhzlhy3f92QD/QCgwd6M 8VtMlefP4wPgVahkVyZ+++w= =+L2n -----END PGP SIGNATURE-----
participants (5)
-
Dan Kenigsberg -
Dave Neary -
Douglas Landgraf -
Eyal Edri -
Karsten 'quaid' Wade