+1, very well said. To be clear, by "decisions need to be brought back to
the list" I would say that the actual decision, including a chance for
others not on the call to have differing opinions, happens on list.

My understanding is that this is a longstanding regular meeting across
multiple orgs contributing to Datasketches. Integrating it appropriately
with Apache mailing list practices should be resolved during incubation. I
think a start is to emphasize this practice of proposing and finalizing
decisions on the list, including rationale/technical summaries that will
allow an asynchronous reader to follow and contribute to the trajectory of
the project.

Sometimes this is taken as some kind of rule forbidding efficient work
style, and it is not that. Most projects have some off-list *work*
happening in the sense that there are often people who may whiteboard, pair
program, talk about their own goals amongst themselves. That's fine and
good IMO as long as the list is still the authoritative and informative
record of what is going on with the project.

Kenn

On Wed, Oct 2, 2019 at 12:10 PM Dave Fisher <[email protected]> wrote:

> Hi -
>
> Having private synchronous discussions is not in good alignment with the
> Apache Way.
>
> Why? It is exclusive of the larger community and anyone who is curious
> about the project will not understand what is going on. If someone is in
> China or Australia they are automatically excluded. If someone is working
> on DataSketches on their own time or weekends they are excluded.
>
> If you must have these discussions then any decisions need to be brought
> back to the dev@ mailing list along with the rationale.
>
> Best Regards,
> Dave
>
> > On Oct 1, 2019, at 2:03 PM, Jelani Nelson <[email protected]> wrote:
> >
> > Is there a data sketches meeting today? I requested to join via Google
> > Hangouts but haven't received a response yet.
> >
> > -Jelani
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to