►
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).
B
C
B
You
could
go
at
it
too,
all
right,
so
here's
our
agenda
today,
so
we
have
kind
of
six
things
on
the
agenda
and
we
can
obviously
add
things.
I
do
want
to
adjourn
just
a
little
bit
early.
I
just
for
chaos.
Con
questions
I
mean
everybody
can
stick
around,
but
at
the
end
I
think
there's
just
a
few
logistics
things.
We
need
to
do
for
chaos.
D
B
So
with
that,
the
first
thing
on
our
list
is
the
metrics
freeze
and
kevin
is
not
here.
But
georg,
can
you
speak
to
this
a
little
bit
because
I
know
you're
always
deeply
involved
in
this
process,
so.
D
D
Here
I'll
put
in
the
chat
and
you
go
through,
there
are
some
metrics
that
are
marked
under
review,
and
this
is
where
we
want
you
to
find
the
issue,
but
there's
also
an
issue
connected
with
it
and
leave
comments.
Feedback
a
simple
head
thumbs
up,
yep,
looks
good,
makes
sense,
or
if
you
have
improvements,
we
want
to
hear
about
them
as
well,
and
the
working
groups
that
develop
the
metrics
then
review
all
of
those
comments
and
feedback
and
make
improvements.
B
All
right,
thank
you,
looks
like
we
have
seven
metrics
under
review
this
time,
which
is
great
on
my
quick
account.
B
A
D
A
To
be
published,
it's
entirely
possible
that
I
miss
remember
or
misunderstood
what
kevin
and
I
talked
about,
but
I
thought
we
put
them
push
them
forward
because
we
weren't
trying
to
hit
the
ossna,
but
maybe
maybe
this
is
maybe
this
is
the
right
date.
So
let's
assume
they're
the
right
dates
unless
kevin
confirms
otherwise.
B
Right
now,
so
they
are
the
mars
project.
The
continuous
metrics
for
the
automated
release
process.
D
D
It
is
something
where,
when
we
get
ready
I'll
se
I'll
share
the
pdf
or
we'll
share
it
shortly,
what
it
looks
like
and
then
we
would
love
some
feedback,
because
we
can
make
changes
to
what
it
looks
like.
We
have
much
more
flexibility
now
under
the
hood,
we're
generating
a
lot
tech
document
and
have
all
freedoms
of
styling
it.
However,
we
want
so
yeah
feedback
on.
That
would
also
be
welcome.
D
This
is
only
automating.
The
pdf
release-
it
does
not
affect
anything
else
with
the
exception
that
now
we
have
some
technical
requirements
for
the
working
groups
with
naming
standards
or
where
images
are
placed,
but
that's
all
described
in
the
metrics
template
and
if
we
find
an
error
running
the
software,
creating
the
pdf
will
definitely
open
a
pr
and
let
you
know.
B
D
D
The
process
is,
we
have
the
metrics
that
are
created
as
markdown
just
like
before
the
naming
convention
is
currently
up
to
date.
So
unless
you
add
anything
else,
we
can
ignore
it.
For
now
we
are-
and
this
is
we
not
just
worked
on
this-
we
are
developing
a
checklist
to
help
with
this
in
the
future,
where
the
different
the
process
itself
is
going
to
be
just
a
checklist
and
we'll
have
a
issue
template
that
the
working
groups
can
use.
D
So
when
a
metric
is
ready,
just
open
an
issue
with
that
issue,
template
and
then
it's
just
check
boxes
to
make
sure
that
all
of
the
requirements
are
being
met,
so
we're
trying
to
simplify
that
and
provide
the
resource
to
the
working
groups,
but
otherwise
right
now.
It's
still
the
same.
Add
the
markdown
file
open
an
issue
and
have
the
review
there
just
like
before.
F
I
have
added
the
link
in
the
chat
to
review
the
checklist
if
anything
like
for
us,
it's
good
to
go.
If
you
feel
anything
you
can
suggest
any
changes.
This
is
like
a
very
handy
thing.
Once
the
working
group
decides
that
metric
is
ready
for
release,
they
can
follow
the
checklist
and
complete
the
process.
F
I
don't
know
whether
markdown
has
this
facility
to
check
mark
that
things
are
done.
I'm
not
sure
on
that.
Okay,
so.
H
Markdown
does
have
that
ability
and
github
has
it,
so
I
can
create
it
in
my
markdown
and
just
you
know
check
it
in,
but
I
wanted
to
call
out
that
this
process
is
fairly
complex,
so
like
as
a
starting
point,
a
checklist
probably
would
be
useful,
but
I'll
bet
that
project
managers
will
find
it
a
little
overwhelming
to
have
this
long
ticket.
But
all
these
items
are
going
to
take
a
while
there's
going
to
be
a
million
comments,
it'll
be
a
mess
by
the
time
they're
done
with
it.
B
Okay,
well
good
thing,
I
think
bernard
was
asking
for
feedback,
so
thank
you.
F
B
F
Yeah,
the
the
only
caveat
in
this
like
reducing
this
is
the
advent
is
the
shortest
version.
What
we
do
in
the
kiosk
while
we
release
the
metric
so
I'll
see
how
I
can
reduce
it,
but
I'll
get
back
next
week.
So
I
I
have
to
review
it
again.
D
So
maybe
we
have
one
checklist
for
for
a
metric
itself
with
the
content
and
technical
requirements
before
it
gets
added,
and
then
we
have
one
checklist
for
the
process,
and
that
is
the
release
feedback
metric.
That
would
be
one
way
we
could
split
it
up.
A
F
A
A
B
Great
thank
you
for
the
feedback
and
stuff
information
yeah,
provided
it
was
like
a
total
loss
of
words,
so
I
I
went
to
stuff.
B
So,
let's
see
moving
on
on
our
list
kind
of
in
the
interest
of
time,
I
moved
one
up
just
because
we're
talking
about
metrics
right
now,
number
eight
on
our
agenda
was:
what's
the
process
of
proposing
changes
to
existing
metrics.
This
isn't
available
in
the
community
handbook.
F
B
Okay,
I
mean
my
first
reaction
to
that
is,
if
it
it's
kind
of
like
making
a
change
to
like
to
certain
documents
like
if
it
doesn't
change
the
nature
of
the
document.
I
I'm
personally
okay
with
just
issuing
a
pull
request
on
that
without
review.
B
Okay,
you
know
like
so,
if
it's,
if
it's
editorial
or
if
it's
adding
a
sentence
that
improves
some
clarity
on
a
topic
I
mean
that's
still
within
the
nature
of
the
metric.
I
think
if
the
metric
is
changing
in
full
okay,
then
it
probably
needs
to
be
back
under
review
and
then
any
change
if
it's
the
first
one,
okay
or
correct
me
if
I'm
wrong,
but
if
there's
just
a
pull
request
issued,
it
would
be
just
picked
up
in
the
next
release
anyway,
without
much
discussion.
F
I
was
like,
if
I
created
a
pull
request.
It
got
merged,
will
just
be
added
as
a
like
review
for
the
next
release
or
something
I
was
not
sure
on
that.
B
B
D
Great
to
have
a
comment
on
the
release
notes
issue
in
each
working
group,
because
this
also
means
the
translators
will
need
to
re-alert
it,
and
so,
if
every
working
group
has
an
issue
for
release
notes
and
any
change
to
existing
metrics,
please
also
just
leave
a
comment
saying
hey.
We
made
a
change.
What
the
change
is
in
detail,
we
can
always
get
from
the
git
log,
but
just
knowing
that
there
was
a
change
would
be
good.
D
B
B
All
right
moving
right
along,
we
are
on
as
this
is
our
monthly
call
we're
on
working
group
updates,
and
so
I
don't
necessarily
need
to
go
working
group
by
working
group.
But
maybe
the
floor
is
open
at
this
point.
So
if
you'd
like
to
speak
up,
that
would
be
great
and
I
can
capture
your
thoughts.
F
Awesome
value
working
group
in
last
two
meetings:
there
was
not
much
attendance,
so
nothing
has
been
done.
The
attendance
is
pretty
low.
B
B
Sorry,
thank
you
for
bringing
that
up.
If,
if
we
need
to
be
more
deliberate
with
improving
attendance,
we
can
do
that
risk
or
evolution
or
common
or.
A
That
risk
has
we're
met,
we
released
one
metric
dependencies
and
it's
upstream
dependencies
and
that's
currently
under
review.
I
may
have
to
had
it-
haven't
added
the
list
because
the
pull
request
didn't
get
merged,
so
it
is
now
and
ready
to
go.
A
A
I
reversed
the
narrative
for
our
two
submissions
and
which
is
why
they
weren't
accepted,
and
so
one
we're
going
to
do
at
a
spokane
and
one
we're
going
to
do
at
ossna
or
I'm
sorry,
the
membership
summit
and
one
of
the
ossma,
and
that
was
a
clerical
error
on
my
clerical
part.
But
we
got
it.
We
gotta
sort
it
out.
D
B
All
right
cool,
could
you
could
you
tell
me
what
minimum
viable
metrics
is
like?
What's
the.
A
So
so,
after
substantial
discussion
about
how
do
we
define
metrics
and
recognition
that
the
boundary
of
what
a
metric
of
what
a
dependency
is
and
how
we
interpret
it
is
the
subject
of
a
great
deal
of
discussion
and
open
source.
Much
like
the
definition
of
a
commit
was
a
mere
five
years
ago,
and
so
that's
that's.
A
lot
of
the
biometrics
are
the
six
or
seven
total
metrics
that
we
have
identified
as
okay.
A
These
are
places
where
we
think
we
can
agree
on
a
common
definition
and
they
are
clearly
bounded
and
they
give
us
a
clear
beachhead
to
start
the
metrics
discussion
to
start
creating
common
definitions
for
things
that
are
related
to
dependencies,
and
I
think
that
from
that
and
sophia,
please
speak
up
as
well,
because
you've
had
a
very
large
role
in
defining
that
with
us.
That's
that's
where
it's
that's,
where
we
start.
J
But
no
yeah,
I
agree
with
what
you
said
sean
I
think,
there's
just
such
a
big
topic
and
we
were
having
trouble
as
a
group
trying
to
figure
out
how
to
tackle
a
huge
topic
so
outside
of
the
first
metrics
definition.
A
lot
of
the
mvp
is
just
trying
to
figure
out
how
to
structure
the
rest
of
the
metrics
that
might
follow
suit
in
a
way
that's
logical
and
thought
through,
just
because
we
are
attempting
not
to
boil
the
ocean
but
boil
like
a
small
pond.
J
Instead,
that
could
be
a
subset
of
the
ocean
and
we
admit
that
it'll
probably
continue
to
grow
the
more
people
that
get
involved.
So
hopefully
it
provides
some
kind
of
starting
point
and
structure
that
can
inform
how
we
approach
the
rest
or
follow-up
metrics.
B
D
D
And
now
we
have
some
improvements
to
make
to
our
recommendations
for
metrics
that
we
are
working
on.
One
of
them
is
to
reduce
the
metrics
and
one
is
to
change
the
presentation
from
a
long
list
in
the
markdown
file
to
maybe
slides.
So
that
is
an
idea
we'll
be
working
on
and
then
also
they
are
now
going
back
to
see
if
they
can
do
the
metrics
for
the
past
events
or
start
collecting
data
to
report
these
metrics
on
future
events.
D
So
that's
that's
exciting
news
and
then
we
are
working
on
marketing
metrics.
We
had
a
podcast
a
while
ago,
where
we
had
collected
a
conversation
or
recorded
a
conversation
with
marketing
experts
from
these
communities
and
so
we're
working
on
the
metrics
there
and
then
most
recently
we
had
some
interest
in.
D
B
Thank
you
and
that's
listening
to
tai,
okay,
it
kind
of
leads
into
there's
a
coordination
for
a
new
working
group
lucas.
You
had
brought
that
together
and
so
I'm
still
staying
with
the
app
ecosystem
stuff,
georg-
and
this
was
about
like
metrics
models
right
about
how
metrics
can
be
brought
together
in
ways
that
are
meaningful
for
people.
So
right
as
opposed
to
just
the
atomic
metric.
I
mean
it's
really
exactly
like
what
you're
talking
about.
A
B
D
We
kind
of
sort
of
do
but
not
like
the
other
working
groups,
so
we
we
do
describe
metrics
that
are
not
represented
in
any
of
the
other
working
groups,
but
we
don't
feel-
or
we
haven't
done,
the
step
of
getting
them
added
to
our
metrics
release
and
formalizing
them.
Okay,
so.
A
D
A
A
B
A
H
Okay,
thank
you.
What,
if
what
if
we
consider
this
as
a
kind
of
a
mandate
for
the
ecosystem
working
group
like
define
it,
I
know
that
that's
like
doing
somebody
else
work.
I
don't
really
mean
to
do
it
that
way,
but
just
it
seems
like
that
might
be
the
natural
breakdown,
and
maybe
the
thing
that
the
that
is
on
the
agenda
right
now
is
to
define
this
task
and
kind
of
figure
out.
What
exactly
the
deliverable
is,
so
that
it's,
you
know
easier
to
do
in
a
practical
way.
D
I
like
the
idea
of
bringing
together
the
work
and
I'm
I'm
happy
to
invite
everyone
who
wants
to
work
on
the
the
metric
models
or
the
design
of
how
do
we
bring
these
together
and
then
we
can
have
the
conversation
in
the
app
ecosystem
working
group
and
because
I'm
not
the
only
person
there
and
then
we
can
see.
A
B
So
even
if
we
spend
some
time
in
the
app
ecosystem
model
and
we're
like
this,
maybe
isn't
we
learned
that
this
quite
isn't
quite
the
place
to
do
the
work
around
say
a
model.
We
at
least
understand
the
process,
like
we've
at
least
learned
for
I.
A
What
they're
doing
there
yeah
I'm
totally
still
like
giving
it
a
shot,
because
I
think
we'd
spend
two
months
defining.
What
is
the
process
for
deciding
what
to
consolidate
and
if
that's
yeah.
I
A
B
B
D
H
Yes,
it's
actually
not
that
horrible.
What
time
is
noon
central
and
it's
it's
like
four
in
the
morning,
I'm
sorry
yeah!
I
got
this
one.
I.
H
A
B
A
It's
not
it's
like:
it's
like
8
a.m.
Central
has
been
a
tolerable
for
everyone,
but
the
question
is
talo.
H
B
A
All
right,
let's,
let's
I
have
a
suggestion.
Yes,
what?
If
what?
If
we
do
have
one
working
group
called
the
and
that's
under
the
app
ecosystem
umbrella
and
we
get
at
least
one
person
who's.
The
current
member
of
the
app
ecosystem
working
group
to
participate
in
an
earlier
version
of
the
asia
pacific
call
make
all
calls
open
but
create
a
separate
call
because
they
are
so
interested
in
this
at
a
time
that
accommodates
their
time
zone
right.
J
A
H
Let
me
throughout
one
other
way
we
might
arrange
this,
which
is,
I
don't
know
if
the
central
time
people
would
be
fine
with
an
8
p.m.
Meeting,
depending
on
your
life
that
could
be
totally
fine
or
totally
unacceptable,
because
8
pm
central
is,
I
think
it's
9
00
a.m.
Beijing,
and
it's
you
know
six
specifics,
oh
no,
but
it's
horrible
and
you're
outside.
A
A
L
Hello,
I
was
not
expecting
to
be
called
out.
Sorry,
it
is.
I
fine
fine
with
me.
I
would
also
like
to
point
out
that
it
is
quite
early
in
the
day
for
me
as
well,
even
though
I
am
in
central,
I
typically
wake
up
quite
a
few
hours
from
now,
but
hello,
I'm
john.
I
work
with
sean
on
auger,
I'm
a
student
at
the
university
of
missouri
currently
and
I'm
happy
to
be
here.
D
A
D
D
B
Last
call
for
working
group
updates
all
right.
Thank
you.
There
is
a
web
content
meeting
that
occurs.
I'm
not
sure
who
put
this
in
here,
but
it
occurs
once
a
month
and
it's
been
attended
pretty
lightly.
B
A
Kev
kevin
and
I
have
yeah-
we
ad
hoc
just
found
time
to
basically
figure
out
what
was
going
to
break
when
we
moved
to
the
website,
and
it
turns
out.
The
only
thing
that
broke
was
a
glitch
with
our
host
printing
provider,
not
wanting
two
domains
with
chaos,
dot
anything
in
them,
but
we
fixed
that
with
a
ticket
in
about
10
minutes,
and
otherwise
it
went
very
smoothly.
B
D
Another
concern
is,
how
do
we
provide
transparency
and
in
what
is
happening
there,
a
swag
channel,
slack
channel
or
mailing
list?
So
that's
the
the
idea
that
kevin
and
I
were
discussing
because
no
one
showed
up
to
the
content
meeting.
I
was
the
only
one
there
this
week
and
then
the
previous
weeks
it
was
only
kevin.
A
A
K
K
B
For
like
a
month
and
chose
to
not
do
this,
and
so
I
just
I
need
to
get
through
the
yeah
go
for
it:
okay,
okay,
so
just
google
summer
code,
sorry
that
was
my
dog
making
a
weird
sneezing
noise.
If
you
heard
that
google
summer
of
code
honestly
from
from
my
perspective,
it's
going
really
really
well
this
summer.
B
So
I
you
know,
I
don't
know
if
people
have
comments,
but
I
just
like
to
say
you
know
well
done
to
the
students
and
we'll
learn
to
the
mentors.
Maybe
I'm
not
seeing
everything,
but
it
looks
really
great
so
far
and
I
do
think
it's
coming
to
an
end
relatively
soon.
Isn't
it
don't
we
end.
B
Great
cool
kind
of
the
last
thing
I
just
we
don't
have
time
today,
but
I
know
that
a
lot
of
people
have
been
working
on
the
ethics
statements.
So
thank
you
for
that
and
I'm
sure
we'll
pick
that
up
next
week
we
had
that
last
week,
so
I'm
doing
some
work
in
and
then
the
the
last
thing
is
with
chaos.
Con
kind
of
slash
events
does
anybody
wanna,
I
know
sean
you
had
mentioned.
You
had
a
panel
accepted,
not
a
kf,
not
a
ks
con
or
no.
I
A
D
Yeah
open
source
summit
north
america
at
the
end
of
september,
I
have
a
session
at
practical,
open
source
from
the
osi
in
mid-september
we
have,
I
don't
know
if
anyone
submitted
to
a
spoken
europe
and
the
finnos
the
open
source
strategy
forum
in
london
in
beginning
of
october,
we
have
all
things
open.
D
B
Thank
you.
Yes,
I
do
plan
on
submitting
to
the
member
summit
as
well,
so
I
think
the
deadline
is
the
eight
just.
So
you
all
know,
I
think
it's
the
end
of
the
week.