As per the newly-merged plugin policy, I've taken a quick pass over all
the gems listed in the RPM packaging (which is more comprehensive than
the Deb packaging), grepped for "foreman" and "proxy", and then used
the Rubygems API to filter for gems with a single author.
This list was pretty long, so for brevity, I've also removed things
which are (as far as I know) not in active use at the moment (we can
always revisit that and run this again later).
Below is the list of gems that need an additional maintainer, grouped
by owner. Could these people please add a second author to the gem,
just in case? If you've got someone in mind just go for it, if you want
help deciding who show be added, feel free to reply here.
Daniel Lobato Garcia:
foreman_ansible
foreman_ansible_core
foreman_azure
foreman_cockpit
Dominic Cleal:
foreman_bootdisk
foreman_hooks
foreman_setup
hammer_cli_foreman_bootdisk
smart_proxy_dns_route53
Ewoud Kohl van Wijngaarden:
smart_proxy_dns_powerdns
Greg Sutcliffe:
foreman_column_view
foreman_default_hostgroup
Marek Hulan:
foreman_chef
smart_proxy_chef
Lukas Zapletal:
smart_proxy_discovery_image
Ohad Levy:
foreman_memcache
Since I'm on the list, who wants adding to my plugins?
> Hi all,
>
> As per the newly-merged plugin policy, I've taken a quick pass over all
> the gems listed in the RPM packaging (which is more comprehensive than
> the Deb packaging), grepped for "foreman" and "proxy", and then used
> the Rubygems API to filter for gems with a single author.
>
> This list was pretty long, so for brevity, I've also removed things
> which are (as far as I know) not in active use at the moment (we can
> always revisit that and run this again later).
>
> Below is the list of gems that need an additional maintainer, grouped
> by owner. Could these people please add a second author to the gem,
> just in case? If you've got someone in mind just go for it, if you want
> help deciding who show be added, feel free to reply here.
>
> Daniel Lobato Garcia:
> - foreman_ansible
> - foreman_ansible_core
> - foreman_azure
> - foreman_cockpit
>
> Dominic Cleal:
> - foreman_bootdisk
> - foreman_hooks
> - foreman_setup
> - hammer_cli_foreman_bootdisk
> - smart_proxy_dns_route53
>
> Ewoud Kohl van Wijngaarden:
> - smart_proxy_dns_powerdns
>
> Greg Sutcliffe:
> - foreman_column_view
> - foreman_default_hostgroup
>
> Marek Hulan:
> - foreman_chef
> - smart_proxy_chef
>
> Lukas Zapletal:
> - smart_proxy_discovery_image
>
> Ohad Levy:
> - foreman_memcache
>
Anyone? historically mmoll used to patch it - interested?
···
On Fri, Aug 18, 2017 at 2:48 PM, Greg Sutcliffe wrote:
Since I’m on the list, who wants adding to my plugins?
Anyone interested? I have no candidate. Btw there's also https://github.com/
theforeman/chef-handler-foreman which is related.
···
On pátek 18. srpna 2017 13:48:06 CEST Greg Sutcliffe wrote:
> Hi all,
>
> As per the newly-merged plugin policy, I've taken a quick pass over all
> the gems listed in the RPM packaging (which is more comprehensive than
> the Deb packaging), grepped for "foreman" and "proxy", and then used
> the Rubygems API to filter for gems with a single author.
>
> This list was pretty long, so for brevity, I've also removed things
> which are (as far as I know) not in active use at the moment (we can
> always revisit that and run this again later).
>
> Below is the list of gems that need an additional maintainer, grouped
> by owner. Could these people please add a second author to the gem,
> just in case? If you've got someone in mind just go for it, if you want
> help deciding who show be added, feel free to reply here.
>
> Daniel Lobato Garcia:
> - foreman_ansible
> - foreman_ansible_core
> - foreman_azure
> - foreman_cockpit
>
> Dominic Cleal:
> - foreman_bootdisk
> - foreman_hooks
> - foreman_setup
> - hammer_cli_foreman_bootdisk
> - smart_proxy_dns_route53
>
> Ewoud Kohl van Wijngaarden:
> - smart_proxy_dns_powerdns
>
> Greg Sutcliffe:
> - foreman_column_view
> - foreman_default_hostgroup
>
> Marek Hulan:
> - foreman_chef
> - smart_proxy_chef
–
Marek
Lukas Zapletal:
smart_proxy_discovery_image
Ohad Levy:
foreman_memcache
Since I’m on the list, who wants adding to my plugins?
> Hi all,
>
> As per the newly-merged plugin policy, I've taken a quick pass over all
> the gems listed in the RPM packaging (which is more comprehensive than
> the Deb packaging), grepped for "foreman" and "proxy", and then used
> the Rubygems API to filter for gems with a single author.
>
> This list was pretty long, so for brevity, I've also removed things
> which are (as far as I know) not in active use at the moment (we can
> always revisit that and run this again later).
>
> Below is the list of gems that need an additional maintainer, grouped
> by owner. Could these people please add a second author to the gem,
> just in case? If you've got someone in mind just go for it, if you want
> help deciding who show be added, feel free to reply here.
>
> Daniel Lobato Garcia:
> - foreman_ansible
> - foreman_ansible_core
Added agx and mhulan for these 2
> - foreman_azure
Added ehelms (2nd most prolific contributor)
> - foreman_cockpit
Added thomasmckay (2nd most prolific contributor with a rubygems
account)
···
On 08/18, Greg Sutcliffe wrote:
>
> Dominic Cleal:
> - foreman_bootdisk
> - foreman_hooks
> - foreman_setup
> - hammer_cli_foreman_bootdisk
> - smart_proxy_dns_route53
>
> Ewoud Kohl van Wijngaarden:
> - smart_proxy_dns_powerdns
>
> Greg Sutcliffe:
> - foreman_column_view
> - foreman_default_hostgroup
>
> Marek Hulan:
> - foreman_chef
> - smart_proxy_chef
>
> Lukas Zapletal:
> - smart_proxy_discovery_image
>
> Ohad Levy:
> - foreman_memcache
>
> Since I'm on the list, who wants adding to my plugins? :)
>
> Regards
> Greg
> --
> IRC / Twitter: @gwmngilfen
> Diaspora: gwmngilfen@joindiaspora.com
>
> --
> 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.
Thanks to all who've already added new authors. I've tidied up my
script and sent it as a PR to the website scripts dir [1]. I've run it
and again hand-edited down to things that jump out at me as "in use"
>
>> Dominic Cleal:
>> - smart_proxy_dns_route53
>>
>
> I'd like to get added to this plugin.
>
> Ewoud Kohl van Wijngaarden:
>> - smart_proxy_dns_powerdns
>>
>
> Looking for a co-owner here
>
You can add me.
Cheers,
-d
···
On Sun, Aug 20, 2017 at 6:49 AM, Ewoud Kohl van Wijngaarden < ewoud@kohlvanwijngaarden.nl> wrote:
> On Fri, Aug 18, 2017 at 12:48:06PM +0100, Greg Sutcliffe wrote:
···
On Sun, Aug 20, 2017 at 09:56:40AM -0700, Dmitri Dolguikh wrote:
>On Sun, Aug 20, 2017 at 6:49 AM, Ewoud Kohl van Wijngaarden < >ewoud@kohlvanwijngaarden.nl> wrote:
>
>> On Fri, Aug 18, 2017 at 12:48:06PM +0100, Greg Sutcliffe wrote:
>> Ewoud Kohl van Wijngaarden:
>>> - smart_proxy_dns_powerdns
>>>
>>
>> Looking for a co-owner here :)
>>
>
>You can add me.
>
>Cheers,
>-d
Hi all, here's the latest list (which hasn't really changed since last
time). Anyone is welcome to add me as an author - I won't be doing
anything to help you, but at least I can add others if plugins become
abandoned
With no response here, or on various pull requests [1,2] in some
months, would anyone object if I add Lukas and Timo to the bootdisk
plugin on GitHub? They could then review each others work as we
normally do.
···
On Sun, 2017-08-20 at 16:33 +0200, Timo Goebel wrote:
> I'd also be interested in helping with foreman_bootdisk. Although
> it's sad to see, it looks like Dominic isn't maintaining this at all
> anymore.
On Mon, 2017-08-21 at 09:19 +0200, Lukas Zapletal wrote:
···
On pondělí 11. září 2017 14:02:06 CEST Greg Sutcliffe wrote:
> On Sun, 2017-08-20 at 16:33 +0200, Timo Goebel wrote:
> > I'd also be interested in helping with foreman_bootdisk. Although
> > it's sad to see, it looks like Dominic isn't maintaining this at all
> > anymore.
>
> On Mon, 2017-08-21 at 09:19 +0200, Lukas Zapletal wrote:
> > I also have some knowledge of bootdisk and hooks.
>
> With no response here, or on various pull requests [1,2] in some
> months, would anyone object if I add Lukas and Timo to the bootdisk
> plugin on GitHub? They could then review each others work as we
> normally do.
>
> [1] https://github.com/theforeman/foreman_bootdisk/pull/42#issuecomment
> -314787206
> [2] https://github.com/theforeman/foreman_bootdisk/pull/43#issuecomment
> -316937459
>
> Greg
I see a +1 from Marek and no -1's, public or privately, so this is now
done. Thanks all.
Greg
···
On Mon, 2017-09-11 at 13:02 +0100, Greg Sutcliffe wrote:
>
> With no response here, or on various pull requests [1,2] in some
> months, would anyone object if I add Lukas and Timo to the bootdisk
> plugin on GitHub? They could then review each others work as we
> normally do.
On Tue, 2017-09-12 at 17:50 +0200, Marek Hulán wrote:
foreman_hooks still seems somewhat unmaintained, I’d be happy to help out here. There’s currently 4 PRs, 1 that hadn’t been looked at since November, I’ve just reviewed 3 of those and 2 of those are ready for merge, just I don’t have write access.
Ooops @sean797, this has been longer than a week. I’ve added you to the Github repo as a maintainer, and I can add you as an author on Rubygems, just PM the account email address
