►
Description
This session was intended to help potential GSoC candidates prepare for their participation ('build their muscles') for the application with Jenkins in GSoC.
A
A
So
this
webinar
is
to
help
address
the
question.
How
do
I
get
started
with
Jenkins
in
gsoc?
So
hopefully,
by
the
end
of
this
session,
it
will
have
helped
you,
you
know,
get
started
figure
out
how
to
get
started,
what
to
expect
and
so
on.
So
my
name
is
Alyssa
Tong
and
I'm.
An
org
admin
for
gsoc
Along
on
this
webinar
with
me
are
John
Mark
Mason.
Also
an
orc
admin.
Bruno
is
also
brunoctan.
Sorry
Bruno
is
also
Oreck
admin.
A
A
So
for
Q
a
feel
free
to
put
it
into
the
chat
window.
We
will
answer
them
as
we
go
along
and
if
we
have
time
at
the
end
of
the
webinar,
we
will
open
it
up
to
q,
a
as
well
so
for
questions
that
you
know
that
may
come
up
after
the
event
feel
free
to
put
it
into
the
getter
or
discourse
Channel,
and
then
we
will
get
to
them.
You
know
as
we
as
we
see
them
and,
of
course
the
code
of
conduct
applies
here
as
well.
A
B
B
B
B
B
You
will
see
great
things.
You
will
do
great
things
together
and
this
picture
for
me
really
summarizes
everything
you
will
get
to
places
where
you
didn't
think
that
you
would
get
to
and
like
Alpine
Alpine,
Adventures
or
Himalaya
for
people
in
India,
which
is
their
this
can
only
be
achieved
as
a
team.
Together,
generally,
you
have
a
guide
that
brings
you
to
explore
these
incredible
sceneries
and
participate
to
these
Adventures.
B
B
Has
only
a
limited
or
finite
coaching
capacity
for
Google
summer
of
code,
that
means
there
are
only
a
limited
number
of
slots
available
and
not
everybody
will
be
selected,
so
the
selection
process
is
already
part
of
the
schooling
of
the
adventure
has
a
first
big
hurdle
to
to
win,
so
only
the
strongest
proposal
will
be
selected
and
on
on
the
criteria.
What
are
the
the
projects
that
are
the
more
likely
to
be
successful?
B
B
B
B
B
B
B
Google
has
also
some
very
good
pages
and
good
readings
on
how
it
goes.
What
is
a
project
idea?
What
is
the
role
of
mentors?
What
is
expected
a
lot
of
documentation,
take
the
time
to
read
it
and
we'll
have
other
opportunities
during
the
process
where
we
can
discuss
together
in
where
we're
available.
To
answer
questions,
the
only
thing
we
would
like
is
that
you
have
read
you
know
the
theory
of
the
the
program.
B
B
B
B
B
When
you're
going
to
work
on
an
idea
when
you're
going
to
work
on
your
codes,
you're
not
going
to
do
it
in
your
corner,
In,
Your,
Den
somewhere,
and
only
show
it
at
the
end
of
the
process
here,
the
process
is
that
all
everything
that
you're
going
to
do
everything
that
you're
going
to
to
build
that
you're
going
to
learn,
is
written
down
somewhere
shared
that
everybody
in
the
community.
There
are
many
time
zones
involved
the
different
skills
involved,
but
everything
is
open,
so
you're
going
to
write
and
prepare
a
project
proposal.
B
All
that
is
done
in
the
open
and
you
ask
the
community.
What
do
you
think
of
that
idea?
Nobody
has
has
a
comment
about
that.
Okay,
then
we
go
on,
but
at
least
you
have
described
your
idea,
and
you
requested
for
comment,
and
so
I'll
come
back
later
in
the
explanation
explanation.
So
this
is
how
the
community
works.
B
B
B
There,
it
is
so
this
is
the
Jenkins
IO
website
is
the
main
Jenkins
and
you
go
in
sub
projects
Google
summer
of
code
in
Jenkins.
This
is
the
main
page
of
our
project
of
our
initiative,
where
you
have
a
lot
of
explanation,
this
is
the
gsoc
home
page
for
for
and
we'll
update
it
regularly.
This
is
where
you
have
a
direction
to
all
the
all
the
various
documentations.
B
B
B
These
are
here
the
current
lists
of
projects,
we're
working
on
I
just
walk
here,
so
the
first
status
of
project
ideas
are
the
ones
being
discussed.
That
means
somebody
woke
up
in
the
morning
suddenly
and
I
have
an
idea,
and
he
writes
it
down.
People
discuss
us,
but
what
you
mean,
what
would
be
the
ielt
com
and
so
on,
and
so
it
starts
to
crystallize.
B
Currently
we
don't
have
any
projects
anymore
that
are
in
this
very
early
stage.
These
are
the
projects
that
are
in
draft
mode.
These
are
ideas.
We
have
a
rough
idea.
What
it
could
be
not
all
have
mentors
assigned
to
when
you
click
here
on
it,
which
one
can
I
can
I.
Take
one
I'm
going
to
take
this
one
here,
so
you
have
details
on
what
is
the
background?
What
are
the
skills
required?
B
What
is
the
difficulty?
What
are
the
outcomes
and
a
lot
of
a
lot
of
details?
This
is
the
first
stage,
study
them
and
try
to
understand
it.
We're
going
to
organize
in
the
second
half
of
January
one
or
several
sessions
where
the
mentors
I
will
present
each
project
idea
in
more
detail,
and
you
will
be
able
to
ask
questions
and
know
what
would
you
mean
I
understand
it?
That
way.
Is
it
in
line
I?
Have
this
novel
idea?
Everything
is
done
in
the
open
everybody
hears
the
same.
B
B
In
March,
February
and
March,
this
is
where
you
have
chosen
a
project
and
you're
going
to
build
your
proposal.
Now
we're
going
to
do
something
at
that
moment
very
unnatural,
especially
unnatural,
compared
to
what
you
have
been
taught
at
school,
or
so
the
first
principle
at
school.
You
don't
cheat,
you
don't
look
what
your
neighbor
is
doing
and
you
you
don't,
and
you
protect
your
work,
that
somebody
is
not
going
to
cheat
on
you.
Well.
B
B
B
This
you're
going
to
burn
your
fingers
with
a
try,
this
method
or
try
this
goal
and
or
these
kind
of
thing,
so
it
will
be
a
very
weird
process
for
you,
but
believe
me,
it's
a
very
rich
process
and
it
will
make
your
draft
your
proposal
stronger.
Yes,
somebody
can
come
and
pick
your
idea.
It
may
be
a
faster
than
you
and
but
it's
it's
part
of
the
game,
so
you
need
to
be
the
best.
B
You
need
to
learn
and
we're
there
to
help
you
and
we
there
to
help
everybody
the
same
the
same
way.
So
there
is
a
little
bit
of
what's
what's
the
English
word
for
that,
but
natural
selection
of
idea,
it's
tough,
but
this
is
the
way
it
works,
and
this
is
why
we
don't
want
to
privilege
this
person
or
that
person
by
giving
him
insight,
and
so
this
is
something
you
really
need
to
to
understand.
We're
going
to
to
explain
that
that
so.
B
That
means
that
we're
going
to
organize
a
meeting
every
week,
we're
trying
to
look
to
have
the
correct
time
zone
to
have
it
friendly
for
the
the
biggest
for
the
majority
of
the
participants
I
see
from
the
names
here
that
will
be
more
on
the
Asian
side,
but
we'll
organize
a
meeting.
That
meeting
is
just
well
here
I'm
there
and
what
are
your
questions?
What
are
your
concerns?
What
are
your
doubts?
B
B
B
B
All
your
proposals
will
reflect
on
them
and
will
rank
them
and
we'll
build
a
proposal
with
a
number
of
slots
that
we're
requesting
from
Google
and
providing
them
evidence
of
what
is
the
the
coaching
capacity
we
have,
and
so
Google
and
our
organization
will
come
with
a
proposal
and
say
these
are
the
number
of
slots
that
we
request.
These
are
the
projects
that
we
want
to
to
run
this
year,
and
these
are
the
people
we
select
in
these
projects
and
this
will
be
announced
May
4th,
and
this
is
where
it
really
starts.
B
So
all
that
is
a
preparation
for,
and
you
will
realize,
there's
a
lot
of
work
involved
to
get
up
to
there
from
the
from
May
4th
I.
This
is
far,
but
in
a
nutshell,
what
will
happen
is
that
during
a
period
you
will
we
call
it
the
bonding
period.
I've
I've
I,
find
it
funny
word,
but
you
will
first
learn
to
know
your
mentors
and
the
mentors
will
learn
who
you
are,
how
you
work.
You
will
set
up
a
work,
a
work
framework.
B
B
B
What
are
the
things
that
you
can
show
and
brag
about
and
then
somewhere
in
September
we'll
have
the
and
terminate
the
end
presentations
and
also
presentation
of
the
deliverables
and
we'll
do
a
wrap
up?
Okay.
So
this
is
the
timeline
I
realize
I
have
been
in
a
lot
of
details
and
I've
eaten
a
lot
of
time,
so
I'm
I
apologize
for
that
I
wanted
I
went
to
to
give
enough
details
about
that
now
to
the
more
technical
part
and
I
give
the
word
to
Chris.
C
Okay
sure
so
I'm
going
to
talk
a
bit
about
tech,
stack
we're
using
a
Jenkins,
so
most
of
the
projects
are
in
Java,
some
in
kotlin
and
for
website
it's
mostly
in
JavaScript.
It
says,
as
in
Ruby,
some
projects
have
been
in
bash,
so
it
all
depends
on
the
requirements
and
for
the
web
development
of
jenkins.io,
which
is
a
project
idea
we
have
for
this
year.
So
our
main
website
we
use
ASCII
dog.
C
They
ask
you
many
project
ideas
involved,
proof
of
concept
and
documentation
such
as
the
website
revamp
I
just
talked
about
an
awesome,
Android
and
Os
projects.
Many
of
the
projects
involve
tooling
or
development
tools.
So
it's
a
good
idea
to
read
about
these
and
do
some
research
and
make
a
good
proposals
later
on
next
page.
C
Okay.
So
how
to
prepare
discussing
first,
we're
just
to
do
with
social
support
idea.
You're
interested
in
that's
important
because,
like
you
need
to
have
a
context,
and
we
don't
normally
give
out
too
much
about
the
context.
So
you
have
to
be
original
and
be
able
to
come
up
with
some
solid
ideas
about
what
it's
necessary
to
to
make
a
successful
for
your
end
and
two
do
ask
enter
any
questions
on
IRC
such
as
guitar.
C
This
is
because,
like
it
will
help
us
to
differentiate
like
to
to
tell
like
who
is
more
likely
to
be
able
to
successfully
complete
the
projects
and
we'll
choose
the
contributors
accordingly
and
three
interact
with
the
community.
So
don't
just
think
that
it's
all
about
what
we
saw.
It's
a
large
part
of
the
application
has
to
do
with
the
interaction
as
well.
C
So
do
do
you
engage
yourself
with
like
early
conversations,
you
might
find
interesting
or
you
might
find,
rather
than
do
a
project
idea
and
Floyd
development
proposal
of
the
community.
So,
like
jean-mark
just
said,
developed
Proposal
with
us,
so
ask
questions.
Share
your
proposal.
I
apologize
with
us.
If
you
have
any
doubts
or
questions,
do
ask
in
five
shows
we
should
can
do
about
some
meaningful
requests.
C
Patches
fixes
impactful
contributions,
so
I
think
I've
heard
from
some
other
organizations
that
they
do
consider
pull
requests
as
a
must
before
they
can
accept
an
application.
So
but
I,
don't
think
that's
the
case
for
Jenkins,
but
we
do
appreciate
any
football
quests
submitted
as
part
of
Aviation
process.
C
Okay,
so
next
so
that's
to
remember,
remember
to
check
Google's
program
timeline
which
is
adding
to
given
and
to
adhere
to
it
because,
like
we
have
very,
very
strict
timelines
and
we
don't
normally
like
give
Grace
periods,
even
if
you
have
very
legitimate
reasons
to
be
late
for
something
so
Jesus
contributes.
The
applicant
period
begins
on
March
20th
at
6,
PM
UTC.
C
It's
that
I
think
that's
about
March,
21st,
Indian
time
or
Asian
time
and
Jesus
contributor
applications
that
only
it's
on
April
4th
same
6,
PM
UTC.
So
that's
April,
5th
Asia
time,
except
these
are
contributed
projects
we
announced
on
May
4th
same
time.
6
00,
PM
UTC,
so
don't
be
late,
be
on
time
and
be
prepared.
B
D
B
Important
I'm
going
to
pick
up
here,
Chris
or,
and
you
can
jump
in
afterwards
here-
are
some
resources
at
this
point.
I
just
would
like
to
pull
into
the
conversation
last
year's
participants,
so
we
have
rushikash
if
I
can
see
correctly
I'm,
not
monitoring
chat,
so
I
will
so
Hoshi
cash
quickly,
well,
not
quickly,
but
take
your
time.
But
what
would
you
like
to
share
with
this
year's
candidate
for
gsoc?
B
E
So
yeah
so
I
feel
communication
is
a
key
for
a
successful
project.
Initially
I
was
a
very
shy
person.
You
know,
I
I,
didn't
know
what
kind
of
questions
to
ask.
I
was
worried.
What
people
would
think
about
me
if
I
asked
some
silly
questions.
I
was
very
anxious
to
share
my
ideas.
I
didn't
know
where
to
get
started.
The
Jenkins
code
base
is
really
big.
There
are
so
many
files,
you
don't
know
where
to
get
started,
but
Jenkins
community
did
make
it.
You
know
easy
for
us.
E
It
was
very
comfortable
Journey
though
I
I
didn't
know
how
those
three
months
far
you
know
just
passed,
but
then
it
was
a
very
smooth.
Journey
I
did
face
a
lot
of
challenges,
but
in
the
end,
yeah
you
have
to
just
get
started.
Explore
the
code
days,
be
very
active
in
the
community
and
take
the
help
of
all
the
people
in
the
community
to
create
a
very
strong
proposal.
B
B
B
You
need
to
explain
what
you
want
to
do
in
in
ask
for
feedback,
so
this
is
key.
It's
a
hurdle
and
pushy
cash
had
some
some
issues
in
the
beginning.
It
was
I,
remember,
very
shy
in
the
beginning
and
who
am
I
to
dare
ask
to
to
people
like
Mark,
Waits
or
or
these
these
knowledgeable
people
I'm,
just
no
you're
an
important
person.
You
come
with
your
experience.
B
You
come
with
your
heart
in
that
that
Adventure
you're
worth
that
that
we
as
a
community
community,
take
the
time
to
help
you,
but
we
need
to
get
that
discussion
going.
We
need
to
get
that.
So
this
is
the
most
important
advice,
efficient
communication.
Don't
assume
that
the
person
you're
talking
to
is
sitting
near
your
desk
and
sees
what
is
your
on
screen?
It
doesn't
work
what
doesn't
work
or
what
did
you
intend
to
do?
B
What
are
you
trying
to
do
see
these
kind
of
thing?
Don't
assume
it.
This
is.
This
is
what
I
feel
a
very
most
important
lesson
in
this
complete
adventure
in
one
of
the
key
stones
of
of
Open
Source.
So
thank
your
cash
to
have
stressed
that
point,
and
now
I've
eaten
most
of
the
time
here,
because
we're
now
listening
to
your
your
question,
and
so
you
can
practice
the
first
lesson
being
don't
be
shy.
F
B
So
there
are
two:
there
are
different
ways
to
contribute
and
then
I
will
I
will
give
the
the
word
to
Mark,
who
isn't
as
his
own
experience,
then
maybe
Chris
Kim
chime
in
the
first
way
to
contribute
and
clarify,
is
to
submit
a
pull
request
on
the
project
proposal,
and
this
will
be
then
reviewed
by
the
team.
This
is
not
the
most
efficient
way
to
do
it.
If
you
have
lightweight
ideas,
questions
queries
you
can
use
community.jenkins.io,
which
is
the
discourse
where
you
can
start
here.
B
I
didn't
I,
don't
understand
this.
This
work
this
word:
where
should
I
look
for,
but
nothing
refrains
you
to
really
start
giving
structure,
and
if
you
have
ideas
you
can
really
start
contributing
on
the
idea
for
that
create
Google,
doc
document,
so
we're
sponsored
by
Google,
so
everything
uses
Google
tools
which
work
well
for,
for
that
purpose,
create
a
Google
doc,
a
document,
a
good
idea
to
use
the
template.
B
That's
available.
Generally,
these
kind
of
contribution,
these
kind
of
working
is
done
in
a
later
phase,
because
now
they're
the
project
ideas
are
still
very
fuzzy.
But
here,
if
you
already
understood
it-
and
you
come
with
novel
ideas
in
it,
go
for
it
you've
seen
what
Mark
Mark
reaction
on
that.
So
to
summarize,
can
we?
Yes?
Yes,
yes,
three
or
four
times
yes,
how
discuss
on
community
or
getter?
B
G
No
I
I
think
you
did
great
the
the
answer
for
me
is:
can
you
contribute
to
project
ideas?
Absolutely
you
can
do
it
by
getting
involved
in
conversations
on
guitar
chat.
You
can
do
it
by
getting
involved
in
conversations
on
community.jenkins.io.
You
can
do
it
by
getting
involved
in
conversations
on
the
Jenkins
developer
mailing
list.
You
can
get
involved
with
the
project
idea
in
the
advanced
way
that
John
Mark
said
of
submitting
pull
requests
to
the
project
idea
to
to
propose
refinement
for
it.
G
I
think
that's
that,
for
me,
is
a
later
stage,
but
just
being
involved
in
the
conversations
about
this
idea,
helping
clarify,
because
inevitably,
if
you
have
a
question
about
a
project
idea,
that's
listed
there,
others
have
the
same
question
and
they're
too
timid
to
ask.
So
you
be
the
Bold
one.
You
ask
the
question
and
except
that
people
will
give
you
an
answer.
E
I
had
one
point:
I
wanted
to
ask:
well
don't
I
want
to
do
it,
like
you
know,
just
add,
don't
get
dejected.
If
your
question
is
on
answered
immediately,
okay,
it
it
takes
time,
for
you
know
the
community
I.
Do
you
know,
answer
your
questions
but
I'm
pretty
sure
someone
or
the
other
will
answer
your
question.
Yeah.
B
G
So
we
sleep
it's
a
very
good,
it's
a
very
good
point
that
we
sleep
and
I
actually
sleep
at
different
times
that
other
people,
sleep
at
India,
is
almost
12
hours
away
from
me
right
and
therefore,
the
time
of
day,
for
you
for
hushikesh,
for
instance,
is
usually
exactly
opposite
from
my
time
on
the
planet,
welcome
to
a
worldwide
project
and
the
complexities
that
come
with
being
in
a
worldwide
project.
One
of
them
is
we're
not
always
awake.
G
The
other
is
many
of
us
have
jobs
in
addition
to
being
to
being
contributors,
and
we
want
to
be
sure
that
we
do
all
the
things
so
ask
your
questions.
Also,
don't
be
shy
if,
if
it
takes
a
while
to
answer
your
question
to
refresh
it
hey
did
anyone
have
this?
Can
anyone
help
me
sometimes
a
question:
that's
asked
is
challenging
enough
that
it
actually
requires
some
research
from
us
and
from
one
of
the
people
who
would
respond
and
that
research
may
be
non-trivial.
B
G
It
if,
if
they'd,
prefer
to
ask
questions
verbally,
they
certainly
can
they've
they've
been
given
the
permission
to
unmute
themselves
van
did
let's,
let's
take
udit's
question
first,
he
says
he
usually
takes
four
or
five
hours
of
research
and
development
in
starting
on
an
issue.
Should
he
be
speeding
things
up,
none
of
us
are
worried
about
how
fast
or
slow
you
proceed.
Truly,
none
of
us
are
worried
about
your
pace.
That's
up
to
you!
What
time
you
have
available
and
what
you
can
do
so
work
at
a
speed.
That's
comfortable
to
you.
G
I
spend
a
lot
of
time
in
debuggers.
I
spend
a
lot
of
time.
Writing
automated
tests.
I
spend
a
lot
of
time,
interactive
testing,
none
of
which
is
actually
writing
new
source
code,
and
that's
okay
van
did
the
question
if
he
gets
stuck
somewhere
while
working
on
a
patch,
is
it
silly
to
ask
for
a
review?
Not
only
is
it
not
silly,
it's
encouraged
highly
encouraged.
The
best
form
of
ask
a
question
is
usually
submit
a
pull
request
with
your
idea
of
how
you
think
you're
going
to
do
it.
G
That
shows
you've
done
the
work
to
make
your
pull
request,
compile
that
you've
understood
enough
to
think
about
the
tests
for
it
and
you've
submitted
it
now
it
may
be
that
you
say:
hey
I'm,
submitting
this
with
a
failing
test.
I,
don't
know
how
to
make
this
test
work.
That's!
Okay,
great!
That's
a
good
way
to
ask
a
question
because
I
can
look
at
the
source
code
or
others
Bruno
or
John.
Mark
can
look
at
the
source
code
or
Chris
can
look
at
the
source
code
and
say:
hey
your
Source
code's.
G
C
G
I,
like
that
question,
so
submit
a
pull
request.
It
can
be
either
a
good
first
issue
or
something
more
advanced
whatever.
Whatever
helps
you
build
the
skill,
what
John
Mark
described
it
as
is
building
developing
your
muscles
for
contribution
and
part
of
that,
is
you
develop
a
skill,
the
skill
to
phrase
your
pull
requests?
Well
to
understand
what
the
expectations
are
from
reviewers
as
you
submit
a
pull
request?
Oh
you
didn't
you,
you
ignored
the
checklist.
No,
don't
ignore
checklists.
Oh
you
forgot
to
add
tests.
No,
don't
don't
forget
to
add
tests.
G
B
Right
now,
it's
building
your
muscle
is
building
the
skills
and
it's
a
way
of
working
and
and
just
remember,
if
you're
still
studying
these
skills
will
be
very
useful
to
you
when
you
start
your
working
career.
So
it's
a
great
opportunity,
even
in
the
selection
process,
or
everything
that
you
learned
in
the
selection
process
will
be
useful
for
you
in
your
in
your
studies
and
a
future
working
a
career.
B
B
Now,
to
be
honest,
it
depends
on
where
the
Moon
is
standing,
what
is
the
height
of
the
water,
and
so
that's
not
true,
so
making
a
joke,
so
the
selection
process
uses
several
criterias
and,
if
I
remember
well,
these
were
written
down
last
year.
I
will
make
sure
that
we
have
guidelines
for
that.
In
a
nutshell,
the
and
I'll
go
back
to.
C
B
That
means
that
you've
shown
that
you
have
the
communication
skills
that
you
understood
the
problem
that
you're
able
to
explain
what
you
want
to
do
and
that
you've
shown
that
you
have
the
right
stuff
to
bring
it
to
the
end,
because
we
have
three
months
to
do
that.
I'm
sure
convinced
that
everybody
will
succeed.
It's
only
that
some
people
will
need
more
time
and
more
help
to
do
that
and
others
it
will
be
quicker.
We
need
to
select
so
it's
it's
it's
competitive.
B
Other
criteria
is:
is
the
project
useful
to
the
Jenkins
project
to
the
Jenkins
community,
because
you
can
come
with
your
own
project
idea?
We've
been
selective.
We
we
worked
out
some
proposals
for
you
to
work
on
these
are
these
are
good.
These
are
useful,
but
some
are
more
useful
than
than
others.
For
instance,
I
know
I'm
not
going
to
to
give
hints
there,
but
try
to
put
yourself
at
at
the
place
of
of
users
of
the
community.
B
Oh
that
that
will
be
useful
for
people,
and
this
is
how
I
will
make
it
more
useful.
Don't
forget
to
to
explain
that
third
criteria
is
and
there
we
will
be,
assessing
your
skills
as
a
contributor.
Where
will
we
have
the
best
return
on
the
mentoring
investment
if
we
have
two
equivalent
projects
and
two
equivalent
proposals.
B
If
one
project
will
require
an
involvement
of
the
mentors
of
let's
say,
10
or
15
hours
a
week
and
on
the
other
side
we
have
a
contributor
who
we
assume
that
he's
self-sufficient,
that
he
knows
so
we
don't
need
to
explain.
For
instance,
what
is
a
unit
test
or
or
a
ski
can
solve
simple
problems.
I
will
prefer
to
select
this
contributor
because
we'll
we
then
with
the
mentorship,
a
a
capital
that
we
have.
We
can
go
further
and
and
go
farther
in
the
in
the
project.
Did
I
answer
the
question.
F
No
I
think
so.
Some
people
were
also
asking
about
building
the
Jenkins
muscle
and
Mark's
suggestion
was
to
use
improve
a
plugin
tutorial
for
giant
Skin's.
Plugin
and
I
still
have
lots
of
things
to
learn
about
Jenkins,
but
this
part
helped
me
quite
a
lot
and
there
was
a
previous
suggestion
for
Mark,
which
is
go
ahead
and
try
Jenkins
on
your
own
use,
Jenkins
to
build
a
project
that
would
be
useful
for
you.
That's
what
I
do
on
a
daily
basis
to
progress
on
my
knowledge
of
Jenkins.
F
So
yes
go
ahead
with
the
improve
a
plug-in
tutorial,
install
Jenkins
on
whatever
machine.
You
have
be
it
your
laptop
Mac,
Windows,
Raspberry,
Pi,
whatever
even
Oracle
feature
it
works
just
about
everywhere,
so
go
ahead
and
try
that
so
that
you
will
build
the
two
kinds
of
muscles:
the
muscles
for
improved
playing
tutorial
and
the
muscles
of
using
Jenkins
on
a
daily
basis.
F
G
Healthy
self-interest
in
this
case
is
a
way
of
saying
do
something
that
is
interesting
to
you
and
use
Jenkins
to
help
you
do
it.
So
if
you
have
an
assignment
at
University
that
is
write
some
Java
program
or
write
some
c-sharp
program
or
write
some
python
or
some
NP,
some
node.js,
whatever
you've
got
some
assignment
in
solid
Jenkins
controller,
and
let
it
help
you
build
that
thing
you
learn.
It
helps
a
little
bit
and
you've
now
used
what
you
already
know.
B
Well,
I
just
opened
a
chat,
I've
seen
a
question
from
udit
about
joining
discourse
and
get
her
I
agree
with
Bruno,
but
they're
complementary.
So
there
are
two
different
ways,
so
you
don't
have
to.
But
it's
it's
good
to
have
a
foot
in
in
both
so
depends
how
much
time
you
have
are
there
other
questions?
I
see
there
have
been
quite
some
activity
in
the
in
the
chat,
so
don't
be
shy.
H
B
B
I
would
recommend
the
following,
so
connect
and
register
to
discourse,
so
the
community.jenkins.io
they're,
interesting
announcements
that
are
made
there
connect
to
it.
Look
if
it
works
for
you
if
it
doesn't
work
for
you
just
leave
it
alone
so
and-
and
you
continue
using
gitter,
did
that
answer
your
question.
B
D
B
I
love
your
question.
It's
a
great
question,
so
the
short
answer
to
that
experiment,
how
it
works
and
what
works
better?
What
you
the
the
problem,
the
exposed
here
is
a
typical
problem
of
when
working
on
open
source
and
also
in
professional
career
when
you're
working
in
big
companies-
and
one
of
the
purpose
of
this
here-
is
to
learn
asynchronous
communication.
B
The
whole
communication
process
is
key.
Different
ways
to
communicate.
One
is
synchronous.
This
is
what
we
have
now.
We
have
a
meeting,
but
you
have
to
stay
late
in
the
evening
or
people
like
Alyssa
need
to
wake
to
wake
up
in
unruly
times
very
early
for
her
or
or
it
I
need
to
work,
and
so,
but
you
can
exchange
a
lot
of
information
synchronously
in
a
meeting
or
in
a
chat
where
you
have
a
immediate
interaction
and
where
you
have
Rewards.
B
On
the
other
side,
you
will
have
different
type
of
answers
and
very
often
better
answers.
If
you
really
go
into
the
asynchronous
a
way
of
working,
it
has
other
requirements,
but
you
reach
a
bigger
crowd
of
people
that
way.
That
means
that
you're
going
to
reflect
on
how
you
ask
your
question
and
you're
going
to
receive
an
answer
several
hours
afterwards.
D
Yes,
sir
I
got
it
now,
I
won't
be
thinking
should
I
answer.
That
question
put
the
question
later
in
my
mind,
at
my
time
or
in
the
morning,
because
generally
you
might,
you
guys
also
might
be
having
holidays,
so
it
won't
guarantee
an
answer
to
me.
I
will
take
care
of
it
and
I'll
I'll
make
sure
to
master
both
the
ways
of
communication.
As
usual.
Thank.
B
D
B
D
B
G
G
So
but
that's
that's
the
same
that
you
get
in
any
use
of
of
any
bug,
tracker
right,
right,
good
bug
reports,
the
permissions
are
generally
pretty
pretty
open
on
the
Jenkins
jira
and
it's
intentionally
so
so
you
can
make
comments
anywhere
you
can
assign
bugs
to
yourself
at
any
time.
You
just
need
an
account
once
you've
logged
in
you
can
assign
things
and
you
could
work
on
them.
Don't
be
shy
about
doing
that
if
and
don't
be
assigned
a
shy
about
unassigning
it
if
you
decided
I,
don't
want
to
work
on
that
anymore.
B
So
we'll
slowly
have
to
wrap
up
so
I'm
personally
very
happy
to
meet
you
and
and
to
start
this
journey
together
with
all
of
you,
remember,
I
will
I'm
sorry
to
be
Church
there.
I
will
not
answer
requests
to
do
one
on
one
discussion,
there's
only
one
exception
to
that
I
explain
it
another
time.
It's
not
the
purpose
here.
So
I
will
not
accept
these.
Ask
your
questions
publicly
so
that
everybody
can
learn
from
your
question
and
you
will
learn
from
the
questions
that
other
are
asking.
B
The
next
step
now
is
good
good
luck
in
bunkuraj
I,
don't
know
how
you
say
that
in
English,
but
be
be
strong
in
building
your
Jenkins
muscle
and
will
organize
another
Interactive
synchronous
meeting
somewhere
in
the
middle
of
January,
where
we'll
go
more
in
details
on
the
project,
ideas,
give
explanations
and
answer
any
questions
on
them.
Stay
tuned
on
guitar,
end
on
on
the
gsoc
channel,
on
guitar
and
on
not
Confluence
on
community.jenkins,
IO
and
Twitter
for
announcement
when,
when
this
will
happen,.