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

[sean roberts]

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 at 3:50 AM, Sean McGinnis 
> wrote:
> > While going through various repos looking at things to be cleaned up, I
> noticed the last commit for openstack/astara
> > was well over a year ago. Based on this and the little bit I have
> followed with this project, it’s my understanding that
> > there is no further work planned with Astara.
> >
> > Should these repos be retired at this point? Or is there a reason to
> keep things around?
> >
> > Thanks,
> >
> > Sean McGinnis (smcginnis)
> >
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> Sean,
>
> There have been a set of e-mails from Andreas in Dec for the inactive
> projects [1] [2] [3] [4] with less or no responce. Just FYI.
>
> [1] Astara:
> http://lists.openstack.org/pipermail/openstack-dev/2017-December/125350.html
> [2] Cerberor:
> http://lists.openstack.org/pipermail/openstack-dev/2017-December/125351.html
> [3] Evoque:
> http://lists.openstack.org/pipermail/openstack-dev/2017-December/125352.html
> [4] puppet-apps-site:
>
> http://lists.openstack.org/pipermail/openstack-dev/2017-December/125360.html
>
> ~coolsvap
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-- 
~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/listinfo/openstack-dev

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

[sean roberts]

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 minor
and major releases only.
- allocating devs to the project. I'm getting spun up around a few teams.
After the watcher, nova mid cycle this week. I will have a better idea who
is available.
- forking OneOps CMS repos as code base start. We are definitely interested
internally in doing this. I suggest I get my devs to propose how the fork
would look and what the implications are. Then the craton team as whole can
discuss the merits and modifications to the approach.



-- 
~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/listinfo/openstack-dev

[openstack-dev] [craton] OneOps CMS demo

[sean roberts]

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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[sean roberts]

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 <seanrobert...@gmail.com> wrote:

> It will transfer both repos
>
> --
> ~sean
>


-- 
~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/listinfo/openstack-dev

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

[sean roberts]

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/listinfo/openstack-dev

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

[sean roberts]

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:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [craton] meeting is published

[sean roberts]

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/cgi-bin/mailman/listinfo/openstack-dev

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

[sean roberts]

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 <seanrobert...@gmail.com>
wrote:

> Hello project team members. We have one week until M1. We need to discuss
> some details of what should be in the Newton release of Craton. Since no
> one has commented on the project name, I am going to assume we all agree to
> the name Craton. I will push the meeting patch to get it published.
>
>
>
> On Mon, May 16, 2016 at 8:51 AM, sean roberts <seanrobert...@gmail.com>
> 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 the project name Craton to stick. Let's propose an
>> alternative here quickly if anyone wants.
>>
>> We agreed to hold meetbot IRC meetings 07:30 PDT. The
>> #openstack-meeting-4 slot is available.
>>
>> We agreed to move all email to openstack-dev@lists.openstack.org with
>> the subject starting with [craton]
>>
>> The chat.freenode.net IRC channel #craton is up and running, but not
>> logged yet.
>>
>> We want to target getting together face to face around the time of the
>> yet to be scheduled Operators Mid-Cycle. 19 July Watcher mid-cycle in
>> hillsboro, OR may be the area and time.
>>
>> I am happy to patch both the IRC meeting and craton logging patches, as
>> soon as we decide.
>>
>> I would recommend that we decide on these items today or tomorrow, so we
>> can get started on important project work.
>>
>> ~ sean
>>
>
>
>
> --
>
> ~ sean
>



-- 

~ 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/listinfo/openstack-dev

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

[sean roberts]

Hello project team members. We have one week until M1. We need to discuss
some details of what should be in the Newton release of Craton. Since no
one has commented on the project name, I am going to assume we all agree to
the name Craton. I will push the meeting patch to get it published.



On Mon, May 16, 2016 at 8:51 AM, sean roberts <seanrobert...@gmail.com>
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 the project name Craton to stick. Let's propose an alternative
> here quickly if anyone wants.
>
> We agreed to hold meetbot IRC meetings 07:30 PDT. The #openstack-meeting-4
> slot is available.
>
> We agreed to move all email to openstack-dev@lists.openstack.org with the
> subject starting with [craton]
>
> The chat.freenode.net IRC channel #craton is up and running, but not
> logged yet.
>
> We want to target getting together face to face around the time of the yet
> to be scheduled Operators Mid-Cycle. 19 July Watcher mid-cycle in
> hillsboro, OR may be the area and time.
>
> I am happy to patch both the IRC meeting and craton logging patches, as
> soon as we decide.
>
> I would recommend that we decide on these items today or tomorrow, so we
> can get started on important project work.
>
> ~ sean
>



-- 

~ 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/listinfo/openstack-dev

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

[sean roberts]

yes it is.

On Mon, May 16, 2016 at 9:36 AM, Tim Bell <tim.b...@cern.ch> wrote:

