►
From YouTube: Jenkins GSoC Office Hours for Feb 5, 2020
Description
GSoC Office Hours for Feb 5, 2020
Agenda:
- Jenkins org pplication period
- New proposal for Jenkins X
- New project section in project ideas called “Ongoing discussion”
- Q&A from Students
A
Hello
everybody
good
morning,
good
afternoon,
good
evening.
This
is
the
google
Summer
of
Code
for
the
Jenkins
project
office
hours
today
is
February
fifth
and
I
would
like
to
welcome
everybody.
My
name
is
Marky.
I
am
one
of
the
org
admins
for
the
google
Summer
of
Code
project
and
we
meet
weekly.
This
is
our
meeting
that
is
my
intra.
A
A
Am
going
to
start
with
action
open
items
from
let's
see,
got
a
few
items
to
take
care
of
here,
I'm
going
to
see
what
we
had
action
items
for
from
last
meeting
and
as
everybody
is
aware,
and
if
you're
not
I
will
share
with
you
the
application
he
ended.
The
application
period
ended
yesterday
or
technically
this
morning,
at
12
a.m.
we
had
submitted
our
application
or
status
with
the
google
Summer
of
Code
I
will
also
share
with
everybody,
make
sure
I
covered
all
of
it.
A
A
Oleg
is
not
here,
he
is
traveling
Oleg.
If
you
are
watching
this,
do
you
have
an
open
item
for
the
blog
post,
copy-editing
I,
believe
that
is
still
a
work
in
progress.
I
have
not
seen
the
PR
come
through
for
that
particular
one.
We
did
have
the
open
item
for
move
project
ideas
to
accepted
State.
There
are
still
a
few
more
that
needs
to
be
moved.
We
will
be
doing
that
this
week
and,
let's
see
I
know
we
have
a
new
application,
and
that
is
our
excuse
me.
A
A
B
A
A
C
A
A
A
Here
that
most
welcome,
so
we
will
we'll
go
ahead
and
start
working
on
that
I
know
I've
also
I
volunteered
to
be
a
mentor
on
that
project.
Like
know
the
code
base
a
little
and
I
think
I
could
help
proposed
purpose.
I
can't
even
count
great
a
possible
students
should
they
come
on
they're
marking,
Martin.
You
said
that
there
was
a
new
section
that
was
added.
B
Yes,
the
new
section
is
called
exec
ongoing
projects
that
are
under
ongoing
discussions.
It's
listed
at
the
bottom
of
the
project,
ideas
page,
and
these
are
for
projects
that
well
apparently,
don't
have
don't
have
it
formal
sort
of
don't
have
a
formal
probe
idea
fully
formed
idea.
There
are
more
links
to
discussions
for
potential
projects,
and
so
I
would
suggest
that
the
two
plugins
that
don't
have
potential
mentors
yet
the
artifactory
rest
and
the
Jenkins
rest.
B
A
A
A
D
So
so,
like
you've,
Mackey
you've
been
a
mentor
last
year,
also
right
and
I.
Think
even
Martin
has
been
so.
My
question
is
basically
that
do
you
know
at
the
end
of
it
like
after
the
deadline,
when
you
decide
on
student,
like
you
might
have
a
you
know,
a
rough
feel
as
to
how
you
decide,
which
is
a
good
application
like
what
are
some
of
the
KPI
is
you're
looking
for
in
an
application
or
something
along
those
lines
that
you
really
think
makes
you
choose
a
student
well.
A
I
can
say
that
the
first
things
that
we
look
at
is
the
students,
aptitude
or
ability
for
a
given
project.
So
if
a
project
requires
more
code
like
base
level
knowledge,
we're
going
to
look
at
that
right,
what
is
the
student's
code
ability?
We
don't
want
to
assign
a
student
that
you
know
has
a
Python
background
and
just
barely
on
beginning
with
Java
to
a
heavy
Java
project,
because
that's
setting
you
up
for
failure.
A
So
what
we
do
is
we
do
sort
of
an
interview
period
where
we
get
to
note
that
this
is
outside
of
the
bonding
period.
What
we
do
is
we
get
to
know
the
student
know
what
their
ability
is
and
then
say:
okay,
this
is
this
is
be
a
right
project
for
you
and
then
assign
them
to
that.
The
second
thing
that
we
look
for
above
that
is
the
students
enthusiasm
to
do
something.
If
you
not
excited
about
a
project,
you're
not
gonna,
want
to
spend
three
months
working
on
something
you're
not
excited
about.
A
So
we
want
to
make
sure
that
that
level
of
enthusiasm
is
there.
Now
that
doesn't
mean
I
expect
you
two
to
go.
Cheering
and
screaming
and
getting
all
crazy,
but
what
I
mean
is
that
you
have
to
really
want
to
do
what
it
is
you're
working
on,
because
I'll
give
some
examples
from
prior
year
students
a
lot
of
these
projects,
if
you
make
it
through
the
full
summer
for
the
google
Summer
of
Code
and
your
project
is
completed
and
you
pass
it's
a
great
reflection
to
potential
employers
to
your
peers.
It's
a
great
reflection.
A
C
So
I
can
I
can
add
a
couple
of
things
too
I
mean
the
students,
write
proposals
or
the
projects
that
the
project
ideas
are
kind
of
basic
and
especially
some
of
the
ones
that
are
more
popular.
You
kind
of
tell
that
that
the
students
didn't
give
it
much
thought
they
kind
of
came
in
at
the
last
minute
and
they
wrote
something
real
vague.
C
So
if
I
see
a
proposal
where
it's
obvious
that
they
gave
a
lot
of
thought
to
like
the
trade-offs
and
there's
a
well
with
written
proposal,
then
definitely
I'd
be
excited
about
that
student.
A
lot
of
times.
Students
might
spend
a
little
bit
of
time.
Actually
products
I
think
something
and
I
mean
you
know.
That's
that's
a
lot
of
risk
if
you
may
not
get
accepted,
but
when,
when
I
see
that
they've
actually
written
some
code
kind
of
a
proof-of-concept
thing,
I
get
really
excited
about
that
student.
D
A
A
So
what
happened?
What
happens
is
starting
the
16th
of
March
we
have
from
the
16th
of
March
to
the
31st
of
March.
Students
will
say:
I
want
to
work
on
project
a
so
we
will
reach
out
to
that
student
and
we
will
say:
ok,
you
would
like
to
work
on
a.
We
have
a
mentor
for
that
project.
We'd
like
to
introduce
you.
The
mentor
will
then
meet
with
you
and
if
it's
everything
is
a
good
fit,
then
you
get
assigned
to
that
particular
project
that
happens
between
the
16th
and
31st.
A
D
A
A
The
application
review
period
is
where
the
organization
reviews
and
selects
the
students,
and
that
goes
for
March
31st
to
April
27th
on
April
27th,
is
when
we
announce
the
student
projects
and
that's
where
accepted
students
are
paired
with
mentors
and
they
start
planning
on
their
project
in
milestones
from
April
27th
to
May.
18Th
is
the
community
bonding
phase.
This
is
where
the
students
spend
a
month.
Learning
more
about
the
organization's
community
coding,
starts
on
May
18th
and
runs
through
August
10th.
A
The
evaluations
for
first
evaluations
is
from
June
15th
through
the
19th.
The
second
evaluation
is
July
13th
through
the
17th
between
August,
10th
and
August.
17Th
is
when
students
submit
their
final
code.
It's
you
may
submit
their
code
in
their
final
evaluations
and
then
from
August
17th
to
argost.
24Th
is
when
mentors
submit
their
final
evaluations
and
finally
on
August.
25Th
is
when
the
results
are
announced.
I
will
kind
of
cover
just
a
little
briefly
how
the
evaluation
periods
go
generally.
A
A
Went
through
it
rather
fast,
I
know
him,
and
if
you
have
any
questions-
and
you
don't
feel
comfortable
asking
here,
do
you
have
the
ability
to
ask
in
the
google
Summer
of
Code
getter
channel?
If
you
don't
feel
comfortable
asking
in
there
and
you're
still
trying
to
figure
this
out,
please
do
reach
out
to
one
of
the
org
admins
directly.
That's
myself,
Martin
Jeff
Oleg,
and
if
there's
any
questions
you
know
again,
don't
don't
hesitate
to
reach
out.