►
From YouTube: 2020 12 07 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
A
A
B
Well,
just
I'm
thinking
about
do
we
need
to
make
such
synchronization
between
installation
of
docker
and
downloads
automatic,
trying
to
write
some
kind
of
script
which
will
grab
the
latest
lts
version
from
downloads,
page
and
included
in
installation,
or
something
like
similar
to
this.
B
C
Mark
can
I
ask
a
dumb
question:
vlad
close
your
ears.
I
ask
questions
like
this
and
mark
filters
them,
but
and
when
you
get
into
pipelines
the
agent
station,
the
agent
statement
takes
docker
and
docker
file
options.
Are
there?
Is
there
anything
there
with
keeping
those
up
to
current
or
does
it
not
matter?
Is
it
so
generic
that
we
just
make
sure
that
the
pipeline
docks
don't
ever
specify
a
version,
or
I.
A
Think
I
think
in
that,
in
the
case
of
dockerfile,
what
it's
saying
so,
let's
see
agent
pipeline
agent
doctor
and
update
author
doctor
file
and
more
let's,
let's
just
put
that
on
the
agenda
mag
and
we'll
talk
through
it,
because
I
think
it's
a
good
question
and
it's
worth
highlighting
something
that
the
platform
sig
has
been
discussing
discussion
discussing
and
what
how
that
matters
for
dogs.
C
A
A
C
A
A
Yes,
okay,
there's
one:
it's
been
a
long
time
since
I've
I've
last
reviewed
feedback
from
users.
So,
let's
how
about
we
do
that?
Let's
take
meg.
Did
you
want
to
report
anything
further
on
pipeline
docs
improvements?
No,
no.
A
B
Just
in
case,
if
we
have
some
time,
I'm
not
sure
if
you
want
to
discuss
one
of
the
latest
issue
on
jenkins
dot
io,
which
was
opened,
and
oleg
made
a
comment
on
this.
It's
regarding
providing
some
link
from
installation
page
to
jenkins
lts
what
lts
is,
and
maybe
there
should
be,
a
link
from
glossary.
B
There
is
like
discussion
on
this
in
the
issue,
so
it's
about
the
content
of
the
page.
A
Good
yeah,
I
like
that.
That's
a
good
one!
That's
a
very
good
one!
Let's
let
me
go
grab
that
issue,
because
I
had
seen
that
and
seen
his
comments
and
was
interested
in
them.
So
how
about
jenkins?
Oh
it's
github,
and
this
one
and
then
the
issue
was
raised
by
josh
soroff.
Here
we
go
okay,
so
I'll
just
link
to
that.
B
A
A
A
A
B
I'm
not
sure
what
kind
of
obstacles
it
will
involve
for.
D
A
Yeah-
and
I
think
that
for
me,
that
the
question
is
what's
the
risk
of
emerging
something
prematurely
and
that's
not
it's
not
that
high
of
a
risk
and
having
an
extra
reviewer
might
be
a
real,
a
real
benefit,
but
giving
you
another
one
or
two
months
might
be
good
as
well.
To
assure
that
everybody's
confident
that
you're
continuing
to
contribute
that
we
can
entrust
you
with
permission
to
merge
to
the
to
the
doc
site.
Like.
A
B
If
you
go
to
jenkins
dot,
I
go,
there
is
download
page
available
and
it
mentions
two
columns,
lts
releases
and
weekly
releases
on
download
page
yes,
and
so
on.
The
left
gen
download,
jenkins
lts.
It
mentions
specific
version
in
this
case
it
is
2
to
631,
and
we
have
now
installation,
for
instance,
for
docker
on
the
same
side
mentions
specific
version
later
in
installing,
like
a
dockerfile,
it
mentions
this
version,
2
261.1,
oh
right
now
it
is
already
merged.
A
A
A
Page
page
is
written
in
in
a
ruby
based
templating
markup
language
called
hamel
h-a-m-l,
a
ruby
based
html
markup.
A
Therefore,
it's
at
page
generation
time
there
is
a
program
clearly
running
and
the
thing
uses
that
programming
context
to
go
out
and
query
the
the
update
center
and
ask
what's
the
most
recent
lts
version,
so
it
it
actually
programmatically
goes
out
and
asks
that
question.
A
A
In
adoc
somewhere
and
read
it
into
the
installing
jenkins
page,
that
might
be
another
concept.
I'm
not
sure
if
adopt
can
use
values
of
environment
variables.
But
those
are
the
kinds
of
options
we
have.
Oh,
we
could
there's
another.
We
could
rewrite
the
page,
rewrite
the
page
and
handle
it,
but
then
then
it
becomes
challenging
to
maintain
because
it
would
be
the
one
page
written
in
hamel
when
all
the
rest
are
ascii
doc.
A
So
vlad,
if
you're,
if
this
is
a
if
you're
interested
in
the
duck
generation
system,
then
this
is
a
great
project.
We
could
also
consider
offering
this
as
a
maybe.
It
may
not
be
big
enough
for
a
google
summer
of
code
project,
because
it's
probably,
I
would
guess
not
more
than
a
week
or
two
of
work,
and
they
really
would
like
google
summer
of
code
to
be
eight
or
ten
weeks
of
work.
C
Crazy,
I
need
to
look
at
this
more
to
see
if
I
really
wanna
argue
for
this.
But
it
seems
to
me
tough
that
we've
got
two
separate
pages
that
are
telling
people
how
to
do
the
same
thing
that
maybe
the
documentation
at
the
download
should
say,
go
to
this
page
and
follow
the
instructions
to
download
and
then.
A
Well,
so
the
for
me,
the
cut
the
two
contexts
are
so
different
that
I
think
they
they
would
have
to
remain
remain
separate.
But
let's,
let's
try
your
idea.
So,
let's,
let's
talk
through
it,
so
this
is
the
downloads
page
and
what
its
goal
is
to
help
people
find
the
package.
That's
right
for
their
environment.
A
A
A
Yeah,
that's
another
way
to
say
it
and
yeah.
That's
it
is
this.
This
is
the
this
is
the
you
can
always
make
this
go.
This
one
is,
is
hey.
This
will
get
you
a
much
much
further
and
it
really
is
amazing
how
much
further
this
gets.
You
thanks
to
vlad's
brilliant
work
with
this
particular
step
right
here
right
and
this
thing
those
these
these
steps
here
have
just
worked
wonders
for
the
simplicity
of
this
of
this
documentation.
Thank
you.
B
I
well
I
personally,
I
can
describe
how
I
was
doing
before
before
providing
this
pr.
I
was
mainly
looking
for
specific.
B
2.263.1
different
releases
and
I
wanted
to
find
release
which
contains
lts
inside
it.
Besides
the
version
number,
and
also
we
used
slim
edition
before,
due
to
the
like,
lower
size
of
the
image,
and
so
I
was
able
to
find
it,
I'm
not
sure
if
we'll
be
able
to
find
it
in
future
releases
and
how
automatic
others,
like
things
created
on
the
docker
hub,
because
those
are
located
on
the
site
which
is
not
controlled
by
genders
and
also
I
manually
looked
at
the
plugins
thought
jenkins.
B
B
Explorations,
I
guess
before
automating
this,
but
I'm
not
sure
if
we
want
to
do
this
in
automatic
way
right
now
or
just
wait
and
see
how
we
want
to
do
this.
But
I
think
that
in
case
you
will
do
this
just
for
docker
in
hammel,
installation
and
the
rest
will
be
in
a
dock.
B
C
I
think
you're
right,
because
this
this
is
not,
for,
I
remember
in
charge
of
this
facility,
where
I'm
going
to
have
a
thousand
jenkins
instances
and
I
need
to
know
how
to
install
this
is
how
I
can
get
I'm
new
to
jenkins,
and
I
want
something
I
can
experiment
with,
and
this
gets
me
through
right
right
right.
That's
so
if
they
end
up
getting
a
back
rev
download,
I'm
not
sure
I
even
care
that
much
right.
A
A
B
B
A
Yeah
my
view:
yes,
good,
okay,
good,
so
so
it's
fine
that
we
do
this
interactively
we'll.
We
know
we'll
see
we'll
have
to
make
this
that
change
in
mid-january,
when
the
2.236
263.2
release
comes
out
mid
february
and
mid-march,
so
once
a
month
we're
going
to
see
it,
I
had
one
other
alternative
that
came
to
mind.
A
I
think
it
might
be
even
worse
than
any
of
yet
well,
let
me
put
it
up
above
here.
We
could
write
a
test
that
complains
when
the
page
is
wrong
and
include
the
test
in
page
generation.
A
But
thinking
about
it,
that's
not
a
lot
different,
that's
still
code,
that's
not
a
lot
different
than
writing
an
ascii,
doc
extension
or
setting
a
variable.
I
mean
in
either
case
all
this
one
does
is
tell
us.
We
have
a
problem,
whereas
these
actually
fix
the
problem.
They
they
automatically
resolve
it.
So
I'm
not
sure
that's
yeah!
Actually,
I'm
going
to
delete
it
because
it
yeah
just
having
thought
through
it.
It
doesn't
make
sense
to
just
test
for
it.
If
we
can
test
for
it
and
we
have
enough
code
to
test
for
it,
we
can.
C
C
A
C
If,
if
anything
and
I'm
not,
this
may
be
a
bad
idea,
we
could
put
a
readme
file
in
the
source
directory
of
this
file.
That
explains
it.
So
if
somebody
finds
it
and
they
say,
were
these
people
total
idiots
that
they
left
this,
you
know
or
something
to
say.
This
is
a
manual
thing
and
we
considered
these
other
ways
of
doing
it
and
decided
it
wasn't
worth
it
or
something.
I
don't
know.
A
A
B
B
Right,
just
just
minor
issues
since
you
touched
marked
the
possibility
of
testing,
should
we
test
when
we'll
update
the
tutorial,
the
tutorials
or
installation
documentation
with
new
version
latest
version,
and
should
we
test
it
in
automatically
or
like
manual
as
before?
It
would
be
enough
and
do
we
need
to
provide
some
automatic
testing.
A
What
they
do
is
they
have
in
their
source
code.
There
are
times
when
the
developers
will
write
a
comment.
They
write
the
comment
in
a
very
specific
way
and
the
comment
can
then
be
extracted
and
converted
into
an
executable
automatic
test,
so
they
they
actually
make
executable
documentation,
and
we
could
consider
something
like
that
in
this
case,
this
would
be
the
only
occurrence
and
I'm
not
yet
personally
persuaded
that
the
python
experiment
in
that
actually
has
worked
successfully.
B
A
A
A
A
C
A
No,
it
it
actually
is
documented
and
what
I've
described
is
a
flawed
and
imperfect
description,
because
we
should
go
to
the
authoritative
documentation
like
this
one
right
here,
jenkins
jenkins.
And
if
we
look
at
the
tags
here.
This
lists
the
tags,
and
so
let's
people
decode,
which
things
are
supported
and
which
are
not.
C
C
At
the
pipeline
reference
they
may
have
actually,
I
think,
there's
a
bigger
issue,
but
we
may
be
able
to
say
they've.
Actually
it
looks
like
what
you
do
there
is
you
put
the
images
you
want
into
your
my
registry
and
then
they
are
just
referencing.
What's
in
my
registry
right,
so
at
the
point
that
I'm
doing
my
pipeline,
I
don't
have
to
actually
deal
with
this.
So
it
becomes
an
administrative
task
of
setting
up
that
registry
to
have
the
agents
that
are
needed
for
my
pipeline
developers.
C
A
A
A
C
A
D
C
What
I,
what
I
suspect
is
that
our
users
are
grossly
under
using
the
the
flexibility
of
the
agents.
I
suspect
that
people
are
doing
sort
of
simple
agents
that
work
for
them
and
they're
missing
out
on
a
lot
of
benefits,
but
they're
working
and
all
of
this
other
stuff
could
get
very,
very
complicated.
C
A
Will
be
reviewing
a
jenkins
enhancement
proposal
to
reduce
the
supported
doctor
images
and
to
create
a
process
so
that
we
know
who
is
maintaining
those
doctor
images
by
image
tag?
A
C
A
C
C
A
Very
good
all
right,
so
then
next
topic
was
issue
of
39.91
lts
description
on
jenkins
location,
on
jenkins
at
ios.
So
I
like
this
one,
because
it's
about
how
do
we
do
a
better
job
of
structuring
the
dogs,
so
what
happened
was
josh
sora
the
author
who
originally
created
the
tables
divs
transition,
said
hey.
I
was
looking
for
the
definition
of
lts
and
saw
there's
this
page
and
there's
this
page,
and
neither
of
them
tell
me
what
the
meaning
of
this
word
that
three-letter
action.
C
D
A
Then
he
checked
this
page,
that
glossary
and
the
glossary
doesn't
mention
lps.
So
we've
got
this
acronym
that
we
all
know
what
it
means
and
yet
nowhere
do
we
nowhere
on
in
the
pages
he
searched.
Do
we
actually
define
it
right
now?
We
do
have
a
place
that
that
does
define
it
and
if
we
go
to
the
downloads
page.
C
D
C
A
I
think
a
very
reasonable
thing
we
could.
We
could
certainly
make.
I
think
anyway,
we
make
this,
because
this
page
is
a.
Let
me
call
it,
this
page
is,
I
believe,
camel
and
generated,
and
so
we
could
change
this
quite
easily
to
be
a
hyperlink
or
have
the
ltsbi,
hybrid,
yeah
or.
C
D
A
C
Think
actually
tammy
is
starting
an
initiative
for
our
internal
docs.
To
use
a
lot
more,
I
mean
this
is
a
big
bad
one,
but
all
over
we
use
we
throw
out
these
terms
that
people
don't
necessarily
know
what
they
mean
and
they
could
all
just
be
links
to
you
know
I
don't
know
if
everything
links
back
to
the
glossary
and
then
the
glossary
has
all
the
links
of
where
to
go
for
more
information
or
if
we
all
you
know,
implementation
details,
but
we
should
have
a
lot
more.
D
C
C
B
That's
I
guess
part
of
the
same
issue
is
like
the
question:
do
you
want
to
link
installation
page
change,
the
content
to
installation
page
and
provide
link
somewhere
to
lts?
A
A
A
C
But
here's
how
you
set
up
a
project
with
freestyle,
here's
how
you
do
with
the
clarity
pipeline,
here's
how
you
do
it
with
scripted
pipeline.
Here's
how
you
debug
here's,
how
you
fix
performance
problems
in
your
project.
You
know,
there's
a
zillion
links
and-
and
I
I
like,
I
would
like
a
document
that
had
all
those
relative
links
that
would
be
nice.
A
Inside
instead
of
I
think
meg,
what
you're
saying
is
instead
of
glossary,
saying
here,
that
a
project
is
just
a
user-defined
prescription
of
work.
It
would
also
have
several
additional
sentences
said
saying
the
pr
some
of
the
project
types
include
freestyle
height
or
pipeline
freestyle,
matrix
yeah.
That
kind
of
thing.
A
D
A
C
C
A
But
for
me
I
think
that
thought
process
is
valuable
because
there
are
times
when
pages
become
so
overwhelmed
with
links
that
I
find
them
more
difficult
to
read
right.
So
so
there's
some
at
least
from
my
reading.
There's
some
balance.
I
don't
know
what
the
balance
is,
but
there's
some
balance
between
enough
links
and
overuse
of
links.
C
Right
because,
at
the
other
end
too,
I
have
seen
some
pages
that,
in
lack
of
links,
start
explaining
every
term
in.
B
C
That's
why
I
in
a
in
a
previous
life,
I
did.
I
called
it
an
encyclopedia,
but
it
was
basically
a
wikipedia
sort
of
thing
that,
and
that
was
all
my
links
went
there
and
each
article
there
then
had
links
and
links
and
links
to
everything
you
might
possibly
want
and
that
kept
it
fairly
clean.
Actually,
because
I
I
can
read
over
a
link,
if,
if
I'm
reading
a
sentence-
and
it
makes
perfectly
good
sense
without
clicking
the
link,
then
I
just
ignore
that
the
link
is
there
so
great
good.
A
B
C
D
A
C
B
A
C
Different
learning
styles
yeah-
and
I
I
admit
that
I
enjoy
a
good
video,
but
I
have
a
hard
time
learning
from
a
video,
I'm
a
words
person,
but
but
I've
also
worked
with
some
brilliant
people
who
would
do
great
reviews
of
the
documentation?
If
I
would
come
to
their
office
and
read
it
to
them,
they
could
not
read
it.
It
wasn't
that
they
were
functionally
illiterate.
C
They
just
do
not
take
information
from
the
written
page,
and
if
I
came
in
and
read
it
to
them,
they
would
give
me
fabulous
previews
so
and
everything
in
between
okay-
and
there
are
also
people
who
are
only
going
to
learn
if
they
can
tinker
and
there
we
get
into
you
know
having
little
training
videos
with
a
little
lab
that
they
can
go
to
and
say.
If
you
need
to
do
this,
do
this
this.
You
know
and
we're
not
quite
there
where
we
can
offer
that
yet,
but
we
may
be
close.
B
Right
for
training
purposes,
I
guess
video
would
be
great
source
and
resource,
but
in
case,
if
you
just
reach
internalization,
for
instance,
it
would
be
hard.
I
guess,
to
internalize
the
video.
D
B
C
C
A
B
A
And
we
reviewed
that
today,
with
xeno
vlad
was
there
as
well
thanks
for
joining
us
lad
thanks
very
much
and
vlad.
I
saw
that
you
had
also
asked
to
view
the
the
seed
questions
document.
You're
welcome
to
put
questions
in
there.
Zenob
will
review
them
tomorrow,
I'm
sure
some
of
them
she
will
say
she
will
decide.
I
don't
want
to
even
be
asked
this
question
or
if
it's
asked
I
want
it
answered
by
marky
or
by
kristen,
not
by
me
and
and
that
will
that
will
all
be
fine.
A
B
Put
together
a
couple
questions,
but
yeah
in
case
she'll
have
some
time
or
she'll
have
time
to
re-address
those.
You
know
that
would
be
fine
whatever
just
like
something.
What
what
is
next
and
our
planning
to
do
this
kind
of
stuff
related
to
documentation
and
yeah
component
that
she
addresses
and
katakura
and
training.
A
Very
good,
okay
last
topic
was
this
review
feedback
from
users,
and
I
propose
given
the
time
we're
at
that.
We
just
ignore
that
one.
For
now
it
needs
much
more
time.
It's
this
worksheet,
that's
automatically
generated
from
user
feedback
and
we
occasionally
get
it
get
feedback
on
it.
It's
becoming
less
often.
So
today
we
had
some
feedback.
Yesterday
we
had
some
and
three
days
ago.