►
Description
Recording of the Jenkins community bonding kick-off on May 19, 2021. We discussed the project selection results, thanked all participants, discussed next steps and the community bonding expectations.
A
We
are
live
hi.
Everyone
today
is
may
19th
and
after
a
short
break,
we
continue
the
summer
of
course
office
hours
just
to
explain
what
happened
during
the
smiles.
A
A
So
before
we
start,
I
just
want
to
thank
everyone
who
applied,
who
engaged
with
the
jinx
community
during
the
application
phase,
because
it's
really
important
that
we
don't
take
for
granted
the
time
where
you
invest
and
we
appreciate
all
your
contributions
and
the
participation
in
the
jinx
community,
which
today
we
will
talk
about
what's
next
and
what
you
can
do,
because
yeah
this
is
the
end
of
jesus.
It
doesn't
mean
that
it
has
the
end
of
your
participation
in
the
community.
A
There
are
other
programs
etc,
and
if
anyone
is
interested
in
the
call,
we
will
talk
about
that
and
yeah
what
else,
yeah
and,
of
course,
congrats
to
the
accepted
students.
So
please
welcome,
should
be
hardship.
I
keep
getting
a
detail
to
the
jenkins
community
and
if
I
pronounce
the
names
incorrectly,
please
let
me
know
because
they
will
adjust
but
yeah.
It
may
be
difficult.
A
A
So,
but
still
it's
google
summer
of
code-
and
we
are
looking
forward
to
it
and,
as
you
may
see
this
year,
we
have
a
number
of
projects
which
are
really
important
from
the
community
standpoint
from
the
jenkins
future
standpoint.
A
Three
of
these
projects
are
tightly
related
to
jenkins
and
the
cloud
including
cloud
events
jenkins,
remote
monitoring
with
parameters
and
also
security
for
validated
photogenic
kubernetes
separator.
So
these
are
topics
which
are
on
our
roadmap.
A
Maybe,
within
a
few
days,
this
time
allows
and
yeah
also
regarding
other
projects,
so
adidas
project
for
semantic
fashioning
plugin
is
important
in
terms
of
software
delivery,
lifecycle,
entity
and
delivery
pipelines,
because
there
is
two
to
nine
focus
on
continuous
delivery
of
jenkins
plugins
and
the
proper
version
is
essential
for
that,
so
that
it
is
convenient
for
users
and
this
project
is
steadily
aligned
with
our
goals
in
this
area
and
these
the
discussions
we
had
at
the
previous
contributor
summit
for
securing
pipelines
and
the
last
button
is
the
credentials
binary
project
so
well.
A
Git
credential,
git
plugin
is
used
by
pretty
much
every
jenkins
instance
in
the
world,
with
some
exceptions
and
yeah,
it's
a
core
functionality
of
genius,
even
it's
located
in
the
plugin
and
yeah.
It's
also
very
important
to
have
a
good,
plugin,
evolving
and
yeah
all
secrets
management.
Credentials.
Management
again
is
tightly
related
to
security
these
days
and
it's
very
important
to
change
this
users.
A
So
all
these
projects
are
very
important
and
we
think
we
are
happy
to
see
this
list
because
we
would
prefer
to
see
more
projects
this
year
we've
got
only
six
slots,
so
we've
been
able
to
accept
our
projects
and
we
can
talk
about
it
later
and
in
the
continuous
literature
foundation.
There
is
another
project
in
spinnercad
which
is
about
price
pinnacle,
so
then
you'll
call
you'll
be
working
on
that
yeah.
A
Of
course,
domain
doesn't
exist
because
it's
not
url
yet
so,
basically
they
are
trying
to
create
a
way
to
trial
spinnaker
quickly
and
see
how
it
works.
And
last
year
we
had
a
project
by
slaying,
numerous
about
custom
engine
distribution
service
which
allowed
to
quickly
build
custom
configurations
of
jenkins
and
maybe
try
jenkins
io
could
be
also
a
good
topic
for
the
next
projects,
whether
it's
gsoc
or
not.
So
it's
great
to
see
that
spinnaker
community
is
working
on
that.
A
So
these
are
current
projects
before
we
continue
adding
questions
comments
from
our
students
and
mentors.
A
Okay.
So
if
no
questions,
let
us
come
here
and
the
other
the
next
steps.
So
there
are
a
few
action
items
for
admins,
so
we
will
be
contacting
all
the
rejected
students
announced
that
we
would
be
doing
it
within
24
hours,
so
this
deadline
has
already
passed,
but
several
students
still
haven't
received
the
feedback.
Accordingly.
Apologies
for
that
there
will
some
events
which
yeah
that's
why
you
didn't
have
so
many
people
on
the
court
now
today,
but
yeah,
all
of
you
will
get
feedback.
A
You
have
collected
feedback
from
all
mentors
he's
been
processed
by
orphanage
and
you
will
be
differently
contacted
if
you
haven't
received
the
feedback
yet
so
we
also
work
with
other
orthodontists
and
these
other
community
members
to
see
whether
we
could
accommodate
projects
in
other
ways.
So
again
we
received
a
less
project
so
than
we
wanted,
but
we
for
particular
projects
and
particular
students.
We
will
look
for
alternatives
and
again
we
will
contact
you.
A
A
A
You
know
how
to
do
that
and
you
can
basically
start
coding
from
day
one
for
that.
Maybe
you
have
some
student
guidelines,
so
there
are
actually
student
and
mentor
guidelines
on
our
website
and
this
guidelines
also
describe
what
is
expected
during
the
community
bonding
phase.
So
if
you
haven't
read
these
documents,
please
do,
for
example,
for
students.
There
are
a
few
topics
defined
and
just
to
highlight
the
process
in
the
jenkins
community
and
in
gso
in
general.
A
It
will
definitely
be
helpful
going
forward
and
we
are
here
to
help
so
during
community
bonding
what
we
expect
teams
to
do
so
teams
consist
of
a
student
who
is
a
project
lead
basically
and
well.
That
is
implemented,
of
course,
and
also
several
mentors.
You
know
we
have
at
least
three
mentors
in
every
project.
At
the
moment
there
might
be
additional
contributors
joining
later
or
maybe
leaving
it
also
happens,
but
yeah.
The
key
objective
for
this
team
is
to
actually
get
ready
to
the
coding
phase.
A
A
So
git
results
is
something
I
would
recommend
for
a
child,
but
you
also
have
an
option
to
use
slug.
So
we
have
a
continuous
delivery
foundation
slot
and
is
here
so
if
you
want
to
join
so
there
was
a
question
of
whether
you
have
to
be
a
member
of
oxamax
to
join
no,
so
the
problem
with
that
is
that
the
governments
on
the
continuous
liberty
foundation
site
are
dated,
but
for
us
there
is
another
guide
here,
so
pretty
easily
foundation.
A
Yes,
okay,
so
so,
basically,
if
you
go
to
gsoc
the
most
of
project
ideas,
gist
of
2021
project
ideas,
if
you
go
there,
you
can
see
that.
Well,
basically,
let's
take
cloud
ones
so
for
cloud
events,
you
can
see
that
there
are
a
few
links
here
that
there
is
a
link
to
a
chat
in
twitter.
There
is
a
link
to
mailing
piece
and
there
is
a
list
linked
to
meetings,
because
this
project
participates
on
table
of
code
native,
which
is
unsurprising,
headless
taking
the
name
and
yeah
here.
A
So
you
have
a
chat.
We
have
mailing
list
and
we
have
regular
meetings
which
points
to
gsoc
apparently
but
yeah.
Actually,
the
team
has
meetings
every
friday.
So
it's
just
a
must
in
the
metadata
here,
because
yeah
we
got
it
fixed,
but
what
I
wanted
to
say
to
the
teams
that
that
means
you
have
in
project
ids,
where
the
links
for
initial
discussion
and
application
phase
going
forward.
The
teams
have
opportunity
to
decide
how
they
iterate.
A
So,
basically,
your
mentors
and
whatever
community
you
have
around
the
project
like
stakeholders
interested
people.
You
are
fully
free
to
choose
what
communication
channel
you
use,
whether
it's
literature
or
whether
it's
slack
or
you
may
just
decide
to
use
something
else.
It's
up
to
you,
so
our
expectation
that
projects
are
community
projects.
So
what
it
means
is
that,
well,
basically,
you
participate
as
a
part
of
wider
community,
not
just
as
a
small
team
and
if
you
get
want
to
get
full
experience
of
open
source.
A
This
is
how
you
should
participate,
so
not
just
working
in
a
small
team
but
actually
reaching
out
to
the
community
to
potential
users
getting
feedback,
collaborating
where
it's
possible,
because
yeah
your
main
goal
in
this
project
not
to
deliver
your
task.
Your
main
goal
is
to
actually
study
something
learn.
How
open
source
community
works,
improve
your
skills,
including
technical
skills,
soft
skills
and
to
have
some
experience,
and
it's
not
only
related
to
students
same
for
mentors
all
of
us
learn
together
when
working
on
gsoc.
A
I
learned
a
lot
when
mentoring
students
over
the
past
years
and
yeah.
Please
make
sure
to
make
it
your
priority
and,
of
course,
if
we
deliver
some
code,
it's
nice
and
yeah,
it's
probably
a
criteria
for
finding
no
competition,
the
project
and
for
successful
regulation.
But
it's
not
the
main
goal
for
you
as
a
participant.
The
main
goal
is
to
actually
study
and
yeah.
Please
focus
on
the
together
mentorship
teams.
A
It
okay,
so
again,
communication
channels,
so
chat,
we
discussed
mainly
increased,
is
optional
because
we
already
have
the
public
g
software
linked
list.
You
can
use
this
mailing
piece
for,
let's
say
top-level
conversations
for
internal
team
announcements
etc.
For
technical
conversations
we
have
other
mailing
ps.
A
So,
for
example,
if
you
want
to
ask
about
jenkins
development,
the
best
way
is
to
go
to
cider,
because
there
is
no
point
to
just
ask
your
team
in
the
million,
please
that
you
can
ask
why
the
junk
is
coming
in
and
you
can
see
that
there
is
a
lot
of
topics.
Actually,
our
developer
manifest
is
a
mix
of
open
governance
and
development.
A
It's
due
to
historical
reasons.
For
now
we
intend
to
keep
it
like
that.
But
if
you
have
any
question
about
development,
just
drop
it
into
the
mailing
list
and
we
can
discuss
same
for
example.
If
you
want
to
discuss
something
specific
to
seek
to
interact
viability,
you
can
go
to
cloud
native
sieve
and
ask
there
it's
a
mailing
list
or
the
resource
cdf
mailing
list
for
interoperability
between
projects.
So
you
can
use
these
channels.
So,
historically,
our
projects
don't
get
mailing
fees,
but
if
you
decide
to
do
so,
you
can
totally
do
that.
A
Another
communication
channel
we
asked
teams
to
establish
is
weekly
meetings,
so
we
asked
all
mentors
and
students
to
have
a
first
meeting
as
soon
as
possible
and
two.
The
main
objective
is
to
define
communication
channels.
So
during
coding
phase
we
recommend
having
two
meetings
per
week.
At
least
it
was
a
recommendation
for
full-time
json
when
students
were
working
40
hours
per
week
now
with
20
hours
yeah,
please
discuss
it
with
the
teams.
How
you
want
to
organize
and
yeah
how
you
will
organize
the
work
for
some
students.
A
I
may
want
to
work
just
full
time
for
one
phase.
Some
students
may
want
work
for
two
phases,
so
discuss
it
with
the
teams,
but
we
expect
at
least
weekly
meetings
between
team
members
because
they
have
been
proven
to
be
very
efficient
in
terms
of
communication
and
experience
sharing.
A
So
we
don't
use
these
meetings
for
status.
Updates
status
updates
can
be
done.
Asynchronously
in
the
chat
use
of
these
meetings
for
knowledge,
transfers,
discussions
again
studying
together,
discussing
things
discussing
obstacles
and
unbolting
each
other,
but
as
much
as
if
you
can
keep
a
communication
system.
So
that's
great,
but
having
this
meeting
is
still
nice,
even
if
it's
15
minutes
or
10
minutes.
If
everything
is
okay,
moving
on
so
yeah.
The
next
topic
we
expect
here
in
community
bonding
is
getting
introduced,
statistic
holders
and
contributors.
A
Again,
it's
not
just
about
your
team.
Many
other
projects
have
communities
already.
So,
for
example,
if
you
talk
about
just
a
second,
so
if
you
talk
about
cloud
events,
probably
this
example
too
often
but
yeah,
there
is
cloud
native
speak
with
many
people
participating
in
there
with
active
charts.
If
you
talk
about
zinc,
supernatural
separated,
then
there
is
even
a
separate,
select
workspace
owned
by
victor
schwab,
where
there
are
ongoing
discussions,
I'm
not
sure
whether
the
team
will
decide
to
use
this
workspace
or
maybe
not.
A
Actually,
when
I
was
thinking
about
that,
I
was
rather
wondering
whether
this
workspace,
whether
this
channel,
should
be
moved
elsewhere,
but
yeah.
It's
totally
up
to
the
team,
so
same,
for
example
for
semantic
version.
It's
like
the
jenkins
infrastructure
sub
project,
because
again
there
is
an
active
community
and
we
are
interested
to
have
it
done
for
remoting.
We
have
promoting
sub
project.
We
have
jenkins
core,
we
have
again
cognitive
c
for
git
credentials.
A
I
believe
that
mark
will
use
the
platform
seek
as
a
base
for
this
project
and
for
what
was
left
well
yeah.
We
discussed
everything
so
but
again,
I
do
define
the
channels
and
I
highly
recommend
to
start
reaching
out
to
the
wider
community
again,
because
all
these
projects
have
significant
community
value.
There
are
many
potential
users
and
agencies
coming
in
and
there
are
many
ways
to
how
you
can
reach
out.
Firstly,
join
the
receive
meetings,
join
project
meetings
or
you
can
just
send
an
email.
A
The
developer
managers,
for
example,
you
see,
for
example,
just
do
quick,
self-introduction
project
introduction.
Another
way
to
communicate
is
actually
writing
financial
blog
post.
If
you
already
have
a
good
proposal
with
a
lot
of
details
and
all
of
you
have
such
kind
of
proposal,
so
you
can
already
use
community
bonding
time
to
write
a
small
block
and
to
speak
about
your
experience
about
your
plans,
which
is
our
main
focus
not
to
build
community
around
the
project
because
most
stakeholders,
you
have
more
feedback,
you
get
and
more
opportunities
for
learning.
A
You
have
the
communication,
so
my
recommendation
during
community
bonding
is
really
go
outside
your
team
and
have
communications
with
more
people.
A
B
C
Yeah
but
jeff
it'll
be
better.
If
you
start
on
this
one.
A
B
So
I
think
that
the
the
important
thing
is
to
just
kind
of
get
to
know
the
the
mentors
a
little
bit
get
get
some
code
out
there,
maybe
get
some
stuff
reviewed
and
kind
of
just
sort
of
get
get
the
conversation
going.
B
Make
sure
that
you're
comfortable
with
with
the
repo
and
and
submitting
pull,
requests
and
kind
of
kind
of
get
get
the
whole
process
going.
Then,
when
we're
ready
to
start
coding
we're
you
know,
everything's
ready
to
go,
we
everybody
knows
what
to
do,
how
to
make
sure
that
the
code
gets
reviewed,
just
kind
of
how
the
whole
process
works.
B
Figure
out
which
which
modes
of
communication
work
work
best.
As
oleg
said
earlier,
the
mentors
have
have
full-time
jobs.
You
know
we're
all
in
different
time
zones,
and
so
I
know
I
I
haven't
in
the
past,
been
really
great
about
keeping
up
on
on
gitter.
If,
if
we
choose
to
use
getter
for
our
project
I'll,
try
that
I
think
during
during
the
process
of
just
trying
to
get
some
some
code
going,
we
might
find
out
which,
which
things
work
best
for
our
particular
project.
A
So
yeah
it's
actually
a
program
for
wider
communities,
so
there
are
commonly
two
types
of
communication:
synchronous,
communications
like
mailing
keys
and
real-time
live
communications
like
charts,
etc.
A
And,
although,
in
the
jenkins
community
like
in
many
other
communities,
we
recommend
to
use
asynchronous
communications
as
much
as
possible,
because
everyone
has
a
different
time
zones,
it's
normal
to
have
something
like
24
hours,
response
delay,
or
so
the
fact
that
most
of
the
teams
use
real-time
communications
like
chat,
it
kind
of
proved
these
tools,
like
slack
where
you
can
have
threads,
where
you
can
actually
recover
these
threads
and
synchronously.
A
But
you
mean
think
about
it
carefully
and
if
there
is
an
opportunity
to
move
communications
to
us
in
front
of
us,
it
might
be
better
for
everyone,
because
yeah,
even
students,
yeah.
This
is
one
of
the
reasons
why
gsoc
is
more
flexible
this
year,
with
20
hours
per
week,
expectation
that
everyone
can
be
more
flexible
with
the
current
the
crazy
times.
I
think
it's
important.
C
Yeah,
so
considering
this
project
is
also
about
cloud
events,
so
hence
we
were
thinking.
Maybe
cdf
slack
would
be
a
better
better
place,
because
a
lot
of
the
stuff
that
is
going
on
in
the
event
sake
in
cds
will
slowly
start
catching
up
with
the
cloud
events
plugin,
so
based
so
based
on
all
these
factors.
It's
it's
important
to
understand
like
who.
What
kind
of
projects
would
also
be
stakeholders
in
in
the
long
run?
So
in
terms
of
cloud
events
plug-in,
it
would
be
cloud
events
and
eventing.
A
Yeah
for
cloud
events,
actually,
the
situation
is
even
more
interesting
because
cloud
events
is
a
clear
interoperability
project
because
it's
not
like
you
work
just
inside
jenkins
in
the
with
the
jinx
community,
but
cloud
events
is
also
open.
Source
project
cloud
advance
is
actually
quite
active,
open
source
project
and
it
has
its
own
community,
for
example,.
A
A
I
think
whether
somebody
would
be
interested
in
participating
and
they
also
use
jenkins
a
lot
multiple
community
members,
so
it
might
be
a
good
opportunity
for
you
to
reach
out
and
to
think
whether
there
could
be
some
collaboration
where
you
could
have
mentors
from
this
community.
Maybe
you
can
even
decide
that
okay,
we
go
and
we
create
our
channel
within
the
cloud
events
community,
because
it's
better
for
collaboration.
A
It's
up
to
you
and
to
the
team
and
yeah.
I
know
that
for
students
it
might
be
quite
difficult
to
operate
on
these
levels
because
yeah
it
requires
significant
open
source
expertise,
but
the
top
three
mentors
might
almost
all
mentors
have
a
lot
of
expertise
in
the
open
source
communities,
not
only
jason
jenkins
and
yeah.
Please
use
this
expertise
so
that
mentors
can
help
you
how
organize
and
help
guiding
you
and
all
mentors
have
a
lot
of
contacts
here
and
there,
so
they
might
be
able
to
assist
when
needed.
C
So
mauricio,
who
is
another
mentor
on
this
plugin,
is
not
present
today,
but
he
is
he's
one
of
the
experts
on
cloud
events
so
through
through
him
we'll
be
getting
a
lot
of
knowledge
on
a
lot
of
other
stuff
that
we
can
do
once
we
reach
like
a
level
where
the
plug-in
can
be
can
like.
We
can
start
using
the
plug-in.
A
A
Well,
I
and
I'm
at
a
few
mentors
I
can
help
forgink
is
removing
its
primitives
community,
for
example,
they
might
be
interested
or
there
is
open,
telemetry
activity,
open,
telemetry
community,
actively
growing,
and
there
was
a
open,
telemetry
plug-in
created
by
elastic
recently
for
jenkins
and
again
it's
a
window
of
opportunity,
because
we
can
use
one
of
these
contacts.
I'm
going
to
go
out.
You
should
get
more
feedback
and
see
how
it
works,
maybe
not
even
during
the
first
coding
phase
but
yeah
again.
A
A
So
why
not-
and
this
is
also
a
topic
where
you
can
talk,
for
example,
with
jenkins
x
community,
because
jinx
x
communication
separates
in
the
cloud
native
domain
domain.
They
also
use
operators
a
lot
and
there
might
be
a
lot
of
opportunities
for
expert
and
sharing
semantic
version.
Yes,
it's
also
jenkins
community.
A
A
Okay,
so
yeah
what
else
so
continue
to
discuss
and
fund
the
project?
So
this
is
an
important
point,
because
what
you
made
during
the
application
is
a
project
proposal
and
we
reviewed
this
proposal.
We
made
a
decision,
but
not
all
proposals
actually
can
happen,
as
is,
for
example,
they
might
be
too
ambitious
in
terms
of
timing.
There
might
be
two
ambitious
in
terms
of
deliverables
or
after
the
discussion
with
mentors.
A
You
may
choose
different
architecture,
different
approach,
it's
totally
possible-
and
we
had
cases
like
that
before,
but
you
as
the
team
you're
fully
free
to
decide
what
you're,
how
you
appreciate
so
the
deliverable
deliverables
you
defined
in
your
original
proposal,
they're,
not
slated
in
the
stone
and
as
a
team,
you
can
discuss
what
you
do,
how
you
adjust
based
on
how
the
project
progresses,
etc,
and
our
main
criteria
for
evaluating
students
is
actually
how
they
progress.
Whether.
A
The
experience
of
mentors
is
great
and
as
long
as
experience
of
mentors
is
great,
we
do
not
really
care
about
what
was
delivered
or
not.
It
might
be,
of
course,
a
different
situation
if,
for
example,
due
to
whatever
unfortunate
reasons,
we
have
escalated
toward
means,
or
maybe
even
to
the
google
in
the
case
of
negative
evaluation,
for
example,
things
like
that
happens,
we
can
discuss
it
later
because
it
hasn't
happened
in
the
jinx
community
yet,
but
I
was
involved
in
other
communities
where
we
had
this
escalations
and
discussions,
but
yeah.
A
A
For
example,
there
was
a
project
where
mentors
and
students
did
prototyping
during
the
first
phase
and
they
realized
that
the
project
is
just
unfeasible,
not
implementable,
due
to
things
unrelated
to
the
student,
and
they
basically
chose
another
direction.
It
wasn't
in
the
engines,
but
the
engineers
will
adjust
projects
a
lot,
so
don't
hesitate
to
do
that
and
again
students,
as
leaders
they're,
basically
eligible
to
make
the
final
call
so
mentors
provide
advice,
provides
inputs,
but
it's
up
to
the
students
to
make
the
final
call.
If
there
is
a
disagreement
etc.
A
So
yeah
there
is
a
lot
of
text
there,
but
yeah
again
take
a
look
at
this
page
later.
So
then
important
topic
set
up
your
development,
environment,
computers,
etc,
and
for
for
projects
which
require
cloud
access,
also
think
about
your
environment.
What
it
means
that,
if
you
need
something
specific,
for
example,
with
kubernetes
cluster
for
cloud
events
for
jnt
separator
or
if
you
need
other
environment
talk
about
it
with
mentors
earlier,
because
we
as
a
project
do
not
expect
you
to
pay
for
this
environment
on
your
own.
A
A
No
questions,
so
we
are
going
to
discuss
the
process
with
mentors.
We
discussed
it's
basically
results
of
engagement.
We
have
mentioned.
We
use
jira
to
track
g
sub
tasks,
so
this
part
is
dated
as
well.
I
will
remove
or
replace
that
over
the
previous
year
we
adopted
github
issues
in
many
projects
we
officially
opened
the
cloud
gates.
So,
for
example,
if
you
go
to
janks
kubernetes
security,
if
you
go
to
many
other
plugins
like
configuration,
is
called,
they
use
github
issues,
and
at
this
point
there
is
no
sense
to
enforce
any
particular
task.
Striker.
A
What
we
ask
for
is
a
jinx
community
that,
for
your
own
benefits
these
creative
tasks,
please
track
them
because
you
it
helps
you
to
stay
on
track
and
well
many
teams.
Do
it
in
production.
Many
teams
do
it
together.
It's
up
to
you.
You
can
decide
that
you
follow
scrum,
you
can
follow
kanban,
you
can
just
do
whatever
works
for
you
as
a
team,
but
yeah.
My
recommendation
is
still
keep
track
of
the
tasks,
because
it's
helpful
for
you,
because
you
can
agree
you
using
tasks.
A
A
So,
for
example,
you
have
a
feature
thread
if
it
fits
interesting,
notepad
request,
even
if
it's
one
line
documentation
fix
or
if
it's
something
like
100
clients
etc.
It's
fine
please
try
to
avoid
big
pull
requests
because
they
have
to
review
they're
hard
to
deliver
and
they're
also
hard
to
integrate.
A
We
want
you
to
integrate,
often
and
again
talk
to
your
mentors
about
how
to
establish
this
process
and,
for
example,
in
my
case
yeah.
I
also
have
a
dashboard
for
junkies
community.
For
example,
physical
one,
as
you
can
see,
my
memory
is
quite
bad
at
the
moment,
but
yeah
just
why
not
yes,
so
I
see
that
kudos
separator
has
a
project
there
so
yeah,
maybe
it's
not
the
best
example
but
yeah.
If
you
want
you
can
create
both
like
that
within
github
issues.
A
All
these
are
within
jenkins
jira
and
as
a
team,
you
just
decide
what
approach
you
want.
So
you
have
freedom
of
how
we
define
that,
and
our
main
ask
is
that
it's
public
so
that
you
can
run
both
contributors
and
orthodontists
have
access
to
that
if
something
is
needed
from
us,
but
how
you
implement
that?
How
you
proceed
is
totally
up
to
you,
then
just
try
some
more
industry
practices,
because
again
you
study
here.
So
if
you
want
to
try
agile
development,
etcetera
and
prevent
yourself
from
that,
why
not.
A
So
if
there
are
specific
domains,
you
want
to
discuss
with
the
team
so,
for
example,
for
cloud
events
plugins,
it
would
be
really
reasonable
if
mauricio
does
inter
introduction
to
cloud
events,
and
we
can
also
do
it
for
the
entire
junkies
community,
because
why
not
again,
if
you
can
go
to
why
the
community
do
it
if
it
doesn't
slow
you
down
and
yeah
for
other
projects,
if
you
need
specific
knowledge,
transfers
talk
to
your
mentors
as
often
as
happy
to
organize
sessions
on
the
month.
A
A
A
A
So
if
you
have
any
questions
fees
free
to
join,
I
would
like
to
start
a
doodle
poll
so
that
we
can
choose
new
time
for
meetings
if
this
time
is
not
comfortable
for
students
for
mentors
or
we
can
have
sessions
in
different
time
zones
depending
on
the
interest
but
yeah.
This
meeting
is
optional
and
do
not
use
this
meeting
for
asking
questions.
Do
not
wait
for
this
meeting
because,
for
example,
you
can
ask
your
team
or
you
can
ask
again
the
github
channel
for
gstock,
so
no
need
to
wait
for
this
meeting.
A
If
you
have
a
quick
question,
just
ask
right
away
our
main
objective
as
mentors
or
as
often
means
is
to
ensure
that
you
don't
have
blockers
and
you
don't
have
anything
delaying
you,
so
we
will
try
to
how
we
can
so
we
can
use
these
meetings
for
anything
so
but
whole
discussions
themselves.
If
you
want
to
show
something
or
share
your
experiences,
you're
welcome
to
do
that.
A
A
They
will
be
the
same
list
for
2021
soon,
and
here
you
can
see
that
there
are
links
to
students,
so
why
it's
helpful
because
it
helps
to
quickly
navigate
through
content
through
history,
etc.
There
are
also
profile
pages
and
we
ask
all
students
and
eventually
all
mentors
to
fill
in
these
profile
pages
so
that
we
can
easily
ask
add
you
to
the
list.
A
So
here
you
can
see
three
roles:
students,
members,
advisors,
so
advisors
is
basically
non-mentors,
but
the
people
who
contribute
to
the
projects
as
stakeholders
sometimes
help
and
well.
If
you
want
to
introduce
morals
in
your
projects,
please
do
so
but
yeah.
This
is
how
we
organized
the
projects
before
and
yeah
a
student.
Please
create
a
profile,
so
some
of
you
have
already
submitted
requests
and
thanks
a
lot
for
that
and
yeah.
A
If
you
haven't
done
it
yet,
please
another
thing
which
I
would
recommend
for
community
bonding
is
to
actually
submit
your
first
book
request.
If
you
haven't
done
it
yet
it
might
sound
a
bit
odd,
because
coding
starts
only
on
june
7th,
but
actually,
by
submitting
your
first
first
full
request,
you
can
evaluate
the
process.
You
can
check
that
your
environment
is
okay,
you
can
also
start
just
ramping
up
in
the
project
and
it
doesn't
have
to
be
bigfoot
requests
just
whatever
and
they
believe
that
many
projects
have
newcomer
friendly
issues
published.
A
A
Does
it
work
for
everyone?
I
basically
summarized
all
I
wanted
to
tell
yeah
sorry.
It
was
a
long
discussion.
We
don't
have
forever
if
any
rejected
students
on
the
call
so
for
rejected
students.
I
will
be
following
up
in
the
million
list
to
save
everyone's
time
and
so
question
for
anyone.
Would
you
like
to
discuss
something?
Would
you
like
to
provide
any
feedback,
or
do
you
need
any
additional
information
to
proceed.
D
I
just
wanted
to
say
thank
you
oleg
for
giving
us
an
overview
what
next.
So
from
my
end,
for
those
of
you
who
don't
know
me,
I
will
be
mentoring
together
with
jakub
and
silvia
kubernetes
jenkins
operator
project,
so
we'll
make
sure
everything
is
aligned
with
the
with
the
overall
schedule.
I
will
make
everything
transparent
as
much
as
possible
and
in
case
of
any
questions
we'll
reach
out
to
you
guys
so
yeah.
Thank
you.
A
Okay,
any
other
comments,
questions,
so
students
have
been
super
silent
during
this
presentation.
Yeah
again
we
can
see
the
use
for
community
members
so
as
mentors
etc.
Just
feel
free
to
interrupt
ask
any
questions
in
any
time.
So
there
is
no
formalities.
We
need
to
follow
and
if
you
have
any
questions,
if
you
need
any
qualification,
then
please
do
so.
E
Continue
hi,
like
I
have
a
question
yeah
sure.
Firstly,
thank
you
so
much
for
the
presentation
and
my
question
was
actually,
if
you
remember
one
month
back,
we
discussed
about
changing
the
name
of
the
project
from
semantic
versioning
to
conventional
comments.
Plugin.
I
wanted
to
ask
about
that.
So
I
think
we
have
time
till
25th
of
may
to
update
it
on
the
g
stock
website.
I
got
a
email,
an
email
regarding
that.
E
So
what
would
be
a
good
way
to
discuss
this
with
the
community
and
go
ahead
and
make.
A
The
changes,
if
renaming,
etc,
it's
rather
meta
for
the
mentoring
team.
So
again
yeah
you
do
planning
you
do
adjustments,
based
on
whatever
discussions
you
had
based
on
whatever
discoveries
you
have
so
just
discuss
it
with
your
mentors
and
it's
enough.
If
it
requires
a
wider
discussion,
then
feel
free
to
reach
out
to
the
link
is
community,
etc.
A
So
yeah,
if
you
have
any
questions
again,
ask
him
jason
computer.
Ask
your
mailing:
please
ask
your
team
members
and
yeah:
all
of
these
approaches
will
be
working.
Fine
next
meeting
will
be
next
week,
but
no
need
to
wait
until
that
and
yep
again,
thanks
to
everyone
for
joining
me,
jsoc
thanks
for
joining
this
meeting.
I
hope
it
will
be
a
great
experience
for
you
and
yep.
Let's
make
sure
that
also
have
fun
and
study
something.
So
thanks
all
and
looking
forward
to
working
with
you
this
year.