Hi, On Wed, Jun 7, 2017 at 8:24 PM, Isabel Drost-Fromm <[email protected]> wrote: > ...Sorry for the many caveats, but I think it makes sense to think about what > could > go wrong and trying to find ways to address these concerns before the > community > is split into those informed by having the time and bandwidth to participate > in > weekly meetings and those who don't...
FWIW I agree with Isabel's concerns. Having video meetings is cool but it MUST be possible to participate efficiently in an Apache project in fully asynchronous mode. For this specific case I think sending brief minutes of those meetings to this list, with timestamps that allow one to quickly jump to a specific part of the video recording that they might be interested in, addresses a good part of the concerns. As well as, of course, announcing all meetings here and making them fully open. The other big thing is refraining from making *any* decisions in those video meetings. Proposals discussed there should be brought back to this list, similar to watercooler (or Slack) discussions that do happen and are great but need to move here. I think the Great Divide can happen between people who work full time on this project and can cope with the synchronous nature of video meetings and others who only have partial availability and other schedules. An Apache project needs to cope with both groups, that takes discipline but it's what enables our long term vision as well as collaboration between widely different groups. "If it didn't happen on the dev list, it didn't happen" remains as valid as ever. -Bertrand
