►
From YouTube: GSoC 2023 Office Hours - March 23, 2023
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
C
Right,
thank
you.
Welcome
everyone.
This
is
the
Google
summer
of
Code
office
hours.
You
should
see
a
copy
of
the
notes
on
my
screen
Alyssa.
Can
you
confirm
that?
Okay,
great
all
right,
so
thanks
everyone
for
being
here?
What
questions
or
topics
do
you
want
to
bring?
Let
me
offer
a
few
to
start
with
it's.
What
about
the
projects
that
have
been
with
the
ideas
that
have
been
withdrawn
right
because
there's
probably
some
question
why
they
withdrawn
Etc?
C
Okay,
what
other
questions
do
you
have
and
you
should
feel
free
to
unmute
yourself
and
state
your
question
or
you
can
type
your
question
in
chat.
C
Okay,
well
so
then,
since
I
didn't
hear
any
I
haven't
heard
or
seen
any
hints
of
of
questions,
I'm
an
attempt
to
answer
the
what
about
the
ideas
that
have
been
withdrawn
from
the
project?
So,
let's
go
to
community.jenkins.io,
look
at
the
at
the
message
from
John
Mark
and
that
way
we
get
get
a
hint
as
we
can
read
through
it
and
be
sure.
Oh,
let's
see
gsoc
right.
C
B
C
B
Okay,
see
Chris
and
harsh
has
put
in
the
link
in
the
chat
window
for.
C
Us,
oh
perfect.
Thank
you.
Thank
you
very
much
perfect.
Thank
you
good.
All
right,
that's
it!
Okay!
So
three
project
ideas
have
been
withdrawn.
We
wanted
to
do
this
now
so
that
you
still
had
time
if
you
were
submitting
to
one
of
these
project
ideas
to
submit
a
different,
a
different
proposal
due
date
for
the
the
closing
date
for
the
submissions
from
you
as
potential
contributors
is
April
4..
So
we've
got
about
two
weeks
still
before
that,
so
you
can
revise
now,
question
might
be
hey.
Why
were
they
withdrawn?
Well
in
each
case?
C
It's
because
we
don't
have
a
lead
Mentor
that
we
feel
could
run
that
project
the
way
we
want
the
project
to
be
run.
So
the
exponential
back
off
and
Jitter
for
agent
reconnections
basel's
had
to
step
back.
I'm,
basel's
manager
and
I've
made
a
choice
to
have
him
step
back
from
this
and
and
work
Works
work
something
other
than
Google
summer
of
code,
displaying
of
plug-in
Health
scores.
We
didn't
have
a
lead
Mentor
even
proposed
initially,
and
we
need
a
lead
Mentor
for
you
as
a
contributor
to
be
successful.
C
Likewise,
for
the
Jenkins
configuration
as
code
drift
detector,
we
need
a
lead
Mentor
there
and
the
idea
had
been
proposed
by
John
Mark,
but
we
feel
like
it
would
not
be
healthy
for
the
project
for
him
as
the
lead
org
admin
to
also
be
a
lead
Mentor.
It's
just
that's
just
too
much
for
one
person
to
do
with
all
the
work
that
he
has
to
do
as
the
org
admin
as
the
lead
org
admin.
Any
questions
on
those
on
those
three
withdrawals.
C
What
about
other
project
ideas
and
how
are
they
going
so
we've
got
over
20
proposals
that
we're
tracking
in
our
tracking
sheet
and
special
thanks
to
Chris
Stern
Chris,
if
I
recall
correctly,
I
think
I've
seen
that
you've
reviewed
every
one
of
them
or
almost
all
of
them,
and
others
of
us
are
reviewing
them.
In
addition,
so
I've
reviewed
three
or
four
and
we've
got
other
reviewers
as
well.
A
C
C
C
C
C
C
C
So
this
is,
this
is
really
a
great
outcome
right.
What
we
see
is
26
proposals
that
are
getting
reviews
and
reviews
from
a
number
of
different
reviewers
thanks
to
John
Mark,
a
special
thanks
to
Chris
Stern,
you
see,
dhiraj
has
reviewed
several
I've
reviewed
several,
so
we've
got
more
to
review
and
hope
to
continue
that
review
process
through
at
least
the
end
of
this
week
now
did
did
any
of
the
potential
contributors
have
concerns
of
a
general
nature
that
we
should
flag
here
or
we'll.
C
Well,
and
if,
if
at
any
time
you
want
to
take
over
John
Mark,
you
are
welcome
to
do
so.
So
what
we
were
just
looking
at
here
was
look
getting
a
review
of
those
things
which
we
still
need
to
be
those
those
project,
ideas
or
project
plans,
proposals
that
we
still
need
to
review
and
giving
note
that
Chris
has
reviewed
almost
all
of
them.
I've
reviewed
several
you've
reviewed
many
and
we'll
continue
those
reviews,
I
think
through
end
of
this
week.
D
Right,
I,
I'm,
sorry
to
jump
in
like
that,
so
I
I
want
to
remind
to
mentors,
but
also
other
people
that
are
part
of
the
community
and
that
knowledgeable.
It's
an
important
mentoring
step
here
to
read
the
proposals.
A
lot
of
work
has
been
done
in
them
and
read
as
many
documents
as
possible
and
review
them.
It's
it's
a
very
important
step
in
the
learning.
C
This
is
open.
Source,
open
source
means
open
in
the
sense
that
you
get
to
see
and
think
about
other
people's
ideas.
There
is
no
shame
in
saying
I
want
to
see
what
they
said
about.
This
should
I
incorporate
that
idea
into
mine
all
right
in
the
University
environment.
That
would
get
you
in
serious
trouble
right.
That's
that's!
Oh
you're,
you're
cheating,
but
in
the
open
source,
World
ideas
build
on
each
other,
so
don't
be
shy
at
reading
each
other's
and
commenting
on
them.
Hey.
What
do
you
mean
by
this?
What's
what
about
this?
D
And
I
I
need
to
to
say
that
I've
seen
several
good
reviews
from
peers
so
from
from
people
that
are
also
submitting
proposals
so
I.
It
was
really
great
to
see
that,
but
we
need
more
Mentor
or
senior
people
reading
the
documents.
So
too
many
documents
are
untouched.
Yet.
C
D
I'm
going
to
move
them,
move
them
out,
so
this
is
part
of
the
once
I
I'm
being
able
to
catch
up
some
some
some
air,
because
I've
been
running
like
hell.
But
yes,
you
know
sorry
for
that.
C
C
Road
well
well
done
very
good.
Driving
in
Belgium
worked
okay
today,
I
like
that,
so
we
had
started
John
Mark
with
what
about
the
ideas
that
have
been
withdrawn
from
the
project,
and
so
we
linked
to
that.
We
looked
at
the
page
and
discussed
it.
I
gave
my
overview
of
the
three.
Then
Chris
has
given
some
additional
guidance
on
project
plans.
Are
there
other
things
you
wanted
to
guide
people
on
or
other
things
you
wanted
to
say.
D
No
I'm
I'm
more
so
I
have
a
general
message
here
to
say,
probably
a
repeat
of
what
has
been
done
today.
D
D
I
know
it's
short:
it's
you
need
to
find
a
balance
between
leaving
enough
time
or
mentors
additional
mentors
to
join,
because
this,
basically
the
problem
we
had,
we
were
lacking
mentors
and
to
give
enough
time
for
them
to
to
rejoin
and
that
we
built
correct
teams,
but
on
the
on
the
other
side,
enough
advance
notice
for
people
to
get
reorganized
or
not
get
the
door
slammed
on
their
on
their
notes.
So
it's
not
an
easy
decision
to
take
the
the
reasoning
behind
the
decision.
D
Was
that
we're
very
respectful
to
the
time
and
effort
that
contributors
have
already
been
done,
but,
okay,
there.
There
is
this,
but
especially
when
you
participate
to
it.
We
want
to
give
the
best
chance
of
success
for
that
and
not
have
to
say
and
to
withdraw
a
project
in
the
middle,
because
here
we
have
nobody
left
to
have
a
proper
support
for
the
contributors.
D
So,
okay,
this
part
of
being
responsible
and
being
a
manager
I
Stand,
For
That.
So
the
other
thing
is:
if
somebody
wants
to
discuss
it
and
better
understand
and
wants
to
have
a
one-to-one
chat
with
me
and
have
a
virtual
coffee
or
a
group
I'm
open
to
that
to
them
so
I
want
to
have
it
face
to
face,
because
so
I
I
can
give
all
the
new
ones
in
there
because
I
know
it's
not
a
fun
experience,
so
I'm
happy
to
have
that
discussion.
D
Explain
how
why
and
especially
how
you
can
build
on
that
experience
in
G-Shock
next
gsoc
in
open
source
and
also
in
your
career,
so
I'm
ready
to
discuss
it
and
share
my
experience
and
help
you
to
see
clear
in
in
that.
So
it's
an
open
proposition
to
anybody.
Just
send
me
a
mail
and
and
I
can
organize.
This
is
important
to
me.
So
all
the
people
that
spends
time
investment
are
important
to
me,
but
also
to
the
Oregon
admin
team
and
also
to
the
Jenkins
community.
D
B
There
is
one
question
from
mukol:
sorry
if
I
say
that
wrong!
Well,
so
McCoy
you
might
want
to
unmute
your
mic
and
clarify
this
question
a
little
bit
because
I
know
that
you
posted
it
a
few
minutes
ago.
But
the
question
is:
won't
that
make
all
the
proposals
almost
the
same.
C
Okay,
I
think
so:
I'm
gonna
I'm
in
a
desk
guest,
try
to
guess
what
makula
is
asking
and
then
we're
going
to
ask
John
Mark
about
it.
So
McCool
I'm
going
to
try
to
put
words
in
your
mouth
I
think
what
makul
is
saying
is
that
if
new
potential
contributors
review
the
the
ideas
of
others,
won't
the
ideas
risk
all
being
the
same
and
and
so
because
they
looked
at
each
other's,
they
thought
about
them.
John
Mark.
How
would
you
respond.
D
It's
it's
a
very
interesting
question
and
it's
it's
the
essence
of
Open
Source,
so
I
I
like
open
source,
very,
very
much
because
it
looks
like
nature
in
in
nature,
copies
duplicates.
But
then
it's
the
difference.
D
Okay,
it's
a
competition
this
this
the
the
negative
side
of
that,
but
it's
the
plus
the
extra
that
you
put
on
it.
So
first
advice:
when
you
review
a
peer
appears
proposal.
D
The
first
thing
you
do
it
because
you
want
to
give
to
your
fellow
contributor
and
say
here
this
paragraph
I
did
not
understand
what
you
wanted
to
say.
So
you
really
do
it
to
help
your
partner
and
the
competition
side.
You
need
to
put
it
a
little
bit
aside.
Second
point
is
that
yes
you're
going
to
learn
other
ideas,
you're
going
to
say
so
you
can
copy
this
idea.
D
It's
part
of
life,
but
then
what
you
need
to
do
is
build
on
that
or
reflect
on
it
and
and
say
what
are
you
able
to
say
more,
better,
more
inventive,
more
with
new
ideas
and
things,
and
this
is
what
open
source
is
it's
this
explosion
of
idea
that
are
triggered
by
all
these
little
ideas,
so
so
I
I,
don't
know
how
to
convey
that.
So
it's
really
part
of
the
process.
C
This
ID
go
ahead:
Mark
I
I
was
going
to
give
a
very
specific
example.
So
one
of
the
proposals-
I
reviewed,
was
talking
about
plug-in
installation
manager,
tool
improvements
now
I'm
the
lead
Mentor
I'm.
The
potential
lead
Mentor
for
exactly
that
project,
but
the
project
idea
described
a
condition
that
I
had
not
considered
in
reviewing
it.
C
D
And
I'll
go
one
step
further
than
that
and
put
it
in
a
delight
when
we
review
and
grade
the
proposals,
don't
forget
that
what
we're
going
to
look
for
is
how
clearly,
can
you
explain
and
convey
your
ideas,
so
the
communication
thread
or
access
this
one
is
very
important.
It's
a
key
element
in
open
source.
D
The
other
element
is,
did
you
understand
the
problem
to
solve?
Do
you?
Do
you
have
a
good
grip
of
what
we're
talking
about
so
what
needs-
and
this
is
why
we
encourage
you
also
to
put
the
hands
in
the
engine
and
start
tuning
things
by
doing
PRS,
that
you
have
a
practical
experience
and
we
want
to
see
that
the
the
contributor
knows
what
he's
talking
about.
He
has
a
good
grip,
then
we
want
also
this.
D
He
even
understood
it
so
well
that
he
starts
thinking
out
of
the
box
and
comes
with
new
ideas
or
New
Perspectives,
and
this
is
where
you
can
cross
seed
Yourself
by
by
the
and
so
whole
process
that
we
look
for.
This
has
nothing
to
do
with
grading
a
an
interim
work
at
University,
I'm.
Sorry
to
say
that
way,
the
process
is
completely
different
and
this
is
why
it's
so
important
and
in
a
a
great
for
you,
it's
a
great
experience
to
go
through
through
this
process.
D
D
Just
a
little
note
for
Mark
and
Alyssa
I
prefer
to
skip
this
the
Outreach
Sig
and
stay
on
this
call
here
to
answer
and
discuss
with
people.
If
you
don't
mind
sure.
C
C
Take
notes,
I
will
happily
take
notes
until
I
have
to
drop
off.
So
if
you
want
to
shift
your
screen
sharing,
the
problem
was
I'm,
not
ready
to
shift
my
screen
to
to
share
my
screen.
That
shows
my
calendar
to
everybody.
I,
don't
want
the
humiliation
of
people
seeing
how
bad
my
calendar
looks
today
right.
C
D
Yeah,
do
that
and
I'm
going
to
pull
up
disorganized.
C
C
D
Here
we're
going
to
leave
it
that
way
so
I
don't
see
the
notes
anymore.
I
want
to
concentrate
on
on
the
questions
and
be
sure
so
chat
here.
I'm
I'm
completely
wasted
there.
It
is
okay,
so
we
had
a
question
from
safak.
D
What
are
the
best
practices
which
I
can
follow
while
communicating
with
mentors
project
maintainers
and
community
members
in
general?
That's
a
great
question,
and
and
if
we
find
the
answer,
I
can
write
a
book
on
it.
So
no
we
we
can
start
so
and
I
first
answered
that
way.
Best
practices
first,
one
General
be
respectful,
so
have
empathy
to
the
people
you're
talking
to,
and
you
need
to
know,
especially
when
talking
to
mentors
maintainers
these
people,
don't
do
only
that
then
so
they
have
other
duties.
D
I
have
other
duties,
so
we
need
to
squeeze
it
in
between
and
we
have
also
a
family
life
that
we
need
also
to
keep
balance
so
be
respectful
of
that.
So
don't
expect
an
immediate
answer.
Give
time
if
you
want
to
to
Ping
again.
Do
that
very.
Very
kindly
second
thing
is.
D
How
am
I
going
to
say
that
I
I
think
I
know
I,
remember
how
I
felt
in
your
position
so
you're,
not
speaking
to
gods
that
you're
just
a
little
warm
and
not
worthy
of
speaking
to
these
people?
No
they're
ordinary
people
like
you,
they
just
have
more
experience
in
one
field
where
you
might
have
much
more
experience
in
another
field,
so
we're
all
equal.
D
We
just
have
different
experiences
and
other
realm
of
exp
of
experience,
knowledge
and
also
the
years
I
I've
been
working
40
years
to
build
my
experience.
So
so
don't
the
message
I
want
to
get
across.
There
is
don't
be
afraid,
and
as
long
as
the
the
the
question
is
is
respectful
is
polite
is
thought
of
so
the
something
that
kills
maintainers
or
mentors
is
the
it
doesn't
work.
D
What
should
I
do
what
doesn't
work?
What
did
you
want
to
do,
or
or
these
kind
of
things
this
this
is
seen
by
mentors
or
project
maintainers
as
a
waste
of
their
time,
because
they
need
to
go
through
they're,
not
not
sure
that
you
tried
everything
they.
They
don't
have
a
clear
picture
where,
where
we
are
so,
this
is
in
the
innocent.
What
else
can
I
say?
D
Well,
this
is
basically
it
and,
and
once
the
project
continues,
that
we
have
the
the
grading
going
on
or
or
so
we
can't
have
this
this
conversation,
but
the
main
thing
is
be
use.
Empathy,
so
try
to
put
yourself
at
the
place
of
the
person
know
the
time
zone
know
his
environment.
He
probably
has
work
a
sick
child
or
something
like
that.
So
don't
expect
an
answer
in
the
in
the
next
two
hours.
If
it's
in
Middle
night,
where
I
need
to
shorten
because
I
seek
questions.
B
Do
you
also
suggest
doing
some
due
diligence
on
your
own
first
yeah.
D
That's
a
very
good
point
for
me:
it's
it's!
So
due
diligence
in
the
sense
when
you
ask
for
help
make
your
homework,
because
something
so
due
diligence
so
explore
read
experiment,
because
this
is
something
that
drives
people
crazy
in
in
well.
I
didn't
even
read
the
documentation,
so
I'm
I'm
exaggerating
a
little
bit
there,
but
here
yes,
yes
and
you
you
phrase
it
100
Alyssa.
Thank
you.
D
E
D
Yeah
Alyssa
I'm,
going
to
reclaim
hosting.
C
D
C
D
I
see
them
and
I'm
always
impressed
by
a
note
note:
keeping
kills.
Okay
now
need
to
show
my
chat.
C
D
D
I
I
I'll
stop
there
here,
so
I'll
walk
through
the
through
the
list.
There
was
a
second
question
from
Santa
next
question.
Most
mentors
would
be
having
other
work
as
well.
What
are
some
of
the
steps
which
I
can
take
as
a
mentee
to
make
it
easier?
I
think
we
answered
that
so
first
thing
is:
don't
expect
an
answer.
Be
patient,
wait
for
a
couple
of
days
and
be
do
your
homework.
D
Show
that
you
you.
You
understand
the
problem
that
you
you.
You
worked
on
it
that
you
did
the
due
diligence
as
Alyssa
said
very
well,
so
I
considered
that
as
Sam
Sam
had
a
question
here.
If
there
are
more
than
one
candidates
interested
from
the
same
project
idea
I
want
to
know.
How
would
you
consider
which
contributor
will
be
accepted
here,
a
very
legit
question,
so
the
process
is
that
way.
D
So
now
we're
still
in
the
preparation
phase
of
of
the
of
the
project
ideas
so
of
the
the
the
forgot
the
word
but
you're
preparing
draft.
Now
the
door
is
open.
You
can
start
submitting
the
final
one,
but
April
4th
is
a
cut
date.
There.
Everything
is
Frozen.
D
You
pull
the
hands
off
the
keyboard
now
it's
done,
and
the
mentors
will
start
then
and
will
not
take
in
account
the
work
that
the
review,
work
and
advice
that
has
been
given
before
so
they
use
as
it
is,
and
we're
going
we're
going
to
rank
or
give
a
note
to
each
of
the
proposals.
The
note
will
be
from
zero
to
five
zero
means
empty
proposal,
waste
spam
where
one
is
well
five
is
this
is
a
killer
proposal.
This
is
a
very
good
candidate.
D
He
knows
what
he's
talking
about.
He
can
explain
it
clearly
and
he
has
the
necessary
skills
to
achieve
the
goals
that
he
announced
every
month.
Mentor
is
going
to
do
independently
this
grading,
the
gradings
will
then
be
put
together,
and
this
work
is
done
by
the
org
admins,
where
we'll
see
patterns
per
project
and
we'll
see.
Who
are
the
proposals
that
will
bubble
up
and
so
we'll
have
an
idea
in
what
order
there
are.
D
D
This
means
that
at
current
state
we
have
seven
running
project
ideas,
but
we
have
a
four
senior
mentors
and
we
decided
that
one
lead
mentor
will
for
the
security
of
the
project
will
only
be
able
to
lead
one
project
idea
or
one
project
it
cannot.
He
cannot
split.
D
Some
of
the
lead.
Mentors
are
shared
on
two
projects-
Mark
for
instance,
and
it
had
two
and
we
get
good
proposal
on
there.
So
there
we're
going
to
decide
overall
holistically
what
is
the
best
candidate
that
we
have?
What
is
the
best
mentoring
team
that
we
can
build?
That
means
that
we'll
have
to
do
choices.
D
So
there
are
many
proposals-
your
this
year,
you're
you're,
very,
very
numerous.
So
it's
a
lot
of
people.
It's
it's
great
to
see
your
enthusiasm
in
there,
but
I
fear
not
all
will
be
chosen,
and
so
there
will
be
a
decision
process
and
will
end
up
with
team
and
best
student
or
best
candidate.
For
that,
and
then
we
need
to
get
that
approved
by
Google
so
because
we'll
go
to
Google
and
say
well,
okay,
this
is
our
plan.
D
These
we
can
do
and
take
the
responsibility
to
bring
to
successful
end
and
they
will-
and
they
will
say,
okay,
we
have
money
enough
and-
and
we
believe
you
you
can
do
this
for
I-
will
not
propose.
Oh
well,
no
I'm
I'm.
So
we
as
an
organ
team
because
we're
working
together
on
that
Chris
and
Alissa
and
Bruno,
but
I
will
make
sure
that
we
will
only
engage
in
projects
that
we
can
do
by
respect
to
the
people
that
are
proposing
projects
and
also
for
the
mentors
their
respect
of
their
time.
D
They
will
invest
and
there
long
long
reply
I
wanted
to
give
enough
details
how
the
process
is
I.
I
can
understand
that
it's
very
fuzzy
and
is
is
not
not
very
clear,
but
here
it's
a
competition.
D
It's
a
competition.
Did
that
answer
your
your
question.
It's
continue
scrolling,
so
I
need
to
hurry
up
and
give
less
details
so
I'm
moving
on
here
there
was
a
question
of
Sam
yell.
If
I
didn't
answer
your
question
correctly,
but
I
think
I
gave
many
details.
Jagruti
asked
in
the
light
of
withdrawn
ideas.
How
can
I
be
the
most
helpful
or
help
to
my
peers?
This
is
a
great
great
question.
D
One
thing:
I,
don't
know:
if
you
already
had
contacts
between
one
thing:
I,
don't
want
anybody
being
discouraged
cheated
or
depressed
about
with
that
I
I
would
feel
very
bad
if
you,
if
you're
there.
These
are
things
that
happen.
These
are
sometimes
you
work
on
a
project
and
at
the
last
time,
you're
just
going
to
tell
you
a
small
personal
history,
a
story
very
I
make
it
very
short.
D
Somebody
published
exactly
the
same
subject
than
him
and
so
five
years
worth
of
work
were
for
nothing
and
he
had
to
redo
everything
and
start
again.
So
these
are
the
kind
of
things
that
happened
so
jakruti
I
think
one
of
the
things
you
can
do
is
help
people
overcome
the
disappointment
and
say
we
can
learn
from
them.
People
that
are
going
to
reorient
themselves
will
ask
publicly
because
they
they
are
learning
in
a
new
subject
which
will
be
a
challenge
for
them
and
they
will
need
some
guidance
here.
D
I,
don't
understand
that.
Could
somebody
explain
me
that
or
some
guidance
there
I
think
it's
a
fair
step
to
help
them
too
there's
a
lot
of
good
activity
on
on
guitar
I
have
a
hard
time
following
all
the
all
the
the
very
good
traffic
happening
there.
So
don't
hesitate
to
help
and
answer
questions
their
be
cautious.
Sometimes
what
you
think
is
the
correct
answer.
You
might
be
wrong,
so
we
will
do
also
your
your
own
research.
So
this
is
the
the
advice.
So
this
is
on
the
top
of
of
my
head.
D
It's
a
it's
a
very
good
question
and
also
a
very
honest
and
I
I,
there's
a
very
good
good
thinking
for
you.
So
I
really
appreciate
and
that's
so
where
I
am
lost.
My
thread
here
so.
C
D
So
two
things
so:
first
a
draft
a
work
in
progress
is,
is
done
to
check
if
the
bases
are
correct.
So
it's
an
interactive
mode
to
come
back
to
what
we
do
in
open
source.
You
can
create
a
pull
request
and
set
it
in
draft
and
say
I'm
still
working
on
it
and
invite
other
hey
have
a
look
to
what
I
already
did
so
this.
This
is
the
usual
way
we
work.
The
second
thing
is
a
very
good
point
too.
D
When
you
completed
your
document
or
you
have
added
another
important
layer
to
the
document,
remind
people
and
say
here:
I
have
my
second
edition
of
the
document
and
please
have
a
particular
look
to
these
sections
that
I
added
so
that
it
it
it
pops
out
to
the
people
that
are
are
Riri,
but
the
process
is
is
correct.
D
I
hope,
I
answered
that
question.
Mark
should
I
look
in
your
document
for
the
next
one
or.
C
I'm
just
going
to
read
you
the
next
question.
Thank
you.
Okay.
So
when
I
register
for
gsoc
there
is
a
question
I
need
to
answer
quote:
have
you
ever
contributed
to
open
source
before
if
I
choose?
Yes,
I
need
to
write
a
reason
to
explain
why
it
looks
like
gsoc
prefers
people
who
haven't
contributed
to
open
source
projects.
Yet
is
it
correct.
D
What
is
behind
this
question
is:
if
you
have
already
been
acquainted
with
the
ways
of
Open
Source,
it's
a
very
interesting
and
important
point
to
explain
what
were
your
motivations?
What
did
you
learn
that
that
helps
to
estimate?
D
What
is
your,
how
comfortable
do
you
feel
with
the
ways
of
open
source
in
in
a
way,
if
you
say
I,
never
contributed
to
open
source?
We
know.
Okay,
this
is
a
blank
page,
so
we
know
that
people
need
to
learn
and
need
really
to
be
coached.
Both
are
interesting
on
on
one
side
showing
showing
the
way
and
showing
the
the
experience
of
Open
Source
to
somebody
who's
completely
new
to
it
can
be
an
interesting
Challenge
and
is
important
on
the
other
side.
Somebody
has
already
some
experience.
D
D
This
is
my
interpretation
of
that
and
what
we
want
to
avoid
and
what
Google
wants
to
avoid
is
that
people
that
have
five
or
ten
years
of
experience
under
the
belts
doing
open
source
and
they
know
everything
inside
out
and
just
want
to
to
earn
some
pocket
money
with
g-soc
I
know
these,
were
we
don't
look,
so
we
want
really
young
professionals,
young
developers
from
schools
or
or
so
some
of
between
you
have
been
dealing
with
open
source
already
since
12
years
or
very
early,
so
I
I,
hope,
I,
didn't
confuse
everybody
with
my
answer
so,
but
the
there
are
two
aspects.
C
C
If,
if
this
is
your
first
experience
contributing
to
open
source,
you
should
answer
yes.
I
have,
and
this
is
in
the
Jenkins
project
as
part
of
preparing
for
Google
summer
of
code
2023,
because
to
say
I've
never
contributed
to
open
source
feels
feels
not
accurate
here,
because
we
hope
you're
contributing
already
to
open
source
with
at
least
a
few
pull
requests
with
Lee,
at
least
some
interactions
that
we
can
use
to
assess
your
abilities.
C
If
you're,
not
that's,
that's
going
to
reduce
your
chance
of
being
accepted,
we
need
to
see
you
make
contributions
so
so,
for
me,
it
may
be
that
you
could
say:
Google
prefers
people
who
haven't
contributed.
What
they're,
looking
for
as
John
Mark
said,
is
people
who
are
less
experienced
and
significantly
less
experienced
than
the
seasoned
professionals
who've
been
doing
open
source
for
a
long
time.
Syed,
for
instance,
would
not
be
acceptable
as
a
as
a
Google
summer
of
code
contributor,
too
much
open
source
experience
already
right.
D
Need
yes,
sure
now
I
see
that
a
chat
is
filling
in,
so
we
have
25
message
to
go
in
quarter
of
an
hour.
I
I
get
I
I
get
over
enthusiastic
about
that,
but
it's
very
near
to
my
heart
so
and
I
want
to
to
answer
as
many
questions
as
as
we
can.
What
is
the
next
question
mark?
Can
you
help
me.
C
C
D
Okay,
I
need
to
be
honest
there,
so
my
my
general
advice
rewind.
So
we
need
to
choose
people
that
have
the
best
ability
to
reach
the
end
and
that
we
don't
have
to
invest
as
mentors
a
huge
amount
of
time
to
get
them
to
level
and
get
them
to
get
them
going.
So,
but
it's
okay,
if
the
the
the
the
your
understanding
is
fuzzy,
so
my
advice
there
would
be
try
it,
but
don't
be
disappointed
if
you
don't
make
it
this
year
and
the
rules
are
open
enough.
D
D
Read
tests,
provide
new
code
so
to
be
part
of
it.
I
I
restate
the
the
example
I
gave
in
December.
How
do
you
prepare
it's
about
building
muscle
and
how
do
you
build
muscle
it's
by
exercising
by
learning?
By
that
everything
starts
to
be
automatic
there?
It
might
be
that
you
don't
make
it
to
the
Olympics
with
the
current
level
and
well
okay,
it
will
be
disappointed,
don't
give
up,
continue,
learning
continue,
exercising
continue
exploring
and
you
will
have
a
much
stronger
position
at
the
next
next
time.
D
C
C
Have
a
new
new
question:
are
you
ready
for
the
next
question?
Go
ahead?
Okay,
how
can
I
make
my
proposal
stand
out,
so
I
get
I'm
the
one
selected?
Does
it
matter
to
send
my
proposal
early
or
should
I
be
late
to
be
make
a
better
proposal.
D
So
the
the
first
thing,
the
only
way
to
stand
out,
is
to
have
the
best
proposal.
Now
it's
your
responsibility
to
find
the
understanding
and
and
so
I
cannot
give
some
magic
tricks.
Otherwise,
I
will
start
giving
you
sorcery
tricks,
since
starting
with
with
a
black
rolling
and
things
like
that
and
doing
weird
things.
D
D
This
is
unfair.
This
is
my
the
the
thing
sending
proposal
early
or
late.
It
doesn't
make
make
a
difference
at
all,
because
we
will
start
reading
the
proposal
and
ranking
them
only
at
April
4th,
and
we
will
forget
everything
that
we
read
before
and
before
what
we're
reading
right
now
is
just
the
mentoring
phase
for
us
to
help
you
to
make
the
the
most
powerful
proposal
so
bringing
it
early
or
these
tactical
questions,
don't
play
a
role
in
our
irrelevant.
So
that's
that's!
D
No!
You
you
can
you
you
can
try
other
tricks
like
like
I.
Don't
know
throwing
salt
over
your
shoulder
or
these
kind
of
things,
but.
C
It
doesn't
work
so
John
Mark
there
is
a.
There
may
be
a
subtlety
that
may
not
be
immediately
obvious
to
them,
I
believe
in
the
past.
Anyway,
once
a
proposal
was
submitted
to
Google
summer
of
code,
it
was
unmodifiable
by
the
submitter,
so
submission,
if
I
recall
correctly,
is
a
lockdown
of
The
Proposal.
Right
so
is.
Is
that
still
the
case
that
it
is
a
lot?
No
as
soon
as
I
submit
it
is
locked
down,
I
can't
modify.
No,
they
lock
the.
B
D
Going
to
request
Google
and
I'll
I'll
delete
the
proposal
to
give
the
chance
for
the
the
candidates
to
to
review
the
the
or
or
to
resubmit,
The
Proposal.
Okay,.
C
D
D
So
a
good
point
mark
I'm,
seeing
I,
don't
know
where
you
are
too
many
things
in
the
chat.
This
is
probably
because
I
talk.
C
D
Yeah,
okay,
is
it
counted?
Yes,
it's
it's
an
indicator
of
experience
and
don't
forget
to
show
evidence
of
that.
Now.
Don't
forget
we're
interested
in
Jenkins
experience
in
Jenkins
that
you
know
what
a
plugin
is
how
Jenkins
works.
This
is
what
we're
interested
now,
if
you
already
had
the
the
experience
by
of
Open
Source
participating
to
another
one,
and
you
submitted
a
pull
request
for
kubernetes.
So
these
kind
of
things
well,
okay,
mention
it
it's
it's
an
interesting
point,
but
it's
not
a
decisive
one
of
this
correct
English.
D
Do
I!
Think
that
answered
the
question
great.
We
have
five
more
minutes
here.
I'm,
sorry
for
the
the
questions
I'm
going
to
look
at
them,
try
to
answer
them
in
the
chat,
otherwise
we
can
revisit
them.
I
will
be
too
late.
C
D
D
So
they
say:
okay,
nobody
else
is
going
to
answer
them
now.
You're,
the
judge
I
know
it's
difficult
to
judge
that,
but
here
at
a
certain
point,
good
is
good
enough.
If
you
continue
tweaking
the
document,
it's
not
going
to
help
and
you're
going
to
miss
the
deadline.
D
C
One
of
the
indicators,
if
you're
not
seeing
Mentor
reviews,
it
probably
hasn't
been
reviewed,
I'm
I'm,
not
aware
of
any
Mentor
who
has
reviewed
a
document
and
given
zero
comments.
That
would
be
quite
shocking,
so
so
jagruti
when
you
when,
if
you
don't
see,
review
comments
now,
if
you've
received
comments
and
not
responded
to
them
either
by
resolving
them
or
applying
them.
That
says:
you're
not
paying
attention
to
our
reviews,
so
so.
D
On
on
the
other
side,
what
could
be
a
good
good
practice?
Is
you
you
thought
about
the
comments?
Yeah
important
thing
that
I've
seen
I
just
do
a
small
side.
Note
here
answering
in
the
comments
will
not
help
improve
your
document.
Answer
the
question
from
from
the
mentor
or
the
reviewer
in
your
document.
This
is
where
it
has
and
coming
back
to
the
to
the
question
is:
if
you
thought
off
and
processed
the
different
comments
that
were
made,
where
maybe
Santa
ping
and
say
here,
I
included
the
various
comments.
D
Could
somebody
have
a
last
last
review
of
IT
Alas
and
focusing
maybe
on
this
part
of
that
part,
comes
to
the
same
question
we
had
earlier
about
submitting
in
layers
so
boom
Mark,
two
minutes
left,
I,
I.
Think.
D
D
Oh
okay,
okay
last
last
thing,
I
say
it
again:
if
people
feel
bad
or
have
problems
with
the
the
decision,
we've
taken
and
I
stand
for
that
decision.
So
this
decision
is
not
going
to
be
changed,
I'm
ready
to
discuss
and
have
a
virtual
coffee
with
anyone
who
would
like
to.
We
can
discuss
it
in
and
see
how
we
can
move
out
of
that.
So
the
offer
is
open
to
anybody.
D
I
said
that
one-to-one
communication
with
mentors
is
frowned
on,
because
I
don't
want
to
give
a
particular
advantage
or
a
non-ethical
advantage
to
to
competitors.
This
is
a
special
case,
the
special
case
and
as
org
admin.
Although
I
like
to
read
the
proposals,
so
I
can
make
an
exception
here,
drash
race,
his
end,
you
probably
will
be
the
last
one
to
go:
go
ahead,
rash.
E
Yes,
so
this
is
very
quick.
I
just
want
to
say,
I
want
to
add
a
little
bit
more
on
the
decision
that
we
have
taken.
I
agree
with
the
decision
that
has
been
taken,
because
I
totally
fully
believe
that
having
a
lead
Mentor
is
extremely
crucial,
because
I
was
contributed
to
Jenkins
last
year
as
a
gsoc,
applicant
and
I
good
I
totally
understand
that
they
do
a
lot
of
planning
for
you
in
advance.
E
They
prepare
the
tasks
for
you
throughout
the
whole
coding
phase,
in
an
increasing
order
of
complexity,
so
that
you
do
not
get
overburdened
at
all.
They
take
care
of
your
mental
health
as
well
I
mean
not
to
burden
you
with
lots
of
work,
so
they
take
care
of
everything,
so
that
requires
lots
of
patience,
planning
and
careful
consideration
right.
So
you
cannot
expect
that
from
a
very
Junior
Mentor,
so
that
would
be
a
problematic
situation
for
both
you
as
a
contributor
and
the
mentor.
E
D
D
Thank
you
dhirash
and
happy
to
have
you
as
co-mentored
this
year,
looking
forward.
Okay,
so
we're
now
at
16
hours,
UTC,
so
we're
around
the
other
the
hour
I.
Thank
you
very
much
for
your
patience
for
being
that
many
here
around
the
table
to
ask
question
and
to
discuss
about
that
really
appreciate
that
I
apologize
again
for
being
10
minutes
late
in
a
meeting.
It
was
an
important
meeting
and
all
your
work
is
important.