[openstack-dev] [congress] Policy mid cycle summit

We are getting together to discuss the state of policy. RSVP at https://www.eventbrite.com/e/openstack-policy-summit-tickets-12642081807. The meeting will be over two days at the VMware campus in Palo Alto. Join us! Help us develop the agenda here https://etherpad.openstack.org/p/juno-midcycle-

[openstack-dev] [congress] specs update

So I have the spec changes all fixed up and pending reviews https://review.openstack.org/#/c/113638/ https://review.openstack.org/#/c/116530/ https://review.openstack.org/#/c/116531/ https://review.openstack.org/#/c/116532/ Once these are merged, i will start pinging people on blueprints that are

[openstack-dev] [congress] policy summit

I am looking for policy overview/impact covering heat, neutron, nova, olso, mistral, and rubric. Are there any others that want to join us and discuss how policy impacts their project? I would welcome some discussion around Opendaylight policy as well. We have 21 people signed up to join us so

[openstack-dev] [congress] specs update

current specs are updated and current with the project blueprints https://blueprints.launchpad.net/congress enjoy! ~ sean ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-d

[openstack-dev] [congress] For people attending the mid-cycle policy summit

We have a couple of requests for all of you planning to attend the 18-19th September Policy Mid-cycle summit. 1. We’re planning on starting with a series of talks describing the state of policy (current and possibly future) in different projects. We've confirmed people for talks on the follo

Re: [openstack-dev] [nova][neutron][cinder] Averting the Nova crisis by splitting out virt drivers

A somewhat self-serving way to start to solve this is to make training and mentoring as the first steps to getting involved with contributions. We would continue to gradually give more responsibilities as the experience and skills increase. We do this last part already, but are missing the suppo

Re: [openstack-dev] [Congress] Nominating Aaron Rosen for congress-core

+1 ~sean > On Sep 12, 2014, at 11:28 AM, Peter Balland wrote: > > Hello, > > I would like to nominate Aaron Rosen for the congress-core team. > > Aaron has been involved in congress for the last few months providing > valuable reviews as well as leading the keystone integration and > congress

[openstack-dev] Fwd: [openstack-community] A bug on OpenStack

I've reposted your query below to openstack-dev for a greater pool of eyeballs. ~sean Begin forwarded message: From: 武田 剛征 mailto:hisayuki.tak...@oceanearth-corp.com>> Date: December 22, 2013 at 6:17:28 PST To: mailto:commun...@lists.openstack.org>> Subject: [openstack-community] A bug on OpenS

Re: [openstack-dev] People of OpenStack (and their IRC nicks)

I re-noticed that the free form projects involved field in doesn't show up on the personal wiki page. Some weird people like me do more "other" than normal stuff. It would be nice to add that free form field, so others know what us unusuals do too for elections and such. ~sean On Dec 10, 2014

Re: [openstack-dev] The scope of OpenStack wiki [all]

Thanks for bringing this up Stef. I have found while introducing OpenStack fundamentals in the user groups, what seems logical to us, the fully OpenStack immersed, is confusing to newcomers. A specific example comes from the How To Contribute wikipage. Explaining the corporate CLA and CCLA li

[openstack-dev] Vancouver Design Summit format changes

I like it. Thank you for coming up with improvements to the summit planning. One caveat on the definition of project for summit space. Which projects get considered for space is always difficult. Who is going to fill the rooms they request or are they going to have them mostly empty? I'm sure the T

Re: [openstack-dev] Vancouver Design Summit format changes

Inline ~sean > On Jan 9, 2015, at 9:30 AM, Thierry Carrez wrote: > > sean roberts wrote: >> I like it. Thank you for coming up with improvements to the >> summit planning. One caveat on the definition of project for summit >> space. Which projects get considered fo

Re: [openstack-dev] [Congress] Nominating Aaron Rosen for congress-core

On Fri, Sep 12, 2014 at 12:14 PM, Tim Hinrichs wrote: >> +1 >> >> Tim >> >> On Sep 12, 2014, at 11:47 AM, Sean Roberts wrote: >> >> > +1 >> > >> > ~sean >> > >> >> On Sep 12, 2014, at 11:28 AM, Peter Ballan

Re: [openstack-dev] [Congress] PTL Non-Candidacy + Nomination

