►
From YouTube: 2021-12-09 meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
A
A
I
don't
know
I
just
usually
I'm
not.
We
have
two.
We
had
two
zoom
links
today
and
I'm
worried
that
some
people
went
to
the
wrong
place.
Here's
adelina
that's
promising.
D
C
F
B
E
F
All
right,
so
is
this:
just
the
open
forum
for
different
items
that
folks
may
have
questions
on
or.
B
E
B
With
so
the
other
link
is
just
one
on
my
calendar,
but
I
noticed
that
this
that
I
copied
originally
from
the
open
telemetry
calendar.
So
maybe
it
was
an
older
one.
C
D
Well,
this
one
isn't
tied
to
the
changes
I
made
because
I
never
touched
the
gcm
meetings
when
I
made
changes
the
last
last
week
or
two
weeks
ago,.
D
B
E
D
C
D
There
was
that
that
looked
like
it
was
fine,
there's
also
a
setting
in
zoom
that
says
if
people
can
join
so
many
minutes
early
and
when
I
looked
this
morning
that
was
off
okay.
So
if
there's
any
kind
of
clock
skew
going
on,
then
perhaps
that's
what's
blocking
them.
I
set
it
to
15
minutes,
which
is
the
maximum.
I
changed
that
setting
this
morning,
though,
that
should
be
acceptable.
A
Well,
I
don't
know,
since
we
have
some
distinguished
guests
researcher,
do
you
have
things
you
wanted
to
ask
or
bring
up
or
feedback
questions
whatever.
B
I
do
actually
have
one
question
I
wanted
to
check
in
with
you
all,
so.
I've
been
working
kind
of
on
the
side
to
chat
around
end
user
like
a
perhaps
a
work
group,
and
one
of
the
challenges
that
we
have
identified
is
that
like?
If
we
were
to
create
a
survey,
it
would
be
tied
to
a
human's
account
and
we
were
wondering.
Is
there
any
resources
that
either
open,
telemetry
or
cncf
has
around
account
management
so
that
it's
not
like?
A
I
don't
know
if
other
people
have
thoughts
on
this,
but
I
know
that
we've
used,
I
mean
for
like
straightforward
surveys
and
things
we've
used.
Google
forms,
which
I
believe
has
a
permissions
model
that
supports
handoff.
I
mean
it's
still
tied
to
individual
accounts
and
that's
somewhat
unavoidable
in
that
world,
but
it's
not
like
yeah
I
mean
you
could
have
multiple
owners
from
different
places
or
whatever,
as
admins
on
the
forum
and
that
sort
of
works.
A
B
B
F
I
do
yeah,
I
use
my
gmail,
but
I
think
I
think
morgan
at
some
point,
we'd
also
discuss
that.
Maybe
it
might
be
possible
to
have
like
an
email
account
which
is
kind
of
a
shared
account
right.
D
I
already
created
it
in
order
to
make
the.
D
D
Yep,
it's
a
full
google
account.
It
doesn't
have
gmail
because
it
uses
the
governance
mailing
list
for
its
email,
but
but
it
is
a
complete
google
account
and
I,
the
main
reason
I
created
a
few
weeks
ago
is
so
that
we
could
tie
it
to
all
the
zoom
accounts,
and
so
people
can
sign
in
to
that.
So
we
can
just
share
the
credentials
for
the
google
account,
as
opposed
to
sharing
various
zoom
credentials,
that
people
can
do
more
damage
with
if
they
get
their
hands
on
yep.
D
Those
credentials
will
be
right.
We
haven't
the
only
place
where
they're
listed
for
sharing
is
they're
in
a
dock.
That's
pretty
locked,
it's
locked
down
just
to
maintainers
for
how
to
deal
with
zoom
and
zoom
bombing
and
the
credentials
are
there
in
plain
text
and
a
dock
which
is
not
amazing.
If
someone
has
a
better
idea,
please
do
it,
but
the
dock
itself
is
locked
down
to
maintainers.
C
At
some
point
we
talked
about
having
like
one
password
for
teams
or
something
like
that
yeah.
I
don't
remember
who
was
looking
into
that.
E
So
alex
clex
button
did
create
one
open,
telemetry
wide
one
password
account.
C
C
That's
a
better
place.
To
put
that,
though,.
F
B
C
Do
you
know
how
often
you
would
create
a
survey?
Are
you
thinking
about
doing
them
like
weekly
or
monthly
or
quarterly
or.
B
Well,
the
survey
in
question
that
we're
chatting
about
right
now
specifically
was
a
the
next
version
of
the
survey
that
was
created
by
some
of
the
folks
here.
That's
in
the
hotel
user
research
channel,
and
so
I
know
at
least
chatting
with
matt,
he
has
embedded
the
survey
link
into
the
docs
for
microsoft,
which
I
thought
was
really
interesting,
and
so
I
think
at
least
the
initial
use
case
would
be
a
persistent
survey
that
people
can
just
go
out
and
add
versus
point
in
time
surveys.
B
There
could
be
a
use
for
point
in
time
surveys,
but
I
don't
we
haven't
chatted
about
that.
Yet.
C
So
if
we,
you
know,
since
we
haven't
really
decided
how
widely
shared
the
credentials
are,
I
don't
know
it.
Would
it
be,
at
least
for
now
a
good
stopgap
measure
if
somebody
that
does
already
have
access
to
that
account
just
creates
a
survey
and
then
adds
your
account
as
an
admin
on
that
survey
or
something.
B
C
Yeah,
so
I
don't
think
I
have
access
to
the
account
yet
or
I
haven't
looked
up
credentials,
but
somebody
who
does
maybe
morgan
do
you
mind
doing
that.
C
B
B
We
don't
have
the
survey
complete
at
this
point
and
we'll
figure
out
how
to
share
whatever
we
need
to
share
at
that
point,
where
you
just
add,
like
my
personal
gmail
account
to
it
excellent,
and
so
the
second
thing
that
I
wanted
to
just
chat
about
is
alida,
and
I
have
chatted
a
little
bit
about
the
idea
of
creating
an
end
user
focused
work
group,
and
so
I
was
just
looking
for
feedback
on
if
you
all
think
that
there
is
a
need
in
the
community
for
a
working
group
that
specifically
targets
end
users,
such
as
doing
research
in
the
survey.
B
F
Yeah
and
and
again,
I
think
that
there
are
several
you
know.
All
of
us
speak
with
the
different
end
users
and
you
know,
try
to
actually
spread
good
practices
across.
You
know
instrumentation
and
configuration
and
other
you
know,
issues
that
folks
have
questions
on.
So
I
think,
having
an
end
user
work
group
on
the
project
itself
would
be
super
useful
because
it
gets
feedback
you
know
available
to
for
everyone
to
kind
of,
join
in
and
know
each
other
as
they're
actively
working
on.
F
You
know
deployments
of
open,
telemetry,
collector
or
or
even
using
the
sdks
right.
So
I
think
that
it's
all
good
because
it
really
provides
the
support,
even
whenever
needed
from
anyone.
You
know
maintainers
included,
who
are
interested,
can
participate
as
experts
so
that
the
thinking
really
was
to
provide
a
forum
for
end
users
to
be
able
to
come
and
ask
questions
and
the
you
know,
and
at
least
help
each
other
initially
and
then,
whenever
needed,
you
know
we
could
have
invite
guest
maintainers
to
come
and
talk
about
specific
areas.
F
It's
a
it
could
be,
I
mean
jurassic.
We
talked
about
a
couple
of
formats.
One
could
be
that
you
know
we
just
do
it
as
an
office
hours
where
we
could
actually
just
have
an
office
hour
session
once
every
you
know,
four
weeks
that
is
once
every
month
where
different
folks,
you
know
who
are
interested
could
participate.
You
know
sharing
trying
to
answer
questions
as
well.
As
you
know,
kind
of
taking
feedback
for
the
project
itself.
F
I
mean
I
mean
I'm
happy
to
you
know,
participate
in
that.
I
do
that.
You
know
for
many
end
users
anyway,
and
char
does
too
and
many
of
our
others
do
it
also
morgan
does
I
know
so
folks,
for
you
know
there
are
several
folks
even
on
the
gc
who
participate
there
and
and
then
use
our
maintainers.
You
know
as
experts
right
because
again
it's
not
that
we're
trying
to
have
a
very
you
know
in-depth
code
based
conversation
here,
it's
more,
you
know
trying
to
actually
address
the
issues
of
configuration.
F
E
Got
it
thanks?
Yeah
I
mean
I,
I
do
participate
also
in
some
other
communities.
So
that's
why
I
was
asking
I
mean.
Perhaps
we
can
you
can
not
use
but
make
connections
with
those
other
communities
and-
and
you
know,
direct
our
users
whenever
it's
something
else
more
than
open
telemetry.
E
F
I
mean
I
again,
I
I
think
one
of
the
things
I
would
say
is
that
it's
good
to
have
it
on
the
project
because
it
is
you
know,
collection
is
a
very
big
pain
point
for
most
end
users.
Today
and
and
as
open
telemetry,
you
know,
gets
deployed
components,
get
deployed
into
different
end
user
environments.
It's
something
that
you
know.
People
actually
want
to
hear
and
or
be
able
to
discuss
under
the
umbrella
of
the
project.
F
I
I
certainly
think
that
you
know
we've
tried
doing
that
in
the
tag
observability
group
for
exam
meetings,
for
example,
where
you
know
different
project
members,
that
the
prometheus
or
or
other
projects
you
know,
do
join
in
and
do
help.
But
I,
like
your
idea
of
you,
know
making
referrals
whenever
needed,
but
I
think
that
having
this
under
open
telemetry
would
be
useful.
F
Now
we
were
just
thinking
I
mean:
are
you
okay?
If
we
did
an
office
hours
kind
of
a
format
for
the
for,
for
this,
like
in
even
a
monthly
you
know
hour
or
so.
F
F
C
Yeah,
that's
in
that
case,
I
I
think
that
that's
a
great
idea.
One
thing
that
we
also
sort
of
are
missing
is
feedback
from
end
users
for
maintainers,
which
would
require
maintainer
participation
at
some
level
at
least,
and
I
you
know,
I'm
hoping
that
that
need
can
also
be
addressed.
Maybe
you
know,
maybe
this
doesn't
address
it
exactly,
but.
F
But
I
think
it's
a
good
way
to
get
the
word
out
right,
because
if
you
have
a
regular
office
hours,
I
mean
that's
very
easy
for
end
users
to
kind
of
know.
Okay,
there's
this
monthly
session
that
that
open
telemetry
has
that
we
can
easily
join
in,
and
it's
also
a
great
way
of
actually
sharing
any
of
the
requests
that
maintainers
have
for
feedback
right.
B
Yeah,
I
think,
there's
a
lot
of
different
ways,
especially
to
get
feedback.
I
hear
that
from
maintainers
that
I
know
of
just
like
they're
missing
that
feedback
loop,
that
you
get
in
a
more
traditional
software
project
and
so
daniel
to
your
question
about
how
to
like.
B
F
And
it's
also
to
take
away
the
is
somehow
reduced
some
of
the
noise
in
the
sig
meetings.
Like
you
know,
the
collector
sig
has
end
users
as
well
as
developers
joining
in
and-
and
we
don't
necessarily
you
know-
have
the
time
as
maintainers
to
be
able
to
address
every
end
user
question
so
just
to
do
justice
to
that,
you
know
again
having
a
more
peer-to-peer.
F
You
know.
Group
also
would
help
there
right
because
many
end
users
do
have
a
lot
of
expertise
on
hotel
they've
been
using,
you
know
different
components
or
they
have
done
specific
work
around
building
shims.
F
On
top
of
you
know,
hotel
components
where
for
to
support
their
own
environments
right,
whether
that's
terraform
scripts
or
whether
that's
you
know
just
deployment
recipes
or
whatever
right
I
mean,
but
but
again,
that's
end
user
territory.
At
that
point,
it's
not
necessarily
maintainers
working
on
the
core
code
base.
C
So
I
definitely
see
a
need
for
the
for
the
end
user
work
group
as
a
maintainer,
I'm
particularly
interested
in
the
like
the
feedback
survey.
I
think
that's
very
useful.
C
As
a
gc
member,
I
think
that
if
there
are
end
users
looking
for
somewhere
to
to
connect
like
if,
if
they're
already
looking
for
something,
then
it
makes
sense
for
us
to
to
provide
that
if
there
aren't.
You
know,
I
just
worry
that
if
we,
if
we
commit
to
doing
this
monthly
meeting
and
then
nobody
shows
up
or
something
like
that,
it's
yeah-
I
don't.
B
Agreed
yeah
and
I'd,
say,
I
think,
running
as
an
experiment
to
see
what
is
that
interest
level,
because
the
end
users
that
I
work
with
are
like,
amazingly
large
proponents
of
open,
telemetry,
and
so
it
doesn't
represent.
You
know
all
end
users,
but
certainly
I've
had
multiple
folks
wanting
to
figure
out
how
to
connect
with
other
end
users
and
have
asked
for
my
help
in
doing
that,
and
I
would
prefer
to
provide
that
in
a
vendor
agnostic
way.
E
So
one
question
that
did
I
have
for
you:
do
you
think
those
folks
would
would
be
open
to
joining
a
slack
channel
instead
of
a
monthly
meeting.
B
I
mean
at
least
from
an
end
user
perspective.
I
think
the
folks
that
I've
talked
to
they're
just
looking
for
any
way
to
connect
and
one
of
the
feedback
that
they
got.
Is
it's
hard
to
navigate
cncf
slack
as
it
is
currently
just
because
there's
so
much
chatter
that
isn't
relevant
to
them,
and
so
maybe
a
special
home
for
them.
There
would
be
something
they'd
be
interested
in.
I
will
definitely
chat
with
the
folks
on
my
side
who
are
interested
in
this
yeah.
I
think
this.
C
A
I
mean
monthly
meetings
are
tricky
because
it's
such
a
slow
cadence
that
it's
like
a
nice
time
to
build
a
relationship,
but
that's
probably
the
extent
of
it.
I
mean
the
thoughts
I
have
are
like
there's,
basically
two
broad
categories
of
end
user
involvement.
Maybe
three
one
is
just
like
literally
using
open
telemetry
and
that's
not
served
by
monthly
meeting.
That's
like
documentation
and
slack
where
we
die
right,
then
there's
people
trying
to
contribute,
which
is
the
thing
and
that
I'm
going
to
set
aside.
A
I
don't
know
people
are
sort
of
doing
that
now
and
then
there's
changing
the
roadmap.
That's
the
piece
that
I
actually
think
a
monthly
meeting
could
be
very
helpful
actually,
and
I
would
frankly
welcome
it.
It
would
force
us
to
have
a
little
more
discipline
around
roadmaps
and
having
like
end
users,
who
are
almost
signing
up
to
show
up
on
a
monthly
basis
and
provide
roadmap
and
prioritization
feedback.
A
I
think
that
would
be
really
useful,
but
and
could
be
done
in
a
monthly
cadence,
but
I
think,
like
the
onboarding
and
getting
started
stuff
in
like
the
sort
of
general
q,
a
is
not
going
to
be
served
by
a
monthly
meeting
and
I
don't
think
people
will
show
up.
That's
just
my
calling
how
I
see
it,
but
I
would
love
to
have
more
end
user
involvement,
input
and
prioritization
roadmap
decisions.
F
And
I
think
that
would
help
us
also
in
get
you
know,
kind
of
prioritizing
what
we
do
in
phase
phase,
one
of
logs,
for
example,
and
other
you
know
core
features
that
we
are
working
on.
A
Yes-
and
it
may
also
be
we-
I
mean
we
may
or
may
not
get
the
feedback,
that's
just
sort
of
like.
Could
you
please
stabilize
what
we
have
and
stop
adding
scope
or
whatever,
instead
of
but
it
would
be
nice
to
have
the
end
user
voice
providing
that
feedback?
So
I
mean
I
don't
know
I'm
happy
to
to
just
let
it
just
be
an
open-ended
thing,
but
I
almost
feel
like
we'd
have
more
participation
and
possibly
a
more
productive
meeting.
A
If
we,
if
we
said
this,
is
specifically
to
talk
about
roadmap
and
prioritization
for
a
contribution,
that's
you
know
the
reason
I
set
that
to
the
size.
I
think
that's
like
we've
talked
a
bunch
about
that.
It's
a
gc
about
improving
the
ratio
of
maintainers
and
things
like
that.
But
I
don't
know
if
a
meeting
is
helpful
or
not
I'm
happy
to
hear
that
it
is,
but
I'm
not
sure
if
that's
the
right
way
to
improve
that.
E
E
A
A
C
And
as
a
casual
user,
I
would
never
join
a
monthly
meeting
for
him
yeah
unless
I
was
super
into
it.
So
I
think
you
lose
out
on
a
huge
number
of
casual
users
if
you
require
them
to
join
a
monthly
meeting.
Yeah.
F
E
There
is
also
the
case
of
you
know,
different
time
zones
so
having
a
meeting
that
is
friendly
to
one
time
zone
is,
is
living
out
the
rest
of
the
road.
You
know.
F
Yeah,
I
I
think
I
mean
I
think
the
slack
channel
is
a
good
suggestion,
but
and-
and
we
should
definitely
do
that
as
a
baseline,
because
I
think
that
that
definitely
helps
everyone
and
we
could
you
know
kind
of,
do
it
in
a
way
where
some
amount
of
it
is
moderated
where
we
say
hey,
you
know
when
you're
joining
the
channel,
please
introduce
yourselves
or
you
know
the
areas
you're
working
on,
and
you
know
something
that
we
could
actually
collect
over
time,
which
is
helpful
to
the
project
or
you
know
at
least
having
some
some
amount
of
casual
handholding
and
then
folks
can
just
chat
with
each
other
right
and
that's
definitely
a
great
way
of
having
this
discussion
again.
C
C
F
F
Great
suggestion,
actually
maybe.
C
F
Yeah
totally-
and
we
can
do
some
more
some
more
sharing
and
communicating
about
this
meeting.
A
A
E
A
You
char
but
like
you
know,
that's,
unfortunately
not
been
the
norm,
so
I'm
not
sure
if
anyone's
really
gonna
care
but
yeah.
A
C
A
Be
yeah,
it
would
be
good,
yeah,
yeah,
okay,.
F
Yeah,
I
think
where
we
can
have
suggested
you
know,
topics
in
the
description
of
the
invite
and
then
we
can
just
you
know
I
mean
I'd,
be
happy
to
share
the
meeting.
You
know
as
as
a
place
for
people
to
come
and
join
and
ask
questions.
I
mean
people,
ask
end
users,
ask
questions
about
the
roadmap.
All
the
time
I
mean.
A
This
is
not
a
single
week,
there's
like
2100
people
in
open,
telemetry
slack,
I
think,
setting
blackboard
to
say
if
they
were
allowed
to
do
that
in
cncf,
select
to
say,
hey,
tomorrow's,
the
whatever
meeting.
These
are
the
sorts
of
things
we
expect.
So,
yes,
it
would
be
nice
people
to
show
up
a
lot
more
than
that.
I.
B
Yeah,
absolutely,
I
think,
there's
more
discussion
on
how
to
like
set
up
a
work
group
for
end
users
to
do
things
like
survey,
creation
and
stuff.
But
at
least
we've
got
the
tactical
issues
of
how
to
even
do
the
permissions
out
of
the
way
and
then
the
confirmation
that
y'all
are
interested
in
in
some
way
figuring
out
how
to
better
sponsor
feedback
from
and
engagement
with
end
users.
So
I'm
happy
with
that.
F
Okay,
cool
cool-
we
are
at
time,
so
we
do
have
follow-up
items
and
chart
will
definitely
connect
and
work
for
work
together
forward.