►
From YouTube: GSoC 2023 Office Hours - April 6, 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
Three
two
one:
hello,
thank
you
for
the
counting
so
good
evening,
good
afternoon,
good
morning,
everybody.
This
is
an
informal
gsoc
office
hour
where
no
real
agenda
is
foreseen.
We
just
meet
and
answer
questions.
A
We
recorded
a
little
bit
late
and
there
was
an
interesting
question
from
mukul
where
he
wanted
to
have
some
ideas
and
maybe
advice
on
how
to
better
handle
discussions.
A
On
GitHub,
so
it
appears
that
mukul
proposed
something,
or
somebody
proposed
something
in
a
PR
additional
informations
were
requested
and
somehow
the
point
was
not
really
understood
and
there
was
an
impedance
mismatch
and
it
didn't
work.
So
the
communication
did
not
work
so
I
open
it.
So
who
would
like
to
start
answering.
B
I
just
have
one
one
question:
I,
just
posted
a
link
to
the
pr
that
I
think
you're
referring
to
be
cool,
and
could
you
please
confirmed.
B
So
I'm
I'm,
just
breathing
through
the
the
pr
and
I,
see
that
so
there's
a
lot
of
exchange
with
Chris
the
maintainer
of
the
plugin
and
from
what
I
see
she's
trying
to
sorry.
He
is
trying
to
push
you
to
Express
what
you
trying
to
say
in
the
pr
a
bit
more
precisely
and
the
different
exchange.
B
I
think
in
the
end,
please
added
the
rfe
label
just
to
mention
that
maybe
that's
more
a
new
feature
that
you
we're
trying
to
address,
rather
than
a
fix
or
something
like
that,
but
to
a
question
how
to
understand
better,
the
miscommunication
and
so
on,
I
think
on
both
sides.
You
did
your
best
to
explain
your
different
points
and
the
different
aspects
of
that
VR.
B
It
seemed
that
I
didn't
see
the
I
didn't
pay
attention
to
the
time
window.
So
it's
all
happened
in
in
the
same
day,
but
I
see
that
there's
like
38
messages,
Edge
changed
in
that
piano.
I.
B
Think
at
some
point,
when
you
were
when
you
reach
that
number
of
message
and
the
point
is
still
not
understandable
or
comprehensive
for
both
party
or
everyone
on
the
involved
in
the
piano,
it
probably
means
the
the
only
solution
forward
is
to
close
the
pr,
because
it
seems
to
have
a
fundamental
miscommunication
or
disagreement
that
will
not
reach
any
constantials
or
reach
any
any
viable
solution
for
both
starting
and
in
the
end.
It's
it's
not
like.
B
The
the
maintainer
has
the
the
power
on
the
on
the
on
the
on
the
plugin
you
can
accept,
because
in
the
end
the
maintainer
is
responsible
to
keep
the
plugin
LC
and
to
keep
the
plugin
working
for
a
very
long
time
more
than
just
your
contribution.
So
if
it
can
happen,
it
did
happen
to
me
in
the
past
also
to
refuse
a
pull
request.
Just
because
I
didn't
see
the
point
of
the
pull
request.
I
didn't
see
what
was
the
value
of
the
addition
and
I?
B
Oh
because
I
was
not
sure
how
to
maintain
that
in
in
the
in
the
long
term,
maybe
you're
trying
to
solve
a
solution,
but
the
way
you
are
trying
to
solve.
It
is
not
the
best
way
to
to
do
it
and
not
the
most
maintainable
way
to
do
it.
So
it
don't
take
it
personally.
It's
not
it's
not
against
you.
It's
not
because
you
are
you
because
of
whatever
personal
reasons.
B
Really
it's
in
the
end,
the
the
the
the
and
I
I
don't
know,
Chris
personally,
but
I
I
I'm
sure
the
the
the
reason
is
just
for
the
sake
of
the
plugin
else
and
it's
long-term
maintainability.
That's
all
so
don't
take
it
personally.
I
think
you
did
your
best
to
try
to
make
your
point
and
try
to
offer
your
Your
solution
to
the
plugin,
but
in
the
end
sometimes
it
doesn't
make.
It
doesn't
mean
that
you
shouldn't
try
to
contribute
to
it
again.
B
It
doesn't
mean
that
you
should
stop
contributing
to
anything.
On
the
contrary,
please
continue
you'll
learn
from
that
and
maybe
next
time
it
will
be
easier
for
Chris
to
understand
your
point
or
to
onto
to
understand
what
you
are
trying
to
add.
One
comment
I
will
I
would
I
would
add
to
maybe
to
improve
the
beginning
of
the
this
of
the
of
the
pull
request
is
your
first
message
on
the
pull
request
is
quite
small.
B
B
In
many
cases,
I
prefer
to
have
a
five
minute
read
when
I
open
up
something
to
read
for
five
minutes
when
I.
First,
on
the
first
message
of
the
pull
request
that
sets.
What's,
the
pull
request
is
trying
to
solve
why
the
problem
was
reported,
how
I
tried
to
how
the
pull
request
author
try
to
solve
it?
B
A
Okay,
very
good
I
have
a
few
comments
before
maybe
letting
somebody
else
so.
First
thing
it
is
a
super
identical
to
have
raised
that
question.
It's
very
interesting
and
we
would
like
to
help
you
understand
and
see
what
happens
so
the
summary
of
what
Adrian
said.
It
is
very
important
that
we
have
efficient
communication.
A
The
reason
for
that
is
that
mentors
or
maintainers
have
a
lot
of
parallel
requests
and
things
to
handle,
so
the
the
advice
of
having
a
strong
description
at
start
definitely
helps
to
to
to
to
to
to
to
to
to
get
the
review
going.
A
The
second
thing
that
I've
seen
is
that
there
were
a
lot
of
confusions
in
in
from
what
what
I've
seen
in
it
so
several
topics
and
at
the
end
it
was
somehow
related
to
the
issue,
but
not
really,
and
the
idea
has
been
picked
and
flagged
as
a
request
for
enhancement.
This
is
the
meaning
of
rfe.
If
you
are
wondering
what
it
what
it
means.
So
this
is
a
request
for
enhancement,
so
he
said
well,
okay.
A
This
is
an
idea
we
need
to
to
to
keep
note
off,
but
at
the
end,
looking
at
it,
it
was
far
too
confused
in
in
too
many
things.
It
was
better
to
start
again
on
a
blank
page
and
and
take
it
over
later.
A
D
At
first
like
during
that,
solving
that
we
are
firstly,
I
learned
a
lot
I
learned,
Ruby
I
I
explored
the
get
lab
code
base
for
this,
like
how
they
are
approaching
this
and
what
they
have
done,
and
on
the
gitlab
login
page
like
how
it
is
handled,
why
that
bug
was
happening
so
throughout
this
I
learned
a
lot,
even
though
the
pr
didn't
get
accepted,
but
I
want
like.
D
No,
no
I
didn't
see
that
what
Adrian
said
I
accepted
what
agent
said
that
at
start
wasn't
clear
like
it
didn't
mention
the
points
that
I
had
to
mention.
Afterward
in
the
conversation
so
and
I
didn't
feel
attacked
like
it
was
normal
to
have
conversation,
I
didn't
clear,
clear
it
out
what
I
was
trying
to
do
in
that
PR
so,
but
like
what
I
want
is
to
clear
that
what
I
can
do
in
future
that
make
my
PR
accepted
faster.
D
Basically
that
at
start
I
have
to
summarize
what
I
am
trying
to
do
in
a
in
the
comment.
It's
comment
not
comment
in
the
pr
itself,
like
description
of
the
pr
that,
like
what
I
can
converse
later
on,
like
what
I
can
explain
later
on
the
through
the
chat.
Through
the
comments
like
what
I
have
tried
to
talk
with
the.
D
While
raising
it,
so
this
can
clear
it
faster
for
the
maintainer
so
that
they
can
easily
accept
it
when
like
they
can
easily
understand
it
when
they
just
go
through
it
at
the
first
time
right.
A
Okay
now,
especially
when
you're
learning
and
you're
getting
into
a
a
code
base,
and
things
like
that,
so
put
yourself
at
the
place
of
the
person
reading
it
and
and
ask
yourself
how
would
I
react,
how
it
because
here
it's
conversation
of
35
messages
or
with
with
just
a
limited
number
of
information,
so
try
to
to
think?
Oh,
he
would
like
to
know
this
or
he
needs
this
context,
and
so
it's
not
because
it's
clear
in
your
head
that
other
people
know
what
you
have
been
thinking
about.
B
And
just
to
add,
a
lot
of
the
open
source
work
is
on
communication
as
well.
It's
very
important.
We
all
work
on
different
aspects.
We
have
day
jobs
we,
but
we
all
are
focused
on
the
same
project,
at
least
for
a
period
of
time,
and
communicating
and
expressing
yourself
is
very
important.
So
the
this
meeting,
for
example,
is
one
way
to
do
that
and
we
have
other
segmentings
in
Jenkins
Community.
A
Yeah
now
he
he's
policing
in
in
organizing
the
work
on
his
plugin
and
we
need
to
respect
it
and
he's
responsible
of
that.
So
at
certain
time
you
say
here
this
this
conversation
is
leading
nowhere,
maybe
hint
on
maybe
restart
or
or
so
or
or
take
it
up
later.
So,
especially
as
here,
we
are
now
in
a
special
period
where
we
try
to
concentrate
on
the
proposals
and
only
the
proposal
not
to
be
influenced
by
external
things.
So
anyway,
good
good
question
and
we'll
try
to
explore
that
later.
C
I
have
a
question
like
in
the
Jenkins
Community.
We
have
a
lot
of
online
meetings
related
to
different
stuff
and
like
I,
just
I
was
just
exploding,
so
should
I
try
to
attend
every
meeting
like
it's
very
hard
to
just
try
to
get
to
know
everything.
A
A
So
yes,
I
I,
know
the
pain.
I,
know
the
pain,
and
but
here
the
only
thing
I
can
say
is
you're
in
front
of
a
big
mountain.
It
looks
very,
very
high
and
difficult,
and
once
you
start
one
step
after
the
other,
you
will
realize.
Oh
it's
not
that
complicated
I'm
in
the
middle.
You
will
still
be
focused
on
the
top,
but
if
you
turn
around
and
realize
oh
I
know
already
all
that
so
I'm
mastering
these
part,
these
parts
I
can
help
others
that
are
lower
on
the
mountain.
A
So
don't
give
up
and
I
I
know
the
feeling
of
this.
This
daunting
pressure
there,
the
only
thing
I
can
say
here
how
exciting
it
is.
There's
so
many
things
to
explore,
try
to
understand
but
I
stopped
chatting,
so
they
are
but
a
good
point.
Good.
A
Now
I
will
I
will
take
again
my
my
lead,
Mentor
or
lead
org
admin,
their
hat
and
say
here.
This
is
really
the
interesting
School
of
this
open
source.
Adventure
that
you
are
embarking
that
you
embarked
on
are
still
in.
You
are
learning
many
many
skills
that
will
be
very
helpful
for
you
professionally
later
in
your
open
source
career
and
also
as
as
a
person
so
you're
you.
How
do
you
organize
your
work?
How
you
organize
your
your
time,
how
you
discuss
with
people?
A
How
do
you
learn
a
new
topic,
so
this
is
an
incredible
tool
to
to
learn
and
where
I'm,
advocating
and
selling
it,
but
I
think
open
source
is,
is
a
great
way
to
invest
your
time
outside
of
school.
A
Okay,
so
this
time
will
stop
on
time
in
three
minutes,
because
we
have
so
I
have
a
meeting
in
three
minutes
and
even
have
a
conflict
between
meetings.
A
So
I'll
have
to
flip
a
coin,
to
decide
which
meeting
I'm
going
to
to
and
I
see,
Alyssa
smiling.
So
she
knows
what
I'm
talking
about
so
we're
going
to
end
here:
I,
just
opening
for
a
last
minute
comment
or
question
or
whatever.
Otherwise
we're
going
to
switch
off.
A
Okay,
so
thank
you
very
much
for
attending
it's
it's
great
to
meet
you
all
in
exchanging
continue
the
best
and
I'm
very
honored
to
participate
in
that.
So
this
said,
I
will
close
the
call
and
move
to
other
discussions
topics
so
have
a
great
week.
Bye,
bye,
everybody
thank.