+1 ~sean > On Sep 29, 2014, at 2:20 PM, Peter Balland wrote: > > It has been an honor to serve as the interim PTL for the Congress project > during Juno. Due to other commitments I have during the Kilo timeframe, I > feel I would not be able to commit the time needed by the growing project.

[openstack-dev] [congress] policy summit specs review

These are the spec action items from the policy summit a few weeks ago. Some of these specs are in the process of being written. See https://github.com/stackforge/congress-specs/tree/master/specs/kilo for the merged specs and https://review.openstack.org/#/q/status:open+project:stackforge/congr

Re: [openstack-dev] [all] Tentative schedule for Kilo Design Summit in Paris

Chance we can move the congress session from Monday 14:30-16:00 to co-locate Tuesday with GBP? either before or after... ~ sean On Oct 7, 2014, at 1:25 AM, Thierry Carrez wrote: > Sylvain Bauza wrote: >> I only see 3 slots for discussing about other projects. Do you know if >> it would be poss

Re: [openstack-dev] [all] Tentative schedule for Kilo Design Summit in Paris

Thx ~sean > On Oct 21, 2014, at 2:18 AM, Thierry Carrez wrote: > > Sean Roberts wrote: >> Chance we can move the congress session from Monday 14:30-16:00 to co-locate >> Tuesday with GBP? either before or after... > > Let me ask Chris Hoge (who is in char

[openstack-dev] [congress] kilo design session

We are scheduled for Monday, 03 Nov, 14:30 - 16:00. I have a conflict with the “Meet the Influencers” talk that runs from 14:30-18:30, plus the GBP session is on Tuesday, 04 Nov, 12:05-12:45. I was thinking we would want to co-located the Congress and GBP talks as much as possible. The BOSH tea

[openstack-dev] [congress] deep dives at the summit, join us!

deep dive congress wed 11am data source drivers dev lounge deep dive congress thur 11am delegation dev lounge reference from the design session etherpad https://etherpad.openstack.org/p/par-kilo-congress-design-session ~ sean _

[openstack-dev] mid-cycle policy summit

September ~Sean Roberts ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] mid-cycle policy summit

I'm thinking location as yahoo Sunnyvale or VMware Palo Alto. ~sean > On Jul 10, 2014, at 5:12 PM, sean roberts wrote: > > The Congress team would like to get us policy people together to discuss how > each project is approaching policy and our common future prior to th

Re: [openstack-dev] [congress] mid-cycle policy summit

I need feedback from the congress team on which two days works for you. 11-12 September 18-19 September ~sean > On Jul 10, 2014, at 5:56 PM, Sean Roberts wrote: > > I'm thinking location as yahoo Sunnyvale or VMware Palo Alto. > > ~sean > >> On Jul 10, 2014, at

[openstack-dev] Use of XML xi:include with xpointer

I'm working on reusing content from remote XML formatted sources to create new content. I'm using xi:include xpointer to a section of an existing XML file. Using the editor oxygen I can see the remote content, so I know my href is valid. But maven fails to build the html from the xml returning b

Re: [openstack-dev] [Openstack-docs] Use of XML xi:include with xpointer

s from a server instance. For information >about the &virt_ext;, see />. > > > etc. > > > Diane > > -- > Diane Fleming > Software Developer II - US > > diane.flem...@rackspace.com > Cell 512.

[openstack-dev] OpenStack Community Training project needs you

We need your help! This is a community driven project to provide the user group community access to OpenStack training materials. We cannot make this work without your help. We are looking for individuals willing to commit to contributing a page at a time. All the details are here http://docs.o

Re: [openstack-dev] Encouraging first-time contributors through bug tags/reviews

How about: First timers assign a bug to a mentor and the mentor takes responsibility for the first timer learning from the bug to completion. Per project, a few people volunteer themselves as mentors. As easy as responding to [project][mentor] emails. On Monday, November 30, 2015, Sean Dague wro

Re: [openstack-dev] Encouraging first-time contributors through bug tags/reviews

Being successful at your first patch for most people means that their first effort is different than an a regular patch. Identifying abandoned work more quickly is good. It doesn't help the first timer. Tagging low hanging fruit for first timers I like. I'm recommending we add a mentor as part of

[openstack-dev] [craton] meeting notes

