►
From YouTube: GSoC Office Hours. Jun 19, 2019
Description
Meeting notes: https://docs.google.com/document/d/1H0gJt1zdr37YDpuSLXSeFqYco_a_CIrAuZ1f0Oyl4XE/edit?usp=sharing
A
Okay,
yeah
now
it's
being
recorded
and
again
I
see
the
message
it's
going
to
be
deprecated,
so
yeah
today
is
June
19th.
We
have
a
leg
about
a
google
Summer
of
Code
submitting.
This
is
just
yet
only
several
days
of
Kodiak
left
until
the
first
evaluation
phase
stops.
We
have
several
people
on
the
call,
and
my
proposal
would
be
to
just
talk
again
about
what's
going
to
happen
during
a
variation
and
maybe
answer
questions
from
students
before
we
press
it
views
other
topics.
The
farm
is
your
base.
C
A
Yes,
oh
yeah,
all
students
and
all
mentors
should
have
already
received
emails
from
Google
about
the
first
affiliations.
Basically,
it's
what
is
written
there
and
he
needs
to
read
them,
and
in
addition
to
that,
like
we
discussed
in
the
previous
course,
we
have
Jenkins
I'll,
see
you
then
yes
should
be
somewhere
here.
Students
here
we
have
variations
which
all
define
our
expectations
for
the
evaluation
period.
A
Okay,
you,
regarding
the
rest,
we
had
voting
for
meetings,
so
there
are
two
slots
you
should
have
been
selected.
I've
sent
the
information
about
what
my
nucleus,
but
basically
all
the
students
expected
to
prepare
oedema
by
this
meeting.
So
what
we
expected
with
these
demos.
First,
we
think
you
delivered.
We
expect
you
to
show
it
to
potential
users
and
petition
stakeholders
and.
A
A
A
Here
you
can
see,
for
example,
phase
3
presentation,
slice
and
pastry
presentation,
demos,
so
yeah,
basically
independently
of
the
face.
It's
the
format
we
recommend
to
follow
so
just
shot
a
self
introduction
short
introduction
of
the
project
which
you
would
like
to
focus
on
and
some
details
about.
The
project
you're
presenting
and
yet
the
most
of
the
time
in
basic,
goes
to
live
demo
so
presenting
what
you've
done,
how
it
works
and
then
just
summarizing
the
status
against
the
plan
and
maybe
adding
some
additional
details.
A
If
you
want
the
most
of
the
time,
it
will
be
demo
and
it
will
be
discussion,
so
be
ready
that
other
participants
on
the
meeting
will
be
asking
questions
and
you
focus
on
the
user
to
visible
features,
because,
basically,
you
present
in
your
work
to
potential
consumers
not
only
to
other
contributors.
So
you
can
find
examples
here.
You
can
just
take
another
demo
because
you
have
plenty
of
them
in
from
jisub
project
pages,
so
just
take
whatever
you
want
and
use
it
as
a
guideline
and
of
course
you
have
Mentors.
A
So
if
you
start
preparing
a
presentation
in
advance,
you
can
talk
to
Mentors,
so
the
mentors
can
review
your
presentation
and
it
provides
some
feedback.
It's
also
something
which
usually
happens
before
the
demons.
Además
image
happen
without
dry
run
without
review
by
mentors.
Usually
don't
go
well,
so
the
recommendation
is
to
spend
some
time
to
prepare
to
that,
so
that
you
are
ready
to
present
when
the
meeting
starts.
A
A
So
yeah
he
basically
just
prepare,
determines
and
the
work
you
team
enters
to
get
to
them
tribute.
So
this
they
must
won't
be
much
formal.
So
we
just
present
the
stuff.
The
most
of
the
participants
will
be
Jenkins
developers,
so
it
won't
be
online
meetup.
For
now
you
will
just
have
sessions
in
there
gently
develop
at
least
with
maybe
some
sign
ups,
but
still
it's
something
which
is
really
important.