►
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
A
B
A
Yeah
so
I
want
to
say
hello
to
everyone.
We
do
have
people
here
now:
apologies
for
the
delays.
We
are
still
fighting
audio
gremlins
in
this
studio
and
we
spent
the
last
15
minutes
trying
to
get
things
going.
We
do
think
we
have
narrowed
it
down
to
a
source,
but
we
do
not
have
a
solution
yet.
So,
if
my
audio
goes
quiet
during
the
show
I
apologize,
we
are
working
very
hard.
Current.
A
The
the
theory
points
to
Windows
self-leveling
audio
whenever
the
guests
on
the
teams
or
Skype
or
hangouts
call
doesn't
see
no
matter
what
we
use.
Someone
goes:
oh
someone's
trying
to
talk
through
a
communications
channel
and
then
it
mute
and
it
like
it
drastically,
lowers
the
volume.
So
we've
tried
to
turn
everything
off.
We
have
threads
with
product,
PM
manager,
engineers
from
all
the
various
teams
and
we're
trying
to
really
figure
this
out
because
we'd
like
to
just
to
have
it
work
when
we
walk
in,
but
we
do
appreciate
people
listening
to
us.
B
A
A
B
A
A
A
A
A
B
A
So
we've
talked
about
this
I
think
after
every
vacation.
Neither
one
of
us
thinks
it's
like
you
come
back
and
you
go.
Oh
that's
right.
I
have
to
go
to
work
and,
like
think
about
things
and
send
emails
and
stuff
in
order
to
like
keep
paying
my
bills,
why
can't
I
just
be
on
a
beach
or
why
can
I
be
traveling
the
world
or
playing
Nintendo
or
something
all
the
time?
Why
is
that
know
how
this
works?
I
just.
B
A
B
A
A
A
I
woke
up
in
terrible
pain.
Oh
no
I
didn't
wake
up
in
pain,
I
was
playing,
it's
actually
quite
depressing,
so
I'm
40
and
yes
and
I
was
playing
I
played
like
I
say
it
was
Friday.
It
was
Thursday
night.
Last
week,
I
was
playing
chess
with
my
son
Fitzwilliam,
and
then
we
decided
to
play
a
game
of.
What's
there.
A
It
just
started
hurting
and
I,
don't
know
I'd
like
it
just
started
hurting.
It
was
like.
Oh,
this
kind
of
saw
now
as
I
kept
playing
cards.
He
got
sorrow,
sorrow
and
then,
as
the
night
went
on
it
got
to
the
point
where,
like
I
was,
whenever
it
would
tweak,
I
would
have
to
sit
down.
It
was
so
painful,
like
I
had
broken
my
wrist
like
majorly.
A
Somehow,
and
so
I
didn't
sleep
well
that
night
and
then
I
went
to
the
hospital
in
the
morning
and
got
x-rays
and
all
that
type
of
stuff
nothing's
broken,
and
so
they
say
it
is.
They
could
see
arthritis
in
my
hand,
I
didn't
break
this
thumb
very
badly
about
13
years
ago
in
a
karate
incident,
so
they
think
it's
tendinitis
and
so
the
treatment
for
that
is
tylenol
and
a
wrist,
brace
or
wrist
splint
just
to
try
and
keep
it
in
one
position
for
a
while.
A
A
A
Obs
is
sending
to
YouTube
and
I,
hear
myself,
yeah
I
absolutely
have
so
I'm
in
theory
can
hear
everything.
John
is
saying
the
sound
is
better
now,
so
an
audio
is
better
well,
of
course
it's
going
up
and
down
like
we
said
we
haven't
solved
that
issue,
so
it
will
go
up
and
down,
but
since
Greg
says
it's
the
best
ever,
this
is
like
asking
our
customers
what
features
they
want
us
to
build.
You
can
never
get.
You
know
at
the
same
answer
twice
so
on
that
note
we
don't
have
John
this
week.
A
A
A
And
I
haven't
yet
I
have
feelings
about
it.
So
I'm
happy
to
talk
about
it
publicly.
I,
don't
hide
like
I'm
kind
of
I'm
very
to
mind
it
about
it,
but
I'm
very
happy.
I'm
taking
on
feedback
from
other
people
and
I've
asked
the
community
what
their
thoughts
are
and
as
expected,
we
got
to
types
of
feedback.
One
was
quite
more
dominant
than
the
other,
but
we'll
chat
about
it,
but
other
things
that
happened.
While
you
were
away.
Obviously
we
were
you
here
when
we
did
preview.
The
last
preview
of
thank
you.
We
are.
B
A
B
A
A
I
know
I
appreciate
that
I
think
the
the
extension
stuff
on
as
your
app
site,
political
as
your
app
service
web
apps
I
saw
websites
as
a
wrap
service.
That
thing
I
always
call
it
in
Terry's,
and
no
one
else
knows
what
that
is
yeah.
It
can
timeout.
So
we've
had
some
issues
where,
if
the
extension
is
quite
large,
it
can
actually
timeout
during
the
install
and
the
other
one
you
mentioned,
which
is
sometimes
it
decides.
A
It
can't
overwrite
a
file
or
something
cuz
something's
in
use,
so
yeah,
just
trying
again,
is
usually
the
best
remedy,
but
yeah
I
was
actually
happy
to
see
your
blog
post
was
very
much
I.
Just
do
what
I
normally
do.
I
ran
my
favorite
open-source
tool
to
determine
what
needed
updating
I
liked
that
you
called
out
to
the
docs
to
talk
about
why
the
meta
package
shouldn't
have
a
version,
because
we
had
discussed
that
on
a
previous
show,
I
still.
A
B
B
A
B
A
A
B
A
B
A
B
B
A
A
B
A
A
B
B
A
A
B
A
A
A
A
A
B
A
A
A
A
B
B
B
B
A
B
A
B
A
B
Clever
about
it
is
that
they've
thought
about
the
idea,
the
thought
about
the
thing
right,
but
then
they
actually
did
it
right
like
it
makes
total
sense
like
look
at
this.
If
we,
amongst
all
open
source
projects
migrate
from
X
to
Y
right
and
you
have
a
CI
and
that
CI
is
badged
or
whatever
or
a
bot.
They're
gonna
have
to
go
and
have
all
the
heuristics
for
figuring
out
those.
A
A
A
Seriously
seriously
cool
someone
told
me
on
here
to
say:
look
at
the
actual
marketing
package,
so
I'm
opening
it
and
you
get
package
Explorer
because
he's
saying
that
they
actually
linked
to
that
dude
Mach
dig.
He
says
that
he
they
actually
linked
to
that
changelog
in
their
new
get
metadata.
So
I'm
looking
I'm
true.
A
A
A
A
A
A
B
B
A
So
if
you
go
to
that
file,
no,
because
we
don't
want
to
make
creation
of
release
notes
today,
it's
been
a
headache.
We've
been
trying
and
it's
just
been
very
difficult
for
lots
of
different
reasons,
mostly
because
our
products
are
composed
from
lots
and
lots
and
lots
of
different
places,
but
that
has
changed
recently
like
the
a
spinet
stuff,
at
least,
is
now
all
in
a
single
repo.
So
in
theory
this
could
get
possible,
but
please
don't
assume
that
it
is
easy,
nothing
that
we
do,
unfortunately,
is
easy,
indeed
I'm
using
this
fluent.
A
B
A
A
It
includes
other
details
and
it
should
be
expanded
to
include
more
about
best
practices
like
this,
so
that
the
your
library
is
not
only
great
to
consume
for
people
who
just
want
to
consume
it
as
a
package,
but
also
great
to
experience
for
folks
who
are
participating
in
it
from
an
open-source
point
of
view
and
there's
there's
so
many
little
things
that
you
can
do
to
make
it
better
right
and
that's
another
one's
like
you
should
integrate
with
dependable.
You
should
do
these
things
and,
what's
great
about
it,
is
it
isn't.
A
It
turns
out
it's
not
very
specific.
It's
just
that
you
should
have
a
release,
notes
thing,
but
how
do
I
do
that?
Well,
it's
probably
some
tool
you
have
to
go
and
set
up
as
part
of
your
CI,
which
CI
you
using
there's
a
whole
bunch
of
forks
in
that
walkthrough
that
should
be
written
down
like
it
should
be
someone.
Maybe
they
are
I.
Just
didn't
know.
I.
A
B
A
Exactly
and
what
are
the
options
of
the
conventions
and,
like
the
whole
thing
of
getting
your
flows
set
up
so
they're?
Not
only
you
just
have
code
and
github,
you
have
CI
setup
on
both
your
check-ins
and
PRS.
You
have
tests
that
are
running.
You
have
a
my
get,
or
at
least
a
CI
feed
of
packages
so
that
people
can
get
packages
before
you
publish
them.
You
have
publishing
to
new
gate
with
automatic
versioning
that
checks
December
breaking
changes,
all
those
type
of
things
you
have
release,
notes
being
scheduled.
Now
you
have
a
change
log.
A
You
have
releases
being
tagged
in
github
as
hub
release
that
point
to
those
release.
States
like
all
and
then
have
your
new
pet
and
have
all
the
correct
metadata
set
up
in
your
CS
produce
or
your
new
specs,
so
that
all
that
stuff
flows
into
new
gates
are
there.
Things
like
dependable
I
can
use
incorrectly
all
that,
as
a
name
to
end
is
not
trivial
like
today,
that
is
hours
and
hours
and
hours
of
work
to
get
just
that
much
going.
A
B
A
A
B
A
A
B
I
blogged
about
these
different
terminals
and
they're
all
very
alpha
right,
because
the
terminal
space
in
in
Windows
is
very
in
flux.
Right
now,
because
they're
making
a
move
from
one
PTY
to
another
and
as
such,
all
the
terminals,
the
Connie
muse
and
the
commanders
and
the
fluent
terminals
and
the
terminus
they're
all
switching
over
this
new
format.
So
there's
this
new
kind
of
like
renaissance
of
updated
terminals
for
Windows,
and
none
of
them
really
have
a
good
installer
right.
B
A
B
Stuff
installed
and
for
them
for
those
who
might
be
listening
and
saying
well,
this
is
just
how
Windows
sucks.
Oh
it
sucks
everywhere.
If
you
want
to
install
something
and
it
requires
homebrew,
right
or
Python
or
you
know,
installing
stuff
is
hard
and
has
nothing
to
do
with
your
project.
So
then,
once
your
thing
is
building
now
it's
20%
getting
the
work
done
in
80%,
making
it
sustainable,
reliable
and
buildable
an
installable
yep.
A
A
A
A
A
couple
weeks
ago
on
this
show
like
we
were
very
open
about
where
people
will
be
working,
we
have
more
than
a
whole
person
who's
whose
sole
job
is
just
making
the
build
work
mainly
build
make
it
do
it
stuff,
because
you
know
there
are
structural
changes
every
time
that
we
do
things
and
it
currently
doesn't
include
doing
stuff
like
this
and
I
would
hazard
a
guess.
If
I
went
to
those
individuals
and
said
hey,
we
want
to
get
all
this
stuff
working.
A
A
B
A
A
B
It's
a
little
command-line
thing
and
it
looks
at
your
wife
eyes
and
removes
them
number
one
complaint
isn't
that
it
works
or
doesn't
work,
it's
I'm
missing
a
license
or
I'm
missing
you,
this
I'm
missing
any
of
that
or
it
son
updated
in
in
chocolaty
or
it
doesn't
have
you
know
so
slowly
over
the
years.
I've
added
license
scanning.
A
A
A
B
A
B
A
You
to
work
a
certain
way
to
automate
those
things,
whether
it's
on
versioning
or
releasing
or
tagging,
or
how
you
structure
your
release,
notes
and
generate
your
change
log
lalala,
and
if
you
miss
one
of
those
things
the
automation
breaks
down,
so
you
it
is
always
a
cost
to
the
maintainer
to
have
to
you
know
to
do
this,
to
make
it
easier
for
your
canoe
to
consume.
Of
course,
it
is
best
practice.
Of
course
it
was
in
the
interest
of
everybody
that
you
do
that,
but
it
is
not
cheap.
It
is
not
free.
B
A
They
want,
they
want
good
practice,
automation,
they
want
to
ensure
that
their
tests
run
every
time
for
products
like
op
server
and
they
have
to
spin
up
my
sequel,
servers
and
Redis
servers
and
goodness
knows
what
else
cross-platform
stuff
they
have
all
that
working.
I.
Think
it's
in
that
failure.
Today
and
folks,
like
you,
shouldn't,
move
to
add
your
DevOps,
because
it's
free
for
open
source
and
stuff.
They
were
like
oh
yeah,
but
last
time
we
spent
30
minutes
looking
at
it.
It
seemed
like
it
wouldn't
support
the
things
that
we
wanted.
A
I
just
do
not
have
the
time
to
go
and
sink.
You
know,
probably
I,
don't
know
hundred
hours
to
reset
up
all
those
builds
on
a
new.
It's
not
click.
Click
go
like.
Maybe,
if
you
just
have
a
bunch
of
unit
tests
that
only
have
to
run
on
one
version,
of.net
yeah,
it's
the
and
it's
all
encapsulated
like
true
unit
test.
A
Maybe
it
is
very
simple,
but
as
soon
as
you
need
to
do
integration
test-
and
you
have
third
page
dependencies
and
you
have
servers-
have
to
have
a
lifetime-
that's
managed
they
have
to
be
cleared
out
between
each
run
like.
That
is
a
lot
of
automation
work,
especially
for
an
open-source
library
where
no
one
was
paying
you
to
do
it,
and
everyone
was
complaining
about
the
fact
that
you
don't
it.
So
it
was
interesting.
That's
why
community
is
so
important
in
in
in
open
source
right.
B
A
A
Up
web
hooks
and
that
it's
like
so
that
can
be
a
real
barrier
to
get
over.
Like
you
know,
you
can't
just
walk
up
and
knock
on
the
door
of
an
open-source
project.
I'm
gonna,
take
over
all
your
builds
and
I'm
volunteering,
and
so
you
shouldn't
say
no,
it's
like
well
I,
don't
know
you
from
it
loaf
of
bread
and
if
I
just
give
you
my
admin
access,
like
goodness
knows
what
you're
gonna
do,
yeah
it's
difficult.
It
takes
time.
You
have
to
establish
trust
like
anything
right
before
you
before
you.
B
A
Did
want
to
spend
some
time
before
we
go
today.
I
did
promise
that
we
would
chat
briefly
about
the
changes.
I
talked
about
potentially
bringing
to
the
stand
up,
and
we
should
chat
very
briefly
about
the
update
I
made
to
the
announcement
yesterday
about
a
spinet
called
two
one
packages
running
undone
that
framework.
Let's
do
that
one
first,
okay,
so
we
talked
about
this.
A
A
couple
weeks
ago,
we've
had
a
series
announcements
over
the
last
three
weeks
regarding
dotnet
framework
done
deferments
future
the
plans,
but
not
like
all
three
and
then
some
of
the
other
dotnet
technologies
that
are
obviously
associated
with
net
core.
Three,
like
updates
to
the
language,
was
c-sharp.
That
post
went
out
yesterday,
c-sharp
eight
Visual,
Basic,
Visual,
Basic,
16
or
vision
posted
on
there,
16
I
think
it
was
yesterday.
A
It's
done
it's
down
to
two
point:
one.
We
got
a
post
last
week
talking
about
what's
coming
in,
to
understand
a
two
point:
one
and
how
that
won't
be
applied
to
dotnet
framework,
and
then
there
was
the
post
before
that
my
post
about
a
spinet
core.
Yet
this
one
here
that
you're
showing
now
a
spinet
core.
Three
and
this
post
was
focusing
on
changes,
not
not
new
features.
I'm
gonna
do
another
post
about
features.
A
I
spoke
about
features
on
this
show
last
week
and
then
I/o
the
community,
a
post
about
you,
know
detailing
what
we
know
about
those
features
right
now,
because
the
team
was
actually
started
working
on
them
so
that
the
announcement
there
there's
the
update
that
I
posted
yesterday,
which
was
based
on
feedback
that
we
received
from
a
few
folks
who
have
quite
a
few
folks
in
the
community.
They
would
like
to
have
some
where
to
land
where
they
can
use
a
spinet
call
on
a
runtime
that
is
supported
longer
term
than
the
dotnet
core
LTS
policy.
A
B
A
So
MVC
five-point
X
signal
are
two
point:
X
Web
API
to
point
X:
that's
the
link
that
you're
showing
there,
which
is
the
asp
net,
support
lifecycle
policy,
which
has
clear
details
there
about
end-of-life
for
the
previous
versions,
how
we
treat
these
packages
and,
if
folks,
don't
know,
I
added
those
links
on
purpose.
Obviously,
obviously
so
folks
can
go
in
understand
how
those
are
supported
and
they're
effectively.
You
know
there
is
no
end
time
put
on
that
support
policy.
That
policy
has
been
n
minus
one
for
quite
a
while,
which
is
you
know.
A
We
support
the
latest
version
and
the
version
behind
it.
So
I
think
we've
announced
the
end
of
life
for
MVC
for
and
web
api
one
and
signaler
one
I
believe
it
was
on
that
page.
You
were
just
looking
at
I
think
it's
June
next
year,
which
means
that
the
minus
1
will
become
MVC,
5
and
web
api
and
signal
or
and
then
the
end
will
become
the
age
banette
core
2.1
packages.
A
A
B
A
B
B
A
A
A
A
There
are
a
lot
more
AP
is
available
on
deck
or
now
than
there
were
in
the
first
version,
thanks
to
doc
near
sender,
thanks
to
the
windows,
compatibility
pack,
which
adds
like
I,
don't
know,
20,000,
more
api's
or
something
and
sure
doc.
Nickel
3
is
adding
more
because
we're
bringing
WinForms
and
WPF
and
all
the
underlying
infrastructure
that
supports
that
and
more
api's,
because
it
turns
out
lots
of
wind
forms,
apps
and
lots
of
WPF
apps,
because
they've
run
on
Windows
depend
on
more
of
that
in
their
framework.
A
And
so
we
are
bringing
more
of
those
api's
either
into
the
windows,
compatibility
pack
or
into
dotnet
core
3
itself.
So
Donna
core
3
will
be
the
most
sort
of
API
compatible
version,
of.net
core
without
the
framework
so
far,
but
that's
little
comfort
to
folks
who
are
like
yeah
but
I'm
on
a
spinet
core
I
need
to
keep
running
on
your
framework,
because
these
the
api's
out
here
and
right.
B
A
B
A
I,
wouldn't
even
put
a
number
on
it
like
I,
don't
like
even
saying
it
or
approach
90,
it'll,
it'll
approach,
something
and
I
see
you
know.
We've
only
had
two
versions
so
like
I,
don't
want
to
correlate.
You
know
trying
to
extrapolate
a
history
out
of
that,
but
we
can
certainly
say
there
are
more
coming
in
each
version,
but
it'll
it'll
flatten
out
at
some
point.
A
They
treat
backwards,
compatibility
very
very
seriously,
and
obviously
we
do
for
dr.
framework
as
well,
which
is
why
a
lot
of
these
changes
have
happened.
So
you
can't
do
the
things
inside
dotnet
framework,
because
it
just
breaks
too
many
applications.
It's
on
one
and
a
half
billion
machines,
that's
a
billion
with
a
B,
and
so
we
moving
functionality
over
the
dotnet
core
based
on
customer
demand
and
strategic
alignment
with
where
we
want
the
framework
to
go.
Obviously,
and
we
will
continue
to
one
of
those.
What
are
those
things?
A
And
so
again,
we've
made
this
a
policy
announcement
so
that
folks
can
a
little
more
comfortable
if
they
still
plan
to
move
to
dock
their
core,
but
they
feel
like
they
need
that
stepping-stone
or,
like
you
said,
there
are
scenarios
where
they
want
to
run
on
an
underlying
framework
and
a
web
framework
that
they
know
will
be
serviced
for
a
lot
longer
than
the
3-year
LTS
policy,
then
as
part
of
the.net
core
family
of
products.
Sorry,
so
there's
that
the
other
thing
I
want
to
talk
about
briefly.
A
Was
the
tweets
I
put
out
a
couple
weeks
ago
about
potentially
making
some
changes
to
the
community
stand
up,
so
we
did
get
some
feedback
from
some
other
folks
internally
that
they
would
like
to
be
able
to.
So
we've
seen
this
show's
format
copied
by
a
few
other
teams
over
the
last
four
years,
and
the
dotnet
community
is
obviously
larger
than
just
a
you
don't
know
there
are
other
dotnet
shows
there
is
own
net.
There's
Visual
Studio
toolbox,
there's
a
bunch
of
twitch
live.
A
You
know,
Jeff's
to
a
twitch
live
coding,
show
James,
Monta
Magna
has
one
as
well,
that's
focus
more
on
xamarin,
and
but
they
are
different
shows
with
different
formats.
Okay
and
so
I
am
personally
I
am
sort
of
open
to
having
this
format
being
expanded
to
support
other
workloads
and
other
shows
I
have
no
problem
with
that.
A
The
one
thing
I
am
a
little
scared
of
is
having
in
broadening
the
scope
of
the
show
in
terms
of
the
workloads,
but
then
have
somehow
it
not
be
the
same
show
so
like
you
get
other
people
in
and
they
call
it.
The
community
stand
up,
but
they're
not
really
doing
community
stand
up
things
they're,
not
highlighting
the
community
links
like
John
does
every
week,
they're
not
giving
the
community
updates
on
what
we're
doing
whatever
they're
different
like
so.
A
The
format
of
this
show
is
the
way
it
is
because
this
is
what
I
wanted
it
to
be,
and
because
you
and
I
and
John
have
been
running
this
show
for
three
years.
It's
very
much.
You
know
sort
of
molded
itself
around
how
we
like
to
interact
in
the
type
of
community
engagement.
You
want
to
do
and
I
would
like
that
to
be
preserved
and
I
did
get
that
feedback
from
folks
when
I
stuck
that
out
in
the
community.
So
the
current
sort
of
straw,
man
idea,
is
that
we
kind
of
overall
rebrand.
A
This
thing
is
just
the
dotnet
community
stand
up.
We
would
continue
to
have
the
same
number
of
shows
on
asp.net,
and
so
we
would
still
do
our
thing
of
Tuesday's
alternating
morning
and
afternoon,
our
time
with
the
same
hosts
for
doing
a
spinet
community
as
a
content,
but
then
for
other
branches
of
dotnet,
whether
it's
desktop
development
or
xamarin
development
or
now
whatever
it
might
be.
We
would
have
a
second
show
each
week.
This
is
the
straw
man
right
now.
A
We
can
obviously
modify
there's
a
second
show,
and
then
we
would
have
to
determine
what
the
who
the
hosts
are,
whether
it's
one
of
us
plus
someone
from
that
side
or
whether
it's
just
them
and
not
us
at
all,
and
then
we
would
rotate
those
other
workloads
through
this
other.
The
other
show
that
was
that
was
the
initial
proposal.
Some
folks
said
that
would
be
too
many
shows
I
can't
watch
them
all,
which
of
course,
is
well.
You
don't
have
to
watch
them
all.
A
If
your
only
interest
in
ease
be
on
there
just
to
ASP
name,
some
folks
were
concerned
that
it
would
dilute
the
amount
of
a
spin
at
content
and
so
I
think
no.
The
idea
was
that
we
would
still
have
the
one
show
a
week
like
we
do
right
now,
because
we
feel
there's
enough
content
to
do
that.
We
would
bring.
B
A
Guests
and
do
the
team
thing
like
we've,
been
doing
which
people
like
we'd
have
the
occasional
code
demos,
but
the
focus
of
the
show
is
very
much
showcase:
the
community
contributions
that
we've
seen
in
the
last
week
and
talk
to
the
community
about
announcements
that
we've
made
directions
that
we're
thinking
about
it's
a
communication
channel
right.
It's
not
a
demo
show
there
are
other
shows
like
on.net
and
the
live
coding
shows
which
are
much
more
about
that.
As
I
said.
A
A
B
A
B
We,
if
it's
one
show
a
week
or
two
shows
a
week
whatever,
but
we
need
to
not
miss,
shows
and
transcend
move
shows
to
feels
like
too
much
but
but
I
like
the
idea
of
broadening
it,
and
it
could
be.
You
know
our
demo
this
week
and
guests
that
week
we
could
add
a
little
structure
mm
second
Thursday.
Second
Tuesday
of
every
month
is
demos.
Third
Tuesday
is
announcements,
you
know
really
add
structure
so.
A
The
challenge
I
were
challenging,
we're
there
is.
We
have
attempted
amongst
the
three
of
us.
We
have
said
that
very
thing.
Many
many
many
times
over
and
I
think
we
have
proven
that
the
three
of
us
are
incapable
of
doing
that
or
that
we're
not
prepared
to
put
the
time
in
behind
the
scenes
to
make
that
a
reality,
because
it
takes
time
it
is
not
free
right
that
takes
someone
yeah
you
can
you
live
an
hour
that
is
hours
a
week
to
make
sure
it's
run
that
well
yeah.
A
We
can
walk
out
and
you
know
to
out
you
know
in
our
defense.
It's
work
pretty
well
and
for
whatever
reason,
but
I
am
NOT
against
that.
We
would
simply
need
to
find
someone
who
owns
that
and
loves
it
and
nurtures
it,
and
that
is
part
of
their
job
to
ensure
that
people
are
scheduled.
People
turn
up
on
time.
All
the
technical,
different
things
are
so
I
know.