►
From YouTube: 2022-06-16 Governance Committee private 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
Oh,
it
was
too
bad
about
trask.
A
Oh,
that's
unfortunate
is
anybody
else
coming
from
microsoft,.
B
I
have
no
idea,
nobody,
that's
joining
the
maintainers
panel,
but
I
I
don't
know.
A
Okay,
I
guess
we'll
we'll
just
if
workshop
will
stand.
A
A
All
right,
let's
do
an
quick
agenda.
A
Is,
oh,
that's,
dead,
good,
hi,
ted.
A
A
Okay,
cool:
I
can
start
with
the
hotel
day
in
austin
on
monday,
and
I
think
that
many
of
us
are
going
there
I'll
be
there.
I
have
already
been
coordinating
with
morgan.
You
know.
Morgan
is
not
being
able
to
join
in
person,
so
he
and
I
will
be
doing
the
welcome
you
know
for
and
kickoff
for
the
hotel
day
and
I
I'll
be
there
in
person.
So
we
have
a
deck
that
we're
working
on
and
I'll
share
it
shortly
with
everyone.
A
So
folks
can
take
a
look
and
if
there's
anything
you
want
to
add
and
other
than
that,
I
think
daniel
again
huge
thanks
for
organizing
the
maintainers
who
are
going
to
be
there
if
they
can
join
in
for
the
maintainer
track.
Did
you
want
to
just
step
through
the
program
quickly?
I
think
they,
like.
I
have
the
link
here.
A
A
I
put
it
on
chat,
is
it
visible.
B
A
B
Yeah
so,
like
alolita,
said
she's
doing
the
opening
remarks
with
morgan.
I
guess
that
will
be
hybrid
in
person
and
virtual
austin
will
be
the
mc
for
the
event.
So
that's
pretty
cool
he's
gonna.
B
Do
a
a
quick
community
update
but
he'll
be
essentially
on
stage
for
the
entire
morning
yeah
after
that
we're
going
to
do
a
meet
the
maintainers
panel,
similar
to
what
we
did
at
kubecon
for
those
that
were
there
just
bring
as
many
maintainers
as
we
can
up
front,
hopefully
try
to
get
as
many
questions
as
we
can
from
the
audience,
but
I'm
gonna
also
prepare
a
bunch
in
advance
also
in
case
there
aren't
enough
questions
to
fill
the
time,
and
I
guess
I'm
sort
of
leading
that
and
yeah
there's
a
handful
of
different
maintainers
on
there.
B
Of
course,
and
you're
you're
obviously
welcome
to
join
us
on
stage
too.
So
after
that
we
have
michael
heyron
from
aspecto.
B
Aspecto
is,
I
think,
most
people
here
are
familiar
with
it,
but
they're
a
thorough
tracing
vendor
who
uses
open
telemetry
for
their
agents
yep,
and
then
we
have
a
few
lightning
talks
in
the
the
late
part
of
the
morning
and
that
really
part
of
the
afternoon
and
then
we're
gonna
have
breakout
sessions
which
we
will
essentially
you
know
be
like
buff
type
breakouts,
we're
gonna
vote
on
topics
in
the
morning
and
then
at
lunch.
B
The
program
committee
will
sort
through
the
votes
and
and
figure
out
exactly
how
many
sessions
we'll
have
and
that
kind
of
thing
and
what
they'll
be
on
so
that's
gonna
be
essentially
the
entire
afternoon
and
then
we'll
have
closing-
and
it's
not
on
the
schedule
here,
but
we're
also
planning
on
having
dinner
with
all
the
contributors
and
maintainers
whoever's
whoever's
there.
So
yeah,
that's
awesome,
that's
basically
it
it's
in
person
and
virtual.
So
if
anyone
wants
to
watch
virtually
it's
not
too
late
to
register,
but.
A
I
think
I
think
ted
should
we
just
ping
austin,
for
you
know
kind
of
doing
some
tweets,
because
I
think
we
should
do
at
least
one
a
day
before
the
event,
so
that
folks
can
just
sign
up
virtually.
Even
if
folks
are
not
going.
I
mean
I've
been
just
spamming,
a
bunch
of
folks
or
just
asking
them
one
slack.
E
Yeah
yeah:
that's
a
great
idea
putting
out
one
last
reminder
on
like
the
main,
open,
telemetry,
slack
channels
and
twitter
and
stuff
like
that
I'll
ask
austin
to
to
do
a
blast.
A
Cool
and-
and
we
do
plan
to
cover,
like
updates
for
the
project
in
the
opening
remarks,
but
again
can
also
I
was.
I
was
actually
more
interested
in
the
breakout
sessions
you
know
and
what,
how
we
do,
those
ted
and
daniel.
Maybe
we
can,
I
think
austin
had
suggested
they
would
just
come
up
with
topics
you
know
and
during
the
sessions,
but
is
that
a
bit
too
disorganized.
B
No,
I
so,
I
think
in
the
morning
we
will
that's
what
this
block
right
here,
break
and
vote.
So,
okay
have
essentially
voting
with
sticky
notes
on
a
board.
Okay,.
B
Because
at
lunch
austin
you
myself
and
probably
lindsey
will
go.
C
B
Them
and
or
no
lindsay,
won't
be
there.
So
yeah
there's.
B
Else
right
you
just
yeah,
I
don't
I
don't
remember
her
name,
but
she'll
be
there
and
we'll
go
through
and
decide.
You
know
if
there's
10
votes
and
they're,
you
know
for
similar
topics,
we'll
consolidate
them
into
a
single
topic
and
decide
on
the
topics
from
there
and
and
make
the
afternoon
schedule
during
lunch.
A
B
Yeah,
I
think
so
lindsay
said
that
there
is
oh
a
sticker
table.
I
don't
know
I
have
a
bunch
of
telemetry
stickers.
I
could
bring
them.
A
Yeah
exactly
I
mean
you
know,
I
asked
shar
had
a
bunch
old,
so
I
asked
her
to
bring
them.
Anyone
who
has
anything
to
share
it'll
be
nice
to
kind
of
have
a
sticker
table.
E
Like
a
big
stash
of
it,
I
don't
I'll
see
if
I
could
get
someone
from
lightstep
to
send
over
a
pile
of
them,
but
that.
C
A
Even
if
we
could
get
and
see
if
I
can
get
some
usb
drives
to
just
give
your
book-
or
you
know
the
other
observability
engineering
book-
that
that
honeycomb
is,
you
know
giving
away
yeah.
E
I'll
definitely
be
able
to
print
out
a
like
a
qr
code
for
people
to
go
get
the
pdf
version
of
the
book.
Also
I'll
have
that
and.
A
Maybe
you
can
use
that
table
as
well.
Yeah,
because
can
we
add
I'll
pay
you
I'll
get
the
info
I'll,
also
broadcast
it
on
our
opening
remarks,
just
as
resources.
E
A
A
B
A
B
Okay,
I
think
that's
it
for
that
for
that
topic,
unless
anyone
has
questions
about
it,.
E
I
assume
that's
you
ted
yeah,
so
just
a
reminder
to
everyone
we'll
be
having
a
github
feedback
user
session
next
week,
thursday,
starting
at
noon.
Pacific
and
I've
invited
the
gc
plus
a
couple
people
from
the
user
feedback
group
that
I
know
would
want
to
attend
like
char
and
henrik,
but
just
wanted
to
check
in.
If
there
was
anybody
else,
people
could
think
of
who
definitely
should
be
there.
B
Have
you
talked
to
them
about
whether
or
not
they
are
okay
with
having
it
recorded.
E
Yeah
yeah
they're
fine
with
that.
B
Okay,
so
if
it's
recorded
and
they're,
you
know
if,
if
somebody
we
think
of
somebody
later.
E
Totally
like
we'll
we'll
be
able
to
yeah,
I
haven't
talked
to
them
about
putting
the
feedback
up
on
youtube,
which
is,
I
think,
where,
where
I
would
put
it
by
default.
But
you
don't.
E
Well
I'll
clarify
with
with
ariel
what
what
their
preference
is.
I
think,
if
they're
fine
with
it
being
publicly
posted,
I
I
don't
see
any
reason
why
we
wouldn't.
I
don't
see.
E
A
Yeah,
the
other
folks
ted
that
I've
still
been
working
with
you
know
again.
I've
mentioned
they
are
still
interested
and
and
also
maybe
atlassian,
because
they
are
very
involved
in
the
project.
It
would
be
good
to
get
some.
You
know
feedback
from
them,
so
we
could.
We
definitely
have
a
list,
it's
just
you
know,
that's,
let's
be
more
organized
and
then
maybe
yuri
yuri
one
of
these
days,
meta
can
provide
some
feedback
and
I'm
hoping
even
my
art
can
provide
some
feedback.
E
Yeah
just
fyi,
I'm
gonna,
be
on
sabbatical
for
a
few
months
so
july.
D
C
E
C
E
But
so
someone
else
should
make
the
calendar
invite
for
future.
Okay,
future
feedback
sessions.
A
E
Would
be
a
great
person
to
collaborate
with
on
this?
I
I
think
it's
just
a
matter
of
finding
the
peop,
the
organizations
that
are
willing
to
give
us
feedback.
A
B
I
just
added
one
I'm
actually
looking
for
the
message
so
in
the
the
gctc
message,
armin
posted
a
message
at
12
23
yesterday,
which
I
believe
is
during
the
tc
meeting.
So
I
assume
they
talked
about
it.
They
were
wondering
or
armin
was
wondering
at
least
whether
the
one
password
account
should
be
owned
by
the
gc
or
the
tc,
and
I
figured
since
we're
all
here.
We
may
as
well
talk
about
it.
A
I
think,
daniel
from
what
I
recall
you
know
in
previous
conversations
when
we
decided
to
use
one
password.
It
was
the
tc
that
was
going
to
be
responsible
for
managing
that.
But
you
know
again
that
doesn't
mean
that
someone
from
the
gc
doesn't
have.
I
mean
we
used
to
have
sega
on
both.
So
you
know
that
worked
out,
but
again
I
think
it
was
tc
first
and
then
gcs
backup.
C
E
Have
to
manage
github
and
all
the
other
stuff,
so
I
presume
it's
more
convenient
for
them
to
have
it
than
us
or
or
both
can
have
it,
but
but
they
definitely
would
need
it.
I
mean.
B
Yeah
I
mean
I
know
we,
somebody
asked
to
have
a
one
password
account
a
long
time
ago
and
it
got
made
and
then,
as
far
as
I
know,
nothing's
even
been
put
in
it.
So
I
don't
know
if
maybe
kill
it,
if
we're
not
using
it
yeah
yeah
exactly,
but
on
the
other
side
of
the
coin,
there
are
a
bunch
of
things
like
the
youtube
account.
Somebody
has
credentials
for
that.
Like
they're
they're.
B
That,
I
would
argue,
should
be
in
there.
I
don't
know
how
granular
the
1password
teams
permission
structure
is
and
whether
you
can
grant
you
know
whether
you
can
make
sub
teams
essentially
for,
like
you
know,
maybe
the
communications
sub
team
has
access
to
youtube
and
twitter,
and
then
the
you
know,
tc
sub
team
has
access
to
all
the
github
stuff.
You
know
I
I
don't
know
how
that
how
that
works?
Is
there?
Anyone
that's
used.
1Password
teams.
B
There's
definitely
some
things
like
that
that
I
think
should
be
in
there,
instead
of
just
whatever
people
happen,
to
have
no.
A
I
I
agree
that
was
the
original
intent
of
setting
it
up
right
so
that
that
was,
I
think,
the
discussion
last
year.
You
know
where
the
dc
actually
covered
this,
and
also
right.
A
B
I
made
a
comment
or
a
reply
on
iran's
message
where
I
said
essentially
that,
in
my
view
that
tc
owns
most
of
the
the
assets
in
there,
but
I
think
the
actual
one
password
account
itself.
I
view
as
more
of
like
a
community
and
governance
thing,
so
if
it
makes
sense,
tc
already
owns
all
the
other
administrative
stuff
if
it
makes
sense
for
them
to
own
this.
To
you,
I
get
that,
but
without
that
sort
of
historical
baggage,
my
immediate
thought
was
that
the
gc
would
own
the
open
telemetry
and
that
theory.
E
I
mean,
I
think,
the
I
I
agree
with
you.
It
would
be
great
to
to
get
all
of
the
passwords
in
one
place.
Instead
of
just
random
people,
who've
been
on
the
project
for
a
long
time
having
access
to
stuff
and
other
people,
maybe
not
the
tc
should
have
access
to
all
of
that
information
yeah.
I
don't
see
a
problem
with
the
gc
having
access
to
that
information
as
well.
E
Could
be
just
both
tc
and
gc
have
have
access
to
to
one
password,
and
then
you
could
look
at
team
structures
or
just
if
individuals
need
access
just
going
into
one
password
and
finding
the
the
account
and
password
that
person
needs
and
giving
them
just
the
thing
that
they
need,
rather
than
trying
to
manage
a
complicated
one.
Password
situation.
B
Yeah
I
mean
it
is
a
one
password
teams
account,
so
I
assume
you
can
give
access
to
a
single
secret
to
someone.
I
don't
know
how
that's
done,
because
I've
never
really
used
a
team's
account
there.
Well.
A
Daniel
is,
are
you
working
with
someone
then
on
the
tc?
Can
t
grin
or
armin
or
somebody
else.
E
B
Yeah
so
I'll
work
with
armin
on
that
and
then
I
suppose
one
more
item.
That's
not
you
know
an
item
from
follow-up.
From
last
week
the
dynatrace
marketing
page
did
get
updated.
I
didn't
get
any
pushback
from
them.
I
just
let
them
know
that
there
was
a
complaint
made
and
they
said
no
problem
and
they
changed
it.
So
they
didn't
even
change
the
wording.
They
just
removed
the
block
entirely
and
then
for
like.
I
think
it
still
says
a
top
contributor,
but
I
think
we
all
agreed.
That's
generally
fine
right.
C
B
Is
there
any
follow-up
for
the
the
telescope
stuff?
I
know
that,
like
we
talked
to
them
at
kubecon,
but
then
since
then
has
there
been
any
do
we
know
where
that.