►
From YouTube: 2021-01-14 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
B
C
New
year,
I'm
fine,
you
know
like
just
feels
a
lot
like
happy.
It
feels
like
old
year
as
well.
B
Yes,
sadly,
it
does
feel
more
like
old
year
than
I
would
like
it
to
feel.
I
saw
I
think
it
was
my
mom
actually
who
sent
me
a
little
image.
You
know
that
first
week
of
january
and
she's
like
I
hope,
to
cancel
my
seven
day
free
trial
of
2021
and
return
it
as
it
does
not
appear
to
be
any
better
than
the
2020
model.
B
B
E
B
B
F
E
E
B
F
A
E
G
Yeah,
maybe.
C
I
think,
given
that
this
this
is
recorded
and
so
on
and
so
forth,
I
feel
okay
about
cancelling
that
if
other
people
do
it
sounds
like
most
of
this.
I
have
a
separate
conflict
too,
so
I
can't
go
either.
I.
C
G
Up
there
answer
a
question
and
direct
them
over
to
the
patrick's
meeting,
but
yeah
just
leave
a
note
in
the
agenda.
Please
all
right.
C
D
C
E
Yeah
I
mean
again,
I
think
I
mean
I
tweeted
about
it.
Josh
did
too
so
we've
been
just
you
know,
kind
of
again,
you
guys
are
welcome
to
retweet.
Also
it's
a
good.
It's
going
to
be
a
good
discussion,
so
we
make
good
progress
on
metrics.
C
Well,
should
we
get
going
with
other
stuff,
a
kind
of
an
advertisement
that
I
I
was
making
some
comments
in
the
doc
that
leah
wrote,
which
I
think
to
be.
C
Like
a
yes
and
to
that
for
sure,
it's
not
like,
I,
like
all
the
content
in
there
too,
but
I
was
trying
to
like
you
know,
save
people
work
or
something
and
just
wrote
up
some
sort
of
like
an
alternative
doc.
That's
much
more
focused
on
just
like
marketing
guidelines
in
general.
I
would
just
maybe
ask
people
take
a
look
at
it.
I
link
to
it
in
the
agenda
happy
to
discuss
async.
E
Yeah
ben,
I
saw
some
of
your
comments
pretty
good.
I
mean
I
agree
that
we
could
easily
extend
and
incorporate
some
of
these
cool.
C
The
other
agenda-
and
if
I
put
on
here
just
going
to
order
oh
yeah,
well
whatever
I
did
it
so,
the
tc
is
now
formally
responsible
for
generating
an
answer
to
donations
within
two
weeks.
It's
more
of
an
fyi
just
to
make
sure
everyone
saw
that
and
ironically,
we
actually
got
a
substantial
donation
like
issue
this
morning
from
stanza.
C
So
I
put
a
note
in
there
just
mentioning
the
tcs.
They
see
it,
but
I
think
the
idea
is
not
to
come
to
a
final
decision
but
at
least
to
get
them
like
some
kind
of
response
within
two
weeks,
and
so
I
think
we
should
take
special
care
to
do
that,
since
this
is
like
a
new
and
a
policy
of
ours,.
E
Is
that
on
a
list
ben.
E
C
I
think
I
mean
we
don't
get
these
very
often
but
yeah
I
put
it
in
the
chat.
That's
it.
F
Yeah,
so
our
later,
you
created
this
request
to
create
a
sig
for
lambdas.
E
F
And
there
is
a
discussion
of
appropriate
like
whether
it's
appropriate
who
would
participate.
It's
all
good.
I
just
wanted
to
discuss
how
we
can
formalize
what
is
seek.
What
is
repository,
whether
repository
necessary,
have
to
have
a
sig
whether
there
is
a
working
group,
I
mean
if
sig
means
weekly
meeting
or
if
she
can
meet
like
once
a
year
or
on
demand
this
kind
of
question
that
we
need
to
have
some
separation.
E
Yeah,
I
I
think
sergey
there
were
a
couple
of
at
least
a
couple
of
items.
You
know
in
terms
of
the
lambda
sig
discussion,
and
that
was
again
to
your
point.
You
know
people
were
discussing
whether
you
know
lambda
specifically,
should
be
a
sig
or
a
workshop
and
and
sorry
a
sig
or
a
work
group
right
because
again,
the
idea
of
a
work
group
is
that
it's
focused
on
a
specific
topic.
E
Amongst
you
know,
among
a
larger,
topical
area
right
or
category
like
serverless,
right
or
and
and
so
if
the
sig
was
a
serverless
sig,
then
would
you
lambda
would
be
a
specific
word
group
or
you
could
take
it
as
a
regular,
weekly
sig,
where
different
you
know,
topics
are
discussed
until
there
is
a
need
to
really
spin
off
into
a
detailed,
focused
work
group.
E
But
I
was
I
mean
I
was
thinking
because
of
the
interest
that
you
know:
I've
seen
on
the
ground
from
several
contributors
having
a
very
focused
weekly
discussion,
starting
off
with
lambda,
and
then
there
are
some
of
our
aws
teams,
also
from
the
lambda
teams,
which
are
interested
in
also
participating
so
really
pulling
in
a
much
larger
community
around
that
discussion.
F
Does
this
like
one
of
the
questions
I
had
is
how
many
repositories
that
doesn't
have
six?
Can
we
accommodate
so
right
now
we
have
build
tools.
We
have
parameters
matrix.
That
is
not
officially
repository
yet
because
it
was
hidden,
then
we
will
have
lambda
that
may
or
may
not
have
a
sig
that
missing
regularly,
I'm
afraid
of
having
repositories
with
no
owners.
You
know
like
regular
sick
owners.
E
I
think
I
think
sergey.
There
is
one
repository
right
now
around
lambda,
which
was
done.
You
know
again
the
light
step
team
worked
on
it
and
then
added
it
in
and
and
again
our
interest
is
in
also
having
more
engineers
from
aws
joining
in
to
maintain,
as
well
as
build
out
that
functionality,
so
that
was,
it
is
associated
with
the
repo,
but
again
just
in
the
infancy
of
the
discussions
around
specific
features
and
support
for
serverless.
F
E
I
mean
again,
we
are
definitely
taking
ownership
with
of
this
sig,
specifically
with
you
know,
of
making
sure
that
we
run
it
with
the
weekly
agenda,
and
you
know,
with
the
standards
of
the
hotel
project.
E
In
in
and
you
know
again,
the
light
step
team
is
also
working
together.
So
there's
also
a
lot
of
interest
from
the
microsoft
team,
which
you
know
is
when
working
on.net
and
and
c
plus,
plus,
to
also
participate
on
specific
azure
functions.
Discussions.
G
Yeah
there's
also
a
code
repository
that
people
are
contributing
to
so
that
has
all
the
fixings
of
a
cig,
but
in
general
yeah
I
share
you
guys
concern
repositories
that
don't
have
special
interest
groups
explicitly
assigned
to
them.
E
E
G
E
Agreed
totally
so
I
mean
sega.
We
can
make
that
clear
on
separate
in
the
dark
on
commun
in
one
of
our
community
docks
or
or
just
create
another
one.
H
Yeah,
I'm
not
necessarily
sure
that
it's
a
requirement
that
the
city
like
regularly
need
what
I
think
is
important
is:
is
there
a
list
of
maintainers
right
like?
Is
there
a
list
of
people
who
are
accountable
and
responsible
for
this,
and
is
there
a
mechanism
for
reporting
issues,
even
if
it's
an
async
mechanism
right,
I
don't
want
to
you-
know,
make
everyone
have
a
half
hour
meeting
for
everything
every
week.
That
would
be
ridiculous.
Yeah.
C
I
wonder
if
it
might
make
sense
to
think
of
this
in
terms
of
I'm
sure,
I'm
forgetting
something,
but
the
the
two
big
goals
that
I
think
we
have
for
any
group
of
people
like
collaborating
with
an
open
telemetry
on
code,
are
like
some
kind
of
maintenance,
accountability,
responsibility
thing,
which
is
what
liz
was
referring
to
and
then
also
some
kind
of
like
openness,
transparency,
collaboration
expectation,
which
is
what
you
know,
especially
in
the
early
days
of
these
things.
C
When
we're
laying
the
groundwork,
I
think
the
meetings
and
the
notes
and
the
minutes
and
all
that
that
makes
sense
and
no
but
those
are
really
separate
things
I
mean
the
the
code.
Maintenance
is
like
a
forever
thing
and
then
the
interesting
part
of
the
meetings
and
the
contentious
part
tends
to
be
kind
of
towards
the
early
stages
of
things.
I
don't
think
that
we
should.
I
guess
it's
a
long
way
of
saying.
I
certainly
don't
think
we
should
require
a
weekly
meeting
for
anything,
that's
being
maintained,
maintained,
it's
not
gonna,
be
scalable.
C
C
It's
not
particularly
clear,
like
what
the
different
forms
of
what
the
core
responsibilities
are
and
like
what
mechanisms
we
have
in
place
to
enforce
them,
and
that
might
be
like
the
real
kind
of
ai
here
is
to
just
do
a
path
to
not
to
change
reality,
but
just
to
kind
of
represent
the
current
reality
of
the
project
and
and
make
it
much
more
self-explanatory
in
the
docs.
Does
that
mean,
and
so
I
guess
my
my
statement
about
those
two
like
fundamental
sort
of
responsibilities.
C
That's
I'm
curious.
People
have
thoughts
about
that
and
then,
if
people
are
okay
with
it,
I'm
happy
to
try
and
like
just
take
a
stab
at
documenting
it
more
clearly
about
you
know
what
sigs
are
for
what
repo,
what
what
we
expect
from
any
repo.
That's
in
a
hotel
organization
like
that
sort
of
stuff
would
that
be
helpful.
C
F
Assume
that
sick
means
repository
and
like
it's
yeah,
we
need
to
make
it
I
mean.
Maybe
issue
need
to
be
clearer.
What
what
is
it?
What
the
request
is
because,
like
is
it
reports
the
request
or
like
if
it's
meeting
request,
so
maybe
that
would
be,
I
would
clarify
things.
E
Yeah
I
mean
I,
I
assumed
that
the
sig
was
above
and
beyond
just
a
meeting
request.
It
really
is
an
interest
group
that
is
interested
in
building
out
and
identifying
the
you
know,
improvements
or
additions
that
could
be
made
to
the
spec,
supporting
serverless
environments
and
specifically,
lambda
came
out,
came
up
a
lot
because
that's
the
practical
implementation
and
and
hence
the
request
for
you-
know
a
sig
with
a
request
for
meetings.
I
think
that
your
rights
again,
the
issue
is
not
very
clear,
but
that
was
my
assumption.
C
D
D
These
are
the
specific
you
know
reasons
for
that
for
this
particular
sig
to
exist,
and
then
you
know
an
end
date
if
applicable,
like
I
don't
know
if,
if
a
serverless
work
group
would
spin
up
and
try
to
complete
some
tasks
and
then
disband
after
some
period
of
time,
that
may
not
apply
in
this
specific
case,
but
just
somewhere
where
it
states
these
are
the
responsibilities
of
the
members
of
this
sig
explicitly.
D
Yeah
we
we
have
responsibilities
for
maintainers,
for
when
the
like,
what
you
do
with
the
things
that
you
maintain,
but
for
something
like
this
there's,
no
there's,
no
explicit
list
of
the
things
that,
like
the
sig,
is
responsible
for,
in
particular,
and
with
the
language
sigs,
it's
sort
of
obvious.
You
have
the
the
language
repositories
that
you
maintain,
but
a
prometheus
work
group
might
be
a
good
example
of
a
group
that
doesn't
have
their
own
repository
and
that's
great
from
the
name.
It's
somewhat
obvious
what
they
do,
but
it
might.
E
E
I
agree
daniel
I
mean
clarity
is
always
good,
doesn't
have
to
be
too
detailed,
but
still
you
know
just
outlining
some
of
the
general
charter.
You
know
charter
points
that
are
associated
with
each
sig.
Again,
you
know
under
metrics.
There
are
just
so
many
topics
that
if
you
were
discussing
sampling
or
if
you
were
discussing
prometheus,
specifically
or
or
you
know
even
zipkin
or
jager
support,
those
are,
you
know
very
detailed
topics
in
in
in
themselves
and
the
metrics
general.
E
You
know,
meetings
or
discussions
are
not
adequate
for
being
able
to
deep
dive
into
those
areas
right.
So
I
I
mean
I
can
totally
envision
a
work
group
spinning
up
for
a
particular
area
and
then
just
spinning
down
once
that
you
know,
functionality
has
been
addressed
or
completed.
D
E
So
would
that
be
useful?
I
mean
daniel
you
and
I
could
work
on
that.
Just
put
put
a
you
know,
put
that
together
just
from
what
exists
today,
as
a
you
know,
read
me
on
the
community
repo
and
then
we
can
work
on
it
for
everyone's
review.
E
E
B
E
C
Only
thing
that
sounds
fantastic,
I
sort
of
the
ai
I
took
in
a
sort
of
martyrdom
mission
kind
of
way
was
to
do
basically
the
same
thing.
If
you're
going
to
write
that
dot,
then
I'm
not
going
to
write
I'm
not
going
to
do
the
pr
which
is
great
but.
C
C
I
I
was
just
thrilled.
This
is
a
fantastic,
I'm
genuinely
happy,
so
it
sounds
good,
but
I'm
going
to
remove
I'm
going
to
cross
out
my
ai
and
be
like
I'll
review.
Your
talk.
C
H
It's
already
taken
care
of.
We
don't
need
to
talk
about
it.
I
one
of
the
groups,
one
of
the
one
of
the
reapers,
was
missing
a
cla
text
that
was
already
fixed
before
I
got
to
it,
but
I
found
another
one
that
needed
to
be
fixed
longer
term
should
probably
just
add
more
people
to
the
left
to
the
apples,
but
it
requires
linux
foundation
tickets,
which
are
annoying.
F
E
D
D
E
E
But
again
I
can
just
share
a
link
here.
E
But
you
can
see
that
you
know,
then
those
are
related
to
the
release
code
names,
which
are
then
related
to
what's
rolling
out
as
major
features.
There.
D
D
Is
that
detailed
enough,
or
would
we
want
more
specific?
You
know,
features
expected
or
anything
like
that.
Is
it
okay
to
just
say
we
expect
a
signal
to
be
available
around
this
time
and
supported
for
about
this
long.
E
So
again,
I'll
fix
that
problem.
Sorry,
so
daniel.
Just
to
your
responding,
I
think
there
is
another
level
that
you
could
look
at,
which
is
an
interesting
example
which
is
very
successful
for
the
aws
containers
team,
and
this
is
also
a
public
roadmap
again
just
as
some
open
source
and
some
you
know,
upcoming
features
that
are
that
are
being
outlined,
but
we
could
go
down
to
that
level
if
you
will.
E
That
is
just
an
example
of,
and
you
know,
working
roadmap
feature
by
feature
or
we
could
be
at
a
higher
level
where
we
just
track
milestones
for
the
project.
You
know
the
sdks
and
the
collector.
D
E
C
Yeah,
I
mean
another
way,
I
think
of
it,
so
the
roadmap
is
for
really
like
two
parties,
external
parties
trying
to
understand
when
they
can
expect
things
from
open,
telemetry
and
then,
frankly,
internally,
so
that
we
can
have
some
kind
of
forcing
function
on
quality
time
trade-offs.
I
guess
like
for
life
a
better
word,
I'm
actually
I
mean
you
know,
certainly
biased.
Since
you
know,
we've
been
working
on
inside
the
project,
but
it's
the
second
problem
that
I
feel
like
is
really
like
urgently
needing
some
addressing.
C
If
that
makes
sense
like,
I
would
be
perfectly
happy
with
the
roadmap
with
just
like
the
really
big
moving
parts.
Like
you
know,
api
stability
for
x
is
kind
of
like
relatively
locked
and
then
the
I
think
the
crucial
thing
is
actually
respecting
that
deadline,
so
we've
burned
through
them
many
times
at
this
point
yeah,
but
in
terms
of
that.
E
H
C
This
morning
I
mean:
can
we
solve
that
problem?
I
I
mean
to
be
honest,
like
I
I'd.
Rather,
the
road
map
was
really
really
simple.
It
was
just
like.
Yes,
we
are
actually
going
to
like
reach
api
stability
in
this
language
for
this
part
of
the
api
on
this
date,
and
then
the
critical
part
is
for
the
the
cigs
or
working
groups
or
whatever
for.
B
C
C
D
D
C
Yeah,
so
one
thing
I
would
mention
I
wrote
a
a
metadata
file
that
was
meant
to
be
maybe
hooked
up
into
the
website
like
six
months
ago,
called
maturitymatrix.em
maturitymatrix.yaml
that
was
supposed
to
kind
of
represent
the
semantics,
the
various
things
people
might
care
about.
I'm
I
think
we
should
delete
that
file
because
it
hasn't
been
maintained,
but
it
might
be
fodder,
since
it
did
get
reviewed
for
you
to
think
about
the
kind
of
semantic
structure
of
what
we
should
be
road
mapping.
C
I
guess,
but
I
would
say
like
for
it
seems
like
widely
held
belief
here,
that,
like
the
urgent
problem
here
for
the
roadmap
to
solve,
is
that
we
actually
hit
our
deadlines.
So
maybe
we
can
focus
on
those
first
and
then,
if
we
can
get
to
like
something,
that's
more
publicly
useful.
The
main
request
I've
seen
from
that
site
world
is
just
for
this,
be
done
and
ready
to
use,
and
so
I'd
rather
be
focused
on
solving
that
problem.
Just
personally.
D
E
I
agree
with
ben
because
I
think
that
having
a
general
high
level
milestones
even
is
super
useful
as
long
as
you
can
tag
dates
and
stick
to
them
right.
So
that's
again,
there's
just
so
many
folks.
You
know
who
are
asking
and
trying
to
understand
where
the
project
is
with
different
goal.
Posts
that
we
have
set
is
just
gonna
would
be
easily
solved.
G
Yep,
okay,
I
I
just
gotta
hop
in
and
point
out
it's
one
thing
to
put
a
group
together
to
figure
out
how
to
express
more
clearly
what
the
project
is
doing
and
trying
to
guess
where
it's
going
and
it's
another
thing
to
put
a
group
together
to
try
to
pick
dates
and
get
working
groups
to
stick
to
deliverables
that
second
one
involves
getting
more
integrated
with
the
actual
backlogs
I
mean,
both
of
them
involve
getting
integrated
with
the
backlogs
right.
I
do
want
to
point
out:
it's
it's.
It's
it'll
be
egg
in
our
faces.
G
If
we
put
a
group
together
that
makes
predictions
in
some
amount
of
detail
about
when
things
are
going
to
get
done.
D
Yeah,
I
definitely
see
that
part
of
it
and
you
know
maybe
as
deadlines
approach.
You
start
saying
you
know
if
the
tracing
deadline
is
approaching
and
the
metrics
one
is
not.
Maybe
you
just
say
we're
not
accepting
metrics
changes
right
now.
Sorry
we're
focusing
on
tracing
until
it's
done
yeah.
I
think.
H
It's
also
like
being
really
clear
on:
where
are
the
blockers?
Who
needs
more
help
right,
like
you
know,
and
I
recognize
the
mythical
man
month
or
person
month
of
the
thing,
but
at
the
same
time,
like
you
know,
if
we
are
not
raising
flags
saying
we're
unable
to
meet
dates
in
sig
x,
then
we
need
to
know
yeah.