►
From YouTube: 2022-07-28 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
A
C
A
A
D
A
D
B
C
Know
I
I
also
have
a
g
suite
for
my
for
my
own
domain
same
and
no
it's
not
the
same.
I
don't
see
that
I.
D
A
Private
g
suite
domain,
but
I
don't
really
use
it
much
for
anything,
but
well,
really
anything.
But
I
bet
it's
an
admin
setting
there.
A
B
E
E
Invited
philip
carter
today
because
he
had
a
question
to
ask
the
governance
committee
about
in
the
meanwhile,
while
we
don't
have
a
formal
community
manager
role,
things
fall
by
default
to
us
to
how
to.
A
D
Cool,
thank
you
yeah.
So
as
some
so
as
some
context,
I've
been
working
with
austin
on
this
a
little
bit
my
employer
and
liz
employer
honeycomb
approved
fifty
thousand
dollars
to
be
like
here
you
go.
This
is
for
people
who
want
to
contribute
now
it's
on
me
specifically
to
like
figure
out,
okay
but
like
like,
for
whom
and
for
what
contributions
and
so
on.
D
So
I
talked
to
various
folks,
the
community
and
some
folks
at
hotel
community
today
to
try
to
gauge
like
what
sorts
of
contributions
are,
the
kinds
of
things
that
are
likely
to
be
accepted,
because
we
don't
want
to
incentivize
like
a
hacktoberfest
pr
spam,
and
you
know
the
reality
is
that
a
lot
of
maintainers
are
stretched
thin
for
time
anyways.
And
so,
even
if
there's
like
a
really
really
awesome
like
feature
added
to
like
hotel,
go
or
something
like
that,
it
doesn't
mean
that
it
could
actually
get
reviewed.
D
And
everybody
agrees
in
that,
so
anyways
came
up
with
some
criteria
where
everybody
who
I
talked
to
felt
like
they
would
be
happy
with,
and
that
was
primarily
around
documentation
samples
part
of
that
is
because
I
can
be
on
the
hook
for
approving
documentation,
changes
on
the
on
the
website
itself
and
then
samples,
even
if
they
live
inside,
of,
like
a
given
languages,
repository
tend
to
be
far
easier
to
to
review
because
it's
more
like.
D
A
Feel
like
docs
and
samples,
also
the
benefit
of
if
someone
comes
in
who's,
never
used
otel
before
they
actually
benefit
from
their
lack
of
experience,
because
they
will
run
into
problems
that
we
would.
Our
experts
would
be
like.
Oh,
I
know
how
to
fix
this,
and
wouldn't
men
wouldn't
really
think
about
it.
Yeah.
D
Yeah,
so
we
would
like
to
move
forward
because,
like
so
from
the
honeycomb
standpoint
like
the
money
is
allocated,
and
so
like
the
you
know,
there's
nothing
administrative
on
the
honeycomb
side
that
will
prevent
a
program
from
being
kicked
off
and
and
happening,
and
then
eventually
giving
people
cash
for
certain
things.
D
When
I
talked
with
austin,
he
managed
to
get
in
contact
with
someone
at
the
cncf
who
now
is
on
like
a
european
vacation,
so
they're
just
totally
gone
for
quite
a
while,
which
is
great
good
for
them,
and
they
wanted
to
like
have
some
written
down
criteria
for
like
what
are
the
specific
things
that
we
want
to
incentivize
and
what
are
like
some
dollar
figures
for
them.
So
I
have
that
in
a
dock
that
I'll
I'll
put
in
chat
here.
This
is
this
is
just
like
me
writing
down.
D
This
is
not
like.
Oh,
this
is
the
the
end-all
be-all
of
everything
here
and
what
categories
of
contributions
and
there
are
and
that
can
be
rewarded
and
like
what
a
reward
for
each
one
could
be.
Consider
examples
numbers
all
this
stuff
as
like
placeholders
that
I
pulled
out
of
my
butt.
These
are
not
like,
like
you
know,
something
that
some
manager
at
honeycomb
is
like.
Okay,
I
have
approved
this
last
bit.
D
There
would
be
some
work
to
identify
what
some
of
those
are
and
who
who's
already
in
the
community,
and
this
is
like
capable
of
getting
something
over
the
finish
line
if
they're
up
for
it
would
be
willing
to
like
actually
do
that
and
be
like
hey,
here's
like
10,
000
or
so
like.
D
I
I
don't
know
just
trying
to
think
creatively
about
that
kind
of
stuff,
but
we're
running
into
administrative
problems
with
the
cncf
now,
because
the
the
community
maintainer
role
that
austin
has
a
proposal
for
like
this
is
exactly
the
sort
of
thing
that,
like
that
person
in
that
role,
can
like
facilitate
and
because
that
doesn't
exist.
He's
like
it's
hard,
and
so
we
would
like,
like
speaking
just
strictly
from
the
honeycomb
standpoint.
D
Not
just
have
it
be
like
this
honeycomb
specific
thing,
but
it's
kind
of
gummed
up
right
now
and
yeah
to
answer
the
question
with
the
cncf
like
right
now,
we're
seem
to
be
talking
to
a
black
hole
where
austin
asks
a
question,
and
then
we
get
nothing.
E
B
Right
right
I
mean
exactly
and
and
also
the
other
thing
is,
that
is
this
again,
I'm
just
wondering
if
these
you
know,
contributor
programs
are
just
under
the
projects.
Typically,
because
these
this
is
like
an
ubuntu
bounty
program.
Where
you
know
you
have
you're
sponsoring
folks
to
contribute
to
the
project.
B
And
and
the
other
question
I
have
again
based
on
the
doc:
that's
there
right
now,
philip
is
that
is
there,
you
know
also
code,
that's
being
worked
or
is
it
just
sample
apps
and
documentation?
And
you
know
things
like
that.
F
I
just
wanted
to
I'll
go
ahead.
No.
C
F
F
I'm
I
think
it's
great
for
the
governance
committee
to
say
this
is
great,
but
honestly,
I
don't
really
know
why
you
need
our
permission
to
do
this.
It
seems
like
I
mean
you
if
honeycomb
wants
to
spend
money
on
stuff,
that's
an
ecommerce
business.
As
far
as
I'm
concerned
I
mean,
is
it.
E
Just
no
it's
the
matter
of
we
don't
want
to
add
excess
load
on
maintainers.
We
would
like
to
you
know,
have
some
help
with
promoting
this
to
say,
like
hey,
like
you
know,
a
generous
sponsor
from
the
community
wants
to
encourage
people
to
make
the
community
project
better.
That's.
B
B
Effort,
I
think
it's
nice
to
have
a
collaborative
effort,
because
it
also
recognizes
that
you
know
different
teams
are
contributing
and
interested
in
supporting
the
project.
So
my.
F
Other
comment
was
just
it's
kind
of
been
tactical,
but
I
partly
just
to
I
mean
I
don't
think.
Hopefully
these
people
who
are
doing
this
work
aren't
going
to
be
strictly
driven
by
the
money,
but
just
to
like
make
it
a
little
bit
more
likely
that
they're,
not
gaming
things.
I've
always
found
that
example
apps.
That
are
more
of
like
it's
like
a
sample
app
or
an
example
of
some
integration,
but
it's
also
an
integration
test
where
we're
validating
that
the
instrumentation
actually
generates
correct
telemetry.
F
On
the
other
side,
it's
a
lot
more
valuable,
mainly
because
when
it
inevitably
falls
out
of
date,
the
test
breaks-
and
I
would
much
more
I'd
much
prefer
to
have
that
and
then
also
as
a
reviewer.
You
don't
take
on
the
burden
of
actually
running
the
thing
and
validating
that's
correct.
It's
like
well
the
test
passed.
I
can
see
that
the
desired
output
in
the
pr-
that's
enough
for
me,
like
the
code,
looks
good
output
looks
good.
I'm
done
so.
F
C
C
Along
along
the
same
lines,
so
I
would
rather-
or
I
prefer
testable
examples
or
use
case
driven
examples
so
that
we
get
notified
whenever
things
break.
So
that's
completely
in
line
with
what
ben
said.
The
other
thing
that
I
I
do
see
as
receiving
by
with
open
hearts
is
open.
Arms
is
fixing
test
failures
or
improving
the
ci,
so
we
have
quite
a
bunch
of
flaky
tests
on
on
a
collector
contrib,
and
I
assume
most
of
the
repositories
have
the
same
problem
and
sometimes
it's
problem
with
the
code.
C
B
C
Great
bigger
features,
even
though
they
are,
they
might
be
on
our
roadmap,
even
though
they
might
be
provided
from
from
0
to
100
by
an
individual
and
refused
by
a
company
that
is
based
on
my
experience,
not
so
much
desirable,
not
not
as
desirable
as
the
other
two
things,
because
we
had
a
case
in
the
operator
where
a
feature
a
big
feature
was
contributed,
and
now
we
don't,
we
don't
actually
have
any
maintainers
that
are
able
to
review
that,
or
people
are
just
busy
with
other
things,
and
now
we're
stuck
with
that
huge
piece
of
code
that
you
know.
C
Nobody
really
cares
about.
So
I'll,
really
accept
or
I'll,
be
really
happy
to
see.
Examples
use
case
driven
examples,
plus
a
fixing
test
switch.
B
Yeah
and
and
also
to
add
to
that
another
consideration
could
be
that
you
know
the
sample
apps,
that
you're
talking
about
one
of
the
things
I've
seen,
which
also
works
out.
That
is
actually
building
a
playground,
which
is
a
you
know,
reaper
within
the
project,
but
at
the
same
time
you
know
relatively
independent
and
has
its
own
maintainers,
so
that
different
types
of
samples
and
applications
and
workflows
can
be
added
in,
and
you
know,
people
can
actually
work
within
that
environment
right.
B
So
that's
kind
of
an
super
sample
app,
but
except
for
a
lot,
a
lot
more
variable
variations
possible
and
being
extensible.
B
So
that
might
be
something
worth
considering
long
term
anyway,
because
of
just
you
know
the
number
of
data
sources
that
can
be
plugged
in
into
hotel,
as
well
as
the
types
of
different
languages
that
have
you,
know,
instrumentation
versus
not
there's
so
many
different
variations
right
so
worth
considering.
But
again,
I
think
this
is
an
excellent
program
and
I
don't
think
that
other
than
you
know
we
can
help
in
helping
it
announce
on
the
project
blog.
I
think
that
probably
you
guys
can
just
go
and
run
with
it.
G
I
don't
see
anything
here
about
who
qualifies
and
what
is
the
process
for
determining
who
qualifies
to
receive
a
monetary
reward?
There
are.
G
And
I
assume
you
don't
want
to
double
pay
those
people
I
I
mean
this
is
something
you're
already
thinking
about,
but
I
don't
see
it
documented
anywhere.
D
G
Yeah,
it's
up
to
you,
it's
your
money
and
that's
just
something
that
that
I
thought
about.
G
Another
thing
is
I'm
having
sort
of
you
know
call
it
flashbacks
to
when
the
aws
and
google
interns
all
flooded
the
project
in
the
first
year
of
covid,
because
they
had
like
50
interns
that
they
didn't
know
what
to
do
with
suddenly
and
in
some
cases
like
I
remember
for
javascript,
we
were
totally
flooded
with
them
and
it
actually
slowed
us
down
in
a
lot
of
cases,
because
the
maintainers
were
completely
overwhelmed
and
I
would
want
to
see
some
protection
against
that
like.
G
I
wouldn't
necessarily
want
to
see
three
people
open,
almost
identical,
pr's
and
then
everyone's
fighting
to
get
theirs
merged
because
there's
a
250
reward
for
it.
I
would
like
to
see
some
sort
of
process
for
saying
this
is
the
feature
or
the
documentation
or
whatever
that
we
want.
G
These
are
the
acceptance
criteria
and
then
to
have
somebody
volunteer
for
it
with
a
with
a
set
timeline
and
like
have
it
pre-approved
for
one
specific
person
before
the
work
starts
and
then,
after
some
number
of
like
you
know,
if
two
weeks
there's
no
pr,
then
it
goes
back
to
open
for
proposals
or
something
like
that
again.
Yeah.
B
Right,
right
and
and
also
I
would
say,
that
consider
a
dsoc
kind
of
model
where
there
is
actually
a
mentor
before
even
the
maintainers
are.
You
know
approached
because
that
was
something
again
I
can
you
know.
Given
I
ran
the
aws
internship
participation.
B
G
Those
are
my
thoughts
comments
concerns
whatever
you
know,
take
with
them
and
do
what
you
will
like.
I
said
it's
your
money
in
terms
of
whether
the
gc
needs
to
approve
this
or
not.
G
I
would
say
I
would
appreciate
it
if
you
know
having
gc
approval
on
something,
and
you
know
says
that
we
we
looked
at
it
and
thought
through
all
these
issues
and
are
happy
with
that,
with
whatever
resolutions
came
from
them,
I
would
say
you
could
do
a
project
like
this
without
the
gc
approval,
but
I
appreciate
that
you're
looking
for
it
and
then
also
if
it's
going
to
be
promoted
in
official
channels,
I
think
yeah.
I
I
appreciate
that
that
you're
asking-
and
I
am
generally
supportive
of
the
idea
and
the
concept.
C
Yeah
same
here
and
just
to
make
it
to
make
my
comments
here
on
the
chat
more
concrete,
we
could
have
a
special
label
across
the
repositories,
like
I
don't
know,
feature
accepted,
donation
accepted
or
whatever
something
similar
to
the
good
first
issues
that
we
have
and-
and
you
can
tell
people
you
can
pick
any
one
of
those
issues
as
long
as
you're
the
first
one
to
take
that
and
candidates
will
then
just
leave
a
comment
on
the
issue
like
can
I
take
this
and
whenever
people
do
that,
then
maintainers
can
then
actually
assign
the
issue
to
that
person
and
that
person
then
becomes
the
owner
for
that
issue
for
and
then
for
a
certain
period
of
time.
C
If
people
just
don't
do
anything
for
a
couple
of
weeks,
then
we
can
just
unassign
and
it's
a
progress
again.
G
Yep-
and
I
think
each
issue
should
have
like
a
you-
know-
a
very
explicit
acceptance
criteria-
something
that's,
hopefully
not
too
subjective
and
a
time
period
right,
yeah,
just
you
don't
want
people
to
say.
Can
I
take
this
and
then
three
months
down,
the
road
have
not
done
anything
and
there's
other
people
waiting.
That
would
have
done
it,
but
I
I
trust
that
you're
competent
to
solve
problems
like
that.
D
To
an
extent
so
so
like
for
honeycomb,
you
could
you
could
actually
just
say.
That's
me,
the
the
the
the
people
who
allocated
the
funds
were
like
here.
You
go,
we
did
our
job.
This
is.
D
So
there's
some
some
of
this
is
in
my
head,
so
I
guess
a
partial
yes,
but
I
think
there's
work
that
I
need
to
do
here
to
clarify,
especially
some
of
this
stuff
is
actually
fantastic
feedback
for
sure,
and
I
think
I
also
do
want
to
do
another
pass
at
talking
to
a
couple
of
other
maintainers,
because,
like
hotel
community
was
amazing
for
that,
because
hey
we're
in
person,
it's
super
easy
to
go
and
chat
to
these
people,
but
now
that
some
time
has
passed
like
chat
to
those
same
people
chat
few
other
people
that
kind
of
stuff,
because,
like
I
also
I
mean
one
of
the
thought
that
I
had
is
like
establishing
like
a
range
for
the
monetary
thingy
for
the
word
and
then
like
a
maintainer,
is
actually
the
one
who's
like.
D
Okay
like
this
is
like
within
this
range
like
this
is
kind
of
worth.
This
amount
that
maybe
that
could
be
helpful,
maybe
not
because
yeah.
At
the
end
of
the
day,
like
I
want
to
incentivize
good
things
that
are
that
everybody
is
happy
with
taking
in
that
are
merged
in
as
a
part
of
the
project,
and
that,
like
everybody,
especially
the
long-term
maintainers,
feel
good
about,
and
so
it's
I
guess
that
makes
it
more
complicated.
D
Asking
maintainers
to
like
help
establish
some
of
this
criteria
as
well,
but
I
feel,
like
that'd,
be
a
lot
better
than
walking
in
and
being
like,
hey
someone's
gonna
throw
this
pr
at
you.
Can
you
please
accept
it
and
we'll
give
them
some
money
and
like
yeah,.
G
I
was
just
gonna
say
the
same
thing
jurassic
just
said
in
the
in
the
chat:
it's
not
my
money
and
I'm
a
maintainer,
and
I
don't
want
to
be
like
I.
I
would
much
rather
have
a
honeycomb
person
say.
It
looks
like
this
is
the
the
range
because
I
I
don't
want
to
be
in
charge
of
of
determining
how
much
of
your
money
is
given
out
for
something.
Even
if
it's.
B
E
G
E
A
G
G
Would
say
it
sounds
like
everybody's
supportive
of
this,
but
there
need
to
be
some
details
ironed
out,
so
it
sounds
like
everyone
is
giving
tentative
thumbs
up,
but
I
wouldn't
want
to
approve
and
say,
like
let's
roll
with
this
and
start
tomorrow.
Until
I
see
more
detail
around
some
of
the
questions
that
we
do.
B
Yeah,
I
think
I
think
that
two
areas
phil
philippio
might
have
to
come
back
to
us
on.
One
is,
of
course,
the
process,
if
you
will,
for
you,
know
the
contributions
to
the
project
and
how
that's
managed
before
it
hits
the
maintainers,
and
the
second
part
is
that
you
know
what
do
you
expect
the
project
to
do
in
terms
of
just
promotion
right
of
the
program?
I
think
those
are
the
areas
where
it
intersects
with
the
project,
so
I
think
that
detail
would
be
great
to
have.
G
Yeah,
so
I
would
suggest
that
unless
anybody
has
burning
questions
about
it
right
now
that
I
think
we've
gotten
about
as
far
as
we
can
here,
I
would
suggest
that
you,
you
know,
fill
in
a
little
bit
more
of
the
detail
and
and
come
back
when
you're
comfortable
with
it.
D
Okay,
awesome
drossie.
I
actually
I
really
love
your
your
question.
There
can
we
start
smalling
ramp
up.
I
could
definitely
take
point
on
that,
specifically
for
the
website
repo,
since
yeah.
E
I
was
gonna
say
like
let's
just
start
with
docs
right
like
let's
do
this
as
a
pilot,
and
I
think
that
we
can,
you
know
not
block
on
the
cncf
to
do
this
right
like
this
is
just
purely
a
governance
committee
thing
we
could
say
you
know
phil
if
you're
willing
to
do
the
work.
She
like
reviewed
the
prs
to
handle
the
process,
we
can
figure
out
what
works
and
what
doesn't
and
then
we
can
do
a
second
run
with
the
wider
program
later
once
we
have
the
results
from
the
first.
D
Yeah-
and
I
mean
I
also
think
from
like
a
promotional,
purely
promotional
standpoint
like
there's,
there's
no
reason
why
there
has
to
be
just
like
you
know.
One
singular
announcement
like
you
know,
maybe
to
this
point
like
we
get
a
little
bit
of
this
going
with
website
repo,
and
it
feels
like
there's
a
pretty
good
process
by
what
that
that
could
be
repeated
in
other
places
and
then,
like
maybe
a
cubecon
or
something
like
that.
D
However,
money,
however
much
is
like
left
out
up
or
something-
and
you
know
other
maintainers
are
aware
of
how
it
can
work
and
that
kind
of
stuff
we
could
talk
about
it
again.
I
think
it's
very
it's
very
open
in
terms
of
how
to
go
about
doing
it,
so
I
just
have
some
more
things
that
I
need
to
go
off
and
do
before
I
come
back.
I
think.
B
All
right
cool,
we
have
five
minutes
just
wanted
to
bring
up
a
couple
of
things,
one
that
morgan,
I
think
you
already
submitted
the
maintainers.
B
Last
week
of
some
sort
to
just
have
the
kubecon
any
planning,
because.
B
A
B
B
B
B
So
again
for
those
of
us
who
heard
about
it
again,
I
at
least
I
was
on
that
thread,
so
I
will
definitely
when
they
have
something
available.
I
will
share
that
with
dgc,
so
but
there's
something
in
the
works.
I
just
wanted
to
let
the
gc
know
what.
B
E
B
Said
they
would
let
us
know
once
they
have
a
draft
of
it.
So
just
a
heads
up
on
that
and
then
you
know
if
there
are
sections
that
we
want
to
add
once
they
have
a
draft,
then
we
can
work
on
it.
You
know
as
a
team,
and
then
I
just
had
a
last
request.
Morgan
is
any
any.
I.