►
From YouTube: Jenkins Advocacy & Outreach SIG Meeting - May 5, 2022
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
Okay,
so
first
on
the
agenda,
so
gsoc
update,
we
are
done
we're
closed
for
the
reviewing
and
grading
period.
All
the
org
admins
met
and
we
are
working
on
the
ranking
at
the
moment.
We
think
we
have
most
for
the
most
part,
what
we
need
in
place
to
deliver
to
google
by
may
12th
right
now.
Mark
I'm
not
sure
if
you're
the
person
that
I
can
ask
about
this,
but
we
need
to
provide
payoneer
information
so
that
how
our
compensation
will
get
compensated
by
google
via
the
payoneer
system.
So
I.
C
C
So
they
are,
they
are
the
they
are
our
the
keeper
of
our
accounts
and
therefore
they
are
the
best
contact
to
tell
us
how
do
we
deposit
money
in
there?
That
may
also
be
the
seed
seed.
The
answer
to
that
may
be
the
seed
that
I
can
use
to
to
take
care
of
two
action
items.
I
have
related
to
jenkins
funding
in
the
governance
board,
so
there
are
two
places
where
I
need
something
similar
to
that.
So,
if
you
ask
the
question,
you
may
also
help
me
when
you
find
the
answer.
A
Okay,
all
right,
I
will
do
that.
I
know
that
they
are
at
an
off
site
this
week,
so
I
will
still
send
out
communication
to
them,
but
most
likely
they'll
get
back
to
us
next
week.
D
Yes,
yeah,
we
we
have,
we
have
already
our
draft
decision
filled
in
great
and
we
only
have
a
doubt
for
one
project
and
we're
still
reflecting
on
that
one
to
make
a
decision
yeah,
but
we're
we're
good
and
checking
that
the
procedure
is
well
understood
that
we
didn't
forget
something.
C
A
No
problem
she
code
africa,
so
mark
I
have
here.
I
don't
know
if
there's
any
update,
you
want
to
add
here.
C
Then
the
the
contributors
are
actively
involved,
they're
interested,
they're,
contributing
and
they're
and
they're
also
learning
in
the
process,
and
so
we
get
both
the
benefit
of
them,
learning
things
and
them
contributing
at
the
same
time,
and
that's
a
good
hybrid.
We
like
it
when
it's
not
just
us
teaching
and
we
like
it
when
it's
not
just
them
contributing
without
learning
something
in
the
process.
C
So
we've
got
this
hybrid
of
contribution
and
education
that
is
helping
them
grow
and
part
of
that
is
because
those
two
projects,
screenshot
update
and
inclusive
naming-
were
relatively
simpler
projects.
They
don't
have
enormous
technical
complexity.
They
do
have
a
lot
of
learning
that
was
required
in
order
to
update
a
screenshot.
You've
got
to
be
able
to
recreate
the
screen
and
recreating
the
screen
means
you've
got
to
know.
A
C
About
jenkins,
to
get
to
that
place
and
surprisingly
enough,
it's
not
in
many
cases
trivial
to
get
to
that
place.
So
it's
been
that's
been
the
education
part
for
them,
inclusive,
naming
the
same
kind
of
story.
There
are
places
where
you
can
make
changes
in
places
where
you
can't
and
they've
had
to
learn
where
it's,
where
it
makes
sense
to
make
changes
and
where
it
doesn't
and
that's
a
learning
piece
on
the
weak
side
on
the
oops
shame
side
week,
whatever
you
want
to
call
it.
C
The
pipeline
help
project
has
not
gone
as
smoothly,
and
part
of
that
is
because
we
didn't
do
as
much
preparation
work
this
year
as
we
did
last
year,
but
we
used
the
same
kind
of
project
ideas
we
had
last
year
and
that
was
too
technically
demanding
too
likely
to
fail
and
has
too
many
opportunities
for
problems
right.
It's
go
ahead.
John
mark.
D
I'm
I'm
very
interested
by
that
experience
so
well,
maybe
we
can
take
it
offline
because
I'd
like
to
record
the
the
learning
of
that.
So
one
lesson
learned
is
that
we
didn't
prepare
the
scope
or
the
tooling
or
a
precise
description
that
we
had
to
to
organize
that
on
the
fly.
D
So
do
I
understand
that
correctly.
C
Right,
yeah,
that's
that's
that's
one
of
many,
and
and
these
are
the
the
comments
we
had
a
retrospective
on
last
year's
project
and
many
of
the
challenges
we're
seeing
here
were
already
included
in
last
year's
retrospective.
So
we
will
do
a
retrospective
again.
It's
just.
We
didn't
heed
the
notes
from
our
eye.
It's
not
we.
This
is
not
the
king
global.
This
is
mark.
Waite
did
not
heed
the
notes
from
our
previous
retrospective,
where
we
said
hey
look.
C
This
is
technically
very
demanding
and
there
are
opportunities
for
failure
hiding
in
technically
demanding
projects
that
a
brand
new
contributor
shouldn't
be
made
to
submit
to
that
kind
of
a
risk
right.
We
we
owe
it
to
contributors
to
give
them
a
better
experience
and-
and
my
my
initial,
my
one
of
my
mistakes
was
thinking.
Oh,
it's
too
easy.
C
C
Effort
good
idea
well
and
I'll
put
a
I'll
put
a
hyperlink
to
the
retrospective
into
this
document.
That
way,
we've
got
a
copy
of
it
because,
because
last
year's
retrospective
is
there
and-
and
it
has
has
many
of
those
those
notes
in
it.
So
let
me
go
get
that
I'll.
Do
that,
while
the
meeting
continues
that
way,
I
can
paste
it
in
here
in
a
minute,
and
that's
all
that
I
had
on
she
code.
Africa
contributes
on.
A
Thank
you
cdcon,
so
that
is
slated
for
june
9th
for
the
contributor
summits,
that's
taking
place
on
site.
The
agenda
for
the
contributor
summit
is
currently
live.
It's
I
posted
it
on
discourse
and
then
I'm
asking
cdf
to
post
it
on
the
austin
meetup
page
as
well,
so
that
will
be
done
next
week
when
they
are
back
in
the
office.
A
I'm
ordering
some
swag
for
the
event
so
getting
some
jenkins
socks
and
stickers
sucks
yeah.
I
figured
it's
lightweight
for
me
to
carry.
D
A
A
Our
jenkins
contributor
summit
at
devops
world
is
scheduled
for
september
27th,
so
that
is
still
available
for
us.
So
we
just
need
to
get
our
plan,
so
we
still
have
some
time
but
planning
to
come
soon.
B
A
I
actually
that's
a
great
question
bruno.
I
have
not
checked
on
the
website,
but
I
know
that
the
website
it's
worked
by
a
different
team,
so
probably.
A
Hasn't
gotten
or
the
task
hasn't
gotten
on
their
plate:
good
jenkins,
online
meetup,
so
localizing
jenkins,
with
crowding
enterprise,
that's
slated
for
may
12,
and
that
is
already
on
the
jenkins
online
meetup
webpage
and
we
are
getting
I
yesterday.
As
of
yesterday.
I
think
we
had
about
28
rsvps.
C
Cool
and,
and
that
one
is,
I
would
expect
the
attendance
to
be
less
than
our
typicals,
because
most
online
meetups
are
targeted
at
showing
some
feature
to
general
jenkins
users.
This
one
is
much
more.
How
do
you
contribute
to
jenkins
and
and
that's
a
smaller
audience
than
the
then
the?
How
do
you
use
jenkins
right.
B
I
was
kind
of
surprised
because
I
wrote
it
on
linkedin,
facebook
and
twitter
and
on
twitter
I
got
two
people
from
russia,
or
maybe
you
know,
east
eastern
countries,
out
of
the
blue-
that
I
never
heard
of
something.
Oh
I'm
I
will
come.
I
would
be
delighted
to
be
able
to
participate
and
ameliorate
jenkins
for
the
translation.
So
maybe
that's
the
subject
that
interests
really
people
which
are
frustrated
with
the
current
state
of
the
translation
in
general.
C
So
so
yeah
or
missing
they've
got
big
gaps
in
in
not
being
up
to
date,
and
I
think
crowding
enterprise
is
a
great
step
for
us
to
find
ways
to
make
them
much.
Better.
Crowdin
enterprise,
coupled
with
continuous
delivery
of
plug-ins,
has
been
a
treat
because
last
week
there
must
have
been
five
or
ten
plug-in
changes
that
came
in
that
were
released
automatically
because
someone
merged
a
new
translation
and
guess
what
you
get
a
new
translation.
You
get
a
new
version
boom.
A
Great
so
mark
this
next
one
mark
to
propose
meetup
for
bicep
bisecting
with
basil.
C
Right
so
I've
just
got
the
action.
I'm
there
basil
and
I
have
agreed
that
as
a
developer
topic-
and
this
is
developer-
centered,
again,
not
user
centered,
but
as
a
developer
topic
highlighting
how
to
use
get
bisect
to
very
effectively
and
rapidly
identify
where
a
problem
was
crea
was
injected
into
jenkins.
D
C
Well,
see,
right
and-
and
I
think
that's
the
story
right
is-
that
is
really
many.
People
know
that
there
is
the
concept
of
bisect
and
that
it
exists,
but
we
don't
bring
it
out
of
our
toolbox,
often
enough
to
be
confident
with
it,
and
basel
has
used
it
very
confidently
and
has
has
enough
experience
with
optimizations
that
he
can
use
in
jenkins
specific
that
not
just
do
we
get
a
story
about
what
is
how
does
git
bisect
help
us,
but
how
do
you
apply?
C
C
D
C
I
I
just
need
to
negotiate.
I
don't
think
that
those
are
really
a
help
thing,
so
so
good
question
to
give
some
background
music,
so
yeah
I
fixed
it.
I
press
alt,
a
when
I
shouldn't
have
additional
meetups
to
propose
accelerating
jenkins
builds
with
gradle
enterprise.
C
D
C
C
D
C
They
they
could
be,
but
the
problem
is
what
what
these,
what
these
talks
are,
or
what
these
these
meetups
are,
is
to
introduce
the
concept
and
announce
the
experiments
we
want
to
run
with
jenkins
infrastructure.
So
we,
the
challenge,
is
when
I
talk
about
these
things.
I'm
talking
about
hypotheticals
because
we
haven't
run
the
experiments
yet
and
what
the
meetups
are
is
to
announce
to
the
community,
we're
going
to
do
these
experiments
and
then
we'll
share
the
results
as
we
learn
and
gradle
enterprise
has
been
willing
to
to
support
the
experiments
here
with
build.
C
Caching
and
kosuke
kawaguchi
has
expressed
his
interest
in
supporting
the
experiments
with
launchable
again
in
the
jenkins
project,
but
they
they
would
both
just
be
experiments
as
we
try
to
see
if
the
the
hoped
for
optimizations
provide
real
performance
improvements
in
our
use
case,
the
gradle
enterprise
one,
for
instance,
there
are
some
experts
in
jenkins,
who've,
said
they're,
not
sure
that
that
will
actually
provide
us
a
detectable
significant
benefit,
and
it
until
we
run
the
experiment,
we
just
don't
know.