►
From YouTube: 2023 09 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
Hello
and
welcome
to
the
Jenkins
documentation
office
hours
today
is
September,
9th
September
7th.
Sorry,
that's
my
American,
showing
I
can't
read
things
properly,
but
is
September
7th.
This
is
the
EU
US
edition,
and
today
we
have
myself
and
Bruno
Marsden
joining
Mark
is
unavailable
to
join
us
today,
so
if
Chris
Stern
or
anyone
else
has
time
to
show
up
and
we'll
welcome
them
in
other
than
that,
we'll
go
over
the
agenda
so
for
the
agenda.
A
A
A
The
process
of
choosing
a
plug-in,
build
materials
version,
the
Java,
11,
17
and
21
support
proposal
for
Jenkins
is
something
that
Mark's
been
working
on
in
other
developments
have
happened
with
Mark
knot
here
we
might
not
have
his
nice
planning
schedule
proposal,
but
even
still
that's
something
that
we've
been
discussing.
A
So
this
is
something
that
I
noticed
have
has
been
in
the
the
open
pull
requests
that
Bruno
actually
really
saw
it,
because
I
saw
your
recent
comment
on
it
about
users
suggesting
what
about
using
wget
instead
of
curl,
oh
yeah,
we'll
talk
about
that.
A
little
bit,
I
think
it's
just
a
good
topic
to
talk
about
here
on
the
office
hours,
the
chicken
stock
contributor
project.
A
This
is
something
that
hasn't
necessarily
been
brought
up
here
in
documentation
hours
previously,
but
we're
actually
getting
to
the
point
of
being
ready
to
or
gearing
up
to,
publish
and
make
things
live
in
the
coming
weeks.
So
I
do
want
to
talk
about
that
and
also
see
if
there
might
be
anyone
that
can
help
out
with
some
of
the
HTML
generation
and
then
last
up
on
the
agenda.
For
today,
I
have
devops
World
Tour,
that's
starting
next
week
and
we're
gonna
have
Jenkins
after
hours
sessions.
A
I
forget
exactly
what
Mark
called
them
earlier,
but
once
the
Dallas
World
Tour
a
day
is
complete
or
if
it's
two
days
like
next
week
in
New
York
we're
gonna,
have
Jenkins
discussion
time
after
hours
meeting,
Social,
Hour,
I,
don't
again
I,
don't
know
what
we're
calling.
A
B
A
Okay,
so
first
episode,
so
we've
had
several
blog
posts
published
recently
the
risk
five
blog
post
from
Bruno
and
Docker
compose
and
gitlab
plugin
from
farsh
and
Oshkosh
respectively.
A
We're
published
just
prior
to
the
two
week,
but
yeah
like
I,
said
we're,
including
them,
because
they
have
to
do
with
Google
summer
code
and
they
are
recapping
their
Project
work,
which
is
great
to
see
they're
sharing
their
insights,
their
challenges,
their
their
successes,
everything
from
their
projects,
which
is
really
nice
to
see
it
does
great
work
all
around
from
the
Google
summer
code
participants
for
their
consistent
work
and
dedication
to
getting
these
things
you
know
taken
care
of,
and
then
the
risk
five
blog
post
that
Bruno
had
written
is
really
nice.
A
It
paints
a
great
picture
of
what
the
future
can
look
like
for
Junctions,
including
Java
support
risk,
5,
Arch,
64
rm64,
just
kind
of
like
all
the
different
developmental
options
that
Jenkins
could
have
going
forward,
and
thank
you
yeah,
of
course,
is
there
anything
that
you'd
like
to
point
out
call
out
or
I.
B
Think
the
first
post
about
GDK,
21
and
we'll
see
lots
of
more
posts
by
people
who
know
what
they
are
talking
about,
for
example,
Mark
Wait
about
GDK
21,
because
I'm
all
when
it
comes
to
experimenting
I
love
what
I'm
doing
but
I'm,
not
the
one
who
worked
the
most
on
gdk21
for
Jenkins,
not
at
all.
It
was
just
fun
to
yeah
fun,
to
experiment
with
jdk
21
and
risk
5..
At
the
same
time
and
yeah,
you
will
see
more
articles
about
jdk,
21
and
we'll
talk
about
that.
Maybe
later
in
the
meeting.
B
A
C
A
No
worries
I,
like
it
we'll
talk
about
my
head
shots
next
time,
but
yeah
so
fantastic.
Thank
you
so
much
Bruno
for
that
and
a
bit
Insight
and
then
the
last
two
blog
posts
we
have
listed
here.
A
So
Mark
just
wrote
this
yesterday,
but
it's
just
a
brief
or
a
brief
preview
of
what
devops
world
2023
will
look
like
for
for
the
Jenkins
project,
so
introductions
to
Tim
Jacob,
Olivia,
olami
and
Mark
White
at
what
their
backgrounds
are,
what
their
Marx's
goes
into
a
little
bit
about
what
he's
going
to
be
talking
about,
but
yeah,
just
a
quick
little
preview
for
those
attending
for
those
wanting
to
attend,
and
then
this
was
just
published
yesterday
as
well
later
in
the
day.
A
But
this
is
part
of
the
artifactory
bandwidth
reduction
project
that
has
been
going
on
for
some
time
now.
A
Just
some
updates
regarding
Maven,
Central,
Catherine
and
kind
of
what
we're
learning
with
the
respective
downtimes
that
have
been
going
on.
This
is
helping
us
figure
out
what
is
causing
bandwidth
overuse.
We
did
have
some
we've
had
issues
recently
with
overuse
by
some
users.
We
have
managed
to
nip
some
of
that
in
the
bud,
but
not
all
of
it.
So
this
is
still
the
ongoing
process
of.
How
can
we
make
the
usage
a
little
bit
less?
Well,
huge
I
guess
is
the
best
way
to
put
it.
A
Jfrog
would
love
for
us
to
get
down
a
little
bit
further
than
we're
at
now.
So
that's
the
that's
the
gold
project
and
that's
what
we're
working
on.
A
Okay,
anything
else
in
the
blog
posts,
no.
A
Great
so
then,
next
up
Google
summer
code,
so
as
I
had
mentioned
earlier,
Google
summer
code
is
getting
towards
the
back
end
of
things
at
this
point.
I
know
that
we
still
have
a
few
weeks
and
that
the
participants
are
going
to
be
creating
their
Recap
blog
posts
to
do
a
full,
just
kind
of
retrospective
on
their
project
and
what
they
worked
on
and
everything
that's
what
we
use
and
have
used
in
the
past
for
Google
as
one
of
the
one
of
the
project.
A
A
So
there
should
be
a
few
more
coming,
but
that's
only
that's
and
that's
due
to
the
fact
that
jigrudi
has
submitted
a
few
different
blog
posts
regarding
the
different
probes
that
she
had
worked
on,
but
that's
their
smaller
individual
blog
posts
for
each
probe,
as
opposed
to
a
full,
Recap,
blog
post,
so
little
things,
but
as
far
as
the
projects
go,
so
the
doc
compose
has
been
successfully
completed.
A
Four
out
of
five
tutorials
are
now
executing
with
a
single
command
and
there
is
some
remaining
work
to
take
on,
but
the
Project's
been
that's
been
completed.
So
this
is
all
you
know
after
the
fact
this
is
you
know,
in
addition
to
not
something
that
we
needed
to
do
to
get
past
the
finish
line.
So
that's
fantastic,
yeah,
the
next.
So
then,
we've
got
the
version.
Documentation
for
building
jenkins.io
that
Barbie
has
been
working
on.
A
The
demo
site
has
been
really
great
to
see.
Vandy
and
Chris
Stern
have
been
demoing
this
respectively
at
various
meetings
over
the
last
couple
weeks
for
the
genuine
project
and
the
Jenkins
Community,
which
is
great
to
see
and
they're.
Getting
to
the
point
where
they're
it's
they're,
almost
at
a
working
site,
which
is
amazing,
you
have
to
be
integration,
needs
some
work
and
they've
just
abandoned
the
strap
strappy
back
end
idea,
which
was
specifically
for
blog
post
reviews
and
then
yeah.
A
A
A
All
right
next,
under
the
Google
summer
code,
so
the
gitlab
plugin
modernization
project
has
completed
successfully
as
well,
which
is
great
harsh,
has
actually
agreed
to
continuous,
plug-in
maintainer
and
that's
a
first
time
a
contributor
became
a
maintainer
for
Google
summer
of
code,
so
that
is
amazing
in
and
of
itself
just
thank
you
harsh
for
the
work
and
for
stepping
up
to
maintain
the
plugin
as
well.
That's
amazing
and
that's
yeah
really
heartening,
to
see
from
the
Google
server
code.
A
It
does
still
need
some
more
testing,
but
it's
completed,
and
you
know
that's
the
main
point
here.
Everything
will
need
some
work
and
maintenance.
After
the
fact.
That's
just
how
things
go
so
knowing
that
but
having
it
be
completed
and
ready
to
go
and
have
harsher's,
enthusiasm
and
and
dedication
to
that
is
yeah,
like
I,
said
really
hard.
A
And
then,
finally,
the
plug-in
Health
scores
so
Adrian
has
been
working
been
working
on
some
code
improvements
that
could
help
degree
in
this
the
yeah
there
have
been
a
couple
of
probes.
There
have
been
several
probes
that
have
been
our
look
to
be
completed
and
merged.
A
There
might
be
one
other
one
that
I'm
forgetting
about
right
now,
but
everything
looks
to
be
going
well
here.
Yeah
this.
This
is
actually
the
project.
Documentation
might
need
additional
documentation
gear
for
the
Health
score,
and
that
could
be
something
that
we
do
for
Octoberfest
Adrian
would
still
be
available
and
kind
of
guide
or
potentially
help
with
that,
but
if
we
do
after
Octoberfest
that
gives
the
opportunity
for
anyone
else
to
come
in
and
help
out
so
yeah
no
good
opportunity.
There.
A
All
right
next
on
the
agenda,
so
this
is
something
that
we've
been
discussing.
The
last
handful
of
weeks
is
how
to
describe
the
process
of
choosing
a
plug-in
bill
of
materials
version,
so
this
is
a
result
of
a
discussion
being
started
in
this
PR.
That
Kyle
had
submitted
so
basically
saying
that
the
instructions
are
a
little
unclear
or
not
explicit.
A
When
saying
which
Bond
version
to
choose
based
on
the
Jenkins
version
itself,
there
are
a
couple
different
pages
to
go
to
to
get
the
releases
so,
for
instance,
there's
our
our
GitHub
release
page
where
you
can
scroll
through
and
see.
You
can
also
search
here,
but
the
other
end
of
that
is
I.
Think
yeah.
This
one
just
lists
them
out
here
very
directly,
straightforward
and
Kyle's
saying
this
is
this
is
just
easier
to
kind
of
navigate,
because
it's
more
clear
and
Direct
in
that
sense,
and
then
Mark
responded,
saying
like
hey
like
what.
A
If
we
do
something
where
we
have
that
bomb
version,
and
we
explain
like
what
this
is
for
or
like
the
specific
use
case,
you
would
want
this
for
such
as
having
2.361.x
be
the
first
one
to
require
drop,
11
or
346
being
the
last
Jenkins
to
support
job
at
eight.
So.
B
Yeah
that
would
help
this
week,
as
I
was
trying
to
help
a
user
who
was
having
some
trouble
with
the
pump
plugin
I
say:
oh,
you
know
what
I
try.
My
luck,
I
will
try
to
update
the
pan
plugin
just
in
case
you
know,
because
he
was
trying
to
use
it
on
Bookworm
and
it
used
to
work
on
Debian
11,
but
it
doesn't
work
anymore
on
Debian
12.
anyway.
So
I
said
hey.
B
B
C
B
Yeah,
why
so
definitely
we
need
something
better.
A
Yeah
definitely
I
think
Mark
had
mentioned
even
using
the
update
CLI
to
do
that
sort
of
thing,
if
I'm
not
mistaken,
that
was
an
option
that
he
had
yeah.
A
That
could
be
an
option
that
we
used
in
the
future
and
I
think
he
actually
with
Asia
doc's
office
hours
I
think
they
determined
where
they
could
add
in
this,
this
exact
sort
of
guidance
and
if
we
go
to
the
bomb
repo
I'm
not
mistaken
in
the
in
the
default
readme
here,
yeah
I
think
this
is
the
one
yeah.
This
is
the
one
that
Mark
went
to
now
in
the
read
me
for
the
bomb
repo.
So
there
there
has
been
some
update,
but
yeah.
It's
not
nothing.
A
That
has
been
enough
to
move
this
original
PR.
A
Yeah
exactly
this
is
the
kind
of
thing
that
is
really
useful,
not
only
for
like
this
instance,
but
going
forward
other
instances
or
if
this
comes
up
again
in
the
future.
Maybe
we
can
take
what
we've
learned
here
and
even
improve
further
it's
one
of
those
just
kind
of
like
Universal.
A
All
right,
the
next
thing
on
the
agenda
is
the
Java
11
Java
17
and
Java
21
support
proposal
that
Mark's
been
working
on,
so
the
long
and
short
of
it
is
that
Java
11
is
currently
supported,
as
well
as
Java,
17
and
Java
21
is
going
to
be
supported
in
Jenkins
as
well.
We've
been
working
on
testing
with
Java
21,
so
this
has
been
happening
and
it's
happening
a
lot
faster
than
originally
anticipated,
so
the
odds
of
Jenkins
supporting
Java
21
after
its
release
this
month
very
very
highly
likely.
A
A
Yeah,
this
is
very
much
a
work
in
progress
and
there's
still
a
lot
that
needs
to
be
done
here
but
yeah.
The
idea
is
that
we
have
a
plan
in
place
to
drop
Java
11
support
eventually
include
Java
17
support
potentially
require
Java
17
and
then
supporting
Java
21
and
when
we
can,
when
we
might
start
requiring
Java
21.
A
and
even
then
that's
been
a
bit
of
a
discussion,
some
developers
feel
that
maybe
just
skipping
Java
17
requirement
and
just
requiring
Java
21
could
be
beneficial.
It
does
provide.
You
know
that
much
more
Power
functionality,
tooling
testing
et
cetera,
et
cetera
Etc,
but
that
is
yeah.
That's
that's
a
little
further
away
from
the
rest
of
this
right
now.
A
Is
there
anything
else
that
you
wanted
to
share
about
the
or
any
insights
you
have
on
that
one
Bruno!
No.
B
I
I
don't
have
that
many,
but
I
think
the
goal
is
to
have
Jenkins
support
each
LTS
version
of
Java
for
four
years
Java
will
be
supporting
their
LTS
for
six
years,
but
I
think
we
will
get
rid
of
the
two
last
years
and
move
to
the
next
LTS
version.
I
think
that's
the
goal
today.
As
you
say,
there
are
still
lots
of
discussion
to
be
had
yeah.
We
have
to
discuss
that
more
and
more
and
more,
but
hopefully
Jenkins
will
be
able
to
support
jdk
21
by
the
end
of
October.
A
A
So
far,
so
good,
so
everything
seems
to
be
going
pretty
smoothly
on
that
part,
which
is
nice,
Java
21
seems
to
be
proving
pretty
useful
in
a
lot
of
the
test.
Cases
and
experimentation.
That's
been
going
on
so
that
part,
at
the
very
least,
is
encouraging
to
see
and
yeah
lots
more
work
to
come
on
there.
A
This
request
I
just
wanted
to
bring
up
and
have
a
short
discussion
about
it.
So
the
reason
being
is
this
user
brought
up
that
the
way
that
they've
gone
ahead
and
installed
and
set
up
their
Jenkins,
not
using
Pearl
their
default
or
their
their
Main
action
was
using
wget,
and
so
this
is
all
very
dependent
on
how
you're
setting
up
your
own
operating
system
your
own
Jenkins
instance.
So
it's
not
consistently
an
issue
or
something
that's
hard
and
fast
tied
to
a
specific
usage.
B
Yeah,
so
it
looks
like
it's
default
on
Ubuntu,
but
I've
never
ever
met
an
instance
of
Ubuntu
Debian
or
whatever
without
curl
I.
Think
it's
one
of
the
first
things
I
install
but
yeah
I
can
get
it.
Some
people
get
a
fresh
installation
of
human
too,
with
nothing
no
additional
package
installed
and
then
they.
C
B
To
install
Jenkins
and
it
fails
yeah
but
as
I
wrote,
I'm
in
the
middle
of
the
brinjal
I,
don't
know.
If
that's
it's
us
iTune
I
mean
maybe
I
was
trying
to
translate
something
French
that
doesn't
make
sense
in
English,
but
whatever
I
don't
know,
each
of
the
two
proposition
makes
sense
to
me:
you
can
keep
curl
and
say:
oh
it's
a
privacy
sign
by
the
way
or
okay
we
could
switch
to
using
wget
as
each
and
every
dstore
is
supposed
to
have
it
I,
don't
know.
What's
your
feedback
about
that.
A
So
I
was
I
was
thinking,
I
was
looking
at
it,
and
I
was
looking
at
your
response.
Bruno
and
I
was
thinking
that
either
some
kind
of
disclaimer,
potentially
at
the
top
of
a
page,
at
some
of
the
on
on
the
top
of
some
of
these
Pages
or
potentially,
if
there's
a
specific
section
that
seems
to
be
a
worse
offender
than
others,
maybe
but
yeah
I
would
say
the
disclaimer
in
my
head
instead
of
saying
something
like
you
should
have
curl
installed
is
something
like
if
you
don't
have
Crow
installed
use.
A
You
know
this
is
what
you
that's,
where
you
would
put
your
action
item
into
or
like
and
if,
if
you're
not
using,
curl
replace
curl
with
wget
or
something
like
that,
yeah.
B
C
A
Yeah
I
I
guess
what
I'm
saying
is
like,
even
if,
even
if
we
don't
encourage
them
to
install
or
use
or
like
install
something
specific
or
use
something
specific.
If
we
just
trust
that
they
know
what
they're
doing
trust
in
the
reader
is
sometimes
tough,
because
you
want
to
give
them
as
much
help.
A
Obviously,
without
you
know,
making
it
too
dumbed
down
at
the
same
time,
but
yeah
I
feel
like
there
might
be
something
we
could
do
where
we
don't
necessarily
replace,
because
I
don't
want
to
replace
curl
with,
but
you
get
throughout
the
documentation.
I
think
curl
is,
like
you
said,
pretty
universally
used
and
installed
on
default,
but
Yeah,
just
something
small
to
say:
hey.
A
If,
if
you
don't
have
this
use
this
or
something
like
that,
but
that
would
also
that
requires
the
user
to
know
what
they
have
installed
and
what
they're,
using
and
yeah
it
could.
It
could
be
tough
I,
think
it
yeah
just
bought
it.
I
feel
like
it
boils
down
to
the
the
user
who's
performing
these
actions
and
their
their
knowledge
of
the
the
their
environment.
B
Yeah
I
forgot
the
name
of
what
I
want
to
talk
about,
but
do
you
think
we
could
have
an
expandable
section?
You
know
just
in
case
if
you
don't
have
curl
and
then
they
click
and
something
appeals
with
the
wget
command
instead
of
curl
or.
A
Like
like
an
example,
drop
down
or
like
that,
you
could
that
would
be
collapsed,
but
could
be
expanded
and
then,
if
yep
and
then
it
says,
if
you
don't
have
curl
use
this
kind
of
thing.
A
I
like
that
too
yeah
that's
I
mean
and
that's
the
kind
of
thing
that
I
was
thinking
of,
because
I
don't
want
to
put
a
disclaimer
at
the
top
of
every
page
or
like
at
you
know
at
all
the
install
Pages
or
something
something
like
that
might
be
a
better
option,
especially
because
we
couldn't
put
it
just
in
front
of
code
blocks
where
this
would
come
up
instead
of
the
whole
page.
So
yeah
yeah
I
like
that
idea,
it's
a
little
more
elegant.
A
But
yeah,
but
I
I,
thanks
for
discussing
that
with
me,
Bruno
I
think
it
was
like
I
said
a
great
example
of
where
there
could
be
questions
or
challenges
to
the
documentation,
but
we
have
to
it's
not
like
a
an
easy
decision.
It's
something
that
we
definitely
need
to
talk
about
as
a
community
at
a
project.
A
So
I
notice
we're
at
time
I
will
do
the
devops
world
tour
info
really
quickly.
I
would
like
to
take
a
minute
just
to
talk
about
the
computer
project.
If
that's
okay
with
you
Bruno.
A
Gary
yeah,
so
devops
World
Tour
starts
next
week.
Again
we're
going
to
be
touching
multiple
locations,
multiple
countries
across
the
world,
New
York,
Chicago
and
Santa
Clara
California
are
going
to
be
our
U.S
stops.
Mark
White
will
be
attending
all
of
those
and
we'll
be
giving
a
talk
as
well
and
then,
after
the
end
of
all
of
these
devops
World
Tour
sessions,
we're
going
to
have
let's
talk
about
Jenkins
time
so
once
the
conference
is
over,
we'll
have
separate
separate
session.
A
Where
we'll
be
able
to
talk
all
things,
Jenkins
Mark
will
be
at
the
U.S
ones.
Olivia
Lami
and
tinjicom
will
be
at
the
Singaporean
London
ones
respectively
and
they'll
be
getting
their
own
docs
there
as
well
again.
The
preview
page
blog
post
went
up
today,
so
it
is
there
for
further
information
and
the
devops
world
tour
site
is
still
available
for
registration
if
you
haven't
already
yet
and
last
thing
on
the
agenda.
A
So
brief
summary
we've
been
working
on
this
for
some
for
some
time
now
we
want
to
recognize
and
acknowledge
and
Spotlight,
highlight
and
show
appreciation
for
the
top
contributors
to
the
judgments
project.
The
this
is
an
open
source
project
that
would
not
be
where
it
is
if
it
were
not
for
the
contributions
and
the
dedication
and
hard
work
of
the
community
and
the
contributors
that
continue
to
prop
Jenkins
up
as
it
is
today.
So
we
are
working
on
getting
a
compilation
of
contributor
stories.
A
Each
of
the
top
contributors
has
been
will
be
responding
to
a
questionnaire
sent
out
or
doing
an
interview
with
me
where
we
can
capture
their
stories,
their
experiences,
etc,
etc,
and
then
we're
going
to
be
publishing
these
live
on
either
the
jenkins.io
site
or
stories.jenkins.io
site,
but
basically
we
just
wanna,
show
and
Spotlight
the
various
contributors
to
Jenkins
and
give
them
their
moment
in
the
Sun
that
they
deserve
for
all
this
we've
gotten
to
the
point
now,
where
we're
getting
responses
back,
and
our
next
step
is
to
create
a
landing
page,
slash
overview
page
for
the
contributors
and
the
individual
contributor
Pages
themselves,
just
to
shout
out
Christina
Pisa
gayley,
who
put
this
mock-up
together,
just
amazing
and
just
really
wonderful
to
work
with.
A
Thank
you
so
much
Christina
for
doing
this.
This
is
just
a
really
nice
little
landing
page
that
we
discussed
simple,
we'll
have
a
different
25
is
not
hard
and
fast.
That's
not
going
to
be
a
part
of
that
text
there,
but
that'll
be
changed.
We
have
the
contributors
and
then
we'll
have
the
individual
contributor
page
like
this.
Where
we'll
have
their
interview
posted
links,
location.
This
is
also
to
show
just
how
Global
the
reach
of
the
Jenkins
project
is
and
get
people
connected.
A
Yeah
really
excited
and
yeah
Christina
did
amazing,
with
this
just
coming
up
with
a
mock-up,
Alyssa
and
I
met
with
her
this
past
Tuesday
and
she
was
able
to
get
this
put
together
in
a
couple
days.
A
So
yeah
just
once
again
massive
thanks
to
her
and
appreciate
the
just
the
ability
to
be
open
to
this
and
helping
us
out
with
this
so
yeah.
If
anyone
has
any
sort
of
HTML
skills
and
would
be
interested
in
helping
put
this
together,
HTML
is
not
my
forte.
Unfortunately,
I
am
not
a
developer.
So
if
anyone
has
any
HTML
skills,
they
want
to
flex
share
and
maybe
even
show
me
how
to
do
some
things
more
than
happy
to
take
a
look.
A
I
have
posted
in
the
ux
Sig
getter
Channel
as
well,
so
it
is
there
too,
but
yeah.
If
anyone
has
any
insights
or
would
like
to
assist
in
building
that
site.
Just
let
me
know.
A
B
Contributor
recognition
and
appreciation
is
a
massive
subject
for
open
source
communities,
I'm
part
of
something
called
community
maintainers
on
GitHub.
It's
a
special
repo
where
people
discuss
about
their
open
source
community
and
lately
there
has
been
a
subject
called
contributor
recognition
and
appreciation,
and
all
the
people
participating
are
facing
the
same
issue
as
we
have.
How
should
we
put
people
under
the
light?
B
And
frankly
there
is
no
answer:
everybody
does
things
more
or
less
looking
the
same
and
they're
not
happy
with
that
no
magical,
skills
or
wound
or
whatever
that
can
help
lots
of
people
have
thought
of
Technical
Solutions
to
this,
for
example,
you
know
finding
all
the
contributors
in
their
GitHub
repos
and
then
crafting
automatically
page,
which
lists
all
the
contributors
with
their
avatars
or
whatever,
but
most
of
the
time
it
almost
works,
but
it
doesn't
work.
B
There
are
lots
of
manual
integration
things
to
modify
by
hand
afterwards,
because
they
also
want
to
link
that
to
people's
LinkedIn
account,
for
example,
Twitter
account
whatever,
and
you
have
to
do
that
by
hand,
because
people
may
be
called
as
me
put
down
on
the
platform
Gunter
on
another
one,
and
so
it
doesn't
match.
So
the
technical
solution
is
not
there.
I
think
we
may
gather
some
statistics
whatever,
but
there
will
be
some
things
to
do
by
real
human
I'm
afraid.
A
If
that
it's
funny
that
you
mentioned
that,
because
when
we
were
discussing
different
ways
to
highlight
and
appreciate
that
one
of
the
things
that
I
had
thought
of
was
one
of
those
contributor
kind
of
Bot
display
tables,
yeah,.
A
Yeah,
that's
the
one
I
was
looking
at
and
then
when
I
was
trying
to
set
it
up
in
my
own
repo
to
test
it
out.
Those
are
the
exact
things
I
found
out
for
myself
too,
how
it's
a
lot
more
work
and
involved
than
it
feels
like
it
should.
A
Yeah
but
yeah,
it's
good
to
know
that
that
other
people
are
having
kind
of
facing
the
same
thing:
it's
definitely
a
Hot
Topic
and
in
my
own
research
and
trying
to
figure
out
how
we
could
do
this
appreciation
I,
you
know
it's
tough,
with
open
source
projects,
you
know
not
being
for
profit
necessarily
takes
like
it's
hard
to
do,
recognition
in
a
form
in
a
forum
where
there
is
necessary,
not
necessarily
monetary
value
associated
with
that
appreciation
or
like
that
hard
work
that
you're
putting
in
it's
like
it
takes
passion.
A
It
takes
dedication.
It
takes
a
lot
of
things
that,
unfortunately,
do
not
always
get
valued
in
how
we
would
maybe
like
them
too,
but
yeah,
there's
yeah.
B
C
B
Know
they
were
reaching
for
a
reward
when
they
were
getting
good
marks.
You
know
A,
Plus
or
something
I
should
get
something.
You
know
a
candy
money,
something
no.
The
reward
is
into
the
good
Mark
you
you
got,
you
learn
something
and
you
had
a
plus
that's
a
real
world
and
it's
difficult
for
people
working
in
open
source,
because
the
reward
is
having
a
good
product,
a
product
that
people
love
people
product
that
people
use.
That's
the
main
reward
talking
about
yourself
bragging
about
your
skills.
B
A
Yeah
I
think
without
giving
anything
away.
One
of
the
responses
that
we've
received
for
the
project,
basically,
is
all
passion.
All
heart,
you
know
just
loves
helping
wants
to
be
part
of
it
just
loves
Jenkins
because
of
how
much
it's
helped
them
and
how
much
like
how
much
they've
invested
into
it.
So
it's
like
they're
very
aware
of
all
of
this.
A
A
You
know
sharing
that
giving
that,
in
effect
like
that
infectious,
like
joy
and
Spark
to
other
people,
maybe
like
that's
all
it
takes,
or
you
know,
I
feel
like
the
interviews
and
and
questionnaire
and
responses
are,
are
pretty
like
low
risk
in
in
terms
of
that
person
being
highlighted
and
stuff
yeah,
there
there's
going
to
be
some
Fanfare
Associated,
but
there
should
be
the
work
that
they're
doing
is
unreal
and
necessary
and
huge
and
like
just
pushes
us
forward,
gives
us
you
know,
gives
us
more
work
to
do
it's
it's
the
driving
force,
so
it's
it
needs
to
be
appreciated.
A
These
people
need
to
be
appreciated
and
highlighted,
but,
like
highlighted,
is
one
aspect
of
it,
but
the
appreciation
needs
to
happen
for
I
mean
I,
know,
I,
feel
better
and
we'll
continue
to
do
things
when
I
know
it's
appreciated
yeah
so,
but
yeah
the
Project's
coming
along,
really
well
we're
you
know
we're
getting
a
lot
of
good
stuff,
we're
in
a
good,
really
good
place
with
it.
It's
just
a
matter
of
getting
it
published
in
live
more
than
anything
else
and
yeah.
A
C
A
We
can
yeah,
it
will
be
out
regularly,
but
yeah
this
way
we
everyone
gets
a
time
their
time
to
kind
of
shine
in
the
spotlight
without
being
overwhelmed
and
yeah
I.
Think
it's
just
nice
to
give
that
personal
aspect
to
to
these
as
well.
For
me,
joining
an
open
source
Community
has
been
really
fun
and
great,
because
I
get
to
interact
with
plethora
of
people.
A
I've
I've
never
met
in
person
before
and
from
all
different
walks
of
life
and
I
might,
but
I
might
not
ever
get
to
connect
with
them
on
a
personal
basis.
This
is
this.
Is
a
really
nice
opportunity
to
get
that
connection.
Even
if
it's
not
direct
with
that
person,
you
can
still
it.
You
know
that
Comfort
level
is
increased
by
just
knowing
that
you
know
I
found
out.
One
of
our
top
contributors
is
super
into
music
and
is
actually
has
been
playing
trumpet
for
15
years.
A
Oh
I,
don't
think
I
would
have
even
asked
no
that
question.
So
it's
really.
It's
really
cool
to
get
insight
into
someone
like
this
and
yeah
I
I
have
high
hopes
that
it's
going
to
be
really
nice
recognition
project
and
that
the
contributors
will
feel
you
know
good
after
this
that's
I
mean
my
end
goal
is
making
sure
that
the
contributors
feel
appreciated.
So
that's
really
all.
A
Yeah,
exactly
that
Butler
is
the
the
face
of
Jenkins,
but
all
the
internal
body,
parts
and
stuff
like
that
they're
all
about
people
anyway,
nice,
one
yeah
we
won't
get
into
which
body
parts
or
who.
C
A
But
I'm,
not
the
brains,
that's
all
I'm,
saying
okay
anyway,
so
that
concludes
the
agenda
I
had
for
today,
thanks
for
sticking
around
for
the
extra
time,
I
appreciate
it
and
thank
you
for
the
discussion
today.
Thank
you
really
nice.
The
recording
will
be
up
in
24
to
48
hours
and
we'll
be
back
next
week
until
then
take
care
and
thank
you,
as
always,.