I want to thank Nguyễn Trí Hải, Ma Lei, and Huang Zhiping for
agreeing to be a part of the goal champion team for the python3
goal for Stein.
The next step for us is to build some tools to make the process a
little easier.
One of the aspects of this goal that makes it difficult is that we
need
Excerpts from Chris Dent's message of 2018-06-19 20:06:15 +0100:
>
> Every now and again I keep working on my experiments to containerize
> placement in a useful way [1]. At the moment I have it down to using
> a very small oslo_config-style conf file. I'd like to take it the
> rest of the way
Excerpts from Zane Bitter's message of 2018-06-18 12:58:07 -0400:
> Replying to myself one more time...
>
> On 12/06/18 17:35, Zane Bitter wrote:
> > On 11/06/18 18:49, Zane Bitter wrote:
> >> It's had a week to percolate (and I've seen quite a few people viewing
> >> the etherpad), so here is
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:
Excerpts from Ghanshyam Mann's message of 2018-06-18 20:38:00 +0900:
> On Sat, 16 Jun 2018 04:01:45 +0900 Doug Hellmann
> wrote
> > Excerpts from corvus's message of 2018-06-15 08:46:40 -0700:
> > > Doug Hellmann writes:
> > >
> > > >
Excerpts from Eric Fried's message of 2018-06-15 18:09:49 -0500:
> Doug-
>
> > The lower constraints tests only look at files in the same repo.
> > The minimum versions of dependencies set in requirements.txt,
> > test-requirements.txt, etc. need to match the values in
> > lower-constraints.txt.
Excerpts from Jean-Philippe Evrard's message of 2018-06-15 17:37:02 +0200:
> > Not sure it'd help but one option we do is to create aliases based on
> > the title. Though since the PTLs don't have addresses on the openstack
> > domain an alias may not make as much sense, it'd have to be a full
>
Excerpts from corvus's message of 2018-06-15 08:46:40 -0700:
> Doug Hellmann writes:
>
> > Excerpts from Ghanshyam's message of 2018-06-15 09:04:35 +0900:
>
> >> Yes, It will not be set on LIBS_FROM_GIT as we did not set it
> >> explicitly. But gate running on
Excerpts from Ghanshyam's message of 2018-06-15 09:04:35 +0900:
>
>
>
> On Fri, 15 Jun 2018 06:17:34 +0900 Doug Hellmann
> wrote
> > Excerpts from Doug Hellmann's message of 2018-06-14 13:02:31 -0400:
> > > Excerpts from Ghanshyam's messag
Excerpts from Balázs Gibizer's message of 2018-06-15 13:34:09 +0200:
>
> On Fri, Jun 15, 2018 at 11:36 AM, Chen CH Ji
> wrote:
> > on patch [1] , PS 50 and PS51 just a minor rebase but PS51 start to
> > fail on requirements-check with following error in [2]
> >
> > Validating lower
Excerpts from Sean McGinnis's message of 2018-06-14 16:28:14 -0500:
> >
> > After giving everyone a week to volunteer as liaisons for project teams,
> > I have filled out the roster so that every team has 2 TC members
> > assigned. I used random.shuffle() and then went down the list and tried
> >
Excerpts from Doug Hellmann's message of 2018-06-14 13:02:31 -0400:
> Excerpts from Ghanshyam's message of 2018-06-14 16:54:33 +0900:
> > > > > Could it be as simple as adding tempest-full-py3 with the
> > > > > required-projects list updated to include the current repository? So
> > > > >
Excerpts from Doug Hellmann's message of 2018-06-07 14:28:02 -0400:
> As we discussed in today's office hours, I have set up some space in the
> wiki for us to track which TC members are volunteering to act as liaison
> to the teams and other groups within the community to ensure they have
> the
Excerpts from Ghanshyam's message of 2018-06-14 16:54:33 +0900:
>
>
>
> On Thu, 14 Jun 2018 05:55:55 +0900 Doug Hellmann
> wrote
> > Excerpts from Doug Hellmann's message of 2018-06-13 12:19:18 -0400:
> > > Excerpts from Doug Hellmann's messag
Excerpts from Doug Hellmann's message of 2018-06-13 12:19:18 -0400:
> Excerpts from Doug Hellmann's message of 2018-06-13 10:31:00 -0400:
> > Excerpts from Ghanshyam's message of 2018-06-13 16:52:33 +0900:
> > > On Wed, 13 Jun 2018 05:09:03 +0900 Doug Hellmann
> > &
Excerpts from Doug Hellmann's message of 2018-06-13 10:31:00 -0400:
> Excerpts from Ghanshyam's message of 2018-06-13 16:52:33 +0900:
> > On Wed, 13 Jun 2018 05:09:03 +0900 Doug Hellmann
> > wrote
> > > I would like to create a version of the jobs that r
Excerpts from Ivan Kolodyazhny's message of 2018-06-13 18:01:26 +0300:
> Hi team,
>
> Last week on the Horizon meeting we discussed [1] possible options for
> Horizon release model to address current issues for plugins maintainers.
> Some background could be found here [2].
>
> The main issue is
Excerpts from Matthew Thode's message of 2018-06-13 10:23:45 -0500:
> On 18-06-13 20:53:06, Rong Zhu wrote:
> > Hi, Matthew
> >
> > Solum removed pycryto dependency in [0]
> >
> > [0]: https://review.openstack.org/#/c/574244/
> >
> > --
> > Thanks,
> > Rong Zhu
>
> Yep, just in time for the
Excerpts from Ghanshyam's message of 2018-06-13 16:52:33 +0900:
> On Wed, 13 Jun 2018 05:09:03 +0900 Doug Hellmann
> wrote
> > I would like to create a version of the jobs that run as part of
> > lib-forward-testing (legacy-tempest-dsvm-neutron-src) that works u
Excerpts from Jean-Philippe Evrard's message of 2018-06-13 11:04:51 +0200:
> > - Drop tags, write a regular report instead that can account for the
> > subtlety of each situation (ttx). One issue here is that it's obviously a
> > lot more work than the current situation.
>
> That's what I'd
Excerpts from Zane Bitter's message of 2018-06-12 17:52:24 -0400:
> On 12/06/18 11:41, Michael Johnson wrote:
> > I think we should continue with option 1.
> >
> > It is an indicator that a project is active in OpenStack and is
> > explicit about which code should be used together.
> >
> > Both
Excerpts from zuul's message of 2018-06-12 21:57:02 +:
> Build failed.
>
> - release-openstack-python
> http://logs.openstack.org/2c/2ca19224a22541ceccf74c6f760ee40a2c90fed2/pre-release/release-openstack-python/124b5be/
> : FAILURE in 6m 45s
> - announce-release announce-release : SKIPPED
>
I would like to create a version of the jobs that run as part of
lib-forward-testing (legacy-tempest-dsvm-neutron-src) that works under
python 3. I'm not sure the best way to proceed, since that's a legacy
job.
I'm not sure I'm familiar enough with the job to port it to be
zuulv3 native and allow
to see any patches during Stein, but it is
still maintained. Is it still part of OpenStack under this definition?
>
> I think 2 and 3 will just lead to confusion and frustration for folks.
>
> Michael
> On Mon, Jun 11, 2018 at 7:50 AM Doug Hellmann wrote:
> >
> > Exc
Excerpts from Dean Troyer's message of 2018-06-12 09:28:48 -0500:
> On Mon, Jun 11, 2018 at 5:02 PM, Emilien Macchi wrote:
> > While I agree with Doug that we assume good faith and hope for the best, I
> > personally think we should help them (what we're doing now) but also make
> > sure we DO
Excerpts from Matt Riedemann's message of 2018-06-11 18:00:12 -0500:
> On 6/11/2018 3:31 PM, Doug Hellmann wrote:
> > As we shift teams over to Storyboard, we have another opportunity
> > to review the processes and to decide how to use the new tool. Some
> > teams with
Excerpts from CARVER, PAUL's message of 2018-06-11 19:53:47 +:
> Jeremy Stanley wrote:
>
> >I'm just going to come out and call bullshit on this one. How many of the
> >>800 official OpenStack deliverable repos have a view like that with any
> >actual relevant detail? If it's "standard"
Excerpts from Jay S Bryant's message of 2018-06-11 11:42:52 -0500:
>
> On 6/11/2018 11:17 AM, CARVER, PAUL wrote:
> > Jumping into the general Storyboard topic, but distinct from the previous
> > questions about searching, is there any equivalent in Storyboard to the
> > Launchpad series and
Excerpts from Doug Hellmann's message of 2018-06-05 12:14:19 -0400:
> 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
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 Thierry Carrez's message of 2018-06-11 11:53:52 +0200:
> Hi everyone,
>
> As some of the OpenStack deliverables get more mature, we need to adjust
> our release policies to best handle the case of deliverables that do not
> need to be updated that much. This discussion started
Excerpts from Dmitry Tantsur's message of 2018-06-11 16:00:41 +0200:
> Hi,
>
> On 06/11/2018 03:53 PM, Ruby Loo wrote:
> > Hi,
> >
> > I don't want to hijack the initial thread, but am now feeling somewhat
> > guilty
> > about not being vocal wrt Storyboard. Yes, ironic migrated to Storyboard
Excerpts from Thomas Goirand's message of 2018-06-07 22:17:11 +0200:
> On 06/06/2018 10:04 PM, Doug Hellmann wrote:
> > I have started submitting a series of patches to fix up the tox.ini
> > settings for projects as a step towards running "python3 first"
> > [
As we discussed in today's office hours, I have set up some space in the
wiki for us to track which TC members are volunteering to act as liaison
to the teams and other groups within the community to ensure they have
the assistance and support they need from the TC.
Excerpts from Jeremy Stanley's message of 2018-06-06 20:09:36 +:
> On 2018-06-06 14:52:04 -0400 (-0400), Zane Bitter wrote:
> > On 29/05/18 13:37, Jeremy Stanley wrote:
> > > On 2018-05-29 10:53:03 -0400 (-0400), Zane Bitter wrote:
> [...]
> > > > * If the repo is a fork of another project,
Excerpts from Sean McGinnis's message of 2018-06-06 15:14:48 -0500:
> On 06/06/2018 03:04 PM, Doug Hellmann wrote:
> > I have started submitting a series of patches to fix up the tox.ini
> > settings for projects as a step towards running "python3 first"
> > [
Excerpts from Anne Bertucio's message of 2018-06-06 12:28:25 -0700:
> > Either way, I would like to ensure that someone from
> > Kata is communicating with qemu upstream.
>
> Since probably not too many Kata folks are on the OpenStack dev list
> (something to tackle in another thread or OSF
I have started submitting a series of patches to fix up the tox.ini
settings for projects as a step towards running "python3 first"
[1]. The point of doing this now is to give teams a head start on
understanding the work involved as we consider whether to make this
a community goal.
The current
Excerpts from Zane Bitter's message of 2018-06-06 14:52:04 -0400:
> On 29/05/18 13:37, Jeremy Stanley wrote:
> > On 2018-05-29 10:53:03 -0400 (-0400), Zane Bitter wrote:
> >> We allow various open source projects that are not an official
> >> part of OpenStack or necessarily used by OpenStack to
Excerpts from Dmitry Tantsur's message of 2018-06-06 18:24:00 +0200:
> In Ironic world we run doc8 on README.rst as part of the pep8 job. Maybe we
> should make it a common practice?
That seems like it may be a good thing to add, but I don't know
that it is sufficient to detect all of the
Excerpts from Akihiro Motoki's message of 2018-06-06 16:36:45 +0900:
> Hi the release team,
>
> When I prepared neutron Rocky-2 deliverables, I noticed a new metadata
> syntax check
> which checks README.rst was introduced.
>
> As of now, README.rst in networking-bagpipe and networking-ovn hit
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 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 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 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 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,
> > >
&
301 - 400 of 3301 matches
Mail list logo
