Excerpts from Zane Bitter's message of 2018-06-05 15:55:49 -0400:
> We've talked a bit about migrating to Python 3, but (unless I missed it)
> not a lot about which version of Python 3. Currently all projects that
> support Python 3 are gating against 3.5. However, Ubuntu Artful and
> Fedora 26
Then we can get a sense of which teams
feel this sort of pressure, overall, instead of individuals.
>
> Thanks,
> Kevin
> ____
> From: Doug Hellmann [d...@doughellmann.com]
> Sent: Tuesday, June 05, 2018 7:39 AM
> To: openstack-dev
> Subject:
The review team [1] for the project-team-guide repository (managed
by the TC) hasn't been updated for a while. I would like to propose
removing a few reviewers who are no longer active, and adding one
new reviewer.
My understanding is that Kyle Mestery and Nikhil Komawar have both
moved on from
Excerpts from Graham Hayes's message of 2018-06-05 16:42:45 +0100:
>
> On 30/05/18 21:23, Mohammed Naser wrote:
> > Hi everyone:
> >
> > Over the past week in the summit, there was a lot of discussion
> > regarding StarlingX
> > and members of the technical commitee had a few productive
Excerpts from Matt Riedemann's message of 2018-06-04 18:46:15 -0500:
> On 6/4/2018 4:20 PM, Doug Hellmann wrote:
> > See my comments on the other part of the thread, but I think this is too
> > optimistic until we add a couple of people to the review team on OSC.
> >
> &g
Excerpts from Ken Giusti's message of 2018-06-05 10:47:17 -0400:
> Hi,
>
> The telemetry integration test for oslo.messaging has started failing
> on the stable/queens branch [0].
>
> A quick review of the logs points to a change in heat-tempest-plugin
> that is incompatible with the version of
Excerpts from Doug Hellmann's message of 2018-06-02 15:08:28 -0400:
> Excerpts from Jeremy Stanley's message of 2018-06-02 18:51:47 +:
> > On 2018-06-02 13:23:24 -0400 (-0400), Doug Hellmann wrote:
> > [...]
> > > It feels like we would be saying that we don't trust 2 c
Excerpts from Jean-Philippe Evrard's message of 2018-06-05 10:14:12 +0200:
> Hello,
>
> *TL:DR;* If you are an openstack-ansible user, consuming our roles directly,
> with tags, without using openstack-ansible plays or integrated repo,
> then things will change for you. Start using git shas
Excerpts from Sean McGinnis's message of 2018-06-05 07:26:27 -0500:
> On Mon, Jun 04, 2018 at 06:44:15PM -0500, Matt Riedemann wrote:
> > On 6/4/2018 5:13 PM, Sean McGinnis wrote:
> > > Yes, exactly what I meant by the NOOP. I'm not sure what Cinder would
> > > check here. We don't have to see if
Excerpts from Jay Pipes's message of 2018-06-04 18:47:22 -0400:
> On 06/04/2018 05:02 PM, Doug Hellmann wrote:
> > The most significant point of interest to the contributor
> > community from this section of the meeting was the apparently
> > overwhelming interest fro
Excerpts from Ivan Kolodyazhny's message of 2018-06-05 16:32:22 +0300:
> Hi team,
>
> In Horizon, we're going to get rid of unsupported Nose and use Django Test
> Runner instead of it [1]. Nose has some issues and limitations which blocks
> us in our testing improvement efforts.
>
> Nose has
Excerpts from Zane Bitter's message of 2018-06-04 17:41:10 -0400:
> On 02/06/18 13:23, Doug Hellmann wrote:
> > Excerpts from Zane Bitter's message of 2018-06-01 15:19:46 -0400:
> >> On 01/06/18 12:18, Doug Hellmann wrote:
> >
> > [snip]
> >
> >>&g
Excerpts from Matt Riedemann's message of 2018-06-04 15:26:28 -0500:
> On 5/31/2018 3:59 PM, Sean McGinnis wrote:
> > We were also able to already identify some possible goals for the T cycle:
> >
> > - Move all CLIs to python-openstackclient
>
> My understanding was this is something we could
Excerpts from Matt Riedemann's message of 2018-06-04 15:38:48 -0500:
> On 6/4/2018 1:07 PM, Sean McGinnis wrote:
> > Python 3 First
> > ==
> >
> > One of the things brought up in the session was picking things that bring
> > excitement and are obvious benefits to deployers and users
On 20 May, 2018 the OpenStack foundation staff, board, technical
committee, and user committee held a joint leadership meeting at
the summit venue in Vancouver to discuss current events and issues
related to the OpenStack community. Alan Clark, Melvin Hillsman,
and I chaired the meeting together,
Excerpts from Ed Leafe's message of 2018-06-04 13:41:36 -0500:
> On Jun 4, 2018, at 7:05 AM, Jay S Bryant wrote:
>
> >> Do we have that problem? I honestly don't know how much pressure other
> >> folks are feeling. My impression is that we've mostly become good at
> >> finding the necessary
During the retrospective at the forum we talked about having each group
working on an initiative send regular status updates. I would like to
start doing that this week, and would like to talk about logistics
Should we send emails directly to this list, or the TC list?
How often should we post
This is the weekly summary of work being done by the Technical
Committee members. The full list of active items is managed in the
wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker
We also track TC objectives for the cycle using StoryBoard
Excerpts from Omer Anson's message of 2018-06-04 16:53:54 +0300:
> Sure. No worries. The project is still active :)
>
> I tagged and branched out Queens.
The build failed, see the other email thread for details.
Doug
>
> Thanks,
> Omer.
>
> On Mon, 4 Jun 2018 at 15:25, Sean McGinnis wrote:
Excerpts from zuul's message of 2018-06-04 14:01:19 +:
> Build failed.
>
> - release-openstack-python
> http://logs.openstack.org/3b/3b7ca98ce56d1e71efe95eaa10d0884487411307/release/release-openstack-python/c381399/
> : FAILURE in 3m 46s
> - announce-release announce-release : SKIPPED
> -
> On Jun 4, 2018, at 7:57 AM, Gilles Dubreuil wrote:
>
> Hi,
>
> Can someone from the core team request infra to create a feature branch for
> the Proof of Concept we agreed to do during API SIG forum session [1] a
> Vancouver?
>
> Thanks,
> Gilles
>
> [1]
Excerpts from amrith.kumar's message of 2018-06-02 15:06:27 -0400:
> Every project on the one-way-trip to inactivity starts with what some people
> will wishfully call a 'transient period' of reduced activity. Once the
> transient nature is no longer the case (either it becomes active or the
>
Excerpts from Jeremy Stanley's message of 2018-06-02 18:51:47 +:
> On 2018-06-02 13:23:24 -0400 (-0400), Doug Hellmann wrote:
> [...]
> > It feels like we would be saying that we don't trust 2 core reviewers
> > from the same company to put the project's goals
Excerpts from Zane Bitter's message of 2018-06-01 15:19:46 -0400:
> On 01/06/18 12:18, Doug Hellmann wrote:
[snip]
> > Is that rule a sign of a healthy team dynamic, that we would want
> > to spread to the whole community?
>
> Yeah, this part I am pretty unsure about t
That presentation says "Users should do their own tagging/release
management" (6:31). I don't think that's really an approach we want
to be encouraging project teams to take.
I would suggest placing Dragonflow in maintenance mode, but if the
team doesn't have the resources to participate in the
Excerpts from Sean McGinnis's message of 2018-06-01 11:45:04 -0500:
> Hi Andrey,
>
> Sorry for the delay getting back to this. I had meant to wait for the
> responses
> from the other projects included in the original thread, but never made it
> back
> to follow up.
>
> Officially governed
Excerpts from Zane Bitter's message of 2018-06-01 10:10:31 -0400:
> On 26/05/18 17:46, Mohammed Naser wrote:
> > Hi everyone!
> >
> > During the TC retrospective at the OpenStack summit last week, the
> > topic of the organizational diversity tag is becoming irrelevant was
> > brought up by
Excerpts from Thierry Carrez's message of 2018-05-31 10:31:12 +0200:
> Doug Hellmann wrote:
> > [...]
> > I'm missing details and/or whole topics. Please review the list and
> > make any updates you think are necessary.
>
> One thing that was raised at the Boar
Excerpts from corvus's message of 2018-05-30 10:09:23 -0700:
> Doug Hellmann writes:
>
> >> * Move many of the git repos currently under the OpenStack project
> >> infrastructure team's governance to this new team.
> >
> > I'm curious about the "many&q
Excerpts from Jeremy Stanley's message of 2018-05-30 17:30:23 +:
> On 2018-05-30 10:09:23 -0700 (-0700), James E. Blair wrote:
> [...]
> > An example of something that probably shouldn't move is
> > "openstack-zuul-jobs". We still need people that are concerned with how
> > OpenStack uses the
Excerpts from Doug Hellmann's message of 2018-05-29 17:26:16 -0400:
[snip]
> Chris brought up a concern about whether we have much traction on
> "doing stuff" and especially "getting things done that not everyone
> wants," Graham noted a lack of "visible impact," and Zane mentioned
> the TC
Excerpts from corvus's message of 2018-05-30 09:25:14 -0700:
> Hi,
>
> With recent changes implemented by the OpenStack Foundation to include
> projects other than "OpenStack" under its umbrella, it has become clear
> that the "Project Infrastructure Team" needs to change.
>
> The infrastructure
Excerpts from Jeremy Stanley's message of 2018-05-29 22:57:45 +:
> On 2018-05-29 17:26:16 -0400 (-0400), Doug Hellmann wrote:
> [...]
> > There was some discussion of whether the office hours themselves
> > are useful, based on the apparent lack of participation. W
Excerpts from corvus's message of 2018-05-30 09:25:14 -0700:
> Hi,
>
> With recent changes implemented by the OpenStack Foundation to include
> projects other than "OpenStack" under its umbrella, it has become clear
> that the "Project Infrastructure Team" needs to change.
>
> The infrastructure
Excerpts from Jeremy Stanley's message of 2018-05-30 13:00:31 +:
> On 2018-05-30 14:42:58 +0200 (+0200), Julien Danjou wrote:
> [...]
> > The question is: why cmd2 0.9.0 does not work and how do we fix that?
>
> The cmd2 maintainers decided that they no longer want to carry
> support for old
Excerpts from Slawomir Kaplonski's message of 2018-05-29 22:49:07 +0200:
> Hi,
>
> > Wiadomość napisana przez Jay S Bryant w dniu
> > 29.05.2018, o godz. 22:25:
> >
> >
> > On 5/29/2018 3:19 PM, Doug Hellmann wrote:
> >> Excerpts from Jonathan
At the forum last week the TC held a retrospective to discuss how
we felt things have gone for the TC over the last 6-ish months,
since the previous election. I will try to summarize the feedback
here based on the notes in the etherpad [1], but please reply if I
misremember something, leave out
Excerpts from Matthew Treinish's message of 2018-05-29 16:16:50 -0400:
> On Tue, May 29, 2018 at 03:51:31PM -0400, Doug Hellmann wrote:
> > Following up on this topic, at the Forum discussion last week (see
> > https://etherpad.openstack.org/p/YVR-python-2-deprecation-timeline)
Excerpts from Jonathan Proulx's message of 2018-05-29 16:05:06 -0400:
> On Tue, May 29, 2018 at 03:53:41PM -0400, Doug Hellmann wrote:
> :> >> maybe we're all saying the same thing here?
> :> > Yeah, I feel like we're all essentially in agreement that nits (of the
> :
Excerpts from Julia Kreger's message of 2018-05-29 15:41:55 -0400:
> On Tue, May 29, 2018 at 3:16 PM, Jay S Bryant wrote:
> >
> >
> > On 5/29/2018 2:06 PM, Artom Lifshitz wrote:
> >> Yeah, I feel like we're all essentially in agreement that nits (of the
> >> English mistake of typo type) do need
Excerpts from Jay S Bryant's message of 2018-05-29 14:16:33 -0500:
>
> On 5/29/2018 2:06 PM, Artom Lifshitz wrote:
> >> On Tue, May 29, 2018 at 10:52:04AM -0400, Mohammed Naser wrote:
> >>
> >> :On Tue, May 29, 2018 at 10:43 AM, Artom Lifshitz
> >> wrote:
> >> :> One idea would be that, once
Following up on this topic, at the Forum discussion last week (see
https://etherpad.openstack.org/p/YVR-python-2-deprecation-timeline) the
general plan outlined below was acceptable to most of the folks in the
room with a few small changes (included below).
Excerpts from Doug Hellmann's message
Excerpts from Petr Kovar's message of 2018-05-28 16:03:41 +0200:
> On Thu, 24 May 2018 07:19:29 -0700
> "Jonathan D. Proulx" wrote:
>
> > My intention based on current understandign would be to create a git
> > repo called "osops-docs" as this fits current naming an thin initial
> > document we
Excerpts from Mohammed Naser's message of 2018-05-29 08:51:16 -0400:
> On Tue, May 29, 2018 at 7:59 AM, Thierry Carrez wrote:
> > Mohammed Naser wrote:
> >>
> >> During the TC retrospective at the OpenStack summit last week, the
> >> topic of the organizational diversity tag is becoming
Excerpts from zuul's message of 2018-05-29 14:28:57 +:
> Build failed.
>
> - release-openstack-python
> http://logs.openstack.org/26/26956a27b95550e2162243da79d62bb1b19d50d7/release/release-openstack-python/2bd7f7d/
> : POST_FAILURE in 6m 34s
> - announce-release announce-release : SKIPPED
Excerpts from Jonathan D. Proulx's message of 2018-05-24 07:19:29 -0700:
>
> My intention based on current understandign would be to create a git
> repo called "osops-docs" as this fits current naming an thin initial
> document we intend to put there and the others we may adopt from
> docs-team.
Excerpts from Doug Hellmann's message of 2018-05-23 22:58:40 -0700:
> Excerpts from Melvin Hillsman's message of 2018-05-23 22:26:02 -0700:
> > Great to see this moving. I have some questions/concerns based on your
> > statement Doug about docs.openstack.org publishing and do not want to
> >
Excerpts from Melvin Hillsman's message of 2018-05-23 22:26:02 -0700:
> Great to see this moving. I have some questions/concerns based on your
> statement Doug about docs.openstack.org publishing and do not want to
> detour the conversation but ask for feedback. Currently there are a number
I'm
You will want to follow the steps of the "project creators' guide"
[1]. Not all of them apply, because this is a docs repo and not a
code project repo. Let me know if you have questions about which
pieces do or do not apply as you go along, and we can work on
improving that document as well.
The
Excerpts from Matt Riedemann's message of 2018-05-17 17:23:09 -0500:
> On 5/17/2018 11:02 AM, Doug Hellmann wrote:
> > After some discussion on twitter and IRC, we've added a new session to
> > the Forum schedule for next week to discuss our options for cleaning up
> > some of
Excerpts from Jeremy Stanley's message of 2018-05-18 00:03:35 +:
> On 2018-05-17 18:47:06 -0500 (-0500), Matt Riedemann wrote:
> > On 5/17/2018 5:23 PM, Matt Riedemann wrote:
> > > Not to troll too hard here, but it's kind of frustrating to see that
> > > twitter trumps people actually
After some discussion on twitter and IRC, we've added a new session to
the Forum schedule for next week to discuss our options for cleaning up
some of the design/technical debt in our REST APIs. It's early days in
the conversation, but we wanted to take advantage of our time together
in person to
Excerpts from Matthew Thode's message of 2018-05-16 15:59:47 -0500:
> Sphinx has breaking changes (yet again) and we need to figure out how to
> deal with it. I think the fix will be simple for affected projects, but
> we should probably move forward on this. The error people are getting
> seems
Excerpts from Wesley Hayutin's message of 2018-05-16 12:51:25 -0600:
> On Wed, May 16, 2018 at 2:41 PM Doug Hellmann <d...@doughellmann.com> wrote:
>
> > Excerpts from Petr Kovar's message of 2018-05-16 17:39:14 +0200:
> > > Hi all,
> > >
> > > In t
Excerpts from Jeremy Stanley's message of 2018-05-16 17:42:09 +:
> On 2018-05-16 13:16:09 +0200 (+0200), Dmitry Tantsur wrote:
> > On 05/15/2018 09:19 PM, Juan Antonio Osorio wrote:
> > > As part of the work from the Security Squad, we added the
> > > ability for the containerized undercloud
Excerpts from Petr Kovar's message of 2018-05-16 17:39:14 +0200:
> Hi all,
>
> In the past few years, we've seen several efforts aimed at automating
> procedural documentation, mostly centered around the OpenStack
> installation guide. This idea to automatically produce and verify
> installation
do it, but you
need to set up a signal handler so that SIGHUP invokes the
mutate_config_files() method of the ConfigOpts instance being used by
the application.
Doug
>
> Cheers,
> Lingxian Kong
>
> On Wed, May 16, 2018 at 2:46 AM Doug Hellmann <d...@doughellmann.com&g
Excerpts from Lance Bragstad's message of 2018-05-14 18:45:49 -0500:
>
> On 05/14/2018 05:46 PM, Doug Hellmann wrote:
> > Excerpts from Lance Bragstad's message of 2018-05-14 15:20:42 -0500:
> >> On 05/14/2018 02:24 PM, Doug Hellmann wrote:
> >>> Excerpts from La
Excerpts from Thierry Carrez's message of 2018-05-15 10:38:36 +0200:
> Doug Hellmann wrote:
> > We will also hold a retrospective for the TC as a team on Monday
> > at the Forum. Please be prepared to discuss things you think are
> > going well, things you think we need to c
Excerpts from Stephen Finucane's message of 2018-05-15 11:44:11 +0100:
> I imagine most people have been seeing warnings like the one below
> raised by various openstack packages recently:
>
> .tox/py27/lib/python2.7/site-packages/psycopg2/__init__.py:144:
> UserWarning: The psycopg2
> wheel
hny,
> http://blog.e0ne.info/
>
> On Mon, May 14, 2018 at 4:30 PM, Akihiro Motoki <amot...@gmail.com> wrote:
>
> >
> >
> > 2018年5月14日(月) 21:42 Doug Hellmann <d...@doughellmann.com>:
> >
> >> Excerpts from Akihiro Motoki's message of 2018-0
Excerpts from Lance Bragstad's message of 2018-05-14 15:20:42 -0500:
>
> On 05/14/2018 02:24 PM, Doug Hellmann wrote:
> > Excerpts from Lance Bragstad's message of 2018-05-14 13:13:51 -0500:
> >> On 03/19/2018 09:22 AM, Jim Rollenhagen wrote:
> >>> On Sat, Mar 1
Excerpts from Lance Bragstad's message of 2018-05-14 13:13:51 -0500:
>
> On 03/19/2018 09:22 AM, Jim Rollenhagen wrote:
> >
> > On Sat, Mar 17, 2018 at 9:49 PM, Doug Hellmann <d...@doughellmann.com
> > <mailto:d...@doughellmann.com>> wrote:
>
This is the weekly summary of work being done by the Technical
Committee members. The full list of active items is managed in the
wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker
We also track TC objectives for the cycle using StoryBoard
Excerpts from Doug Hellmann's message of 2018-03-25 16:04:11 -0400:
> Excerpts from Doug Hellmann's message of 2018-03-22 16:16:06 -0400:
> > Excerpts from Doug Hellmann's message of 2018-03-21 16:02:06 -0400:
> > > Excerpts from Doug Hellmann's message of 2018-03-15 07:03:11 -0400:
> > > >
> > >
Excerpts from Akihiro Motoki's message of 2018-05-14 18:52:55 +0900:
> 2018年5月12日(土) 3:04 Doug Hellmann <d...@doughellmann.com>:
>
> > Excerpts from Akihiro Motoki's message of 2018-05-12 00:14:33 +0900:
> > > Hi zigo and horizon plugin maintainers,
> > >
&
Excerpts from Akihiro Motoki's message of 2018-05-12 00:14:33 +0900:
> Hi zigo and horizon plugin maintainers,
>
> Horizon itself already supports Django 2.0 and horizon unit test covers
> Django 2.0 with Python 3.5.
>
> A question to all is whether we change the upper bound of Django from <2.0
Excerpts from Zane Bitter's message of 2018-05-10 16:38:37 -0400:
> On 17/04/18 05:24, Thierry Carrez wrote:
> > Hi everyone,
> >
> > As you know the Technical Committee (the governance body representing
> > contributors producing OpenStack software) meets with other OpenStack
> > governance
Excerpts from Ilya Etingof's message of 2018-05-10 15:48:34 +0200:
> On 05/10/2018 03:01 PM, Julia Kreger wrote:
> > On Mon, May 7, 2018 at 4:34 PM, Doug Hellmann <d...@doughellmann.com> wrote:
> >
> >> As a consumer of team updates from outside of the team
Excerpts from Julia Kreger's message of 2018-05-10 09:01:42 -0400:
> On Mon, May 7, 2018 at 4:34 PM, Doug Hellmann <d...@doughellmann.com> wrote:
>
> > As a consumer of team updates from outside of the team, I do find
> > them valuable.
>
> Ditto, if I have tim
Excerpts from Doug Hellmann's message of 2018-05-09 16:06:01 -0400:
>
> The last time we had a joint leadership meeting, several TC members
> expressed the desire to have more information about what was going
> to be covered before the meeting. The agenda for the next meeting
> (to be held in
The last time we had a joint leadership meeting, several TC members
expressed the desire to have more information about what was going
to be covered before the meeting. The agenda for the next meeting
(to be held in Vancouver), is in the wiki at
I have created the etherpad for the TC Retrospective session planned for
Thursday at the Forum. I set up the document structure, but have not
added any substantive content. Please consider the questions in the
etherpad before the session and either add content or be prepared to add
it in the room
I have created the etherpad for the forum session to discuss
deprecating python 2.
https://etherpad.openstack.org/p/YVR-python-2-deprecation-timeline
I pre-populated it with some of the details from the earlier mailing
list thread, but please add any additional notes you have that will
help
Excerpts from Alexandra Settle's message of 2018-05-09 13:13:44 +:
> Hi all,
>
> It is with a super heavy heart I have to say that I need to step down as core
> from the OpenStack-Ansible and Documentation teams – and take a step back
> from the community.
>
> The last year has taken me in
Excerpts from Lance Bragstad's message of 2018-05-04 15:16:09 -0500:
>
> On 05/04/2018 02:55 PM, Harry Rybacki wrote:
> > Greetings All,
> >
> > After a discussion in #openstack-tc[1] earlier today, the Keystone
> > team is adjusting its approach in proposing default roles[2].
> > Subsequently, I
Excerpts from Matthew Treinish's message of 2018-05-08 13:55:43 -0400:
> On Tue, May 08, 2018 at 01:34:11PM -0400, Doug Hellmann wrote:
> >
> > (added [glance] subject tag)
> >
> > Excerpts from Matthew Treinish's message of 2018-05-08 12:22:56 -0400:
> > >
(added [glance] subject tag)
Excerpts from Matthew Treinish's message of 2018-05-08 12:22:56 -0400:
> On Tue, May 08, 2018 at 05:01:36PM +0100, Graham Hayes wrote:
> > On 08/05/18 16:53, Doug Hellmann wrote:
> > > Excerpts from Graham Hayes's message of 2018-05-08 16:28:46 +010
(I added the [qa] topic tag for the QA team, since they own hacking, and
[requirements] for that team since I have a question about capping.)
Excerpts from Julia Kreger's message of 2018-05-08 12:43:07 -0400:
> About two hours ago, we started seeing Ironic CI jobs failing pep8
> with new
Excerpts from Graham Hayes's message of 2018-05-08 17:01:36 +0100:
> On 08/05/18 16:53, Doug Hellmann wrote:
> > Excerpts from Graham Hayes's message of 2018-05-08 16:28:46 +0100:
> >> On 08/05/18 16:09, Zane Bitter wrote:
> >>> On 30/04/18 17:16, Ben Nemec wro
Excerpts from Doug Hellmann's message of 2018-05-07 10:53:04 -0400:
[snip]
> The Adjutant project application [10] is still under review, and
> the only votes registered are opposed. I anticipate having the topic
> of how we review project applications as one of several items we
> discuss during
Excerpts from Graham Hayes's message of 2018-05-08 16:28:46 +0100:
> On 08/05/18 16:09, Zane Bitter wrote:
> > On 30/04/18 17:16, Ben Nemec wrote:
> >>> Excerpts from Doug Hellmann's message of 2018-04-25 16:54:46 -0400:
> 1. Fix oslo.service functional tests -- the Oslo team needs help
>
Excerpts from Michel Peterson's message of 2018-05-07 17:54:02 +0300:
> On Fri, Apr 20, 2018 at 11:06 PM, Doug Hellmann <d...@doughellmann.com>
> wrote:
>
> >
> > We have made great progress on this but we do still have quite a
> > few of these patches t
Excerpts from Julia Kreger's message of 2018-05-07 13:53:13 -0400:
> Greetings everyone,
>
> For some time, Rama Yeleswarapu (rama_y) has been graciously sending
> out a weekly update for Ironic to the mailing list. We found out late
> last week that this contributor would be unable to continue
Excerpts from Jeremy Stanley's message of 2018-05-07 14:06:35 +:
> On 2018-05-07 09:52:16 -0400 (-0400), Doug Hellmann wrote:
> [...]
> > 3. We could do nothing to record the work related to the goal.
> [...]
>
> For situations like 557863 I think I'd prefer either the st
This is the weekly summary of work being done by the Technical
Committee members. The full list of active items is managed in the
wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker
We also track TC objectives for the cycle using StoryBoard at:
There is a patch to update the Python 3.5 goal for Kolla [1]. While
I'm glad to see the work happening, the change adds a new deliverable
to an old goal, and it isn’t clear whether we want to use that
approach for tracking goal work indefinitely. I see a few options.
1. We could update the
Excerpts from Jean-Philippe Evrard's message of 2018-05-07 13:36:34 +0200:
> We've been juggling with python3, ansible and multiple distros for a while
> now.
> That dance hasn't been fruitful: many hidden issues, either due to
> ansible modules, or our own modules, or upgrade issues.
>
> I've
Excerpts from Graham Hayes's message of 2018-05-02 20:15:14 +0100:
> On 02/05/18 20:11, Doug Hellmann wrote:
> > Excerpts from Zane Bitter's message of 2018-05-02 11:38:55 -0400:
> >> On 01/05/18 16:21, Doug Hellmann wrote:
> >>> Excerpts from Andreas Jaeger's messag
Excerpts from Petr Kovar's message of 2018-05-02 15:56:36 +0200:
> On Tue, 01 May 2018 10:08:23 -0400
> Doug Hellmann <d...@doughellmann.com> wrote:
>
> > The TC has had an item on our backlog for a while (a year?) to
> > document "constellations" of O
Excerpts from Zane Bitter's message of 2018-05-02 11:38:55 -0400:
> On 01/05/18 16:21, Doug Hellmann wrote:
> > Excerpts from Andreas Jaeger's message of 2018-05-01 21:51:19 +0200:
> >> On 05/01/2018 04:08 PM, Doug Hellmann wrote:
> >>> The TC has had an item on o
Excerpts from Jean-Philippe Evrard's message of 2018-05-02 17:14:07 +0200:
> Hello everyone,
>
> Now that we are all part-time, I'd like to toy with a new idea,
> proposed in the past by Jesse, to rotate the duties with people who
> are involved in OSA, or want to get involved more (it's not
Excerpts from Andreas Jaeger's message of 2018-05-01 21:51:19 +0200:
> On 05/01/2018 04:08 PM, Doug Hellmann wrote:
> > The TC has had an item on our backlog for a while (a year?) to
> > document "constellations" of OpenStack components to make it easier
> > for de
The TC has had an item on our backlog for a while (a year?) to
document "constellations" of OpenStack components to make it easier
for deployers and users to understand which parts they need to have
the features they want [1].
John Garbutt has started writing the first such document [2], but
as
Excerpts from Kendall Nelson's message of 2018-05-01 00:02:36 +:
> Hello Everyone :)
>
> Please join me in congratulating the 7 newly elected members of the
> Technical Committee (TC)!
>
>
>- Thierry Carrez (ttx)]
>- Chris Dent (cdent)
>- Sean McGinnis (smcginnis)
>- Davanum
Excerpts from Alex Schultz's message of 2018-04-30 15:43:16 -0600:
> On Mon, Apr 30, 2018 at 3:16 PM, Ben Nemec <openst...@nemebean.com> wrote:
> > Resending from an address that is subscribed to the list. Apologies to
> > those of you who get this twice.
> >
>
Excerpts from Ben Nemec's message of 2018-04-30 16:16:35 -0500:
> Resending from an address that is subscribed to the list. Apologies to
> those of you who get this twice.
>
> On 04/30/2018 10:06 AM, Doug Hellmann wrote:
> > It would be useful to have more input from PTLs on
Excerpts from Clark Boylan's message of 2018-04-26 11:22:15 -0700:
> On Thu, Apr 26, 2018, at 7:27 AM, Sean McGinnis wrote:
> > On Wed, Apr 25, 2018 at 04:54:46PM -0400, Doug Hellmann wrote:
> > > It's time to talk about the next steps in our migration from python
&
Excerpts from Doug Hellmann's message of 2018-04-27 10:02:08 -0400:
> The latest release of reno tries to add anchors to the page in a way
> that ensures they are named consistently across builds. For projects
> with the same version number in multiple series (which can happen for
> non-milestone
The latest release of reno tries to add anchors to the page in a way
that ensures they are named consistently across builds. For projects
with the same version number in multiple series (which can happen for
non-milestone projects that haven't tagged for rocky yet), this causes
duplicate anchors
401 - 500 of 3451 matches
Mail list logo