first team meeting notes here https://etherpad.openstack.org/p/craton-meeting-2016-05-16 We have two weeks until M1, which is a good date to finalize what features we will have in the newton release. We proposed the project name Craton to stick. Let's propose an alternative here quickly if anyone

Re: [openstack-dev] [craton] meeting notes

yes it is. On Mon, May 16, 2016 at 9:36 AM, Tim Bell wrote: > Thanks for the notes. > > > > Is the agreement to work using Craton as a base for the fleet management ? > > > > Tim > > > > *From: *sean roberts > *Reply-To: *"OpenStack Deve

Re: [openstack-dev] [craton] meeting notes

Mon, May 16, 2016 at 8:51 AM, sean roberts wrote: > first team meeting notes here > https://etherpad.openstack.org/p/craton-meeting-2016-05-16 > > We have two weeks until M1, which is a good date to finalize what features > we will have in the newton release. > > We proposed th

Re: [openstack-dev] [craton] meeting notes

I missed that bi-weekly all four meeting slot are taken at 14:30 UTC Mondays. I am going to move the meeting to 15:00 UTC. Speak up if that doesn't work for you. On Mon, May 23, 2016 at 11:45 AM, sean roberts wrote: > Hello project team members. We have one week until M1. We need to

[openstack-dev] [craton] meeting is published

http://eavesdrop.openstack.org/#Craton_Team_Meeting ~ sean __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/

[openstack-dev] [craton] agenda for Monday's team meeting

I'd like to resync what our teams has been working on so we can create a common agenda -- ~sean __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:u

[openstack-dev] [craton] patch submitted to OpenStack project-config

It will transfer both repos -- ~sean __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listin

Re: [openstack-dev] [craton] patch submitted to OpenStack project-config

Once the patch is merged and repos transferred, I will create the gerrit bits and jenkins job config. On Wednesday, June 22, 2016, sean roberts wrote: > It will transfer both repos > > -- > ~sean > -- ~sean _

[openstack-dev] [craton] OneOps CMS demo

Vitaliy is available 9:00 PDT, 15:00 GMT tomorrow. Let's use webex link here https://walmart.webex.com/walmart/j.php?MTID=m2e306e0b4a7fec980b21cdc5a02f7815 This is about the option to fork CMS for use in Craton. Everyone join in! -- ~sean

[openstack-dev] [akanda] outstanding issues from last meeting

*This coming Monday meeting is a holiday, so I propose to cancel the 07 September meeting. * I do want to highlight a few things we need to iron out in the mean time. As part of getting ready for the design summit, the Akanda project needs to elect a PTL. It has been my pleasure to run the weekly

[openstack-dev] [akanda] weekly irc canceled due to summit

