►
A
A
A
What's
this
what's
going
on
here,
okay:
volume:
okay,
yeah!
We
don't
need
that
yeah!
That
was
yeah.
We
don't
need
that
at
all
alice,
docs,
actually
yeah,
okay.
So
what.
B
A
And
actually,
let's
see
put
it
in
the
really
service
put
what
in
okay.
I
don't
remember
that
similar
to
op,
adding
up
up
and
ctx
where
upstream
points
to
data
flow.
Don't
leave
that
operation
in
it.
It's
futures,
okay,
yeah
yeah.
I
think
this
is
all
stuff
for
later.
Let's,
let's
get
the
hell
out
of
here,
okay,
so,
okay,
where
are
we
all
right,
pwd,
all
right,
we're
in
the
right
directory?
This
is
the
main
branch.
A
A
I
think
this
is
a.
Please
contribute,
okay
and
it's
mad,
it's
mad
about
something.
I
can't
remember
what
the
hell
what's
going
on
here,
but
yeah.
So,
okay,
I
think
we're
fine.
I
think
this
is
basically
fine
right
here
so
or
let's
just
create
a
new
repo,
real
quick.
A
Okay
and
then
we'll
do
a
good
clone.
A
Commit
push
all
right,
node
one,
how
many
a's
do
we
have
four
okay,
perfect
and
let's
see,
do
we
get
a
clean
contribution
here?
A
A
Okay,
so
then,
now
that
we
have
a
clean
integration
test,
so
we
know
the
state
of
the
repo
get
status
clean,
clean
tree,
basically
sort
of
and
none
of
the
none
of
the
modified
files
are
there.
None
of
the
track
files
are
modified.
Okay.
So
now,
let's
go
about
the
process
of
splitting
out
cd
entities
alice.
A
A
System
context
say:
hello:
okay,
we
just
played
with
that.
Okay,
so
and
then
here's
the
stuff
we
care
about
moving
okay,
so
we're
gonna
grab
all
of
those
overlays
and
we're
gonna
throw
them.
I
think
what
do
get
pull
okay.
So
what
do
the
docs
or
what
did
the
docs
say
is
what
I'm
more
curious
about.
I
think
they
changed
right
there.
So
what
did
the
docs
used
to
say?
A
A
It
looks
good
all
right
so
now
we're
gonna
do
a
bunch
of.
C
B
B
A
A
Please
contribute
recommended
community
standards,
yeah,
okay,
yeah,
please
contribute
recommended
community
standards.
I
think
our
convention
is
just
to
say,
recommended
community
standards
again
and
then
we
import
from
init.
If
we
so
desire.
Okay,
so
t
it
there.
Where
else
do
we
want
it?
A
B
Read
a
community
standards
overlay.
A
A
A
A
Operations
but
I
wonder
operations
should
that
be
overlays.
A
This
is
the
current
convention.
We
can
change
this,
but
I'm
following
the
current
convention,
for
consistency's
sake
so
and
the
current
convention
is,
you
know
if
you
have
basically
a
base
class
or
base
flow,
that
name
it
the
same
thing,
and
then
we
import
from
init
to
expose
to
that
to
anything
trying
to
import
in.
A
Okay,
so,
oh
yes
and
thank
you,
absec
pacific
northwest
at
the
days
conference
for
the
mug
so
still
waiting
on
the
recording
there.
I
know
that
they're
they're
busy
trying
to
figure
out
getting
all
those
uploaded
and
that's
a
lot
of
work
but
excited
to
post
that
once
it's
there,
so
yeah,
okay,
so
overlays
dfl
operations
get
kit.
A
A
Yeah
operations.
A
A
A
A
A
C
A
There
it
is
okay
overlays,
but
this
is
not
an
overlay.
This
is
alice
operations,
get
okay,
alice
operations
get
is
itself
an
overlay
into
the
git
operations,
but
it
doesn't
need
to
be
it
doesn't
really
matter
so
because
it's
in
it
it's
because
I
guess
I
guess
we're
doing
so.
What
yeah?
What
makes
something
distinct
as
an
overlay
versus.
A
So
why
would
we
say
operations
kit?
So
maybe
we
don't
even
want
overlays
there
in
that
instance,.
A
A
A
A
All
right,
so
it
should
look
like
the
same
list.
Basically
so
get
operations
recommended
community
standards,
okay,
yeah
and
then
see
okay.
So
I
screwed
up
the
cli
okay,
okay
yeah
and
I
screwed
up
to
py.
A
B
A
A
A
A
I
think
maybe
they
should.
How
do
we
distinguish
between.
A
How
do
we
distinguish
between
okay?
Let
me
just
put
them
in
here:
okay,
okay,
wait:
how
do
we
distinguish
between
ones
that
are
overlays
and
ones
that
are
not?
I
think
it
makes
more
sense.
Yeah
recommended
community
standards
where
you
can
just
use
all
these
things
together.
Everything
in
here
you
can
use
together
is
the.
A
So
if
they
don't
have
a
package,
we
need
to
be
named
spacing
them
into
the
place
that
they
come
from
and
they
don't
necessarily
need
to
be
seen
as
overlays
one
of
they're
all
going
to
be
combined
or
let's
see
they
don't
yeah.
They
do
necessarily
need
to
be
seen
as
overlays,
so
maybe
within
overlays.
A
Okay,
then
good,
I
recommended
community
standards.
A
Okay,
so
obviously
you
can
do
this
any
way
you
want,
but
one
of
these
is
going
to
make
sort
of
more
sense,
intuitively,
so
we're
trying
to
figure
out
which
one
that
is
okay,
so
and
then
should
these
be
all
in
overlays
or
would
these
work
as
base
flows
by
themselves?
I
think
they're,
all
sort
of
like
stand
on
an
if
you
want
to
overlay
them
and
you
overlay
in
the
past
process,
so
they're
all
standalone.
A
Okay,
that
answers
our
question.
So
operations
get
get
okay,
so
basically
I
think
that's
redundant.
Then
why
did
I
do
that
operations
get
operations
get
okay,
because
one
is
an
overlay
for
okay.
A
Issue
operations
get
okay,
so
overlay
operations
get
and
overlay
alice
operation
where's
this
one,
this
one:
okay,
oh
yeah,
okay,
so
this
is
just
this
one
yeah,
which
is
yeah.
That's
what
I
thought?
Okay!
So
this
then
yeah
acts
as
an
overlay
into.
A
A
B
A
B
A
A
I'm
just
gonna
fill
this
one
out
while
we're
here.
Where
is
this?
Dfm
operations
get
so
dot?
Dot
is
get
dot,
dot,
dot
is
operations,
dot.
Four
dots
is
dfml.
Five
dots
is
recommended
community
standards,
one
two,
three
four
five
or
wait.
So
actually
this
is
alice
get
repo,
so
that
would
be
us
operations
get.
A
A
A
A
A
B
A
Okay,
so
github
issue
overlay,
github
issue,
permissions
checks.
What
is
this
github
pull
request.
A
B
B
A
C
A
A
I'm
like
going
back
and
forth
on
whether
these
are
all
really
distinct
or
whether
we
should
just
throw
them
actually
in
the
same,
if
they
really
should
just
be
in
like
if,
if
there's
is
there
any
reason
that
they're
actually
separate,
I
just
want
to
question
it
so
because
they
use
alice,
get
repo
so,
but
you
could
actually
not
use
them
yet.
Okay,
so.
A
A
All
right
so
pull
request
reference
issue.
Okay,
so
basically
this
says
read
me
april
body
readme,
pure
title:
okay,
so
yeah,
okay.
So
this
just
sets
these
defaults
see
these
are
the
title
and
body
are
there
or
yeah
title
and
body?
Are
there
and
they
get
set
by
this
as
an
overlay?
So
you
can
optionally
grab
them
from
the
read
me
issue.
Okay,
so
oh
yeah,
that's
nice!
Okay,.
A
A
A
Cli,
okay
and
that's
in
a
recommended
community
of
cli:
okay,
then
operations
get
alice,
we
see
alice,
please
contribute
okay,
great
and
then
alex
operation
is
good
and
then
alice
get
repo
alice
overlay
operations,
good
okay,
so
there
there
and
then
we
have
one
missing,
which
is
overlay,
get
okay.
A
Okay-
yes,
it's
just
in
cli,
so
we
need
to
move
that
to.
B
A
All
right,
so
we
are
splitting
out
the
cli
code
into
different
overlays,
each
yeah,
with
with
their
own
some
with
their
own
files.
Some
just
you
know,
optionals
within
the
same
file.
Okay,
so
looks
good.
This
one
has
two
get
a
pull
request
and
the
reference
issue
you
can
optionally
add,
and
then
here's
the
cli
and
the
cli
looks
like
okay
yeah.
We
got
that
and
this
needs
to
be
trimmed
down
a
little
more.
Let's
go
trim
that
yeah,
let's,
let's
remove
all
the
imports.
A
C
A
A
A
All
right,
okay,
I
think
I'm
just
going
to
throw
on
all
these
imports
on
everyone.