►
From YouTube: GSoC Office Hours - July 7, 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
morning,
good
afternoon,
good
night,
everybody
nice-
to
meet
you
all
for
this
g-shock
office
hour
for
the
7th
of
july,
where
we're
going
to
discuss
a
few
matters
around
the
gsoc,
the
jenkins
g-stock
program.
So
I
have
a
few
points
that
I'd
like
to
share
with
you
in
the
beginning
and
then
afterwards,
we're
going
to
do
a
round
table
to
see
the
various
projects.
A
So
first
announcement
is
that
the
gsoc
project
criterias
have
been
published
earlier
this
week,
so
high
raj,
so
they
have
been
published.
They
have
been
discussed
first
with
the
org
admins,
then,
with
the
mentors
now
they're
open
for
the
public,
and
for
you
open
for
comments.
A
If
you
have
improvements,
comments,
questions,
doubts
or
suggestion
you're
welcome
to
use
it
during
the
on
on
the
document
and
say:
if
do
you
want
to
walk
them
through?
Did
everybody
read
them
or
we
can
eventually
walk
through
them?.
A
Yeah,
okay,
I'm
going
to
do
that,
so
I'm
going
to
share
that
screen.
Okay
there.
So
does
everybody
see
my
screen
with
the
project
success
criterias.
A
A
Okay,
just
a
joke,
so
here
these
are
the
criterias
that
will
help
us
as
a
global
team,
so
mentors
and
contributors
to
evaluate
did
we
have
a
successful
google
summer
of
code
when
we
reached
september.
So
the
first
question
we're
going
to
ask
is:
do
we
have
a
functional
and
or
usable
product
artifact
feature
delivered
at
the
end
of
gsoc,
the
meaning
of
that
can
be
fine-tuned
or
or
can
be
adapted?
So
we
can
clarify
that
even
further.
A
There
can
be
good
reasons
why
the
initial
idea
didn't
work,
but
currently
I
don't
see
that
in
any
project,
so
I
leave
it
very
open
what
is
delivered,
but
we
we
need
to
have
something
at
the
end,
being
a
report,
a
description,
a
jar,
a
plug-in,
a
documentation
or
whatever.
So
there
must
be
an
outcome.
A
A
So
we
don't
want
to
see
somebody
hacking
and
working
in
this
in
a
cave
on
his
side
and
sully
pops
comes
out
and
there
has
been
no
discussion.
I
don't
see
that
at
all
for
the
four
projects
here
did
the
gsoc
contributor
learn
and
demonstrate
the
ability
to
work
in
public,
which
is
a
a
very
important
point
for
working
with
open
source.
It's
it's
a
complete
different
way
of
working
than
in
in
a
company
or
professional
environment.
So
that
means
sharing
progress,
give
ample
opportunity
for
review,
interact
with
the
community
etc.
A
Did
the
gsoc
contributor
learn
and
demonstrate
adequate
communication
skills
so
written
verbal?
So
we'll
have
some
presentations
work
interactions.
So
this
is
another
important
skill
that
we
want
to.
A
To
have
the
contributors
getting
proficient,
and
this
is
the
purpose
of
the
learning
process
now
per
project
you
can
define
other
criterias.
I
just
want
to
emphasize
that
this
is
not
a
university
exam.
A
This
is
not
a
death
march
it
well.
I
made
my
military
service,
so
I
know
what
that
means,
so
that
cost
what
it
costs.
Even
if
you
need
to
crawl,
you
absolutely
must
reach
it.
This
is
not
the
purpose.
The
purpose
is
to
have
an
enjoyable
experience,
to
learn
things
and
especially
learn
to
work
together.
A
A
Okay,
next
point
is
we're
going
to
reach
an
important
milestone
for
you,
but
I
know
it's
intimidating,
but
it's
part
of
the
learning
process
so
we're
going
to
hold
the
jenkins
online
meetup
on
the
21st
of
july
at
this
time
here.
Thank
you
for
alyssa
to
have
organized
the
meetup,
so
it's
announced
now.
It
has
been
announced
also
on
the
various
social
media.
A
Don't
forget
to
register
to
it,
because
you
will
receive
the
link
only
once
you
have
registered.
We
can
walk
through
that
afterwards,
but
I'll
send
a
link
to
the
meetup
page
or.
A
Yeah,
okay,
thank
you
very
much
for
that.
Alyssa
yeah.
So
just
a
reminder:
it's
a
15-minute
presentation
where-
and
you
can
use
slides
slides-
are
a
good,
a
good
way
to
do
that.
Where
you
explain
to
the
crowd,
I
don't
know
how
many
peoples
will
be
there.
So
don't
get
scared
about
that.
A
What
the
purpose
of
your
project
is,
what
is
the
plan
for
your
project?
What
is
it
about?
Explain
it
in
simple
words:
where
are
you
standing
now
in
this
idea
in
this
project?
Where
are
you?
What
are
the
difficulties
you're
facing?
What
are
the
challenges
you're
facing?
What
did
you
already
achieve?
So
you
tell
the
story.
This
is
where
we
are
bragging
is
allowed
and
encouraged,
because
you
all
did
tremendous
work
and
you
achieved
good
results
up
to
now.
A
If
you
have
the
the
possibility,
but
don't
don't
fret
fret
out,
if,
if
you
don't
have,
have
it
ready
but
having
a
demo,
something
to
show
helps
people
to
understand
what
you
did.
What
the
aim
of
the
project.
A
A
good
way
to
do
it
is
to
use
either
zoom
or
whatever
conferencing
system
that
you
used
to,
and
you
record
yourself
doing
that
and
you
go
a
couple
of
times
through
the
presentation
and
that
way
you
will
first
know.
Are
you
able
to
explain
everything
that
you
want
to
to
to
tell
the
the
people
in
the
allocated
15
minutes?
A
I
can
tell
you
it's
hard
to
keep
it
in
the
15
minutes,
so
rehearse
it
and
you
will
feel
much
much
better,
especially
if
english
is
not
your
your
native
language.
A
A
A
Next
point:
I've
seen
a
lot
of
very
enthusiastic,
dedicated
people
working
on
gsoc,
very
proud
and
honored
to
have
been
selected
in
gsoc
and
putting
a
huge
amount
of
energy,
meaning
that
I
see
messages
very
early
in
your
time
zone
and
very
late,
so
you're
you're
you're.
I
I
fear
somewhere
and
I'm
speaking
here
as
a
grand,
a
father
grandfather.
A
A
So
it's
a
a
one-time
experience,
it's
a
great
experience,
but
nobody
will
win
if
you
burn
out
on
it,
so
just
to
clarify
the
expectations.
A
The
contract
moral
contract
is
that
during
the
coding
period,
the
project
is
estimated
at
175
hours
for
12
week.
That
makes
about
15
hours
per
week
that
you
can
arrange.
A
Now
this
is
the
the
goal.
I
can
really
understand
that
you
want
to
explore
things
that
you're
taking
more
time
you
get
into
trouble,
see
it
doesn't
work
that
you're
spending
more
time,
I'm
doing
exactly
the
same.
So
this
is
why
I
allow
myself
to
give
you
this.
This
advice
is
be
careful,
it's
fun
it's
great,
but
keep
the
balance
so
learn
to
hook
off.
A
Is
it
necessary
to
go
during
the
weekend
on
it
at
a
certain
moment,
you
need
to
shut
off
if
you
feel
the
necessity-
and
I
had
this
discussion
with
one
of
you-
the
the
here
I
want
to
to
think-
or
I
have
personal
things
that
I'd
like
to
to
sort
out
it's
perfectly
okay
to
say
here.
I
need
to
take
a
good
breath.
A
I
want
to
go.
I
don't
know
I
want
to
go
to
my
parents
or
or
this
or
that
to
have
a
break.
So
I
I
insist
on
that
yeah
and
the
last
thing
that
very
often
especially
learning
now
you're
in
the
generation
that
was
born
with
that,
but
slack
getter
mails
are
asynchronous.
A
Communication
means
that
means
it
does
not
require
an
immediate
reply.
Read
it
at
certain
times
when,
when
you
allocate
it,
it
does
not
require
an
immediate
reply.
I
don't
expect
also
an
immediate
reply,
so
I
sound
maybe
a
little
bit
too
advising.
I
feel
it's
my
my
role
to
to
give
you
that
advice,
because
I've
seen
a
huge
amount
of
super
dedication.
I
see
very
enthusiastic
young
people.
A
D
I
think
it's
it's
good
word
of
advice
and
I
suggest
our
con
our
young
contributors
take
take
that
in
because
it's
it's
important
we
want
to.
We
want
you
to
be
successful.
We
want
you
to
be
happy,
and
you
know
we
want
you
to
have
a
life
as
well.
A
Here
now
this
was
a
long
long
introduction.
I'm
sorry,
but
I
I
wanted
to
share
that
with
you:
let's
go
around
the
various
projects,
so
let's
go
diraj
how's
the
plugin
health
going.
E
So
in
the
previous
week
we
worked
on
mostly
some
of
the
enhancement
tasks
and
there
were
some
bug
and
core
related
or
chore
related
prs
as
well,
so
to
quickly
tell
you
what
we
worked
on.
First
of
all,
we
had
some
problems
in
generating
the
reports
on
our
ci
configuration,
so
adrian
helped
us
in
that.
E
So
he
opened
a
pr
and
corrected
everything,
and
now
it
works
very
well
and
there's
reports
generating
as
well
after
that
there
was
one
announcement,
pr
that
I
submitted
to
to
simplify
what
was
going
on
in
the
project,
and
there
are
two
tasks
in
progress
right
now
and
they're
like
it's
like
we're
in
that
zone,
where
we
are
going
to
climb
the
hill
like
the
main
task,
that's
going
to
come
up
in
near
week,
so
that
is
in
progress
right
now.
That
is
adding
a
json
object
inside
our
database.
E
A
So
I
think
you're
really
in
the
middle
of
it.
Now,
yes,
okay!
Good!
Thank
you
jenkins
file,
runner
action
for
github
gaming.
Can
you
tell
us
a
little
bit
where
we're
standing.
F
Okay,
so
so
last
week
I
did
three
things
manually,
so,
firstly,
I
submitted
a
program
pull
request
about
the
method
of
how
to
package
the
maven
binaries
and
the
additional
plugins.
So
now
it
is
based
on
the
cash
action.
You
can
see
it
in
the
pro
request,
but
some
actual
implementations
needed
to
be
published
or
changed
after
the
weekly
discussion,
because
they
are
not
good
enough
to
be
a
feature
also.
F
It
is
only
my
personal
idea
and
secondly,
I
submitted
a
poor
request
about
how
to
create
a
japanese
file
around
their
image
that
bundles
new
or
jacking
score
so
and-
and
I
think
I
don't
need
to-
I
think
this
pro
request
does
not
be
needed
at
all,
because
the
jackings
file
runner
project
all
lag
well,
helps
me
to
release
a
new
version
with
a
newer
jacking
score
in
jackings
file,
runner
upstream
project
project.
F
A
Good,
just
a
point:
don't
hesitate
to
propose
enhancements
upstream
or
to
help
oleg
in
in
things,
because
oleg
has
a
very
tight
schedule.
So
don't
hesitate,
but
I
don't
know
enough
there
so
and
and
discuss
that
with
the
with
your
mentors
to
move
ahead
with
with
that.
E
Hello,
so
this
week
I
worked.
I
and
mr
I
mark
russia.
We
all
worked
on
setting
up
the
ssh.
You
know
so
that
I
could
connect
with
mark's
machine
and
run
the
git.
You
know
and
check
whether
which
gate
get
the
version
supports,
which
get
maintenance
tasks
that
we
have
done
a
detailed
analysis
on
that
and
come
up
with
the
results.
E
Also,
I
tried
fixing
few
logical
errors,
which
were
there
in
the
code.
So
there
were
like
one
two
errors.
I
tried
fixing
those
that
that's
it.
That
was
what
I've
done
this
week
I'll
this
so
I'll,
be
adding
so
this
week
I'll
be
adding
how
you
know
how
to
add
legacy,
get
maintenance
into
gen.
You
know
the
git
plugin
so
yeah,
that's
it.
A
So
the
last
point
was
adding
legacy:
get
maintenance.
G
H
Hey
everyone
we've
been
working
together,
yeah.
So,
first
of
all
I
would
like
to
thank
thank
you
a
lot
so
for
getting
the
release
done.
So
that
was
one
of
the
biggest
checklist
for
the
week,
so
I
checked
it
and
the
artifactory
shows
are
released
well
and
good
and
also
try
to
include
it
as
a
dependency
and
everything
is
working
great
and
on
my
side
this
week
was
like
a
pr
week
for
me.
H
So
yesterday
itself,
if
I
counted
correctly,
I
guess
five
prs
were
merged
so
and
the
few
things
that
were
done
was
adding
search
on
pipeline
steps
reference.
So
this
was
a
follow-up
to
the
plugin
list
that
was
not
merged,
so
maybe
some
sort
of
a
modification
of
that
and
getting
the
source
ready.
So
it's
merged
and
it's
working
on
the
website
now.
So
that
was
the
first
thing
that
was
done
after
that
we,
the
data
type
parameter
list,
so
that
has
also
that
will
request
in
pipeline
step.
Docs
has
also
been
merged.
H
So
now
we
can
see
the
updated
versions
on
the
website
itself,
so
everything
has
gone
into
build
after
that,
the
updation
of
the
majority
was
complete
as
we
did
together
and
so
for
those
who
don't
know,
we
have
updated
the
repository
to
support
the
plugin
manager
that
is
required
by
the
stepdoc
generator
repository
and
the
reason
that
we
separated
that
artifact
from
the
main
repository
was
in
the
future,
some
others.
Other
projects
can
also
use
us
use
that
as
an
artifact.
H
Extractor
and
we'll
just
write
some
test
queries
to
see
the
results
are
matching
them
or
not.
So
those
would
be
the
tests
overview
as
of
now
so
once
that
is
done,
we
can
set
up
the
next
cycle.
I
guess
so
yeah.
A
Okay,
good,
I
worked
together
with
vihan.
I
I
had
the
the
pleasure
because
I
don't
get
the
opportunity
that
much
anymore,
but
to
do
some
technical
stuff
and
help
for
the
release,
something
that
we
observed
and
that
might
be
a
general
interest.
The
teacher
again
a
reminder
for
everybody.
Is
you
bump
in
a
problem?
A
And
here
in
this
case
we
we
had
a
problem
in
the
generation
of
the
javadoc.
There
were
some
illegal
parameters.
A
A
The
immediate
thing
that
you
need
to
trigger
is:
what
do
I
need
to
add
so
that
that
error
gets
caught
the
the
next
time
during
the
ci,
so
adding
integration
tests,
adding
unit
tests
adding
the
goal
to
the
build
command?
A
In
this
case,
I
founded
a
very
interesting
experience
here
and
I
wanted
to
share
that
to
the
group.
Okay,
we're
running
out
of
time.
I'd
like
to
give
the
word
to
jake
chris
and
alyssa
is
one
of
does
one
of
you
three
want
to
ask,
say
or
comment
on
anything
that
was
said.