►
From YouTube: GSoC Office Hours - August 18, 2022
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Here
we
go
good
evening
good
afternoon
good
morning,
everybody,
this
is
august,
18th
gsong
office
hour,
global
one,
hello,
hello,
everybody
joining,
and
let's
start
so.
The
first
point
I
wanted
to
to
discuss
or
or
to
raise
was
that
I
think
now
is
a
good
moment
that
the
projects
are
advancing
very
well
and
we're
slowly.
A
Reaching
the
end
of
this
campaign
is
that
it
would
be
a
very
good
idea
that
every
project
would
write
blog
posts
on
the
jenkins
io
community
blog
to
describe
in
word
format
what
the
project
is
about
to
give
some
explanation
about
the
the
project.
This
would
be
a
compliment
to
the
jenkins
online
meetup.
A
We
had
some
time
ago.
A
I
have
some
suggestion
for
the
topics.
So
500
words
depends
how
you
count
them.
This
is
about
a
page,
a
page
and
a
half
a
maximum,
and
besides
describing
what
the
project
does.
A
It
would
be
interesting
to
explain
in
a
couple
of
words
why
the
project
is
important
for
the
jenkins
community
or
would
it
brings
to
the
community
and
another
topic
idea
is:
why
is
it
or
was
it
important
to
you
as
a
so
contributor
couple
of
words.
A
What
you
learned
or
what
it
is,
what
you're
learning
right
now
is
we're
still
busy
with
that
with
the
projects.
The
the
purpose
of
that
is,
it's
a
way
to
communicate
and
explain
a
couple
of
things
to
future
gsoc
candidates,
because
we
we
start
to
have
people
interested
in
the
next
gsoc
campaign.
A
Clarifications
regarding
this
recommended
blog
post.
B
Yeah
I
do
like,
should
the
contributors
include
the
code
products
as
well.
B
B
A
B
A
Everything
everything
that
could
be
useful
for
the
community
and
the
passerby
to
to
to
learn
more
so
to
go
deeper.
We
don't
want
to
scare
the
people
by
having
three
or
four
pages
to
wade
through
to
understand
what
it's
talked
to,
but
it's
it's
always
a
good
idea
to
have.
A
C
A
For
how
to
proceed,
what
is
the
magic
required
for
proposing
a
blog
post
on
jenkins.io?
Your
mentors
can
can
help
you
with
that.
There
is
also
the
contributing
page
on
the
jenkins
io
page
or
repository.
A
Okay,
good:
we
have
two
projects
being
present
here:
three,
which
is
third
one
yeah.
A
You
just
sneaked
in
so
on,
okay,
good
evening,
so
we'll
so
we
have
three
projects
and
we'll
start
with
the
viejan
jan
tell
us
where
you
standing
what
you
you
achieved
and
where
are
you
heading
to
so
the
usual
roundup.
B
Yeah
hi
everyone,
so
in
this
week
I
was
able
to
create
a
draft
build
request
for
the
changes
that
I
have
proposed
last
week
and
the
changes
are
getting
built
nicely.
So
no
errors
with
that
and
for
the
draft
pull
request.
You
are
also
planning
to
add
the
instructions
for
the
readme
so
that
I've
done
today
and
along
with
that,
we
also
throw
in
some
tests
that
will
test
the
new
processing
layer
and
that
would
basically
sum
up
the
entire
per
request
and
then
it
would
be
merged.
B
And
after
that
we
plan
to
add
the
last
feature.
That
would
be
to
get
the
plugin
names
from
which
each
parameter
of
a
step
is
coming.
So,
for
example,
if
we
have
an
scm,
we
have
something
like
git
scm.
So
once
the
user
clicks
on
that,
so
now
it
will
be
applicable
link
which
leads
to
a
new
page.
So
once
you
click
on
that,
the
user
should
see
that
okay
yeah
this
parameter,
this
class
is
coming
from
the
git
plugin.
So
we
are
working
around
the
page
to
do
that,
but
other
than
that
I
think.
A
A
D
So
so
recently,
I
worked
mostly
about
my
documentations
and
useful
examples,
so,
firstly,
I
created
the
documentation,
demos
and
the
detail,
the
plane
and
how
I
will
develop
with
my
documentation,
which
includes
user
guide
and
developer
guide
or
something
similar
so
because
we
decided
to
host
all
the
documentations
in
the
github
pages.
So
I
need
to
write
a
detailed
plan
in
the
demo
and
about
how
I
want
to
implement
it.
So.
Secondly,
I
created
several
useful
examples
for
the
users,
so
they
can
get
started
in
our
actions
quickly.
A
Okay
and
no
impediments,
I
think
everything
is
under
control
yeah
for
your
project,
that's
very
good!
Okay.
That
sounds
sounds
good.
Thank
you
for
the
update
jimmy
the
last
one.
We
have
un
unless
somebody
else
sneaks
into
the
meeting.
A
C
This
week
I
work
persisting
the
maintenance
records
into
an
xml
file,
so
after
each
maintenance
task
is
run
on
a
cache.
I
store
all
that
data
into
an
xml
file
on
the
jenkins
controller.
After
persisting
the
data
into
an
xml
file,
I
also
created
a
table.
I
also
created
a
table
to
display
the
maintenance
records,
so
this
table
contains
pagination,
sorting
and
also
a
search
functionality.
C
So
that's
what
I've
been
I
you
know
I
worked
the
previous
week
I'll
have
to
improve
the
performance
of
how
things
are
being
done,
because
behind
this
was
only
a
way
to
connect
things
and
you
know,
integrate
and
finish
the
functionality,
but
behind
the
scenes,
the
performance
isn't
that
great,
so
I'll
have
to
create.
You
know,
think
of
a
way
to
improve
performance
and
improve.
You
know
the
overall
functionality
of
this
feature.
A
Good
advice-
and
I
hope
you
will
remember
that-
is
when
you're
working
on
something
like
yes,
like
that
first
implement
the
feature
note
that
the
performance
is
is
not
as
expected
and
then
only
work
on
improving
fine-tuning
and
eventually
refactoring
the
code
to
improve
performance.
A
C
A
It's
it's
it's
a
lesson
and
you
experience
that
and
and
think
about
about
that
tip,
but
try
to
do
it
sequentially,
it's
it's
a
general
advice.
That's
very
often,
given
people
get
lost
in
trying
to
improve
performance
while
they're
still
building
and
they
lose
oversight,
justice,
a
small
tip
based
on
my
experience,
do
you
want
to
add
something
else:
washi
cache.
C
A
Nothing.
No,
it
sounds
good
too.
So
I'm
very
very
happy
to
hear
these.
These
updates
well
done.
Congratulations.
A
Everybody
vihan
shared
the
link
to
the
contributing
document
of
jenkins
at
io
and
how
to
add
a
blog
post,
and
I
added
it
to
the
meeting
notes
here.
So
the
link
is
available.
There
is
there
another
subject:
question
comment
that
somebody
would
like
to
discuss
or
raise.