Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

2017-12-11 Thread Emilien Macchi
I went ahead and added Wes part of tripleo-core, when we expect him to use +2 on tripleo-ci and tripleo-quickstart(-extras) repos. Thanks! On Mon, Dec 11, 2017 at 8:41 AM, Sagi Shnaidman wrote: > +1 > > On Wed, Dec 6, 2017 at 5:45 PM, Emilien Macchi

Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

2017-12-11 Thread Sagi Shnaidman
+1 On Wed, Dec 6, 2017 at 5:45 PM, Emilien Macchi wrote: > Team, > > Wes has been consistently and heavily involved in TripleO CI work. > He has a very well understanding on how tripleo-quickstart and > tripleo-quickstart-extras work, his number and quality of reviews are >

Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

2017-12-07 Thread James Slagle
On Wed, Dec 6, 2017 at 10:45 AM, Emilien Macchi wrote: > Team, > > Wes has been consistently and heavily involved in TripleO CI work. > He has a very well understanding on how tripleo-quickstart and > tripleo-quickstart-extras work, his number and quality of reviews are >

Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

2017-12-07 Thread Steven Hardy
+1! On Wed, Dec 6, 2017 at 3:45 PM, Emilien Macchi wrote: > Team, > > Wes has been consistently and heavily involved in TripleO CI work. > He has a very well understanding on how tripleo-quickstart and > tripleo-quickstart-extras work, his number and quality of reviews are >

Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

2017-12-07 Thread Matt Young
+1 On Thu, Dec 7, 2017 at 9:05 AM, Ronelle Landy wrote: > +1 > > On Thu, Dec 7, 2017 at 8:47 AM, Brad P. Crochet wrote: > >> +1 >> >> >> On Wed, Dec 6, 2017 at 10:46 AM Emilien Macchi >> wrote: >> >>> Team, >>> >>> Wes has been

Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

2017-12-07 Thread Ronelle Landy
+1 On Thu, Dec 7, 2017 at 8:47 AM, Brad P. Crochet wrote: > +1 > > > On Wed, Dec 6, 2017 at 10:46 AM Emilien Macchi wrote: > >> Team, >> >> Wes has been consistently and heavily involved in TripleO CI work. >> He has a very well understanding on how

Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

2017-12-07 Thread Brad P. Crochet
+1 On Wed, Dec 6, 2017 at 10:46 AM Emilien Macchi wrote: > Team, > > Wes has been consistently and heavily involved in TripleO CI work. > He has a very well understanding on how tripleo-quickstart and > tripleo-quickstart-extras work, his number and quality of reviews are >

Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

2017-12-07 Thread Julie Pichon
On 6 December 2017 at 15:45, Emilien Macchi wrote: > Wes has been consistently and heavily involved in TripleO CI work. > He has a very well understanding on how tripleo-quickstart and > tripleo-quickstart-extras work, his number and quality of reviews are > excellent so far.

Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

2017-12-07 Thread Arx Cruz
+1 !!! On Thu, Dec 7, 2017 at 7:47 AM, Marios Andreou wrote: > +1 ! > > > On Wed, Dec 6, 2017 at 5:45 PM, Emilien Macchi wrote: > >> Team, >> >> Wes has been consistently and heavily involved in TripleO CI work. >> He has a very well understanding on

Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

2017-12-06 Thread Marios Andreou
+1 ! On Wed, Dec 6, 2017 at 5:45 PM, Emilien Macchi wrote: > Team, > > Wes has been consistently and heavily involved in TripleO CI work. > He has a very well understanding on how tripleo-quickstart and > tripleo-quickstart-extras work, his number and quality of reviews are

Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

2017-12-06 Thread Juan Antonio Osorio
+1 On 6 Dec 2017 18:25, "Harry Rybacki" wrote: On Wed, Dec 6, 2017 at 11:19 AM, mathieu bultel wrote: > On 12/06/2017 04:45 PM, Emilien Macchi wrote: >> Team, >> >> Wes has been consistently and heavily involved in TripleO CI work. >> He has a very well

Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

2017-12-06 Thread Harry Rybacki
On Wed, Dec 6, 2017 at 11:19 AM, mathieu bultel wrote: > On 12/06/2017 04:45 PM, Emilien Macchi wrote: >> Team, >> >> Wes has been consistently and heavily involved in TripleO CI work. >> He has a very well understanding on how tripleo-quickstart and >>

Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

2017-12-06 Thread mathieu bultel
On 12/06/2017 04:45 PM, Emilien Macchi wrote: > Team, > > Wes has been consistently and heavily involved in TripleO CI work. > He has a very well understanding on how tripleo-quickstart and > tripleo-quickstart-extras work, his number and quality of reviews are > excellent so far. His experience

Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

2017-12-06 Thread Martin André
+1 On Wed, Dec 6, 2017 at 4:45 PM, Emilien Macchi wrote: > Team, > > Wes has been consistently and heavily involved in TripleO CI work. > He has a very well understanding on how tripleo-quickstart and > tripleo-quickstart-extras work, his number and quality of reviews are >

Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

2017-12-06 Thread Jiří Stránský
+1 On 6.12.2017 16:45, Emilien Macchi wrote: Team, Wes has been consistently and heavily involved in TripleO CI work. He has a very well understanding on how tripleo-quickstart and tripleo-quickstart-extras work, his number and quality of reviews are excellent so far. His experience with

Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

2017-12-06 Thread Alex Schultz
+1 On Wed, Dec 6, 2017 at 8:45 AM, Emilien Macchi wrote: > Team, > > Wes has been consistently and heavily involved in TripleO CI work. > He has a very well understanding on how tripleo-quickstart and > tripleo-quickstart-extras work, his number and quality of reviews are >

[openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

2017-12-06 Thread Emilien Macchi
Team, Wes has been consistently and heavily involved in TripleO CI work. He has a very well understanding on how tripleo-quickstart and tripleo-quickstart-extras work, his number and quality of reviews are excellent so far. His experience with testing TripleO is more than valuable. Also, he's