►
From YouTube: 2023 01 06 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
A
B
A
Okay,
then,
let's
go
ahead
so
my
way
of
action
items
Kevin's
got
the
action
item
to
Archive
the
docs
mailing
list
sometime
this
month.
We
hope
it'll
be
done.
That's
those
are
the
only
that
I'm
aware
of
Google
summer
of
code
documentation.
So
what
do
you
need
to
share
Chris
and
let's
talk
further?
Okay.
B
So
we
have
got
a
thing
about
10
project
ideas
so
far,
and
but
only
one
of
them
is
confirmed
so,
which
means
that
none
of
them
needs
working
on
by
contributors
or
potential
mentors
and
that
we
may
need
to
communicate
better
with
the
like
potential
mentors.
B
And
I
think
we're
gonna
have
a
meeting
soon,
but
that's
going
to
be
like
in
a
week
or
two.
B
You
know
that
it
should
be
a
I
got
it's
my
next
Wednesday
or
next
Wednesday
yeah,
so
in
the
next
Thursday
next
Thursday
we're
gonna
have
a
meeting.
A
B
B
Sorry,
but
it
should
be
open
to
judgment
was
too
because
we
got
a
few
more
over
the
holidays,
which
is
good
news.
A
B
But
we
do
not
have
all
the
a
complete
set
of
like
details
for
the
mentees
to
start
so
it
may.
We
may
need
to
add
more
for
a
complete
set
of
starting
points.
Foreign.
B
B
I,
mainly
I
made
it
through
liaise
with
gym
members
to
see
what
he
thinks.
B
Yeah
mainly
as
an
email
to
to
everyone
in
the
advocacy
and
I
wish
as
I
chase
a
new
Louisa,
Jim
and
and
because
it's
new
yeah
actually
including
today,
right.
B
C
A
A
So
how
about
let's
look
at
those
ideas
and
then
we'll
we'll
decide
which
ones
we
should
improve
and
how?
So,
if
we
look
at
Google
summer
of
code
in
Jenkins
and
gsoc
2023
project
ideas
list,
so
we
certainly
could
talk
more
about
the
plug-in
installation
manager
tool
improvements.
That's
one
that
I've
got
a
little
involvement
in
specific
to
documentation.
There.
B
Because,
like
I
think
it,
the
one
I
I
have
been
assigned
to
work
on
like
I.
Think
the
the
alternative
tools
also
involves
documentation.
It's
like
we
go
up
yeah
that
one
this.
A
Okay,
well
so,
let's
yeah,
so
let's
spend
let's
spend
more
time
on
this
one.
That's
a
that's
a
good
one
to
to
talk
through
okay,
yeah,
okay.
So
the
the
background
here
is
that
we've
got
we.
Today
we
generate
the
jenkins.io
site
with
awestruckt,
using
ASCII
doc
sources
and
yaml
files
and
data
sources
and
Ruby
scripts
and
all
sorts
of
cool
things
that
ultimately
result
in
a
static
site,
and
the
challenge,
of
course,
is
that
awestruckt
is
no
longer
being
actively
maintained.
A
So
so
the
idea
was
okay.
Should
we
consider
antora
or
Hugo
as
a
tool
that
is
actively
being
being
maintained
to
replace
it,
and
this
is
the
one
that
that
I
know
cloudbee's
documentation
team
is
using
it,
so
we're
more
likely
to
get
mentors
and
coaches
from
the
cloud
Beast
side.
If
we
were
to
choose
antora
Gavin
Mogan
like
Shugo,
so
he.
B
B
And
he
he
also
said
yes
to
guess
me
as
well,
but
I
I'm
thinking
like
because
like
I'm,
both
Hugo
and
and
Gatsby
they're,
not
they're,
not
designed
for
Esky
dogs
persons.
A
A
B
C
B
I
think
we
may
need
to
work
a
bit
more
on
on
the
background,
because,
like
right
now
we
we
don't,
we
only
discuss
much
about
until
we
go
because,
like
you,
count
like
with
I
mean
decisive
I
think
we
should
set
on
one
tool.
A
B
B
C
B
A
A
What
do
you
call
it
if
I'm,
using
a
if
I'm,
generating
the
site
locally?
Okay,
so,
okay,
the.
B
A
A
B
A
Like
the
get
site-
and
there
are
so
I
think
I
suspect
others,
the
FreeBSD
and
others
right-
there
are
many
sites
now
that
do
version
documentation,
yeah.
A
So
the
preferred
tool
how
about,
if
we
just
admit
it,
we
think
we
should
use
antora
to
replace.
Oh,
oh,
and
this
is
generated
as
a
static
site
using
awestruckt
awestruck.
B
B
C
C
A
A
So
then,
once
the
existing
site
is.
C
C
A
A
So
we've
got
the
quick
start
and
the
quick
start
this
one
I
think
we
can
actually
put
it
in
is
some
ideas
might
be
create
quick
start
so
documentation.
C
A
The
current
documentation
site
locally
yeah,
familiarize
yourself
structure.
B
C
A
Road
map
right
is
kind
of
an
exotic
one
secure.
Let's
see,
changelogs.
C
A
Artwork
see
what
are
some
others:
oh
security,
security,
advisories,
yeah
version,
specific
tutor
of
content
in
tutorials.
Thank.
C
A
Because
there
is
some
of
that
right
see
the
like
Mike.
What's
the
example
like,
like
oh,
improve
a
plugin.
A
So
now
page
types
and
there
are
probably
more
but
all
right
so
then
familiar
then
page,
formatting
or
page
content
sources
like
Hamel.
B
A
A
B
B
A
Use
Ruby
inside
the
docker
containers
yeah,
because
that's
how
I
believe
that's
how
awestruckt.
A
And
so
we
ought
to
put
Ruby
in
there
Hamill
slash
Ruby,
okay,.
A
Docker
containers
we
just
had
some
additions,
syntax
and
spelling
checks.
C
A
B
C
C
A
Now,
after
they've
fixed
several
of
those
that
gives
them
and
they've
built
the
site
now,
it's
that's,
that's
gives
them
familiarity
with
the
current
tool
set.
Now,
how
do
we
get
them
familiarity
with
with,
and
maybe
this
is
where
we
should
put
Explorer
antora.
B
A
A
B
A
A
All
right
so
explore
antora.
Should
we
should
they
as
part
of
their
Quick
Start
review
version,
specific
documentation,
techniques,
things
that.
B
A
A
C
C
B
A
C
A
And
since
we'll
probably
want
more
than
one
I'm
going
to
make
that
Cloud,
these
documentation
site.
C
A
A
C
B
B
B
Got
Version
Control,
okay,.
B
B
But
this
one
is
generated
with,
if
you
have
this
tool,
I
used
to
use
for
all
these
things
is
that
that
part
was
definitely
with
things
swings
so.
B
B
A
C
A
B
A
A
A
C
A
Another
for
me,
I'm
not
as
thrilled
with
that
one
but
I
think
maybe
what
we
do
is
we
include
it
as
hey.
Here's
an
example:
another
idea
to
to
see
how
somebody
else
did
it
I
rather
prefer
the
Sphinx
technique
or
the
the
cloud
Beast
technique
where
it
embeds
it
right
into
the
it.
It
makes
it
more
obvious
in
the
page.
A
A
B
A
C
B
A
B
A
B
Yeah,
so
it's
like,
we
can
try
out
yeah.
One
thing
we
can
try
is
like
it's
kind
of
like
I'm,
not
sure
if
we
should
use
it,
but
I
think
for
the
talks
of
10.
So
far.
C
A
A
And
and
I
think
at
least
this
gives
the
the
candidate
a
chance
to
think
about
several
different
ways
that
people
are
doing
it,
they
don't
they
don't
have
to
get
stuck
on.
Oh
there's,
only
one
way
to
do
this
or
it's
no.
There
are
a
lot
of
different
ideas
and
they've
gotta
they'll
need
to
bring
their
ideas
to
how
should
it
be
done?
Yeah.
B
C
B
A
B
A
For
yaml
data
files
to
drive
web
page
templates,
okay.
A
Then
probably
haml
files,
Hammel
templates.
A
C
B
I
can
say
for
the
future.
We
can
have
like
an
improvement
on
the
current
layout
yeah.
B
B
C
B
We
can
include
like
new
layout
for
the
web
pages.
Oh.
C
C
B
A
B
How
to
how
to
introduce
the
Chinese
as
we
go,
because
we
need
to
change
the
the
two
to
be
as
fast
or
should
we
like
start
a
new
Branch
I'll
work
on
that.
B
A
A
C
C
C
A
C
A
Wait
a
sec
where
to
go
and
I
picked
the
wrong
thing
to
get
there.
Oh,
yes,
I
need
to
go
here,
Google
summer
of
code
and
Jenkins,
and
this
one
has
the
project
ideas
list.
Okay,
and
here
we
should
find
building
jenkins.io
with
alternative
tools.
Let's
see
if
the
layout
came
out,
correct,
nope,
so
I
didn't
get
it
right.
So
I
need
to
do
the
the
nested
list.
Thing.
I
use
the
wrong
syntax,
just
a
minute.
A
C
A
C
C
A
C
A
C
B
I,
don't
think
so.
It
looks
really
good.
A
C
C
A
C
C
A
Yeah
yeah,
you
can
do
it
whenever
is
comfortable
for
you.
What
I
think
I'm
going
to
do
is
I'm
going
to
say
that
as
soon
as
somebody's
approved
it
it's
going
to
Auto,
merge.
A
B
C
A
B
That's
the
most
important
thing
because,
like
we
still
need
to
to
work
on
the
other
ones,
yeah,
oh.
A
Maybe
we
could
take
a
few
minutes
on
one
or
two
of
these
others,
because
I
think
you
may
be
able
to
help
me
on
some
of
the
others
sure
these
deprecation
topics
what's
happened
is
there's
an
plug-in
deprecation
process
in
the
life
cycle
of
Jenkins
plugins,
and
that
deprecation
process
shows
a
a
warning
dialogue
to
users
to
tell
them
that
hey
this
plugin
you're
using
is
deprecated
well
one
of
the
plugins
that
was
recently
deprecated
was
this
wmi
Windows
agents
plug-in,
and
it
was
deprecated
for
very
good
reasons.
A
The
reasons
are
described
here
in
this
issue
tracker.
Why
is
it
deprecated?
What's
that
mean?
What's
the
impact
Etc,
but
the
crucial
thing
here
is
that
Jesse
Glick,
a
core
maintainer,
offered
a
really
good
idea
of
a
way
to
make
it.
So
we
don't
have
to
do
quite
as
much
work
to
do
this,
and
so
there's
a
core
change.
That's
been
proposed
here
to
make
it
so
we
do
much
less
work
with
in
order
to
implement
this
finalize
this
deprecation
and
make
it
good
for
our
users.
A
So
that's
that's
the
info
piece
here
now.
The
next
piece
is
an
entirely
different
topic,
and
this
was
the
one
if
you
could
stand
to
spend
five
or
ten
minutes
with
me,
we'll
we'll
try
to
make
progress
together
on
it.
There's
there's
a
component
in
jira
called
website.
That's
the
place!
We
track
issues
until
about
two
years
ago,
on
jenkins.io
for
jenkins.io
about
two
years
ago
we
switched
to
use
GitHub.
A
So
let's
read
them
and
we're
just
going
to
read
them
one
at
a
time
and
make
our
decision.
So
this
one
is
system
administration
capabilities
using
groovy
and
the
suggestion
was
hey.
There's
a
lot
of
capability
in
the
Jenkins
script,
console
for
administrative
use
of
groovy,
and
this
could
be
a
dedicated
section.
I
think
this
should
just
be
transported
as
an
issue
to
jenkins.io.
It's
a
yes.
We
want
this
I,
don't
know
when
we'll
get
it,
but
I
think
it
would
be
a
good
thing
to
have
yeah.
A
Other
one
is
now:
let's
take
the
next
one:
this
734
create
a
c
or
C,
plus
plus
tutorial
similar
to
Maven
Python
and
node.js,
yeah
and
again,
I.
Think
I.
Think
that's
a
good
thing.
There's
still
plenty
of
people
who
code
in
C
and
C,
plus
plus
rust,
is
not
used
by
everybody
yeah
so
for
me,
I'd
say:
move
it
to
GitHub
as
well.
A
A
B
A
C
B
C
B
A
B
B
A
A
A
B
A
A
C
B
C
C
C
B
A
A
What
this
is
really
asking
is
hey.
Please,
please,
give
us
some
way
of
filtering
the
content
of
this
community
reported
issues
text
so
that
people,
when
they
submit
bogus
bug
reports
like
69
or
420
or
whatever
they
they
would
not
appear
here.
Oh
okay,
I
see
I
can
show
you
an
example.
A
live
example
is
even
better.
We.
B
A
At
this
so
download
and
if
I
look
at
the
change
log
here
for
2.375.1
Community
reported
issues,
what
happened
was
people
a
user
clicked
one
of
these
two
Cloud
icons
either
this
one
I
had
to
roll
back
or
this
one
I
experienced
notable
issues
and
when
they
did,
they
typed
a
bogus
number
in
here.
So
instead
of
typing
69955,
which
is
a
valid.
A
They
typed
one
two
or
three,
oh
or
two:
nine,
nine
right,
two,
nine
nine
is
not
an
interesting
issue
in
in
Jank
in
that
version
of
Jenkins,
okay,
but
the
problem
is
there's
a
whole
curation
problem.
There
of
three
is
in
fact
a
valid
GitHub
issue
or
a
valid
Jenkins
issue.
It's
just
not
a
valid
Jenkins
issue.
Here
it
means
someone
has
to
review
these
and
filter
them
and
that
that
is
well.
The
core
maintainers
haven't
been
willing
to
do
that
yet
and
I'm
one
of
those
core
maintainers
who's,
unwilling,
okay,
okay,
Chris.