Re: [openstack-dev] [kolla] Committing proprietary plugins to OpenStack

2018-09-17 Thread Eduardo Gonzalez
te may be warranted by the core team. > > > Cheers > > -steve > -- > *From:* Shyam Biradar > *Sent:* Wednesday, September 12, 2018 5:01 AM > *To:* Andreas Jaeger > *Cc:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re:

Re: [openstack-dev] [kolla] Committing proprietary plugins to OpenStack

2018-09-14 Thread Steven Dake (stdake)
Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [kolla] Committing proprietary plugins to OpenStack Yes Andreas, whatever deployment scripts we will be pushing it will be under apache license. [logo] Shyam Biradar Software Engineer | DevOps M +91 8600266938

Re: [openstack-dev] [kolla] Committing proprietary plugins to OpenStack

2018-09-12 Thread Shyam Biradar
Yes Andreas, whatever deployment scripts we will be pushing it will be under apache license. [image: logo] *Shyam Biradar* * Software Engineer | DevOps* M +91 8600266938 | shyam.bira...@trilio.io | trilio.io On Wed, Sep 12, 2018 at 5:24 PM, Andreas Jaeger wrote: > On 2018-09-12 13:21, Shyam

Re: [openstack-dev] [kolla] Committing proprietary plugins to OpenStack

2018-09-12 Thread Andreas Jaeger
On 2018-09-12 13:21, Shyam Biradar wrote: Hi, We have a proprietary openstack plugin. We want to commit deployment scripts like containers and heat templates to upstream in tripleo and kolla project but not actual product code. Is it possible? Or How can we handle this case? Any thoughts