►
From YouTube: CHAOSS Weekly Community Call 2-2-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).
B
B
Hopefully
we'll
have
time,
but
if
not,
we
know
we
can
power
through
and
speed
speed
update
like
two
minutes
each
so
we're
good.
We
do
have
a
lot
on
the
agenda
today
because
there's
a
lot
going
on,
so
let's
hop
right
to
it.
The
first
one.
The
first
thing
I
wanted
to
just
mention
was:
I
just
want
to
remind
everyone
that,
as
you
see,
we
have
a
mix
of
people
with
cameras
on
and
cameras
off,
and
that
is
absolutely
fine.
Like
do
not
feel
obligated
to
turn
your
camera
on
at
any
time.
B
We
do
not
care,
we
still
love
you.
We
still
want
you
to
be
a
part
of
things.
So
absolutely
totally.
Fine
just
wanted
to
reiterate
that,
for
anyone
who
was
maybe
feeling
like
they
had
to
have
it
on
or
whatever
like
just
don't
worry
about
it,
it's
not
that
kind
of
meeting.
So
it's
totally
up
to
you.
B
Second,
one
is:
we
have
now
officially
frozen
the
metrics,
so
we
are
starting
our
public
community
review
period
in
the
next
few
days.
I
would
imagine
once
we
because
kevin
what
what
has
to
happen
is
kevin
has
to
get
him
all
onto
the
website,
which
I
believe
that
he's
done,
but
we
need
to
just
make
sure
of
that
before
we
open
the
review
period
publicly.
So
if
you
are
in
a
working
group
and
you're
working
on
metrics,
that's
just
going
to
be
on
hold
for
a
little
bit
for
a
little
bit.
B
B
So
that's
why
we
freeze
the
metrics
right
now
and
then,
in
march
after
we
start
this
30
day
review,
we'll
have
our
official
release
in
march
and
then
we
can
start
all
over
again
with
brand
new
metrics
or
revising
something
we've
we've
brought
up
from
the
past,
but
that
that
30-day
public
review
is
where
we
invite
members
of
the
chaos
community
or
the
general
public
who
happens
to
have
an
interest
in
what
we're
doing
to
review.
B
B
So
does
anybody
have
I
see,
people
are
adding.
Georg,
is
adding
some
information
there.
The
link
for
anyone
who's
not
looking
at
the
minutes,
is
chaos.community
metrics
and
they
will
have
a
little
tag
on
there,
a
little
red
label
that
says
under
review.
I
believe
so
there
we
go.
C
The
only
comment
is
that
you
can
jump
in
and
provide
feedback,
because
we
have
the
continuous
contribution
process
where
we
accept
feedback
the
entire
time
from
when
we
put
it
on
the
website.
Two
minutes
going
to
be
released
and
I
believe
kevin
finished,
putting
all
of
the
metrics
onto
the
website
so
feel
free
to
go
there.
The
issues
where
we
are
asking
for
feedback
on
are
linked
on
this
page,
so
yeah
just
go
ahead.
Look
through
the
metrics
that
have
the
attack
under
review.
D
D
B
We'll
just
whip
that
out
real
quick.
It's
no
problem!
I
was
just
going
to
say:
if
we're
keeping
track
somewhere
of
like
a
master
to-do
list
or
like
a
main
to-do
list
that
you
know
we
kind
of
work
from
that
would
be
on.
It
is
to
kind
of
solve
this
problem
of.
How
do
we
make
these
these
metrics
a
little
bit
easier
to
navigate
for
people
who
are
looking
and
we
do.
We
have
had
some
ideas.
B
What
would
you
all
recommend
as
a
best
venue
for
that
discussion?
Would
it
be
the
web
content
meeting,
or
would
it
be
this
meeting
or.
B
Okay,
so
for
anyone
who's
interested
in
being
a
part
of
that
who
has
experience
or
ideas
on
data
presentation
or
how
we
can
make
these
easy
to
to
navigate
and
to
search
through
and
to
find
what
you
know,
a
newcomer
or
an
outsider
might
be
looking
for
those
web
content
meetings
are
once
a
month
and
they
are
the
first
monday
of
the
month.
I
believe
usually
so
we
just
had
one
yesterday.
So
sorry,
you
gotta,
wait.
You
gotta
wait
till
the
next
one,
but
that's
all
right.
B
We
have
enough
to
do
anyway,
so
we
will
maybe
put
that
on
the
on
the
agenda
for
that
meeting.
B
Any
other
questions
about
this
metric
release.
I
see
kevin's
on
as
well,
so
he
can
answer,
I'm
sure
anything
specific
with
regard
to
logistics
or
operationally
how
we
do
this.
If
anybody
has
any
questions,
comments.
B
Yes,
10
000
agree
with
that.
Kevin
gets
10
gold
stars
for
all
his
hard
work
at
this.
In
this
like
twice
a
year,
I
mean
he
works
hard
all
year
long.
I
shouldn't
say
it
like
that,
but
especially
these
this
period
and
then
in
the
fall
again,
it's
kevin's
time
to
to
shine
and
he
gets
the
burden
of
it
all.
So,
thank
you.
Kevin
you're,
awesome.
B
All
right,
so
I
guess
we
can
just
move
on.
Excuse
me.
The
next
thing
on
here
is
the
auger
hackathon.
We
are
having
our
very
first
auger
hackathon,
virtually
of
course,
and
that
will
be
on
february
13th.
There's
the
link
to
registration,
I'm
gonna!
Let
sean
talk
about
it
a
little
bit.
I
don't
know
if
we've
made
that
live
yet
that's
between.
A
A
A
So
we're
gonna
focus,
we're
gonna.
Do
our
first
hackathon
focused
on
the
time
zones
of
north
america
and
europe,
so
it'll
start
at
7
a.m,
central
time
or
8
a.m.
I
think
we
said
I
guess
it's
7.,
which
will
be
sometime
later
in
the
afternoon
like
an
early
afternoon
in
europe
and
we'll
go
for
five
hours
and
I'll
begin
with
an
overview
of
auger
for
anybody.
That's
familiar
with
that.
A
So
if
you've
got
that
already,
you
don't
have
to
come
for
the
first
hour
and
then
we'll
start,
focusing
on
the
different
issues
in
augur
and
working
together,
individually
or
groups
to
attack
different
open
issues
in
the
auger
repository
and
basically
learn
how
to
operate
run
and
to
work
with
auger
in
the
company
of
people
who
know
it.
So
that's
the
whole
pitch.
B
B
So
yeah,
so
the
site
is
live.
If
you
have
comments
or
questions,
if
something
doesn't
look
clear
because
shawn
and
I
did
this
together
and
so
like,
we
know
what
we
wanted
to
say,
but
sometimes
you
know
it
doesn't
actually
translate
into
something:
that's
reasonable
for
other
people.
So
yeah
just
send
send
us
comments.
You
can
email
me
and
I
can
put
them
on
the
site.
It's
no
big
deal
or
email
shot.
Neither
one
of
us
we'll
make
it
happen.
B
C
B
E
No,
it's
okay!
I
just
wanted
to
let
you
guys
know
that
we're
starting
an
open
source
calendar
for
ieee
essay
open,
but
it's
not
just
for
our
events,
we're
doing
all
foss
events
and
so
we're
actually
in
the
midst
of
putting
everything
in
right
now.
So,
if
you
guys
do
have
any
more
events
like
that,
you
know
feel
free
to.
Let
us
know
we
can
get
it
up
on
our
calendar.
E
E
Yeah
so
right
now
we're
literally
trying
to
get
all
that
all
of
our
stuff
on
there
first.
So
I
can't
share
the
link
to
the.
I
can
share
the
link
to
the
calendar,
so
you
can
see
what's
on
there,
but
it's
just
our
advisory
group
events
and,
like
I
said,
we're
still
kind
of
formulating
what
we
want
this
calendar
to
look
like.
So,
unfortunately
they
have
to
go
through
me
right
now,
but
yeah
I'll
send
that
information.
B
All
right,
I
think
we
can
probably
move
on-
is
that
cool
anybody
else
have
questions
about
this
hackathon
or
anything.
B
Word
up
we're
moving
on
then
all
right,
advertising
events-
oh
we
just
talked
about
that.
Sorry,
okay,
review
documentation,
relocation,
consolidation
efforts,
elizabeth
and
matt
s.
Matt
s
is
not
on
here.
So
here's
the
deal.
We
have
a
lot
of
documents,
as
you
know,
in
the
chaos
organization.
B
So
what
we
decided
to
do
was
create
a
google
chaos
account
that
we're
going
to
try
to
put
all
of
these
google
docs
in
what
we're
not
sure
is
how
each
working
group
wants
to
handle
this.
If
we
want
each
to
have
their
own
folder
in
that
central
account
or
just
share
it
with
us,
like
we're,
just
not
sure
what
you
all
want
to
do.
B
So
we
thought
we
would
bring
the
discussion
here
to
see
what
people
think
about
how
we
should
structure
the
folders,
how
we
should
set
up
the
process
of
archiving
minutes,
for
instance,
that's
kind
of
what
drove
this
whole
thing,
so
you
know
matt
also
matt
snell
was
thinking
to
also
put
them
on
github
as
markdown
files,
all
the
the
old
minutes.
So
really,
I
just
think
we
need
to
open
it
up
and
kind
of
figure
out
what
we
want
to
do.
D
Well,
george
started
with
a
comment
in
there
about
transferring
ownership
of
like
minutes
or
documents
to
chaos
project
I
mean
it's
interesting.
I
couldn't
even
begin
to
remotely
tell
you
how
many
people
probably
own
the
google
documents
that
comprise
the
work
we've
been
doing
in
the
project
over
all
these
years.
D
D
D
G
H
H
B
Okay,
so
each
working
group
will
take
their
minutes
and
add
and
add
that
gmail
address
that
the
chaos
project
owns
as
a
collaborator,
and
then
it
can
transfer
ownership.
What
do
we
want
to
do
about
the
archived
minutes?
B
I
Be
noticed
here
yeah,
so
the
purpose
was
sorry
to
like
a
lot
of
people
have
very
slow
connection
or
it
takes
time
to
load
the
entire
document
when
it
gets
bigger
and
bigger.
So
the
issue
was
like:
if
we
purge
one
year,
data
and
archive
it
so
that
when
anybody
joins,
they
can
quickly
load.
The
document
start
contributing
to
it.
J
I
think
they're
archiving
it
as
a
basically
they're
archiving
it
by
one
year
and
they're
archiving
it
as
a
markdown.
So
it's
it's
fairly
easy
to
convert
google
docs
into
markdown
using
some
of
the
plugins
that
are
out
there.
So
that's
my
understanding
is
they're,
just
converting
one
year's
worth
of
meetings
into
markdown
and
moving
it
into
github.
Okay,.
C
J
B
Okay,
so
here's
one
more
question
about
this:
when
we
go
to
create
a
new
metric
and
we
open
a
google
doc,
do
we
do
we
care
about
putting
that
in
the
centralized
thing
because
it
doesn't
really
live
on
past?
You
know
once
it's
released,
then
we
don't
really
ever
access
that
google
doc
again,
but
maybe
just
the
templates.
D
So
in
terms
of
like,
if
a
working
group
has
a
new
metric
that
they
start
tomorrow,
I
don't
see
a
real
problem
with
like
me,
just
starting
a
google
doc,
because
to
your
point,
it
ultimately
just
leaves
that
google
doc
and
moves
into
github
and
then
it
during
the
review
period.
Everything
happens
in
github
and
then
it
moves
to
the
website.
B
J
J
To
the
nod's
point,
though,
it
does
capture
who
commented
on
and
who
made
notes
on
that
metric
when
we
created
them.
So
I
mean
we
do
lose
we're
losing
that
information
when
we,
when
we
move
it
into
the
get
up
markdown,
I
don't
know
if
we
need
to
keep
it
or
not,
but
but
that
is
information
we
are
losing
like
who,
who
originally
wrote
the
metric
or
who
collaborated
on
the
metric.
I
D
C
J
I
would
say
that
that's
just
generally
best
practice
for
working
in
the
open,
but
you're
I
mean
you're
you're
right,
there's,
probably
nothing
specific
that
we
would
that
we
would
use
it
for,
but
it
does
provide
transparency
to
the
work
we're
doing.
D
J
On
a
related
note
for
the
release,
I
am
it.
The
the
contributor
list
has
gotten
so
large
that
it
is
difficult
to
maintain
and
figure
out
who
has
contributed
on
the
new
release
that
was
not
there
prior.
C
K
I
I
don't
know
if
it's
practical
to
recreate
contributor
logs
for
each
metric
in
the
past,
and
I
think
not,
but
I
do
think
that
it
would
have
the
advantage
of
helping
contributors
be
recognized
for
what
they
worked
on
sort
of
the
these
last
two
topics
have
a
surprising
relevance
to
one
another
in
that
the
contributor
list
is
now
very
long
for
the
project
as
a
whole,
and
the
per
metrics
contributor
contributor
list
would
help
ameliorate
that
problem.
D
K
The
breaking
it
out
in
the
contributor
list
would
be
less
distracting
to
people
who,
whose
main
mission
is
to
study
the
metrics.
That
said,
each
metric
has
a
lot
of
real
estate
right
like
a
we
give
it
a
full
page,
you
give
it
a
full
page
and
there's
plenty
of
room
to
breathe,
and
so
it
does
seem
to
me
that
there
is
not
too
much
to
lose
by
putting
it
there.
I
think
gathering
the
data
is
probably
the
harder
point.
K
K
D
A
D
L
B
I
really
like
it
too
lucas.
I
think
that's
a
great
idea,
and
you
know
maybe
this
is
something
we
could
offer
as
a
volunteer
opportunity
for
someone
to
go
back
through
all
of
the
old
google
docs
and
pull
that
information
out
and
maybe
correlate
it
with.
You
know
the
meeting
minutes
or
on
on
that
day.
What
do
you
all
think.
J
A
good
idea
there
is
the
question
on
whether
or
not
we
can
even
find
some
of
these
google
docs.
I
think
some
of
them
are
maybe
maybe
gone
or
hidden
or
lost.
D
D
I
Excel
sheet,
so
a
lot
of
links
are
there.
Maybe
we
can
track
from
there.
B
J
Oh,
I
was
just
gonna
say
for
some
of
the
older
metrics.
We
might
just
put
a
put
a
call
out
for
to
people.
You
know
if
you,
if
you,
if
you
worked
on
a
metric
and
want
your
name
added
to
the
author
list,
let
us
know
and
we
we
could
capture
it
that
way.
J
Honestly,
we
could
probably
do
that
for
all
of
them.
If
we
don't
want
to
spend
the
time
going
through
the
records
and
finding
out
who
is
who.
A
C
G
Contributions
so
maybe
then
it's
something
we
just
do
going
forward
that
way.
We
don't
have
to
worry
about
getting
consent
for
prior,
but
adding
that
end
as
part
of
the
metrics
release,
just
the
confirmation
of
everyone
who
contributed
to
it
and
then
then
we
have
the
information
to
publish
that
going
forward
and
then
you
can
opt
in
at
that
point.
J
As
a
as
a
as
a
pilot,
should
we
try
to
do
that
with
the
metrics
that
we
are
releasing
this
cycle.
G
It
does
kind
of
raise
an
interesting
question,
though
I
guess
for
this
context,
in
the
risk
working
group
we're
talking
about
the
bus
factor
and
adding
that
to
the
official
chaos
metrics,
where
it's
actually
something
that
we
came
up
with.
It's
something
that's
just
been
discussed
prior
in
the
industry,
so,
like
I'm,
not
quite
sure
how
we
would
attribute
that
metric
outside
of
the
west
working
group
decided
that
we
all
agree
with
this
metric
and
have
used
it.
G
G
D
B
Okay,
let's
go
ahead
and
move
on
because
we
do
have
other
stuff
to
talk
about.
Thank
every.
Thank
you,
everyone
who
contributed
to
that.
That
was
an
amazing
conversation.
I
feel
much
better
about
where
we
stand
with
all
of
it
and
I'm
sure
that
will
continue
to
evolve
but
yeah,
I
feel
like
we
make
good
progress
there.
B
So
the
next
item
on
our
agenda
is
to
talk
about
the
google
summer
of
code,
georg
and
sean,
and
I
have
started
the
application.
I
don't
think
we've
filled
it
yet
because
we're
still
working
on
refining
our
answers
to
the
application,
but
we
need
to
do
a
couple
of
things.
First,
we
need
to
get
some
volunteers
that
would
like
to
mentor.
We
need
to
kind
of
solidify
that
list
and
then
we
also
need
to
solidify
our
list
of
potential
projects
for
augur
and
grimoire
lab
as
well.
B
So
I
don't
know
sean
or
if
you
want
to
talk
about
anything
right
now
or.
A
Georg
created
it
and
it's
due
february
19th
is
it.
I
want
to
say.
C
A
Okay,
so
I
know
augur
will
propose
one
or
two.
I
think
we
had
some
ideas
at
the
community
level
as
well
for
organizing
some
of
our
auger
community
report
stuff.
Was
that
going
to
be
a
google
summer
of
code
project
or
either?
Can
you
asking
your
airport
stuff.
I
D
Is
the
plan
to
still
do
the
micro
task
approach,
georg
or
sean
or
elizabeth?
You
know
where,
like
there's
the
project
and
then
there's
the
set
of
small
tasks
just.
A
A
D
B
C
D
B
J
M
I'm
sorry
word
I
mean
like:
are
we
planning
to
restructure
or
refine
the
chaos
website
as
well
like
developing
up
the
new
version
of
it
or
going
through
some.
J
M
J
During
the
during
the
migration,
there
are
some
tasks
that
we
have
identified,
that
we
want
to
put
in
place
immediately
and
then
through
the
through
the
process
of
developing
the
proposal
for
the
migration
and
through
previous
discussions
and
and
comments,
we've
we're
also
kind
of
assembling
a
a
secondary
list
of
of
changes
to
the
website
and
restructuring
that
we
would
like
to
do
after
the
after.
The
migration
has
happened
so
there
there
are
any
any
number
of
tasks
that
could
be
could
be
added
to
that
phase.
J
At
this
point,
so
in
answer
to
your
question,
yes,
we
are
planning
on
continuing
to
upgrade
and
add
new
features
to
the
website,
and-
and
some
of
that
may
involve
some
some
restructuring.
M
Okay-
maybe
we
could
add
this
as
well,
maybe
adding
up
some
of
the
micro
task
of
like
just
refining
or
upgrading
the
website
like
what
more
features
we
can
import
or
like
all
these
type
of
things.
We
can
add
up
as
a
one
idea
and
then
we
can
go
with
it
if
everyone.
D
D
So
kevin,
if
you
to
joshua's
point,
if
you
are
interested
in
this
infinate
too,
like
on
whether
it's
the
community
report
stuff
or
if
it's
automating,
like
the
release,
I'd,
be
happy
to
also
mentor
in
that
space.
You
know
or
new
features
to
the
website.
Maybe
we
could
think
about
how
one
proposal
could
maybe
touch
on
a
few
of
these.
J
Additionally,
I've
been
wanting
to
do
a
diversity
and
inclusion
audit
of
the
website,
an
accessibility
audit
of
the
website
and
and
a
marketing
audit
at
the
website.
So
those
those
are.
A
J
That
could
provide
direction
for
future
improvement.
A
I
wouldn't
see
those
you're
not
suggesting
those
are
google
summer
of
code
project
story,
because
those
are
not
really
technical
enough.
I
don't
think.
J
J
So
without
committing
yes,
I
I
agree
that
all
of
these
things
are
good
ideas.
I
think
I
need
to
kind
of
think
about
what
those
tasks
would
entail.
B
Okay,
let's
go
ahead
and
move
on.
I
think
we
have
some
a
good
start
here
and
if
people
want
to
take
the
next
week
and
kind
of
think
about
other
things,
we
might
we
might
touch
on
next
week.
That
would
be
great,
so
we
have
about
nine
minutes.
Okay,
so
just
wanted
to
mention
really
quick.
B
The
next
thing
is
the
volunteer
opportunity
of
the
week,
so
we
want
to
get
our
file
names
and
folders
standardized
across
working
groups,
because
they're
kind
of
like
a
mishmash
right
now
and
it's
a
little
bit
confusing,
especially
for
newcomers
to
try
to
navigate
all
of
it.
So
giorg
had
this
idea
of
getting
some
help
with
just
renaming
some
things.
B
So
if
you
know
anybody
who
needs
practice
or
would
like
to
kind
of
get
a
little
bit
more
experience
using
git
and
github
in
that
way,
I
think
that
would
be
a
great
opportunity
and
it
wouldn't
take
forever.
You
know
it's
like
a
one-time
thing,
one
and
done
so
and
then
moving
forward
we
can,
we
can,
you
know,
obviously
have
it
have
it
all
set.
So
we
are
estimating
about
one
hour
per
working
group
to
go
through
and
kind
of
rename.
B
Everything
and
georg
has
documented
quite
a
lot
of
the
thought
process
of
how
we're
gonna
move
forward
so
and
how
to
how
to
do
all
of
that.
So
it's
all.
It's
should
be
pretty
pretty
simple,
I
think,
but
it
might
be
kind
of
tedious
it
would
be
also.
But
if
you
know
anybody
who
wants
more
experience
doing
any
of
that
or
has
a
little
bit
of
extra
time
can
help
us
with
that
that'd
be
awesome,
send
them
either
my
way
or
to
georg
either
one.
J
J
J
B
So
yes,
if
this
is
something
that
you
are
interested
in
being
a
part
of
george,
you
did
drop
a
link
to
his
proposal
in
the
minute
so
check
that
out
and
you
can
follow
up
with
with
him
on
that
someone
sneakily
added
something
to
the.
D
So
we
have
the
translation
repository
and
I
quickly
realized
that
pull
requests
that
were
coming
in
in
chinese
were
not
something
that
I
could
really
make
have
any
comment
on
do
well
with
so
king
and
shoya
as
maintainers
of
that
repository
as
well,
and
so
they
can
obviously
provide
better
feedback,
and
it's
really
the
conversations
are
really
interesting.
D
Already,
there's
a
conversation
around
how
to
define
an
issue
like
what
does
issue
even
mean
in
chinese
and
then
the
cascading
effects
has
to
how
to
represent
that,
because
right
now
the
the
question
is
whether
or
not
it's
even
represented
correctly
in
in
one
metric,
and
if,
if
it's
not,
then
that
would
obviously
have
implications.
So
it's
just
it's
really
interesting
to
kind
of
watch
the
issue.
So
I
just
a
big
thank
you
to
to
shoya
and
king
for
offering
their
help.
There.
B
D
Yeah
daniel
has
alluded
to
perhaps
be
willing
to
help.
B
Okay,
so
we'll
just
we'll
check
in
with
daniel
and
just
see
how
he
feels
about
that
and
then,
if
anyone
else
is
fluent
in
spanish
and
would
like
to
participate
in
that,
let
me
know
and
I'll
add
you
to
we'll
create
a
team
on
github
and
then,
whenever
we
have
revisions
to
the
metrics,
if
you
want
to
be
a
part
of
just
looking
over
those
and
making
sure
that
they
make
sense,
because
we
are
not
going
to
have
those
professionally
translated.
So
if
you
can
help
us
with,
that
would
be
great.
B
Oh
geez,
we
have
four
minutes
and
we
have
a
lot
of
a
lot
of
working
group
updates.
So
let's
just
do
this.
If
you're
on
a
working
group
that
has
a
major
update,
for
instance,
the
risk
because
meetings
were
moving.
A
We're
pivoting
towards
dependencies
kind
of
hard
right
now
and
our
meeting
time
is
now
2
p.m,
on
2
p.m.
On
thursdays,
we
moved.
A
For
evolution
correct,
so
the
next
one
is
whenever
it
is,
I
think
it
it's
this
week
or
next
week.
B
H
B
Awesome
diversity,
inclusion.
D
B
I
think
matt
snell,
I
just
caught
the
tail
end
of
the
outreach
badging
meeting,
but
emily
nicole
were
there.
I
think
beth
was
there
as
well.
I
believe
we
have
another
application
for
badge.
So
that's
exciting.
Is
that
right?
B
L
Oh
I'd
have
to
look
at
it,
but
we
found
out
about
or
actually
it
was
announced
in
this
morning's
meeting.
G
L
L
B
The
only
that
is
very
exciting.
I'm
excited
the
only
other
thing
that
we
might
want
to
mention
in
that
about
that
working
group
is
we're
talking
about
changing
it
from
diversity
and
inclusion
to
diversity,
equity
and
inclusion,
since
that
seems
to
be
a
little
more
what's
the
word,
I
want
just
kind
of
staying
up
with
like
how
the
general
movement
is
going
to
to
recognize
that
that's
another
piece
of
it.
B
So
if
you
have
thoughts
on
that
feel
free
to
join
that
that
group,
I
believe
they're
meeting
this
week,
obviously,
and
so
hop
in
on
that
call.
If
you
have
strong
feelings
about
that,
and
then
I
think
the
only
other
update
for
is
value,
we
have
a
new
facilitator
vernad.
Thank
you
very
much
for
stepping
in
because
matt
b
had
to
step
away
for
career
obligations,
so
vernatus
joined
as
the
new
facilitator.
B
I
Right,
thank
you
and
just
a
note.
We
are
planning
to
move
meeting
one
hour
ahead
or
like
letter.
Maybe
so
I'm
sending
the
email
and
figuring
out
so
it
will
be
either
one
hour
earlier
or
one
hour
later
or
or
the
alternate
weeks
so
I'll
send
out
the
email
and
we'll
confirm
what
is
the
best
option
and
then
we'll
finalize.
I
And
one
more
thing:
I've
created
a
pull
request
for
a
metric
to
be
added.
I
haven't
had
it
in
this
list,
because
the
pull
request
was
not
merged
as
yet
so
wanted
to
check
if
it
is
possible
to
merge
and
add
it
in
this
release,
because
I
created
a
request,
there.