> Thanks for the notes.
>
>
>
> Is the agreement to work using Craton as a base for the fleet management ?
>
>
>
> Tim
>
>
>
> *From: *sean roberts <seanrobert...@gmail.com>
> *Reply-To: *"OpenStack Development Mailing List (not for usage
> questions)" <openstack-dev@lists.openstack.org>
> *Date: *Monday 16 May 2016 at 17:51
> *To: *"openstack-dev@lists.openstack.org" <
> openstack-dev@lists.openstack.org>
> *Subject: *[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 wants.
>
>
>
> We agreed to hold meetbot IRC meetings 07:30 PDT. The #openstack-meeting-4
> slot is available.
>
>
>
> We agreed to move all email to openstack-dev@lists.openstack.org with the
> subject starting with [craton]
>
>
>
> The chat.freenode.net IRC channel #craton is up and running, but not
> logged yet.
>
>
>
> We want to target getting together face to face around the time of the yet
> to be scheduled Operators Mid-Cycle. 19 July Watcher mid-cycle in
> hillsboro, OR may be the area and time.
>
>
>
> I am happy to patch both the IRC meeting and craton logging patches, as
> soon as we decide.
>
>
>
> I would recommend that we decide on these items today or tomorrow, so we
> can get started on important project work.
>
>
>
> ~ 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/listinfo/openstack-dev
>
>


-- 

~ 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/listinfo/openstack-dev

[openstack-dev] [craton] meeting notes

[sean roberts]

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 wants.

We agreed to hold meetbot IRC meetings 07:30 PDT. The #openstack-meeting-4
slot is available.

We agreed to move all email to openstack-dev@lists.openstack.org with the
subject starting with [craton]

The chat.freenode.net IRC channel #craton is up and running, but not logged
yet.

We want to target getting together face to face around the time of the yet
to be scheduled Operators Mid-Cycle. 19 July Watcher mid-cycle in
hillsboro, OR may be the area and time.

I am happy to patch both the IRC meeting and craton logging patches, as
soon as we decide.

I would recommend that we decide on these items today or tomorrow, so we
can get started on important project work.

~ 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/listinfo/openstack-dev

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

[sean roberts]

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  wrote:

> On 11/25/2015 03:22 PM, Shamail wrote:
> > Hi,
> >
> >> On Nov 25, 2015, at 11:05 PM, Doug Hellmann  > wrote:
> >>
> >> Excerpts from Shamail Tahir's message of 2015-11-25 09:15:54 -0500:
> >>> Hi everyone,
> >>>
> >>> Andrew Mitry recently shared a medium post[1] by Kent C. Dobbs which
> >>> discusses how one open-source project is encouraging contributions by
> new
> >>> open-source contributors through a combination of a special tag (which
> is
> >>> associated with work that is needed but can only be completed by
> someone
> >>> who is a first-time contributor) and helpful comments in the review
> phase
> >>> to ensure the contribution(s) eventually get merged.
> >>>
> >>> While reading the article, I immediately thought about our
> >>> low-hanging-fruit bug tag which is used for a very similar purpose in
> "bug
> >>> fixing" section of  the "how to contribute" page[2].  The
> low-hanging-fruit
> >>> tag is used to identify items that are generally suitable for
> first-time or
> >>> beginner contributors but, in reality, anyone can pick them up.
> >>>
> >>> I wanted to propose a new tag (or even changing the, existing,
> low-hanging
> >>> fruit tag) that would identify items that we are reserving for
> first-time
> >>> OpenStack contributors (e.g. a patch-set for the item submitted by
> someone
> >>> who is not a first time contributor would be rejected)... The same
> article
> >>> that Andrew shared mentions using an "up-for-grabs" tag which also
> >>> populates the items at up-for-grabs[3] (a site where people looking to
> >>> start working on open-source projects see entry-level items from
> multiple
> >>> projects).  If we move forward with an exclusive tag for first-timers
> then
> >>> it would be nice if we could use the up-for-grabs tag so that OpenStack
> >>> also shows up on the list too.  Please let me know if this change
> should be
> >>> proposed elsewhere, the tags are maintained in launchpad and the wiki I
> >>> found related to bug tags[4] didn't indicate a procedure for
> submitting a
> >>> change proposal.
> >>
> >> I like the idea of making bugs suitable for first-timers more
> >> discoverable. I'm not sure we need to *reserve* any bugs for any class
> >> of contributor. What benefit do you think that provides?
> > I would have to defer to additional feedback here...
> >
> > My own perspective from when I was doing my first contribution is that
> it was hard to find active "low-hanging-fruit" items.  Most were already
> work-in-progress or assigned.
>
> This was a direct consequence of us dropping the auto-abandoning of old
> code reviews in gerrit. When a review is abandoned the bug is flipped
> back to New instead of In Progress.
>
> I found quite often people go and gobble up bugs assigning them to
> themselves, but don't make real progress on them. Then new contributors
> show up, and don't work on any of those issues because our tools say
> someone is already on top of it.
>
> -Sean
>
> --
> Sean Dague
> http://dague.net
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>


-- 
~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/listinfo/openstack-dev

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

[sean roberts]

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 the idea, so the project mentor is responsible for the
work and the first timer learning.

On Monday, November 30, 2015, Doug Hellmann  wrote:

> Excerpts from sean roberts's message of 2015-11-30 07:57:54 -0800:
> > 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.
>
> That would mean the learning process is different from what we want the
> regular process to be.
>
> If the problem is identifying "In Progress" bugs that are actually not
> being worked on, then let's figure out a way to make that easier.
> sdague's point about the auto-abandon process may help. We could query
> gerrit for "stale" reviews that would have met the old abandon
> requirements and that refer to bugs, for example. Using that
> information, someone could follow-up with the patch owner to see if it
> is actually abandoned, before changing the bug status or encouraging the
> owner to abandon the patch.
>
> >
> > Per project, a few people volunteer themselves as mentors. As easy as
> > responding to [project][mentor] emails.
> >
> > On Monday, November 30, 2015, Sean Dague >
> wrote:
> >
> > > On 11/25/2015 03:22 PM, Shamail wrote:
> > > > Hi,
> > > >
> > > >> On Nov 25, 2015, at 11:05 PM, Doug Hellmann  
> > > > wrote:
> > > >>
> > > >> Excerpts from Shamail Tahir's message of 2015-11-25 09:15:54 -0500:
> > > >>> Hi everyone,
> > > >>>
> > > >>> Andrew Mitry recently shared a medium post[1] by Kent C. Dobbs
> which
> > > >>> discusses how one open-source project is encouraging contributions
> by
> > > new
> > > >>> open-source contributors through a combination of a special tag
> (which
> > > is
> > > >>> associated with work that is needed but can only be completed by
> > > someone
> > > >>> who is a first-time contributor) and helpful comments in the review
> > > phase
> > > >>> to ensure the contribution(s) eventually get merged.
> > > >>>
> > > >>> While reading the article, I immediately thought about our
> > > >>> low-hanging-fruit bug tag which is used for a very similar purpose
> in
> > > "bug
> > > >>> fixing" section of  the "how to contribute" page[2].  The
> > > low-hanging-fruit
> > > >>> tag is used to identify items that are generally suitable for
> > > first-time or
> > > >>> beginner contributors but, in reality, anyone can pick them up.
> > > >>>
> > > >>> I wanted to propose a new tag (or even changing the, existing,
> > > low-hanging
> > > >>> fruit tag) that would identify items that we are reserving for
> > > first-time
> > > >>> OpenStack contributors (e.g. a patch-set for the item submitted by
> > > someone
> > > >>> who is not a first time contributor would be rejected)... The same
> > > article
> > > >>> that Andrew shared mentions using an "up-for-grabs" tag which also
> > > >>> populates the items at up-for-grabs[3] (a site where people
> looking to
> > > >>> start working on open-source projects see entry-level items from
> > > multiple
> > > >>> projects).  If we move forward with an exclusive tag for
> first-timers
> > > then
> > > >>> it would be nice if we could use the up-for-grabs tag so that
> OpenStack
> > > >>> also shows up on the list too.  Please let me know if this change
> > > should be
> > > >>> proposed elsewhere, the tags are maintained in launchpad and the
> wiki I
> > > >>> found related to bug tags[4] didn't indicate a procedure for
> > > submitting a
> > > >>> change proposal.
> > > >>
> > > >> I like the idea of making bugs suitable for first-timers more
> > > >> discoverable. I'm not sure we need to *reserve* any bugs for any
> class
> > > >> of contributor. What benefit do you think that provides?
> > > > I would have to defer to additional feedback here...
> > > >
> > > > My own perspective from when I was doing my first contribution is
> that
> > > it was hard to find active "low-hanging-fruit" items.  Most were
> already
> > > work-in-progress or assigned.
> > >
> > > This was a direct consequence of us dropping the auto-abandoning of old
> > > code reviews in gerrit. When a review is abandoned the bug is flipped
> > > back to New instead of In Progress.
> > >
> > > I found quite often people go and gobble up bugs assigning them to
> > > themselves, but don't make real progress on them. Then new contributors
> > > show up, and don't work on any of those issues because our tools say
> > > someone is already on top of it.
> > >
> > > -Sean
> > >
> > > --
> > > Sean Dague
> > > http://dague.net
> > >
> > >
> 

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

[sean roberts]

*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 Akanda development
meetings this year. As we transition into being a fully functional project,
we need a someone who has shown technical leadership in the project to
date. That person is Adam Gandelman. I nominate Adam to be the Akanda PTL.
We can delay the voting until the next meeting, but I wanted to put it out
there for discussion.

Set F2F hack for either week of 13 sept PDX, week of 20 sept SFO, or week
of 27 Sept PDX. Adam will be able to attend if we do PDX. Mark's schedule
is really tight. I would like to hold it 28-29 Sept in PDX. That should
allow everyone to join. Let's agree soonish so I can find a space for us
and we can start booking things.

Set either 10 or 17 sept for Mitaka design summit planning.

~ 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/listinfo/openstack-dev

[openstack-dev] [akanda] prep for m2

[sean roberts]

Lets make sure we have checked on outstanding reviews
https://review.openstack.org/#/q/status:open+project:stackforge/akanda-appliance+OR+project:stackforge/akanda-appliance+OR+project:stackforge/akanda-appliance-builder+OR+project:stackforge/akanda-rug+OR+project:stackforge/akanda-horizon+OR+project:stackforge/akanda-neutron,n,z,
double checked on past outstanding actions from our last meeting, pushing
outstanding patches to gerrit.

~ 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/listinfo/openstack-dev

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

[sean roberts]

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
effort for a spec.

~ 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/listinfo/openstack-dev

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

[sean roberts]

Note that the 11am PDT meeting has moved to the #openstack-meeting channel

On Sun, May 31, 2015 at 2:20 PM, sean roberts seanrobert...@gmail.com
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/Meetings/akanda
 See you there

 ~ sean




-- 

~ 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/listinfo/openstack-dev

[openstack-dev] [akanda] meeting time change

[sean roberts]

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 (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[sean roberts]

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:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[sean roberts]

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 seanrobert...@gmail.com wrote:

 today, Wednesday 20 may, 14:40-15:20, Dev lounge outside room 220
 https://etherpad.openstack.org/p/liberty-akanda-design


 --
 ~sean



-- 
~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/listinfo/openstack-dev

[openstack-dev] [akanda] design session

[sean roberts]

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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[sean roberts]

The neutron work sessions schedule changed last minute today, so we needed
to adapt. It looks like 1:30pm tomorrow is the remaining time slot where no
time conflicts exist. Plan to meet outside room 220 in the developer lounge
area as it has been a bit less crowded. We can move a bit deeper into the
lounge as if space is available.

On Wed, May 20, 2015 at 1:49 PM, sean roberts seanrobert...@gmail.com
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 seanrobert...@gmail.com wrote:

 today, Wednesday 20 may, 14:40-15:20, Dev lounge outside room 220
 https://etherpad.openstack.org/p/liberty-akanda-design


 --
 ~sean



 --
 ~sean




-- 

~ 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/listinfo/openstack-dev

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

[sean roberts]

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 questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[sean roberts]

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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[sean roberts]

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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[sean roberts]

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 thie...@openstack.org
wrote:

 Thierry Carrez wrote:
  You could also try to use the milestone.sh release script I use:
 
  http://git.openstack.org/cgit/openstack-infra/release-tools/tree/

 Hrm... I now realize the script is forcing openstack/* namespace and
 won't work as-is for stackforge projects.

 That repo is accepting patches, though :)

 --
 Thierry Carrez (ttx)

 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
~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/listinfo/openstack-dev

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

[Sean Roberts]

I'm good for either time Tuesday. 

~sean

 On Feb 16, 2015, at 15:45, Tim Hinrichs thinri...@vmware.com wrote:
 
 Lets default to 3p/7a if we don't hear from Bryan.
 
 Tim
 
 P. S. Pardon the brevity. Sent from my mobile. 
 
 On Feb 15, 2015, at 10:15 PM, Zhipeng Huang zhipengh...@gmail.com wrote:
 
 2 - 4 pm Tuesday (which means 6 - 8 am China Wed) should work for me. Let's 
 see if Bryan is ok with the time slot. And yes you don't need an account :)
 
 On Mon, Feb 16, 2015 at 1:36 PM, Tim Hinrichs thinri...@vmware.com wrote:
 I just realized Monday is a holiday. What about 8a, 10a, 2-4p Tuesday?
 
 I'm happy to try out gotomeeting.  Looks like I don't need an account, 
 right?
 
 Tim
 
 P. S. Pardon the brevity. Sent from my mobile. 
 
 On Feb 13, 2015, at 4:25 PM, Zhipeng Huang zhipengh...@gmail.com wrote:
 
 Hi Tim,
 
 Monday 9am PST should be ok for me, it is better if u guys could do 4 - 5 
 pm, but let's settle on 9 am for now, see if Bryan and others would be ok. 
 Regarding meeting tools, in opnfv we use GoToMeeting a lot, would u guys 
 be ok with that? Or should we have a Google Hangout?
 
 On Feb 14, 2015 8:04 AM, Tim Hinrichs thinri...@vmware.com wrote:
 Hi Zhipeng,
 
 Sure we can talk online Mon/Tue.  If you come up with some times the 
 Copper team is available, I’ll do the same for a few of the Congress 
 team.  We’re usually available 9-4p Pacific, and for me Monday looks 
 better than Tuesday.
 
 If we schedule an hour meeting in Santa Rosa for Wed at say 1:30 or 2p, 
 I’ll do my best to make it there.  Even if I can’t make it, you’ll always 
 have Sean to talk with.
 
 Tim
 
 
 
 
 On Feb 12, 2015, at 6:49 PM, Zhipeng Huang zhipengh...@gmail.com wrote:
 
 THX Tim!
 
 I think It'd be great if we could have some online discussion ahead of 
 F2F LFC summit.We could have the crash course early next week (Monday or 
 Tuesday), and then Bryan could discuss with Sean in detail when they 
 met, with specific questions. 
 
 Would this be ok for everyone ? 
 
 On Fri, Feb 13, 2015 at 7:21 AM, Tim Hinrichs thinri...@vmware.com 
 wrote:
 Bryan and Zhipeng,
 
 Sean Roberts (CCed) is planning to be in Santa Rosa.   Sean’s 
 definitely there on Wed.  Less clear about Thu/Fri.
 
 I don’t know if I’ll make the trip yet, but I’m guessing Wed early 
 afternoon if I can.  
 
 Tim
 
 
 On Feb 11, 2015, at 9:04 PM, SULLIVAN, BRYAN L bs3...@att.com wrote:
 
 Hi Tim,
 
  
 It would be great to meet with members of the Congress project if 
 possible at our meetup in Santa Rosa. I plan by then to have a basic 
 understanding of Congress and some test driver apps / use cases to 
 demo at the meetup. The goal is to assess the current state of 
 Congress support for the use cases on the OPNFV wiki: 
 https://wiki.opnfv.org/copper/use_cases
 
  
 I would be doing the same with ODL but I’m not as far on getting ready 
 with it. So the opportunity to discuss the use cases under Copper and 
 the other policy-related projects
 
 (fault management, resource management, resource scheduler) with 
 Congress experts would be great.
 
  
 Once we understand the gaps in what we are trying to build in OPNFV, 
 the goal for our first OPNFV release is to create blueprints for new 
 work in Congress. We might also just find some bugs and get directly 
 involved in Congress to address them, or start a collaborative 
 development project in OPNFV for that. TBD
 
  
 Thanks,
 
 Bryan Sullivan | Service Standards | ATT
 
  
 From: Tim Hinrichs [mailto:thinri...@vmware.com] 
 Sent: Wednesday, February 11, 2015 10:22 AM
 To: OpenStack Development Mailing List (not for usage questions)
 Cc: SULLIVAN, BRYAN L; HU, BIN; Rodriguez, Iben; Howard Huang
 Subject: Re: [openstack-dev] [congress][Policy][Copper]Collaboration 
 between OpenStack Congress and OPNFV Copper
 
  
 
 Hi Zhipeng,
 
  
 
 We’d be happy to meet.  Sounds like fun!  
 
  
 
 I don’t know of anyone on the Congress team who is planning to attend 
 the LF collaboration summit.  But we might be able to send a couple of 
 people if it’s the only real chance to have a face-to-face.  
 Otherwise, there are a bunch of us in and around Palo Alto.  And of 
 course, phone/google hangout/irc are fine options as well.
 
  
 
 Tim
 
  
 
  
 
  
 
 On Feb 11, 2015, at 8:59 AM, Zhipeng Huang zhipengh...@gmail.com 
 wrote:
 
  
 
 Hi Congress Team,
 
  
 
 As you might already knew, we had a project in OPNFV covering 
 deployment policy called  Copper, in which we identify Congress as one 
 of the upstream projects that we need to put our requirement to. Our 
 team has been working on setting up a simple openstack environment 
 with congress integrated that could demo simple use cases for policy 
 deployment.
 
  
 
 Would it possible for you guys and our team to find a time do an 
 Copper/Congress interlock meeting, during which Congress Team could 
 introduce how to best integrate congress with vanilla openstack? 
 Will some of you attend LF Collaboration Summit?
 
  
 
 Thanks a lot

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

[sean roberts]

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 and/or if setting the head pointer to a
specific commit is more accurate.

git checkout master
git pull --ff-only
git tag -s 2015.1.0b2
git push gerrit 2015.1.0b2


Launchpad cleanup:
I move all the blueprints and bugs from the juno series and kilo m1 to kilo
m2. I then remove the juno series and kilo m1. I release kilo m2. I upload
the congress tar file kilo m2.

Next Steps:
We target releasing kilo m3 on 19 march and repeating most of the above
steps. I won't be deleting any milestones or series this time. We also
target releasing the congress kilo release on 30 april.

~ 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/listinfo/openstack-dev

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

[sean roberts]

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 cor...@inaugust.com wrote:

 sean roberts seanrobert...@gmail.com writes:

  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 and/or if setting the head pointer to a
  specific commit is more accurate.
 
  git checkout master
  git pull --ff-only
  git tag -s 2015.1.0b2
  git push gerrit 2015.1.0b2

 Yes, this matches:

   http://docs.openstack.org/infra/manual/drivers.html#tagging-a-release

 But yes, if you want to tag a specific commit instead of the tip of
 master, you can do that.

 -Jim

 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




-- 

~ 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/listinfo/openstack-dev

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

[sean roberts]

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 seanrobert...@gmail.com
wrote:

 Join the Congress team to push your code over the milestone line. The
 Congress team will be online from 9am to 5pm over the next two days. Reach
 out through the #congress IRC channel. We will start a google hangout and
 post the URL in the #congress channel.

 See you there!


 On Tuesday, February 3, 2015, sean roberts seanrobert...@gmail.com
 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 channel and google hangout.

 Reply to this thread, so we can allocate people’s time.

 ~ sean



 --
 ~sean




-- 

~ 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/listinfo/openstack-dev

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

[sean roberts]

Join the Congress team to push your code over the milestone line. The
Congress team will be online from 9am to 5pm over the next two days. Reach
out through the #congress IRC channel. We will start a google hangout and
post the URL in the #congress channel.

See you there!

On Tuesday, February 3, 2015, sean roberts seanrobert...@gmail.com 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 channel and google hangout.

 Reply to this thread, so we can allocate people’s time.

 ~ sean



-- 
~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/listinfo/openstack-dev

[openstack-dev] [congress] sprinting towards Kilo2

[sean roberts]

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 can allocate people’s time.

~ 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/listinfo/openstack-dev

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

[Sean Roberts]

Inline

~sean

 On Jan 9, 2015, at 9:30 AM, Thierry Carrez thie...@openstack.org 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 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 TC can figure it out by looking at the number
 of contributors or something like that. I would however, like to know a
 bit more of your plan for this specific part of the proposal sooner than
 later.   
 
 That would be any OpenStack project, with the project structure reform
 hopefully completed by then. That would likely let projects that were
 previously in the other projects track have time to apply and to be
 considered full Design Summit citizens. The presence of a busy other
 projects track to cover for unofficial projects in previous summits
 really was an early sign that something was wrong with our definition of
 OpenStack projects anyway :)
Got it. This is going in the right direction. 

 
 Now I expect the TC to split the limited resources following metrics
 like team size and development activity. Small projects might end up
 having just a couple sessions in mostly-empty rooms, yes... still better
 than not giving space at all.
Agreed. I don't want to starve innovation at the summits. 

 
 -- 
 Thierry Carrez (ttx)
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[openstack-dev] Vancouver Design Summit format changes

[sean roberts]

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 TC can figure it out by looking at the number of
contributors or something like that. I would however, like to know a bit
more of your plan for this specific part of the proposal sooner than
later.

On Friday, January 9, 2015, Thierry Carrez thie...@openstack.org
javascript:_e(%7B%7D,'cvml','thie...@openstack.org'); wrote:

 Hi everyone,

 The OpenStack Foundation staff is considering a number of changes to the
 Design Summit format for Vancouver, changes on which we'd very much like
 to hear your feedback.

 The problems we are trying to solve are the following:
 - Accommodate the needs of more OpenStack projects
 - Reduce separation and perceived differences between the Ops Summit and
 the Design/Dev Summit
 - Create calm and less-crowded spaces for teams to gather and get more
 work done

 While some sessions benefit from large exposure, loads of feedback and
 large rooms, some others are just workgroup-oriented work sessions that
 benefit from smaller rooms, less exposure and more whiteboards. Smaller
 rooms are also cheaper space-wise, so they allow us to scale more easily
 to a higher number of OpenStack projects.

 My proposal is the following. Each project team would have a track at
 the Design Summit. Ops feedback is in my opinion part of the design of
 OpenStack, so the Ops Summit would become a track within the
 forward-looking Design Summit. Tracks may use two separate types of
 sessions:

 * Fishbowl sessions
 Those sessions are for open discussions where a lot of participation and
 feedback is desirable. Those would happen in large rooms (100 to 300
 people, organized in fishbowl style with a projector). Those would have
 catchy titles and appear on the general Design Summit schedule. We would
 have space for 6 or 7 of those in parallel during the first 3 days of
 the Design Summit (we would not run them on Friday, to reproduce the
 successful Friday format we had in Paris).

 * Working sessions
 Those sessions are for a smaller group of contributors to get specific
 work done or prioritized. Those would happen in smaller rooms (20 to 40
 people, organized in boardroom style with loads of whiteboards). Those
 would have a blanket title (like infra team working session) and
 redirect to an etherpad for more precise and current content, which
 should limit out-of-team participation. Those would replace project
 pods. We would have space for 10 to 12 of those in parallel for the
 first 3 days, and 18 to 20 of those in parallel on the Friday (by
 reusing fishbowl rooms).

 Each project track would request some mix of sessions (We'd like 4
 fishbowl sessions, 8 working sessions on Tue-Thu + half a day on
 Friday) and the TC would arbitrate how to allocate the limited
 resources. Agenda for the fishbowl sessions would need to be published
 in advance, but agenda for the working sessions could be decided
 dynamically from an etherpad agenda.

 By making larger use of smaller spaces, we expect that setup to let us
 accommodate the needs of more projects. By merging the two separate Ops
 Summit and Design Summit events, it should make the Ops feedback an
 integral part of the Design process rather than a second-class citizen.
 By creating separate working session rooms, we hope to evolve the pod
 concept into something where it's easier for teams to get work done
 (less noise, more whiteboards, clearer agenda).

 What do you think ? Could that work ? If not, do you have alternate
 suggestions ?

 --
 Thierry Carrez (ttx)

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



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

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

[Sean Roberts]

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 link was moved to the infra manual. It is cleaner 
presentation of the information for sure. It also left the google searchable 
wiki links hanging. This is the primary way most newcomers will look for 
information.  It wasn't easy to find the information once it was brought to my 
attention it was missing. I fixed it up pretty easily after that. 

The point being, we need present a certain level of organizational maturity to 
the public. The wiki is important for us to innovate and make changes on the 
fly. Some bits of information are super critical and need to be handled with 
the utmost care. I was able to help the person that was stuck looking for the 
CCLA. Without that direct contact, we would have lost a new contributor for at 
least the short term. 

~sean

 On Jan 8, 2015, at 10:31 AM, Stefano Maffulli stef...@openstack.org wrote:
 
 hello folks,
 
 TL;DR Many wiki pages and categories are maintained elsewhere and to
 avoid confusion to newcomers we need to agree on a new scope for the
 wiki. A suggestion below is to limit its scope to content that doesn't
 need/want peer-review and is not hosted elsewhere (no duplication).
 
 The wiki served for many years the purpose of 'poor man CMS' when we
 didn't have an easy way to collaboratively create content. So the wiki
 ended up hosting pages like 'Getting started with OpenStack', demo
 videos, How to contribute, mission, to document our culture / shared
 understandings (4 opens, release cycle, use of blueprints, stable branch
 policy...), to maintain the list of Programs, meetings/teams, blueprints
 and specs, lots of random documentation and more.
 
 Lots of the content originally placed on the wiki was there because
 there was no better place. Now that we have more mature content and
 processes, these are finding their way out of the wiki like: 
 
  * http://governance.openstack.org
  * http://specs.openstack.org
  * http://docs.openstack.org/infra/manual/
 
 Also, the Introduction to OpenStack is maintained on
 www.openstack.org/software/ together with introductory videos and other
 basic material. A redesign of openstack.org/community and the new portal
 groups.openstack.org are making even more wiki pages obsolete.
 
 This makes the wiki very confusing to newcomers and more likely to host
 conflicting information.
 
 I would propose to restrict the scope of the wiki to things that
 anything that don't need or want to be peer-reviewed. Things like:
 
  * agendas for meetings, sprints, etc
  * list of etherpads for summits
  * quick prototypes of new programs (mentors, upstream training) before
 they find a stable home (which can still be the wiki)
 
 Also, documentation for contributors and users should not be on the
 wiki, but on docs.openstack.org (where it can be found more easily).
 
 If nobody objects, I'll start by proposing a new home page design and
 start tagging content that may be moved elsewhere. 
 
 /stef
 
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

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

[Sean Roberts]

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, at 1:01 PM, Matthew Gilliard matthew.gilli...@gmail.com 
wrote:

 I'll take the
 old content out of https://wiki.openstack.org/wiki/People and leave a
 message directing people where to look.
 Yes, please, let me know if you need help.
 
 Done.
 
 to link
 directly gerrit IDs to openstack.org profile URL
 
 This may be possible with a little javascript hackery in gerrit - I'll
 see what I can do there.
 
 which IRC nick goes to which person. Does anyone know how to do
 that with the Foundation directory?
 I don't think there's a lookup for that (might be worth logging a
 feature request)
 
 Done: https://bugs.launchpad.net/openstack-org/+bug/1401264
 
 Thanks for your time everyone.
 
 
  Matthew
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

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

[Sean Roberts]

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 
https://etherpad.openstack.org/p/par-kilo-congress-design-session

~ sean

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

[openstack-dev] [congress] kilo design session

[Sean Roberts]

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 team has the Tuesday, 04 Nov, 16:40-18:10 slot and wants to switch. 

Does this switch work for everyone?

Maybe we can get some space in one of the pods or cross-project workshops on 
Tuesday between the GBP and the potential Congress session to make it even more 
better.

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

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

[Sean Roberts]

Thx

~sean

 On Oct 21, 2014, at 2:18 AM, Thierry Carrez thie...@openstack.org 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 charge of the larger ecosystem
 sessions), see if you could switch from Monday to Tuesday.
 
 -- 
 Thierry Carrez (ttx)
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

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

[Sean Roberts]

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 thie...@openstack.org wrote:

 Sylvain Bauza wrote:
 I only see 3 slots for discussing about other projects. Do you know if
 it would be possible to get more as there are particular slots around
 14:50, 15:40 and 17:20 which are quite empty ?
 
 There are actually Other projects sessions on those slots (the
 placeholders cover multiple 40-min slots), as can be seen at:
 
 http://kilodesignsummit.sched.org/grid/
 
 So we currently have 6 other projects slots, but I hope we can secure
 a few more.
 
 Regards,
 
 -- 
 Thierry Carrez (ttx)
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


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

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

[Sean Roberts]

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/congress-specs,n,z
 for the specs in review. If a spec is missing from below, you want to get 
involved on any of these specs below, are looking for help on writing your 
first spec, and/or looking for a status update. Respond on this thread. 

Granular/trigger-based datasource driver for ceilometer (Peter, yathi, debo, 
forbes )
Passing hints from congress to nova-scheduler so placement can leverage policy 
(Peter, yathi, debo, forbes)
Workflow description (Tim, Jim jimjunxu,yapengwu, rukhsana.ansari, nils.swart, 
Rukhsana, Nils, Cheng -- we'll split between overview  sources of truth 
workflows)
Architecture Overview
Source of Truth
- Congress (pushes/publishes down)
- GBP (Congress validates/checks what GBP has)
- Hybrid (where group membership comes from GBP and contract comes from 
Congress)
- Both (no single source of truth - possibly a migration scenario)
Translate to GBP -- push to (Alex, Cathy, Louise, Cheng, Helen, Hemanth)
Translate to Neutron Security Groups -- push to” (Alex, Rajdeep)
Runtime support for change to Tier Table -- (pull or trigger fetch) (Tim)
Add trigginer infrastructure to Congress engine (Alex, cathy, louie)
Implement GBP triggering methods (Alex, cathy, louie)
Add GBP translators from reachable table to GBP trigger-tables. (Alex, cathy, 
louie)
Add language semantics to existing catalog (Sean, straz)
Group primitives (Sean, straz)
Temporal const (Sean, straz)

Note that these are not all the specs that we will be reviewing at the Kilo 
summit, rather just the ones from the Policy summit.
Cheers!

~ sean


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

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

[Sean Roberts]

+1

~sean

 On Sep 29, 2014, at 2:20 PM, Peter Balland pball...@vmware.com 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.  
 In my place, I would like to nominate Tim Hinrichs for PTL of Congress.
 
 Tim has been involved in the Congress project since its inception, and has 
 been serving as its chief architect.  He is very active in policy research, 
 code, and community, and has a great strategic vision for the project.
 
 - Peter
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

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

[Sean Roberts]

Congrats Aaron

~sean

 On Sep 22, 2014, at 12:49 PM, Peter Balland pball...@vmware.com wrote:
 
 Aaron has now been added to the congress-core group in gerrit.
 
 Cheers,
 
 Peter
 
 From: Rajdeep Dua rajdeep@gmail.com
 Reply-To: OpenStack Development Mailing List (not for usage questions) 
 openstack-dev@lists.openstack.org
 Date: Thursday, September 18, 2014 at 1:26 AM
 To: OpenStack Development Mailing List (not for usage questions) 
 openstack-dev@lists.openstack.org
 Cc: Aaron Rosen aro...@vmware.com
 Subject: Re: [openstack-dev] [Congress] Nominating Aaron Rosen for 
 congress-core
 
 +1
 
 On Fri, Sep 12, 2014 at 12:14 PM, Tim Hinrichs thinri...@vmware.com wrote:
 +1
 
 Tim
 
 On Sep 12, 2014, at 11:47 AM, Sean Roberts seanrobert...@gmail.com wrote:
 
  +1
 
  ~sean
 
  On Sep 12, 2014, at 11:28 AM, Peter Balland pball...@vmware.com 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
  congressclient work.
 
  References:
 
  https://review.openstack.org/#/q/owner:arosen+project:+stackforge/congress,
  n,z
 
  https://review.openstack.org/#/q/owner:arosen+project:+stackforge/python-co
  ngressclient,n,z
 
  https://review.openstack.org/#/q/reviewer:arosen+project:+stackforge/congre
  ss,n,z
 
  Please respond with +1's or any concerns.
 
  Thanks,
 
  Peter
 
 
  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 
  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Sean Roberts]

+1

~sean

 On Sep 12, 2014, at 11:28 AM, Peter Balland pball...@vmware.com 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
 congressclient work.
 
 References:
 
 https://review.openstack.org/#/q/owner:arosen+project:+stackforge/congress,
 n,z
 
 https://review.openstack.org/#/q/owner:arosen+project:+stackforge/python-co
 ngressclient,n,z
 
 https://review.openstack.org/#/q/reviewer:arosen+project:+stackforge/congre
 ss,n,z
 
 Please respond with +1's or any concerns.
 
 Thanks,
 
 Peter
 
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

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

[Sean Roberts]

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 support for the 
mentoring and training. I think landing this mentoring responsibility into the 
ambassador program makes some sense. 

This doesn't directly solve the subject of this thread. But it does start the 
process of giving help to those that are trying to learn inline while the cores 
are trying to land quality code. 

What do you think?

~sean

 On Sep 8, 2014, at 5:20 PM, Stefano Maffulli stef...@openstack.org wrote:
 
 On 09/05/2014 07:07 PM, James Bottomley wrote:
 Actually, I don't think this analysis is accurate.  Some people are
 simply interested in small aspects of a project.  It's the scratch your
 own itch part of open source.  The thing which makes itch scratchers
 not lone wolfs is the desire to go the extra mile to make what they've
 done useful to the community.  If they never do this, they likely have a
 forked repo with only their changes (and are the epitome of a lone
 wolf).  If you scratch your own itch and make the effort to get it
 upstream, you're assisting the community (even if that's the only piece
 of code you do) and that assistance makes you (at least for a time) part
 of the community.
 
 I'm starting to think that the processes we have implemented are slowing
 down (if not preventing) scratch your own itch contributions. The CLA
 has been identified as the cause for this but after carefully looking at
 our development processes and the documentation, I think that's only one
 part of the problem (and maybe not even as big as initially thought).
 
 The gerrit workflow for example is something that requires quite an
 investment in time and energy and casual developers (think operators
 fixing small bugs in code, or documentation) have little incentive to go
 through the learning curve.
 
 To go back in topic, to the proposal to split drivers out of tree, I
 think we may want to evaluate other, simpler, paths before we embark in
 a huge task which is already quite clear will require more cross-project
 coordination.
 
 From conversations with PTLs and core reviewers I get the impression
 that lots of drivers contributions come with bad code. These require a
 lot of time and reviewers energy to be cleaned up, causing burn out and
 bad feelings on all sides. What if we establish a new 'place' of some
 sort where we can send people to improve their code (or dump it without
 interfering with core?) Somewhere there may be a workflow
 go-improve-over-there where a Community Manager (or mentors or some
 other program we may invent) takes over and does what core reviewers
 have been trying to do 'on the side'? The advantage is that this way we
 don't have to change radically how current teams operate, we may be able
 to start this immediately with Kilo. Thoughts?
 
 /stef
 
 -- 
 Ask and answer questions on https://ask.openstack.org
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

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

[Sean Roberts]

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 following projects.

Nova
Neutron
Congress 

Are there any other projects interested in giving a talk?  It could just be a 
chalk-talk (on the whiteboard), if that makes it easier.

2. We’re planning to use the talks as level-setting for a discussion/workshop 
on how all our policy efforts might interoperate to better serve OpenStack 
users.  We’d like to drive that discussion by working through one or more use 
cases that require us to all think about OpenStack policy from a holistic point 
of view.  

Examples of the kinds of questions we envision trying to answer:

How would the OpenStack users communicate their policies to OpenStack?  
Can OpenStack always enforce policies?  What about monitoring?  Auditing?
What is the workflow for how OpenStack takes the policies and 
implements/renders them?
What happens if there are conflicts between users?  How are those conflicts 
surfaced/resolved?
What gaps are there?  How do we plug them?  What’s the roadmap?
Below is the start of a use case that we think will do the trick.  Let’s work 
together to refine it over email before the summit, so we can hit the ground 
running.  Please reply (to all) with suggestions/alternatives/etc.

a) Application-developer: My 2-tier PCI app (database tier and web tier) can be 
deployed either for production or for development.  

When deployed for production, it needs 

solid-state storage for the DB tier
all ports but 80 closed on the web tier
no network communication to DB tier except from the web tier
no VM in the DB tier can be deployed on the same hypervisor as another VM in 
the DB tier; same for the web tier
b) Cloud operator.  

Applications deployed for production must have access to the internet.
Applications deployed for production must not be deployed in the DMZ cluster.
Applications deployed for production should scale based on load.
Applications deployed for development should have 1 VM instance per tier.
Every application must use VM images signed by an administrator
 c) Compliance officer

No VM from a PCI app may be located on the same hypervisor as a VM from a 
non-PCI app.

~ sean

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

[openstack-dev] [congress] specs update

[Sean Roberts]

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-dev

[openstack-dev] [congress] specs update

[Sean Roberts]

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 
missing specs.
There is a process for holding over non-implemented specs into the next 
release. I will update the wiki.

~ sean

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

[openstack-dev] [congress] policy summit

[Sean Roberts]

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 far here 
https://www.eventbrite.com/e/openstack-policy-summit-tickets-12642081807. It 
will be much better to join us in person, but I will setup a remote, so Kyle 
and others that can join in. Go ahead and add yourself as remote to the event.

Those people that have signed up, update the etherpad 
https://etherpad.openstack.org/p/juno-midcycle-policy-summit. The proposed 
agenda is Thursday covers various project policy overview and/or impacts. 
Friday covers various cross-project policy use cases including security.  More 
information on the etherpad sooner, will allow us to pre-debate content and we 
will get a lot more out of the two days.

~ sean

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

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

[Sean Roberts]

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 seanrobert...@gmail.com wrote:
 
 I'm thinking location as yahoo Sunnyvale or VMware Palo Alto. 
 
 ~sean
 
 On Jul 10, 2014, at 5:12 PM, sean roberts seanrobert...@gmail.com 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 the Paris 
 summit. More details about the Congress can be found here 
 https://wiki.openstack.org/wiki/Congress.
 
 I have discussed the idea with mestery and mikal, but I wanted to include as 
 many other projects as possible.
 
 I propose this agenda
 first day each project talks about their policy approach
 second day whiteboarding and discussion about integrating our policy 
 approaches
 I propose a few dates
 11-12 September
 18-19 September
 ~Sean Roberts
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Sean Roberts]

I've reposted your query below to openstack-dev for a greater pool of eyeballs.

~sean

Begin forwarded message:

From: 武田 剛征 
hisayuki.tak...@oceanearth-corp.commailto:hisayuki.tak...@oceanearth-corp.com
Date: December 22, 2013 at 6:17:28 PST
To: commun...@lists.openstack.orgmailto:commun...@lists.openstack.org
Subject: [openstack-community] A bug on OpenStack

Hi OpenStack experts,

Could you please, help me out on this? I need your experts advice.
I am trying to build VlanManager environment with OpenStack grizzly on Cent OS 
6.4, but it doesn't work.
I am using all-in-one architecture (single-host). FlatDHCPManager successfully 
worked.

So, I am assuming that there is any bug/defect that VlanManager can't work with 
single-host architecture.
Does anyone know if there is such a bug related to VlanManager on single-host 
architecture?

Any pointer or letting me know anyone who is familiar with this would be highly 
appreciated.
Thank you so much in advance,


Bird Kafka

___
Community mailing list
commun...@lists.openstack.orgmailto:commun...@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/community
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] OpenStack Community Training project needs you

[Sean Roberts]

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.openstack.org/trunk/openstack-training/
Contact me at @sarob or email for any additional information.

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

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

[Sean Roberts]

Ah hah, the element syntax was missing. Thanks, I owe you a beer!

~sean

On Jul 29, 2013, at 9:34, Diane Fleming diane.flem...@rackspace.com wrote:

 I don't know if this will work, but this is how I used xpointer to pull in
 content from one file to another:
 
 
 Target file (pulls in content)
 
 titleOverview/title
 xi:include href=ch_gs_overview.xml
xpointer=element(over1)/
 xi:include href=ch_gs_overview.xml
xpointer=element(over2)/
 xi:include href=ch_gs_overview.xml
xpointer=element(over3)/
 xi:include href=ch_gs_overview.xml
xpointer=element(over4)/
 xi:include href=ch_gs_overview.xml
xpointer=element(over5)/
 xi:include href=ch_gs_overview.xml
xpointer=element(over6)/
 xi:include href=ch_gs_overview.xml
xpointer=element(over7)/
 xi:include href=ch_gs_overview.xml
xpointer=element(over8)/
 xi:include href=ch_gs_overview.xml
xpointer=element(over9)/
 xi:include href=ch_gs_overview.xml
xpointer=element(over10)/
 xi:include href=section_virt_ext.xml/
 
 
 
 Source file
 
 
titleOverview/title
section xml:id=cn_overviewtitleCloud Networks/title
para xml:id=over1Cloud Networks lets you create a virtual
Layer 2 network, known as an isolated network, which gives you
greater control and security when you deploy web applications.
 /para
para xml:id=over2When you create a next generation Cloud
Server, Cloud Networks enables you to attach one or more
networks to your server. You can attach an isolated network
that you have created or a Rackspace network. /para
para xml:id=over3If you install the virt_ext;, you can create
a virtual interface to a specified Rackspace or isolated
network and attach that network to an existing server
instance. You can also list virtual interfaces for and delete
virtual interfaces from a server instance. For information
about the virt_ext;, see xref linkend=section_virt_ext
/./para
 
 
 etc.
 
 
 Diane
 
 --
 Diane Fleming
 Software Developer II - US
 
 diane.flem...@rackspace.com
 Cell  512.323.6799
 Office 512.874.1260
 Skype drfleming0227
 Google-plus diane.flem...@gmail.com
 
 
 
 
 
 
 On 7/29/13 9:27 AM, Sean Roberts sean...@yahoo-inc.com wrote:
 
 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 bad pointer.
 
 The remote content isn't using DTD or XMLschema. I'm hoping I can figure
 out how to walk the structure without having to.
 Any XML peoples that can help?
 
 ~sean
 ___
 Openstack-docs mailing list
 openstack-d...@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
 
 

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