►
From YouTube: Jenkins GSoC Office Hours, Dec 02, 2020
Description
Recording of the Jenkins GSoC office hours. We discussed how to get started with GSoC, and how to explore the project ideas. Full agenda and meeting notes: https://docs.google.com/document/d/1H0gJt1zdr37YDpuSLXSeFqYco_a_CIrAuZ1f0Oyl4XE/edit#heading=h.idvd06lmb0n1
A
A
So,
let's
just
go
through
that
again,
we
are
in
a
preparation
stage:
google
summer
of
code
applications
open
in
january
for
organizations
or
even
in
february
this
year.
So
we
have
plenty
of
time
to
prepare,
but
we
still
do
office
hours
so
that
students
can
ask
questions
for
our
organization
and
at
the
same
time
we
can
prepare
project
ideas
and
applications
in
advance.
A
C
A
Yeah-
that's
perfectly
fine,
so
anyway,
here
marquee
will
likely
explain
what
I
mean.
You
have
a
chat,
but
it's
to
be
seen.
Martin.
He
has
already
sent
a
message
that
he
would
prefer
to
step
down
this
year,
so
he
will
be
available
to
help
a
bit
here
and
there,
but
not
in
the
official
capacity
of
our
carnegie.
A
So
we
have
up
to
five,
for
we
can
have
up
to
five
four
or
five
minutes
in
the
application.
So
definitely
we
have
quite
a
number
of
slots
and
if
somebody
wants
to
join
that
is
okay,
so
another
open
question
we
have
is
a
collaboration
with
continuous
delivery
foundation,
because
last
year
we
had
two
organizations.
One
is
jenkins
organization
which
hosted
the
jenkins
and
jackman
sex
and
another
is
continuous
delivery
foundation
which
hosted
the
projects
for
the
rest
of
the
continuous
delivery
foundation.
A
A
Yeah,
so
what
it
means
for
students
that
if
you
do
not
see
the
junkies
organization
next
year,
it
doesn't
mean
that
we
don't
participate.
We
might
just
participate
in
the
umbrella
of
continuous
delivery
foundation,
which
is
a
current
current
organization
for
the
junkies
project,
but
yeah.
Basically,
it
remains
the
same
for
us.
So
project
ideas
and
information
on
our
website
remains
totally
relevant.
Even
if
we
participate
in
the
umbrella
of.
B
A
A
The
elections,
work
and
the
junk
selections
are
finishing
tomorrow.
So
after
that
I
will
start
booking
contributors
to
find
more
project
ideas
and
the
mentors
yeah.
I
think
that
our
target
for
this
year
is
to
have
approximately
15
project
ideas
and
regarding
painters,
let's
see
maybe
20
or
so
but
yeah
it's
to
be
seen,
because
this
year,
gsoc
will
be
different
in
terms
of
organization.
A
A
B
C
A
We
had
a
quick
discussion:
okay
I'll
show
it
and
by
the
way
for
students
hold
on
the
call,
please
don't
state
on
mute
and
ask
any
questions.
So
it's
office
hours
and
everybody
can
interrupt
the
discussion
at
any
moment,
so
we
can
discuss
it.
So
if
you
take
a
look
at
the
timeline,
you
can
see
that
the
applications
opening
in
late
january
is
declined
in
february.
So
it's
later
than
usual,
and
actually
everything
is
later
than
usual,
except
the
final
date,
because
coding
phases
are
shorter.
A
Okay,
so
timing,
yes,
may
17th
is
accepted.
Project
june
7th
is
coding,
so
there
are
almost
three
weeks
of
community
bonding
instead
of
one
month
and
then
you
know
first
coating
phase
and
the
second
according
phase,
so
they
are
also
approximately
one
month
a
bit
longer
than
before
so
yeah.
That's
the
only
significant
change
in
the
process.
There
are
also
changes
in
the
eligibility
for
students
because
they
made
adjustments
and
students
who've
been
able
to
participate
in
the
previous
year,
but
they
could
participate
this
year,
even
if
they
wouldn't
be
eligible
according
to
common
goals.
A
A
Okay,
so
yeah
still,
we
need
to
send
call
commenters
in
the
developer
managers.
Things
are
quite
slow
right
now,
but
yeah
it's
rather
better
to
do
it
now
than
in
one
month
when
you
have
christmas
break.
So
it's
just
a
meeting
time
carol.
One
question
to
you
about
jenkins
sex
woo
jenkins.
Your
drinking
sex
this
year
is
an
open
question.
B
I
would
leave
that
as
an
open
question.
For
now.
I
probably
need
to
speak
to
the
james's
about
it.
My
main
concern
with
that
would
be
mentoring
capacity,
so
I
yeah
I'll
put
a
feeler
out
into
the
jenkins
x
community
and
discuss
that
further
with
the
james
is.
I
am
not
sure
so
we'll
leave
that
open
for
you.
B
Okay,
and
so
from
my
understanding
of
your
question,
then
from
the
point
of
view
of
the
jenkins
project,
as
with
last
year,
if
need
be,
we
would
be
very
happy
to
have
jenkins
x
within
the
jenkins
or
umbrella
again
or
within
the
cdf
or
umbrella,
depending
on
which
way
we
go
there
is
that
is
that
a
good
understanding?
Okay?
So
then
it's.
A
B
A
A
D
A
C
A
In
the
previous
year,
our
project
ideas
once
which
are
published,
they
include
references
to
some
good,
they
provide
getting
started
guidelines
and
since
you
participated
in
the
previous
year,
basically
these
are
the
same
guidelines
as
before.
We
still
need
to
refactor
them,
but
yeah.
There
are
newbie
different
issues.
You
can
take
a
look
at.
There
are
some
quick
start
guidelines
you
can
start
from
and
in
addition
to
that,
you
can
also
just
explore
jenkins
export
areas
using
existing
guidelines
like
getting
started
with
jenkins.
A
Also,
there
are
contributing
guidelines
for
drinks
participate,
so
you
can
go
here
and
you
can
find
some
references
to
newcomer
tasks
by
exporting,
for
example,
yeah
google
summer,
of
course,
is
about
code,
and
here
there
are
references
for
newcomers,
for
example
new
friendly
issues,
good,
firstly,
issues
on
github,
etc.
So
you
can
just
take
one
of
these
categories
and
there
will
be
some
issues.
You
could
start
from.
A
D
A
D
Yes,
but
for
getting
the
project,
so
we
can't
make
ourselves
some
ideas
right,
because
we
have
not
worked
specifically
on
this
domain
right.
So
if
you
can
provide
some
ideas
or
some
small
small
project
ideas
on
which
we
can
work
and
explore
specifically,
so
that
would
be
great,
so
student
perspective
you're
not
done
hands-on
on
jenkins
site.
Just
we
have
last
year
when
I
have
articulated
what
means
have
run
the
jenkins
and
I
have
seen
how
the
export
exported
animation
is
working
and
how
the
rest
of
va
is
working.
D
A
D
A
A
Actually
we
ran
out
of
good
first
issues,
but
there
is
still
one
left
and
we
can
definitely
create
more.
But
here,
if
you
interested
to
explore
it,
the
best
way
would
be
to
actually
to
use
the
tool
to
see
how
it
works.
Maybe
to
do
some
improvements,
for
example,
in
documentation,
based
on
your
experience,
to
create
some
tests,
because
any
component
needs
more
tests
and
if
you
see
some
patches,
which
you
would
like
to
do,
you're
also
a
modern
welcome
to
contribute
to
this
company.
A
A
So
you
can
go
through
this
documentation
and
just
set
up
jenkins
and
kubernetes
and
then
configure
parameters
to
monitor
it,
and
it
will
provide
you
some
insights
about
how
the
systems
work
and
after
that,
you
can
explore
what
would
be
good
to
monitor
on
the
agent
communication
side,
because
many
things
can
be
done.
The
use
existing
plugins,
but
you
can
just
see
what
else
could
be
improved.
D
C
So
to
further
support,
oleg's
oleg
suggestions.
We
had
good
success
last
year
with
the
git
plug-in
the
students
that
were
considering
applying
took
one
of
their
tasks
as
write,
more
tests
for
the
git
plug-in,
and
we
had
a.
We
had
actually
a
transformation
story
that
we
were
a
ticket
that
we
were
working
on.
So
writing
tests,
for
whatever
target
is
a
good
thing.
A
A
C
It's
a
way
to
allow
a
much
richer
set
of
actions
inside
pipeline
get
related
without
requiring
that
we
do
implement
those
all
of
those
in
code
that
one
is
number
three
and
the
most
requested
features.
So
it's
it's
very,
very
popular
right
now,
embarrassingly
popular
it's
so
so
much
interest
in
the
community
wants
that
fix
that
change.
A
C
That's
that's
the
one
and,
and
I
think
it
as
I've
been
detailing
it.
I
think
I've
detected
that
credentials
binding
is
exactly
the
way
to
do
it
and
and
we
just
need
to
refine
and
adapt
it
slightly
to
do
to
do
it.
So
it
looks
very
potent
very
probable
that
it
would
be
done
using
a
credentials
binding
plug-in
technique.
C
Okay,
this,
but
but
the
the
challenge
there
was,
I
guess.
Well,
let
me
go
through
the
the
topics
first
really
quickly
and
then
then
we
can
guide
the
next
one
was
add:
pipeline
symbols
to
the
git
plug-in
and
the
the
benefit
there
is
users
will
get
a
much
simpler
presentation
of
their
pipeline
as
they're
editing
it
as
they're
looking
at
it.
Instead
of
these
big
long
class
references,
they
get
nice
simple
keywords.
C
C
And
then
the
fifth
is
get
lfs
improvements
and
my
thinking
is
the
top
two
are
the
most
interesting
to
me
and
I'll
do
more
detailing
on
them.
The
the
third
is
an
almost
a
research
project.
It's
not
really.
It's
not
been
proven
that
would
even
work
and
therefore
I'm
not
sure
it
fits
well
with
google
summer
of
code.
Is
it
okay
to
do
research
style
projects
in
google
summer
of
code
or
advised
against
four.
A
Well,
research
projects
make
sense
if
there
is
a
clear
goal.
So,
okay,
yeah
research
project
may
mean
that
there
are
some
uncertainties,
but
still
the
main
focus
is
creating
code
and
solutions,
so
it
wouldn't
be
a
research
project
as
let's
explore
their
and
summarize
the
results
it
would
be.
Rather,
let's
create
a
prototype
of
a
particular
idea.
C
Okay,
so
that's
good
guidance.
That
means,
I
think,
what
I'm
going
to
do
is
likely
work
on
the
top
three
most
focus
on
number
one,
because
it's
detailing
is,
is
crucial.
I'll
put
straw,
some
focus
on
item
two
and
just
a
little
on
three
accepting
that
the
project
idea
review
process
may
reject
it
as
insufficient
information.
Thank
you
that
was.
That
was
the
kind
of
guidance
I
was
seeking
yeah
for
second
issue.
C
And
and
my
problem
with
not
making
it
a
g
stock
project
is
all
my
attempts
to
test.
It
have
proven
that
it's
not
as
small
as
I
hoped
it
was
okay,
it's
it,
but
it's
it's
much
more
heavy
test
focused
than
it
is.
Writing
code
focused
right.
So
it's
maybe
a
bad
choice.
Just
because
there's
not
enough
code
to
write
as
there
is
a
whole
lot
of
testing
that
has
to
be
done.