Re: [openstack-dev] [all] [tc] [api] Paste Maintenance

2018-10-24 Thread Chris Dent
On Wed, 24 Oct 2018, Jean-Philippe Evrard wrote: On Mon, 2018-10-22 at 07:50 -0700, Morgan Fainberg wrote: Also, doesn't bitbucket have a git interface now too (optionally)? It does :) But I think it requires a new repo, so it means that could as well move to somewhere else like github or

Re: [openstack-dev] [all] [tc] [api] Paste Maintenance

2018-10-24 Thread Jean-Philippe Evrard
On Mon, 2018-10-22 at 07:50 -0700, Morgan Fainberg wrote: > Also, doesn't bitbucket have a git interface now too (optionally)? > It does :) But I think it requires a new repo, so it means that could as well move to somewhere else like github or openstack infra :p

Re: [openstack-dev] [all] [tc] [api] Paste Maintenance

2018-10-23 Thread Chris Dent
On Mon, 22 Oct 2018, Chris Dent wrote: Thus far I'm not hearing any volunteers. If that continues to be the case, I'll just keep it on bitbucket as that's the minimal change. As there was some noise that suggested "if you make it use git I might help", I put it on github:

Re: [openstack-dev] [all] [tc] [api] Paste Maintenance

2018-10-22 Thread Ben Nemec
On 10/22/18 10:32 AM, Morgan Fainberg wrote: I can spin up the code and make it available. There is an example (highly-flask specific right now, but would be easy to make it generic) from keystone [0] has been implemented. Where should this code live? A new library? oslo.?  The

Re: [openstack-dev] [all] [tc] [api] Paste Maintenance

2018-10-22 Thread Zane Bitter
On 22/10/18 10:38 AM, Thomas Goirand wrote: On 10/22/18 12:55 PM, Chris Dent wrote: My assumption is that it's "something we plan to minimally maintain because we depend on it". in which case all options would work: the exact choice depends on whether there is anybody interested in helping

Re: [openstack-dev] [all] [tc] [api] Paste Maintenance

2018-10-22 Thread Morgan Fainberg
I can spin up the code and make it available. There is an example (highly-flask specific right now, but would be easy to make it generic) from keystone [0] has been implemented. Where should this code live? A new library? oslo.? The aforementioned example would need "external middleware via

Re: [openstack-dev] [all] [tc] [api] Paste Maintenance

2018-10-22 Thread Sean McGinnis
On Mon, Oct 22, 2018 at 07:49:35AM -0700, Morgan Fainberg wrote: > I should be able to do a write up for Keystone's removal of paste *and* > move to flask soon. > > I can easily extract the bit of code I wrote to load our external > middleware (and add an external loader) for the transition away

Re: [openstack-dev] [all] [tc] [api] Paste Maintenance

2018-10-22 Thread Morgan Fainberg
Also, doesn't bitbucket have a git interface now too (optionally)? On Mon, Oct 22, 2018, 07:49 Morgan Fainberg wrote: > I should be able to do a write up for Keystone's removal of paste *and* > move to flask soon. > > I can easily extract the bit of code I wrote to load our external >

Re: [openstack-dev] [all] [tc] [api] Paste Maintenance

2018-10-22 Thread Morgan Fainberg
I should be able to do a write up for Keystone's removal of paste *and* move to flask soon. I can easily extract the bit of code I wrote to load our external middleware (and add an external loader) for the transition away from paste. I also think paste is terrible, and would be willing to help

Re: [openstack-dev] [all] [tc] [api] Paste Maintenance

2018-10-22 Thread Thomas Goirand
On 10/22/18 12:55 PM, Chris Dent wrote: >> My assumption is that it's "something we plan to minimally maintain >> because we depend on it". in which case all options would work: the >> exact choice depends on whether there is anybody interested in helping >> maintaining it, and where those

Re: [openstack-dev] [all] [tc] [api] Paste Maintenance

2018-10-22 Thread Chris Dent
On Fri, 19 Oct 2018, Thierry Carrez wrote: Ed Leafe wrote: On Oct 15, 2018, at 7:40 AM, Chris Dent wrote: I'd like some input from the community on how we'd like this to go. I would say it depends on the long-term plans for paste. Are we planning on weaning ourselves off of paste, and

Re: [openstack-dev] [all] [tc] [api] Paste Maintenance

2018-10-19 Thread Thierry Carrez
Ed Leafe wrote: On Oct 15, 2018, at 7:40 AM, Chris Dent wrote: I'd like some input from the community on how we'd like this to go. I would say it depends on the long-term plans for paste. Are we planning on weaning ourselves off of paste, and simply need to maintain it until that can be

Re: [openstack-dev] [all] [tc] [api] Paste Maintenance

2018-10-15 Thread Lance Bragstad
On Mon, Oct 15, 2018 at 8:52 AM Ed Leafe wrote: > On Oct 15, 2018, at 7:40 AM, Chris Dent wrote: > > > > I'd like some input from the community on how we'd like this to go. > > I would say it depends on the long-term plans for paste. Are we planning > on weaning ourselves off of paste, and

Re: [openstack-dev] [all] [tc] [api] Paste Maintenance

2018-10-15 Thread Ed Leafe
On Oct 15, 2018, at 7:40 AM, Chris Dent wrote: > > I'd like some input from the community on how we'd like this to go. I would say it depends on the long-term plans for paste. Are we planning on weaning ourselves off of paste, and simply need to maintain it until that can be completed, or are

Re: [openstack-dev] [all] [tc] [api] Paste Maintenance

2018-10-15 Thread Sean McGinnis
On Mon, Oct 15, 2018 at 01:40:37PM +0100, Chris Dent wrote: > > Back in August [1] there was an email thread about the Paste package > being essentially unmaintained and several OpenStack projects still > using it. At that time we reached the conclusion that we should > investigate having