Sounds like an excellent idea!

+1 to a DIB meeting that includes office hours. I could've used this last week 
:)

-amrith

From: Gregory Haynes [mailto:g...@greghaynes.net]
Sent: Friday, July 15, 2016 7:40 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [DIB] [TripleO] Should we have a DIB meeting?

On Fri, Jul 15, 2016, at 06:20 PM, Stephane Miller wrote:
There are a lot of interesting and complex changes going on with DIB at the 
moment. This is a good thing, but it also means that we have more complex 
decisions to make for the project. We've already taken one step to address this 
in proposing a specs process (https://review.openstack.org/#/c/336109/). 
However, I'm thinking we could also use some higher-bandwidth communication.

I'm proposing that we have a regular, IRC-based meeting for the project. This 
could be done on its own, or as part of the TripleO meeting. I don't think we 
necessarily need to do this every week, but a fortnightly chance to get 
together to chat about big changes, design, etc would be great.

DIB and TripleO DIB community, what are your thoughts?

- Stephane

Thanks for sending this out. I'd like to add another cause for having a weekly 
meeting:

I have noticed a pattern where our users don't have a great way to communicate 
with us and often this results in some incorrect assumptions about DIB as well 
as us not realizing some features that could help these users. I've been trying 
to make a point to get in contact with these downstreams and it's been pretty 
clear that just a small amount of communication between them and some folks who 
are more familiar with DIB goes a long way. Maybe this could serve as a sort of 
open office hours for these downstreams to bring up potential issues / ask 
questions / etc?

Something that might also work rather than decreasing frequency is making the 
meeting smaller than the standard hour (maybe just a 30 min max)? Obviously 
meeting times are never a minimum though, so we could also just hope to 
regularly decide we are done early.

Anyhow, I think the risk here is very low and there's a few things it could 
help with so IMO it's worth trying out.

Cheers,
Greg
__________________________________________________________________________
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

Reply via email to