►
From YouTube: GSoC Weekly Meeting (Feb 13, 2019)
Description
Meeting notes: https://docs.google.com/document/d/1H0gJt1zdr37YDpuSLXSeFqYco_a_CIrAuZ1f0Oyl4XE/edit#heading=h.6zwekq9jal39
A
B
B
B
B
It's
not
captured
in
the
meeting
tones
what
we
also
had
two
action
items
on
me:
one
was
create
internal
Google,
Doc
commenters,
so
that
we
can
share
information
about
students.
It
hasn't
been
completed
yet
and
click
Michelle
the
same
with
scheduling
internal
mental
meetings.
Let's
try
to
do
something
starting
from
next
week,
I'll
Center,
the
video
today.
B
C
C
B
A
B
B
Yeah
so
I
just
decided
to
change
it
at
some
point,
because
project
idea
is
what
we
actually
propose
to
students.
We
don't
propose
projects
per
se.
That's
why
edited
that?
But
I,
don't
think
that
it's
important
change
so
yeah.
It
makes
some
sense,
but
there
is
no
need
to
go
and
modify
all
published
projects.
Okay,.
B
There
is
to
some
action
items
only
from
previous
once
some
updates
I
have
been
a
scientist,
be
different,
didn't
it,
which
is
so
great
about
JSON
budgeting,
a
long
story
shot
yeah
it's
finite
to
do
whatever
budget
inconvenient
right
now,
but
in
the
long
term,
the
recent
discussion
about
changes
project
the
journey
inclusion
in
the
division
foundation.
If
it
happens,
we
will
need
to
revisit
at
least
Jeff
to
adjust
to
a
new
expense
photos
and
a
little
bit.
B
A
A
B
B
A
B
A
B
So
now
we
have
five
project
IDs
in
the
draft
state
in
search
the
factory
freestyle
job
to
pipeline
job
converter
pipelines
that
the
documentation
generator
I
believe
this
is
only
you
and
Christine
and
also
drink
is
remotely
monitored,
and
we
wish
we
need
to
discuss
with
a
wood
on
the
general
died
with
children.
Given
the
changes
they
proposed
and
yeah.
It
also
had
a
project
idea
for
coverage
which
we
haven't
published,
but
if
we
do
all
of
them,
we
are
getting
to
27
project
a
baby's
favicon
correctly.
A
A
D
B
By
planning
interact
series
source
control
management
system,
with
poles,
the
repository
and
for
branches
for
pool
requests,
if
able
to
create
branches
automatically
and
to
get
rank
automatically,
and
it
has
some
retention
strategies
from
an
example
one
they
pull
request
is
immersed.
It
can
close
to
the
branch
for
this
protocol
and
yeah.
It
also
has
all
kinds
of
history
management,
so
the
biggest
problem
for
multi
branch
and,
for
example,
we
need
experience,
faith
and
the
agent
inside
all
many
times
that
it
may
consume
a
lot
of
space
diversity.
B
A
A
B
B
B
Yes,
okay,
so
yeah,
let's
take
three
with
Rumple
Oh
drinking,
sherry
Jenkins,
it's
our
link,
it's
called
and
we
have
multi
branch
country,
but
for
this
repository
so
for
example,
if
I
click
here
you
may
see
that
there
is
some
automation
happening
there.
This
automation,
no
one,
is
powered
by
Jenkins.
B
B
Okay,
it's
blown
it
downloads,
a
lot
of
JavaScript
stuff.
So
you
may
be
that
that
is
the
number
of
steps
executed.
But
you
see
that
actually,
this
is
for
one
to
seven
Oh
wishes
or
poor
request
number.
If
we
just
go
to
the
coda
job
here,
you
may
see
that
yeah
there
is
a
kind
of
dashboard
here.
You
may
see
the
there
are
multiple
branches
and
here
in
the
web
interface.
You
may
also
see
that
there
are
branches
and
pull
requests.
B
B
B
So
he
seems
it
doesn't
work
in
such
way.
Ok
I
really
have
always
oh
an
option
to
show
across
again
his
joy.
So
we
have
now
it's
probably
less
fancy,
but
it
does
the
job.
So
if
you
open
any
branch
here,
you
may
see
that
there
is
a
number
of
commits
or
a
Suriname
war.
He
builds
so
for
branch.
Javits
and
support
we
lost
built
was
the
same
time
a
twinkie.
B
You
may
see
that
there
are
four
bills
and
for
these
four
bills
actually
contain
attached
arthropods,
and
you
may
see
that
yeah
they
consumed
some
disk
space.
So,
for
example,
James
Purefoy
consume
70
megabytes
it's
about
100
in
total,
for
the
bill,
and
here
we
have
four
hundred
gigabyte
four
hundred
megabytes
just
for
this
branch,
which
has
been
actually
lost
in
September
and
most
likely,
nobody
needs
that,
and
this
is
the
problem
for
edging.
It
say.
Oh
because
yeah,
when
we
have
so
many
branches,
actually
it
means
that
we
consume
a
lot
of
disk
space.
B
B
B
So
you
may
see
that
extension
points
can
read:
Christie
risk
environment
variables,
so
this
pull
request
has
been
created
by
our
level
in
2014.
In
still
our
chip
and
the
yeah.
You
may
see
that
for
this
pull
request,
we
have
restored
more
than
20
bills.
So
it's
about
2
gigabytes,
just
for
this
bench,
and
this
is
active
so
yep,
you
know
it's
a
separate
bill
history
and
for
each
branch
yep.
You
could
use
current
to
discard
project
to
discard
so
on
a
single
branch.
But
again
it's
not
clear
by
AB
is
built.
B
So
I
would
need
to
show
configuration.
Unfortunately,
I
have
no
access
to
this
instance,
but
multiplying
so
here,
malcontent
she's
configured
on
this
level,
so
it's
a
github
organization
and
the
or
server
is
not
as
organized
a
ssin.
It's
multi
branch
project
in
this
case
and
you
can
set
up
different
return
policies
for
branches.
So,
for
example,
when
you
merge
the
branch
you
can
configure
Jenkins
to
automatically
inaudible
history
or
you
can
configure
it
to
delete
the
history
after
particular
time,
if
I
recall
correctly,
but
there
is
not
that
much
flexibility
about
that.
A
B
B
A
B
A
D
B
D
B
So
from
advanced
do
discover
the
plugin
standpoint.
It
would
be
just
extension
point
implementation
for
multi
branch
which
integrates
somehow
this
advanced.
You
just
call
the
like
in
logic
itself,
so
you
have
your
own
logic
and
due
to
by
documentation,
you
can
integrate
with
this
logic,
is
multiplying
Python.
D
Yes,
so,
like
we
just
define
now,
you
know
know
what
our
own
logic
that,
how
we
want
to
describe
the
bills
and
add
what
conditions
to
be
scarred,
so
it
so
like
just
defining
it
as
extensions
when
you
administer,
but
like
a
propelling
a
flow
art
of
a
painting.
You
know
logic
that
how
we
want
to
discard
that
bill
and
generally
how
we
want
to
deal
with
it
would
be
much
more
interesting.
A
Is
no
sorry
there
is
an
another
idea
from
Thurston
which
is
he
what's
the
ability
to
mark
the
build
from
inside
his
champions
filed
pipeline?
He
suggested
that
he
could
mark
the
build
with
some
Flagg
tell
ya
that
they
extended
that
the
that
the
discard
plug-in
would
be
able
to
read
and
based
on
the
value
of
this
flag,
decide
to
discard,
build
or
not,
but
I
was
not
clear.
It's
not
clear
to
me
like
I
know
the
run.
A
D
D
Then
fourth,
one
is
of
production
right
so
like,
and
there
are
some
pipeline
if
a
particular
code
is
being
pasted
in
a
particular
black
pipe
line,
then
that
name
is
fixed
for
that,
like
for
some
code
for
some
testing,
they
will
use
QA
testing
for
some
pre-production
test.
They
will
use
the
tech
pre-production,
so
we
can
just
give
a
facility
to
give
a
tag
and
based
on
that
tag
we
can
just
decide
that
which
build
we
should
keep
and
which
should
not
like.
A
D
A
D
A
D
So,
like
actually
I
was
just
looking
at
the
poor
base
of
run
selector
just
yesterday
or
two
days
before,
and
you
know
like
I,
was
just
finding
a
way
that
how
this
idea
can
be
implemented
with
or
and
this
runway
select
area.
So
you
are
right
like
just
finding
a
way
would
be
who
did
much
more
work,
and
we
don't
know
the
difficulty
like.
Sometimes
it
like,
it
would
be
easier
to
integrate
it.
It
can
be
also
like
we
just
need
some
more
time
to.
D
D
Yeah,
so
here
it
is
so
he
you
know
just
told
that
we
can
also.
We
can
also,
you
know
not
exactly
the
words
but
yeah.
We
can
also
create
a
you
know,
data
structure
in
which
there
will
be
a
a
key
and
its
value
right,
so,
like
basically
I
just
thought
it
and
I
thought
that
a
type
of
hashing
will
be
better
for
this,
so
a
key
and
a
value.
Now
what
would
be
a
key
like
which
build
has
been
deleted
like
which
bill
has
been
discarded
and
its
value
would
be.
D
A
D
A
I
think
I
understand
what
you
are
saying.
Let
me
repeat
it
to
make
sure
you
are
saying
you're
proposing
that
the
build
the
starter
would
well.
It
would
discard
the
build,
but
it
would
kind
of
put
it
aside
and
it
would
be
in
this
I
don't
know
recycling
bin,
and
if
the
user
needs
to
access
it,
we
could
it
could
be
brought
out
of
the
recycling
bin
and
back
in
the
history.
A
D
D
So
actually,
I
have
a
doubt
like
so
it's
just
a
general
doubt
like
if
we
want
to
delete
the
external
work
spaces
which
are
created
by
the
external
work,
space
lab
manager.
So,
first
of
all,
we
need
to
delete
the
beetles,
and
you
know
all
the
details
from
the
third
result
which
has
been
used
and
after
that
we
have
to
delete
sour
bill
or
first
we
have
to
delete
the
bills
which
have
been
displayed
in
Jenkins
mode
and
up
and
the
Basil's
on
the
information
they
said.
D
A
A
D
A
D
Actually,
I
got
this
query,
you
know
from
person
who
is
using
Jenkins
frequently.
So
actually
he
just
told
me
that
sometimes
what
happens
that
they
uses
this.
They
use
this
plug-in
of
external
workspace
when
I
just
write
and
the
bills
which
were
I-
and
you
know
the
bills
were
only
getting
discarded
from
Jenkins.
Only
that
external,
you
know
third-party
agent
or
the
tool
was
keeping
all
that
builds,
so
they
should
also
be
deleted
by
making
some
API
calls
all
like
that.
D
A
D
A
I,
don't
know
the
source
code,
I,
don't
know
where
these
things
happen
exactly
we
would
need.
We
would
need
to
talk
to
probably
Alexis.
Oh
my
who
is
the
author
of
the
external
workspace
manager
and
probably
Oleg
in,
like
which
we
would
have
that
we
would
need
a
discussion
with
them.
Vendemmia
right
are
in
the
details.
Yes,.
D
B
D
Was
just
looking
through
the
project
proposal
so
in
you
know
that
the
the
three
points
which
you
have
given
that
in
existing
plug-in
scenarios,
discussion
I,
think
the
second
one
is
the
one
which
we
carried
just
discussed.
The
first
was
the
first
is
pretty
clear
that
what
the
feature
yeah,
you
know
what
people
we
clever
Peter
no
need
to
be
implemented
and
that.
D
A
B
A
D
D
Yeah,
so
I
got
this
yes,
oh
yes,
so
actually
I
was
just
looking
at
the
core
of
the
operation
and
yeah.
So
I
think
this
feature
can
be
implemented.
The
way
it
is
written
here
right.
So
it's
not
an
issue
right.
The
second
point
was
just
we
discussed
that
what
exact
picture
should
be
implemented.
Was
it
true
yeah?
It
should
be
included
in
this
a
project
proposal
or
not.
D
So
we
need
to
discuss
much
more
for
this
right
yeah
for
the
third
point,
which
users
are
not
able
to
keep
bills
that
are
part
top
brands
that
lead
to
production
so
that
well
you
know
we
need
to
I.
So,
like
one
thing,
I
would
like
to
say
that
if
we
do
not,
you
know
give
some
facility
of
tagging
or
naming
called
description.
Then
there
should
be
a
way
to
find
out
that
which
stage
is
off
which
situation
like
see
here.
D
It's
written
that,
if
you
have
built
by
plans
which
contains
stage
name
like
deploy
to
taste
and
deploy
to
production,
then
we
can
just
know
that
these
stages
of
this
purpose
and
this
stages
of
this
purpose.
But
if
we
don't
have
any
clue
or
we
don't
have
any
you
know,
if
you
don't
have
any
description,
then
we
cannot
get
or
I
think
it
would
be
not
much
more
appreciated
to
discuss
that
builds,
because
we
are
not
pretty
much
sure
that
that
stages
of
test
is
for
which
purpose.
D
Actually,
this
third
point
needs
some
more
elaboration.
That's
exactly
how
we
are
going
to
approach
and
what
facility,
and
are
we
giving
some
Festa
to
do
that
to
them
to
choose
what
they
want
to
discard
like
during
some
checkboxes
that
this
is
TD's
can
be
discarded
after
some
time
or
like
that
or
I.
Think
like
we
should
give
some
some
type
of
that
feature
or
something
that
it
are.
We
need
to
define
a
specific
path
that
how
we
will
lead
to
this
role.
Amin
solve
this.
A
A
A
D
D
So,
actually,
I
would
like
to
add
a
point
into
this,
so
yeah.
Actually
he
is
right
like
and
when
I'm
you
know
just
caught
first
time
to
Jenkins
and
when
I
just
started
using
it
in
first
picking.
You
know
in
my
first
years
of
my
internship
at
that
time
when
I
started
to
build
the
pipelines
and
just
started
building
it
the
the
barrels.
What
like
we
were,
not
image
created
when
that
bill
will
get
discarded
or
for
how
much
time
it
will
be
their
industry
or
like
that.
D
So
like
we
can
add
up
feature
in
this
like
that
or,
like
you
know,
a
special
tag
or
a
special
work
for
lighted.
Like
suppose,
if
someone
attached
is
some
like,
like
suppose,
we
just
introduced
one
tag
like
special
right
and
if
someone
just
addresses
or
at
edges
that
egg
to
that
I
plan
or
to
that
bill,
then
that
bill
won't
be
discarded
until
that
egg
is
removed
from
that
pipeline
or
from
that
bill.
Otherwise,
the
other
bills.
D
A
A
D
D
So
I
think
the
existing
plugin,
the
scenarios
discussion
is
converted,
and
this
proposed
new
plugin
discussion
was
I.
Think
you
know
like
like
almost
clear
to
me
that,
on
what
basis
and
on
what
conditions
and
on
what
filters
we
are
going
to
discard-
or
we
are
going
to
indicate
views
to
discard
so
I
think
it
was
pretty
clear
and
straightforward
right
and
the
possible
implement.
Like
the
you
know,
the
examples
were
I
am
also
clear.
So
now,
I
think
I
have
one
doubting
QuickStart
like
is
not
in
QuickStart,
but
I
have
one
doubt
like.
D
D
Then
this
permalink
run
selector
and
some
of
the
other
run.
Selectors
are
only
useful,
so
I
think
only
so
like
I
just
want
to
suggest
instead,
which
filters
of
which
Java
files
specifically
should
I
focus
to
you
know,
get
your
school
or
like
know.
Some
word
that
later,
like
gonna,
get
useful
to
the
poor
base
of
this
yeah.
A
A
Implementations
in
the
run
selector
to
cover
the
other
cases
that
that
we
are
discovering
with
the
the
advanced
discard
advanced
this
car
build.
So
maybe
the
the
the
the
answer
needs
to
be
created
here.
I
would
like,
because
there's
only
a
few
minutes
left
and
I
see
that
our
knob
is
still
on
the
call,
so
I
wanted
to
know
if
I
wanted
to
give
him
the
opportunity
to
work
to
talk.
If
he
has
something
to
say.
A
C
Well,
not
much
to
add
from
my
side,
I
think,
I.
Think
from
what
I'm
understanding
this
are
you
staking
quite
good
initiative,
I
think
in
the
project
he's
trying
to
understand
the
project?
So,
yes,
so
nothing
to
add.
Actually
I
I,
myself,
I
learned
quite
a
few
new
things
or
this
project
between
your
discussion
on
this
discussion
and
this
alga
I.
Think
if
you
have
any
doubts
you
can
like
like
Martin
said:
if
there
are
any
doubts
related
to
the
codebase,
you
can
maybe
frame
the
questions
on
guitar,
then
oleg
or
the
others.
C
D
We
are
so
only
just
last
question
like
you
like,
actually
what
I
only
one
problem
which
I
am
facing
right
now
in
studying
that
like
here,
it's
mentioned
that
contribute
to
existing
related
plugins
run,
select
all
right.
So
in
quick
start,
the
statement
is
this
so
when,
like
not
me
like,
if
any
of
the
student
opens,
that
Pervez
and
all
that,
so
it's
a
huge
structure
to
get
understand
and
all
that.
So
if
in
quick
start
that,
if
more
description
can
be
added
or
more
newbie
friendly
issues
are
added
which
are
useful
to
this.
D
A
I,
don't
I
don't
have
this
they're
issues
that
are
listed?
There
are
the
ones
that
we
have
in
sometimes
there's
no
newbie
friendly
issues,
because
people
do
not.
Users
do
not
take
the
time
to
create
issues
for
their
problems.
They
just
go
on
the
mailing
list
and
they
talk
about
the
problem.
So
oftentimes
there's
no
issues
with
regards
to
the
build
discard
plug-in.
If
you
allow
me
to
share
my
screen
one
last
time.
D
A
A
I
thought
I
listed.
It.