►
From YouTube: 2022-03-31 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).
A
D
Whatever,
although
it
sounds
fun,
we
have
like
four,
three
or
four
of
the
gc
people
going
is
that
right,
yeah,
morgan.
C
I
I
have
my
cousin
visiting
me
that
week,
what
do
you
not
know
and
anything
on
the
agenda
today.
F
D
G
B
D
Let's
just
start:
let's
talk
yeah,
so
this
morning
we
had
the
end
user
working
group
or
whatever
it's
called,
which
is
good.
Although
there
are
zero
end
users,
I
mean
it's
like
which
is
maybe
okay.
I
think
the
idea
is
to
more
have
plans
around
end
users
and
I
felt
that
the
conversations
we've
had,
which
have
been
somewhat
limited
in
number,
but
there
have
been
a
couple
of
them
like
there's
the
one
with
atlassian
last
summer,
and
you
know
here
and
there
we
go
other
things.
D
I've
actually
been
quite
valuable
at
like
in
clarifying
in
some
ways
and
and
there
you
know,
there's
like
a
stream
of
work
related
to
doing
surveys
and
kind
of
broadcast
level.
You
know
end
user
engagement,
but
I
actually
really
wanted
to
more,
like
do
longer,
much
more
in-depth
sessions
with
specific
end
users
from
you
know,
organizations
that
are
trying
to
adopt
open
telemetry
at
scale
to
talk
about
where
their
bottlenecks
are
and
stuff
like
that.
D
So
I
think
a
lot
of
us
are
doing
that
as
part
of
our
day
jobs
with
our
you
know,
company
hats
on
anyway,
but
then
the
feedback
kind
of
comes
back
to
this
group
and
a
piecemeal,
and
I
don't
see
any
reason
not
to
do
a
sort
of
an
open
telemetry
head-on.
So.
D
Seems
to
think
this
is
a
fine
idea.
It'll
end
up
being
like
a
monthly
thing.
It's
not
a
requirement
for
the
gc
to
be
there
to
be
clear,
but
what
I
was
hoping
I
could
do
is
to
conscript
some
of
you
to
sign
up
to.
I
think
the
way
this
will
work
is
like
once
a
month
there
will
be
probably
an
hour
long
session,
where
we'll
get
an
end
user
to
show
up
and
people
from
hotel.
D
You
know
inside
people,
hotel,
insiders
like
us
and
tc
members,
or
just
anyone
really
who
understands
the
project
will
also
show
up
and
just
sort
of
like
interview
them
and
do
some
discovery
around.
What's
working,
what's
not
working
what
they
want.
Like
that
kind
of
stuff
record,
it
gather
the
notes
you
know,
and
hopefully
that'll
be
fodder
for
prioritization
in
the
future.
So
yeah.
D
So
the
thing
I
really
want,
though,
is
I
want
people
it
doesn't
have
pgc
members,
but
that's
why
I'm
bringing
it
up
people
to
kind
of
volunteer
to
just
get
someone
from
an
end
user
or
organization
to
show
up
like
on
a
given,
like
you
know,
you'll
like
if
I
I
might
sign
up
like
may
2022,
I'm
going
to
bring
someone
to
this
thing.
D
It
doesn't
have
to
be
like
that
customer
to
be
clear,
but
like
I'm
going
to
bring
someone
to
this
thing
and
then
you
know
someone
else
will
sign
up
for
june
and
hopefully
we
can
get
coverage
that
once
a
month
we
have
like
a
high
quality
conversation
and
I'm
just
looking
for
volunteers
to
find
those
people,
I'm
not
looking
for
the
end
users
right
now,
but
more
like
volunteers
from
this
group.
H
E
H
Reasonable,
I
have
a
quick
question,
though
two
of
the
javascript
maintainers
are
also
themselves
and
users.
Are
you
interested
in
people
like
that
or
on
people
who
are
only
end
users.
D
No,
no
that's
great.
I
mean,
I
think
the
point
is
just
I
mean
you're,
you
kind
of
sort
of
count,
but
not
relicus,
like
from
from
a
facebook
standpoint
like,
but
we
don't
have
many
people
who
are
coming
at
the
project
with
sort
of
semi
like
fresh
eyes.
D
A
D
I
I'm
not
saying
no
and
I'll
try
to
to
get
involved
as
much
as
I.
D
D
I
Know
you
know
going
to
conferences.
The
best
part
that
I
that
I,
that
I
find
is
talking
to
end
users,
is
talking
to
users
of
software
that
I'm
building
because
they
have
available
information.
For
me
they
have
ways
of
using
the
software
that
I
built
that
I
haven't
thought
about.
You
know,
so
it's
it's
very
valuable
to
talk
to
those
users.
So
I'm
not
saying
no,
quite
the
opposite.
I
love
talking
to
end
users
and
customers
and
so
on.
But
what
I
don't
see
here
yet
is
our
final
goal.
I
Here
I
mean
we
are
talking
to
them,
we're
gathering,
hopefully
gathering
information
and
then
what
what
are
we
doing
with
that?
Are
we
just
you
know
talking
to
users
and
collecting
this
data
and
then
figuring
out
what
to
do
with
that
or
do
we
have
some
something
concrete
that
we
can
tell
them.
I
Yourself
an
hour
with
us
and
then
in
six
months
time,
you're
gonna
come
up
with
a
survey
or
we're
gonna
do
x
or
y
well.
A
I
think
I
think
jurassic
we've
discussed
this.
You
know
in
parts
before
in
the
end
user,
you
know
meeting
as
well
as
otherwise
the
idea
was
that
we
would
have
a
list
of
questions.
You
know
or
topical
areas.
Focus
areas
in
the
discussion
say
we
want
to
do
30
minutes
with
a
particular
end
user
right
and
and
have
in
specific
categories
of
questions
and
questions
there
which
can
be
used.
D
Yeah
jurassic,
I
I
think
it's
you're
asking
the
right
question
in
terms
like.
What's
the
point
I
mean:
that's,
not
what
you
said,
but
that's
spirit
of
it,
and
I
I
just
I
guess
you
know
to
sort
of
show
my
hand
I
I
don't
think
that
we
have
enough
of
an
end
user
focus
in
terms
of
the
way
we're
prioritizing
things,
and
I
expect,
if
we
do
this,
the
comments
we
would
get
back
would
be
things
like
yeah.
D
You
know,
like
people
are
really
struggling
with
the
documentation
or
I
really
just
need
this
thing
to
be
stabilized
or
whatever
you
know,
and
then
I
think
that
would
just
help
us
as
we
try
to
step
back
from
the
kind
of
day-to-day
of
the
github
issues
and
to
make
sure
that
we're
applying
like
cons
there
are
considerable
resources
being
devoted
open,
telemetry
right
now,
but
I'm
not.
Actually
we
don't
have
a
very,
even
even
I
mean
forget,
like
a
quantitative,
data-driven
approach.
D
We
don't
really
have
a
qualitatively
data-driven
approach
to
prioritization
right
now
and
I
just
want
that
to
be
based
on
end
users
and
not
based
on
vendors.
Frankly,
so
that's
that's
kind
of
my
agenda
here
just
to
be
clear,
and
so
I
think
it
would.
The
ideal
thing
would
be
coming
out
of
these
things.
I
think
it'll
be
pretty
obvious
that
there's
some
pain
points
and
then
we'd
be
like
well.
D
I
I
How
about
then
we
we,
we
state
that
this
is
our
goal.
With
that
I
mean
in
six
months
time
or
one
year's
time
we
regroup.
Here
we
discuss
what
we
heard
from
customers
or
from
from
end
users,
and
then
we
we
try
to
get
some
information
out
of
this
data,
and
then
we
discuss
whether,
since
this
is
worth
or
not
doing,
you
know,
because
just
having
that
data
just
collecting
that
we
all
know
here
that
you
know
just
collecting,
it
is
not
enough.
I
D
Yeah,
okay,
I
mean
I,
I
think
that
the
the
goal
is
more
like
holistic
and
that
I
would
like
to
see
other
processes
like
reference
this
stuff,
I
would
be
happy
to
say,
like
we're,
going
to
schedule
six
of
these
and
then
decide
whether
to
continue
doing
it
like.
Is
this
just
extra
work
and
overhead,
or
is
this
actually
informing
decisions
and
think
of
it
in
that
way?
If
that
makes
sense,
yeah.
A
Because
I
I
agree
with
ben,
because
if
we
take
too
much
of
a
formal
approach,
it
also
you
know,
details
and
users
from
being
able
to
join
in.
So
I
think
that
we
should
just
do
three
sessions.
Learn
from
it
then
reiterate
iterate
based
on
lessons
learned
and
then
I
I
don't
think
we
have
a
prescriptive
solution
here.
D
Yeah
I
do
like
the
idea
of
saying
this
is
like
an
experiment
and
we
were
going
to
explicitly
decide
whether
or
not
it
was
useful,
and
that
sounds
good
to
me,
but
I
just
don't
want
it
to
be.
I
don't
want
like.
I
don't
want
to
tie
some
very
specific
outcome
to
the
what's
basically
user
research.
In
my
mind,.
I
That
that
makes
sense-
I'm
not
I'm
not
looking
for
a
very
specific
goal.
It's
just
that
yeah,
but
by
the
end
of
six
months
we
should
know
that
or
we
should
have
an
idea
what
to
do
with
this
data.
Yeah.
A
A
D
Makes
sense,
that's
that
makes
sense
good
good,
good
point
too
yeah.
A
H
Yeah,
I
guess
what
we
have
so
far
is
sponsorship
packets.
I
know
I
we
got
an
email
about
that
yesterday
from
lindsay
and
a
rough
schedule
which
I,
if
I
was
smarter,
would
have
already
pulled
up,
but
the
idea
is
to
have
you
know
an
opening
keynote
and
then
a
couple
of
speakers
in
the
morning
and
then
in
the
afternoon
have
a
a
handful
of
either
workshop
or
boss
sessions
or
similar.
H
The
three
sponsorship
levels
that
lindsay
sent
to
us
are
diamond
platinum
and
gold.
There's
a
limit
of
four
diamond
at
thirty:
seven
thousand
five
hundred
dollars,
gold
at
16,
500
and
or
no
platinum
at
16.5
and
gold
at
9
000.,
and
I
can
give
you
guys
the
the
specifics
on
what's
included
in
those
if
you're
interested.
H
And
then
there's
additional
sponsorship
opportunities
around
like
scholarship
funds
and
travel,
scholarships
and
stuff,
like
that
also,
I
guess
at
the
moment.
That's
all
we
really
have
in
terms
of
sponsorship
stuff,
the
cost
is
relatively
low.
Early
bird
in-person
tickets
are
200,
standard
would
be
250
and
on-site
would
be
350
or
360.,
and
then
virtual
tickets
are
20..
H
H
H
H
A
I
think
it
looks
good
daniel.
I
think
we
just
need
to
share
the
information
across
all
lords,
so
maybe.
H
H
But
I
think
we
have
what
eight
weeks
left
so
we're
getting
relatively
close.
Anything,
that's,
not
final
has
to
be
finalized
fairly
soon.
Is
anybody
here
planning
on
attending
open
source
summit.
H
H
H
E
More
things
firmed
up
of
what
we
want
to
do
for
room
time,
then
we
can
drive
something.
A
E
And
then
for
the
keynote
it
sounds
like
they
will
be
doing.
The
project
updates
they're,
going
to
reach
out
to
us
in
two
weeks.
E
Think
about
what
they're
gonna
do.