►
From YouTube: 2023 07 20 Docs Office Hours
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
Okay,
hello
and
welcome
to
the
Jenkins
documentation
office
hours
today
is
July
20th
2023,
and
this
is
the
EU
us
version.
A
Today
we
have
myself
and
Bruno
Mark
Waits
on
p
on
well-deserved
PTO,
so
hopefully
you're
enjoying
his
time
off
and
we'll
see
him
when
he
gets
back
just
briefly
tonight's
or
July
21st
Asia
docs
office
hours,
it's
canceled
because
Mark
is
on
PTO
and
he's
unavailable,
we'll
just
remind
again
at
the
end
of
the
session,
but
just
put
that
out
there
today
on
the
agenda,
so
a
couple
blog
posts
that
were
recently
posted
LTS
information
and
next
LTS
information.
A
Last
week's
security,
advisory,
quick
updates
on
Google
summer
of
code,
the
transition
for
Java
17
usage
in
the
documentation,
a
couple
open,
pull
requests
of
Interest,
some
notes
on
devops,
World,
Tour
and
again
Mark's
well-deserved
PTO,
and
how
that
affects
the
scheduling
going
for
the
next
session.
A
Sounds
good
so,
first
up
the
blog
post,
so
just
the
last
week
or
two
we
had
the
June
newsletter
published
and
Damien
deportel
actually
wrote
up
a
nice
post-mortem
for
the
infrastructure
outage
that
happened
on
I
think
it
was
July
7th
that
it
came
up
really
goes
into
detail
talks
about
their
actions,
how
they
figured
it
out
what
they
were
going
to
be
doing
in
the
future
to
alleviate
that
and
prepare
better
next
time.
A
So,
just
really
great
information
here,
if
you're
curious,
feel
free
to
check
it
out.
We
had
the
weekly
release
2.415
this
past
Tuesday
went
through
successfully
and
coming
up.
Next
week
we
have
LTS
2.401.3
to
be
released,
that'll
be
on
Wednesday
July
26th
changelog's
already
been
merged
at
this
point
in
time.
A
So
that's
good
to
go,
not
a
whole
lot
there,
since
we've
been
have
been
pretty
successful
lately,
so
yeah
I,
don't
know,
I'll
be
ready
to
go,
and
then
the
next
LTS
Baseline
discussion
has
started
in
the
developer
mailing
list
right
now,
the
for
the
front
runner
looks
to
be
2.414.
It's
been
very
successful,
no
issues
to
speak
of
or
any
issues
that
have
come
up.
We've
been
discussed
in
that
mailing
list.
A
Conversation
2.414
has
been
supported
by
most
people
and
it's
actually
been
accepted
by
Tim
Jacob
as
the
release
officer.
So
that's
most
likely
going
to
be
the
case.
The
change
log
and
upgrade
guide
will
need
to
be
created
for
that,
but
this
is
going
to
be
happening
sometime
later
in
August,
so
we
still
have
time
to
get
that
taken
care
of.
A
Last
week
there
was
a
security
advisory
published.
This
was
for
plugins.
Something
to
note
with
this
advisory
is
there
at
the
bottom
of
the
list.
There
are
a
list
of
security
vulnerabilities
that
are
no
have
no
fixes.
A
One
thing
that
we
pointed
out
last
week
was
the
Rebuilder
plug-in:
that's
actually
been
removed
from
the
suggested,
install
plugins,
it's
still
available,
if
you
want
to,
but
it's
been
removed
from
the
default
and
recommended
plug-in
installations
once
installing
Jenkins
as
of
I
think
it
was
backboarded
actually,
as
of
2.401
point,
two
I
could
be
wrong,
but
actually
no
that
would
have
been
way
too
far
back
I.
Think
if
anything
is
backboarded
into
the
weekly
release,
forget
exactly
but
it's
been
remote
View.
B
A
B
A
Yep
so
yeah,
so
the
we
have
been
made
aware
of
these
things.
The
security
team
is
actually
working
on
making
sure
this
is.
You
know,
noted,
and
the
infrastructure
team
is
also
making
sure
that
these
things
are
resolved
and
these
issues
are
sorted
so
just
great
work
by
everyone
overall,
all
to
help
keep
Jenkins
healthy.
So
thanks
to
everyone
for
their
incredible
work
on
this
Google
summer
of
code
has
been
moving
along
nicely,
so
we
just
had
the
midterm
presentations
a
couple
weeks
ago.
A
Last
week
we
had
the
mentor
evaluations
due
things
are
making
great
progress
for
the
most
part.
Thank
you
very
much
to
the
participants
for
joining
up
and
and
doing
all
this
work
and
the
recording
from
the
midterm
presentations
is
available.
If
you
want
to
go
back
and
watch
it,
everyone's
able
to
just
bring
a
lot
of
perspective
and
share
their
work,
their
progress,
their
challenges-
and
it's
really
nice
to
just
get
that
Insight
from
the
folks
that
are
on
this
project.
A
So,
thanks
to
all
the
participants
for
their
constant
work
on
this
and
everything
so
far
and
really
massive,
thank
you
to
all
the
org
admins
Bruno
Alyssa,
jean-mark,
Chris
Stern,
for
helping
make
sure
this
is
successful
and
running
this
and
being
the
guidance
that
we
all
need
in
this,
so
really
great
and
just
something
that
we'll
be
looking
forward
to
in
the
future
the
jenkins.io
site,
building
being
built
with
alternative
tools.
So
right
now
the
testing
is
being
done
with
antora.
A
So
this
would
actually
a
lot
more
closely
align
with
other
Tech
documentation,
for
instance,
Cloud
Bees
No
uses
that
I
know
and
various
other
Solutions
and
other
platforms
I'm.
Using
this
too.
It
allows
for
version
documentation,
which
is
great,
so
we
can
have
the
various
LTS
and
weekly
release
versions,
documentation,
support
them
directly
and
specifically
so
that
no
more
issues
in
the
future
of
having
to
worry
about
well
we're
putting
like
the
Java
17
transition.
A
Obviously,
Java
17
wouldn't
be
supported
by
older
versions,
but
we
can
make
it
so
that
the
documentation
reflects
that
by
making
sure
that
it's
attached
to
the
correct
versions
so
I
think
it's
gonna.
Be
really
nice
and
the
amount
of
work
that's
been
done
here
has
been
really
great.
A
The
navigation
is
really
smooth.
Everything
is
presented
really
cleanly
and
even
things
like
I
think
it
was
just
an
Administration
yeah.
Something
I
noticed
last
time
when
we
looked
at
this
things
like
the
reverse
proxy
configuration
would
normally
have
to
be
clicked
into
to
actually
see
this
on
the
page,
but
in
the
intoria
version
of
the
documentation,
the
drop
down
actually
expands,
which
is
nice.
The
collapse
is
removed
and
we
can
see
all
the
different
reverse
proxy
options
as
opposed
to
right
now.
A
If
we
were
to
look
the
same
thing,
you
can
see
here
it's
just
one
option,
but
then,
if
we
click
it,
you'll
get
the
list
of
reverse
proxy
options.
So
little
things
like
that
having
to
scroll
down
the
navigation
here
versus
not
having
to
is
nice
too
everything's
just
present,
so
lots
more
to
come
with
that.
There's
still
plenty
of
work
to
be
done,
but
yeah.
It
looks
really
good
and
thanks
Stephanie
for
doing
that.
Work.
A
Foreign.
As
far
as
the
Java
11
to
Java
17
transition
goes
so
I've
made
some
a
good
amount
of
Headway.
In
the
last
couple
weeks,
I've
been
able
to
update
a
lot
of
the
regular
documentation
for
Java
17.,
so
things
like
the
Linux
installation,
docs
Docker
installation
docs,
using
Docker
in
pipeline
architecting
for
manageability.
You
can
see
a
list
here
and
we
do
have
an
issue.
A
I
didn't
link
it
here
for
some
reason,
but
the
issue
is
currently
tracking
all
of
the
pull
requests
and
has
a
list
a
running
list
of
what
we're
updating
I've.
Also
as
of
I,
want
to
say
yesterday,
we
now
actually
have
instructions
on
upgrading
the
Jenkins
Java
version
from
11
to
17..
Darren
popes
created
a
video
that
actually
walks
this
walks
through
this.
So
we've
included
that
and
for
the
most
part,
the
instructions
are.
A
You
know
one
for
one
for
the
8
to
11
instructions,
biggest
differences,
things
like
the
Java
web
start
being
removed.
Don't
need
to
be
called
out
here
since
we're
going
from
a
point
where
it
already
has
been
in
an
11
to
17,
which
still
doesn't
include
it.
A
So
we've
cut
out
any
unnecessary
info
here,
but
we
want
to
make
sure
that
this
is
a
seamless
experience
and
that
people
are
able
to
follow
the
instructions
and
get
the
results
they
need.
One
of
the
bigger
things
that
we
changed
is
just
making
sure
that
people
have
their
plugins
updated
prior
to
doing
any
sort
of
updating
yeah.
This
is
a
hugely
important
step
that
it
was
not
actually
put
into
the
8
to
11
upgrade
so.
A
Put
it
here,
I'm
probably
going
to
go
back
honestly.
It
might
not
go
back
and
update
the
8
to
11,
since
that
won't
be
in
love
with
it
soon
enough.
But
updating
plugins
before
upgrading
everything
is
hugely
hugely
important
in
the
process
and
once
again
doing
so
after
you've,
upgraded
Jenkins
as
well.
Making
sure
that
everything
is
properly
updated
and
supported
is
crucial,
so
make
sure
I
put
that
in
here
and
might
add
some
more
context
into
the
upgrading
plug-in
sections.
A
B
A
Yeah
and
it
there
are
any
number
of
stories
out
there
about
what
happens.
If
you
don't,
you
don't
have
to
look
far.
A
You
can
search
on
community.jenkins.io
and
there
is
plenty
of
other
resources
out
there,
but
that's
something
that
we
want
to
try
and
occur
going
forward
so
making
sure
that
we
have
that
explicitly
called
out
is
Step
number
one
and
all
this
being
said
so
right
now,
there's
nothing
tentatively
planned
but
I'm
thinking
that,
with
all
of
these
updates
in
transition,
a
blog
post,
announcing
it
and
sharing,
that
would
probably
be
a
great
idea
so
once
I've
actually
gotten
through
some
more
of
the
tutorials
and
other
documentation.
A
A
Yeah,
it
doesn't
need
to
be
anything
too,
too
crazy,
but
I
think
we
owe
it
to
users
to
share
hey
just
so.
You
know
this
is
a
thing
that
we're
doing
and
we
have
been
doing
and
why
so.
B
Yeah
and
thanks
a
lot
for
that,
because
the
maven
tutorial
the
Python
tutorial
the
other
tutorials
with
astrotage
for
the
gsoc
project,
we
are
working
on
a
new
version
of
them.
You
know
when
we
will
simplify
the
process
but
having
it
Rewritten
beforehand
will
simplify
our
job
later
on.
So
thanks
a
lot
for
what
you're
doing
I've
seen
the
reviews
I've
seen
what
you've
done
and
frankly,
it's
brilliant.
It's
really
a
better
documentation.
A
Appreciate
it
yeah
and
like
and
I
just
want
to
share,
so
this
is
so
the
first
one
I've
gotten
through
is
the
build
a
Java
app
with
Maven
tutorial
for
the
most
part.
I
have
not
I
have
done
everything
in
my
power
not
to
change
any
of
the
actual
instructions.
The
wording
has
been
changed
a
little
bit
to
make
it
read
a
little
bit
better
and
some
punctuation
formatting,
mostly
and
then
I've
gone
through,
and
some
of
the
in
like
this
is
the
biggest
thing
that
I've
gone
and
done.
A
No
I
and
I
think
I
know
where
you're
going
with
that,
but
I'm
not
opposed
to
it
whatsoever,
yeah,
because
I
I
think
there's
a
way
to
probably
put
a
placeholder
in
there.
That
would
automatically
take
care
of
that.
For
me,
I
know
that
Mark
has
done
that
with
I
think
we
were
doing
it
for
Maven
3.90
9.0,
but
yeah
I'm,
I'm,
very
interested
in
knowing
what
we
can
do
about
that
because
I
like
it
a
lot.
Okay,
thank
you,
but
yeah.
A
So
yeah
and
I've
gotten
some
review
from
my
other
fellow
documentation,
writers,
so
they've
helped
me
get
this
even
better
arranged
and
honestly,
the
syntax
and
content
updates,
like
just
from
a
standpoint
of
simplifying
some
of
these
instructions,
makes
a
lot
more
sense,
yeah,
so
yeah
I'm,
hoping
that
I
can
get
some
reviews
from
other
folks.
A
Maybe
some
subject
matter:
experts
or
anyone
who's
built
a
job
app
like
following
this
tutorial
be
great,
but
it's
available
it's
out
there
and
it'll
be
open
until
we
have
some
proper
review
from
Jenkins
folks
as
well,
but
yeah.
So
that's
that's
coming
next
and
then
I
have
the
other
tutorials.
On
my
list
to
do
as
well,
the
guided
tour
is
not
going
to
be
updated,
as
I
thought.
A
It
was
because
Mark
and
I
were
able
to
discuss
previously
the
way
that
the
the
guided
tour
setup
is
not
it's
showing
how
the
tools
run
in
Jenkins,
not
how
the
not
that
the
Java
version
needs
to
be
up
like
it's
not
the
same
process
in
that
sense,
so
we're
leaving
the
guided
tour
alone
for
the
time
being,
but
we're
working
towards
making
sure
that
the
other
tutorials
and
everything
else
is
probably
alive.
So.
A
So
to
open
pull
requests
to
talk
about,
so
the
news
has
submitted
this
pull
request
for
administering
Jenkins
when
kubernetes
it's
got
a
great
start.
Just
needs
review
from
people
that
have
kubernetes
experience
their
expertise.
So
anyone
that
wants
to
pop
over
and
check
it
out
feel
free
share,
provide
feedback.
It's
always
welcome.
A
Jeffrey
Chen
I've
submitted
a
best
practices,
page
migration
from
the
the
Jenkins
Wiki,
so
I
had
a
couple
bumps
along
the
road,
but
we
got
this
to
a
point
where
it's
acceptable
and
it
has
now
been
merged.
It
is
live
in
the
Jenkins
best
practices
page
is
available
from
the
site
yeah,
and
we
talked
last
week
about
how
best
practices
is.
A
You
know
good
idea
and
how
these
are
recommended,
but
you
know
these
are
the
kind
of
things
that
best
practices
is
a
discussion
to
be
had
at
some
point.
If
it
comes
down
to
it,
someone
else's
best
practice
might
actually
work
better
or
someone's
best
practices
that
they've
been
using
may
not
align
with
ours.
So
that's
the
kind
of
conversation
that
we
should
be
having
and
want
to
have
and
find
out
ways
to
improve
or
things
that
we
can
change
or
add
to
this
page.
A
Anything
that
comes
up
you
know
with
the
various
new
projects
we've
got
going
on
with
Google
summarize
code,
like
there's
a
lot
of
different
places
that
we
could
even
get
more
best
practices
from
projects
like
hacktoberfest
can
actually
even
expose
new
best
practices
based
on
you
know,
we've
got
new
people
coming
in,
they
have
different
viewpoints
and
perspectives,
and
maybe
no
experience
or
different
experiences
with
this
sort
of
thing
that
that
kind
of
exposure
really
helps
us
understand
more
and
more
and
can
help
these
best
practices
expand.
So.
A
Anything
on
the
best
practices
or
you're
just
excited
about
having
it.
There.
B
Yeah
yeah,
that's
right,
I
think
I
made
a
review
of
this
PR.
All
at
least
I
have
read
it
and
I
was
really
happy.
I
discovered
some
things
in
fact,
so
I'm
super
happy
that
it's
now
part
of
the
Jenkins
area
website,
mm-hmm.
A
Good
awesome,
that's
great
I'm
glad
to
hear
it.
It
sounds
like
it's
already
serving
its
purposes:
yeah
good
next
episode,
there's
scripting
and
security
page.
This
full
request
has
been
exist,
has
existed
for
a
little
bit.
It's
got
a
lot
of
comments
and
review,
but
needs
more
review
and
feedback,
Mark
or
I
would
be
able
to
start
working
on
that.
A
But
although
it's
a
little
bit
lower
priority
than
the
job
17
transition,
so
it
might
not
be
worked
on
for
a
little
bit
still,
but
it's
there
it's
not
going
away,
and
it's
part
of
the
pull
request
that
we
found
were
valuable
and
usable.
So,
regardless
of
what
happened
next,
that
contents
stuff
that
we
need-
and
it
will
be
usable
foreign.
B
Yes,
it's
something
I've
been
working
on
for
quite
a
few
weeks
now,
not
a
lot,
but
you
know
I've
been
getting
some
feedback
and
changing
a
few
things
here
and
there,
but
some
people,
some
yeah
community
members,
didn't
feel
like
it
was
something
which
was
much
needed
and
some
other
people
thought
that
it
was
much
needed,
but
not
with
that
tool.
B
Update
CLI,
because
some
other
tools
like
renovate
both
or
Dependable
already
do
that
kind
of
things,
but
I
purpose
to
do
it
with
update
CLI,
because
I
know
just
a
little
bit
better
of
the
tli
and
for
some
of
the
tasks
that
I
was
proposing.
It
may
be
difficult
to
do
with
other
tools
or
even
impossible
to
do
so.
That's
why
I
chose
update
CLI
I'm
trying
to
force
push
this
PR
another
doll.
First
of
all,
this
was
just
matter
to
discuss
the
subject.
B
Should
we
continue
to
upgrade
the
dependencies
by
hand
or
could
we
automate
that
now
I
have
a
fork
of
Duncan's
IO,
of
course,
on
my
GitHub
account
and
I
have
run
that
and
it
created
eight
PRS
for
me
that
prove
somehow.
This
could
work
for
Jenkins
IO
I'm
supposed
to
have
nine
PRS,
but
for
whatever
reason,
I
think
it's
PHP
or
python.
That
is
not
yet
up
to
date
on
Docker
Hub,
you
know
with
the
Alpine
the
latest
Alpine
version.
That's
why
there
are
eight
and
nine
whatever.
B
So
what
I
was
proposing
is
that
people
interested
in
that
subject
vote
with
a
sum
up
or
thumb
down
in
a
few
weeks
from
now.
Maybe
we
could
choose,
should
we
close
this
pull,
requests
or
merge
it
if
we
have
more
thumbs
up
that
thumbs
down
totally
open
to
your
one
or
the
other
solution
just
wanted
to
show
that
this
can
be
done.
A
Bruno
I
think
that
it's
I
could
understand
if
it
like,
is
not
ideal
like
the
the
way
to
do
it's
not
ideal
for
other
applications
or
other
like
functions
and
stuff,
but
I
think
for
something
like
this.
It's
perfect
and
it
works.
It
clearly
works
really
well.
You've
got
PR
showing
as
much
and
yeah
I
mean
for
for,
like
for
what
I'm
doing.
B
But
the
thing
is
it's
still
somehow
manual,
because
whenever
you
will
be
writing
another
piece
of
documentation,
nothing,
you
have
nothing
to
do
right
in
the
documentation.
Okay,
it's
more
or
less
automatic,
but
you
will
have
to
modify
the
update.
Cli
workflow
flies
in
order
to
have
your
yeah
new
piece
of
documentation
update
all
automatically
yes,
so
yes,
it's
automatic,
but
whenever
you
will
create
other
parts
of
documentation,
the
automation
will
still
need
somebody
to
change
something
in
the
configuration
files
and
I.
Don't
know
how
to
automate.
B
You
know:
I
prefer
that
so
I
should
be
the
maintainer
of
these
update
to
my
files,
but
I
should
know
when
somebody
adds
something
to
jenkins.io.
That
would
need
to
be
updated
thanks
to
update
CLI.
So
I
don't
know,
I'm
still
partial
about
that.
Of
course.
I
want
to
do
that,
but
I
don't
know
how
to
be
informed.
I
used
to
be
subscribed
to
every
jenkins.io,
PR
or
issue
and
I
just
couldn't
manage
it
because
there
were
so
many
of
them.
A
Yeah
I
mean
I
I,
don't
think,
there's
an
issue.
Well,
okay:
I!
Don't
see
any
issue
with
having
to
update
the
CLI
file
in
the
first
place
to
have
everything
else
update
like
to
me
that
makes
sense
because,
yes,
it's
automatic
and
yes
you're
having
it
run
and
do
do
these
updates,
but
at
the
same
time
like
how
does
it
know
what
to
update?
A
If
you
don't
tell
it
kind
of
thing,
and
so
that,
like
that
part,
makes
sense
to
me,
but
I
also
could
see
why
automating
even
that
process
would
be
helpful
in
the
long
run.
So
you
have
one
less
thing
to
deal
with
and
worry
about
and
all
that,
but
for
what
we're
looking
at
already
I
think
that's
really
great
and
I
think
that
works
really
well.
A
I
have
no
problems
personally,
adding
you
know
if,
if
that
is
the
end
result,
but
I
have
to
make
sure
that
I
update
that
or
add
that
in
myself,
prior
to
it
running
I'm,
okay,
with
adding
that
step
to
my
workflow.
If
it
takes
away,
you
know
five
others
or
six
others
or
whatever.
That
might
look
like.
But
you
know
in
time
we'll
get
there
we'll
figure
it
out.
Okay,
but
I
think
it
works.
A
Really
great
I
I
mean
for
what
it's
worth:
I
I
like
it
a
lot
I
like
the
concept
and
I.
Think
it's
really
worthwhile,
like
yeah
I,
know,
like
you
said,
there's
the
panda
bot
and
renovated
bot
and
like
other
things,
but
that
you
know
that
doesn't
mean
that
there
can't
be
another.
You
know
useful
tool
that
we're
relying
on
to
help
us.
B
Maybe
we
should
just
use
you
know
the
best
tool
for
the
best
use,
I
mean
a
digitali,
won't
be
the
best
tool
for
each
and
every
dependency.
Update,
renovate
mode
could
be
useful
for
other
ones
and
of
course,
we
all
I
think
we
already
have
the
depend
about
working
on
jenkins.io.
So
why
not
combine
the
three
of
them
to
get
most
of
the
automation
done,
we'll
see.
Anyhow,
thanks
a
lot
for
your
feedback
and
for
the
thumbs
up.
I
do
appreciate
it.
A
Always
give
you
a
real
one,
too
yeah,
no
and
like
you're
right.
Why
shouldn't
we
combine
tools?
Why
shouldn't
we
try
to
make
our
lives
easier
in
that
sense
like
yeah,
if
it's
possible,
we
can
do
it.
Why
not
sure
Sam?
Thank
you
very
much
for
sharing
all
that
Bruno
and
you're
kind
of
walking
us
through
and
explaining
the
the
process
a
little
bit
that
helps
a
lot
and
I
think.
As
long
as
we
can
get
more
eyes
on
it
and
people
see
what
the
goal
is.
A
I
don't
see
why
people
would
be
opposed
frankly
outside
of
I.
Could
I
could
see
an
argument
like
it's
too
many
things
but
like
even
then
I,
don't
that's
a
that's.
A
I
can
see
that
as
a
personal
view
versus
like
a
factual
thing,
so
we'll
see,
but
thank
you
anytime
cool.
So
next
up
so
devops
devops
world
is
happening
again
this
year
as
expected,
however,
the
format
is
different.
This
year
we're
it's
going
to
be
devops
World
Tour,
so
the
idea
is
smaller.
One
or
two
day
shows.
A
You
know
days
at
most
and
kind
of
compacting
everything
to
one
day.
Instead
of
having
one
conference
in
one
place,
that
may
be
more
difficult
to
get
to
or
attend-
or
you
know
be
a
part
of
at
that
point
so
what's
happening
is
devops
is
going
to
be
going.
Devops,
World,
Tour,
there's
going
to
be
multiple
locations
so
places
in
the
US.
For
instance,
New
York,
Chicago,
Silicon
Valley
we're
doing
there's
going
to
be
one
in
London
Singapore.
A
So
multiple
dates
multiple
days
for
some
of
these
dates
and
the
the
speakers
and
talks
that
will
be
had
are
already
being
determined,
developed,
Mark
waite's,
actually
going
to
be
at
the
U.S
locations.
To
give
a
talk.
A
Title
benefit
your
business
by
contributing
to
open
source,
so
plenty
of
incentive
right
there
to
go
to
one,
if
not
all
of
them
and
yeah
and
we're
gonna
like
forget
who
but
I,
think
we're
gonna,
try
and
have
Olivia
lame
in
for
the
Singapore
since
he's
over
there
Bruno
are
you
gonna,
be
at
the
London
Museum
or.
A
Oh
okay,
got
it
got
I
got
it
I
always
forget
where
team
is
so
good
to
know
but
yeah,
so
the
reputation
is
going
to
be
there
registration's
open.
Now
you
can
sign
up
and
yeah
just
get
excited,
it'll
be
there
and
more
details
are
available
on
the
site.
So
if
you
have
questions
check
it
out
and
then
last
but
not
least,
since
we
are
right
of
time
so
Mark
is
still
is
on
PTO
again.
A
He
will
be
unavailable
for
this
evening
tomorrow,
whatever
time
zone
for
Asia
docs
office
hours.
So
the
meeting
is
canceled
he'll
be
back
next
week,
so
July
27th,
Asian,
Asia
docs
office
hours
will
be
back
on
as
normal
good
yeah
and
that
wraps
us
up
for
today.
So
I'm
going
to
go
ahead
and
stop
the
recording.
In
just
a
moment,
video
will
be
available
24
to
48
hours
same
as
normal,
and
we'll
see
you
next
week,
thanks
for
coming
by
and
have
a
good
rest
of
your
day.