►
Description
Meeting notes: https://docs.google.com/document/d/1ttqkcYPmYZyqvtkaHs92bx2UeVUiXDhuzP-0WbP11Fw/edit#heading=h.7o2ubzl5z39r
A
B
B
A
B
B
A
B
A
B
B
Well,
you
know
it's
not
it's!
It's
it's
yeah!
It's!
But
it's
anyway!
It's
it's,
but
that's
that's
there
and
then
there's
the
kind
of
like
organization
that
we
came
up
with
in
the
in
the
discussions
about
how
to
how
to
organize
these
things
into
different
categories
and
and
so
I
took
the
the
markdown
thing
and
I
committed.
C
B
Into
well
into
a
branch
here,
whatever
turbo
patch
one
and
just
to
give
a
kind
of
flavor
of
what
I
think
this
could
look
like
if
we
go
this
way
where
so
we
have
like
you
know
what
developers
would
would
come
to
they.
Oh
they're
they're,
coming
to
us
here,
we're
at
The,
Source,
Credit,
Management,
best
practices,
I
wonder
what
the
source
code
management
practices
has
and
then
you
know
they
would
come
to.
B
B
B
Basically,
so
so
that's
another
way
for
for
that
data
to
be
consumed.
Besides
link,
you
know
clicking
through
from
one
of
these
pages
and
then
the
other
thought
that
I
had
was
well.
We
can
have
this
presentation
of
the
of
the
and,
by
the
way,
I've
included.
Some
of
the
material
that
I've
included
in
here
is
is
pulled
from
Christine's
documents.
So
that's
where,
if
we
need
some
intro
material
with
some
more
General
recommendations
that
would
that's
coming
through
from
Christine's
document,
I've
reworded
it
to
be
genericized.
B
So
it's
not
talking
about
GitHub,
but
it's
just
talking
about
organizations
and
then
prevent
specific
recommendations
are
the
links
through
to
the
to
the
legitified
data.
But
if,
if
somebody
wants
to
come
in
and
I
want,
you
know
what
I
don't
care
about.
Your
editorialization
of
this
I
want
to
know
what
your
recommendations
are
for
GitHub
then-
and
this
is
just
a
sample
list
like
this-
would
be
the
this
would
be
everything
actually
but
I've.
B
Only
I've
just
put
this
here
as
a
as
a
indicator
of
what
it
could
look
like.
We
just
have
the
list
of
best
practices
and
then-
and
then
you
know
here
we
can
link
through
to
the
one
that's
specific
to
GitHub
and
you
go
over
to
gitlab.
Do
you
see
all
the
all
the
ones
that
are
applicable
to
only
to
gitlab
and
then
you
click
through
and
you
see
the
gitlab
specific
recommendation.
B
And
then
the
other
thing
I
did
is
I
took
some
of
the
operations
stuff
that
was
coming
out
of
your
document
Christine
because
I,
because
we
were
speaking
about
that
last
week
or
not
last
week,
but
the
last
time
we
had
a
call
and
we
talked
about
the
need
for
an
operations
section
that
specifically
addresses
the
needs
of
P
of
of
of
of
operators
or
or
of
as
it
says
here,
ospo
or
operations
team
responsible.
But
this
is
this-
is
lifted
directly
from
your
document.
B
So
it
it
talks
a
lot
about
GitHub
and
probably
we
need
to
just
figure
out
either
we
genericize
it
or
we
split
it
up
into
GitHub
operation,
section
gitlab,
operation,
section
or
or
we
just
say
this
is
only
applicable
to
give
I
don't
know
we
need
to
talk
about
kind
of
editorially.
What
we
want
to
do
there
so
anyway,
that
that's
kind
of
my.
D
A
Nice
wow,
like
a
lot
of
that's
a
lot
of
a
lot
of
work
there.
Thank
you,
yeah
and
I.
Think
even
like
the
thought
that
you
said
just
going
on
the
theme
that
you've
done
with
the
GitHub
and
the
git
lab
even
to
the
operations
could
do
the
same
thing.
Little
icons
and
specific
sections
related
to
operations,
yeah.
B
Yeah
and
we
can
like,
we
can
revise,
and
this
allows
us
by
having
them
in
separate
things
and
Sarah
you
separate
files.
We
can
revise
the
table
of
contents
or
the
different
tables
of
contents,
depending
on
how
you
want
to
look
at
the
data
separately
from
the
actual,
like
recommendations
and
Remediation
steps
that
are
coming
directly
out
of
legitify.
We
don't
have
to
worry
about,
like
you
know,
inlining
all
of
that
stuff.
So
anyway,.
C
B
B
What
I
was
hoping
that
gnome
might
be
able
to
take
this
as
a
template
and
generate
some
of
the
the
the
lists
so
that
we
don't
have
to
you
know
generate
because
because
the
markdown
for
this
is
actually
quite
complex,
especially
when
you
include
SVG
icons
and
you
want
to
size
them
at
a
certain
size,
it's
not,
it
doesn't
look
pretty
so
I
was
like.
How
do
you
do
this
again,
Google
or
DuckDuckGo?
You
know
markdown,
how
do
you
size
svgs,
oh
yeah,
okay,
anyway,
that's.
D
Thank
you,
Dan
I
think
this
looks
great
I
love
this
approach
and
I
love.
The
fact
that
you
were
thinking
about
integrating
with
scorecard
I
think
that's
going
to
be
a
big
big
win.
Awesome
ideas
could
work
good
work
to
the
team,
but
yeah.
Thank
you
for
synthesizing.
This
I
think
I
feel
this
is
a
good
direction
to
take.
It.
A
B
B
B
D
B
A
B
Right
so
at
some
point,
there's
a
there's
there's
a
script
that
gnome
has,
or
one
of
his
colleagues
has
created-
that
takes
that
and
splits
it
up
into
all
these
different
markdown
files
and
and
I
guess
all
I'm
saying
is
that
some
of
this
can
be
auto-generated.
Then
we
just
need.
Maybe
we
need
to
when
it's
when
those
things
are
auto-generated,
we
can
either
have
one
manual
step
of
okay.
B
Now
that
these
lists
have
been
auto-generated,
we
can
insert
them
into
the
into
the
readme
file,
or
we
could
even
do
some
kind
of
you
know
naughty
templating
thing
where
we
say:
okay,
you
know
the
readme
template
has
a
little
meta
tag.
That
says
this
is
where
the
list
goes,
and
then
the
the
markdown
generator
knows
that
and
can
and
can
replace
it
with
the
with
the
with
the
lists,
but
it
doesn't
need.
You
know
that
that
that
that
was
a
factor
on
my
mind.
B
A
B
B
A
A
B
B
So
what
I
was
so
I
think
it
needs
a
little
bit
of
editorial
in
terms
of
like
adapting
some
of
the
material.
That's
in
your
document
into
into
heading
into
edit
sorry
into
intro
sections
of
each
subsection
that,
and
you
know
that
that
would
be
appropriate
and
not
restate
that
doesn't
restate
the
these
things.
You
know
yeah.
B
B
D
So
thinking
about
kind
of
holistically
about
this
project,
approximately
how
far
along
towards
complete,
do
you
think
we
are?
It
feels
like
just
my
observation
about
three
quarters
of
the
way
done.
We
have
some
polishing
we
like
to
get
the
scripts
and
some
editorialization
is
that
kind
of
pretty
accurate
I.
D
A
Yeah,
so,
even
before
we
started
this,
this
collaboration,
hi
Randall,
even
before
we
started
this
collaboration,
I,
had
to
put
in
like
a
talk,
broken
Source
Summit
in
North,
America
or
just
to
get
ahead
of
it,
because
I
knew
we
were
going
to
be
working
with
GitHub
management
and
it
seemed
like
an
interesting
topic
so
fortuitously.
It
seems
like
this.
This
collaboration
formed
up
and
I
think
it
might
be
like
a
great
opportunity
to
to
definitely
tie
in
that
work
and
talk
about
what's
been
going
there
as
well.
So
you.
A
B
D
B
B
D
Maybe
we
can
reach
out
to
him
on
slack
and
email
and
say:
hey
we'd
like
to
have
a
special
call:
can
you
make
it
and
it
doesn't
have
to
be
this
time
we
can.
You
can
reuse
the
zoom
link
to
have
to
hold
the
meeting
and
all
the
plumbings
in
place
so
it'll
get
recorded,
so
you
could
just
you
could
if
he
wants
to
meet
an
hour
before
this
time
on
a
Tuesday.
You
know
that
that's
an
option:
okay,
but
I.
D
A
D
A
D
B
D
D
A
Yes,
yes,
yeah
and
there's
some
like
nuances
there,
like,
for
example,
coming
back
to
your
point
Dan.
You
know
that
GitHub
is
now
going
to
make
a
multi-factor
2fa
mandatory
by
the
end
of
the
year.
Like
you
know,
it's
almost
like
that
recommendation
is
like
sort
of
mood
at
that
point
because
you
have
to
yeah,
but
I
guess
you.