►
Description
Meeting notes: https://docs.google.com/document/d/1ttqkcYPmYZyqvtkaHs92bx2UeVUiXDhuzP-0WbP11Fw/edit#heading=h.7o2ubzl5z39r
A
C
B
B
B
B
C
You
can
actually
extend
this
to
other
fcms,
but
then
also
mentioned
that,
where
this
legitify
support
scale
lab,
but
also
check
out
squawk
card,
because
there's
some
things
that
work
with
one
or
not
not
the
other.
But
it
was
a
50-minute
talk
seemed
to
be.
People
said
that
it
was
pretty
good,
so
so
it
was
good
to
just
kind
of
like
cover
that
I
didn't
I
wasn't
able,
because
I
was
also
kind
of
like
doing
it
from
a
lens
of
lessons
that
we
had
learned
at
F5.
C
I
also
spoke
about
what
we
were
doing
there.
We
were
on
that
stage
and
then
the
call
to
action
at
the
end
was
to
have
people
join
this
others
guide
and
also
told
them
that
we'd
be
meeting
next
at
this
time,
so
that
was
kind
of
like
a
quick
and
then
also
mentioned,
as
we
had
spoken
about
that
we'd,
probably
like
folks
to
who
had
more
get
lab
expertise
or
experience.
They
just
come
in
and
also
chat,
so
that
was
that
was
it.
C
C
B
B
D
B
B
E
C
Yeah
I
think
now
that
now
that
things
have
settled
in
come
back
to
normal
at
least,
hopefully
on
my
side,
I
should
be
able
to
power
through
more
and
I'm,
focusing
in
more
on
that
as
well
internally.
So
at
least
for
me,
I
think
it'll
be
easy
within
the
next
week.
I
do
leave
a
next
couple
of
days.
I
will
be
able
to
get
that
PRN,
but
then
our
next
meeting
is
not
until
two
weeks
from
now.
E
B
Him
we
can
do
that.
We
can
I,
can
do
something
next
week
on
this
on
this
slot,
if
you're
Christine,
if
you
think
that
would
be
yeah,
what
I
was
thinking
was
because
I
think
what
you're,
what
your
PR
is,
is
adding
a
bunch
of
editorial,
not
editorial,
but
more
content,
basically
from
your
five
documents
into
the
structure
that
we
currently
have
right
and
I
think
that.
C
E
Like
basically,
the
the
zoom
link
is
active,
so
it'll
work
and
what
we
could
do
is
send
a
note
to
the
mailing
list
and
use
in
slack
to
make
sure
people
are
aware,
but
just
statistically
there's
a
95
probability.
Something
will
get
temporarily
or
permanently
broken.
If
I
ask
operations
to
change
the
calendar
entry.
B
E
C
A
B
Let
me
put
something
in
the
calendar
for
next
Friday,
sorry
for
next
Thursday
I'm
going
to
use
the
email
addresses
that
are
in
the
minutes
as
people
to
invite
and
I'll
just
do
it
as
a
as
a
as
a
off
the
calendar,
invite
thing,
and
we
can
use
that
as
a
review
step,
and
then
we
can
have
something
to
we.
We
can.
We
can
therefore
have
something
to
present
back
to
to
the
group
the
following
week:
okay,.
C
A
B
A
B
B
B
Each
one
of
the
individual
principles
can
be
regenerated
at
any
point
out
of
the
out
of
legitify
data
and
that
we
simply
we
we,
but
we
keep
the
readme
files
we
kind
of
not
freeze
them,
but
we
start
managing
them
through
through
GitHub
through
the
pr
process,
rather
than
regenerating
those
those
files.
Does
that
make
sense?
B
Okay
right!
So
that
way,
if
you
make
a
a
change
to
the
data,
we
can
regenerate
that
Singleton
page
or
whatever.
It
is.
You
know
or
the
all
of
the
all
of
those
pages,
but
we
don't
have
to
go
back
and
reapply
changes
to
the
index
files
to
the
to
the
readme
files
unless
they're,
unless
we're
adding
a
new
thing.
A
B
All
right,
I'm
trying
to
remember
what
my
I
had
something
in
my
head
about
another
kind
of
like
work
item
that
we
need
to
do:
oh
yeah!
No,
no!
No!
It's
no,
never
mind
actually,
because
I
think
that
that
we
just
we've
we've
kind
of
I
was
going
to
talk
about
how
we
could
do
some
kind
of
templating
system
that
would
allow
you
know
for
the
readme's,
but
I
don't
know
I,
don't
know.
If
we
really
need
to
do
that
at
this
point,
I
think
we
can.
C
So,
just
to
clarify
the
pr
I'll
be
doing
it's
just
initially.
The
last
time
we
had
spoken
about
our
dual
PR
so
that
you
could
see,
look
at
the
structure
to
see
how
that
would
fit
into
the
auto
generated
stuff
and
then,
at
that
time,
you're
talking
about
the
templating,
but
you
don't
think
we
will
need
that
right
away.
Well,.
B
I'm,
just
not
sure
if
we,
if
we
because
just
talking
through
it
just
now,
if
we
don't
re,
if
we're
not
going
to
regenerate
the
readme
files,
then
I
don't
think
we
we
will
need
kind
of
fancy.
You
know
templating
system,
I,
think
we
we
can
I
mean
if
we're
happy
with
the
structure
as
it
is
then
then
or
how
it
looks.
B
Rather,
then,
then
I
think
you
know
it's
it's
at
some
point
where
you
know
if
we
add
a
third
source
code
management
system,
for
instance,
then,
or
if
we
add
significant
new
coverage
or
new
principles,
then
we
are
going
to
need
to
regenerate
some
or
all
of
those
lists.
As
of
that,
the
lists
of
links
to
the
to
the
individual
principles
but
I
think
if
we're
just
making
changes
here
and
there
we
can
do
it
using
the
the
pr
using
GitHub
PRS.
C
C
A
D
D
B
C
B
B
The
other
thing
that
Christine
that
I
wanted
to
ask
you
about
was
the
the
other
part
of
the
document
that
you
originally
shared
had
operations,
information
which
doesn't
really
isn't
in
the
scope
of
the
legitify
data.
But
it
was
additional
information
about
Opera
that
covers
the
roles
that
might
be
played
by
operations
in
managing
source
code
Management
systems,
and
is
that
something
that
you're
hoping
to
add
as
well
in
this
PR
or
in
a
subsequent
PR.
C
You
use
this
group
so
that
that's
another
place,
but
I
could
also
put
it
in
the
slack
Channel,
but
putting
it
in
front
of
people
might
have
been
a
better
idea
as
well
and
they
meet
they
meet
every
two
weeks
and
if
I
don't
catch
them
on
that
time,
slot
probably
gonna
be
four
weeks
from
now,
because
every
two
weeks,
it's
such
a
different
time
zone,
but
that's
another
possibility
I
can
I
can
share
within
the
group
as
well
on
the
slack
channel.
It's
called
to
do
to
do
a
group.
C
But
the
operations
thing
it
might
be-
it's
it's
probably
situational
to
a
particular
hospital,
so
it
might
not
be.
It
might
not
be
like
relevant,
but
it
could
be
called
a
summer
like
if
you're
doing
some
kind
of
operations.
These
are
things
that
you
might
think
about
if
you're
setting
up
something
room
but
I
don't
know
if
it
belongs
to
that
document
in
time.