►
From YouTube: 2020-11-05 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
C
A
I'm
wearing
my
patriotic
zucchinis
across
america
shirt
from
1988.
A
A
B
B
F
Yeah
proper,
proper
american
ford
ranger,
it's
a
tiny
truck
though
they
don't
make.
It
was
difficult
to
find
a
smaller,
cheaper
truck
everyone's
become
obsessed
with
very
expensive
suv
trucks,
status,
symbol
things
I'm
like
no,
I
need
something
I
can
dump
a
bunch
of
gravel
into
the
back
of
and
like
not
feel
bad
about.
It.
I
F
G
Okay,
so
the
only
topic
for
today
is
the
one
that
I
asked
you
to
differ
from
last
time.
Should
we
start
with
that?
I
think
ted
was
the
one
that
raised
this
issue,
but
were
comments
from
liz
as
well
in
the
email,
and
I
would
like
one
of
you
to
start
a
conversation
and
mention
what
you
think
was
wrong
in
that
conversation.
And
what
do
you
think
we
should
fix
that
problem.
C
Was
that
dev
stats
are
being
misused
for
marketing
purposes?
The
primary
reason
why
devs
deaths
exists
is
to
help
the
cncf
judge
the
health
of
the
community,
in
particular,
as
we've
seen
with
things
like,
you
know
the
code,
you
know
open
source
code,
tober
or
whatever
right
like
where
people
started,
spamming,
repos
with
pull
requests
and
so
forth.
I
think
that
it's
going
to
be
really
really
important
for
us
to.
C
You
know,
use
devstats
as
a
rough
guide
of
you
know
who
are
the
most
active
contributors
to
open
telemetry,
but
I
don't
think
that
it's
appropriate
for
individual
companies
to
say.
Oh,
you
know
we're
the
number
one
contributor.
The
number
two
intruder
right
like
I
feel
like
loose
things
like
you
know,
hey
like
we
have
contributed
like
roughly
a
third
of
both
long-term
things.
Like
you
know,
hey
like
we,
you
know
we're
in
the
top
three
contributors.
That's
fine!
C
Just
like
you
know
the
we
are
number
one
is
going
to
generate
like
this
hamster
wheel
of
people,
spamming
of
fuel,
spamming,
commits
and
bugs.
F
F
D
Yeah
we
actually
reached
out
and
asked
red
hat
to
stop
using
special
interest
group
leadership
as
a
metric
in
their
marketing
marketing
ads
because
in
kubernetes
people
they
were
like
very
their
last
ad
about
this
was
like
you
know.
We
lead
six
of
the
top
10.
You
know
whatever
special
interest
groups,
we
can
help.
You
fix
your
problems
as
opposed.
You
know,
which
implies
a
whole
lot
more
than
everybody
who
works
in
those
groups
can
help.
You
fix
those
problems.
J
Yeah,
that's
totally
fair.
I
guess
for
like
transparency,
like
we
weren't
aware
of
that
blog
post
still
came
out,
but
the
thing
was
like:
that's.
Actually,
we've
been
raining
and
marketing
even
trying
to
before
and
pr,
and
so
we
actually
already
have
a
meeting's
gonna
be
sent
out
for
today
or
tomorrow,
just
to
be
like
hey
guys,
remember.
This
is
not
business
like
this.
C
Much
yeah,
I
I
know
that
none
of
the
folks
on
the
gc
would
have
approved
this
messaging
right.
I
just
wanted
to
make
sure
that
you
have
some
ammunition
when
you
go
to
your
marketing
department
to
say,
like
hey
the
rest
of
I
am
the
rest
of
the
gc
are
concerned
about
this.
Please
stop
so.
A
I
I
totally
agree
with
that.
Listen
and-
and
especially
the
part
about
this,
is
not
a.
This
is
not
a
dig
on
bagner
constance.
I
think,
if
you
as
valuable
allies
in
our
in
our
request
to
address
this
issue,
but
I
think
it
would
be
much
easier
for
you
to
if
open
telemetry
had
a
sign
on
the
wall.
That's
like
we
don't.
I,
like
you,
know
some
sort
of
like
summary
of
like
what
we
think
is
an
appropriate
way
to
market
contributions,
or
something
like
that.
I
don't
know
how
you
all.
C
C
We
filed
a
bug
right,
like
we
filed
a
bug
against
the
devstats
repo
asking
them
like
you
know.
Please
hide
these
statistics,
don't
make
them
like.
You
know
super
commonly
advertised
and
they
refused
right
because
they
were
like
hey.
This
is
useful
for
engaging
community
health,
which
I
understand
right
so
now.
Instead,
we
need
to
go
this
path
of
creating
marketing
guidelines,
which
you
know
I
was
hoping
we
wouldn't
have
to
do
it.
But,
like
you
know
here
we
are,
I
guess,
we're
going
to
have
to
do
it
at
some
point.
H
G
So
let
me
let
me
point
two
things.
First,
I
think
having
us
having
clear
guidelines
is
good.
I
think
removing
these
stats
from
dev
sites
is
not
necessarily
a
good
thing
for
two
reasons:
one
they
are
open,
so
everyone
can
go
and
scrape
github
and
build
these
dashboards
by
themselves.
So
you
don't
have
to
to
rely
on
dev
stats
to
have
this
github
actually
has
insights
already
like
on
the
github
pages.
You
can
see
this,
so
it's
very
hard
to
hide
the
stats
as
long
as
they
exist
and
they
are
public.
G
D
The
other
thing
we
can
do
is
we
can
take
it
from
this
is
what
we're
asking
for
in
open
telemetry.
We
can
socialize
it
with
some
of
the
other
projects
who
have
had
trouble
like
kubernetes
and
others
and
say:
do
you
agree
with
this,
and
then
we
can
bring
it
up
to
the
cncf
and
say:
would
the
cncf
be
willing
to
adopt
this
for
cncf
projects,
because
I
would
love
to
see
vc's
funding
from
open
source
projects
that
have
gotten
into
the
cncf
based
on
that
as
a
presumption
of
a
winner?
D
I'd
like
that
to
stop
too,
like
that
seems
like
a
bad
thing,
but
I
don't
know
quite
how
to
fix
that.
Let's,
let's
focus
on
the
marketing
one,
but
I
think
asking
the
cncf
if
they
would
work
with
us
to
make
global
standards
for
lack
of
a
better
word
would
also
be
helpful,
but
I
think
we
need
to
make
ours
first
and
see
if
it
meshes.
D
I
Yeah,
I
wanted
to
say
that
I
remember
microsoft
was
claiming
leadership
in
open
source
all
the
time,
but
I
couldn't
find
any
articles,
so
it
seems
that
any
time
it's
claimed
it's
some
third
party
doing
that.
So
I
don't
know
whether
microsoft's
ever
done
it
or
is
maybe
techcrunch
always
did
it
so
yeah.
If
you
want,
I
mean
there
always
will
be
workarounds
around
this.
I
Situation
so,
like
some
third
party
may
publish
articles,
saying
like
splunk
is
like
or
like
microsoft
or
whatever,
like
top
contributor
of
the
day,
is
a
top
contributor
and
that
may
be
problematic.
So
our
code
of
contact
will
apply
to
contributors,
but
we
cannot
control
third
party.
D
C
I
B
B
D
G
Mean
a
bunch
of
people
have
their
twitter
account
saying
that
they
are
not
coupled
with
their
employee
and
whatever
and
their
opinions
are
there?
Do
we
do
they
apply
to
them
as
well
or
we.
We
say
that,
oh
no,
because
they
don't
represent
splunk
or
or
other
company,
they
can
do
whatever
they
want.
They
are
third
party
or
whatever
we
call
them.
E
F
B
F
D
If
you
post
it
on
your
twitter
account,
which
has
you
know,
I
know
gazillions
of
followers,
I'm
the
number
one
contributor
to
to
open
telemetry
and
you
know
splunk-
is
riding
on
my
heels
kind
of
thing
or
whatever.
Then
I
think
we
would
go
to
you
and
go
dude
really,
not
that
you
would,
but
but
as
community
member
you
know,
we
would
ask
you
and
we
will
hold
you
accountable
as
peers
for
behaving
in
a
manner
that
hey
stop,
that
in
a
manner
that
did
not
meet
our
our
preferences.
D
But
but
it
is
you
who's
doing
it,
not
the
company.
I
think
we
can
hold
the
company
accountable
more
directly.
G
Okay,
the
other
thing
yeah.
We
had
a
huge
campaign
by
the
way
and
I
think
the
devstats
started
from
from
us
doing
this
huge
campaign
of
being
number
two
project
is
f,
and
should
we
remove
that
whole
campaign?
Should
we
just
because
no.
C
G
C
We're
like
the
the
bit
about
the
community
as
a
whole
being
healthy
right.
I
think
that's
a
very
different
message
than
you
know:
company
extra
company-wise
number
one
contributor
right,
like
you
know
to
talk
about
the
you
know,
but
in
addition
to
talking
about
number
of
raw
number
of
contributions-
and
that
looks
like
like
only
kubernetes,
we
should
say
like
you
know,
we
have
100
something
companies
contributing
right
like.
I
think
that's
the
more
meaningful
statistic
to
me.
C
There's
still
a
death
star
thing
right
like
I'm,
not
I
don't
object
to
dev
stats.
What
I
objected
downstates
for
is
like
when
people
kind
of
you
use
it
to
kind
of
spam,
commits
right
like
or
right
like
it's
a
dev
stats.
It's
a
tool
for
the
stance.
You
have
to
measure
the
health
of
the
community.
It
is
appropriate
for
us
to
talk
about
the
health
of
our
community
in
terms
of
death
stats,
so.
K
C
K
Similarly,
I
do
think
the
dev
stats
are
valuable
in
certain
situations
like
I
know,
there's
been
now
some
marketing
by
app
dynamics
about
their
commitment
to
open
telemetry.
As
far
as
I
know,
app
dynamics
has
zero
involvement
in
open
telemetry
at
all.
I
think
it
is
useful
that
the
dev
stats
reflect
that,
so
that
that
firms
that
claim
that
they're
making
massive
contributions
it
can
be
seen,
but
that
is
not
actually
accurate.
A
We're
going
to
resolve
exactly
what
the
guidelines
should
be,
but
I
think
we
do
need
to
do
that.
So
I
would
suggest
that
maybe
we
find
some
group
of
individuals
from
this
call
and
hopefully
from
the
rest
of
the
community
that
could
like
take
some
kind
of
rough
deadline
to
to
draft
like
some
actual
guidelines.
There's
also
some
interesting
questions
about
whom
they
apply
to,
whether
even
if
it
is
corporations
and
not
people
like
you
know,
we
as
a
gc
are
representing
ourselves,
not
our
employers
and
so
there's
a
lot
of
complexity.
A
I
think
in
like
who
actually
has
to
abide
by
these
roles
and
what
are
the
consequences
and
stuff
like
that.
So
there's
a
lot
to
figure
out.
I
think
we
should
figure
out
like
now
like
who,
from
this
group,
is
actually
responsible
for
coming
up
with
these
guidelines
and
what
their
rough
timeline
is
and
they're
I'm
positive.
The
discussion
will
take
more
than
the
12
minutes.
We
have
so.
H
Yeah,
I
think
the
action
item
would
be
just
to
then
start
a
thread
on
the
community
repo
to
build
these
guidelines
as
a
community
and
and
then
I'm
sure
we
can
get
rough
consensus
to
to
have
a
basic
set
in
place.
A
F
There's
a
there's
a
core
ask
here
for
me,
which
is
it's
true.
There
may
be
like
outsiders
who
come
around
and
try
to
pull
some
stuff
or
something
like
that,
but
but
we're
talking
about
like
the
the
the
tent
poles
of
this
community
right,
like
the
people
and
the
companies
who
are
at
the
core
of
lifting
this
project
up
and
making
it
real
like
we
have
to
be
the
one
setting
the
best
example
for
everyone
else,
and
that's
just
an
important
part.
I
think
of
making
this
this
work
in
the
long
run.
F
Oh
and
I've
got
the
vets
calling
me
on
the
other
line,
so
I
have
to
drop.
But
this
is
a
great
discussion.
I'm
happy
to
follow
up
and
I'll
follow
up
also
with
the
cncf
and
certification,
trademarks
and
compliance
programs
and
how
they
could
help
with
this
as
well.
H
H
Can
do
that?
Do
you
want
me
to
thank
you,
ali.
D
H
D
Thank
you.
So
are
we
good
to
move
on
to
the
next
question
which
I
had
thrown
into
email,
which
it
isn't
on
the
agenda
at
the
moment?
But
and
I
don't
think
it's
a
long
conversation
I
just
wanted
to.
D
I
got
reached
a
lolita
I
got
reached
out
to
by
mark
atwood
from
aws
as
well,
and
he
just
said:
hey
has
there,
have
there
been
any
rumblings
in
the
open,
telemetry
community
about
our
release
of
a
distribution,
and
so
I
wanted
us
to
take
a
moment
without
alolita
here
to
see
if
there
was
any
feedback
in
that
for
us,
because
this
was
the
first
distribution
we've
seen
come
out
right
because.
A
That's
accurate,
although
I
I
think
that
amazon
market
cap
difference
with
lights,
that
made
it
a
much
more
interesting
thing
to
the
world.
I
think
it
was
the
first
one
to
get
a
lot
of
outside
attention,
which
I
totally
appreciate.
Actually,
but
but
that's
the
this
question
stands
I
mean
it
definitely
got
a
lot
of
attention.
G
So
I
can
tell
you
a
couple
of
reasons
why
we
did
it
for
for
good
or
bad,
so
we
want
to
have
to
offer
our
customers
specific
support,
timelines
and
stuff,
and
there
may
be
some
times
where
we
cannot
push
a
fix
upstream
as
soon
as
the
contract
says
to
us,
so
we
may
have
to
maybe
even
fork
for
a
small
period
of
time,
the
code
specif
parts
of
the
code
and
and
do
the
fix
for
our
customers.
So
what
we
want
to
achieve
there
is
mostly
to
be
the
the
the
the
customer
support
things.
G
So
so,
in
that
regard,
what
we
did
was
actually
we
did
not
fork
anything.
We
just
create
our
own
main
function
for
the
collector
put
all
the
things
from
upstream
into
one
place
in
that
with
that
in
mind
that
if
there
is
a
bug
in
any
of
this
component-
and
we
cannot
push
a
fix
upstream,
we
will
fork
immediately.
The
component
fix
that
and
then
push
upstream
and
then
remove
the
four
anyway.
This
was
our
our
reasoning
for
doing
a
distribution,
and
I
would
like
to
hear
maybe
the
the
problems
for
aws.
H
I
mean
we
haven't
again.
I
can
just
give
you
an
update
on
the
aws
distro.
So
far
we
have
not
heard
anything
negative.
Our
objective
really
was
to
re-amplify
the
the
that
open
telemetry
as
a
project
is
the
core
and
and
what
we
are
doing
is
providing
support
around
the
integrations.
H
K
D
K
K
Yes,
but
it's
not
one
that
we're
so
we
we
have
a
bundled
version
of
the
collector,
but
it's
one
that
we're
only
embedding
in
our
own
compute
environments.
It's
not
one
we're
going
to
be
actively
sending
customers
to
so
our
documentation
is
going
to
tell
customers
like.
Oh,
if
you
want
to
set
up
open
source
yourself,
go
download
the
open
source
components
if
you're
running
in
kubernetes
on
google
cloud,
the
collector's
already
there
like
you,
don't
have
to
do
anything,
it's
just
there,
and
so
the
version
art
distribution
is
the
one.
That's
just
there.
C
C
K
K
K
Exactly
yeah,
we
don't
expect
our
customers
to
be
downloading
that
source
or
compiling
it
or
downloading
artifacts
from
it.
It's
just
it's
the
fork
that
the
fork
it's
the
distribution
that
we're
just
embedding
in
certain
compute
environments.
But
again
our
documentation
is
going
to
tell
people
like
if
they're,
like.
Oh
I'm,
running
my
own
vm
and
want
to
use
the
open
source
collector,
we're
going
to
say,
like
okay,
go
down
download
the
core
open
source
version.
A
Yeah,
my
first
of
all,
I
was
really
happy
to
see
the
amazon
announcement.
Just
if
nothing
else,
I
mean
I
kind
of
it's
sort
of
obvious
people
on
the
inside
of
the
project,
given
the
amount
of
work
that
amazon
is
putting
into
open
telemetry,
but
you
know
with
open,
open
tracing
and
open
census.
There
is
always
some
question
around
what
was
going
to
happen
with
amazon,
because
x-ray
had
its
own.
A
You
know,
I
mean
they
were
open,
but
they
were
amazon,
specific
standards
and
so
on
so
forth,
and
it's
just
like
even
six
months
ago,
it
wasn't
clear
how
things
were
going
to
shake
out
and
just
great
to
be
like.
Yes,
this
is
actually
going
to
like
all
the
major
cloud
providers
have
bought
into.
This
is
great
right.
A
I
I've
got
no
issue
with
the
announcement
per
se,
but
I
I
do
think
like
the
project
in
general
is
so
muddy
right
now
as
to
what
the
scope
of
the
project
is,
and
I
don't
know
what
the
announcement
could
necessarily
have
done
to
clarify
that,
while
still
being
like
concise
but
but
it's
open,
telemetry
isn't
like
a
single
thing
and
with
the
the
amount
of
scope,
especially
including
both
the
sdks
and
the
apis
and
the
collectors,
and
even
more
so,
for
an
organization
like
amazon,
where
you're
not
just
a
vendor,
you're
a
platform
and
a
vendor.
A
And
so
it's
like
I'm
worried
that
we're
going
to
like
glon
everything
together,
which
is
a
natural
thing
for
someone
not
familiar
with
open,
telemetry
and
and
and
people.
One
of
the
goals
in
my
mind
for
the
project
is
to
be
modular
and
I'm
a
little
bit
concerned.
A
That
distributions
are
the
way
that
people
consume
it
that
it's
going
to
become
a
pretty
heavy
dependency
like
if
you
take
open
to
limit
you're
actually
like
if
you
use
the
distribution
for
convenience,
you're,
actually
bringing
in
like
a
huge
amount
of
functionality
that
you
kind
of
get
tightly
coupled,
which
could
become
an
issue
for
some
of
the
initial
design
goals,
the
project
around
being
lightweight.
So
I've
got
no
issue
with
the
distribution.
It's
more
of
an
issue
for,
like
the
mission
vision
stuff
that
we're
doing
to
really
clarify
our
stance
on
being
modular.
A
I
think
if
the
project
gets
too
heavy,
it's
going
to
be
harder
to
embed
in
certain
scenarios,
so
no
issue
with
announcement,
but
the
distributions
in
general,
even
though
whatsapp's
obviously
doing
it
too
right,
but
it's
just
like
it
does
make
me
a
little
nervous
around
the
modularity
goal
for
the
product.
I.
H
Mean
the
thing
has
been
that
you
bring
up
a
very
good
point
right
because
even
in
the
collector
world,
specifically
right
now,
it
would
and-
and
we
are
kind
of
you
know-
seeing
the
evolution
of
the
project-
also
where
there
will
be
a
lot
more
exporters
that
will
get
added
and
there
will
be
a
lot
more
receivers
that
will
get
added
in
and
and
at
that
point
you
know,
performance
or
footprint
or
all
these
you
know
aspects
will
become
equally
important
to
the
project
as
they
are
to
the
distributions
downstream,
and
we
do
need
to
figure
out.
H
G
That
should
be
the
goal
and
stuff
I
I
do
think
that
we
should
talk
a
bit
with
kubernetes
community
about
this.
They
have
a
large
experience
and
kubernetes
is
mostly
used
via
distributions
gpe,
you
name
it
all.
The
the
vendors
or
all
the
things
are
providing
distributions
of
the
kubernetes,
and
I
think
we
should
talk
a
bit
with
them
and
see.
How
did
they
manage
to
to
to
do
this
and
what?
What
is
the
story
behind
that?
And
maybe
we
learn
from
that?
Maybe
we
don't
repeat
some
of
the
mistakes.
D
I
agree
totally
so
bogdan
ted
is
reaching
out
to
the
cncf
to
talk
about
how
they
do
conformance
programs.
I
worked
with
william
dennis
and
I
bet
morgan
can
actually
pull
william
dennis
in.
If
he's
still
at
google,
to
talk
to
us
about
yeah.
D
K
Comes
from
the
scala
community
as
well,
where
they've
had
to
do
this
he's
already
they're,
all
in
contact
with
ted
already.
D
Awesome
yeah
and
if
we,
if
we
get
ted
and
william
to
potential
and
whomever
ted
brings
in
from
the
cncf
to
come,
talk
to
us
about
pros
and
cons,
I
think
we
can
make
decisions
pretty
clearly
from
that
and
then
figure
out
what
the
work
is.
I
mostly
wanted
to
make
sure
that
nobody,
you
know
like
with
no
rules,
was
have
these.
Have
these
different
distributions
not
been
okay
so
far,
and
I
think
the
answer
is
yes,
we
just
need
to
figure
it
out
longer
going
forward
or
bigger
going
forward.
Yes,
absolutely
and.
H
Just
to
add
to
that
again
conformance
and
testing
and
certification
obviously,
is
a
big
thing
for
distributions,
and
we
have
been
looking
at.
You
know
how
to
have
a
general
purpose
set
of
guidelines
as
well
as
test
harnesses,
which
we
can
then
contribute
back
to
the
project
right.
So
again,
I
do
see
that
much
of
the
heavy
lifting
that
we're
doing
comes
back
completely
to
the
project.
G
G
For
example,
I
think
I
think
the
most
the
most
distributions
will
be
on
two
things
will
be
a
lot
of
distributions
on
the
collector
and
a
lot
of
what
lifestep
calls
starters
on
the
sdks,
which
mostly
will
be
some
configure
embedded
configuration
that
is
different
than
the
default
configuration
that
open
telemetry
produces
or
or
distributes.