►
From YouTube: 2023 05 25 - Jenkins GSoC 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
Foreign
is
on
a
good
evening
good
afternoon,
good
morning,
everybody
to
this
last
office
hour
of
the
Google
summer
of
code,
bonding
periods,
so
I
think
all
projects
are
represented
here,
so
we
can
go
immediately.
I
have
one
General,
no
I
have
two
general
comments,
but
I
will
make
them
at
the
end
of
the
round
table.
So,
as
usual,
the
round
table
will
be
going
project
per
project
to
listen
to
you
sharing
what
was
done
during
the
last
week.
A
What
was
achieved,
what
is
planned
in
the
coming
week
and
if
there
are
any
impediments
or
difficulties
or
things
that
prevent
you
from
moving
as
you
would
like
so
first
projects
on
my
list
is
a
plug-in
Health
score.
B
A
B
A
And
nice
work
well
done
Adrian.
Do
you
want
to
add
something.
C
No,
not
really
yeah.
Everything
was
done
on
when
I
asked
jacooti
last
week
to
to
the
blog
post
and
the
different
countries.
C
The
bio
was
already
online
so
that
that
was
easier,
I
guess
and
I
I
don't
have
any
worries
for
the
what
we
do
next,
because
we
have
a
lot
of
things
to
do
already
listed
in
the
in
the
repository
issues,
but
also
in
a
jagoti
proposal.
For
so
there's
plenty
of
things
to
do,
and
but
we
we
take
them
one
by
one.
So
great,
looking
forward
to
merge
the
first
put
a
request
on
the
forzagoti
I.
B
A
Well
done
so
that
goes
well.
I
had
a
more
General
remark
or
observation
that
I
can
hook
in
here.
Instead
of
waiting
for
everybody
to
share
I've,
seen
that
for
pull
requests
that
are
submitted
or
jenkins.io
the
the
mentors,
so
the
blog
post,
for
instance,
and
that
are
not
automatically
notified
by
the
system,
and
so
a
good
advice
is
when
you
do
on
jenkins.io
or
other
repository,
but
jenkins.io
make
sure
that
in
the
comment
you
explicitly
name
the
mentors,
you
would
like
them
to
review
your
PR.
A
So,
like
the
blog
post
update
to
the
project
description
and
these
kind
of
things,
so
it
went
a
little
bit
fast
and
and
Chris
or
myself.
We
got
involved
in
the
review,
although
it's
normally
the
task
of
the
mentors
to
steer
that.
So
don't
forget
to
mention
explicitly
the
your
mentors
on
it
in
your
project
in
your
repository
I,
assume
that
there,
the
notification
go
correctly,
but
here
I
wanted
jenkins.io
is
configured
in
a
special
special
way.
A
Okay,
good!
Thank
you
jacruti
and
Adrian,
or
the
good
progress
good
news,
and
for
your
for
your
report
on
that
leave
a
little
blank.
If
somebody
wants
to
jump
in
on
that
project,.
D
Yes,
just
wanna
say
she's
doing
really
great.
She
has
this
nice
ability
to
be
after
the
problem.
We
keep
her
giving
a
hint
after
hint
and
she
catches
that
and
then
finally
delivers
what
you
were
expecting
her
in
the
first
place.
So
that
is
very
nice
quality.
A
D
A
Herself,
okay,
thank
you
for
your
comment.
Very
good
building
jenkins.io
will
alternative
tools
so
vandit.
E
Hello
everyone
this
week,
I
didn't
do
much
because
I
have
I
had
my
exams,
I
have
them
till
27,
but
for
the
next
week
we'll
be
doing
a
lot
of
stuff.
We'll
we'll
set
up
I
have
already
seted
up
an
experiment,
an
experimental
repository
where
we
will
start
developing
Jenkins
docs.jenkins.io.
That
was
like
mentioned
somewhere
in
the
developer
groups
for
for
to
be
the
top
URL
and
everything
will
be
redirected
to
it
later
on
so
yeah
that
that
I
have
set
it
up.
That
and
we'll
start
working
on
that
and
everything.
A
Great
Rajiv
or
or
Chris.
F
Yeah
so
yeah
everything
is
going
well,
I
mean
last
meeting
we
discussed
about
your
ux
in
this,
and
also
we
replied
to
Gavin
and
basil
and
Gavin
I
mean
the
comments.
They
are
very
insightful
comments
on
that.
What
we're
building?
Also
we
discuss
about
some?
We
have
questions
like
SEO
and
is
how
SEO
is
going
to
affect
the
things
we
are
making.
The
Jenkins
Mark
has
good
V1
like
research
thing,
so
we
we
talked
with
on
Monday,
then
I
think
he's
doing
well.
I
mean
also.
We
had
like
I.
F
Think
Oneness
is
connected
with
I
think
this
this
code,
so
we
are
just
like
figuring
out
the
MLS,
how
we
can
have
plugins
and
all
that,
so
they
they
might
have
a
good
Insight.
Maybe
so
yeah
I
mean
everything
is
going
well
and
yeah
thanks
that.
A
G
G
So
I
think
I
mean
the
progress
is
good,
but
the
thing
is
that
I
we
we
still
have
to
finalize
our
project
plan
so
that
that's
something
we
could
work
on
over
the
next
like
weak.
So
even
though
I
think
it
has
like
ended
by
then
and
that's
about
it.
For
me,
good.
A
Good
point:
Chris
yeah
good
point
and
especially
seen
that
we
have
interest
of
some
high-profile
contributors
in
the
community.
It's
important
that
we
we're
very
clear
in
what
we're
going
to
do.
What
we're
not
going
to
do
great
any
other
comments
on
the
Jenkins
IO
project.
A
Good,
the
next
one
is
Docker
based
quick
start,
Jenkins,
quick,
start
examples.
Ashutosh
you
had
a
late
starts
because
of
exams.
H
Yes,
ketchup,
we
had
a
first
meeting
and
and
the
meeting
after
that
and
I
have
created
an
experimental
repo
for
the
project
and
the
project
page
is
updated.
The
blog
poster
is
still
in
PR.
Pr
is
open
right
now.
It
will
nearly
complete
March
tomorrow
by
tomorrow.
A
Right,
okay,
good
A
little
comment:
you
I
think
you
heard
my
my
advice
earlier
so
don't
forget
to
put
Bruno
and
other
yeah
yeah
and
Saeed
in
the
comment.
Otherwise
they
don't
know
that
the
pr
is
is
ready.
I
But
yes,
that
would
be
better
to
be
notified
via
GitHub,
so
that
I
get
even
notification
on
my
phone.
So
I
I
can't
miss
it
via
GitHub
right.
A
You
ashutosh,
are
you
blocked
for
the
polishing
of
your
blog
post?
Do
you
see
what
you
need
to
do,
how
you
can
do
it,
because
I
I,
honestly
I
replied
very
quickly
through
the
pr
and
said
hey
hold
on
I
want
and
I
didn't
help
you
so
do
you
know
how
to
move
on.
H
A
Okay,
try
to
read
the
text
with
the
eyes
of
somebody
who
doesn't
know
the
project
and
be
sure
that
the
subject
of
the
phrase
that
we
know
what
you're
talking
about,
so
this
is
going
to
be
done
on
what
because
it
can
be
and
the
circumstances
this
was
a
little
bit
needed
some
some
clarification
good.
So
this
is
going
on
moving,
don't
forget
to
Ping
your
mentors
on
that
ask
for
help
or
for
guidance.
If
you
don't
understand
comments,
I'm,
just
watching
Bruno
is
there
something
you
would
like
to
add.
I
No,
you
said
it
all.
Thanks
for
the
review
by
the
way,
John
Mark
I
would
have
said
more
or
less
the
same
thing,
but
you
were
quicker
than
I
was
so
thanks
for
your
help.
A
A
So
we're
good
and
we're
going
to
move
to
the
last
project
and
hear
what
harsh,
as
today,
yeah
there
is
Harsh
gitlab
plug-in
modernization.
So
tell
us
what
happened.
J
So
the
project
plan
is
completed.
We
are
moving
towards
the
first
Milestone
and
the
community.
Bonding
checklist
is
also
completed.
So
I
think
we
are
good
to
ready
to
start
yep
I'm
working
towards
my
first
milestone
and
which
is
what
I'm
just
migrating
the
rest
easy
to
gitlab
4J,
that's
the
first
thing,
then
I'll
migrate,
the
web
hook
thing
and
the
proxy
thing
it's
discussed
in
the
project
plan.
We
are
having
technical
discussions
on
the
guitar
Channel
and
yeah.
Things
are
going
great.
A
J
Not
yet
we
are
having
technical
discussions,
so
we
have
that
in
the
greater
Channel
most
of
the
times,
so
I
don't
think
so.
I
should
be
discussing
it
here.
A
Not
the
purpose
but
I
like
to
to
hear
hear
we
struggling
or
it
doesn't
work,
but
here,
like
others,
you're
with
the
teeth
in
the
subject
and
you're
you're
moving
ahead.
So
very
well
I
like
that.
So
as
the
general
summary
bonding
period
achieved
the
objectives,
people
know
each
other.
Things
are
now
settled:
how
to
communicate.
How
to
work.
A
Presentation
to
the
community
has
also
been
done,
some
little
details,
but
because
of
the
late
start
for
shutoff,
and
everybody
is
ready
to
start
next
week
with
the
actual
coding,
please
General
comments
or
reminders
so
we're
starting
now
you
have
your
project
plan.
The
next
important
Milestone
Global
Milestone,
is
that
mid
July,
so
that's
in
a
month
and
a
half
will
have
the
first
intermediate
checkpoint,
where
we'll
have
a
review
of
your
work
and
where
we
need
to
report
to
Google.
A
Yes,
the
contributor
is
working
as
expected
and
we
can
continue
to
fund
him.
Everything
is
going
fine,
so
this
is
the
purpose
of
that
evaluation.
The
second
thing
there
is
that
we're
going
to
ask
the
four
of
you
to
make
a
15-minute
presentation
of
your
project
and
what
you
achieved
in
these
first
six
weeks
elapsed
six
weeks,
so
it's
a
small
presentation,
think
about
that
on
time
will
give
more
details.
A
So
this
is
around
July
14th
second
thing
just
to
be
sure
that
we're
starting
on
on
on
the
correct
foot,
so
I'll
have
one-on-one
discussions
with
the
mentors
and
also
with
contributors
starting
in
June
contributors
are
going
to
to
propose
a
one-on-one
meeting
with
each
of
you
starting
the
second
week
of
June
third
week
of
June
and
we're
it's
just
for
me
to
confirm
the
feeling
that
you're
you're
good
you're
feeling.
Well,
it
works.
Well,
you
have
a
good
relationship.
A
The
two
two
important
things
I
wanted
to
share.
Are
there
questions
comments
or
can.
K
Can
I
just
add,
with
reference
to
the
the
Jenkins
online
Meetup
for
me
for
the
July
time
frame
the
midterm
presentation,
so
we
do
have
presentations
from
last
year
that
you
can
use
for
reference
or
inspiration
if
it
helps
you
in
any
way.
So
I
will
include
that
in
today's
meeting
notes
so
feel
free
to
reference
back
to
it.
It's
it's
also
on
our
YouTube
page
and
it's
also
on
our
Jenkins
online
Meetup
page,
but
I'll
reference
it
in
our
meeting
notes
today.