►
From YouTube: GSoC 2019 in Jenkins. Retrospective. Part 1
Description
Recording of the public GSoC 219 retrospective meeting in the Jenkins project. Retrospective document: https://docs.google.com/document/d/1qWeuQzMr1lGQUuirgorODwvqEXYH7RiyKkRByIed9co/edit?usp=sharing
A
Okay,
it's
been
recorded
so
hi.
Everyone
today
is
August
28.
We
have
a
retrospective
meeting
for
google
Summer
of
Code,
solid
banking.
We
had
some
sensations
over
past
week,
thanks
again
to
all
students
and
inventors
and
orchid
means
to
someone.
Thank
him.
The
purpose
of
this
meeting
is
to
talk
about
what
one,
what
went
well
and
what
didn't
go
so
well
and
discuss
possible
items.
So
basically,
it's
a
formal,
informal
discussion
about
what
were
the
issues
in
the
project
and
how
to
improve
them.
A
A
So
yeah
I'll
probably
turn
off
a
little
child
because
it
becomes
a
bit
noisy
okay.
So
we
have
a
retrospective
document
where
everybody
is
welcome
to
put
his
or
her
feedback
so
without
Russia
that
we
just
collect
this
feedback
at
this
meeting.
We
will
have
another
meeting
next
week
also
to
talk
about
people
and
comments
and
then
orchid
means
will
process.
All
the
information
probably
will
reach
out
to
our
students
and
mentors
to
gather
more
comments,
and
then
we
will
aggregate
all
the
information
and
action
a
list
of
action
items
for
the
next
year.
A
So
if
you're,
not
fine
about
change
your
feedback
in
public
in
such
way
just
feel
free
to
send
your
feedback
to
orchid
means
if
you
are
not
comfortable
about
sending.
That
means
just
because,
for
example,
if
one
of
the
members
is
enough,
good
mean
also
feel
free
to
just
send
personal
feedback
to
one
of
other
members.
So
the
author
means
and
then
we
will
process
them
at
the
orchid
min
meetings
and
I
more
privately
any
questions
before
we
proceed
any
comments.
A
A
A
A
For
example,
jack
you
you,
maybe
you
of
you
they're,
not
sure
whether
we
have
other
students
on
the
call.
We
have
a
rich,
a
on
the
call
but
parish
a
provided,
useful
back
just
a
in
the
bottom.
Otherwise
even
cannot
the
document.
So
again
we
will
spend
some
time
to
create
it
and
push
to
the
main
dog.
A
C
A
Well,
yeah
and
listen
that
there
is
a
lot
of
confusion.
Probably
this
document
will
be
pretty
long
and
sure
with
respect
to
feedback
from
2018
it
was
five
or
six
pages
and
then
yeah,
we'll
just
read
it
after
printing
in
the
plane
and
I.
Think
it's
fine.
So
now
or
that
means
we'll
softer
this
bed
drop
it
yeah.
Maybe
next
year
we
should
use
something
like
the
trailer
feed,
both
or
whatever
toward
baby
dated
birth
or
maybe
a
specialized
science
but
yeah.
You
have
to
be
seen.
A
A
So
I
think
we
should
just
stop
going
through
the
feedback,
maybe
through
the
which
will
be
improved
part.
So
yeah
I'm,
just
looking
at
the
feedback-
and
it
looks
like
the
coding
period-
is
probably
the
most
big
part
in
terms
of
feedback.
There
are
not
so
many
items,
so
probably
we
should
start
from
there.
A
It's
a
what
should
we
improve
so
zoom
usage?
It's
a
feedback
from
a
bigger
because
yeah
just
interpret
it.
We
had
online
meetups
and
broadcasts,
but
basically
we
got
less
people
in
zoom.
Then
we
used
to
making
hangouts
on
air
and
one
of
the
reasons
that
there
is
no
need
to
broadcast
so
that
we
do
not
get
subscribers
of
the
changes
channel.
It's
pretty
speaking,
but
yeah
I'm
not
sure
what
we
could
do
about
it.
H
A
Student
applicants
from
China,
and
so
when
we
could
hang
out
near
the
meetings
in
the
beginning
of
the
year,
that
was
mainly
replaced
not
to
use
and
also
here
initially,
we
have
no
other
ways
now.
So
why
not?
So
if
we
could
explore
this
option
to
stop
streams,
maybe
we
could
work
around
the
issues
via
outreach,
but
I'm
not
sure
whether
it's
all
the
feedback
we
had
to
be
there
and
maybe
I'm
missing
something.
F
A
A
A
A
E
A
I
I
So
we
tried
doing
that
at
work
for
the
same
reason
and
it
didn't
work
well,
maybe
maybe
it
would
work
for
this.
The
problem
that
we
had
is
that
we
worked
across
a
lot
of
repos,
and
so
we
ended
up
having
to
create
a
special
repo
just
for
tracking
the
issues,
and
it
was
just
it
was
hard
to
get
a
sense
for
what
work
was
outstanding
and
there's
it's
it's
not
nearly
as
functional
as
JIRA.
I
A
So
you
can
see
that
there
are
linked
repositories,
another
one
to
show
that
you
can
basically
manage
permissions
for
this
project
inside.
So,
if
you
have
a
project
within
the
repository,
you
have
no
way
to
it
teams
to
the
project,
but
they,
if
you
use
organization
level,
projectors
what
you
can
add
teams
and,
for
example,
people
will
be
able
to
manage
but
not
ideal
solution,
but
it
kinda
works.
I.
H
A
To
a
structure
to
mislead
you,
whether
I
worry
about
it,
so
why
it's
slow,
sometimes
I,
think
this
project
now
uses
GT,
which
is
hosted.
Well,
basically,
it's
self
hosted,
so
we
don't
use
that
lesson
cloud
for
it
and
has
no
scalability,
sometimes
their
performance
issues.
Sometimes
that
is
just
memory,
degradation
and
yeah.
There
is
a
long
extended
friction
I
can
relate
somewhere,
but
yeah.
There
are
high
cloud
projects
right
now.
A
A
G
C
I
find
it
quite
okay,
there
were
some
times
the
server
was
inaccessible,
but
generally
it
was,
and
it
was
fine.
I
didn't
have
this
any
ship
it
slow
and
like
that
one
issue
I
had
was
like
every
time
there
was
a
genetical
we'd.
Never
had
our
conversation
on
that
like
on
github
issues
you
used
to.
It
was
generally
on
the
pull
request
that
the
thread
static.
So
so,
basically
it
was
nice
that
they
were
options
to
configure
your
zero
ticket,
but
there
were
no
discussions
on
the
tickets.
E
Think
well,
I
think
what
we
can
do
for
that
prachi
is
an
action
item
could
be
is,
is
during
the
onboarding
of
a
google
Summer
of
Code
students.
During
the
bonding
phase,
we
can
I
think
as
org
admins.
We
can
sort
of
design
a
better
flow,
so
the
students
are
aware
of
what
the
flow
is
ahead
of
time
and
I.
Think
that
was
I.
Think
that's
what
you're
describing
please
correct
me.
If
I'm
not.
C
A
C
C
E
I
think
it's
up
to
the
mentors
to
to
set
that
to
set
that
tone
with
the
during
the
bonding
phase
and
I
think
so
what
I
think
the
action
item
is
on
the
org
admins
to
create
sort
of
a
checklist
during
the
bonding
face
for
mentors
to
follow,
and
one
of
the
items
in
that
checklist
should
be.
We
need
to
discuss
what
the
flow
is
going
to
look
like
for
our
given
project,
not
for
overall,
but
just
a
given
students,
project.
A
G
G
Actually
Catherine
another
thing
about
the
kind
of
points
for
jira
sure
so
I
think
using
is
a
kind
of
like
another
positive
thing
about
using
like
JIRA
like
having
conversations.
There
is
part
of
the
like
post,
google
Summer
of
Code
when
we're
trying
to
encourage
the
community
to
maybe
like
look
at
this
or
adopt
it
and
have
more
usage.
It
shows,
like
all
the
thought
that
went
into
the
ticket
or
kind
of
like
ideas.
J
A
Okay,
mental
commitment
so
yeah.
This
is
probably
a
painful
topic
because
they
even
put
it
at
least
few
projects,
and
actually
it's
not
the
first
year
we
had
a
decision
and
it's
not
only
about
the
coding
trees.
So
how
the
process
work
this
year
is
that
during
the
project
selection,
we
asked
all
mentors
to
commit
to
at
least
five
hours
per
week,
because
a
we
lost
few
mentors
in
previous
years
and
the
idea
was
that,
if
mentors
explicitly
come
into
them,
it
will
be
better
but
yeah.
A
Of
course,
life
happens
so
in
the
case
of
some
metals
are
going
to
expect
it
events
which
prevented
them
from
participating
in
G,
so
corrupt
ones,
but
still
it
wasn't
evil.
So
some
mental
unfortunately
disappears
and
yeah
is
how
action
item
we
already
have
a
kind
of
blacklist
for
hundreds.
We
will
be
expanding
that
without
mentioning
names
right
now,
but
still
eating,
but
that
the
projects
significantly
and
apologies
for
that
so
I
thought.
That
means
we
got
involved
in
a
few
projects
during
phase
one,
but
mainly
it
was
pretty
late
for
some
projects.
A
There
is
definitely
something
to
improve,
but
it
would
be
really
nice
to
get
student
feedback
because
it
basically
it's
not
only
active
projects,
it
inputs,
other
students
who
applied
and
selected
because
other
mentors
committed
and
then
maybe
didn't,
work
well
yeah.
In
some
cases
we
had
great
mentor
teams,
but
we
set
project
sort
of
so
yeah.
It
would
be
really
great
to
ensure
that
this
amount
of
teams,
the
Alliant
and
them
can
execute
on
projects,
even
if
there
are
some
initial
translations.
A
K
Like
if
I
might
me,
I
think
I
may
be
one
of
those
mentors
you're
talking
about
I,
know
agreed
early
on
were
quite
involved
in
terms
to
you
know.
Trying
to
you
know,
find
students
for
our
project
and
so
on,
but
once
the
project
was
not
selected,
I
I
didn't
realize
it
was
an
option
to
sort
of
continue
on
with
with
other
projects.
K
A
So
yeah
maybe
taught
this
someone,
this
feedback
for
selection
projects,
so
what
I'm?
Actually
working
on
for
selection
Mary
is
one
B
for
not
accepted
projects
and
be
accepted
projects.
So
if
you
follow
my
office
and
outreach
special
interest
group,
what
we
introduced,
the
reason
we
have
coming
into
breach
and.
A
So
we
start
that
one
project
here
by
slide
and
he
was
presented
presented
on
Monday
it's
for
cheaper
developers
tools,
but
the
plan
is
to
keep
expanding
and
accident
an
action
item
to
reach
out
to
you
or
honest
actually.
So
it's
one
of
the
mitigations
we
plan
for
not
accepted
projects,
but
in
need
having
clear
way
for
matters
to
join
other
projects
with
also
help.
K
K
I
think
you
know,
the
early
formation
of
of
mentor
teams
is
is
important
as
use
you
know,
you're
finding
out.
There
is
a
lot
of
charm
and
a
lot
of
people.
You
know
life
catches
up
with
them
during
this
summer,
especially
I'm
wondering
if
we
could
sort
of
have
a
pool
of
sort
of
backup
letters
that
you
know
they
would
be
available.
If
you
know
some
projects
news
mentors
and
then
you
know
those
people
are
available
to
sort
of
come
in
and
help
ad
hoc.
A
It
would
be
different,
very
nice,
so
main
problem
was
that
many
projects
are
just
quite
specific
and
we,
although
we
did
some
effort
to
find
backup
minders,
it
didn't
always
work.
So
in
2018
we
had
cases
where
we
needed
to
add
mentors.
In
2019
year
there
were
some
pieces
as
well
so
yeah.
If
were
there,
are
people
who
are
ready
to
get
back
up
matters?
It's
perfectly
fine,
but
yeah
operation
this
year
was
actually
stuff
from
many
mentors.
A
E
Another
thing
that
we're
doing
on
that
front
is
a
lot
of
us,
especially
that
we're
at
Jenkins
Worlds
I
can
say
we
were.
We
were
actively
trying
to
like
pump
people
up
and
recruiting
people
for
that.
I
think
that
worked
did
I,
think
it
worked.
Good
I'd
have
two
people
that
you
know
out
of
a
lot
of
people
too,
that
are
remaining
in
contact
with
me
yeah
about
wanting
to
do
that.
So
I
think
it's
a
good
thing.
E
A
In
episode,
19
and
all
our
previous
Jesus
students
have
been
actually
potential
mentors
to
some
at
19,
for
example,
one
on
Alex
on
Alex,
oh
my
mentors
this
year,
so
yeah
I
think
it
worked
well.
Another
thing
we
do
in
order
to
improve
the
situation.
We
basically
start
early,
so,
for
example,
this
year
we
start
preparing
at
this
table
and
started
more
ongoing
projects
in
November
right
after
the
mentor
summit
for
2020
year.
A
But
basically
we
can
start
doing
it
right
now,
and
so
we
we
have
natural
source
of
project
ideas
from
the
previous
year,
because
for
some
projects
we
had
really
great
applications,
mentor
teams,
but
in
various
reasons
we
were
unable
to
accept
them.
So
we
can
make
sure
to
just
drag
and
drop
for
these
projects
to
the
next
year
and
have
a
basic
list
and
we
can
keep
expanding
it.
L
Are
they
not
like,
but
in
some
ways
I'd
rather
have
some
help
than
no
help
at
all,
and
so
for
for
my
project,
tim
was
not
actually
a
mentor,
but
did
a
lot
of
like
code
review,
which
is
really
helpful.
So,
even
though
he
wasn't
able
to
attend
like
any
of
our
meetings,
just
the
fact
that
he
was
able
to
like
you
know,
give
me
feedback
on
the
codes
that
I
had
written
and
how
to
do
like
some
best
practices
and
stuff
like
that.
That
was
really
helpful
for
me.
L
So,
like
I,
don't
know,
I
know
you
guys
were
saying
like
well.
It
helps
to
obviously
have
mentors
who
are
you
know
more
familiar
with
the
project
which
I
think
he
was
one
of
those
but
I
think
also
having
people
who
maybe
are
like
really
good
engineers
or
something
who
would
just
be
able
to
give
you
like
feedback
on
your
code.
I
think
it
would
also
be
helpful
too
part
of
my
goal
as
a
student
is
to
continue
to
develop
my
skills
over
the
summer
as
well.
A
Right
so
basically,
it's
also
what
we
did
for
this
year,
so
it
was
called
technical
advisors
so,
for
example,
I
and
Battiste.
We
were
technical
advisors
in
Natasha's
project,
so
yeah
this
one
so
yeah
we
listed
here
as
mentors
just
because
what
we
didn't
fix
met
at
beta,
but
in
the
spreadsheets
we
have
high
technical
advisors.
So
one
of
the
issues
here
was
that,
for
example,
in
my
case,
I
just
committed
to
too
much
things
this
year,
so
that
was
less
anger
available
than
I
wanted
to
yeah,
but
he
was
busy
with
other
things.
A
L
G
You
know
thanks
got
interested
and
then
they,
you
know,
became
very
involved,
so
it's
like,
after
they
were
able
to
see
that
the
project
would
benefit
them.
I
think
it
kind
of
has
a
lot
more
power
to
pull
people
in
so
unfortunately
that
doesn't
seem
like
it
can
even
start
to
happen
until
after
projects
are
selected
or
until
like
the
community
bonding
phase.
So
unfortunately
that
doesn't
really
help
us
pull
it
enters,
but
it
does
help
us
pull
in
people
who
are
super
interested
and
seeing
the
project
succeed.
A
Regarding
that,
when
we
were
selecting
the
project
ideas,
actually
our
focus
was
to
have
project
ideas
from
special
interest
groups
and,
and
we
were
reaching
out
to
all
these
entities,
we
were
going
through
meetings
in
order
to
propose
projects.
So
add
this
for
pretty
much
every
project
and
the
least
we
try
to
do
some
outreach
work.
Even
before
the
j-stop
officially
started.
A
We
were
going
to
platform
sneaks
a
presented
project
idea
is
facilitating
feedback,
I
wouldn't
say
we
got
too
much
out
of
it,
but
we
joined
pretty
much
every
special
interest
group
and
we
reached
out
pretty
much
every
project
and
the
idea
was
that
the
most
the
project's
somehow
binded
to
special
interest
groups,
for
example.
We
can
just
take
something
like
this
multi
branch
for
its
up
yeah.
You
can
and
see
it
on
the
page,
but
if
you
go
to
the.
A
Metadata
so
here
there
is
no
sig
marking,
but
for
many
projects
there
is
Sigma,
pink
and
a
metadata,
because
we
really
wanted
these
projects
to
be
a
part
of
special
interest
groups.
You
not
all
projects
you're,
naturally,
a
part
of
that.
So,
for
example,
a
Buda
was
working
on
rod,
strategic
performance
improvement
and
right
now
we
didn't
have
security
special
interest
group.
There
are
some
activities
to
have
it
on
the
CDF
level,
but
we
were
able
to
mitigated
own
to
platform,
seek,
for
example,
for
performance
testing
to
very
rapid
speaking
MJ
cask
sub-project.
A
K
Essentially,
we
were
spanning,
you
know,
probably
you
know
the
entire
time
zone
of
universe,
so
it
was
kind
of
hard
to
organize
meetings
and
so
on.
Is
there
any
kind
of
ideas
or
suggestions
on
how
to
improve
on
these
any
kind
of
you
know
regional,
perhaps
focused
on
teams
that
may
be
more
local
to
the
to
the
student
I
think
that
can
be
quite
disruptive
to
well.
A
So
when
we
were
selecting
projects,
time
zone
over
the
proposals,
a
topic
well
historically
in
google
Summer
of
Code,
the
most
of
the
students
allocated
in
the
Asian
and
Pacific
region
and
the
most
of
the
Mariners
allocated
in
America.
So
in
Europe,
so
there
is
kind
of
timezone
difference
by
design
in
Gstaad
just
due
to
the
distribution.
A
A
A
K
K
A
So
yeah,
but
well
we
have
to
work
on
that.
Somehow
this
tribute
work
is
challenging
even
for
senior
engineers,
because
it
is
just
completely
different
lifestyle
and
when
you
go
to
JSOC
it's
even
worse,
because
mentor
says
the
partially
available,
there
is
no
mentors
who
can
dedicate
full-time
our
mentorship
and
it's
it's
a
very
much
an
engine,
but
we
have
to
somehow
deal
with
it.
A
E
One
of
the
things
that
I
would
like
to
add
for
the
mentor
commitment
is
regular
communication
from
the
org
admins
to
regular
asynchronous
communication
from
the
org
admins
to
the
Mentors,
more
so
in
the
sinneth,
in
the
form
of
a
stand
up
and
that
doesn't
have
to
be
something
that
has
to
be
in
person.
But
maybe
it's
something
twice
a
week
emails
or
you
know
Monday
and
a
Friday,
something
that
is
showing
that
there's
progress
a
lot
of
times
I
find
we're
all
very
busy
for
most
of
us.
E
We
all
have
day
jobs
so
a
lot
of
times.
We
can
attend
meetings,
but
I
may
read
emails.
You
know
at
night
or
early
in
the
morning.
It
makes
it
easier
for
us
to
catch
up
and
catch
from
an
orgasmic
perspective
to
catch
something
early.
If
I
see
something
or
don't
see,
something
sorry
for
being
long-winded.
There.
A
K
A
L
A
So
yeah,
one
of
the
reasons
why
we
introduced
it
hub
teams
is
because
we
need
a
way
to
include
students
to
the
Jenkins
organization.
It
was
otherwise
if
you
learn
at
the
part
of
our
organization
and
if
you
didn't
have
a
your
project.
For
example,
when
the
case
of
promoted
Beals
in
the
case
of
fraud
strategy,
there
was
no
new
repository
for
students
created
the
beginning
and
hence
they
wouldn't
be
able
to
even
request
reviews
unless
they
edit
to
the
github
organization.
So
it
happens
was
a
way
to
do
that.
A
But
here,
for
example,
in
row
strategy
project
we
region
team
mentions
for
requesting
previews
and
I
show
how
it
was
forbidden,
but
yeah
I
think
that
it
was
still
not
positive
to
help
them
and
oh
yeah.
If
you
don't
use
them,
you
basically
have
no
programs,
so
you
just
don't
use
them.
It
wasn't
a
big
deal
to
set
them
up.
A
If
somebody
is
missing,
but
is
just
the
first
part
so
next
week
retrospective?
So
if
you
would
like
to
add
something,
just
put
your
feedback
to
the
church
and
we
will
make
sure
to
process
that
and
to
discuss
that,
and
even
if
you
just
want
to
speak
up
towards
something
it's
time
to
do
it.
If
not,
we
can
just
go
through
I.
A
E
E
If
you
don't
feel
comfortable
doing
that,
there
is
the
org
admin
I,
don't
know
a
little
different
way
to
send
it
anonymously,
but
what
I
can
say
from
an
organ
inspected
is:
if
you
do
wish
to
remain
anonymous,
you
can
reach
out
to
one
of
the
org
admins
individually
and
they
will
keep
your
information
anonymous
from
not
only
the
community
but
or
other
organs
as
well.
I
just
want
everybody
to
be
able
to
with
providing
you
know
that
can
be
anonymous
as
well.
A
A
H
H
C
C
A
A
So
again,
please
spend
the
next
week
to
just
put
some
feedback
if
you
are
a
mentor
and
if
you
haven't
submitted
your
feedback
yet
please
also
do
so.
I
mean
evaluations.
All
students
have
already
submitted
abbreviations
and
thanks
a
lot
for
that
and
yeah
I
will
just
keep
working
on
the
keyboard,
structuring
that
so
any
kinds
of
being
down
just
put
them
near
there
and
you
build
process.
It.