Nominating Ivan Necas for Foreman commit access

Development
1

Hi all,

I'd like to nominate Ivan Necas (iNecas on GitHub) for commit access to
Foreman core. He's contributed to Foreman, plugins, dependencies and
packaging for a few years with code and reviews and I think has a strong
understanding of the codebase.

Some examples of contributions (per
Foreman :: Contribute):

  • Maintains foreman-tasks plugin
  • Maintains various dependencies, such as apipie-rails, dynflow
  • Co-maintains foreman_remote_execution plugin and associated smart
    proxy, CLI plugins
  • Has contributed to provisioning related bug fixes lately (e.g. #5859,
    #13984, #9704, #9705), and fixed a technically difficult bug (#14340)
    affecting tests
  • Has been helping with good reviews and testing of Foreman PRs (e.g.
    #12746, #12979, #14204).
  • Spoken at DevConf.cz on Foreman
    (https://www.youtube.com/watch?v=F-SyKv9KKmU).

I'd encourage Ivan to participate more on Redmine and packaging
(particularly with his experience there), but otherwise think he's doing
a good job across the project.

Objections or comments in private are welcome by e-mail too.

Regards,

··· -- Dominic Cleal dominic@cleal.org
2

> Hi all,
>
> I'd like to nominate Ivan Necas (iNecas on GitHub) for commit access to
> Foreman core. He's contributed to Foreman, plugins, dependencies and
> packaging for a few years with code and reviews and I think has a strong
> understanding of the codebase.
>
> Some examples of contributions (per
> Foreman :: Contribute):
>
> - Maintains foreman-tasks plugin
> - Maintains various dependencies, such as apipie-rails, dynflow
> - Co-maintains foreman_remote_execution plugin and associated smart
> proxy, CLI plugins
> - Has contributed to provisioning related bug fixes lately (e.g. #5859,
> #13984, #9704, #9705), and fixed a technically difficult bug (#14340)
> affecting tests
> - Has been helping with good reviews and testing of Foreman PRs (e.g.
> #12746, #12979, #14204).
> - Spoken at DevConf.cz on Foreman
> (https://www.youtube.com/watch?v=F-SyKv9KKmU).
>
> I'd encourage Ivan to participate more on Redmine and packaging
> (particularly with his experience there), but otherwise think he's doing
> a good job across the project.
>
> Objections or comments in private are welcome by e-mail too.
>

big +1 from MPOV, thanks for raising it!
inecas++

Ohad

··· On Thu, Mar 31, 2016 at 11:03 AM, Dominic Cleal wrote:

Regards,

–
Dominic Cleal
dominic@cleal.org

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

3

+1 from me too - https://media.giphy.com/media/3o7abB06u9bNzA8lu8/giphy.gif

··· On 03/31, Dominic Cleal wrote: > Hi all, > > I'd like to nominate Ivan Necas (iNecas on GitHub) for commit access to > Foreman core. He's contributed to Foreman, plugins, dependencies and > packaging for a few years with code and reviews and I think has a strong > understanding of the codebase. > > Some examples of contributions (per > http://theforeman.org/handbook.html#Becomingacommitter): > > - Maintains foreman-tasks plugin > - Maintains various dependencies, such as apipie-rails, dynflow > - Co-maintains foreman_remote_execution plugin and associated smart > proxy, CLI plugins > - Has contributed to provisioning related bug fixes lately (e.g. #5859, > #13984, #9704, #9705), and fixed a technically difficult bug (#14340) > affecting tests > - Has been helping with good reviews and testing of Foreman PRs (e.g. > #12746, #12979, #14204). > - Spoken at DevConf.cz on Foreman > (https://www.youtube.com/watch?v=F-SyKv9KKmU). > > I'd encourage Ivan to participate more on Redmine and packaging > (particularly with his experience there), but otherwise think he's doing > a good job across the project. > > Objections or comments in private are welcome by e-mail too. > > Regards, >

–
Daniel Lobato Garcia

@dLobatog
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato

4

+1 :slight_smile:

··· -- Marek

On Thursday 31 of March 2016 09:03:45 Dominic Cleal wrote:

Hi all,

I’d like to nominate Ivan Necas (iNecas on GitHub) for commit access to
Foreman core. He’s contributed to Foreman, plugins, dependencies and
packaging for a few years with code and reviews and I think has a strong
understanding of the codebase.

Some examples of contributions (per
Foreman :: Contribute):

  • Maintains foreman-tasks plugin
  • Maintains various dependencies, such as apipie-rails, dynflow
  • Co-maintains foreman_remote_execution plugin and associated smart
    proxy, CLI plugins
  • Has contributed to provisioning related bug fixes lately (e.g. #5859,
    #13984, #9704, #9705), and fixed a technically difficult bug (#14340)
    affecting tests
  • Has been helping with good reviews and testing of Foreman PRs (e.g.
    #12746, #12979, #14204).
  • Spoken at DevConf.cz on Foreman
    (https://www.youtube.com/watch?v=F-SyKv9KKmU).

I’d encourage Ivan to participate more on Redmine and packaging
(particularly with his experience there), but otherwise think he’s doing
a good job across the project.

Objections or comments in private are welcome by e-mail too.

Regards,

5

I thought he already had access :slight_smile:
definitely +1!!

··· On Thu, Mar 31, 2016 at 11:43 AM, Ohad Levy wrote:

On Thu, Mar 31, 2016 at 11:03 AM, Dominic Cleal dominic@cleal.org wrote:

Hi all,

I’d like to nominate Ivan Necas (iNecas on GitHub) for commit access to
Foreman core. He’s contributed to Foreman, plugins, dependencies and
packaging for a few years with code and reviews and I think has a strong
understanding of the codebase.

Some examples of contributions (per
Foreman :: Contribute):

  • Maintains foreman-tasks plugin
  • Maintains various dependencies, such as apipie-rails, dynflow
  • Co-maintains foreman_remote_execution plugin and associated smart
    proxy, CLI plugins
  • Has contributed to provisioning related bug fixes lately (e.g. #5859,
    #13984, #9704, #9705), and fixed a technically difficult bug (#14340)
    affecting tests
  • Has been helping with good reviews and testing of Foreman PRs (e.g.
    #12746, #12979, #14204).
  • Spoken at DevConf.cz on Foreman
    (https://www.youtube.com/watch?v=F-SyKv9KKmU).

I’d encourage Ivan to participate more on Redmine and packaging
(particularly with his experience there), but otherwise think he’s doing
a good job across the project.

Objections or comments in private are welcome by e-mail too.

big +1 from MPOV, thanks for raising it!
inecas++

Ohad

Regards,

–
Dominic Cleal
dominic@cleal.org

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

6

Based on the above feedback, it is done - Good luck Ivan!

··· On Thu, Mar 31, 2016 at 2:48 PM, Marek Hulán wrote:

+1 :slight_smile:

–
Marek

On Thursday 31 of March 2016 09:03:45 Dominic Cleal wrote:

Hi all,

I’d like to nominate Ivan Necas (iNecas on GitHub) for commit access to
Foreman core. He’s contributed to Foreman, plugins, dependencies and
packaging for a few years with code and reviews and I think has a strong
understanding of the codebase.

Some examples of contributions (per
Foreman :: Contribute):

  • Maintains foreman-tasks plugin
  • Maintains various dependencies, such as apipie-rails, dynflow
  • Co-maintains foreman_remote_execution plugin and associated smart
    proxy, CLI plugins
  • Has contributed to provisioning related bug fixes lately (e.g. #5859,
    #13984, #9704, #9705), and fixed a technically difficult bug (#14340)
    affecting tests
  • Has been helping with good reviews and testing of Foreman PRs (e.g.
    #12746, #12979, #14204).
  • Spoken at DevConf.cz on Foreman
    (https://www.youtube.com/watch?v=F-SyKv9KKmU).

I’d encourage Ivan to participate more on Redmine and packaging
(particularly with his experience there), but otherwise think he’s doing
a good job across the project.

Objections or comments in private are welcome by e-mail too.

Regards,

7

The procedure we agreed for
Foreman :: Contribute calls for a
week-long period, not four hours. Still, thanks.

··· On 31/03/16 13:09, Ohad Levy wrote: > > > On Thu, Mar 31, 2016 at 2:48 PM, Marek Hulán > wrote: > > +1 :-) > > -- > Marek > > On Thursday 31 of March 2016 09:03:45 Dominic Cleal wrote: > > Hi all, > > > > I'd like to nominate Ivan Necas (iNecas on GitHub) for commit > access to > > Foreman core. He's contributed to Foreman, plugins, dependencies and > > packaging for a few years with code and reviews and I think has a > strong > > understanding of the codebase. > > > > Some examples of contributions (per > > http://theforeman.org/handbook.html#Becomingacommitter): > > > > - Maintains foreman-tasks plugin > > - Maintains various dependencies, such as apipie-rails, dynflow > > - Co-maintains foreman_remote_execution plugin and associated smart > > proxy, CLI plugins > > - Has contributed to provisioning related bug fixes lately (e.g. > #5859, > > #13984, #9704, #9705), and fixed a technically difficult bug (#14340) > > affecting tests > > - Has been helping with good reviews and testing of Foreman PRs (e.g. > > #12746, #12979, #14204). > > - Spoken at DevConf.cz on Foreman > > (https://www.youtube.com/watch?v=F-SyKv9KKmU). > > > > I'd encourage Ivan to participate more on Redmine and packaging > > (particularly with his experience there), but otherwise think he's > doing > > a good job across the project. > > > > Objections or comments in private are welcome by e-mail too. > > > > Regards, > > > > Based on the above feedback, it is done - Good luck Ivan!

–
Dominic Cleal
dominic@cleal.org

8

> >
> >
> >
> > +1 :slight_smile:
> >
> > –
> > Marek
> >
> > > Hi all,
> > >
> > > I'd like to nominate Ivan Necas (iNecas on GitHub) for commit
> > access to
> > > Foreman core. He's contributed to Foreman, plugins, dependencies
> and
> > > packaging for a few years with code and reviews and I think has a
> > strong
> > > understanding of the codebase.
> > >
> > > Some examples of contributions (per
> > > Foreman :: Contribute):
> > >
> > > - Maintains foreman-tasks plugin
> > > - Maintains various dependencies, such as apipie-rails, dynflow
> > > - Co-maintains foreman_remote_execution plugin and associated smart
> > > proxy, CLI plugins
> > > - Has contributed to provisioning related bug fixes lately (e.g.
> > #5859,
> > > #13984, #9704, #9705), and fixed a technically difficult bug
> (#14340)
> > > affecting tests
> > > - Has been helping with good reviews and testing of Foreman PRs
> (e.g.
> > > #12746, #12979, #14204).
> > > - Spoken at DevConf.cz on Foreman
> > > (https://www.youtube.com/watch?v=F-SyKv9KKmU).
> > >
> > > I'd encourage Ivan to participate more on Redmine and packaging
> > > (particularly with his experience there), but otherwise think he's
> > doing
> > > a good job across the project.
> > >
> > > Objections or comments in private are welcome by e-mail too.
> > >
> > > Regards,
> >
> >
> >
> > Based on the above feedback, it is done - Good luck Ivan!
>
> The procedure we agreed for
> Foreman :: Contribute calls for a
> week-long period, not four hours. Still, thanks.
>

my apologies, I've missed the one week waiting period.

Cheers,
Ohad

··· On Thu, Mar 31, 2016 at 3:13 PM, Dominic Cleal wrote: > On 31/03/16 13:09, Ohad Levy wrote: > > On Thu, Mar 31, 2016 at 2:48 PM, Marek Hulán > > wrote: > > On Thursday 31 of March 2016 09:03:45 Dominic Cleal wrote:

–
Dominic Cleal
dominic@cleal.org

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

9

Thanks all for the trust that I don't want to break (and it will still take some time to take confidenceme before I push my first PR to develop). Looking forward to see you in the PR comments section :slight_smile:

– Ivan

··· ----- Original Message ----- > On Thu, Mar 31, 2016 at 3:13 PM, Dominic Cleal wrote: > > > On 31/03/16 13:09, Ohad Levy wrote: > > > > > > > > > On Thu, Mar 31, 2016 at 2:48 PM, Marek Hulán > > > wrote: > > > > > > +1 :-) > > > > > > -- > > > Marek > > > > > > On Thursday 31 of March 2016 09:03:45 Dominic Cleal wrote: > > > > Hi all, > > > > > > > > I'd like to nominate Ivan Necas (iNecas on GitHub) for commit > > > access to > > > > Foreman core. He's contributed to Foreman, plugins, dependencies > > and > > > > packaging for a few years with code and reviews and I think has a > > > strong > > > > understanding of the codebase. > > > > > > > > Some examples of contributions (per > > > > http://theforeman.org/handbook.html#Becomingacommitter): > > > > > > > > - Maintains foreman-tasks plugin > > > > - Maintains various dependencies, such as apipie-rails, dynflow > > > > - Co-maintains foreman_remote_execution plugin and associated smart > > > > proxy, CLI plugins > > > > - Has contributed to provisioning related bug fixes lately (e.g. > > > #5859, > > > > #13984, #9704, #9705), and fixed a technically difficult bug > > (#14340) > > > > affecting tests > > > > - Has been helping with good reviews and testing of Foreman PRs > > (e.g. > > > > #12746, #12979, #14204). > > > > - Spoken at DevConf.cz on Foreman > > > > (https://www.youtube.com/watch?v=F-SyKv9KKmU). > > > > > > > > I'd encourage Ivan to participate more on Redmine and packaging > > > > (particularly with his experience there), but otherwise think he's > > > doing > > > > a good job across the project. > > > > > > > > Objections or comments in private are welcome by e-mail too. > > > > > > > > Regards, > > > > > > > > > > > > Based on the above feedback, it is done - Good luck Ivan! > > > > The procedure we agreed for > > http://theforeman.org/handbook.html#Becomingacommitter calls for a > > week-long period, not four hours. Still, thanks. > > > > my apologies, I've missed the one week waiting period. > > Cheers, > Ohad > > > > > -- > > Dominic Cleal > > dominic@cleal.org > > > > -- > > You received this message because you are subscribed to the Google Groups > > "foreman-dev" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to foreman-dev+unsubscribe@googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. > > > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. >