►
From YouTube: 2023 09 01 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
Welcome
it's
documentation,
office
hours.
This
is
the
first
day
of
September
2023..
Thanks
for
being
here,
topics
that
I
had
on
my
list
quick
overview
of
blog
posts,
brief
discussion
of
Google
summer
of
code.
We
were
hoping
that
ashitosh
might
join
us
and
then
some
leftovers
from
previous
previous
sessions
about
plug-in
bill
of
materials,
version,
Java,
11,
17
and
21.,
and
that's
pretty
much
it
of
topics
that
I've
got
Chris
any
that
you
want
to
add.
B
Maybe
should
I
like
we
have
like
the
docker
companies
project
successfully
completed
even
there's
like
all
the
and
all
the
items
in
scope
were
like
or
have
been
done
to
satisfaction,
but
so
it
was.
It
was
good
progress.
One
boy.
A
A
Great
excellent
yeah
this
this
is
I.
Just
I
was
just
reading
comments
from
a
user
who
was
saying.
Hey
such
and
such
a
switch
doesn't
work
in
the
tutorial,
and
it
was
one
of
the
long
involved
set
that
is
now
completely
removed.
Once
we
get
this
finally
integrated,
it
will
be
gone
and
they'll
just
type
Docker
compose
up
and
yeah
much
better
much
much
better.
Yeah.
B
B
Yep
so
I
was
like
we
I
think
we
have
finally
have
a
like,
like
an
almost
Wicked
function,
a
draft
for
the
entire
site,
except
for
the
pages
we
haven't
implemented
with
Gatsby.
Okay,
because,
like
some
of
the
pages,
will
be
implemented
in
yazby
and
then
those
needs,
those
who
need
to
be
integrated
into
the
whole
website.
B
And
we
have
like
abandoned
idea
of
using
a
strappy
backend,
even
though
that
was
that
was
waste
between.
B
Before
with
the
community,
so
we're
gonna
simplify
the
process,
so
we're
going
to
retain
the
existing
reviewing
process
for
blog
posts.
A
Oh
okay,
so
you'll
use
GitHub,
yep,
very
good.
Okay.
A
B
Next
up
would
be
to
focus
on
attacking
the
and
toy
side
lines
scenes
like
we
have
faked
most
broken
legs
previously,
but
from
previously,
but
but
there
might
still
be
some
broken
links
somewhere.
So.
A
B
Have
some
great
chocolate
because
I
track
with
I
checked
with
track
with
band-aid,
and
he
told
me
like
the
only
thing
that
we
we
currently
have
for
automation.
It
belongs,
but
that'll
be
a
good
start
except
like
we'll
have
to
analyze
like
what's
installed
or
what's
in
the
logs.
B
A
Very
good.
Well
then,
certainly
there
are
there
are
automated
link
Checkers
so
that
that's
a
that's!
That's
happened.
We've
done
that
before
and
and
generated
long
lists
of
oh
here,
A
bunch
of
broken
links
from
jenkins.io
already
so
I
think
I
I
I
see
Good
Hope
for
later
automation,
not
not
required
immediately,
but
good
and
good
chance
to
apply
it
later.
A
B
I
think
well
I
think
for
the
project
like
we
might
be
able
to
complete,
like
all
the
models,
the
only
sort
of
set
out
to
do
at
the
beginning,
congratulations
it
might
be
able
to
because
they
well.
The
blog
is
now
easier
to
do
without
the
strappy
back
in.
A
Right,
okay,
and
by
not
using
the
strappy
back
end
instead
staying
with
GitHub
you've,
you've
simplified
I,
like
that.
That's
great.
B
A
A
B
A
This
this
is
the
first
time
that
I
know
of
anyway,
when
a
a
contributor
became
a
maintainer.
So
congratulations
to
harsh
yeah.
B
Yeah,
we
should
talk
about
it
a
little
bit
because,
like
I
think
like
there
was
I
I
saw
like
some
discussion
on
on
GitHub
before
I'm,
not
sure
if
it's
like
related
to
the
work
now
but
I
think
that
was
a
mentioning
of
like
some
kind
of
an
issue
Andrew.
Let
me
check
because
I
think
it
was
something
to
do
if,
like
the
score
being
like
the
way,
it's
calculated,
it's
not
like
not
ideal
and
or
something
like
that.
It
was
a
like
on
GitHub
before
they
see
that.
A
Okay
well,
I
know
that
I
know
that
that
Adrian
was
working.
Adrian
was
was
working
on
what
I
call
a
code
refactoring
or
a
code
improvements
that
that
may
help
to
grudy's
work.
B
A
B
I
think
it's
I
get
they're
working
on
some
like
I'm,
not
sure
I'm,
not
entirely
sure
about
a
trick
with
progress,
because
I
can
she
was.
She
wasn't
being
very
queer
last
time
during
the
meeting
except
like
she
sat
like
she
was
working
on
the
third
party
repo
Pope
again,
and
it
was
with
holy
for
a
while,
because
there
was
an
issue
with
how
to
get
the
first
party
papers.
B
B
But
other
thing
I
thought
you
could
use
project
like
so
I'm,
not
I
will
need
to
check
on
the
documentation
for
that
project
because,
like
I
I
I'm
kind
of
having
the
feeling
that
we
might
need
to
act.
To
like
add
some
dogs
to
a
wig.
A
B
B
A
A
A
So
what
we've
got
is:
we've
got
Java
11,
reaching
end
of
life
in
October
of
2024
Java
17
has
been
well
supported
and
Java
21
coming
online
in
sept
mid-september,
and
what
I
was
looking
at
is
trying
to
find
a
way
to
describe
a
proposal
for
which
version
should
be
supported
when
oh
I
need
to
hide
some
of
the
rows.
I've
got
my
worries
about
here.
We
go.
Let's
do
this.
A
I'll
hide
the
product
that
I
was
worrying
about
for
now.
Hide
that
the
cbci
thing
is
a
cloud-based
product,
okay
and
so
I
I
have
to
be
sure,
I
think
about
them,
but
in
terms
of
community
discussions
we
don't
have
to
worry
about
them
as
much
from
the
community
side,
yeah,
okay,
so
here's
the
picture.
B
A
The
the
reasoning
there
was,
we
don't
want
to
end
that
prematurely,
but
we
can't
support
it
after
Java,
after
open
jdk
stops
supporting
it
yeah.
So
then
we
have
to
transition,
and
my
initial
proposal
had
been
hey.
Let's
make
Java
21
be
required,
but
the
feedback
I've
I've
received
from
the
cloudbees
Enterprise
customers
is
no.
A
So
that's
why
this
is
trying
to
get
us
to
a
a
state
where,
given
a
six-year
life
span
for
a
Java
version,
so
Oracle
releases,
the
Java
version
and
the
open
jdk
project
takes
it
up
and
they'll
support
it
for
six
years
from
its
release,
so
2023
September
goes
until
2029
for
Java
21.
So
that's
this
green
bar
here.
B
A
B
Like
hang
on
so
I
just
want
to
ask
a
question.
First,
like
for
Java
17,
for
example,
it
would
be
quite
for
for
March
25th
to
September
25th.
A
B
About
between
March
26
and
March
27th.
B
11
is
fine
that
was
fine,
but
17.
21
25
29
I
see
like
a
patent.
It's
like
there's
a
period
when
the
operation
is
required,
but
afterwards
it's
unsupportunity.
Oh.
A
A
Absolutely
right:
that's
they
they
certainly
they're
they're.
One
of
the
one
of
the
challenges
here
right
is
balancing
the
the
needs
of
the
users
and
the
needs
of
the
developers,
and-
and
that's
that's
what
this
is
trying
to
strike
a
compromise
there
between
hey
the
developers
would
just
as
soon
support
one
Java
version
and
not
have
to
do
two,
but
the
users,
especially
Enterprise
users,
say
hey.
We
take
a
long
time
to
move
from
one
version
to
another.