►
From YouTube: koha-US Sandboxes Webinar 1/16/2020
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
Right
well,
hello,
everyone
and
thank
you
for
joining
us
today.
This
Koha
sandboxes
webinar
is
brought
to
you
by
co.
Hi
us,
the
kohai
u.s.
education
committee
and
by
water
solutions
were
thankful
that
we
could
have
kyle
and
nick
join
the
Koha
u.s.
committee
members
today
to
help
bring
this
webinar
to
you.
So
first
I'd
like
to
present
Lisette.
She
is
the
kohai
US
president
to
just
have
a
few
words
for
us.
A
B
B
A
B
We
are
going
to
show
you
quickly
how
to
use
the
sand
boxes
so
just
a
little
bit
of
background
on
what
the
sandbox
is
are.
Basically,
when
you
come
here.
This
is
our
link,
SB
or
SB,
once
an
boxes
that
buy
whatever
solutions.
Comm.
This
is
our
sandbox
a
server,
and
when
you
come
here,
you
can
create
a
new
server.
A
sandbox
is
going
to
give
you
a
fully
installed
development,
koha
environment.
This
will
be
for
all.
B
This
is
a
you
know,
a
running
koha
there
will
be
patrons
in
it.
There
will
be
items
in
it
and
you
can
go
here
just
to
if
you
want
to
test
out
some
functionality.
You
can
try
that
if
you
want
to
test
patches
which
is
kind
of
what
they're
designed
for
you
can
do,
that
there
is
for
some
background,
wiki
co-hosts.
B
So
let
me
see
if
this
has
come
up
yet:
hey
we've
got
one
that
is
ready.
That
will
be
good.
So
when
you
come
here,
the
first
thing
your
own
going
to
want
to
do
is
set
up
your
new
sandbox.
You
can
see
usually,
who
has
created
the
sand
boxes.
This
just
lets.
You
know
you
know
who
owns
it:
who's
testing,
what
there's
a
description
here
you
can
include
that
or
not,
but
we'll
go
through
the
creation
form.
So
if
I
click
create
here,
what
I
get
is
this
form
your.
D
B
B
Thanks
Kyle
enter
a
sandbox
name.
Now
note
this
little
text
down
here.
It
needs
to
be
lowercase
all
letters
and
numbers
generally.
This
is
going
to
be
the
name
of
what
you're
testing,
so
we
can
just
use
the
bug.
I've
pulled
up
a
few
bugs
here.
They
happen
to
me,
be
my
bugs
that
need
sign
of
I
just
pulled
a
few
sample
ones
for
us
to
look
at,
so
you
give
it
a
name,
a
sandbox
number.
This
is
where
you
can
put
the
number
of
the
patch
you
want
to
test.
B
If
you
want
to
start
up
your
sandbox
with
that
patch
applied,
you
can
leave
this
blank.
If
you
leave
it
blank
you'll
get
a
current
community
master
which
is
sort
of
the
and
the
head
of
the
development
version.
It's
all
the
most
recent
patches
that
have
been
pushed
and
will
be
included.
The
next
kelabra
lease
yeah.
B
Get
remote
and
branch
occasionally
there
are
a
patch
sets
that
are
real
big.
They
have
a
lot
of
changes
and
they're
too
big
to
go
into
logzilla,
and
so
the
co,
developer
or
developer
will
actually
set
up
a
remote
git
repository
with
them
there.
If
I
have
already
scared
you
off,
that's
fine,
you
don't
have
to
test
those
patches.
Otherwise
what
you'll
do
is
you'll
enter
the
repository
URL
and
the
name
of
the
branch
I
think
that's
probably
a
little
more
advanced
than
we're
gonna
cover
today,
yeah
that.
B
And
you
can
always
reach
out
to
us
at
slack
or
IRC.
If
you
want
to
do
that,
and
you
have
any
questions
if
you
hit
one
of
those
rare
bugs,
and
that
goes
for
anything
that
you
see
today,
just
Kyle
and
I
are
both
available.
He
is
cayhall
an
IRC
and
I
am
kit,
clamp
and
salmon
slack
and
if
you're
not
part
of
our
selection,
I'll
talk
to
Margaret
or
anyone
on
the
support
team,
all
right
description.
This
can
be
whatever
you
want.
A
B
B
So
the
login
information
is
here:
if
you
need
to
log
in
initially
koha
and
koha
are
the
username,
the
password
and
the
database
user,
which
you
shouldn't
need
for
much,
but
if
you,
if
it
does
ask
for
it,
it's
just
this
koha,
the
sandbox
name
that
you
put
up
here
and
one
password
password
so
I'll
hit
submit
you'll,
see
now
that
we
have
on
this
page
the
list
of
things
that
are
elusive,
sand
boxes
that
have
been
created.
If
we
refresh
the
one
that
we've
just
created
says
provisioning.
B
Fortunately,
we
set
up
this
one
ahead
of
time
now,
when
I
set
up
this
one
I
left
the
bug
number
blank.
So
there
are
no
patches.
This
is
actually
master,
but
I
did
set
it
up
to
test
bug
2
for
4
to
3.
So
let's
go
look
at
that
bug
and
we
can
see
what
it
is.
If
you
want
to
test
a
bug,
there
should
be
a
test
plan
there.
B
B
B
B
And
find
a
bit
with
at
least
one.
I
don't
we'll
start
with
this
one
from
detail:
PL
use
the
check
boxes
in
the
holdings
table,
select
one
or
more
items.
So
when
we
click
on
that
record,
that
takes
us
to
detail
dot
PL
a
lot
of
times,
that's
the
language
that
developers
really
use.
When
writing
test
patches.
We
will
name
the
script
that
you're
on
without
necessarily
saying
how
to
get
there
we'll
try
to
do
better.
B
B
So
now,
this
next
step
is
apply
patch.
So
this
is,
if
you've
created
the
sandbox
without
the
bug
already
applied.
This
is
where
we
can
go
and
use
one
of
the
features
of
the
sandboxes
that
we
have
these
actions.
We
have
a
few
options
here.
We
have
research
services.
This
is
one
that
if
it
says
to
restart
everything
in
the
test
plan,
that's
what
you
would
click
full
zebra
re-index
build
CSS.
These
are
all
things
that
should
be
indicated
in
the
test
plan.
B
B
We
can't
interact
with
this.
If
you
see
this,
where
it
just
ends
with
asking
you
a
question,
everything
has
worked
as
it
is
supposed
to
do.
Not
worry
that
you
cannot
answer
that
question.
It
has
been
answered.
The
script
will
automatically
say
yes
to
this
and
then,
if
there
are
any
errors,
I
believe
they
will
show
up
here,
but
in
this
case
the
patch
applied.
If
it
didn't,
that's
where
you
would
use
the
status
in
the
bug
called
patch
does
not
apply,
and
you
would
just
say,
I
tried
to
apply.
B
It
didn't
work,
but
it
did
so
I'm
gonna
close
this
and
go
back
over
to
the
sandboxes
and
just
because
it
never
hurts
I'm
gonna
hit
restart
services
that
just
restarts
memcached
plaque
Apaches,
some
other
things
on
the
server
to
make
sure
that
we're
using
the
up-to-date
version
of
the
code.
So
I
can
click
back
over
here
and
start
the
test
plan
over.
B
So
the
next
step
is
just
to
say:
okay,
I've
applied
the
patch
I
have
test
with
the
patch.
Now
what
I
want
to
do
is
sign
off
on
the
patches
when
you're
signing
off
all
you're
doing
is
confirming
that
you
have
followed
the
test
plan
and
it
did
what
it
said
it
would.
You
don't
have
to
worry
about,
checking
that
it
doesn't
break
anything.
That's
QAS,
job
and
they're,
very
good
at
it.
They're
very
particular.
B
So
when
we
click
that
little
sign
off
button
under
actions
will
get
sent
to
this
page,
your
name
will
be
copied
over
from
what
you
put
in
before
stand
with
your
email.
Please
make
sure
both
of
these
are
filled
out.
This
is
so
that
you
will
get
credit
in
the
release,
notes
for
having
helped
us
test
a
patch
for
Kohana.
It's
exciting
the
bug
number
and
the
number
of
patches
now
the
number
of
patches
you
need
to
go
and
look
and
physically
count
this
yourself.
B
B
Note
this
little
thing
down
here
at
this
time
the
signup
cool
does
not
set
the
status
of
the
bug
to
signed
off.
So
all
this
will
do
is
attach
your
patches.
If
we
hit
submit
and
wait
a
few
moments,
you'll
be
able
to
see
what
I
mean
okay,
so
again
we
get
the
command
line
stuff
again.
It
ends
with
the
question
assumed
that
it
happens.
B
If
you
click
back
over
here
to
the
bug
and
you
reload
the
bug,
what
you'll
actually
see
down
here,
is
that
now
it's
signed
off,
so
it
says
Bywater
sandboxes,
because
that's
who
technically
signed
it
off,
but
then
your
name
is
put
down
here
as
the
person
who
signed
it
off
and
tested
what
you
would
do
now
once
you've
done.
That
is,
you
would
go
up
to
here,
say
signed
off
and
you
could
say,
tested
with
a
sandbox
works
great
or
whatever
you
want
to
do.
You
don't
even
have
to
say
anything.
B
B
Studying
into
science,
silence
is
golden
now.
One
thing
I
will
note
just
here,
so
we
spun
up
the
sandbox
we
tested
bug
two
four
four
two
three
I
did
spin
up
a
second
sandbox
that
and
I'll
refresh
to
make
sure
that
it
is
provisioned
to
test
two
four,
two,
three
six,
it's
possible
that
I
could
just
decide
to
use
this
same
sandbox
and
test.
Another
bug.
I
could
just
go
here
and
hit
apply
patches
and
apply
the
patches
for
two
for
two
three
six
to
this
sandbox
as
well.
B
There
are
instances
where
two
patches
will
affect
one
another.
So
if
you
decide
to
test
on
a
single
sandbox
and
either
you
get
problems
during
the
application
or
problems
during
testing,
you
may
want
to
retest
with
just
the
single
patch
applied,
just
to
make
sure
that
you
haven't
gotten
any
sort
of
cross
contamination
from
the
two
bugs.
That's
only
likely
if
they're
two
bugs
that
are
very
related,
that
are
kind
of
touching
the
same
code
question
for
you,
Kyle
our
depends
on
links
followed
automatically
for
the
sand
boxes.
Ooh.
E
B
What
I
wanted
to
see
was
now,
if
so,
you'll
see
now
that
the
bug
number
applied
to
this,
it's
now
updated
it
to
two
four
two,
three
six,
even
though
we
have
two
sets
of
patches
applied,
we
have
two
four
four,
two
three
and
then
two
four,
two
three
six.
It
shows
me
the
most
recent
one
so
at
least
for
testing
I'll
always
know,
which
is
the
most
recent
one
that
I
provide
so.
E
E
E
The
next
one
is
the
Quahog,
so
you
can
see
after
we
create
the
sandbox.
We
do
a
whole
lot
of
setup
to
create,
like
all
those
items
and
those
patrons
that
default
data,
then
we
index
the
the
records-
that's
everything
you
see
in
here,
so
if
you
like,
where
to
reindex,
you
would
see
things
here
if
there
is
the
rare
test
plan
that
says,
look
at
the
error
log
and
like
see
that
there
is
this
error,
and
this
patch
makes
it
go
away.
E
This
is
where
you
would
look
for
that
error,
so
it
all
you
have
to
do
is
just
hit
refresh
to
keep
updating
and
to
see
the
latest
stuff
in
the
log.
If
you
go
back
there
I,
we
also
have
the
other
logs
too,
so
it
might
specifically
reference
the
plac
log,
the
Internet
era
log
or
the
OPAC
log.
We
have
those
three
things:
let's
just
put
it
at
that
and.
E
The
really
useful
one
for
knowing
what
the
heck
patches
you
have
applied
to
a
sandbox
is
the
Quahog
git
log.
This
is
where
you
can
open
it
up
and
see
exactly
what
bugs
have
been
applied.
So
you
can
see
those
two
bugs
that
Nick
applied
there
right
at
the
top.
That
way,
if
you're,
unsure
of
what's
been
done
to
this
sandbox,
you
can
just
open
this
up
and
you'll
know
exactly
which
bugs
are
on
that
sandbox.
B
B
A
I'll
watch
the
chat
and
see
if
more
questions
come
in,
but
maybe
it
would
be
a
good
time
Lisette.
Just
if
you
could
share
a
few
words
like
you're
working
in
a
library
and
even
at
Koha
us.
The
annual
conference
this
year
was
that
got
up
in
front
of
the
crowd
and
showed
everyone
how
to
sign
off
on
a
patch
so
Liz.
That
may
be
some
like
encouraging
words
to
share
with
people
who
might
be
a
little
nervous
about
getting
started.
Yeah.
C
So
the
first
couple
times
I
signed
off
on
patches
were
I
was
really
afraid,
especially
when
something
went
wrong,
because
I
didn't
want
to
mark
anything
as
didn't,
apply
or
failed
QA.
When
it
didn't
do
it,
it
said
it
wanted
to
do,
but
everyone
was
always
really
but
I.
Just
well.
I
did
I
did
it
anyway,
and
then
everyone
was
always
really
nice
about
it,
because
I
was
afraid.
Some
was
gonna
be
like.
Why
do
you
keep
failing
my
patches,
cuz
I
kept
testing
like
the
same
people's
patches
cuz?
C
C
Library
and
I
kept
failing
you
guys's,
patches
and
I
was
afraid
that
you're
gonna
come
over
and
be
like.
Why
are
you
failing
all
my
patches
and
instead
they
came
over
and
they
were
like
hey
thanks
for
testing
all
those
patches,
and
so
like
people
just
want
their
patches
tested
and
if
it
doesn't
work,
they'd
rather
know
you
know
sooner
rather
than
later.
C
If
you're
doing
a
bunch
of
different
patches,
like
I,
did
five
patches
in
a
week
a
couple
weeks
ago
that
we're
all
just
little
typos
and
they
all
worked,
but
I
was
glad
that
they
all
got
tested
that
week,
because
then
I
remembered
you
know
if
any
of
them
had
failed
where
I
went
to
do
it.
So
that's
helpful.
Oh
yeah
and
the
dashboard
is
really
great.
That
Kyle
is
bringing
up
because
it
shows
you
know
what
needs
sign-off.
C
C
If
you
go
and
try
signing
them
off
a
lot
of
times,
they
fail
to
apply
because
they're
on
code
that
doesn't
match
up
anymore,
and
so
then
that's
good
to
do
too,
because
then
you
can
get
them
out
of
the
sign
of
cue
sign-off
queue
and
people
know
that
they
need
to
go
back
and
fix
them
if
they
still
want
that
to
go
through
and
there's
a
few
things
that
we've
signed
off.
That
I've
signed
off
on
here
that
we
were
really
excited
for
at
our
library.
C
That's
in
the
system
now,
and
so
that's
been
helpful
because
we've
been
able
to
push
along
some
things
that
we're
kind
of
hovering
and
you'd
sign
off,
especially
enhancements.
Don't
always
get
off
right
away
if
they're
not
sponsored,
because
almost
the
we're
worried
about
fixing
like
that,
oh
yeah,
so
he's
like
an
enhancement
or
new
statuses,
normal
alright.
B
Only
teasing
so
I
think
what
we
were
just
highlighting
was
the
different
statuses
here
in
Bugzilla.
Lisette
was
talking
about
her
experience,
getting
started,
which
I
will
echo
as
well
I.
Remember
when
I
first
started
testing
I
was
always
testing
Kyle's
patches
and
always
failing
QA
on
them
and
I
was
pretty
sure
that
Kyle
did
not
like
me.
Then
it
turns
out
that
Kyle
wanted
them
to
hire
me.
So
that
was
great.
B
B
See
like
the,
let
me
see
you
zoom
in
a
little
bit,
all
the
enhancements
are
highlighted
in
kind
of
a
light
gray
and
all
the
bugs
are
in
a
darker
black
and
then
the
more
severe
bugs
are
in
the
darker
red.
So
when
you've
gone
to
the
dashboard
and
gone
to
the
neat
sign-off
list,
you're
looking
for
things,
these
red
ones
are
often
the
ones
that
would
be
dire.
A
B
Testing
these
are
also
nice
because
the
ones
that
are
marked
as
bugs
are
typically
the
ones
that
will
get
backported.
So,
if
you're
facing
an
issue
generally,
what
will
happen
is
Kyler
and
I
will
write
a
patch
and
then
we'll
say:
hey
we
put
it
in
community
if
you
can
test
it.
That
would
be
great,
and
this
is
the
process
that
you
can
use
to
do
that
to
help
us
out
and
help
get
these
things
back
into
your
Kohana.
It's
also
true
for
enhancements.
B
If
you
have
paid
for
a
development,
the
best
thing
you
can
do
once
we
submit
that
code
is
to
come
here
and
test
it
yourself.
Not
only
will
it
help
move
it
ahead,
but
it
will
allow
you
to
go
through
what
we've
done
and
verify
that
everything
works.
As
you
expected
you,
and
so
just
to
highlight
one
more
place
over
here
on
the
dashboard
again
at
the
very
top.
We
have
this
little
green
link.
That
is
a
link.
It's
got
the
little
care
there
kind
of
to
help.
E
Yeah,
thank
you.
I
was
going
to
point
that
out.
Next,
though
that
is,
Kelly
is
right
there
to
keep,
because
any
given
server
can
only
handle
so
many
sand
boxes
and
a
lot
of
people
don't
tend
to
clean
up
after
themselves.
You
can
delete
your
sandbox
manually
with
that
big
red
delete
button
after
you're
done
with
it,
but
sometimes
people
forget
and
it
just
sits
there.
A
lot
of
people
fear
deleting
someone
else's
sandbox
because
maybe
they're
still
using
it.
So
basically
we
have.
We
have
an
expiration
time
on
it
24
hours
from
then.
E
E
Another
thing
I
want
to
say
is:
if
you
are
a
heavy
sandbox
user,
and
you
would
like
your
own
server
like
this,
it
is
very
I'm
going
to
say
fairly
easy
to
set
one
up.
Maybe
your
library
has
some
servers
and
they
have
a
some
space
to
give
you
to
have
your
own
server
yeah.
It's
that
top
one
I,
basically
to
set
this
up.
E
All
you
do
is
it
needs
to
be
a
debian
server
with
ansible
installed,
and
then
you
run
that
on
setup,
sandbox
server
and
it
does
everything
else,
there's
a
few
things
that
you
can
set
and
and
then
you'll
be
off
and
running,
and
that
one
you
can
choose
all
the
things
you
can
choose,
whether
to
have
an
expiration
time
or
not.
How
many
renewals
that
way,
maybe
you
can
just
have
those
in
boxes
around
indefinitely
on
your
own
personal
playground.
E
E
D
And
then
there's
just
one
more
thing
that
I
thought
of
when
Liz
was
talking
is,
if
you
do
have
a
comment,
or
you
really
can't
understand
that
says
plan
or
you
have
questions
for
the
developer,
but
you
want
to
be
able
to
sign
off
on
it.
You
should
add
a
CC
to
the
bug.
So
you'll
know
when
the
developer
comments
back
and.
E
D
If
you
add
yourself,
then
you'll
know
because
I
feel
as
though
a
lot
of
the
developers
who
have
patched
or
who
have
things
that
want
to
be
signed
off
on
are
waiting
for
feedback,
so
it
can
move
on.
So
there
I
found
they're
very
quick
to
respond,
and
then
you
can
pop
back
into
the
sandboxes
and
and
either
sign
off
or
make
more
comments.
If.
B
B
D
You're
welcome
right
before
we
got
like
shaken
up
a
little
bit.
Somebody
did
ask
to
see
another
patch
signed
off
Nick,
okay,.
B
It
was
not
one
of
ours,
but
so,
let's
see
if
we
go
back
to
the
same,
because
I
had
just
applied
to
for
two
three
six
to
this
next
sandbox,
so
we
can
test
this
one
out
if
anyone
has
another
one
that
they
want
to
see,
go
ahead
and
you
can
put
a
link
in
the
chat
or
let
us
know-
and
we
can
test
it,
but
I'll
just
carry
on
with
this
one.
So
this
one
again,
we
should
look
at
the
test
land.
B
It
should
tell
us
what
to
do,
or
it
should
tell
us
what
the
problem
is.
This
is
when
you
do
a
search
that
has
multiple
page
results
in
cataloging.
If
you
do
that
searching
quotations,
it
will
not
allow
you
to
advance
the
page,
so
we
can.
Unfortunately,
we've
already
applied
the
patch,
which
means
that
we
can't
do
these
first
four
steps.
We
can
just
kind
of
trust
it
there.
That's
why
generally
I
like
to
bring
the
same
boxes
up
empty
first
and
apply
the
patch
after
the
fact,
but.
B
So
we
click
on
staff
again
for
either
one
of
these
we
go
to
cataloging
and
we
just
do
a
search
for
I'm
gonna.
Do
a
search
for
a
because
I
know
that
cat
won't
get
us
enough
results
in
the
sandbox.
B
B
B
And
this
is
a
good
point
to
point
out
that
you
know
I
did
in
that
test
plan
I
just
assumed
that
you
knew
how
to
enable
system
preferences
and
where
to
find
them,
and
all
of
that,
if
you
don't
feel
free
to
ask
the
first
person
who
test
this
bug
was
in
Micah
who
I
don't
know
if
she's
in
our
group
today,
but
when
she
tested
she
could
not
recreate
the
problem,
and
that
may
be
because
I
didn't
specify
what
I
met
by
cataloging
search
that
could
have
met
a
Z
3950
search.
B
B
Yeah
I
can
still
paginate.
Are
there
statistics
of
the
number
/
last
numbers
of
current
record
types
for
the
database,
as
provided
during
a
fresh
sandbox
provision?
I,
don't
know
that
we
have
any
of
that
listed
anywhere.
I
can
tell
you
off
the
top
of
my
head.
There
are
436
Records
installed
when
you
install
the
sample
database
and
there
are
709
Authority
records
installed.
That
data
is
actually
all
out
in
the
Quahog
github
in
the.
B
Yes,
so
this
is
the
Quahog
miscellaneous
tools
for
developers
that
actually
lists
all
of
the
stuff.
This
is
what
we
use
to
run,
that
log
that
installs,
the
super
library
and
installs
all
the
files-
and
this
do
you
can
do
PL.
The
data
is
here
in
the
data
sequel
mark
21.
There
is
only
mark
21
data
right
now.
That
is
what
is
done
standard
and
here
there's
the
Biblio
sequel.
The
item
sequel,
and
I
think
that
these
are,
we
don't
have
like
mark
records.
We
just
force
install
the
data
directly.
B
B
B
B
B
B
B
This
is
just
really
community
rules
so
that
a
developer
can't
just
sign
off
their
own
patches
and
get
them
through
community.
In
fact,
Kyle's
not
allowed
to
sign
off
on
my
patches
and
I
can't
sign
off
on
Kyle's
patches,
and
we
can't
QA
each
other's
patches
because
apparently
we're
too
invested,
although
I'm
really
happy
to
feel
QA
on
Kyle's
patches.
Like
thank
you.
Oh
sorry,
Kyle
still
here.
E
A
B
Yeah
and
we're
definitely
like
any
problems
that
you
hit
any
questions
that
you
have.
We
are
happy
to
help.
The
sandbox
is:
do
support
elasticsearch
right
now,
however,
they
don't
index
the
records
into
elastic
and
you
don't
have
that
tool.
But
if
you
want
to
test
something
on
the
sandbox
just
catch
us
in
IRC
or
slack
and
poke
us,
and
we
can
actually
go
into
the
backend
and
reindex
the
last
and
I'm
very
happy
to
do
that
to
get
elastic
patches
signed
off
on
so.
A
B
B
So
applying
the
patches
will
automatically
run
any
database
updates
that
are
on
the
bug.
So
you
won't
need
to
worry
about
that
part,
which
is
good.
Having
done
that,
though,
I
am
going
to
still
restart
all
the
services.
Well,
actually,
let's
reload
the
page,
because
that'll
show
me
that
I
applied
it
and
then
I
can
restart
the
services.
B
B
It
keeps
adding,
without
this
passed
the
same
library
for
several
times
with
this
patch.
You
will
see
a
friendly
error
message:
I
applied
the
patch
I
did
the
upgrade,
but
I
don't
see.
E
B
B
B
D
B
E
B
B
B
B
E
Ahead,
oh
I
didn't
mean
to
cut
you
off
there.
No,
no,
no
that's
fine,
I
would
say
any
that
tells
you
to
run
scripts
at
the
command
line.
I
do
remember
a
long
ago
adding
a
feature
we
have
not
enabled
that
would
allow
you
to
ssh
into
your
sandbox
machine,
but
we
are
fully
we're
trying
to
fully
explore
the
security
implications
of
that
before
we
turn
it
on
and
once
that
is
enabled,
then
there
is
very
little
that
you
would
not
be
able
to
do
with
the
sandbox.
E
B
So
would
be
anything
that
says:
command-line
you're
not
gonna,
be
able
to
do,
but
I
believe
that
sip
actually
might
run
out
of
the
box,
and
if
it
doesn't,
it
will
very
soon
and
then
you
would
actually
be
able
to
well.
You'd
have
to
have
this
if
command-line
installer
installed
locally,
but
you
would
technically
be
able
to
hit
the
server.
B
We're
all
waiting
for
George
to
type
we're
watching
the
chat
for
the
listeners
out
there,
so
you
can
see
along
the
header
at
the
top
somewhere
next
to
co-host.
Sandbox
is
home,
create.
Could
you
add
a
link
to
a
set
of
instructions
on
how
to
use
the
sand
boxes?
That's
a
really
great
idea
to
have
a
link
to
the
sand
boxes.
Wiki
here
and
possibly
we've
done
several
demos
of
the
sand
boxes
and
things
like
that.
So
that
might
be
some
useful
things.
I
mean
even
just
some
other
useful
links.
This
video,
yes
I,
was.
A
I
think
we
have
a
Monday
minute
on
one
of
them,
two
about
just
how
to
fill
out
the
form.
So
we
can.
We
can
link
to
those
things
so.
E
Yeah
please
once
you're
here
you
can
see
this
issues,
tab
which
it
was
I
was
about
to
bring
up,
I,
feel
free
to
file
issues
where
you
run
into
bugs,
like
our
sign
off
bug
or
enhancements.
That
would
be
nice
and
useful.
B
You
will
need
a
github
account
if
you're
going
to
do
this
I'm
signing
up,
for
that
is
simple.
Basically
a
web
form
again,
but
if
you
have
one
that
you
can
come
in
and
comment
on
any
of
those
sandbox
issues
here
or
anything
else
that
is
in
our
github.
There
are
plugins
here
and
other
things
like
that,
but
again
I'm,
just
I'm
just
talking
because
they've
given
me
a
microphone.
Yes,.
B
D
B
E
A
Thank
you.
You
guys
did
great
and
we're
terribly
sorry
for
the
zoom
going
down
in
the
middle
of
the
session
there.
I
will
splice
them
together
and
send
that
link
out
on
the
kohai
us
website.
So
if
anyone
wants
to
go
back
and
watch
it,
you
can
we
watch
it
it'll
be
available
on
demand
within
the
next
day
or
so,
and
I'd
like
to
just
greatly
thank
kohai
us
first
starting
these
education
hours
Lisette.
Thank
you
so
much
and
also
a
big
thank
you
to
Kyle
and
Nick.