Re: jenkins slaves

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 >>> >>>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(a)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(a)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) >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.