[openstack-dev] [all] cross-project deployment tool meeting

Hi, i just wanted to follow up on this session (https://etherpad.openstack.org/p/newton-deployment-tools-discussion ) were we talked about a cross-project meeting for deployment tools. I would love to see something like that

Re: [openstack-dev] [all] A proposal to separate the design summit

> On 25 Feb 2016, at 15:54, Doug Hellmann wrote: > > Excerpts from Jan Klare's message of 2016-02-25 15:29:08 +0100: >> >>> On 25 Feb 2016, at 13:39, Daniel P. Berrange wrote: >>> >>> On Thu, Feb 25, 2016 at 12:40:27PM +0100, Thierry Carrez wrote: Qiming Teng wrote: > [...] > Wee

Re: [openstack-dev] [all] A proposal to separate the design summit

> On 25 Feb 2016, at 13:39, Daniel P. Berrange wrote: > > On Thu, Feb 25, 2016 at 12:40:27PM +0100, Thierry Carrez wrote: >> Qiming Teng wrote: >>> [...] >>> Week 1: >>> Wednesday-Friday: 3 days Summit. >>>* Primarily an event for marketing, sales, CTOs, architects, >>> operators, jour

Re: [openstack-dev] [all] A proposal to separate the design summit

Hi Qiming, this sounds like a much more pragmatic and practical idea to me and it think just splitting the events into two not parallel parts, but keeping them in the same “week” would also solve most of the problems mentioned in this thread, but allow people to attend both summits without trav

Re: [openstack-dev] [all] Proposal: copyright-holders file in each project, or copyright holding forced to the OpenStack Foundation

> On 15 Jan 2016, at 14:57, Jeremy Stanley wrote: > > On 2016-01-15 07:31:09 -0600 (-0600), Dolph Mathews wrote: >> This is a topic for legal-discuss, not -dev. >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/legal-discuss > > And not only that, but we've discussed it to death in ye

Re: [openstack-dev] [all] Proposal: copyright-holders file in each project, or copyright holding forced to the OpenStack Foundation

Hi Thomas, good thoughts for a very important topic. I am currently refactoring a lot of code inside of the openstack-chef cookbooks and constantly have to ask myself, if i now have to add any copyright thingy to any file or am even allowed to delete the original copyright in a file after chang

Re: [openstack-dev] [chef] deprecation and removal of old branches

active :) ). I will present the final list of still-active-core-reviewers in our next weekly meeting on Monday and we can decide how to proceed. Cheers, Jan > On 08 Jan 2016, at 11:10, Jan Klare wrote: > > Hi, > > Good point, i will talk to infra and figure out how to properly p

Re: [openstack-dev] [chef] deprecation and removal of old branches

Hi, Good point, i will talk to infra and figure out how to properly push these eol tags to the last commits of the branches before we remove them. Since i only got positive feedback on this, i will also go ahead and ask them to help me with the cleanup. Cheers, Jan > On 07 Jan 2016, at 07:42

[openstack-dev] [chef] deprecation and removal of old branches

Hi everybody, due to a hint on this patch https://review.openstack.org/#/c/264130/1 i walked through some of our cookbooks and found that we never actually deprecated or removed the old branches for most of our cookbooks. To do this, we just need to d

[openstack-dev] [chef] Refactoring and cleanup of all cookbooks during the Mitaka cycle

Hi everyone, we have just merged the last patches to branch our stable/liberty release for all our openstack-chef cookbooks (starting right now). During the liberty cycle and at the mitaka design summit we discussed our goals for the current cycle and our next big steps. Since we identified the

Re: [openstack-dev] [HA] RFC: moving Pacemaker openstack-resource-agents to stackforge

+1, sounds great, thanks for the effort cheers, Jan Adam Spiers schrieb am Di., 23. Juni 2015 um 12:28 Uhr: > [cross-posting to openstack-dev and pacemaker lists; please consider > trimming the recipients list if your reply is not relevant to both > communities] > > Hi all, > > https://github.c

[openstack-dev] [chef] Chefstackers Monday Get-together

Hi, if you are interested or even working with Openstack and Chef and attending the summit in Vancouver, you might want to join us on Monday for a nice evening full of discussions around that topic (exact meeting point and time will be announced in the event and again over the mailing list). h

Re: [openstack-dev] Social Monday night

> On May 13, 2015, at 10:51 AM, Thierry Carrez wrote: > > Kevin Benton wrote: >> I thought it would be fun to have a get-together for Neutron developers >> (and anyone else interested in Neutron development) on Monday night to >> get acquainted before we get into the design sessions on Tuesday.

Re: [openstack-dev] [chef][infra] #openstack-meeting-5 proposal to open up

Hi, i think you meant 16:00 UTC == 16:00 GMT == 17:00 BST for our meeting on Monday? Regarding the official meeting room: it would be great if we could get one :) For our second "sync up" meeting on Thursday to include people from Asia, zhiwei and myself agreed that 8:00 UTC would be a fitting t

Re: [openstack-dev] [chef] Feedback to move IRC Monday meeting and time.

Hi, for me (i live in Germany) the full hour (so 15:00 UTC) is fine. Cheers, Jan > On May 6, 2015, at 7:11 PM, JJ Asghar wrote: > > Hey everyone! > > As we move forward with our big tent move[1] Jan suggested we move from our > traditional IRC meeting in our main channel #openstack-chef to