►
From YouTube: CHAOSS Evolution Working Group 12-2-20
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
A
And
I'll
I'll
share
the
minutes
with
everyone.
Once
I
find
that
window.
A
B
A
A
C
A
B
A
Yes,
that's
what
it
was
yeah,
so
let
me
bring
up
the
spreadsheet.
B
It
it's
it's
online
28,
it's
six.
A
B
A
Sharing
the
one
window,
because
my
experience
is
it's:
it
lets
people
with
smaller
monitors,
see
things
better
and
don't
generally
leave
the
browser,
whereas
when
we're
doing
like
auger
meetings,
we're
often
going
back
and
forth
in
the
browser
and
other
things
right,
so
we
did.
We
just
widen
this
a
little
bit,
so
we
can
see
the
comments,
and
so
this
is
one
one
that
we
were
working
on.
A
B
A
A
So
the
the
way
that
we
classified
things
in
the
last
meeting
is,
first
of
all,
I
had
a
misunderstanding
of
what
the
difference
between
considering
and
in
progress
were,
and
so
we
had
so
the
in-progress
ones
are
the
ones
that
were
targeting
for
the
next
release,
which
is
one
of
the
things
we
got
clarity
with
each
other
on
during
the
last
meeting.
Am
I
recalling
it
correctly?
A
A
Yes,
so
maybe.
A
And
maybe
with
this
number
of
things,
we
want
to
establish
a
sort
of
a
person
who
might
be
the
driver
of
the
development,
not
the
only
person
contributing,
but
the
person
who
sort
of
leads
the
charge.
A
For
well
so
I
had,
I
was
mentioning
that
we
have
identified
a
number
of
metrics
that
we
want
to
release
and
with
with
that
in
mind,
it
might
be
helpful
if,
if
we
gave
action
items
to
sort
of
lead
different,
no
different
of
these
metrics
or
we
just
iterate,
we
could
just
work
through
them.
We
have
probably
three
meetings,
including
this
one
between
now
and
when
the
metrics
would
be
released.
So
I
don't
think
we'll
work
through
all
of
these
in
the
meeting.
C
A
It
works
really
really
well
so
to
have
everyone
work
on
their
own
individual
metric
during
the
meeting
the
earlier
or
where
we
collectively
work
on
one
yeah
with
branch
lifecycle,
we
spent
a
good
deal
of
time
sort
of
sorting
out
what
that
means,
and
I
don't
know
if
it
might
make
sense
to
accept
some
of
these
changes
at
this
point.
So
it's
more
readable
and
then
edit
from
here,
probably
that's.
E
B
B
A
A
A
And
we
settled
on
a
question:
are
we
we
discussed
this
as
the
main
question?
This
is
a
more
general
question
that
space
fish,
which
is
me,
oh
okay,
I
don't
know
who
are
you
suggesting?
We
replaced
the
question
with
this.
That
is.
B
Yeah,
I
just
it
was
under
the
question,
so
I
didn't
know
if
that
was
an
alternate
one,
that
we
wanted
to
consider
that
somebody
put
there
or
if
it
was
used
to
be
there
and
we
just
didn't
delete
it
in
case
we
wanted
to
come
back
to
it.
A
So
the
the
discussion
yeah,
that
is
so
the
the
reason
the
persist
thing,
which
is
a
more
complex
question,
is
what
I
think
king
was
getting
at,
because
sometimes
projects
create
branches,
often
projects
create
branches
for
a
feature
and
then
the
branches
destroyed.
A
Sometimes,
projects
maintain
a
number
of
branches
that
they
continue
to
work
on
and
don't
destroy.
Many
the
the
rate
of
creation,
destruction
etc
is
is
the
metric,
so
this
would
be
included
in
the
metric.
The
question
is:
does
it
need
to
be
included
in
the
question,
or
could
the
question
be
kept
more
simple
with
something
like
this,
and
is
that
going
to
be
easier
for
someone
to
consume
and
maybe
matt
and
elizabeth?
A
You
have
a
broader
experience,
knowing
what
questions,
what
kind,
what
what
sort
of
question
is
going
to
help
people
know
what
we're
doing
here
without
overwhelming
them
with
like
this
question
up
here,
has
a
lot
of
nuanced
jargon
in
it.
So
I
don't
know
if
it's
more
or
less
useful
than
the
other
option
we
have
on
the
table.
C
D
C
C
A
B
Well,
I
there
is
something
that
I
liked
about
the
first
question
versus
this
one
with
using
the
word
manage.
I,
this
question
is
specifically
about
life
cycles
and
about
when
they're
created
and
destroyed,
and
the
conditions
surrounding
that
to
me,
management
is
more
than
just
that.
It's
like
how
do
you
manage
merges
between
branches
who
gets
to
work
on
what
like
assigning
it?
I
think
the
part
from
the
previous
question
about
and
to
what
extent
do
they
persist,
was
the
key
part
of
that
question
yeah.
I
like
this
better.
B
C
A
And
I
think
I
think,
actually
bernard
did
a
good
deal
of
editing
on
the
description
to
bring
it
on.
So
do
we
want
to
spend
10
minutes
editing
and
reviewing
this
for
where
it's
at
right
now.
G
G
A
Did
you
I
can't
remember
you,
maybe
there
would
those
be
links
that
you
would
add
on
your
vote.
Elizabeth
gave
us
some
really
outstanding
links
about
branching
strategies
in
the
last
meeting.
Is
this
what
what
you
mean?
These
kinds
are
you're
saying:
there's
something
from
microsoft.
G
That
was
a
research
paper
by
thomas
zimmerman.
I
think
I
shared
it
sometime,
but
I
don't
know
he
did
it
with
in
collaboration
with
prince
university,
and
I
think
the
practice
goes.
Maybe
if
you
click
on
the
the
the
azure
thing
might
be
it's
the
same
document
I
don't
know,
but
that
one
is
really
a
strong
finding
from
microsoft
about
this
branching.
G
Okay,
this
is
now
the
practice
and
this
practice
is
based
on
the
under
on
the
finding
yeah.
So
this
this
link
reflects
the
microsoft
yeah,
the
studies
that
they
did
at
microsoft.
It's
by
thomas
zimmerman
it's
one
of
the
pioneers
of
microsoft,
research,
yeah
and
it
doesn't.
I
don't
see
his
byline,
so
there's
a
separate
link
from
thomas
zimmerman
yeah,
because
now
the
the
key
is
they
try
to
really
focus
more
on
collaboration
on.
Why
sometimes
future
branching
is
not
really
a
good
idea.
G
G
A
A
I
think
it's,
including
the
reference
that
you
mentioned,
is
important
to
help
people
decide
what
is
optimal
in
their
context,
but
we
don't
want
the
metric
definition
to
make
a
choice
about
what's
better,
if
that
makes
sense,
like
that's
a
kind
of
a
value
that
we've
maintained
through
chaos,
that
we
want
to
define
what
we're
measuring
and
what
organizations
apply
their
context
to
whatever
value
judgments
they
want
to
make
pertaining
to
those
to
the
resulting
metrics.
Does
that
didn't
know
what
I'm
saying.
A
No
problem,
so
all
I
said
was
that
we
don't
want
to
like.
I,
I
like
the
idea
of
adding
additional
references
that
have
different
perspectives
on
best
practice
branching
strategies.
A
Okay,
just
if
we
kept
that
in
mind
as
we
edited
this
and.
C
G
Reference
something
like
that,
then
at
least
we
acknowledge
that
we
are
not
ignorant
of
yeah.
It's
just
that.
We
don't
want
to
sound
opinionated
on
how
people
should
handle
things,
because
when
things
is
based
on
empirical
finding,
we
cannot
also
just
neglect,
but
we
can
we
just
bring
things
out
of
the
light
and
say:
okay.
This
is
that's
what
this
is.
What
is
cooking
now?
How
do
we
walk
around
those
yep
armstrong?
Can
you
drop
that
link
in
the
chat?
Yes,
I'm
in
the.
C
G
C
C
A
I
I
started
editing
while,
while
armstrong
looked
for
the
link,
I
think
I
think
we
want
to
unless
there's
objection
maybe
give
this
10
minutes
of
editing,
and
I
started
with
the
description
because
I
wanted
to
for
myself
understand
if
the
thing
the
parts
of
the
discussion
that
we
just
had
are
reflected.
C
A
Yeah,
oh
okay.
I
didn't
start
the
recording.
D
A
I
made
a
number
of
changes
in
description
and
objectives
that
I
think
clarify
the
purpose
of
the
metric
and
make
some
of
the
things
that
we're
trying
to
say
a
little
bit
more
clear,
but
I
may
of
course,
chef
changed
the
meaning
in
some
cases,
so
I'm
interested
in
feedback
on
that,
as
well
as
on
changes
that
were
made
to
the
objectives,
the
aggregators
and
the
filters
and
there's
some
comments
down
below
to
address.
As.
B
A
B
If
I
did
I've
forgotten
it's
all
right,
it's
not
that
bad!
I
was
just
curious
if
anybody
knew
one,
I
said
it.
A
Carter,
if
you
can,
if
anybody
can
find
that
we
can
do
it.
D
A
D
B
G
G
G
A
C
A
C
C
A
A
B
That's
usually
where
we
put
like
the
period
of
time
for
this
one,
I
think.
That's
probably
I
don't
want
to
say
probably
the
only
parameter,
I'm
sure
there's
more.
A
A
So
I
might
make
each
of
those
a
few
of
those
parameters
carter.
I
think,
like
a
period
of
time,
period
of
time
and
like
there's
the
what
dates
do
you
want
to
look
at
this
information
for,
but
there's
also
the
at
what
level
of
aggregation
do
you
want
to
see
the
data
the
which
I
think
we
call
periodicity
like
that's
our
week
month
year,
kind
of
aggregation.
B
B
B
B
So
for
the
for
the
aggregators-
maybe
this
is
somewhere
else,
but
how
is
there
a
language
difference
in
how
we
want
to
refer
to
branches
that
have
been
opened?
There's
code
pushed
to
them,
but
they
don't
get
merged
anywhere
and
then
get
deleted
versus
branches
that
have
code
pushed
to
them,
get
merged
and
then
get
deleted
kind
of
like
closing
versus
merging
a
pull
request.
I
think,
though,.
A
B
A
Think
I
think
the
pull
request
is
the
action
that
prompts
another
action
related
to
the
branch,
whether
it's
the
deletion
of
the
branch
or
or
the
persistence
of
the
branch
right
so
like
once,
a
pull
request
against
the
branch
is
processed
it.
It
may
be
deleted
after
one
or
more
poll
requests
or
it
may
never
be
deleted.
A
B
A
A
And
if
you
push,
if
you
ultimately
push
the
results
up
to
git
hub
or
git
lab
those
local
actions
are
going
to
appear
they're,
just
not
visible
until
the
until
your
work
locally
is
pushed
up
to
the
platform
for
two
minutes
I'll.
Just
I'll
note
some.
Maybe
we
can
take
this
and
use
just
the
last
two
minutes
to
see.
If
there
are
people
wanting
to.
A
Sorry,
can
you
say
that
again
sean
so
so
back
on
the
back
on
the
agenda.
These
are
the
these
are
the
metrics
that
we
want
to
work
on
for
the
next
release
and
I
think
it
would
be
helpful
if
one
of
us
looked
at
each
of
them
prior
to
the
next
meeting
and
was
able
to
provide
at
least
a
short
report
on
its
status
and
remaining
work
required
and
if
time
permits,
maybe
do
some
work
on
them.
A
A
And
pull
request
comments
exists
up
here,
and
acceptance
ratio
does
as
well
so
I'll,
bold
them
up
here
and
I'll.
Take
the
ai
out
down
here
so
that
we
don't
double
up.
B
E
B
A
Yeah-
and
I
think
we
I
think
we
do
want
to
we've-
done
a
lot
of
work
under
this
branch
life
cycle
and
I
think
we
wanna,
I
think
I
think
I
think
it's
just
flat
out
in
progress.
A
There's
no
question
100
yeah,
so
I'm
just
gonna
add
that
it
may
in
fact
be
the
one
that's
most
advanced
at
this
point.
C
A
I
think
for
me,
the
minimum
I'm
gonna
do
is
at
least
I'm
gonna
look
at
each
of
these
and
have
a
brief
statement
about
its
status.
G
A
A
As
I'm
gonna
be
able
to
take
on
and
again
it's
just,
it's
not
an
expectation
necessarily
you
do
any
work
on
them
on
the
metric,
but
at
least
review
its
status
and
be
able
to
just
report
briefly
to
the
group
the
scale
of
work
involved.
For
example,
some
of
these
that
we
say
are
in
progress,
may
have
templates
and
little
else.
So
I
mean
with
with
that
in
mind.
A
A
Thank
you,
and
this
is
the
end
of
the
evolution
meeting
on
december,
2nd
2020.