►
From YouTube: Jenkins Governance Meeting, Aug 11, 2021
Description
Jenkins governance meeting August 11, 2021 with topics including DevOps World, Discourse increasing use, JFrog investigation of artifact repository issues
A
Welcome
everyone:
it's
jenkins
governance
meeting
for
august
11.,
so
we've
got
gavin
logan.
A
Randall
becker
thanks
very
much
everyone
for
being
here.
I
had
only
two
items:
news
and
devops
world
on
the
jumbotron,
any
other
things
that
need
to
be
on
our
agenda
today.
A
A
From
the
epel
repository,
it
makes
it
more
consistent
with
debian
and
removes
a
bunch
of
legacy
code
from
java.
A
Next
piece
of
news,
jenkins
2.302.1lts,
is
coming
with
its
change
to
the
docker
images.
Jdk
elections
are
coming
up
in
december
and
did
I
get
it
right
this
time?
Oleg
and
newly
are
the
two
officers
two
board
members
up
for
election?
Yes,
that's
right!
Okay,
big
win
good!
I
am
teachable
contributor
summit
from
june.
I
still
have
the
action
item.
Sorry,
it's
carrying
forward
it'll
be
a
while
before
I
get
to
that.
One
next
topic,
then,
was
I
submitted
a
pull
request
asking
for
permission
to
update
the
jumbotron.
A
This
thing
right
here
with
the
devops
world
announcement
and
remove
the
outdated
items
on
it,
which
include
things
like
she
code.
Africa
contributes
on
and
cdcon,
and
things
like
that
contributor
awards,
those
could
be,
will
be
removed.
If
this
change
is
approved,
any
discussion
needed
on
the
proposal.
I
thought
it
was
approved.
A
B
A
A
B
A
A
A
Yeah,
it's
it's
mostly
about
a
financial
commitment
dollars
donated
or
people
donated
red
hat's
donated
people.
Github
hosts
all
of
our
repositories.
Jfrog
hosts
our
our
artifacts
cd
foundation
pays
our
rather
large
infrastructure
bills,
osl
hosts
equipment
for
us
and
cloud-based
funds.
People.
B
B
A
Right
so
yeah
good
good,
good
point,
so
digital
ocean
still
needs
to
be
added,
oracle
needs
to
be
added,
and
there
oh
and
scale
way.
B
Not
really
I'm
drafting
up
some
more
discourse
stuff.
I
have
some
updates
to
the
faq.
I
wouldn't
like
mine,
getting
feedback
on,
especially
from
you
mark,
because
I
don't
write
well
and
a
draft
email
to
send
out
to
blast
again.
If
assuming
we
want
to
go
down
this
route,
I
think
it
discourses
kind
of
tapered
off,
so
I
don't
know
if
that's
just
because
it's
summer
or
because
people
are
not
interested.
I
wish
people
would
tell
me,
but
you
know,
yeah.
B
Olivia
is
back
next
week,
so
we
can
have
a
bigger
chat
next
time
as
well.
I
think.
A
He's
back,
I
don't
know
when
he's
back,
he
is
next
week
yeah
next
week's
the
plan
and
for
me
at
least
it's
it's
a
clear
benefit.
I
know
alyssa
tong
really
likes
discourse,
strong
preference.
I
think
we've
we've
been
very
pleased.
At
least
I
have
with
the
feedback
that
we
get
from
blog
posts
by
pasting,
a
link
to
the
discourse
page
into
the
blog
post,
and
it's
just
a
good
feeling.
B
And
then
speaking
of
olivier,
j
frog,
it
was
on
info
list
is
looking
at
doing,
is
is
trying
to
investigate
some
of
the
issues
we're
having
with
copy
artifacts.
They
realize
that
we're
on
our
out-of-date
versions.
They
want
to
do
an
upgrade
and
that
will
be
arranged
when
obvi
is
back.
B
Oh
okay,
yeah,
apparently
there
was
a
bug
fix
for
something
to
do
with
copying.
Artifacts.
I
don't
I
don't
know
what
mailing
list
is.
I'm
not
too
many
mailings
to
know
which
one
it
was
in,
but
yeah,
apparently
they
have.
It's
been
fixed
in
one
of
the
more
recent
ones
and
we're
running
an
old
one.
So
they
want
to
do
an
upgrade
to
hope
that
fixes
things
so.
A
A
Good
all
right,
thank
you,
weldon
and
that
copy
artifact
performance
is,
is
not
critical
for
typical
releases,
but
becomes
critical
for
security
releases.
So
2.302.1
is
not
a
security
release.
Therefore
we're
okay
for
august
25,
but
predictably,
there
will
be
something
in
the
302
line.
That
probably
has
a
security
fix
at
some
point.
B
Oh,
it
reminds
me,
I
mean
I'm
sure
jfrog
will
eventually
want
a
bit
of
an
outage.
To
do
this.
Do
we
link
status
page
anywhere?
Is
that
something
that's
super
public?
Yet.
A
B
Cause
I
was
thinking
about
how
there
was
a
discussion.
I
think
it
might
have
been
the
java
11
one
about
how
we're
doing
announcements
and
stuff
like
that.
So
we
don't
have
a
formal
policy
on
how
where,
when
how?
What
we're
doing
for
any
sort
of
announcements
affect
users,
so
you
know
artifactory
being
down
for
half
an
hour,
not
the
end
of
the
world,
but
it
would
affect
users.
You
know
like
that
kind
of
thing
right,
so
it
is
something
we
should
think
longer
term
about
how
we
want
to
do.
A
Yeah
so
we've
we've
used
blog
posts
in
the
past
to
announce
outages
like
that,
but
I'm
not
sure
how
effective
that
is.
We
can
continue
that
and,
in
addition,
add
announcements
on
status.jenkins.io
because
it
has
the
concept
of
a
scheduled
outage.
If
I
remember
right.