►
From YouTube: GSoC 2023 Office Hours - March 2, 2023
Description
Jenkins in GSoC project idea presentation:
* Plugin installation manager tool improvements
* Building jenkins.io with better tools
* Screenshot automation for Jenkins documentation
A
So
just
a
word
of
introduction.
Welcome
to
everybody
interested
in
participating
in
Google
summer
of
code.
Thank
you
to
be
part
of
this
Great
Adventure.
Just
a
little
reminder.
This
office
hour
will
be
held
every
week
at
this
time,
normally
limited
to
half
an
hour,
but
these
weeks
will
have
more
substantial
meetings
to
answer
questions
and
to
give
more
details
on
projects,
so
we're
not
going
to
spend
too
much
time
in
general
stuff,
so
I'll
walk
quickly
through
them.
A
So
first
important
thing
I'd
like
to
share
with
everybody,
is
that
during
this
proposal
time
where
everybody
is
competing
by
writing
his
proposal,
we
want
a
fair
treatment
of
everybody,
and
this
means
that
we're
not
going
to
engage
in
no
Mentor
will
engage
in
private
discussions
or
answering
private
questions.
Questions
should
be
asked
publicly
and
will
be
answered
publicly.
It's
not
that
we
are
ignoring.
You
are
receiving
rights.
A
A
Don't
forget
also
be
to
have
a
substantial
proposal.
You
need
to
exercise
your
G-Shock
muscle.
Important
thing
is
that
you
do
a
pull
requests
and
especially
in
the
domain
where
you
want
to
to
apply,
you
need
to
have
a
good
understanding
how
it
works
and
also
show
that
at
least
you
can
do
the
the
the
simple
things
or
that
you
know
the
the
grammar
of
how
things
work
and
that
you
know
how
to
do
it.
A
A
A
Do
that
exercise
as
soon
as
possible.
You
will
have
the
best
proposal
and
the
strongest
one
to
compete.
The
last
point
I
would
like
to
do
before
getting
to
the
hardcore
agenda
of
this
meeting
is
that
this
year
they
are.
There
are
a
lot
of
people
interested
in
participating
to
Google
summer
of
code.
This
is
great.
There
is
a
lot
of
enthusiasm
and
energy
and
is
very
rewarding
for
everybody.
A
I
just
want
to
warn
that
we
have
only
a
limited
capacity
of
mentoring
projects,
and
this
will
make
that
we'll
have
to
make
decisions
on
how
many
projects
will
be
able
to
field.
Actually
they
will
there
might
be
some
reshuffling
of
the
mentorship
and
we're
only
going
to
choose
the
best
proposal,
so
there
is
also
the
competition.
A
This
doesn't
does
not
mean
that
you,
as
a
candidate
are
not
good,
are
not
worth
it
or
that
you
should
change
career
erections
or
things
like
that.
Not
at
all
it's
at
this
stage.
It
didn't
work
out
I'm
open
for
discussions,
one.
The
selection
has
been
done
to
give
personal
advice
to
people
and
guide
them
how
they
can
prepare
even
better
and
use
the
time
to
learn
about
open
source
and
get
more
up
to
speed
and
have
a
better
chance
to
to
participate
to
Google
summer
code.
A
It
would
not
be
fun
for
me
or
us,
as
org
admins,
to
have
to
tell
people
here.
You
had
a
great
proposal,
but
we
had
to
choose
and
you
didn't
make
it
so
I
I
apologize
in
advance
for
that,
but
we're
together
to
to
build,
and
there
will
be
great
opportunities
to
continue,
help
and
learning
and
and
having
other
opportunities.
A
A
So
before
we
start,
I
just
would
like
the
mentors
that
are
online
in
this
meeting
either
for
these
three
projects,
or
eventually
for
other
projects
to
step
forward,
say
a
word
and
present
so
I'm
going
to
pick
and
then
because
I
I,
don't
remember
all
the
names
I
know,
Mark
Wait
will
be
mentoring.
Oh
is
is
available
to
Mentor
one
project
and
he's
interested
in
several.
So
can
you
present
yourself
in
a.
B
Couple
of
words
sure
I'm
Mark
Waite
I'm,
the
maintainer
of
the
Jenkins
git
plug-in
I'm,
a
member
of
the
Jenkins
governing
board
I've
served
in
the
past
as
Jenkins
documentation,
officer,
I'm,
part
of
the
platform
Sig.
So
I've
got
a
lot
of
things
that
I
I
find
interesting
in
Jenkins,
documentation,
Jenkins,
core
git
and
all
those
things
mean
that
I've
got
far
more
ideas
than
I
have
time,
and
that
means
that
I
will,
as
John
Mark
said,
Mentor
one
project
for
Google
summer
of
code.
C
Yeah
hi
hi
everyone,
I'm
film
and
I've,
been
entering
the
plugin
installation
project.
I
am
actually
I'm
actually
here
I,
just
to
give
like
you
know,
guidance
to
all
the
new
upcoming
open
source
contributors,
because
I
feel
that
I
have
a
lot
to
share
here.
I
have
a
lot
to
share
from
my
past
to
XP
I
mean
past
few
years
of
experience
in
open
source
in
Google
summer,
of
course,
specifically
so
I'm
just
here
to
like
learn
and
at
the
and
at
the
same
time
also
teach
others.
D
A
E
A
G
Yeah,
hello,
everyone,
so
my
name
is
Adrian
I've
been
in
the
Jenkins
Community
for
last
10
years
or
more
even
more
now,
I've
been
maintaining
plugins
I've
been
helping
people
use
plugins
and
Jenkins
instances
for
more
than
more
than
10
years,
and
now
I'm
walking
almost
full
time
on
the
plugin
as
scoring
project,
and
that's
why
I'm,
mentoring
and
purposing
comment
on
two
ideas
on
that
subject,
which
we
are
discussed
on
Tuesday.
So
I
won't,
maybe
not
repeat
myself
but
come
come
back.
A
F
I
suppose
I'm
here,
John
Mark
hello,
everyone
I
work
closely
with
Adrian
on
the
plug-in
Health
scoring
project.
I
was
a
mentor
last
year
on
that
excited
to
bring
those
projects
forward.
This
year
excited
to
see
the
contributions
there.
Jenkins
has
I've
been
working
with
Jenkins
for
the
last
two
years,
I
think
it's
consumed
my
life,
so
yeah
looking
forward
to
working
with
all
of
you.
H
I
Hello,
everyone,
so
this
is
Rajiv
I'm,
a
software
engineer
I
graduated
last
year,
so
I
was
a
G-Shock
student
with
Captain
project
and
I
think
this
is
a
time
to
contribute
back
to
the
community
and
Mentor
some
people,
so
even
the
last
year.
Okay,
so
I'm
entering
for
the
project,
building,
Jenkins
IO
with
alternative
tools
and
I.
A
J
Okay,
okay
yeah,
so
this
is
logi,
so
I'm
a
potential
Mentor
for
the
exponential
back
off
and
cheetah
for
age
and
reconnection
this
year
and
I
am
a
former
jsoc
student
from
2020.
So
I
know
how
students
are
struggle
to
get
into
this.
She
sock
at
first
and
so
I'm
here
to
help
and
learn
with
them
and
yeah
happy
to
see
you
all
I
can
see
some
long
faces.
Yeah
it's
great
to
meet
you!
Okay,.
A
A
Okay,
so
thank
you,
everybody
for
joining
as
mentors
and
especially
as
contributors
and
people
interested
in
Google
summer
of
codes
in
in
Jenkins.
So
thank
you
very
much
for
for
that,
and
it's
a
good
choice
to
be
here.
So
we'll
start
with
the
first
project
idea
of
today,
the
plug-in
installation
manager,
tool,
improvements,
I
think
Mark
you're,
going
to
present
that.
B
So
the
let's
first
do
it
an
introduction.
What
is
the
plug-in
installation
manager
tool?
What
it
is
is
a
Google
summer
of
code
project
from
2019.
in
2019.
We
had
this
idea
that
we
would
really
like
to
be
able
to
replace
the
replace
or
duplicate
the
features
that
are
included
in
the
Jenkins
plugin
manager
inside
the
Jenkins
product
itself
inside
the
Jenkins
War
file.
B
You
would
like
to
do
as
part
of
a
Google
summer
of
code
project.
You
will
need
to
learn
more
about
plug-in
installation
manager.
You'll
need
to
learn
more
about
how
Jenkins
does
plugins
right.
There
are
Concepts
associated
with
Jenkins
plugins,
which
are
rather
different
than
other
dependencies,
and
so
you'll
you'll
learn
a
number
of
things
as
you
investigate.
This
propose
make
your
proposal
prepare
ideas
Etc.
B
So
if
we
look
at
the
issue
tracker-
and
let's
just
look
for
now
at
enhancements,
so
there
are
actually
some
bugs.
That
may
also
be
be
good
things
for
you
to
consider,
but,
for
example,
here's
here's
right
at
the
very
top
generate
a
plugins
lock
file
from
a
list
of
plugins.
So
what
this
user
is
suggesting
is
they
would
like
a
way
for
the
plug-in
installation
manager
tool
to
generate
a
prototype
of
its
own
configuration
file
based
on
existing
directory,
and
it
almost
does
it,
but
not
quite
and
almost
is
not
enough.
So
this.
B
B
Sometimes
I
write
things
in
my
plugins.txt
file,
which
matter
to
me
and
those
things
that
I
write
I
don't
want
to
lose,
but
when
doing
this
round
trip
technique,
I
may
lose
those
those
comments.
So
this
is
again
an
interesting
and
useful
suggestion
what
to
do
with
plug-in
installation
manager
tool
how
to
improve
it.
B
Proxy
support
is,
is
sort
of
a
a
strong
request
for
many
people,
because
many
times
they're
sitting
behind
someone's
corporate
configuration
and
that
corporate
configuration
requires
specialized
proxy
variables
or
specialized
proxy
username
and
password
or
or
some
other
novel
or
exotic
thing.
Each
of
those
things
could
be
a
very,
very
interesting
and
useful
addition
to
to
the
plug-in
installation
manager
tool
as
another
example.
Okay,
this
one
is
one
that
I
like,
because
I
spend
a
lot
of
time
in
maven
add
a
facility
to
take
a
pom
file
as
input
to
the
tool.
F
B
Okay,
I
successfully
coughed
without
coughing
in
all
of
your
ears,
I'm
proud,
that's
great
all
right.
So
today
we
have
several
different
input.
Formats
I
can
use
a
simple
ASCII
text
file.
A
simple
text
file
that
uses
specifically
formatted
lines.
I
can
use
a
yaml
file
with
specific
data
formats.
What
this
is
suggesting
is
hey.
Give
another
idea
of
a
way
to
to
use
a
this
input
format
maven
to
do
a
proposal
for
I
want
this.
Plugin
I
want
this
plugin.
Now
there's
some
there's
some
challenges
hiding
here.
B
As
with
any
of
these,
a
Jenkins
plug-in
has
an
artifact
ID,
but
really
the
group
ID
I'm,
not
sure
how
relevant
that
is
in
this
case,
because
Jenkins
itself
doesn't
honor
so
so
interesting
challenges
here
and
useful
things
that
would
be
added
to
the
plugin
installation
manager
tool.
Now
I've
talked
already,
probably
more
than
I
should
have.
Are
there
any
specific
questions
that
any
of
the
anyone
wants
to
ask
that
we
might
dive
into
specific
questions
around
plug-in
installation
manager,
tool.
A
B
B
This
one
was
a
potential
Google
summer
of
code
contributor,
who
said
I
want
to
try
something
and
started
the
pull
request
and
I
reviewed.
It
gave
some
comments
asked
for
some
changes.
The
changes
have
come
back
and
now
I've
got
to
do
another
review,
that's
what
I
get
for
taking
time
off.
So
that
is
one
way
to
you.
Look
at
the
issue
list.
B
Consider
which
ones
are
interesting
include
those
in
The,
Proposal
and
prioritize
them
based
on
your
perception
of
preferably
hey.
This
would
be
a
good
one
to
get
started.
This
one
would
be
a
good
one
to
to
be
sure
that
I
understand
it.
This
one
would
be
a
good
one,
that's
more
difficult
and
then
maybe
two
or
three
at
the
end,
which
say-
and
here
are
some
alternates
in
case-
one
of
these
gets
solved
in
the
interim
and.
A
Did
really
show
that
the
substance
of
the
issue
was
understood
and
that
you
come
already
with
I
I
will
tackle
it
that
way.
That
way,
this
is
the
danger
zone
or
the
things
that
are
unclear.
So
it's
not
just
listing
issue.
One
issue,
two
issue.
Three,
it's
really
discussing
the
issue
and
come
with
the
plan
is:
is
that
what
happened?
It.
B
Is
well
and,
and
one
of
the
things
that
I
as
an
evaluator
of
project
proposals
will
be
doing,
is
I'm
looking
for
the
technical,
technical
content
of
The
Proposal.
That
tells
me
that
the
person
has
done
the
research
to
be
able
to
show
that
they
can
be
successful.
Doing
this
so
I
acknowledge
this
is
this
is
real
work
and
in
fact
the
nice
thing
about
it
is
for
the
Jenkins
project.
As
you
do
this
real
work
you're
actually
helping
the
project.
B
A
B
It
is
okay,
and
so
that
John
Mark
I
think
that's
worth
noting.
Why
why
this
matters
to
me
and
why
it
matters
to
the
Jenkins
project,
so
the
plug-in
installation
manager
tool
is
used
very
very
widely
because,
among
other
things,
it's
bundled
into
the
Jenkins
container
images.
So
when
a
Jenkins
controller
at
company
XYZ
is
configured
to
use
Docker,
they
will
typically
configure
it
to
use
a
very
specific
set
of
plugins
and
the
reason
they
can
do
that
is
because
of
this
tool.
B
A
It
is
also
possible
to
ask
questions
through
the
getter,
the
main
guitar
Channel,
there's
no
specific
Channel
yet
for
this
project
so
use
the
main
goal
sum
of
code
Sig
or
use
community.jenkins.io,
which
has
a
lot
of
benefits
right
of
using.
We
have
two
more
minutes
for
that
project,
so
we're
waiting
for
questions.
B
So
so,
okay,
while
in
those
two
minutes,
I,
have
to
have
to
highlight
a
way
that
Chris
and
I
did
it
Chris
and
I
Chris,
Stern
and
I
as
part
of
a
documentation,
office
hours
some
weeks
or
months
ago,
actually
went
through
the
list
of
of
enhancements,
and
we
gathered
ideas
that
we
thought
were
interesting
into
this
page.
By
all
means
you
can
use
our
work
where
we
thought
these
were
interesting
right
by
all
means
use
those
as
suggestions.
B
Very
good
question,
so
so
the
way
I
interpret
your
question
is:
should
you
should
your
proposal
include
this
entire
list?
If
it
did,
I
would
discount
your
proposal
as
not
having
not
being
a
realistic
proposal.
I
don't
expect
any
Google
summer
of
code
project
could
implement
this
entire
list.
There's
just
too
much
work
hiding
in
those
things,
so
you'll
have
to
choose
a
subset
or
even
items
that
may
not
be
on
this
list.
Your
exploration
will
help
you
decide
which
items
from
this
you
should
choose
as
part
of
the
subset.
B
K
B
Good
well,
and-
and
you
make
a
good
point-
our
initial
proposal
for
this
was
that
it
would
be
a
175
Hour
project
and
175
hours,
while
that
may
sound
like
a
lot
in
terms
of
the
working
world.
That's
only
four
weeks
of
full-time
work
in
the
United
States
at
40
hours
a
week,
so
it's
actually
not
as
much
time
as
you
might
think
over
a
summer,
it's
about
20
hours
a
week
for
three
months,
but
it's
not.
A
B
Yes,
all
right
doing
code
reviews
from
other
people's
proposals
yeah.
There
are
all
sorts
of
things
that
that
will
make
make
the
that
will
fill
the
time
for
the
Google
summer
of
code
project,
certainly
so
definitely
choose
only
a
subset
of
those
ideas
and
choose
the
ones
that
you
think
would
be
most
valuable
part
of
that
learning
process.
Reading
the
issue
descriptions
trying
to
understand
them
exploring
experimenting
with
it
will
help
you
understand
how
people
use
this
tool
now
and
why
they
would
care
about
these
different
things.
B
A
B
H
Oh,
you
can
share
your
screen.
Yes,
I'm
just
going
to
look
at
this
page
anyways,
it's
like,
let's
see
so,
let's
maybe
go
to
yeah.
That's
good!
That's
good
is
good.
So
for
this
project
the
main
purpose
is
to
replace
Austrian,
which
is
the
tool
we're
using
to
build
ASCII
dogs
sources
from
Hammer
templates
and
yeah
whatever.
H
The
hard
part
is
for
the
front
end,
so
it's
like
to
make
it
look
like
to
make
the
site
look
like
what
we
have
now,
which
I
can
start
IO.
It
may
take
a
while
to
to
get
the
layout
and
the
visuals
like
really
perfect,
and
maybe
maybe,
as
you
go
to
GitHub
issue
5474.
So
if
we
head
to
that
issue,
we
should
be
able
to
see
if
we,
if
it's
going
down
a
bit
to
I,
think
it
to
a
bit
down
yeah
right
here.
H
So
we
see
if
you
look
at
the
fallings
provided
by
base
battle.
These
are
the
prototypes
for
what
he
has
tried
before
to
so.
Essentially,
what
Basel
did
was
he
spent
I
think
according
to
what
he
told
us
a
while
back
before
he
spent
a
couple
of
hours
during
lunch
time
to
come
up
with
prototype
just
for
user
handbook
alone.
If
my
memory
is
accurate,
but
we
can
see
here,
besides
user
handbook,
we
also
have
dog's
site
yep
that
one.
H
A
H
B
H
H
It
will
be
all
in
adox
and
maybe
possibly
yaml
files,
but
no
Hammer
valves
as
we
currently
have
now
because,
like
I
think
it's
because,
like
Australia
uses,
Ruby
and
Ruby,
it
uses
Ham
versus
template,
but
that
will
no
longer
be
the
case
here.
I'm
saying
this
is
I'm,
saying
this
because,
like
someone
it
mentioned,
did
ask
about
this
on
getter
before.
B
And
so
so
Chris
one
of
the
challenges
there.
So
that's
that's
focused
intentionally
on
the
user
handbook
right
where
the
user
handbook,
we
think,
can
be
generated
without
needing
the
custom
custom
things
that
are
in
the
handles,
whereas
developer
handbook
I
know
is
dependent
on
it
and
security
advisories.
These
all
depend
on
it.
So
so
it's
effectively,
this
project
is
not
just
a
generate
the
site
using
antora.
It's
separate
the
site
into
more,
more
broadly
separated
components
where
user
handbook
becomes
its
own
component
and
is
version
specific,
but
the
others
don't
right.
So
so
this.
H
H
So
it
could
be,
but
the
most
basic
point
we
need
to
work
on
this
user
documentation
with
versioning
and
for
the
second
part,
would
be
the
developer
documentation.
The
one
you
mentioned
before,
which
strongly
depends
on
the
handbook
files
as
templates,
but
we
have
to
if,
if
we're
going
to
just
like
go
event,
or
we
have
to
come
up
a
way
to
to
rebuild
that
as
well,
so
we'll
ask
to
win
with
the
dependency
on
animal
files,
and
the
third
point
is
to
build
the
block
using
SP.
B
H
K
H
Second
part:
it
I
think
we
can.
We
can.
We
can
have
like
the
block
two
depends
but
or
the
development
developer,
documentation
that
that
is
the
ordering
for
the
second
and
third
is
not
as
important
great
and
if
we
can
go
down
to
Quick
Start
so
for
to
start
this
project,
it's
recommended
to
find
some
good
first
good
dishes
in
the
jungle
style
repo
and
to
like
yep
but
I
think
like
for
now.
We
we
have
like.
We
still
have
some
good
first
issues,
so
it's
like.
H
A
H
Yep,
so
next
be
besides,
like
submitting
a
good
PR
would
be
to
explore
the
Jenkins
Island
components,
repo
that
that
part.
It's
separate
from
the
chances
because,
like
that's
Ripple,
as
for
all
the
web
components
that
we
see,
that
includes
the
header,
footer
and
other
components
as
well
across
different
changes.
The
Isle
sides.
B
Yeah
so
Chris
are
you?
Okay,
if
I
open
up
the
example
to
show
what
this
one
is
just
so
people
are
aware,
so
when
I
open
up
jenkins.io
here's
the
page
that's
presented
to
me
right.
This
looks
like
a
single
unified
site
and
when
I
click
on
documentation
and
go
to
One
Piece.
Oh,
it's
still
the
same
top
level
header.
It
still
has
the
same
footer
on
it.
B
Now
when
I
go
to
plugins,
oh
hey,
the
header
is
slightly
changed,
but
same
content
in
the
header
and
same
content
in
the
footer,
because
it's
using
a
web
component
for
the
header
and
the
footer,
and
so
so
the
benefit
of
that
header
and
footer
technique
is
and
as
we
split
this
site
as
this
site
becomes
more
and
more
component.
So
if
blog
eventually
becomes
generated
from
its
own
set
of
repositories,
its
own
tools,
it
will
still
have
the
same,
look
and
feel
because
of
these
top
level
web
components.
A
Okay,
Mark
and
Chris
I'm
going
to
pause
for
a
second,
because
I
need
to
keep
the
things
on
on
on
the
rails
here.
So
thank
you
very
much
before
going
to
questions
on
that
topic.
If
contributors
have
specific
questions
and
they
don't
feel
that
it's
not
working
efficiently
to
get
the
answer
or
to
discuss
ideas
on
guitar
or
community.jenkins.io,
you
can
also
propose
or
request
to
have
dedicated
projects
online
meetings
where
you
can
interactively
discuss
and
explore
play
with
ideas.
This
can
also
be
done,
so
we
don't
need
to
stay
in
this
format.
A
B
To
say
something:
no,
no
just
I
think
actually,
if
there
are
no
questions,
I've
certainly
been
pleased
with
the
boldness
and
the
creative
creative
genius
applied
by,
for
instance,
vandit
and
several
others
who
were
attending
with
us
today
have
submitted
pull
requests
to
the
jenkins.io
documentation
site
for
things
that
I
thought
were
really
quite
Advanced
and,
and
so
well
done.
That's
great.
B
My
apologies
that
they're
not
yet
reviewed
and
finally
merged
vandeep,
for
instance,
picked
up
the
upgrade
guide,
which
I
thought
was
a
major
huge
Challenge
and
has
started
a
very
nice
work
on
it.
So
there
are
ways
that
you,
as
Google
summer
of
code
candidates,
can
learn
things
about
the
sites
and
also
help
the
project.
A
B
Now
screenshots.
Oddly
enough,
are
a
very
common
thing
in
user
interface,
test
automation,
tools
like
selenium
or
Cyprus
do
navigate
web
pages
and
do
perform
screenshots
of
those
of
those
things.
What
this
proposed
was
hey.
Couldn't
we
take
some
form
of
description
of
the
steps
required
to
reach
a
particular
UI
put
that
into
the
documentation
as
a
comment
and
then
use
those
comments
in
that
documentation
to
drive
a
tool
that
would
capture
the
screenshots
based
on
the
latest
Jenkins
Jenkins
release.
B
A
B
A
M
A
A
B
Sure
the
the
current
process
is,
we
find
the
screenshots.
We
tell
someone
please
go
recreate
that
in
Jenkins
and
use
a
screenshot
tool
on
your
computer
to
take
the
screenshot
and
then
submit
it
as
a
pull
request
to
the
to
the
documentation.
Kevin
Martens
had
to
do
that,
he's
our
Jenkins
documentation
officer,
and
he
did
it
three
or
four
months
ago,
and
it
was.
It
was
a
useful
thing
that
he
did,
but
it
was
not
a
terribly
thoughtful
thing
that
he
did
right.
It
wasn't
filled
with
more
sexual
activity.
Okay,
John
Mark
said
the
word.
B
B
B
L
Yeah
good
morning,
everyone
so
I
have
one
question
like
what
is
the
scope
of
this
project
like,
for
example,
one
can
be
just
take
the
screenshot
and
save
it
to
a
folder
like
some
resource,
slash,
image
or
or
it
can
be
like
taking
the
screenshot
and
updating
it
in
the
resources.
Also,
for
example,
if
we
change
the
version
of
the
Jenkins
in
the
jenkins.io,
then
image
will
automatically
get
fixed
and
it
will
show
up
in
the
website.
B
Okay,
and
so
so
good
good,
good
question,
so
the
Jenkins
documentation
site
is
intentionally
managed
as
a
static
site,
because
it's
a
static
site.
That
means
we
take
the
content
from
a
repository,
build
it
and
deploy
it
as
a
site.
So
what
we
would
want,
this
thing
to
do
is
submit
be
be
usable
to
submit
ultimately
pull
requests
to
the
Jenkins
documentation.
B
L
B
No,
the
image
comparison
here
is
I.
Think
the
the
purpose
for
calling
image
comparison
here
is
not
for
Speed
of
rendering,
but
rather
to
decide.
If
a
change
that
has
been
generated
is
a
relevant
change
or
not
so
conceivably.
If
a
change
was
three
pixels
of
colors,
it
changed
and
nothing
else.
It
may
not
be
relevant,
and
so
an
image
comparison
concept
might
be
needed
to
say,
hey.
Let's,
let's
do
something:
let's
choose
that
this
is
a
significant
change
or
an
insignificant
change.
There's
a
there's,
a
UI
automation,
tool,
I
think
called
zikuli.
B
That
does
something
like
this,
where
what
it
does
is
it
takes
pictures
of
your
entire
screen
and
then
tries
to
apply
image
comparison
techniques
to
decide
if
the
reference
screen
and
the
new
copy
are
actually
relevantly
different.
So
that's
what
I
think
it's
trying
to
say
when
it's
pointing
to
image
comparison
is
that
there
could
be
some
sophisticated
techniques
for
comparing
the
two
images
and
deciding
this
is
a
relevant
update
or
no
there's
not
enough
change
in
this
one
to
be
relevant
for
to
actually
justify
a
pull
request
to
to
update
the
content.
L
B
Okay,
now
I'm,
not
sure
I,
understood
I,
think
you
I
lost
some
some
sound
there,
a
breakup.
So
you
mentioned
videos,
and
this
thing
is
not
focusing
on
attempting
to
do
any
any
capture
of
videos
it
would.
These
would
be
static
screenshots.
Could
you
restate
your
questions
that
I'm
sure
that
I
understood
yes,.
A
A
M
N
A
N
Like
I
want
to
ask
okay,
like
we
have
a
quarry
like
in
into
this
particular
project
like
I,
get
the
idea
of
the
web
browser
automation,
because
currently
I
am
doing
the
Automation
in
my
internship.
So
it's
I
know
this
thing
and
I.
My
question
is
like:
where
do
I
start
so
that
I
can
prove
you
like
I
know
this
thing
so
I
can
do
it.
B
So
one
way
might
be
to
to
create
outline
what
you
think
the
human
readable
format
should
be
and
then
show
a
little
proof
of
concept
that
says:
hey
this
human
readable
format
and
whether
that's
capybara,
whether
that's
cucumber,
whatever
format
you
feel
that
is,
should
be
here's,
this
basic
format
and
here's
how
we
would
use
it.
Here's
how
a
user
would
do
it.
So
what
you're
doing
is
then
describing
here's
some
of
the
concepts
that
might
be
involved
in
doing
this.
N
Okay
and
I
want
like
there
is
one
more
curry
like
I,
am
not
new
to
this
and
I
joined
the
the
last
P
week
in
the
Jenkins,
so
should
I
like
okay
focus
on
this,
to
make
okay,
okay,
like
a
pro,
how
to
approach
like
this
project
or
should
I
like
okay,
contribute
to
like
issues
currently
like
issues
like
new
issues
in
the
Jenkins.
The
main
project.
B
You're
going
to
need
both,
so
the
the
bigger
challenge
for
me
is
assuring
that
that
your
project
idea
is
solid,
because
your
project
idea
will
be
evaluated
by
the
by
the
potential
mentors
and
we
will
read
your
project
idea.
You
need
to
be
sure
that
that
is
reviewed
and
discussed
in
the
group
that
it's
publicly
visible
Etc
all
the
good
guidance
that
John
Mark
has
offered.
B
K
B
So
so
is
it
mandatory?
No,
it
certainly
is
not
mandatory.
The
the
GitHub,
the
the
Google
summer
of
code
rules
don't
require
any
such
thing.
Is
it
very
wise
to
show
those
of
us
who
are
evaluating
your
project
idea
that
you
are
involved
enough
in
the
community
to
know
how
to
submit
a
pull
request
to
know
how
to
respond
to
feedback
to
know
how
to
get
that
pull
request
revised
so
that
it
finally
is
merged?
B
A
A
A
I
think
everybody
some
of
you.
It
has
been
very
late
in
the
time,
a
time
of
the
day
or
very,
very
early,
because
they're
on
the
west
coast
of
the
United
States.
So
thank
you
everybody
to
to
have
joined.
Thank
you
for
the
questions
and
the
energy.
That's
behind
that
I'm.
Looking
forward
for
a
great
summer
together.