►
From YouTube: 2023-02-14 meeting
Description
cncf-opentelemetry@cncf.io's Personal Meeting Room
A
C
Hey
era:
okay,
happy
Valentine's
Day.
It
might
make
the
meeting
easier
for
everyone.
C
C
Okay,
so
we.
C
Thanks
everyone
for
counting
so
for
people
who
haven't
met,
Alex
is
from
elastic
and
he
has
been
working
with
like
Josh
Trask
and
me
on
the
some
of
the
semantic
convention.
Part
in
the
past
few
weeks.
Hey
I
haven't
just
saw
your
joy,
so
the
purpose
of
this
is
there's.
C
An
old
have
I
put
that
in
the
meeting
with
invite
so
there's
an
an
old
type
which
has
been
running
for
for
a
long
time,
and
the
intention
is
to
better
align
the
elastic
common
scheme
at
ECS
with
open
time
trade,
semantic
convention,
I,
I,
think
on
one
side
of
inflammatory,
cementing
companies,
especially
like
when
Josh
and
fast
car
driving
something
we're
saying
some
benefits,
we're
saying.
Oh,
like
maybe
like
we.
We
should
better
look
at
elastic
common
scheme
and
see
what
we
can
learn
from
that.
C
Instead
of
introducing
our
own
thing
and
for
some
existing
thing,
we
already
know
this
hey,
it
might
be
better.
We
just
take
ECS
on
the
other
side,
we're
also
seeing
something
like
ECS
invented
certain
things
back
like
10
years
ago,
but
now
there's
a
better
way
to
model
it
like,
like
Josh
export
resource.
So
we're
saying
this
at
the
base
on
the
elastic
side,
my
God's
feeling
is
there
there's
some
thinking
about
hey.
We
should
have
some
translation
so
like
open,
Telemetry
and
elastic
can
interrupt.
There's.
C
Also
one
extreme
push
like
maybe
like
we'll
just
merge
them
and
announce
it's
just
one
single
schema,
whatever
we
call
it,
maybe
like
open,
Telemetry,
common
schema
or
something
then
it'll
be
much
easier.
So
the
purpose
of
this
meeting
is
to
explore,
like
from
from
both
elastics
and
and
open
Telemetry.
What
are
the
things
that
we
we
can
accept?
C
What's
the
bottom
line
and
see
in
like
if
we
put
a
Time
boxing
working
to
release
the
HTTP
cement
convention
by
maybe
like
end
of
March
or
end
of
April-
and
we
don't
want
to
just
spend
two
years
discussing
about
this
over
and
over
again,
what
can
they
do
either?
We
agree
on
okay,
this
is
something
feasible.
Let's
just
take
necessary
change
and
try
to
online
and
make
some
big
announcements.
This
is
great
for
the
industry
or
we'll
just
realize.
C
Oh,
there
are
too
many
details
or
maybe
like
work,
conservative
there's
something
we
don't
want
to
give
up,
so
we
won't
be
able
to
have
a
perfect
plan.
Let's
just
face
the
reality
and
have
two
different
schemas
and
go
to
the
translation
and
give
up
on
the
on
the
extreme
goal
of
aligning
on
one
single
schema.
So
one
has
to
have
this
open
discussion
and
explore
here.
I'll
stop
here
and
see
if,
like
anyone
else,
wants
to
add
additional
topics.
C
It
really
okay,
so
I'll
put
the
extreme
question
here
now
now
that
I
started
saying
I'm
crazy,
but
my
ask
is
what?
If
open,
Telemetry
and
elastic
can
work
together
and
in
the
end,
elastics
Will,
Made
announcements,
saying
ecis
is
contributed
to
open
climate.
What
may
make
a
donation
and
open
temperature
will
make
announcements
saying
hey
like
we're
about
the
most
part
of
the
ECS,
with
the
understanding.
C
Some
part
will
need
to
be
modernized
and
won't
work
that
in
the
next
course
of
years
closely
with
all
the
relevant
folks
and
and
for
HTTP
semantic
comments
that
also
helped
unblock
us,
because
a
lot
of
house
seems
to
be
if
we
can
borrow
from
ECS.
We
have
high
confidence
because
most
of
this
have
been
existing
for
multiple
years
and
used
in
production.
So
so
that's
my
question
and
I
want
to
know
like
from
Alexander.
C
B
B
Of
course,
otherwise,
I
mean
we
cannot
break
our
products
right.
The
existing
ones
and
also
the
big
concern
is
like
what
what
to
do
with
the
yeah
is
I
mean
the
the
less
the
common
schema
is
generally
available
right,
so
we
have
a
community
who
built
like
their
Integrations
using
that
schema.
B
So
if
we
cannot
align
in
a
way
that
that
we
are
not
introducing
breaking
traditionships
and
I
think
being
realistic
on
both
sides,
it
won't
be
possible
to
go
this
route
without
introducing
breaking
changes
so
yeah.
Those
are
basically
the
concerns
we
have,
so
what
we
were
thinking
is
whether
we
can
find
like
a
common
core
that
we
can
align
on
and
like
if
ECS
would
be
like
a
superset
of
of
something
that
is
based
on
on
open
Telemetry,
maybe
something
that
is
more
realistic
and
easier
to
achieve.
Also
yeah
for
both
sides.
C
Yeah,
maybe
I'll
I'll
just
call
like
jobs
and
had
to
share
some
of
the
collaboration
between
like
open
instances
and
open,
slash
and
also
open,
tracing
and
open
language,
because
they
previously
they
were
leading
some
of
the
effort
and
and
during
the
merge
like
there's
a
there's.
A
huge
decision
at
open
synthesis,
open
tracing
will,
merge
and,
and
still
today,
we're
not
100
done
so
they're
always
pros
and
cons.
But
from
my
observation,
because
I
I,
like
I,
started
open
census
from
my
observation.
C
E
Oh
okay,
I'll
go
first
yeah,
so
you
know
it
was
a
big
lift
to
switch
from
open
tracing
to
open
Telemetry,
but
the
idea
of
being
like
anti
XKCD
and
actually
reducing
the
number
of
standards
in
the
world.
It's
like
really
attractive,
but
there
were
some
differences
there.
E
The
main
thing
on
the
open
tracing
side
that
we
were
having
to
do
was
change
to
a
new
API
and
because,
as
part
of
like
Building
open
Telemetry,
we
were
able
to
have
the
API
layer
as
like,
fully
separate
interfaces
that
are
fully
separate
from
the
implementation.
It
made
it
a
lot
easier
to
build.
E
You
know,
Bridge
code,
that
allowed
open
tracing
to
still
work
but
ensuring
that
open
tracing
would
we
didn't
so
radically
change
the
model
that
open
tracing
wouldn't
work
was
was
I,
think
part
of
the
deal
and
I
imagine.
It
was
something
fairly
similar
on
the
open
census
side.
A
Well,
outside
of
metrics,
but
I,
think
I
think
that
one
made
sense
because
we
actually
aimed
to
align
with
Prometheus
there.
A
A
You
know
when
we
look
at
the
number
of
users
of
open
census.
It's
not
it's
not
growing,
but
it's
not
declining
right
and
so
we're
still
working
on
some
open
census.
Compatibility
work
at
the
spec
to
kind
of
fully
turn
that
down
from
a
tracing
standpoint,
I
think
anyone
who
was
using
open
census
purely
for
tracing
has
already
migrated
to
open
telemetry,
but
folks
who
are
using
it
for
both
metrics
and
tracing
that
that
work
is.
A
If
you
want
to
see
what
it
looks
like,
you
can
just
watch
the
open
census
space
for
the
next
like
year
and
you'll,
see
what
turndown
looks
like
there
from
us,
like
the
compatibility
layers
that
we're
building
and
that
sort
of
thing
just
as
an
FYI.
But
the
I
think
the
important
thing
here
is.
It
is
possible
to
kind
of
move
people
towards
a
single
Direction
and
it
is
a
movement
and
it's
organic
and
it's
slow.
It's
not
you're,
not
on
a
one-year
timeline.
A
We
announced
open
census
deprecation
three
years
ago
to
move
people
to
hotel,
actually
possibly
bored
at
this
point,
but
I
believe
it
was
about
three
years
ago
to
2019
yeah
so
and
then
there's
a
journey
right
and
so
we're
not
forcing
anyone
to
move
the
two
specs
still
live
together,
we're
just
not
making
any
changes
to
open
census,
because
we
said
the
future
is
open,
telemetry
and
we're
ensuring
that
there's
a
compatibility
kind
of
layer
and
enough
friendliness
that
that
journey
is
not
expensive
for
users
when
they're
ready
to
shift
to
like
a
new
standard.
A
So
that's
kind
of
that's
kind
of
what
we're
going
after
there
with
ECS.
This
is.
This
is
rather
interesting
right
because
you
have
the
same
thing
with
you
know:
open
census,
to
open
Telemetry,
there's
a
resource,
that's
in
the
model
and
that
resource
is
a
bag
of
of
attributes
and
things
that
is
modeled
in
ECS,
but
not
necessarily
as
its
own
Concept.
In
some
thing
right,
we
we
see
that
with
Prometheus
as
well.
A
Now,
if
you
look
at
their
push-based
protocols
and
like
where,
where
they're
enhancing
their
spec,
so
they're
actually
looking
at
otel
to
kind
of
help
out
with
that
a
little
bit
for
their
evolution
and
future,
so
that
that's
an
area
where
we
might
look
at
the
two
specs
and
say
you
know,
this
resource
concept
has
a
lot
of
value.
We
see
value
for
users,
shifting
to
it
right
and
then,
in
the
end,
users
kind
of
get
a
better
view
of
telemetry
because
of
it.
A
But
remember
this
is
a
long
journey
and
there
there
you
what's
the
we're
not
going
to
force
users
to
get
rid
of
something
they
find
useful
right
like
you,
don't
some
users
are
like
you,
you
probably
this
from
my
dead,
cold
hands
kind
of
a
thing
if
they
really
like
a
piece
of
technology
and
they
don't
want
to
move.
That's
not
the
goal
here
right.
The
goal
here
is
is
to
align
the
direction
to
provide
to
make
sure
that
there's
value
in
aligning
the
direction
right
that
there's
a
gain
for
users.
A
That's
the
most
important
part
and
then
provide
enough
kind
of
help
in
layers
of
utilities
where
they
actually
see
moving
to
the
new
standard
as
an
overall
gain,
as
opposed
to
purely
a
cost
right
open
tracing
by
design.
It
was
easy
to
swap
out
a
new
back
end,
so
an
open
tracing,
open,
Telemetry
Bridge
was
pretty
easy
to
create
open
census
by
Design
was
global,
and
so
we
actually
had
to
go
into
open,
set
the
only
changes
in
code
to
open
census.
A
A
What
does
apply,
though,
is
there's
going
to
be
an
equivalent
set
of
tools
and
kind
of
thinking
and
Transformations,
where
we
want
to
be
able
to
say
if
you
have
ECS
data
right.
What
does
it
look
like
in
hotel
and
if
you
have
tools
that
rely
on
ECS
structured
data?
Is
there
some
sort
of
convenient
thing
we
can
provide
with
in
otel
to
basically
get
the
same
value
that
those
tools
are
providing,
but
on
the
otel
spec
right?
E
Yeah
and
if
I
could
just
add
one
thing,
I'd
like
to
comment
on
something
you
said
Alex,
which
is
around
like
ECS
being
like
a
superset
of
what
we're
doing
from
from
our
perspective,
we're
we're
actually
like
I
would
say
the
consensus
seems
to
be
that
we're
actually
very
fine
with
adopting
the
parts
of
ECS
that
we
haven't
touched
yet
Whole
Hog
right,
like
they
might
actually
need
to
be
extended
in
some
sense,
because
they're
event
focused
and
we'd
have
to
talk
about.
E
Well,
how
do
we
apply
this
to
tracing
and
other
things,
but
for
us,
that's
not
a
problem,
and
when
it
comes
to
governance,
we
would
want
to
make
sure
that
all
of
the
expert
working
groups
who
are
currently
working
on
those
domains
would,
you
know
like
we
would
have
like
a
model
that
would
make
them
feel
comfortable,
totally
merging
it.
So
for
us
that
that
part
is
is
fined.
The
only
real
Humdinger
we
have
is
just
on
both
sides.
It's
actually
the
the
core
stuff,
that's
in
use
by
everyone
everywhere.
E
You
know
both
user
bases
and
those
are,
of
course,
the
parts
that
are
mappable
but
aren't
exactly
the
same
stuff
like
networking
and
HTTP
and
like
super
bread
and
butter
stuff.
So
for
us,
that's
that's
the
tricky
bit
of.
E
Are
we
willing
to
to
basically
make
something
that
would
what
is
what
we're
getting
out
of
merging
these
things?
Valuable
enough
that
it's
worth
the
multi-year
journey?
That
Josh
is
talking
about
in
terms
of
setting
up?
You
know
translations
and
figuring
out
how
you
know
to
make
instrumentation
not
just
automatically
break
for
people
if
they
aren't.
You
know
already
running
some
kind
of
translator
and
things
like
that
is
all
of
that
worthy
the
effort
and
what
what
are
the
lines?
E
Maybe
for
both
communities
like
what
what
amount
of
pain
is
acceptable
and
what
is
what
is
like,
not
acceptable
and
I.
Think
there's
since
I
think
something
Trask
mentioned
the
last
time
we
were
talking
about
it,
but
if
we
are
actually
like
merging
these
things
into
some
new,
like
you
know,
Telemetry
common
schema
or
something
like
that.
E
A
big
announcement
like
that
sort
of
like
open
census
and
open
tracing
is:
is
it
a
big
enough
thing
that
it's
it's
understandable
to
end
users,
not
that
we're
gonna
break
them
immediately
but
like?
Why
there's
going
to
be?
E
You
know
a
bit
of
a
zipper
and
that
they're
gonna
have
to
participate
in
at
some
point
like
that,
going
all
the
way
there
provides
a
reason
for
for
doing
some
of
that
work,
but
stopping
short
of
that
feels,
like
the
amount
of
pain
tolerance
reduces
dramatically.
If
we
aren't
gonna,
we
aren't
gonna.
Take
that
that
final
step.
E
So
that's
that's
to
me
that
that's
kind
of
like
the
heart
of
it.
What
are
we
gonna
do
about
all
of
this
core
stuff?
That's
actually
the
parts
that
are
different,
the
easy
stuff
to
me
is
like
security.
We're
just
like
that's
awesome.
You
guys
are
already
gotten
to
the
point
that
you're
working
on
that
stuff
and
we
would
be
happy
to
just
adopt
what
you're
you're
already
doing.
C
E
C
Addition
to
what
had
mentioned
Alexa
wonder
is
from
elastic.
You
have
a
another
layer
of
the
sermon
you
mentioned.
The
same
point
maybe
like
elastic,
would
want
to
be
able
to
advance
certain
semantic
convention
and
and
there's
a
little
bit
concerned
about
like
like
if
things
is
merged
with
open
slabs
it
might
slow
down
or
it
will
lose
control.
So
my
observation
is
not
because
open
fluctuate,
like
even
for
the
API
SDK
part.
We
have
the
rendering
concept
automatic
convention.
C
We
also
have
the
like
ongoing,
like
conversation
about
allowing
vendors
to
either
stuff
and
also
like
being
being
a
Microsoft
employee.
Microsoft
always
had
has
something
that
cannot
be
fulfilled
by
open
Telemetry.
We
have
like
some
data,
compliancing
or
Microsoft
internal
schema
for
office
windows.
We
need
so
so
far.
I
haven't
seen
open,
telemetry,
communicate
blocks
or
slowing
us
down
on
any
part
of
that,
and
another
part
is
I.
Like
I've,
been
working
on
the
Telemetry
space
for
like
many
years,
I've
seen
like
semantic
convention
or
people
call
it
schema.
C
I've
seen
that
like
Windows
Office
the
departure,
sometimes
they
develop
their
own
thing
and
eventually
it's
just
too
different
than
some
somebody
will
reach
out
to
me
and
say
like
we
need
to
merge
again
and
that's
cause
more
pain
later
so
like
like
from
what
I've
observed
in
the
past
15
years
in
Microsoft,
people
start
operation
more
and
more
of
aligning
things
and
I've
actually
aligned.
Seven
different
schemas
across
Microsoft
I
know
what
like
Microsoft
GitHub
LinkedIn
every
time.
Such
things
happen.
C
The
thing
is
now
just
to
have
multiple
things
to
do
in
Translation,
it's
about
alignment
and
Facebook
probably
has
similar
things.
They
have
a
paper
cup
10
of
them.
That's
a
similar
thing.
So
so
it's
based
on
like
what
you
believe
and
and
based
on
my
experience.
I'm,
saying
like
aligning
earlier
is
much
better
than
independently
developing
things
by
some
loose
collaboration
and
in
the
end
throughout
the
thing
and
try
to
merge
them
all
together.
B
Yeah
make
some
sort
of
sense
to
me,
like
I
mean
what
you
just
mentioned,
that
there
are
like
vendor
specific
stuff
anyways
like
always
on
top
it
I
mean
it
practically.
It
doesn't
sound
like
yeah,
really
different
to
to
what
I
meant
I
think
yeah
we'll
have
like
our
modification
and
in
the
beginning,
maybe
more
than
like
long
term.
So,
as
you
said,
it's
maybe
a
journey
of
aligning
these
two
schemas.
C
B
C
We
have
a
high
schedule
focusing
on
the
HTTP
semantic
comment
right.
The
main
Drive
is
open
climate.
It
started
as
a
distributed
tracing
solution.
Later
we
added
a
matrix
now
like
tracing
and
metrics.
Both
have
stable
version
of
the
apis,
they
can
be
offer
the
user.
So
it's
like
you
have
all
the
cookware,
but
people
ask
like
do
you
have
food,
and
the
answer
is:
oh,
that
part
is
not
stable.
We
don't
have
stable
automatic
conversion,
even
for
hdv.
C
If
they
use
open
Telemetry
and
and
this
means
they
have
a
tight
schedule
like
we
hope
to
get
the
HTTP
semantic
convention
stable
by
like
March
April
time
frame
and
and
we
have
a
hard
decision
so
either
we
we
know
that
oh,
it
doesn't
seem
to
be
feedable
for
us
to
align
with
elastic
very
soon.
So
we'll
keep
that
conversation,
but
that
probably
will
take
a
year
or
two
or
like
don't
go
notes
so
we'll
just
take
the
existing
HD
semantic
conventions.
C
Another
option
is:
let's
take
the
short-term
pen
and
we'll
maybe
we'll
have
some
breaking
changes,
or
maybe
it
will
need
to
even
bring
some
tools
to
smooth
out
the
change,
but
we're
going
to
make
the
change
to
align
with
ECS.
If
elastics
is
willing
to
work
with
open
climate
tree
just
to
have
one
single
standard,
then
it
gives
us
a
better
position.
We
can.
We
can
convince
other
folks
by
saying
this
breaking
change
or
additional
tooling
work.
It's
worth
it
so
so
these
are
the
two
options
we
have.
C
The
third
option
is
we
try
to
break
something
by
aligning
with
ECS
while
elastic
is
not
giving
us
a
high
confidence
that
we're
like?
We
can
have
this
one
standard,
then
it'll
be
almost
impossible
to
convince
the
like
folks
in
the
community
like
this
morning,
I've
received
a
lot
of
folks
from
Europe.
I
won't
be
able
to
make
this
meeting,
because
it's
too
late
for
me
or
because
it's
Valentine's
Day
but
I,
want
to
make
sure
that
you
mentioned
like
breaking
changes,
is
going
to
be
a
huge
issue
for
us.
C
We've
been
running
open
climate
trade,
showing
our
customers
in
production
for
a
year
or
two,
and
unless
there's
a
super
strong
reason,
we
shouldn't
break
anything.
So
we
think
that
from
GitHub
from
dynastrates
from
from
many
Fox.
So
if
you
can
give
us
some
support
by
saying
hey,
taking
this
breaking
change
or
making
additional
tools
won't
achieve
a
better
story
for
the
entire
industry
down
the
past,
for
maybe
like
five
ten
years.
That's
something
we
can
use
to
convince
the
others.
Otherwise,
without
strong
support
from
you,
I
feel
we're
we're
going
to
just
announce.
B
I
see
okay
like
by
by
when
do
we
need
to
decide
because
I
mean
I
cannot
decide.
This
covers
like
multiple
Solutions
within
elastic,
yes
and
I
mean
the
the
problem.
Is
that
like
ECS
was
a
lot
driven
by
our
security
solution
so
which
is
like
a
bit
far
away
from
observability?
That's
why
it's
a
bit
like
also
tricky
conversation
there,
like
in
in
you
know
like
deprecating,
something
where
they
like
to
don't
see
like
the
the
actual,
immediate
impact
on
on
their
side,
like
from
merging
into
open,
Telemetry
yeah.
C
Open
parameter
is
not
owned
by
any
single
individual
or
company,
so
I
cannot
speak
for
the
entire
Community,
but
we
have
fair
amount
of
like
technical
community
and
also
chat
from
the
governance
committee
here.
So
if
they
believe
I'm,
not
crazy,
I
think
maybe
I
can
represent,
like
eighty
percent
of
the
perspectives
just
crazy.
So
my
gut
feeling
is
if
we
cannot
have
a
conclusion
by
end
of
this
month,
then,
due
to
the
tight
schedule,
open
till
I'm
sure
will
just
move
ahead
and
and
stabilize
the
HTC
cement
convention,
which
is
the
core.
C
The
most
important
schema
that
we
ever
need
will
just
stabilize,
without
aligning
with
ccs,
of
course,
like
if
there's
anything
with
cecs,
we're
saying.
Oh,
this
makes
more
sense
and
it's
not
going
to
cause
a
lot
of
huge
headaches
or
bringing
changes.
We'll
probably
learn
leverage,
something
or
borrow
something
still
whatever
we
call
it.
It
might
make
it
easier,
but
their
their
fundamental
pieces,
which
is
just
too
big
to
break
and
what
will
not
be
aligning
with
ccs,
so
just
go
ahead
and
make
that
stable.
D
No
I
I
think
that's
really
how
I
see
it
also
is.
You
know
the
for
us
to
I,
actually
I
support
introducing
those
breaking
changes
into
HTTP.
D
If
and
only
if
we
can
make
an
announcement
that
you
know
that
ECS
and
open
Telemetry
schemas
are
aligning
from
a
governance
perspective
that
that
is
the
roadmap,
because
I
feel
like
that
is
the
only
I
think
that
is,
that
does
justify
the
breakage
and
I
think
that's
the
only
thing
that
justifies
the
breakage
to
our
community
and
from
a
timeline
perspective
yeah
we
are
targeting.
D
We've
got
about
I.
Think
four,
more
weeks
before
we
are
our
working
stability
working
group
is
going
to
make
final
recommendation
to
the
community,
and
then
the
communities
has
four
weeks
then
to
review
that
final
recommendation
and
two
weeks
to
Market
stable.
So
we
are
looking
at
late
April
current.
We
are
targeting
late
April
for
stability
and
given
the
amount
of
churn
there
of
introducing
if
we
do
break
everything
and
introduce
ECS
I
agree
with
Riley
that
we
need
to
we
needed
to
know
by
the
end
of
this
month.
B
E
Yeah
and
I
would
say:
yeah
we
don't
have
to
have
all
the
final
details
worked
out
by
then
just
you
know
do.
Do
we
have
a
commitment
to
to
hashing
out
those
details
or
yeah,
or
is
it
not
just
not
attractive
enough
for
the
record?
We,
you
know
looking
at
the
two
schemas
like
we're,
we
could
definitely
find
some
of
the
things
that
ECS
preferable
to
some
of
the
things
that
that
we
started
out
with
so
we're
not
we're,
definitely
not
opposed
to
this.
It
would
in
a
way
make
some
things
cleaner.
B
Yeah
makes
sense,
I
mean
there
are
things
in
open
Telemetry
that
we
also
would
like
to
like
adopt
in
ECS
and
and
I
think
wise
words,
which
are
like
the
low
hanging
fruits
and
the
easy
Parts,
but
like
the
the
really
core
and
and
really
hard
part
is,
are
the
breaking
changes
and
where
we
have
like
overlaps
that
are
different.
Yeah.
E
Be
very
reluctant
to
you
know,
change
their
choice
once
once
they've
done
it,
so
it
not
just
like
for
our
own
internal
timeline
but
also
kind
of
globally.
It
seems
it
really
seems
like
the
right
time
to
to
to
make
this
work
and
personally,
I
think
the
the
short-term
pain
of
like
sorting
out
a
new
governance
model
and,
having
some
you
know,
Annoying
duplication
in
our
instrumentation
repos
or
whatever
is
like
really
worth
the
idea
of
of
having
an
even
stronger,
more
unified
standard
around
this
stuff.
E
C
B
Okay,
yeah
I
have
my
homework.
I'll
reach
out
to
you
once
once
I
get
some
insights
on.
C
Okay
cool,
so
so
folks,
how
do
you
want
us
to
follow
up
on
this
like?
Like?
Do
you
prefer
I,
just
book
some
like
future
meetings,
maybe
like
like
twice
a
week
or
but
won't
just
see
a
slack.
C
I
I
would
suggest
we
use
slide
because
having
me
like
it's
hard
to
schedule,
meeting
that
fits
everyone's
schedule,
especially
a
lot
of
folks
are
in
different
time
zones.
So
all
the
early
morning,
meetings
for
me,
like
already
booked
by
some
other
community,
meets
inside
I,
know
probably
the
same
for
trust
and
and
Josh.
So
so
by
default,
I'll
create
a
slack,
Channel
and
add
all
of
us
so
Alex.
You
can
add
folks
from
elastic
I
who
won't
be
able
to
make
such
decisions.