►
From YouTube: 2020-09-24 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).
A
B
A
A
So,
meetings
for
this
have
been
spotted,
so
we
originally.
This
was
like
the
website
sig
and
then
about
a
month
ago,
there
was
kind
of
a
discussion
in
the
community.
A
A
Because
they're
all
very
intertwined,
so
it's
like
okay!
Well,
let's
just
change
it
to
communications
in
general
and
the
website's
part
of
that
and
workshops
are
part
of
that.
And
if
we
want
to
say
you
know
say
something
as
the
project
yeah.
That's.
C
A
Agenda
read
that
issue:
yeah
we've
got
the
two
things
I've
got
for
really
are
seeing
who
showed
up
seeing
if
there
was
a
vibe
on
like
do
we
like
this,
this
charter
of
like
hey?
This
is
combining
these
things.
Actually,
let
me
find
that
and
move
that
in
here.
A
B
I'm
the
cto,
so
I
run
a
bunch
of
different
teams:
product
devrel,
technical
partnerships,
kind
of
own,
our
security
business,
somewhat
yeah,
a
bunch
of
other
stuff.
B
Yeah
we're
doing
working
on
an
exporter
and
been
participating
in
some
of
the
logging
work
and
a
little
bit
of
the
metrics
work.
So.
A
Yeah,
I
think
the
logging
stuff
will
be
interesting.
I
don't
like
when
it's
I
feel
like
there's
two
big
things
that
should
happen
once
we
get
out
of
once
we
kind
of
get
to
this
1.0
and
one.
A
A
It
was
a
really
good
suggestion
that
came
up
in
that
suggestion,
but
there
was
like
an
issue
filed
in
spec
today
of
remove
spam
context.
You
know
and
just
make
trace
id
span
id
attributes
on
things
and
it's
like
well,
if
that's
the
case,
then
you're
really
just
like
you
know,
trace
id
is
just
like
overall
context
fan
id
is
just
like
uuid
for
yeah
work
in
context,
and
it's
like.
Oh
well,
that's
the
same
sort
of
stuff
that
applies
to
spans,
and
then
you
talk
about
events
anyway.
B
A
C
A
Of
the
things
it's
it's
interesting
because
I
feel
like
it's
it's
one
of
the
things
that's
hard
to
talk
about,
because
it's
both
extremely
useful
and
also
extremely
not
useful,
because
the
way
it
works.
It
requires
a
lot
of
coordination.
I
think
between
like
different
humans
writing
software
about
like
what
is
bad,
what
goes
in
baggage,
and
that
makes
it
hard
to
use
in
practice,
even
though
it
sounds
easy.
A
A
Glitch
glitch.io
or
glitch.com.
Sorry,
oh,
okay,
there's
a
team!
It's
glitch.com
forward,
slash
at
open
telemetry!
I
think
yeah
put
a
link
to
it
in
the.
A
I
don't
necessarily
like
the
idea
of
using
glitch,
it's
like
the
canonical
sort
of
place
for
it,
but
there
is
one
downside,
so
there's
a
cool
thing:
where
glitch
will
let
you
basically
sync
a
glitch
project
to
a
github
repository
very
easily,
but
because
of
the
way
glitch
containers
work.
It's
like
we
couldn't
have
a
single
repo
with
all
these
different
things
in
it.
We
would
need
like
a
lot
of
different
repos
and
creating
repos,
and
the
hotel
organization
is
sort
of.
B
A
A
A
C
B
A
So,
like
we've
tried
in
the
past
to
have
like
basically
pms,
you
know,
project
level,
pms
that
can
kind
of
have
triage
roles
or
approver
roles
across
a
lot
of
things
to
make
sure
that
stuff
keeps
going
and
issues
are
getting
triage
and
there
was
a
lot
of
pushback
on
that.
So
you
know
one
option
might
be
kind
of
go
back
to
that
and
say
like
hey.
Could
we
have
people
that
are
responsible
for
these
things?
Have
this
sort
of
cross
project?
You
know
role
where
they
can
maintain
example:
code
in
each.
B
A
But
once
we
kind
of
pass
that
we're
at
a
stable
release
or
the
release,
cadence
drops
down
a
lot.
You
know
you
actually
almost
want
to
move
people
away
from
saying:
hey
go
to
the
repo,
because
the
repo
is
going
to
be
in
a
lot
of
flux
or
theoretically,
a
lot
of
flux,
as
opposed
to
whatever
is
happening
in
stable.
A
A
B
A
A
Github
and
you
look
under
the
pull
request,
there's
like
a
site
refresh
work
in
progress,
pr
that
has
some
that
I've
been
working
on,
and
this
is
basically
getting
the
site
ready
for
1.0.
A
Or
the
pr's
it's
in
the
pr's,
it's
247.
yeah!
I
see
it,
yeah
got
it
so
there's
some
work
that
needs
to
be
done
on
this,
both
making
this
branch
mergeable,
but
also
like
doing
more
stuff
kind
of
going
forward
with
it.
So
if
there
are
people,
if
you
know
anyone
that
is
interested
in
contributing
to
hotel,
that
is
more
like
a
design
or
a
web
person
or
wants
to
do
stuff
like
that,
then
shooting
my
way
appointment
with
the
repo.
I
can
step
back
and
do
more
pm
stuff.
B
So,
do
you
want
like
what
what's
the
site
written
like
I
just.
A
It's
a
hugo
site,
so
people
that
know
how
to
do
hugo
templating
people
that
know
how
to
do.
You
know:
scss
html,
yeah,.
B
Yeah,
let
me
ask,
let
me
ask
the
person
that
runs
our
studio.
If
we
have
anyone
like
that
yeah,
I
would.
A
Certainly
be
thrilled
to
get
some
people
that
know
what
they're
doing
oh
and
the
last
thing
is:
there's
a
open
country
community
day
coming
up
as
a
day,
zero.
A
To
that
in
the
notes,
but
if
y'all
have
anyone
or
want
to
publicize
that
we're
looking
for
lightning
talks.
A
It
just
we
just
announced
it.
I
just
I
think
they
just
put
the
site
up
yesterday
so
publicizing
this
getting
you
know
more
people
aware
of
it,
and
I
also
believe
that
they'll
be
looking
for
sponsors.
So
if
it's
something
you
all
are.
A
Cncf
is
running
the
event.
I'm
part
of
the
program
committee
and
I've
been
trying
to
drive
a
lot
of
it
cool
a
few
other
people
from
outside
the
community.
People
that
have
helped
with
the
observability
practitioners
summits
in
the
past
are
helping
with
it.
So
we'll
have
a,
I
think,
a
more
formal
announcement
pretty
soon
about
who
is
reviewing
stuff,
but
we're
also
not
trying
to
we're
trying
to
be
pretty
like
open
about
people
submitting
talks
like
I
really
like.
B
Yeah
yeah
for
sure
yeah.
I
will
let
our
folks
know
and
same
with
my
devrel
people
also
but
yeah.
It
looks
like
a
cool
event.
Yeah.
A
Thank
you,
yeah.
B
Is
it
like
gonna,
be
the
full.
A
Day
or
I
don't
know,
if
it'll
be
the
full
day,
I
don't
think
people
really
pay
like.
I
don't
think
people
would
pay
attention
to
like
a
full
day
event,
but
I
would
say.
C
A
Four
to
six
hours
depends
on
how
many
talks
we
get
like
lightning
talks.
We
get
depends
on
any
keynote
speakers
we
get
depends
on
how
many
like
group
discussions
we
get.
I
really,
I
think,
because
the
real
focus
I
want
I
want
to
be
is
on
sort
of
those
affinity
groups
and
the
the
breakouts.
So
you
know
if
you
figure
three
hours
of
breakouts
or
two
and
a
half
hour,
two
and
a
half
two
to
three
hours
of
breakouts.
B
Yeah
cool
and
the
breakouts,
you
want
tutorial
type
stuff,
or
what
are
you
thinking.
A
A
Because
of
the
cncf
yeah,
but
they
did
like
cubecon
for
free,
they
did
the
kubecon
keynote
for
free.
I
yeah
there
are
certain.
B
A
Yeah
and
once
we
maybe
in
a
couple
weeks,
if
we
have
a
bunch
of
sponsors
and
there's
no
sponsors
that
they
can
come
back
and
say-
oh
basically,
they're
pricing
it
to
try
to
offset
their
costs.
A
C
B
A
B
Yep
yeah,
if
you
here
I'll
fire,
you
away.
A
B
It
looks
like
they're.
All
these
days
are
actually
priced
the
same
yeah
I
pretty
much.
B
B
A
B
I
know
my
my
vp
of
demand
is
gonna
when
I
I
just
sent
it
to
her
she's
gonna
be
like
yeah.
I
don't
know
about
25k.
B
B
So
I'm
gonna
jump
on
to
this
other
call.
I
was
double
booked
on,
but
yeah
I'm
happy
to
contribute
and
let
me
know
what
my
I'll,
let
you
know
of
my
designer,
so
my
my
guy
that
runs
the
studio,
says
yeah.
C
B
No
I've
seen
a
couple
like
where
you
can
see
the
separation,
but
it's
about
it's
about
three
and
a
half
three
hour
drive,
maybe
something
right.
C
North
because
they're
in
near
orlando,
orlando.
C
C
B
Yeah,
well,
they
were
supposed
to
I
wore
my
nasa
shirt
because
blue
origin
was
supposed
to
launch
a
rocket
at
noon,
but
it
didn't
happen.
So,
oh
you
got
to
go
change
your
shirt.
I
know
I'm
just
kidding.
I've
been
stuck
on
calls
since
4
30
in
the
morning.
So
ouch,
that's
fine.
It's
all
good!
A
I
know
you
can
check
the
notes.
The
biggest
thing
is
a
community
day.
Did
you
get
my
email
about
that
by
the
way.
A
Anyway,
would
you
be
able
to
help
out
on
the
program
committee.
A
A
C
A
A
C
C
A
Yeah
but
yeah
other
than
that.
I
think
there
was
so
there
was
one
other.
We
had
a
discussion
about
this,
but
I
think
when
the
impetus
for
this
was
like
what
happened,
where
do
we
put
all
the
sample
stuff,
all
the
sample
code?
Because
right
now
it's
kind
of
split
you've
got
stuff
in
each
sig
repo?
Yes,.
A
I
don't
think
like
we
could
go
back
out
and
try
to
do
a
you
know
project-wide,
like
committer
approver,
for
just
like
examples,
but
that
doesn't
feel
like
a
great
fix
for
this,
and
I
think
it's
just
gonna
make
people
mad.
We
could
make
it
into
a
different
github
org
entirely
and
then
that
would
maybe
better
better
way
to
do
it,
but
then
you'd
be
splitting
splitting
stuff
up
and
maybe
in
a
natural
way.
B
A
C
C
A
Kind
of
one
and
avoid
shortcuts
right,
like
it,
avoids
unnatural
sharing
of
code
or
whatever
in
a
way
that
maybe
makes
that
example
hard
to
extract.
It
also
becomes
easier
to
say
like
rather
than
having
open,
dash
telemetry
forward,
slash
examples
forward,
slash
c-sharp.
B
A
C
C
A
A
A
C
A
Move
maybe
off
for
now,
but
I
guess
the
one
good
thing
about
an
example's
repo
is
it
would,
I
think,
the
pro
the
problem
with
the
single
examples.
Repo
is
just
like
so
many
different
concerns
right
like
yeah,
but
maybe
that's
not
like.
Maybe
maybe,
though,
it's
easier
to
deal
with
than
I
have
14
different
repos
now
other
than
that,
that's
really
the
only
two
things
I
really
had
was
like
making
sure
everyone's
kind
of
cool.
With
like
this
sig
expanding
and
becoming
a
website
and
educational
stuff.
I
think.
C
A
A
Another
than
that.
I
think
we're.
A
Okayish
sweet
just
do
you
know
where
the
do
stuff,
please
once
spec
finishes
or
runs
everything.
C
A
C
C
A
C
But
thank
you
for
that.
A
Yeah
no
problem,
I'm
surprised
at
the
amount
of
traction
it
got
to
be
honest.
C
A
C
Yeah,
that
was
my
feedback
as
well
like
there
were.
There
were
two
critical.
There
were
like
three
groups
of
critical
comments.
One
was
saying:
hey
the
spec,
like
everything
he's
breaking
all
the
time.
The
spec
keeps
changing
like
yeah,
fair
enough.
Like
that's
true,
there's
another
one,
they're
saying
hey,
they
hope
the
apis
seem
a
little
more
complex
than
I
think
they
should
be.
I'm
like
yeah,
I
mean
that's
my
opinion
as
well,
but
people
like.
C
A
I,
like
the
guy,
that's
like
120
16,
by
trace
identifier.
C
A
C
C
I
literally
the
only
person
I've
ever
heard,
saying
that
the
trace
identifiers
are
too
long
are
like
engineers
from
amazon.
That's
it
that's.
I've
literally
outside
of
like
ansi
auntie
from
amazon
have
never
heard
that
feedback
before.
A
C
A
A
C
A
A
C
C
A
C
A
C
Anyway,
I
was
happy
with
it
overall
and
thank
you
for
jumping
on
that,
so
quickly.
A
Okay,
all
right!
Well
I'll,
look
at
rescheduling
this
and
I
will
yeah
we'll
keep
going.
I
think
I
think
things
are
going
pretty
well
with
the
website
with
yeah
workshops.