►
From YouTube: 2021-01-29 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).
C
Good
good,
how
are
you
doing
all
right?
I
just
moved
into
my
new
place
last
week,
so
fantastic
is.
B
C
B
B
C
To
get
your
new
employer
to
hire
you
in
canada.
B
Splunk
yeah,
although
I'm
still
on
u.s
payroll
for
a
while,
which
I'm
not
gonna,
complain
about.
Oh
interesting.
C
Well,
I'm
glad
that
you,
your
immigration
status,
works
with
that.
Well.
D
A
B
E
A
Oh
it'll
work
out.
It's
it's
it's
cool!
Well,
as
you
set
up
your
new
home.
Definitely
you
know:
it'll
be
a
transformation.
Nice
transformation.
F
C
Piano
is
here
that's
kind
of
all
that
matters.
How
many
people
are
waiting
on
a
quorum
on.
We
do
not
have
a
quorum
out.
We
only
had
five
of
us
yeah
hi.
C
D
G
B
Yeah
yeah,
what
the
part
I
find
the
most
surprising
is
that,
like
robin
hood,
had
a
number
of
like
technical
issues
earlier
this
year
when
the
market
was
going
down
and
then
back
up
again
and
yet
the
folks
on
reddit
keep
using
them
even
after
swearing
up
and
down
that
they're
gonna
switch
away,
and
you
watch
this
time.
They're
all
angry
at
robin
hood.
But
in
six
months
there'll
be
some
other
issue
and
they'll
be
angry.
Robin
hood
again,
yeah.
B
Well,
I
mean,
but
so
schwab
and
fidelity
now
and
I
think
ameritrade
like
a
lot
of
them,
are
free.
B
This
one's
not
necessarily
a
technical
issue,
this
one's
quite
likely
their
market
maker,
blocking
them
from
buying
or
selling
shares
in
that
stock.
D
B
D
H
It
seems
very
legally
like
a
legally
risky
move.
You
know,
I
assume
they
hire
a
lot
of
intelligent
lawyers,
but.
B
Yeah,
it
seems
questionable
when
I,
when
I
was
leaving
google
citadel
was
a
company
I
was
interviewing
with
and
had
a
job
offer
from,
and
I'm
kind
of
glad
that
didn't
happen.
C
I'm
glad
that
you
got
to
stay
working
in
this
community
because
we
really
appreciate
you
morning
well.
A
B
B
B
B
A
H
I
have
the
only
topic
and
all
of
the
wrong
windows
open.
Where
am
I
okay
yeah?
So
this
is
just
the
main
branch
renaming
I
volunteered
to
take
this
over
last
week
and
I'm
happy
to
report
that
it
is
more
than
50
of
the
way
done.
Yeah
there's
12
repositories
remaining,
but
of
those
12.
A
lot
of
them
are,
like
you
know,
not
duplicates,
but
it's
like
go
and
go
contrib,
so
they're
maintained
by
the
same
people-
and
I
expect
them
to
go.
H
At
a
similar
time,
so
there's
really
only
like
six
people
to
still
actually
bug
about
this
and
it's
been
moving
through
pretty
quickly.
Actually
bogdan's
been
very
active
on
this
on
all
of
the
tc
maintained,
repos
and
things
like
that.
So
it's
moving
along
and
I
don't
really
have
much
else
to
say
other
than
I'm
glad
we're.
Finally
doing
this,
I've
been
hoping
to
get
this
done
for
a
long
time.
Yay.
B
I
Okay,
I'm
gonna
add
a
topic
really
quickly,
even
though
I'm
gonna
have
to
step
out
in
like
two
minutes
to
get
my
groceries
being
delivered.
Are
we
good
with
us
scheduling
time
with
six
deserve
billy
to
do
the
incubation
vetting
process?
Are
we
all
happy
with
the
doc.
A
I
H
H
I
just
dropped
the
doc
into
the
into
the
doc.
B
Yeah,
no,
I
I
have
my
new
email
address.
Liz
is
going
to
have
me,
go
ahead
and
refresh.
A
Yeah,
I
just
wanted
to
very
quickly
give
an
update
on
kickstarting
the
prometheus.
You
know
metrics
discussions.
We
had
a
very
good.
You
know
start
yesterday
was
which
was
the
first
work
group
meeting
and
we
had
about
23
participants,
so
all
the
core
stakeholders,
both
from
the
prometheus
community,
as
well
as
from
our
maintainers.
You
know,
including
bogdan
and
josh,
and
also
the
whole
google
team,
so
again,
very
good
synergy.
A
We
have
actually
created
a
task
list
of
the
areas
and
the
you
know,
tasks
in
phase
one
that
we
are
going
to
kind
of
itemize
and
listing
them
out
as
issues
today
on
on
the
spec
repo
and
and
then
we
should
be
able
to
kind
of
allocate
ownership
to
work
through
those,
so
good
pro
good
progress.
We
are
kind
of
you
know,
honing
in
on
the
tactical
components.
A
First
and-
and
the
reason
for
that
is
that
you
know
just
to
ensure
that
at
least
a
prometheus
drop-in
server
is
fully
usable
and
compatible
and
then,
of
course,
we're
also
starting
to
look
at.
You
know
the
data
model,
the
and
and
the
other
changes
in
the
really
in
the
you
know,
discovery
and
other.
You
know
larger
areas
that
will
kind
of
affect
the
collector's
architecture
at
large,
so
lots
of
moving
parts,
but
we
are
itemizing
that
as
tasks
and
then,
of
course,
reporting
back
to
the
metrics
thing.
A
So
just
just
wanted
to
make
sure
that
you
guys
have
an
update,
and
you
know
everything
is
published
in
the
in
google
docs,
so
I'll
make
sure
that
the
links
are
available.
Someplace.
Is
there
a
way
that
we
post
links
someplace,
you
know,
which
is
a
centralized
way
of
reporting
on
this
progress
or
how?
How
do
you
do
that
formally.
A
A
Just
you
know,
progress
design,
docs
they'll,
obviously
be
in
their
individual
issues,
but
they're.
Also,
overall,
you
know
design
and
spec
changes
right.
B
Yeah,
so
if
it's.
H
A
Exactly
exactly
so
again,
project
board
is
a
great
suggestion.
I'll
start
with
that,
and
then
you
know,
if
you
need
anything
more,
we
can
definitely
track
it.
Also,
maybe
with
the
tag
on
all
the
issues,
but
just
just
wanted
to
you
know
kind
of
update
you
guys
so
that
again
there's
a
lot
of
energy
around
the
work,
so
good
stuff.
A
Daniel
we
don't
have
a
repo
right
now.
That's
why
I
was
wondering
where
I
should
file
the
issues.
You
know,
because
there
are
some
issues
which
are
collector
related.
You
know,
because
of
the
prometheus
receiver
and
the
exporters,
then
there
are
some
issues
for
the
sdks,
obviously,
and
then
some
for
the
data
model
which
affects
the
spec.
So
what
what
do
you
recommend?
H
I
wonder
if
we
should
create
a
repo
specifically
for
I'm
sorry
for
for
working
group
issues
and
things
like
that
for
not
only
this
working
group
but
for
future
ones
too,
where
each
working
group
is
just
a
folder
inside
some
centralized
repository.
Oh.
A
That's
a
great
idea,
I
think
I
can.
I
can
draft
up
an
issue
and
just
file
that
in
the
community
for
repo
for
request
for
a
repo
that.
H
J
Good
point,
so
we
in
kubernetes
had
a
community
repo
where
all
things
about
community
happen,
but
then
each
sig
ends
up
with
its
own.
Repo
doesn't
have
to
be
that
way,
but
just
a
thing
to
to
see
as
prior
art.
I
love
the
idea
of
community
space
and
collecting
it
all
together.
I
think
that's
makes
way
more
sense.
If
you're
not
going
to
have
a
ton
of
documents
and
code
that
you
need
to
track
together
for
each
sig.
A
F
F
A
And,
and
can
I
also
report
on
the
lambda
sig,
we
also
kicked
off
the
the
lambda
discussions
and
again
have
had
good
good
participation
with
lightstep
maintainers,
google,
mint,
maintainers
and
splunk
as
well
as
aws
participating.
A
You
know
again
both
discussing
lambda,
specific
implementation
because
we're
in
the
process
of
moving
the
code
that
was
built
for
the
python
integration
into
hotel.
So
I've
asked
for
a
repo
for
that
and
also
you
know,
working
forward
on
javascript
and
and
java
implementations
going
forward,
but
nonetheless
I
mean
those
again:
the
cigars
started.
We
got
zoom
bombed
on
the
first
one,
but
the
second
one
was
good
and
again
just
continuing
to
make
progress
in
that
area.
So
just
just
wanted
to
give
you
a
heads
up:
okay,
thanks.
B
All
right,
I
have
the
next
update.
It's
very
quick.
We
talked
about
implementing
passwords
on
the
zoom
meetings
last
week.
That's
now
done.
I
didn't
see
any
complaints
on
gitter
anywhere
so.
F
Thank
you
so.
B
B
I
also
enabled
hd
video,
which
had
been
disabled
for
some
reason.
Don't
really
know
why.
So
that's
on
now.
B
No
well,
I
it
was
even
720p
was
disabled,
like
it
was
only
doing
480p
previously.
So
no,
I
I
don't
know
why
it
was
like
that
anyway,
that's
enabled
and
yeah,
it
appears
have
worked
calendar
links
now.
The
direct
links
are
there
and
I
updated
all
of
the
readmes
that
reference
the
meeting
ids
to
not
embed
the
password
but
to
say
the
password
in
like
in
regular
text.
After
the
meeting
link.
F
If
I,
when
I
press
right
now
in
couple
of
meetings,
is
keep
going
me
to
the
old
meeting
thing
and
asked
me
to
introduce
the
password.
So
that's.
F
H
B
No,
I
kept
the
id's
the
same.
I
just
added.
B
Yeah,
in
fact,
I
don't
know
if
we
can
change
the
ids,
because.
B
Yeah
and
worst
case,
the
other
thing
we
can
do
is
enable
require
authentication,
though
that
would
require
all
attendees
to
create
zoom
accounts,
they're
free,
but
then
I
believe
that
gets
rid
of
most
of
the
bot
issue
and
anyway,
we'll
see
what
happens.
D
Yeah
I
mean
I've
been
sort
of
sitting
on
this
for
a
while,
as
I
was
waiting
for
a
meeting,
we
had
some
extra
time.
I
started
something
I
mean
gosh.
It
must
have
been
like
almost
a
year
ago
at
this
point,
to
try
and
make
well
first
measure
and
then
make
some
improvements
to
the
dna
stuff
as
part
of
the
gc
election.
We
did
get
the
stats
which
I
sent
out
a
while
back.
I
don't
know
if
you
all
saw
that,
but
you
know
tldr
like
surprise.
D
Surprise
like
the
dni
in
hotel
is
really
bad,
so
I
I
know
we
talked
about
this
a
while
back,
but
when
we
were
working
on
the
marketing
kind
of
guidelines
or
whatever
I
was
thinking
like
one
one
thing
we
could
do
is
I
don't
know
what
the
term
would
be,
but
on
hotel.io
right
now,
I
don't
think
that
we
call
out
the
names
of
any
of
the
vendors
who
are
basically
paying
the
salaries
of
some
of
the
contributors.
D
We
could
potentially
do
something
where,
like
I
don't
again,
I'm
not
sure
the
nomenclature
would
be,
but
like
vendors,
that
a
like,
like
comply
with
the
guidelines
and
the
marketing
marketing
guidelines
and
b,
like
I
don't
know,
can
have
people
contributing
the
product
who
are
a
member
of
underrepresented
groups
or
something
can
have
their
name
like
on
the
actual
hotel
website
to
be
clear,
I'm
not
particularly
self-interested
in
this,
and
I
don't
think
lifestyle
actually
meets
both
those
criteria
right
now,
but
but
but
anyway,
I
was
just
I
wanted.
D
I
just
still
would
like
to
have
something
where
we're
providing
some
kind
of
non
trivial
incentive
looks
like
we
put
put
like
I
don't
know.
A
teeth
is
the
wrong
word,
but
I'd
like
there
to
be
a
little
bit
higher
stakes
to
get
vendors
to
think
about
dni
when
they're
staffing
projects,
including
hotel,
and
I
know
that
there's
been
pushback
before
about
like
the
practicalities
of
doing
this,
and
this
is
individuals,
not
vendors
and
so
on,
and
I
respect
that.
D
But
I
also
think
that,
like
since
the
actual
fact
that
most
of
the
core
contributors,
the
project,
are
working
for
vendors,
it's
one
of
the
easier
ways
to
actually
affect
the
dni
of
the
project,
and
I
just
wanted
to
like.
I
guess,
re-erase,
that
topic.
We
don't
need
to
resolve
it
right
now,
but
I
did
want
to
bring
it
up
because
I
would
like
to
do
something.
A
Ben
definitely
I
mean
I
absolutely
support
that.
I
think
you
know
what
has
worked
well
is
again,
and
maybe
we
can
call
this
out.
Just
you
know
in
the
community
repo,
as
in
dni
kind
of
guidelines-
or
you
know
just
read
me-
is
that
first
of
all
encouraging
you
know
all
organizations
actively
to
support
and
consider
dni.
You
know
when
they
are
actually
allocating
project
members
or
you
know
sponsoring
time
for
individual
contributors
and
also
leveraging
the
linux
foundation
dni
initiatives
calling
that
out
as
well.
A
As
you
know,
any
of
the
other
open
source
initiatives
from
a
like,
for
example,
gsoc
has
a
you
know,
has
a
very
specific
initiative.
Women
tech
makers
has
an
initiative
and
and
kind
of
really
you
know
calling
that
out
as
to
how
folks
can
leverage
those
networks
to
be
able
to
participate.
Also
right
outreachy
has
that,
but
really
you
know
providing
some
guidance
actively
as
to
how
that
can
be
done
and
you'd
be
amazed
at
how
much
is
left
out.
You
know
I
mean
we.
A
D
Am
very
supportive
of
anything
along
those
lines,
and
so
this
is
a
yes
end
to
that.
I
I
do
like
all
that
I'm
actually
happy
to
sign
up
to
do
it
if
you
want,
but
I
mean
you
all
want,
but
when
we
talked
to
this
a
while
back
again,
it
was
probably
a
year
ago.
D
It's
also
a
much
higher,
much
harder
thing
to
do,
but
I
think
the
the
scope
of
the
top
I
mean
totally
all
in
on,
like
adding
anything
we
can
to
make
it
easier
to
navigate
from
hotel
to
various
initiatives
that
are
designed
to
improve
dni.
I'm
wondering
if
there's
something
that,
if
there's
a
lever
that
we're
willing
to
paul
to
help
encourage
vendors
to
think
about
dni
as
they
staff
their
own
hotel
stuff.
I
mean
that's,
that's
the
thing.
D
A
I
mean
one
of
the
things
we
can
leverage
where
you
know.
Most
of
the
organizations
that
are
participating
in
hotel
are
also
participating
in
the
to
do
groups,
and
if
we
do
have
a
dni
charter
that
we
can
propose,
or
just
you
know,
some
basic
guidelines
that
the
to
do
group
can
then
share
at
least
that's
one
channel
again.
That
doesn't
mean
we
cannot.
You
know,
access
other
channels.
A
We
should,
but
it's
just
formally
that
we
hold
the
linux
foundation
to
actually
also
help
us
on
some
of
these
driving
some
the
awareness
and
messaging
to
organizations
to
support
this.
D
Yeah
and
what
are
no
one
actually
formally
said,
like
a
good
idea,
a
bad
idea,
not
sure
about
the
idea
of
saying
like
if
you
want
to
be
a
vendor
that
associates
yourself
with
hotel
on
our
marketing
site,
like
on
hotel.io,
that
we're
going
to
require
some
kind
of
something
around
dni
in
terms
of
actual
staffing.
What
do
people
think
about
that?
Is
that
too
aggressive?
Is
that
the
wrong
idea?
Does
that
sound
great?
I'm
just
curious.
B
J
The
data
and
even
and
publishing
it
okay,
yeah
and
and
thanking
our
sponsors
and
companies
who
are
supporting
our
dni
initiative.
So
you
know,
dear
microsoft,
and
you
know
aws
and
you
know
pick
the
group
that
needs
to
be,
but
if
we
do
a
blog
post
on
hey,
we
recognize
here's
the
data,
here's
the
number
crunching
we've
done,
and
we
want
to
thank
these
sponsors.
J
Then
later
we
could
potentially
throw
in
a
phase
two
of
the
and
we
actually,
if
you
want
to
use
our
our
license
in
marketing,
we
actually
want
you
to
be
participating
in
the
project
and
so
on
so
and
with
dni
as
part
of
your
thought
process.
But
I
do
think
that's
more
face
too.
We
need
to
kind
of
stay
here
are
the
marketing
guidelines,
and
then
we
reserve
the
right
to
change
them
because
because
we
do
yeah,
I
agree.
A
D
F
D
I'll,
happily,
post
some
of
this
stuff
there
I
like
the
idea
of
asking,
for
I
mean,
there's
always
some
complexity
right.
It's
like
we
can't
certainly
can't
require
the
contributors
themselves
to
reveal
their
demographic
information
right,
so
there
might
be
some
unknowns
or
nas
or
something
like
that.
I
kind
of
like
the
idea
of
I
mean
that
was
what
you're
getting.
I
think
just
to
make
sure
I
understand
someone
write
it
down
that
we
we
ask.
D
All
vendors,
some
vendors,
I'm
not
sure
which
vendors
to
that
to
provide
demographic
information
about
the
contributors
and
publish
that
somewhere,
is
that
the
suggestion
specifically
like
to
break
it
down
by
a
vendor.
D
Well,
that's
actually,
I
kind
of
I'm
fine
with
that
that
I
mean
I
don't
want
them
to
like.
You
know
be
like
so
upset
that
they're
like
forget
this
project
or
something,
but
I
don't
need
them
to
love
it
like.
I
just
need
to
do
it
so
that
I
mean
that
at
least
that's
my
honest
opinion.
I
just
think
like
I
just
like
I'd
like
to
see
us
do
something
a
little
bit
more
than
just
talk
about
recommending
best
practices.
You
know-
and
I
think
that'll
be
helpful,
so.
J
J
That
says
you
know
we're
so
excited
about
these
partners
and
here's
the
data
we
have
so
far
about
our
dni
in
this
project
and
we're
always
looking
for
new
ways
to
make
this
better
and
we
look
to
our
you
know
contributing
companies.
For
that,
then
maybe
the
next
post
is
now
we've
broken
this
down
by
sponsor-
and
here
is
where
we
are,
and
here
is
the
progress,
because,
ideally
we
will
be
making
progress
against
it.
D
J
D
J
Okay,
well,
I
think
it's
we
can't
limit
them
so
much
as
we
say
what
we
will
offer
them,
which
is
more
more
noise
about
how
awesome
they
are
in
helping
us
with
this
dna
thing,
yep
yep.
A
F
C
And
then
figure
out
where
to
where
to
draw
a
line,
speaking
of
which
apparently
honeycomb
is
not
on
the
list
of
vendors
on
hotel.io,
slash
vendors.
So
we'll
fix
that
and
then
we'll
expect
to
be
asked
about
our
dna
metrics
in
the
next
month
or
two.
So.