I'm thinking of canceling next week's meeting as well unless someone has a burning desire to follow up the summit with another meeting right afterwards. -- ~sean __ OpenStack Development Mailing List (not for usage question

[openstack-dev] [akanda] design session

today, Wednesday 20 may, 14:40-15:20, Dev lounge outside room 220 https://etherpad.openstack.org/p/liberty-akanda-design -- ~sean __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-req

Re: [openstack-dev] [akanda] design session

Neutron sessions moved, so we need to move to 4:30-5:20pm today, dev lounge by room 220. On Wednesday, May 20, 2015, sean roberts wrote: > today, Wednesday 20 may, 14:40-15:20, Dev lounge outside room 220 > https://etherpad.openstack.org/p/liberty-akanda-design > > > -- > ~

Re: [openstack-dev] [akanda] design session

the lounge as if space is available. On Wed, May 20, 2015 at 1:49 PM, sean roberts wrote: > Neutron sessions moved, so we need to move to 4:30-5:20pm today, dev > lounge by room 220. > > > On Wednesday, May 20, 2015, sean roberts wrote: > >> today, Wednesday 20 may,

[openstack-dev] [akanda] Monday dev meeting cancelled

Agenda would be to review the summit design session. I will put notes on the ML on this. -- ~sean __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:

[openstack-dev] [akanda] meeting time change

Starting tomorrow, the akanda project will be meeting on #openstack-meeting at 11:00 PDT. Agenda is in the usual place https://wiki.openstack.org/wiki/Meetings/akanda See you there ~ sean __ OpenStack Development Mailing List

Re: [openstack-dev] [akanda] meeting time change

Note that the 11am PDT meeting has moved to the #openstack-meeting channel On Sun, May 31, 2015 at 2:20 PM, sean roberts wrote: > Starting tomorrow, the akanda project will be meeting on > #openstack-meeting at 11:00 PDT. Agenda is in the usual place > https://wiki.openstack.org/wiki

[openstack-dev] [akanda] work breakdown for milestone 1

Each of us have a few blueprints due third week in june. I need each of us to write up a description, proposed changes, and work items. The work items need to be into 1, 2, 3, 5, 8, 13 approximate hour chunks. I'm okay with this in the blueprint summary if it makes sense, otherwise make the extra e

[openstack-dev] [akanda] prep for m2

Lets make sure we have checked on outstanding reviews

[openstack-dev] [congress] sprinting towards Kilo2

Over the last couple of meetings, we have discussed holding a hackathon this Thursday and Friday. You each have some code you are working on. Let’s each pick a 3-4 hour block of time to intensively collaborate. We can use the #congress IRC channel and google hangout. Reply to this thread, so we ca

Re: [openstack-dev] [congress] sprinting towards Kilo2

, 2015, sean roberts wrote: > Over the last couple of meetings, we have discussed holding a hackathon > this Thursday and Friday. You each have some code you are working on. Let’s > each pick a 3-4 hour block of time to intensively collaborate. We can use > the #congress IRC channe

Re: [openstack-dev] [congress] sprinting towards Kilo2

started congress sprint hangout https://plus.google.com/hangouts/_/gwspatjycr3rore6smdkganufua and / or join on the #congress channel On Wed, Feb 4, 2015 at 4:59 PM, sean roberts wrote: > Join the Congress team to push your code over the milestone line. The > Congress team will be onlin

[openstack-dev] [congress] following up on releasing kilo milestone 2

At our last meeting I volunteered to figure out what we need to do for milestone 2. Here is what I propose: Repo cleanup: We tag today's release with 2015.1.0b2. This is copying tag the other openstack projects are using. I believe below is the correct syntax. Let me know if there is a cleaner way

Re: [openstack-dev] [congress] following up on releasing kilo milestone 2

so git checkout master git pull https://git.openstack.org/stackforge/congress.git dbef982ea72822e0b7acc16da9b6ac89d3cf3530 git tag -s 2015.1.0b2 git push gerrit 2015.1.0b2 On Wed, Feb 11, 2015 at 5:26 PM, James E. Blair wrote: > sean roberts writes: > > > At our last meeting I vo

Re: [openstack-dev] [congress][Policy][Copper]Collaboration between OpenStack Congress and OPNFV Copper

ith. >>>>> >>>>> Tim >>>>> >>>>> >>>>> >>>>> >>>>>> On Feb 12, 2015, at 6:49 PM, Zhipeng Huang wrote: >>>>>> >>>>>> THX Tim! >>>>>> >

Re: [openstack-dev] [congress] following up on releasing kilo milestone 2

I will take a close look and see what mods I need to make. Or we could just move the congress repo :) Thanks for reaching out on this. On Thursday, February 12, 2015, Thierry Carrez wrote: > Thierry Carrez wrote: > > You could also try to use the milestone.sh release script I use: > > > > http:/

[openstack-dev] [congress] missing today's meeting

I'm in an all day board meeting. My update is https://launchpad.net/congress/kilo is cleaned up. tagged https://github.com/stackforge/congress/tree/2015.1.0b2 is out. I am still working out getting the tarred file out to http://tarballs.openstack.org/ as part of the process. ~ sean __

[openstack-dev] [congress] is an openstack project

All is left now is to patch infra to copy the three repos from stackforge. Aaron can you take that on? Congratulations team! ~ sean __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-re

Re: [openstack-dev] Retirement of astara repos?

It’s my understanding that the development has been moved back into DreamHost. I stopped working on it over two years ago. I’ll ping them to double check that repo retiring is what they want. Thanks for asking first! On Wed, Jan 10, 2018 at 21:56 Swapnil Kulkarni wrote: > On Thu, Jan 11, 2018 a

[openstack-dev] [craton] branch clean up and other stuff

I'm going to have to miss this mornings meeting again. Here out my outstanding issues - project patch https://review.openstack.org/#/c/332470/9, is pending a request to clean up the branches in the craton repo. Once the repo is moved, branch cleanup is expensive time wise. Branches are typically mi