►
From YouTube: 2020 12 17 Docs Office Hours
Description
Jenkins Docs office hours Dec 17, 2020. Topics included Google Season of Docs retrospective, and upcoming calendar events
A
A
Excellent
okay,
so
aws
account
deactivation
was
one
topic
for
me:
pull
request
progress,
another
calendar
for
the
next
two
weeks.
What's
next
and
I
propose
we
review
briefly
the
jenkins
wiki
plan,
just
so
that
xenobio
aware
of
that,
and
and
have
some
notion
of
it
and
can
consider
it
any
other
topics.
People
would
like
to
discuss.
B
A
C
A
A
So
what
I'm
seeing
is
on
my
I'm
still
spending
roughly
two
us
dollars
a
day
on
elastic
container
service
for
kubernetes
and
ec2
other.
Now
I
don't
know
what
those
mean
and
actually
maybe
what
we
ought
to
check
is.
Are
they
in
a
different
region
somehow
and
you're
not
seeing
them
because
of
the
region
they're
in
so
they're?
Definitely
in
the
u.s
east
ohio
regions,
which
I
think
is
u.s
east
2?
A
B
A
D
B
A
A
B
A
A
C
D
A
That
that
is
already
good
enough,
because
the
the
only
place
I
was
seeing,
potential
charges
were
in
the
eks
cluster.
So
the
fact
that
you
had
one
is
a
big
victory
for
me
because
it
says,
even
though
I
can't
see
your
cluster,
when
I
look
at
the
same
account,
you
found
it,
you
were
able
to
delete
it
so
major
victory.
Thank
you
very
much.
A
A
A
A
Yeah
and-
and
you
are
welcome
to
before
we
merge
this-
we
will
actually
squash
all
of
this
out,
so
we
won't
in
particular,
because
a
number
of
the
pictures
that
I
did
are
with
with
the
brand
new
current
weekly
ui,
because
it
makes
better
pictures,
but
they
are
large
and
I
don't
want
to
waste
the
space
having
old,
outdated
pictures
in
there.
So
I
will
squash
this
before
we
before
we
or
squash
our
rebase.
Before
we
do.
The
final
merge.
C
A
So
as
part
of
that
I've
been
working
through
and
I
work
I
work
with
it
in
about
two
hour
chunks
and
since
I'm
a
kubernetes
novice,
my
two
hour
chunks
tend
to
be
spent
exploring
this
exploring
that
follow
the
directions
then
decode
it
and
as
part
of
that
I'll
make
comments
or
make
changes
and
push
them.
So
don't
be
shy
if
you
feel
like.
Oh,
I
changed
something
that,
for
you
was
important,
because
I
didn't
understand
it
well
enough
and
I
changed
it
wrong.
B
A
And
the
other
is,
I
think,
likely,
will
partition
the
content
into
other
locations
rather
than
the
scaling
page,
because
the
more
I've
more
I've
been
experimenting
with
it.
There's
managing
agents
right
and
that's-
we've
already
got
a
page
on
managing
agents,
that's
weak
on
content,
so
adding
kubernetes
would
be
a
big
win.
There's
more
on
choosing
on.
Let's
see,
there
is
there's
a
nice
section
on
installing
and
administering
agents.
B
A
B
A
D
A
A
A
All
right
so
that
pr,
I
suspect,
we're
probably
still
a
week
away
from
merging
it
just
because
of
the
pace
that
I'm
going
at
thanks
for
letting
me
take
the
time
to
go
through
it.
It's
been
very
instructive
to
me
and
and
I'll
keep
working
at
it.
I've
I've
spent
two
different
two-hour
sessions
this
week
and
I
assume
it'll
take
two
or
three
more
just
like
that.
A
Oh
hey
this
well,
this
has
been
so
educational
for
me
in
terms
of,
I
need
to
be
sure.
I
know
how
to
administer
kubernetes,
because
part
of
my
responsibilities
in
the
jenkins
project
is
dealing
with
our
kubernetes
server,
but
I'm
unskilled
in
that,
and
so
I
tend
to
avoid
it.
This
is
helping
me
stop
avoiding
it.
A
A
A
Oh,
are
you
sure
you
want
to
do
this
you're
going
to
make
this
a
draft
pull
request
and
a
draft
means
no
review
is
required
yet
so
I'm
going
to
convert
it
to
draft
and
notice
that
it
put
up
the
pretty
the
big
button
there
that
says.
Oh,
this
is
a
draft
now,
when
I'm
done
with
that,
when
I
think
oh
hey,
this
is
ready
to
be
reviewed.
B
A
B
B
A
So,
for
me,
one
of
the
things
that
earlier
review
might
have
might
have
helped
was,
let
me
grab
the
scaling
one.
The
pictures
here
inside
I've
shifted
them
so
that
they
they
are
much
smaller
in
terms
of
screen,
width
and
and
by
making
them
smaller.
They
oops
not
that
one
that's
one
of
the
existing
ones.
A
A
Oh,
we
were
oh,
my
sakes,
that's
embarrassing!
You
are
correct
and
I'm
not
ready
for
that
that
you're
right,
that's
that
is
really
awkward.
Let's,
let's
get
that
that
should
have
been
higher
priority
than
any
of
the
other
things
on
the
list.
Sorry,
let's
put
that
here
retrospective
and
we
had.
I
had
a
document
started
on
google
season
of
docs.
A
Let
me
see
if
I
can
find
it
just
a
minute
and
we
will.
We
will
start
with
that
retrospective.
Sorry
about
that
zenob.
Okay,
google
season
of
docs
retrospective,
there
29
2020
google
season
of
docs
retrospective.
Here
we
go
okay,
wow
that
that.
Thank
you
very
much
zenob.
You
are
wonderful,
sorry
that
I
forgot
that.
A
A
A
D
D
A
A
B
B
A
B
B
B
A
C
B
A
A
A
D
I
guess
the
one
thing
I
was
like,
I
didn't
really
see
us
have
many
many
tickets,
or
maybe
I
just
somehow
missed
that
in
a
lot
of
our
like
or
how
how
we
were
planning
out
the
work
and
advanced.
I
guess
it
was
mostly
just
through
google
docs.
I
didn't
know
if
it
would
be
better
to
have
tracked
that
somewhere
or
like
to
show
to
point
the
stuff.
I
don't
really
know
if
that
was
as
important
for
this
project,
but
it
might
have
been
a
good
place
to
like
solicit
early
feedback.
D
A
Well,
but
I
think
that's
an
interesting
one,
because
github
ish
issues
and
github
and
github
projects
are
both
being
used
in
different
parts
of
the
jenkins
project
in
portions
of
the
jank
of
jenkins,
so
github
issues
are
available
for
jenkins.io.
Here
we
could
have
used
issues
to
track
and
a
project
is
is
an
interesting
one.
For
me,
it
was,
I
found
github
projects
to
be
something
lighter
weight
than
jira
projects
than
jira
epics
see.
Where
did
that
go
retrospective?
A
A
D
Right
yeah,
I
don't
really
care
what
ends
up
being
used,
and
sometimes
github
is
easier.
It
could
have
issues
are
easier
than
it's
right
there
in
the
repository
I
didn't
know
if
it
would
be
like
it.
It's
kind
of
like
publishing
a
timeline
of
what
would
have
been
expected
or,
like
kind
of
maybe
been
able
to
share
that
out
with
the
wider
community
right.
D
Then
have
a
chance
for
people
to
make
comments
on
that
versus
like
because
we
were
doing
a
lot
of
things
on
google
docs,
and
that
was
great
for,
like
you
know,
going
in
and
editing
and
things
before,
making
the
pull
request.
But
it
wouldn't
be
given
a
chance
for
maybe
some
other
people,
the
community,
to
have
some
say
something
or
have
input
or
just
be
like
yeah.
I'm
really
excited
for
this
and
it's
something
they
can
track
and
follow
for
when
it
does
get
released.
C
A
B
A
A
C
A
A
A
A
D
A
B
Okay,
so
aside,
the
fact
that
mentors
might
not
have
time
also
then
consider
knowledge
base.
There
might
be
people
in
the
community
that
has
more
knowledge
about
the
topic.
We
are
working
on
say,
for
instance,
tustin
reviewing
the
pull
requests
on
helm
and
things
like
that.
So
I
think
that's
another
reason
to
give
us
a
second
time.
A
B
B
A
A
A
A
A
A
B
A
Kristen
that
okay
for
you
so
we'll
meet
again
on.
Oh
dear
wait,
a
second,
I
better
check
my
calendar
to
see
if
it's
january,
7th,
okay
january
7,
is
our
next
scheduled
meeting.
I
am
out
of
the
office
on
that
day
and
unavailable
for
a
personal
thing,
and
so
it
may
be
best
well
kristen.
Would
you
be
willing
to
run
the
next
meeting
or
we
could
ask
marky
to
run
the
next
meeting.