Re: [foreman-dev] Taking over plugins - do we need a policy?

2017-08-15 Thread Greg Sutcliffe
On Tue, 2017-08-15 at 08:20 +0200, Marek Hulán wrote: > curl https://rubygems.org/api/v1/gems/foreman_chef/owners.json > > see http://guides.rubygems.org/rubygems-org-api/#owner-methods for > more details. Ah, perfect, thanks. I'll get a policy drafted up and then I can script this an mail all pl

Re: [foreman-dev] Taking over plugins - do we need a policy?

2017-08-14 Thread Marek Hulán
On pondělí 14. srpna 2017 17:31:00 CEST Greg Sutcliffe wrote: > Hi all, > > This went fairly quiet, but we all seem largely in agreement. I'll > draft something up for the website and send a PR tomorrow. I had a few > side questions though: > > On Wed, 2017-07-19 at 10:13 +0200, Marek Hulán wrote

Re: [foreman-dev] Taking over plugins - do we need a policy?

2017-08-14 Thread Greg Sutcliffe
Hi all, This went fairly quiet, but we all seem largely in agreement. I'll draft something up for the website and send a PR tomorrow. I had a few side questions though: On Wed, 2017-07-19 at 10:13 +0200, Marek Hulán wrote: > In general +1. I'm not sure if official policy changes anything, > prob

Re: [foreman-dev] Taking over plugins - do we need a policy?

2017-07-19 Thread Ewoud Kohl van Wijngaarden
On Wed, Jul 19, 2017 at 10:13:24AM +0200, Marek Hulán wrote: On úterý 18. července 2017 13:15:22 CEST Greg Sutcliffe wrote: Hi all, I've been thinking for a while about plugins, and how to continue them when original authors move on. It's only natural that developers will come and go, so we nee

Re: [foreman-dev] Taking over plugins - do we need a policy?

2017-07-19 Thread Marek Hulán
On úterý 18. července 2017 13:15:22 CEST Greg Sutcliffe wrote: > Hi all, > > I've been thinking for a while about plugins, and how to continue them > when original authors move on. It's only natural that developers will > come and go, so we need to think about how to deal with this. We've got > a

Re: [foreman-dev] Taking over plugins - do we need a policy?

2017-07-18 Thread Daniel Lobato Garcia
On 07/18, Greg Sutcliffe wrote: > Hi all, > > I've been thinking for a while about plugins, and how to continue them > when original authors move on. It's only natural that developers will > come and go, so we need to think about how to deal with this. We've got > a few examples of this now, and ha

Re: [foreman-dev] Taking over plugins - do we need a policy?

2017-07-18 Thread Dmitri Dolguikh
FWIW, the approach I arrived at for smart-proxy plugins: - Explain the original developer their options for hosting the plugin (i.e. within Foreman github organization, and outside of it, and what each option entails). The former implies that Foreman developers have a say over technical matters t