►
From YouTube: 2023 05 05 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
A
A
B
C
A
A
Okay,
the
first
thing
I
stole
this
slide
from
Melissa
because
I
like
it
very
much
some
Journal
information
about
questions
and
answers
and
a
quick
reminder
to
the
code
of
conduct.
This
is
the
link
we
have
and
I
love
this
picture
so
we're
here
to
congratulate
the
contributors
that
were
selected
for
a
Google
summer
of
code
2023
and
to
discuss
how
we
move
ahead,
so
the
people
that
were
and
the
projects
that
were
selected.
A
A
A
A
A
We
are
now
starting
with
those
four
persons
and
the
mentor
teams
we're
now
starting
the
bonding
period.
That
means
that
we're
going
to
plan
what
we're
going
to
do,
how
we're
going
to
do
it
and
yesterday
evening,
after
the
announcement,
already
sent
some
ideas,
guidelines
or
recommendations
on
how
to
move
on
with
the
bonding
period
we're
going
to
let
you
breathe
a
little
bit
because
there's
a
lot
of
excitement
for
that.
A
A
A
We
were
lucky
I
want
to
remind
everybody
that
our
ranking
Choice
was
based.
First
of
all,
proposals,
quality
and
I
must
say.
Besides
some
junk
proposals,
people
never
attended.
They've
tried
and
I
want
to
emphasize
here
that
all
the
projects
that
were
or
the
proposals
that
were
in
the
short
list
hat
drafts
published
in
reviewed.
A
A
As
said
we
were
short
in
mentors
and
some
mentors
had
to
hook
off
and-
and
this
is
something
I'm
a
little
bit
sad
on,
but
it
played
an
important
role
on
our
capacity
and
then
we
also
put
into
the
equation
before
shaking
everything
very
very
strongly
and
make
a
decision.
The
importance
of
the
project
for
the
Jenkins
project.
A
Important
message
is
it's
not
a
judgment
on
your
capacity
or
skills,
so
this
is
important.
There
are
many
many
parameters.
The
plate
there,
so
I
want
to
acknowledge.
Disappointment
is
not
easy.
The
people
that
already
went
through
that
process
know
what
I'm
and
the
people
that
are
currently
that
were
not
selected
know
what
I'm
talking
about
I
have
a
few
recommendation.
A
A
few
things
I
want
would
like
to
share
first
look
forward,
Don't
Look
Behind
or
have
regrets
the
only
thing
where
you
or
the
only
reason
you
would
look
behind,
is
to
be
proud
of
all
the
work
that
was
accomplished.
The
things
you
learned
during
these
long
weeks
and
months
of
preparation,
so
look
forward,
continue
to
learn
and
the
tip
is
build
your
open
source
or
your
Jenkins
muscle
in
the
same
Spirit.
As
the
discussion
we
had
in
December,
they
prepare
learn,
get
to
know.
A
People
I
am
available
for
whoever
wants
to
have
a
discussion
with
me
on
the
experience
I'm
interested
to
know
how
you
feel
and
and
how
you
perceived
what
happens
so
I'm
I'm
I'm,
ready
to
make
my
time
available
for
that
I'm
ready.
Also
to
describe
to
discuss
with
you
individually,
so
we
can
speak
more
freely
how
to
move
forward.
So
I
will
not
discuss
any
details
on
the
ranking
decision
and
how
we
made
soldiers,
don't
try
it.
A
A
In
particular,
so
several
people
had
very
interesting
through
the
projects
in
The.
Proposal
on
these
projects
were
very
good.
Very
strong
had
very
good
ideas
in
them.
A
lot
of
prototypes
and
ideas
were
in
these
documents
and
I
know:
there's
a
lot
of
work
in
sweat
in
it.
Submit
them
just
create
a
PR
and
have
have
the
people
have
the
community
discuss
them
improve
them.
The
best
example
I
can
give
for
that
now.
A
Forgive
me,
I
am
I,
forget
the
names
so
I
apologize
for
that,
but
one
of
the
projects
we
had
that
we
had
to
stop
before
was
about
the
user
interface
for
plug-in,
Health
probes,
the
user
interface.
The
project
was
dropped
and
one
of
the
would
be
contributors
for
that
project
where
he
just
submitted
the
pr
of
start
of
his
work.
This
PR
was
merged
and
was
a
huge
Improvement
and
also
a
first
step
in
that
direction,
and
it
it
had
a
lot
of
positive
influence.
A
A
If
you
want
to
do
that,
just
remember
that
you
will
be
using
the
resources
of
Plug-In
maintainers
or
the
community.
It's
less
focused
as
the
mentorship
for
Google
summer
of
code,
so
you
will
have
to
find
Solution
by
yourself
and
it
will
be
more
slow
and
also
more
effort
intensive,
but
this
can
spread
on
on
weeks
months,
so
no
problems,
so
it
is
the
first
advice.
A
A
This
is
where
you
will
learn.
I
know.
Oh,
this
is
important.
Okay,
I
can
participate
to
the
effort,
so
this
is
why
I'm
pointing
to
that-
and
also
you
will
know
who
are
the
the
people
in
the
community
and
they
will
also
start
to
learn
Who
You
Are.
So
this
is
also
very
useful
stuff
for
you
personally,
but
also
for
preparing
the
the
next
gsoc
run.
A
Stay
engaged
in
active
one
tip
so
web
submit
PRS
and
things
like
that.
But
if
you
still
want
to
learn
something
that
I
I
find
very
useful,
is
any
your
subjects
in
in
the
matter
you're
interested
in
look
at
the
PRS
that
are
submitted
by
more
experienced
people,
so
try
to
understand
it,
contribute
to
the
review
and
suggest
Improvement
or
ask
clarifications
I.
Don't
understand
why
this
particular
test
is
included.
A
A
A
Especially
as
for
instance,
maintainers
or
other
people
are
very
busy,
people
are
generally
very
focused
on
some
of
the
issues
be
respectful
of
their
time
and
do
your
homework.
Do
your
homework
in
having
looked
on
your
own
for
the
solution,
or
why
am
I?
Why
am
I
stuck
in
trying
to
describe
your
problem?
A
What
you
tried
to
do
as
precisely
as
possible
and
be
patient
here
for
g-soc
Preparation?
We
had
a
lot
of
people
involved.
Yeah
I
want
to
give
a
a
shout
out
to
Chris
turn,
who
was
particularly
present
in
the
presentation
and
so
I
hope.
The
noise
of
the
rain
doesn't
get
through
the
micro,
the
microphone
so
be
patient
for
that.
A
D
C
D
E
F
E
A
F
A
You
a
lot
of
things
can
be
done
offline,
so
I
think
for
the
people
that
were
selected,
it's
quite
overwhelming,
because
now
you
you
realize
now
it's
a
real
thing
in
in
especially
with
a
male
with
all
the
the
thing
I
sent
yesterday.
So
don't
don't
get
scared
by
that
and
ask
for
guidance
to
your
mentors.
D
And
I
think
one
thing
I
learned
from
our
last
year's
g
sock
is
over.
Communication
is
much
welcome,
so
even
if
you
can't
attend
meetings,
keep
the
communication
Line
open
with
status,
updates
questions
via
emails.
Like
you
know,
Jean
Mark
mentioned
earlier
that
there's
other
ways
of
communications,
but
over
communication
is
very
helpful
and
it's
key
yeah.
A
B
B
A
A
A
A
That
follows
a
certain
format.
Where
are
you
going
to
give
who
you
are?
What
is
your
background
and
and
show
you
look
what
the
the
others
did
a
little
picture
or
an
avatar,
and
this
this
can
already
be
be
done.
So
the
null
gsoc
contributor
file
I'm,
seeing
the
chat
here-
is
not
the
file
to
update
it's
a
file
to
duplicate
so
create
one
with
your
own
name,
and
you
submit
a
pull
request
on
it
and
if
the
syntax
is
not
correct,
you
will
be
helped.
A
A
So
this
you
can
already
do
and
we'll
take
some
some
time.
One
of
the
expectation
is
for
the
end
of
the
bonding
period.
Is
that
you're
able
to
do
a
blog
post
on
Jenkins
IO,
where
you
will
describe
who
you
are,
what
the
project
is
about
and
what
you're
going
to
do
so
you're
going
to
address
to
the
community
to
explain
what
you're
going
to
do
and
because
now
people
that
didn't
participate
to
Google
summer
of
code
are
eager
to
know
what?
What?
What
is
this?
A
A
Okay,
so
don't
hesitate
to
ask
the
questions
on
the
g-sox
Sig
Channel
or
on
a
community.jenkins.io
working
asynchronous
is
a
perfect
way
of
doing
I.
Have
a
general
detail
that
I
didn't
raise
in
in
my
presentation.
Discussion
at
the
beginning
was
that
we
will
continue
to
hold
at
this
time
an
open
Office
hour.
It
will
be
dedicated
to
the
the
gso
contributors,
the
mentors
it's
a
moment
where
we'll
sit
together
and
see
where
we're
standing.
A
We
can
move
it
if
you
can't
make
it
once
in
a
while
exams
work
or
whatever
the
the
hey
we're
not
at
school.
Here
we're
we're
here
with
with
adults
working
together,
there's
a
community
so
we'll
we'll
move
forward.
Last
year,
these
office
hours
for
gsoc
participants
were
felt
as
being
very
helpful
and.
B
A
So
if
people
would
like,
like
sarthak
I've
seen,
mukul
is
also
around:
don't
hesitate
to
reach
out
directly
to
me
and
and
I'm
ready
to
discuss
a
few
things
where
I
will
not
get
in,
don't
try
to
so
no
complaining
whining.
Why
I
wasn't
picked
up
it's
unfair
and
these
I
will
not
go
into
these
discussions.
So
you
know
we're
here
to
think
and
build
for
the
future
so
that
you
can
make
it
in
the
future.