►
From YouTube: CHAOSS Evolution Working Group 10-19-21
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
B
B
Yes,
I
think
that's
the
only
pull
request.
We
were
waiting
on
yep.
D
A
quick
question
for
everyone:
after
the
change
from
the
master
to
maine,
did
you
all
have
to
reform
the
repositories?
Because
I
faced
that
issue
before
like
when,
when
we
change,
I
created
a
port
before
the
name
changed
from
master
to
main
that
should
have
been
fine
yeah.
But
now
I
have
I
had
to
delete
my
fork
and
recreate
a
four,
because
it
was
not
picking
the
main.
C
D
The
fork
was
same
like
I
cannot
edit
the
fork,
because
the
fork
was
linking
to
the
master
master
focus
branches
is
still
with
the
chaos
repos.
D
B
D
Cannot
edit
the
fork
on
user
interface,
not
a
branch,
okay,
yeah?
So
so
my
fork
was
pointing
to
the
master
rather
than
the
main
branch.
D
B
Requests
then,
and
then,
if
you're,
if
you're,
if
you
have
a
local
clone
on
your
machine,
you
just
have
to
run
some
code
to
to
update
it.
That's
just
that's:
it's
basically
changing
your
your
branch
domain.
B
So
so
now,
there's
a
command
there's
an
issue
with
code
changes,
so
the
only
the
only
repo
that
had
an
issue
with
that
by
the
way
venad
was
common.
B
I
don't
know
why.
I
don't
know
if
anyone
else
is
having
that
issue.
I,
as
far
as
the
release
goes,
I
looked
and
come
and
was
the
only
one
that
was
having
a
problem.
On
the
other
hand,
comment
appears
to
be
the
only
one
made
in
the
edicts
as
well,
so.
A
Yeah
right
now,
I'm
doing
it
looks
like
there's
some
issues
with
there's
a
conflict.
A
While
we're
doing
that
we're
talking
code
change,
commits
yep,
yeah,
there's
a
type
to
see
what
the
conflict
is,
which
is
not
very
hard,
but
still
it
still
has
to
be
done.
A
A
A
A
B
A
A
A
B
So
I'm
going
to
put
it
back
in
so
I
published
it's
published
as
issues
new
yeah.
So
how.
B
B
A
Probably
before
we
realized
that
he
had
a
naming
convention
yeah,
it
was
certainly
one
of
the
first
metrics
released
ad
reactions.
One
is
one
that
we're
going
to
ponder
over
the
course
of
the
mixed
metrics
development
cycle
yeah.
So
I
had
an
action
item
to
talk
to
remy
and
I
did
and
does
he
seem
interested
yeah,
okay
yeah.
So
I
will
get
him
involved
in
this
and
try
to
talk
to
him
next
monday.
So
we'll
talk
about
it
then,
and
maybe
we're
gonna
become
a
little
meeting
the
next
meeting.
A
Okay,
let's
see.
B
Should
we
create
a
an
issue
for
the
emoji
reactions.
A
So
I
yeah,
I
think
that
would
be
our
convention
right.
So
it's
a
little
bit.
Is
it
a
metrics
release,
question
or
issue,
or
is
it
so
our
interim
release,
or
I
mean
I
guess
the
question
is
we
talked
about
this
at
linkedin
in
one
of
the
community
meetings
and
I
think
we
I
think
we
agreed.
We
could
just
release
stuff
like
this.
At
our
discretion
like
it's.
A
B
A
A
A
E
A
B
A
A
B
A
B
A
B
A
A
F
D
B
F
B
A
B
A
It
looks
like
we
added
dot
m
d
and
we
changed
dashes
to
underscores
yeah.
These
are
not
translation
issues
per
se.
These
are
going
to.
B
G
Anymore,
let's
see
who
did
this
change
request,
though?
I
think
I
did
it.
I
guess
yes,
armstrong
signed
off.
I
blame
armstrong.
D
A
B
We
moved,
we
moved
everything
to
dashes
to
standardize
that
was
part
of
the
yes
standardization,
so
we
got
rid
of
the
underscores
and
and
moved
to
dashes.
So
prior,
I
think
evolution
was
using
underscores
and
maybe
one
other
group
was
using
underscores
and
everyone
else
was
using
dashes.
D
A
B
A
A
B
October
19th,
oh
I
signed
in
I
signed
you
in.
Thank
you.
Thank
you
from
last
week
next
metric
to
work
on
change,
request,
change
request
commits
all
right.
B
Looks
like
we
do
and
then
it
says
we
also
review
release.
Metrics
we've
already
done
that
next
up
work
on
change,
request,
metrics
model,
I'm
assuming
sean
added
that.
B
From
last
week,
continue
work
on
so
from
last
week,
new
metric
on
view,
release
metrics
and
let's,
let's
change
that
to
review
pull
requests
and
choose
which
we
did
or
are
doing.
B
A
A
B
Okay,
I
moved
so
last
from
last
week,
so
okay,
so
we
already
did
right
now
we're
reviewing
prs
and
issues.
So,
let's
maybe
finish
doing
that
and
then
we'll
move
on
to
change.
Request
commits
metric
work
on
change,
request,
metrics
model,
we're
already
done
with
this.
A
I
would
I'm
just
verifying
that
that
does
make
it
work.
A
No,
it
does
not
pr
the
pr
doesn't
work,
it
doesn't
make
it
work.
So
now
I
have
to
figure
out
why
that
is.
A
B
So
I'm
adding
something
to
the
agenda
here.
I
would
propose
that
we
each
meeting
we
go
back
and
we
review
one
metric
that
has
been
released.
Maybe
just
go
through
and
read
it
see
if
anything,
pops
out
of
us
as
being
as
needing
an
edit.
B
And
I
think
that
would
that
would
satisfy
the
we
talked
about
basically
going
through
all
of
the
working
groups
going
through
and
looking
at
their
their
metrics.
So
just
looking
at
it
together
would
I
don't
think
it
would
take
as
long
as
actually
editing
or
creating
a
metric.
B
A
B
B
Should
be
20
2204,
so
the
the
review
period
will
happen
in
march
and
the
review
elect
the
release
will
actually
happen
the
first
week
of
april
with
the
plan
so
the
so
it
would
be
dated
before
which
I
am
having
considerable
trouble.
Changing.
Apparently.
B
Playing
tricks
on
you,
because
I'm
trying
to
fix
this
readme
file
yeah
so
in
our
in
our
new
in
our
new,
the
new
cadence
six
months
apart,
so
it's
2204
and
22
10
will
be
the
next
one.
So
it's
basically
the
release
happens
the
first
week
of
april
and
the
first
week
of
october
tentatively.
If,
if
everything
is
ready
and
I'll
be
honest
with
you,
nothing
is
ever
ready.
B
B
Change
default:
this
is
done,
so
this
is
the
code.
If
you,
this
is
the
code.
You
have
to
run
on
your
local
machine
yeah.
If
you
have
a
local
club
to
make
the
so
you're,
not
so
you're,
not
still.
D
B
And
we
don't
need
a
review
on
this.
However,.
H
B
So
the
there's
a
we
talked
about
doing
this.
I
didn't
realize
that
they
had
finally
implemented
this,
so
we
have
a.
We
actually
have
a
template
for
updating
translations.
However,
the
the
template
is
linked
to
the
the
review
process.
So
if
we
use
that
one
that
looks
like
this
link
to
candidates
release
metric
translations
team
previously
removed
language
label,
this
issue
can
be
closed
when
all
translations
are
done,
labels
are
removed,
change
affected,
work,
group,
metric
area,
focus,
name
yeah.
Let's
use
this
change
okay,
so
this
is
a
name
change,
correct.
F
B
Should
we
use
the
new
one
right,
so
it's
are
the
issues.
B
Issues:
new,
oh
okay,
this
one's
gonna
be
header,
better
edit
evolution
issues,
new
and
what's
the
focus
area
for
that.
A
Area
for
which
one
you
choose
new,
that's
would
be
under
the
co-development
process
or
no
do
we
have
a
second
there's,
an
issue
resolution
focus
area,
so
that
would
seem
to
be
where
that
would
fit.
B
B
B
Oh-
and
this
was
what
was
that
issue
resolution.
B
B
Issue
again,
okay,
this
one
is
metric
name
change.
B
F
Here
yep:
this
is
the
readme
which
sean
is
fixing
right
now,
yeah,
I'm
fixing
it.
But,
oh,
my
goodness
looks
like
he's
not.
B
For
a
moment,
add
new-
I
get
it
here.
What's
this.
B
E
B
Okay,
so
this
these
these
two
up
top
these
two
bullet
points
are
this
is
this:
is
this
actually
would
be
a
metric?
So
this
would
the
the
metric
itself
would
actually
be
labels,
and
then
we
could
add
it
as
a
filter
in
time
to
first
response,
but
this
here,
I
think,
would
be
metric
and
I
and
I'm
not
sure,
I'm
not
sure
that
how
many
labels
or
tags
is
the
right
question.
B
I
think
the
rather
than
a
how
many,
I
think,
a
what
would
be
a
better
question
for
that
metric.
B
What
labels,
what
labels
and
tags
are
attached
to
an
issue
of
pull
request,
so
it
could
include
account,
but
I
think
there
would
need
to
be
a
discussion
of
what
the
tags
are,
because
just
just
saying
there
are
five
five
labels
on
a
pr
doesn't
tell
you
anything
of
value.
H
A
A
All
right
there's
a
new
pull
request
that
should
that
will
fix
the
issue
that
the
one
issue
that
remained
this
so
is
github
link
was
in
there
twice
for
one
of
them,
because
apparently
it
existed
previously
and
then.
B
B
B
B
Okay,
so
we
reviewed
our
yep,
so
we
reviewed
our
prs
and
issues.
G
B
And
I
would
say
the
three
things
that
we
have
on
the
agenda.
Are
these
bottom
three,
so
work
on
the
change
request
commits
metric.
We
could
start
some
work
on
change,
request,
metrics
model,
and
then
we
can.
Maybe
if
we
have
time
we
can
review
a
previously
released
metric.