Re: [foreman-dev] Plugin gems with a single author - redux
On 10/11/17 15:20, Ewoud Kohl van Wijngaarden wrote: > On Fri, Nov 10, 2017 at 02:02:10PM +, Greg Sutcliffe wrote: >> To make this a more "official" policy, I've created a "Foreman" account >> on Rubygems, and the user can be added >> to any gem we keep on our namespace. This should minimize any issues >> when transferring gems to new owners. > > For what it's worth: it'd be good if this was rubyg...@theforeman.org, > even if it's still stored on gmail. That way you can easily change it as > long as you own the domain. Agreed. Ohad is away (he controls the DNS domain), and I wanted to get it done while I was thinking about it. I'll get that alias sorted when he's back. -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: [foreman-dev] Plugin gems with a single author - redux
On Fri, Nov 10, 2017 at 02:02:10PM +, Greg Sutcliffe wrote: To make this a more "official" policy, I've created a "Foreman" account on Rubygems, and the user can be added to any gem we keep on our namespace. This should minimize any issues when transferring gems to new owners. For what it's worth: it'd be good if this was rubyg...@theforeman.org, even if it's still stored on gmail. That way you can easily change it as long as you own the domain. -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] Plugin gems with a single author - redux
On 10/11/17 14:23, Ewoud Kohl van Wijngaarden wrote: > > I like this. What are the opinions on deploying gems through Travis like > voxpupuli does? > > https://docs.travis-ci.com/user/deployment/rubygems/ > > tl;dr: on tags it can deploy the gem to rubygems. It standardizes the > deploy process and you're sure that any gem has a tag and vice versa. I was about to suggest *exactly* this. Add the gems to a bot, let the bot handle pushing new versions. Can be automated from the Git so we don't even need any other authors on a gem (provided the access to the bot account is properly shared for yanking etc). Thoughts everyone? -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] Plugin gems with a single author - redux
On Fri, Nov 10, 2017 at 02:02:10PM +, Greg Sutcliffe wrote: A few months ago we added a policy that required 2 gem authors per plugin. We did, however struggle to actually get two authors on some plugins. To make this a more "official" policy, I've created a "Foreman" account on Rubygems, and the user can be added to any gem we keep on our namespace. This should minimize any issues when transferring gems to new owners. The account has a recovery email of my RedHat address, which means it can be recovered even if I get hit by a bus (because my superiors can open it). I will also revive the discussion about sharing infra passwords with appropriate security ;) Unless anyone has any strong objections, I'll send a PR for review to make adding this owner an official policy for our gems. I like this. What are the opinions on deploying gems through Travis like voxpupuli does? https://docs.travis-ci.com/user/deployment/rubygems/ tl;dr: on tags it can deploy the gem to rubygems. It standardizes the deploy process and you're sure that any gem has a tag and vice versa. -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[foreman-dev] Plugin gems with a single author - redux
Hi all, A few months ago we added a policy that required 2 gem authors per plugin. We did, however struggle to actually get two authors on some plugins. To make this a more "official" policy, I've created a "Foreman" account on Rubygems, and the user can be added to any gem we keep on our namespace. This should minimize any issues when transferring gems to new owners. The account has a recovery email of my RedHat address, which means it can be recovered even if I get hit by a bus (because my superiors can open it). I will also revive the discussion about sharing infra passwords with appropriate security ;) Unless anyone has any strong objections, I'll send a PR for review to make adding this owner an official policy for our gems. Greg -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] Plugin gems with a single author
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 Makes sense to me -- Marek -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] Plugin gems with a single author
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 -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] Plugin gems with a single author
On 08/18, 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 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) > > 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: gwmngil...@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+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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 -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: [foreman-dev] Plugin gems with a single author
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 Anyone interested? I have no candidate. Btw there's also https://github.com/ theforeman/chef-handler-foreman which is related. -- Marek > Lukas Zapletal: > - smart_proxy_discovery_image > > Ohad Levy: > - foreman_memcache > > Since I'm on the list, who wants adding to my plugins? :) > > Regards > Greg -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] Plugin gems with a single author
>> - foreman_memcache > I currently use foreman_memcache in production, so I do have some interest > in seeing it maintained. I'd volunteer if nobody else wants to. I can jump in here. I also have some knowledge of bootdisk and hooks. -- Later, Lukas @lzap Zapletal -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] Plugin gems with a single author
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 < ew...@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 Done -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] Plugin gems with a single author
On Sun, Aug 20, 2017 at 6:49 AM, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote: > On Fri, Aug 18, 2017 at 12:48:06PM +0100, Greg Sutcliffe wrote: > >> 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 > -- > 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+unsubscr...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] Plugin gems with a single author
Am 20.08.17 um 15:48 schrieb Ohad Levy: On Fri, Aug 18, 2017 at 2:48 PM, Greg Sutcliffe mailto:greg.sutcli...@gmail.com>> wrote: Ohad Levy: - foreman_memcache Anyone? :) historically mmoll used to patch it - interested? I currently use foreman_memcache in production, so I do have some interest in seeing it maintained. I'd volunteer if nobody else wants to. 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. - Timo -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] Plugin gems with a single author
On Fri, Aug 18, 2017 at 2:48 PM, 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 > > Lukas Zapletal: > - smart_proxy_discovery_image > > Ohad Levy: > - foreman_memcache > Anyone? :) historically mmoll used to patch it - interested? > > Since I'm on the list, who wants adding to my plugins? :) > > Regards > Greg > -- > IRC / Twitter: @gwmngilfen > Diaspora: gwmngil...@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+unsubscr...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] Plugin gems with a single author
On Fri, Aug 18, 2017 at 12:48:06PM +0100, Greg Sutcliffe wrote: 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 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[foreman-dev] Plugin gems with a single author
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 Since I'm on the list, who wants adding to my plugins? :) Regards Greg -- IRC / Twitter: @gwmngilfen Diaspora: gwmngil...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
