►
From YouTube: GSoC Office Hours - June 30, 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
So
good
good
evening,
good
afternoon,
good
morning,
everybody
in
early
morning
for
some
of
you,
so
this
is
the
gsoc
Global
office
hour.
It
is
June
30th
2022
and
we're
going
to
do
a
small
Roundup
of
the
project
and
where
we're
standing
so
first
thing
is
I
need
to
do
this
before
so.
First
thing,
I
had
a
very
interesting
personal
chat
with
all
four
contributors,
a
very
interesting,
very
pleasant,
so
I,
thank
everybody
for
the
time
it
was
very
interesting.
A
For
me.
Second
point
is:
I
did
not
see
updates
from
all
projects,
so
the
project
page
on
Jenkins,
IO,
I,
think
I've
seen
an
update
from
the
plugin
Health
score
for
the
meeting
in
the
the
note
page.
So
that's
okay.
There
have
been
quite
some
updates
on
a
yearmings
project.
So
just
a
reminder
check
if
your
project
page
is
up
to
date
that
everybody
can
find
all
necessary
indications.
A
If
you
have
issues
to
update
the
project
page,
just
ping
me
or
ask
your
Mentor,
but
sometimes
updating
jenkins.io
can
be
a
little
bit
tricky.
But
don't
forget
to
update
that
page
on
the
same
page,
I
also
sent
a
small
small
mail
to
the
various
mentors.
A
Asking
just
confirmation
that
all
the
goals
of
the
bonding
period
were
met
now,
I'm
convinced
that
they
were
met,
but
if
the
mentors
could
just
check
that
they
confirmed
that
everything
is
rolling,
but
don't
stay
awake
of
that
during
the
night
I
considered.
That
no
answer
is
a
positive
answer.
A
Okay,
so
these
are
the
introductory
notes,
I
plan
to
do
now
a
Roundup
of
the
different
projects
to
see
where
we're
standing
and
then
we'll
talk
about
the
midterm
evaluation.
Online
Meetup
presentation
have
some
some
discussions
around.
That
is
there
another
topic
that
should
be
added
to
the
agenda.
A
Okay,
let's
roll
so
project
Roundtable,
so
usual
questions.
What
were
the
important
activities?
Were
there
any
reached
mile
tone?
Milestones?
Are
there
impediments
or
things
that
are
preventing
you
or
worrying
you
in
the
process
of
your
your
development?
A
Who
wants
to
start
on
my
list?
I
have
so
do
you
want
to
start
the
rash.
C
C
Hi
everyone
so
about
updates
from
our
project.
So
this
week
we
were
able
to
do
quite
a
lot.
So,
for
example,
now
our
project
can
be
built
using
Dockers,
so
it
has
been
completely
dockerized
and
so
PR
for
that
has
been
merged.
And
the
second
big
thing
is
that
all
thanks
to
Adrian
he
worked
with
Jenkins
infra
team
trying
to
set
up
a
CI
for
our
project
and
that
has
also
been
resolved
and
merged
in
our
project.
C
C
A
C
A
C
Yes,
so
I
don't
think
it
deploys
it
it
just
spins
up
the
it
builds
the
application
and
then
runs
one
in
a
test
that
that's
written
written
there.
Okay,
that's
all,
and
that
test
is
just
checks
whether
we
are
able
to
reach
the
database
container
or
not.
That's
all
so.
Checks.
D
C
Able
to
communicate
with
each
other
so
that
has
been
written
by
Adrian,
so
big
thanks
to
him
and
other
than
that.
The
things
that
are
in
progress
right
now
are
is:
is
one
of
the
pr
it's
like
an
enhancement
PR
and
it's
I'm
aiming
to
work
on
it
and
get
get
it
merged
this
week
and
after
that
there
is
another
PR
in
line,
which
is
also
it's
a
bug.
Actually
it's
a
bug
reported
by
Adrian,
so
that
might
take
I
think
sometime
I.
C
It
might
be
completed
by
next
week's
first
half
and
after
that
is
where
the
fun
begins.
There's
a
very
big
issue
that
Adrian
asked
created
for
me,
and
that
requires
me
to
think
about
the
whole
designing
aspect
of
the
probes.
So
that's
going
to
be
the
fun
one
to
work
on
and
it's
going
to
take
the
major
part
of
July
for
me.
So
that's.
C
A
Good
and
then
big
issue
from
Adrian
will
be
away
for
a
couple
of
days
if
I
remember
well,
so
are
you
all
set
where
Jake
is
there
anyway,
but
in.
E
A
Go
on
go
on
the
on
the
health
channels
and
if
you're
really
stuck
you
can
can
come
to
me.
But
Jake
is
there
to
see
that
everything
goes
okay,
so
you're
set
moving
along.
B
No
I
think
the
garage
covered
it
well
we're
making
good
progress
and,
as
you
said,
the
the
real
fun
will
begin
when
we
start
working
on
the
the
actual
design
of
the
the
rules
engine
and
the
the
probes,
and
things
like
that.
So
really
looking
forward
to
getting
that
started
and
I
think
we're
in
a
good
spot.
As
far
as
deadlines
go
and
all
that
good
stuff.
So.
A
D
Yeah,
okay,
so
let
me
see
so
last
weekend
this
weekend
made
decision
on
which
check-inspile
wrong
actions
will
be
preserved
and
iterated
in
the
future.
So
they
are
checking's
container
action
in
the
jacking
static
image,
action
so
and
I
also
as
I
also
developed
some
optimizations,
such
as
dependencies
caching
and
pipeline
log
downloading
Service
in
these
two
actions.
D
So,
although
there
are
still
obstacles
in
this
project,
but
I
think
I
think
I
need
to
stop.
I
need
to
solve
them
quickly
so
later
in
this
weekend
next
week,
I
will
update
some
content
or
descriptions
in
the
jackings
io
project
page
and
the
repository
page.
So
I
think
the
progress
is
good,
though.
A
Okay,
good
I,
so
you
posted
some
questions
and
you
proposed
a
review
from
the
community
on
jenkins.io.
You
had
the
first
answer.
That
was
not
really
an
answer.
I've
seen
it
was
a
second
one,
but
I
didn't
read
it.
Did
you
have
feedback
from
the
community
on
what
you
did
up
to
now.
D
I
didn't
receive
the
emails,
but
in
the
this
course
I
received
two
feedbacks:
yeah
I
really
I,
read
them
carefully.
Okay,.
A
Good
then
you're
probably
going
to
integrate
them
in
so
you're
good.
A
Good
okay
sounds
good.
Thank
you
for
the
updates
yaming
and
next
one
in
my
list
is
automatic.
Git
cash
maintenance.
A
Oh
I
see
a
message
from
the
rash:
do
you
want
to
interrupt
before
we
go
to.
A
C
So
I
forgot
to
mention
one
more
thing
that
this
week
we
shared
our
community
survey
with
the
whole
community
on
Jenkins
Dev
mailing
list,
so
purpose
of
the
survey
purpose
of
the
service
to
get
their
feedback
and
try
to
find
out
weights
of
the
probes
based
on
those
feedbacks.
So
we
have
finally
shared
with
the
community
and
big
thanks
to
Jake
for
working
on
the
whole
survey.
It's
really
beautiful.
So
if
you
received
it,
please
feel
it.
That's
all.
Did
you
already
publish
it?
B
A
So
that's
that's
good.
Okay,
I
need
to
to
look
at
it
so
and
I
also
want
to
give
a
feedback
on
yemmings
thing,
but
several
things
piling
up
here,
but
okay,
good
good,
update,
I
added
that
to
the
note,
if
the
notes
are
not
correct,
you
can
update
okay.
Thank
you.
Thank
you
very
much
for
the
updates.
So
let's
get
back
to
automatic,
git
cash
maintenance.
So
this
hurricane.
F
This
week
I
worked
on
integrating.
You
know
the
git
maintenance
on
Jenkins,
so
now
forget
versions
greater
than
or
equal
to
2.30.
You
can
run
all
the
maintenance
tasks
on
the
caches
present
on
the
Jenkins
controller,
that
is
prefetch
GC
incremental
repack
use
objects
and
commit
graphs.
These
all
have
been
added
I've,
even
added
log,
like
you
know,
I've
even
added
logging
into
the
software
so
Whenever.
F
There
are
problems
that
whenever
administrators
face
any
problems,
they
can
go
through
the
logs
next
week,
I'll
be
adding
the
get
maintenance
for
get
versions
less
than
2.30.
So
far,
so.
A
A
A
So
last
one
is
a
pipeline
step
documentation.
So
this
vihan,
hey
everyone.
E
So
last
week,
two
of
my
pull
requests
were
merged,
one
for
the
jenkins.io
sidebar
and
another
one
for
separate
separating
a
declarative,
Steps
From,
the
main
class
pipelines
that
docs,
so
those
who
are
merged
and
then
I
created
one
more
pull
request
to
get
a
data
type
thing
going
for
the
parameters
of
the
pipeline
steps.
So
with
that
now,
you'll
be
able
to
see
that
the
types
of
the
parameters
are
not
present
under
the
help
content,
but
they
are
present
right
next
to
The
Heading
itself.
E
So
I
noticed
that,
on
a
larger
page,
the
size
got
reduced
by
a
sixth
which
is
quite
helpful,
so
that
is
not
yet
merged.
We
are
still
working
on
refining
the
logic
flow.
So,
but
the
entire
thing
is
working
then,
and
the
next
thing
that
we
have
started
is
separating
the
plugin
manager
from
the
pipeline
step,
documentation
and
all
that
code
is
now
being
maintained
inside
the
pipeline
metadata
utils
Repository.
E
So
our
plan
with
that
is
to
maintain
the
entire
plugin
manager
with
that
and
we
will
publish
it
as
an
artifact
to
Maven
which
can
be
imported
in
any
of
the
Jenkins
projects.
Whichever
require
that
as
a
dependency
and
then
we
can
use
it,
so
the
same
will
be
done
for
the
pipeline
step
docs,
and
so
the
big
thing
for
here
in
this
process
will
be
releasing
it
as
an
artifact.
E
E
A
That
the
yeah
or
or
edits
in
the
in
the
notes-
oh
sure
I'll,
do
that
so
I'll
share
the
repository
in
which
we
are
maintaining
it
yeah,
and,
and
is
that
the
one
where
you
have
discussions
where
the
mechanism
is
not
working
smoothly
or
there's
some
issues,
I've
seen
some
questions
from
Christine
about
that?
Are
you
stuck
with
that
or
are
you
moving.
E
I
think
that
is
with
the
one
on
the
plugin
list,
the
Jenkins
attire
on
which
we
had
discussion
with
Tim
and
Mark.
So
we
are
actually
holding
that
pull
request
for
now,
because
we
think
that
the
benefit
compared
to
the
amount
of
content
that
is
increasing
on
that
page
is
not
really
a
well
balanced.
So
I
think
I'll
move
over
that,
because
it's
not
a
good
to
spend
more
time
on
it
and
we
will
basically
land
back
on
it
whenever
we
think
that
yeah,
the
other
things
are
sorted
out.
E
So,
okay,
right
now
and
The
Meta
titles
is
actually
it
was
created,
I
think
five
years
ago.
So
all
the
code
is
outdated
and
I
have
created
the
pull
request
today,
as
a
draft
call
request,
I'll
just
share
the
repository
link
and
once
the
artifact
gets
going,
I'll
share
that
too
for
the
feedback
and
like
so
maybe
because
I'm
not
quite
sure
how
releasing
it
under
the
or
dot
Jenkins
CI
group.
It
works.
Okay,
because
I
don't
have
the
credentials
for
that
and
as
a
risk
question.
E
A
I'll
review
exactly
where
we're
standing
with
that,
because
Christine
pinked
me
about
that
I
have
a
meeting
with
her
on
Monday
a
general
one-to-one
meeting
with
with
her
just
to
listen,
and
she
raised
that
point.
I
will
read
the
conversations
in
details
on
on
guitar
and
see
if
I
can
do
something
to
help
or
at
least
get
the
right
persons
involved.
There.
I'll
also
have
a
chat
with
Mark.
Where
are
we
standing
sure
that
would
be
helpful?
A
Okay,
just
give
me
the
name
of
the
the
of
the
artifact
you're
you're,
creating.
A
A
Is
good
I'll
I'll
update
it
I'm,
not
good
at
taking
notes,
while
talking
I
apologize
for.
E
A
Okay,
no
problem,
so
that's
good,
but
there
we
need
to
keep
an
eye
that
this
new
dependency
can
be
can
be
released
correctly.
Yes,
that
is
the
main
goal
for
next
week.
A
Yeah
I
don't
know
I
change
I'll
do
that
after
the
meeting
is
there
something
to
add
about
the
projects.
A
There's
several
people
are
working
on
the
document
so
anyway,
just
resending
the
question
anything
to
add
about
the
projects.
A
I
like
that,
so
normally
the
next
Milestone
is
that
we
have
to
supply
with
Google,
who
is
sponsoring
a
Google
summer
of
code
for
end
of
July,
the
29th,
an
evaluation
of
where
we're
standing,
and
they
want
to
have
a
formal
reply
for
that.
Now,
if
you
go
on
the
document,
so
I
supplied
a
link
to
the
document
that
will
be
used
for
this
evaluation.
A
Now,
as
I
said
individually,
these
are
general
questions.
It's
not
an
exam.
It's
not
something.
Horrible
is
just
to
check
that
the
the
contact
is
established
that
you're
doing
work
and
that's
Google
can
continue
to
provide
you
with
a
stipend
for
your
work
during
the
the
summer.
A
You
can
have
a
closer
look
on
the
document,
so
no
worries
about
that
milestone,
but
I'd
like
to
have
during
the
the
summer
about
that
period
as
we
discussed
a
presentation
for
the
community
and
it
will
be
in
the
form
of
an
online
Meetup
of
what
is
the
purpose
and
what
you
plan
to
do
with
your
project.
A
Where
are
we
standing
in
the
project?
So
are
we
at
the
beginning?
Are
we
nearly
done
and
eventually
a
preliminary
demo
of?
If
you
have
something
to
show
already
now,
this
presentation
would
be
15
minutes,
no
more.
A
Your
mentors
can
help
I,
don't
want
that
you
waste
too
much
time
in
preparing
it
so
well,
it
doesn't
work
for
for
this,
but
generally
I
count
for
the
preparation
of
such
presentation
about
three
times
to
four
times
the
time
of
the
presentation.
So
a
quarter
of
an
hour
put
aside
at
least
two
hours
in
this
case
because
the
shorter
it
is
the
more
work
it
is.
The
you
can
count
on
my
experience
on
that.
A
So
you
need
to
be
able
to
put
about
two
hours
aside
and
if
you
want
to
train
yourself
to
do
a
dry
run
of
it,
do
it
with
your
Mentor
during
one
of
your
weekly
meetings
or
I'm
also
available
to
help
you,
if
you
feel
uncomfortable
for
that,
but
here
we're
talking
together
here
in
this
meeting.
It
works
quite
well.
Do
it
the
same
way,
just
a
little
bit
more
organized
a
couple
of
slides
so
that
you
know
where,
where
you're
going
so
don't
be
too
worried.
A
My
initial
proposal,
knowing
that
in
India
school,
doesn't
start
the
first
of
September
and
I.
Think
if
I
remember
well
hurry
cash,
no
I,
think
it's
beyond.
E
Yes,
I
think
we
discussed
about
it.
Yeah.
A
Vyam
is
is
a
little
bit,
so
he
needs
to
start
a
school,
so
my
proposition
was
to
hold
this
presentation,
the
21st
of
July,
so
to
do
it
on
Thursday.
A
So
first
question
is
that
okay,
for
you
is
it?
Is
it
not
too
early,
or
does
somebody
have
an
alternate
alternate
date
to
propose
so
who
has
opinions
on
that.
E
F
E
F
A
I
remember
that
no
was
not
sure
that
I
wrote
it
down,
so
you
would
not
be
available
in
cash.
F
F
No
I
prefer
it
in
July
only
at
fine
on
21st
I'm,
not
sure,
but
even
if
it's
on
the
21st,
it
should
be
somewhere
in
the
evening,
because
if
I
go
to
the
Quality
morning,
I
can
attend
in
the
evening.
So
okay.
A
Now
we
can
eventually
do
the
following:
is
that
I
find
it
much
more
difficult
to
do
it?
That
way
is
that
you
provide
me
with
a
recording
that
I
could
play
because
you're
not
available
at
that
moment.
I
could
play
it,
and
but
somebody
should
be
there
to
answer
questions
from
from
people.
So.
F
A
Good,
so
we
have
vihan
that
voted.
We
have
holy
cash
durash.
Would
a
21st
work
for
you
time,
wise
and
content-wise
I
believe
so
content-wise.
C
I
think
it
will
work,
but
just
to
confirm,
since
it's
on
Thursday
and
on
next
Thursday
from
that
date
would
be
28th
July.
So
that's
not
feasible
right
because
we
are
college
is
starting.
That's
the
reason
right.
D
Oh,
oh
I,
I,
don't
have
any
preference,
so
you
can
you
can
you
can
make
it
priorities
for
others,
because
my
my
the
first
day
of
my
next
semester
will
be
at
the
end
of
the
August
August
Okay.
So.
A
We
keep
okay,
bye-bye
Jake
is:
are
there
questions
about
the
content
because
it
will
be
a
month
that
you
will
be
working
and
coding?
Do
you
have
worries
about
the
content.
A
Fifth
I
plan
15
minutes.
Oh.
A
Okay,
but
so
in
one
hour,
so
so
make
it
between
10
and
15
minutes,
and
so
in
one
hour
we'll
have
the
four
projects
presented
so
that
they
and
and
give
them
the
the
chance
to
the
community,
to
ask
questions
and
and
so
10
to
15
minutes.
But
okay,
yes,
perfect
and
the
the
the
three
points
that
you
should
answer
there
in
the
meeting
notes.
A
So
what
is
the
purpose
and
the
plan
of
the
project?
So
it's
very
important
that
you
rephrase
exactly
what
is
the
the
purpose
of
your
project?
What
what?
What
is
it
about
people?
Don't
always
read
all
the
the
online
documentation?
So
it's
always
better
to
explain
them
verbally
so
where
you
are
in
a
project,
so
you're
halfway
or
you're
still
solving
problems
or
so,
and
it's
always
good.
If
you
have
already
some
prototypes
or
if
you
have
something
to
show
by.
D
A
Okay,
you
have
doubts,
you
have
you
don't
know
exactly
where
how
or
are
you
giving
too
many
details
discuss
that
with
your
mentor
and
or
ping
me
directly
and-
and
we
can
have
a
little
chat
about
that
so
Alyssa
we're
going
to.
B
A
The
the
Meetup
for
the
21st
yeah.
A
Foreign,
so,
let's
conclude
then
I
see
your
in
the
middle
of
it.
You're
making
progress,
I
I
start
to
see
interesting
results
coming
out.
So
well
done.
Continue.
That
way
and
talk
to
you
then
next
week.