Flavio Percoco wrote: > [...] > Not being able to easily ping someone during a meeting is kind of a bummer but > I'd argue that assuming someone is in the meeting channel and available at all > times is a mistake to begin with.
I think people can be pinged by PM or on #openstack-dev, it's just an habit to take. It's just that there are cases where people passively mention you, without going up to a formal ping -- I usually go back later to that person to answer the issue they informally raised. We'll lose that, but it's minor enough. > There will be conflicts on meeting times. There will be slots that will > be used by several teams as these slots are convinient for cross-timezone > interaction. We can check this and highlight the various conflicts but I'd > argue we > shouldn't. We already have some overlaps in the current structure. Yes we could give an indication of how busy a given slot is, when people book it. I think the problem solves itself when the meeting participants are asked to select a time slot -- if there are too many conflicts people will naturally choose a less busy slot< > The social drawbacks related to this change can be overcome by interacting > more > on te mailing list. Ideally, this change should help raising awareness > about the distributed nature of our community, encourage folks to do more > office > hours, fewer meetings and, more importantly, to encourage folks to favor the > mailing list over IRC conversations for *some* discussions. My main gripe is that it that it reinforces silos, so this change hurts inter-project work more than it helps it. But at the same time, nobody was actually following every meeting anyway, so the damage is very limited. > So, should we let teams to host IRC meetings in their own channels? > Thoughts? I think it would smooth the transition to office-hour style coordination, which is a good step for more inclusion. I objected to the idea in the past (due to the social damage) but at this points the benefits probably outweigh the drawbacks. -- 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