►
From YouTube: GSoC Office Hours - June 23, 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
There
we
are
so
good
evening,
good
afternoon,
good
morning,
everybody
we're
for
this
gsoc
global
office
hour
and,
let's
start
immediately.
A
I
have
a
general
information
to
to
give,
but
I
don't
find
my
notes
hold
on
there.
I
tend
I
am
an
old
man,
so
I
tend
to
forget
here.
We
are
okay,
hey
chris.
That
would
be
a
great
help
if
you
can
write
the
name
just
in
the
document.
So
the
first
question
I
have
a
lot
of
documents
have
been
produced
during
the
bonding
period
and
currently
project
plans.
A
Planning
descriptions,
don't
forget
to
update
the
your
project
page
on
jenkins.io,
with
the
links
to
this
document.
A
lot
of
good
work
has
been
done
and
if
the
community
wants
to
learn
more
and
follow.
A
A
Speaking
of
that,
we're
just
to
be
sure
that
all
the
projects
are
are
okay
and
we
didn't
forget
anything.
I'm
going
to
ask
the
lead
mentor
of
each
project
to
see
if
all
the
tasks
in
the
bonding
periods.
A
Face
especially
project
plan
describing
what
is
what
will
be
delivered?
What
is
the
timing
that
all
that
is
defined,
and
everybody
agrees
with
that,
so
I'm
going
to
send
a
survey
to
the
mentors
to
check
that
a
little
detail
for
adrian
and
diraj,
I'm
missing
the
link
for
your
office
hour,
so
this
will
need
it
needs
to
be
updated
in
in
a
project
page.
A
A
Sure,
okay,
no
no
problem,
so
this
is
just
housekeeping.
So,
let's
start
with
the
status
of
the
different
projects
and,
let's
start
with
the
first
one,
because
jimin
was
was
ready
to
to
start
immediately.
I
think
he's
done
quite
a
lot
of
work
this
this
week,
gaming.
The
floor
is
yours.
So
what
did
you
achieve
this
week?.
D
Okay,
this
weekend
last
week
I
created
a
proof
of
concept
repository
and
develop
several
draft
github
actions
for
jackings
file,
runner
yeah,
you
can,
you
can
see
it
in
that
proof
of
concept
repository
and
I
also
send
out
the
messages
about
this
project
in
the
developer
mailing
list
in
the
discourse.
D
So
I
think
the
progress
is
good.
Now.
A
A
A
Okay,
do
you
have
some
impediments
or
things
that
are
not
working
or
that
could
prevent
you
moving
ahead.
A
A
I
had
already
a
good
discussion
with
diraj
and
the
three
others
will
have
the
discussion
next
week,
so
you
so
you
know
that
and
what's
discussed
during
these
meetings
stays
between
each
other
but
other
things
to
share
so
good.
So
yummy
we're
we're
going
to
have
a
chat
together,
free
nobody
else.
Listening.
A
Yeah,
okay,
so
just
to
listen.
If
everything's
going,
okay,
okay,
the
next
projects,
do
we
have?
Oh,
no,
we
have
the
rush
rash,
tell
us
what
has
been
happening
last
week.
I
I
know
one
I'm
going
to
to
tell
it
immediately.
You
had
your
first
pr
emerged.
C
Sure
so
this
week
I
got
my
first
pr
merged
in
and
it
was
a
rather
long
pr
and
we
decided
that
there
are
some
things
that
we
will
be
coming
back
to
later
in
time
to
improve
a
few
minutes
and
gets
so
that
has
been
decided
and
now
that
we
have
some
more
like
some
part
of
the
application
in
the
repository
merged.
C
Then
we
started
the
work
on
dockerizing
the
whole
application.
C
So
I
put
up
a
pr
two
days
ago-
and
I
got
very
great
review
comments
all
around
that,
like
how
can
I
improve
the
docker
file
creation
and
all
about
it,
so
I'm
I'll
be
currently
working
on
it
and
on
on
a
side
note
this
week
I
was
little
less
a
little
less
available
due
to
some
other
commitments,
work
commitment.
So
that's
why
it
was
a
little
slow.
C
So
I'm
aiming
to
compensate,
not
compensate,
but
just
I
really
excited
to
work
on
it
this
weekend
to
dockerize
the
con
container
the
project
and
get
that
vr
merged
as
soon
as
possible
as
well.
So
that
can
I.
A
C
D
A
A
Thank
you
so
much!
That's
that's
a
good
excuse!
No,
no
excuse,
but
a
good
thing
that
way
you
you
couldn't
spend
as
much
time
on
the
gsoc
project
so
that
that's
good
comments
from
the
two
mentors
jacob
adrian.
Do
you
want
to
add
something.
E
No
really
direct
has
been
very
good
at
answering
comments
on
on
the
previous
pr's
and
he's
learning
a
few
things.
That's
what
we
try
to
to
have
him
to
to
learn
so
not
only
saying
no,
that's
not
correct,
but
pointing
to
the
correct
direction.
I
think
that's
the
whole
purpose
of
this
gsoc,
so
we're
trying
to
do
that.
A
E
E
C
Or
no,
no,
everything
is
covered
by
it.
Congratulations.
A
Okay,
good
are
any
impediments
or
problems.
Is
the
infrastructure
part
solved,
or
did
you
get
the
answers.
E
C
D
E
Requirement
for
the
moment,
we
are
not
in
the
deployment
phase
phase
so
far
so.
B
E
No,
no
problem
for
that,
and
if
at
when,
I
see
that
we
are
close
to
something
we
could
deploy
on
on
the
infra
on
the
jenkins
infra
I'll,
be
targeting
that.
So
I
don't
want
to
disturb
diraj
with
that
kind
of
questions
and
requirement
and
meeting
people
and
getting
details
and
so
on.
So
I'll
I'll
be
I'll,
be
doing
that
part
further
for
the
project,
so
that.
E
On
on
the
on
on
the
code
and
on
the
actual
project,
but
not
on
the
how
to
deploy
the
project
he'll
be
doing,
of
course,
dhiraj
will
be
doing
the
deployment
and
making
sure
that
the
project
is
deployable
correctly
and
so
on.
But
all
the
infrastructure
questions
I'll
be
tackling
that,
and
so
jiraj
won't
have
to
won't,
have
to
to
ask
questions
or
to
figure
out
how
to
deploy
I'll,
be
able
to
help
him
do
that
and
have
all
the
requirements.
E
That
that's
good
also,
I
think
that's
one
of
the
first
from
my
marriage.
It's
one
of
the
first
gesso
project
jenkins
has
that
will
not
land
in
jenkins
or
in
the
existing
infra.
So
we
are
being
a
big
on
the
side
from
different
other
projects.
B
E
The
past,
so
no,
no,
that's
a
very
good
question
and
we
haven't
forgot
forgotten
about
that
and
it's
just
it's
not
a
priority
for
the
moment.
There's
a
bigger
fish.
A
A
Very
good,
great
chris
or
jake.
Do
you
want
to
add
something
to
the
discussion.
B
A
No
vyan
is
there:
okay,
now
you're
you're
in
the
corner
of
my
screen.
I
apologize
for
that.
I'm
awfully
sorry,
oh
no,
no
problem,
and
you
were
one
of
the
first
to
be
to
be
there.
Oh
I'm!
I'm
sorry
about
that.
Diane
tell
us
where,
where
are
you
standing?
What
what
was
done
this
week.
C
Sure,
hey
everyone!
So
this
week
I
went
ahead
and
did
the
second
request
first,
which
was
which
was
about
the
plugin
list
on
the
python
steps
reference
page.
So
that
has
been
done
and
tim
was
quite
skeptical
about
it,
whether
it
is
required
or
not.
C
But
then
we
had
a
nice
discussion
about
that
in
the
project
meet
and
then
we
thought
that
it's
nice
to
include
it
and
then
we'll
see
if
we
have
any
feedback
regarding
that,
if
there
is
a
need
to
alter
it
or
maybe
remove
it
in
the
future,
so
that
can
be
seen
because
there
is
no
specific
feedback
about
that
particular
page
as
of
now.
So
we
actually
don't
know
what
the
user
will
be.
C
You
know
getting
benefit
from
so
that
was
the
first
half
of
it
and
then
in
the
pipeline,
like
the
step
talks
officers,
we
had
a
a
pretty
long
discussion
where
christian
explained
a
lot
of
the
code
to
me,
and
we
came
out
with
new
some
great
ideas
how
to
improve
that
particular
piece
of
code
and
with
respect
to
that,
she
suggested
that
we
can
separate
the
declarative
steps
generation
from
the
main
class,
which
would
be
actually
very
helpful.
C
If,
in
the
future,
we
decide
to
exclude
the
declarative
all
together
from
the
steps
reference.
So
I
today
I
separated
that
and
there's
a
request
in
the
step,
doc
generator
repository
for
that
and
in
this
week
until
the
next
me
tell
them
next
officers.
The
target
is
to
work
on
the
step,
steps,
details
that
are
generated
and
shift
the
data
type
from
the
body
to
the
heading.
So
that
is
some
because
so.
C
Can
you
say
that
again
the
data
type
thing.
A
C
C
C
That
is
slightly
challenging
to
do,
because
there
are
two
or
three
variations
of
how
that
is
done
on
the
page
itself,
so
we
can
go
towards
that
in
a
bite-sized
manner,
so
one
by
one-
and
that
is
what
the
put
requests
are
also
about
so
christian
and
I
both
agreed
that
it's
better
to
keep
the
pull
requests
bite-sized.
C
So
one
feature
at
a
time,
so
the
third
pull
request
was
created
today.
So
far,
none
of
them
have
been
merged,
mostly
because
of
the
security
release
that
was
coming
for
jenkins
at
iowa,
so
yeah
requests
are
still
there,
but
I
am
I'm
hopeful
that
they'll
get
merged
with
them
this
week
or
so
so,
no.
A
Very
good
any
problems
worries.
No,
I
think
everything
is
going
great
from
what
I
see
from
it.
I
can
confirm
that
good.
I
think
we
went
wrong
around.
We
had
a
a
good
overview.
There
is
one
project
who
she
didn't
join,
don't
forget,
as
there's
been
quite
some
interesting
and
good
project
documentation
that
has
been
generated
to
add
that
to
the
project
page,
so
that
people,
when
they
join
later
in
the
project,
can
see
what's
how
where
things
are
done.
Okay
last
questions
remarks
wishes.