►
From YouTube: Keptn Community Meeting - May 25, 2022
Description
Discussion about community bonding phase during GSoC. Meeting notes: https://docs.google.com/document/d/1y7a6uaN8fwFJ7IRnvtxSfgz-OGFq6u7bKN6F7NDxKPg/edit
Learn more: https://keptn.sh
Get started with tutorials: https://tutorials.keptn.sh
Join us in Slack: https://slack.keptn.sh
Star us on Github: https://github.com/keptn/keptn
Follow us on Twitter: https://twitter.com/keptnProject
Sign up to our newsletter: https://bit.ly/KeptnNews
A
A
So
basically
a
legend
is
also
pretty
short.
I
want
to
spend
most
of
the
time
on
jisokuni
yeah,
so
thanks
and
eric
for
joining
and
yeah
before
that.
So
first
of
all,
we
have
announced
g-shock
projects,
so
we
have
four
g-shock
projects
this
year
and
yeah.
Congratulations
to
everyone
who
was
accepted
so
arranging
rajiv.
A
A
What
is
important
that
we
were
unable
to
accept
a
number
of
other
projects
because
of
the
limitations,
the
size
of
the
mentorship
teams.
So
right
now
we
are
looking
into
opportunities
to
host
lfx
mentorship,
most
probably
this
autumn-
maybe
one
summer
project,
but
I'm
not
100
sure
about
that.
So,
if
you're
interested
to
participate,
if
you
participated
in
gsoc,
if
you
didn't,
then
we
will
be
working
on
additional
opportunities
so
and
again,
congrats
to
everyone
who
is
accepted.
So
just
a
quick
heads
up
what
happens
next,
there's
community
bonding.
A
We
send
the
expectations
to
mentors
about
the
community
bonding.
I
can
duplicate
some
of
them
to
the
students
if
you're
interested,
but
basically
the
whole
point
of
this
phrase
is
to
make
sure
that
by
the
time
the
calling
phase
begins,
you
can
actually
start
coding
what
it
means
that,
firstly,
you
need
to
under
get
all
the
required
permissions
and
get
all
the
repositories
so
you're
not
blocked
by
that
also
the
required
knowledge
transfers,
etc.
A
A
One
item
which
commonly
gets
discussed
at
this
phase
is
what
is
actual
scope
of
your
work
because
yeah
they
were
project
applications.
This
project
applications
they're
quite
realistic
in
terms
of
what
needs
to
be
delivered,
but
some
morality,
mapping
still
might
need
to
be
done
so,
for
example,
timing,
scope,
etc.
A
So
again,
a
community
bonding
is
a
great
opportunity
for
teams
to
discuss
what
they
actually
plan
to
deliver,
because
your
project
is
insulated
and
stone.
You
can
adjust
as
needed
together
these
mentors
and
you
can
basically
drive
this
discussion
or
mentor
well
in
most
of
the
projects.
We
assume
that
students
contributors
the
project
leads
so
mentors
just
provide
advice,
etc
and
provide
guidance
when
needed.
But
you
can
take
initiatives
almost
everywhere
and
yeah.
It's
a
good
time
to
have
conversation
with
your
mentors
about
what
would
be
the
scope
for
that.
A
So,
if
you
need
any
additional
things,
for
example,
if
you
need
repositories,
if
you
need
github
projects
for
dashboards,
I'm
not
sure
whether
you
plan
to
use
kanban
style
or
agile
style.
So
it's
all
of
that
can
be
discussed
again
with
your
team.
A
But
if
you
need
all
this
in
project
infrastructure,
I'm
available
and
other
maintenance
also
able
to
set
it
up
for
you,
but
you
need
to
request
it.
So,
just
in
the
chat
is
okay,
but
don't
expect
many
things
to
be
set
up
for
you
unless
you
ask
for
that,
because
there
is
community
process
so,
for
example,
for
hosting
here
repositories
there
is
a
process
for
sandbox
etc,
and
we
generally
recommend
following
this
process,
but
at
the
same
time
for
gsoc.
A
Of
course,
we
try
to
speed
it
up
as
much
as
possible
so
that
you
don't
get
blocked.
Still.
These
three
weeks
is
something
you
can
use
for
that,
and
maybe
another
important
topic
is
infrastructure,
slash
budgets.
So,
for
example,
if
you
need
a
cluster
or
let's
say
gcp
or
whatever
again
it's
something
that
it
will
be
better
to
discuss
now,
so
that
we
can
prepare
before
the
coding
begins.
A
A
A
A
A
Okay,
so
I
do
have
a
few
other
topics
on
agenda.
But
yes,
since
we
don't
have
many
contributors,
maybe
I
will
skip
them
until
tomorrow,
so
just
quick
summary
for
incubation,
etc.
It
will
require
some
of
my
time
in
the
coming
weeks
too,
because
captain
incubation
was
delayed
because
of
toc
review
process,
and
so
the
really
realistic
estimation
for
that
is
beginning
of
june.
So
there
will
be
a
lot
of
buzz
and
I
will
probably
have
to
disappear
for
a
week
or
so
from
the
coming
india.
A
So
yeah
again,
I'm
happy
to
join
the
projects
if
needed,
I'm
enjoying
meetings
etc
to
help
with
some
guidance,
because
I've
used
gsoc
since
2016.,
but
if
needed
again,
please
let
me
know
so
that
I
can
plan
my
schedule
accordingly.
A
Most
probably,
I
won't
be
mentoring
any
project
on
my
own
this
year,
but
yeah
I
will
be
providing
kind
of
advisory
for
all
projects
in
terms
of
processes
in
terms
of
how
to
do
things
better
et
cetera,
et
cetera,
okay
and
keep
considering
conferences
happened,
and
we
had
something
like
10
ish
contributors
at
kipcon.
It
was
nice
time.
A
Well,
I
missed
most
of
that
because
I
had
to
depart
on
tuesday,
so
I
haven't
really
visited
cubecon
itself,
which
is
unfortunate
but
well
that's
it,
but
yeah
thanks
a
lot
to
everyone
who
helped
to
stop
the
booze
to
do
the
presentations
around
project
office
hours
and
do
all
other
activities
around
coupon
because
yeah
there
were
a
lot
of
them.
So
in
total
we
had
five
or
six
presentations,
including
mentioning
captain
and
yeah.
A
A
So
again
the
timeline
potentially
allows
to
invite
successful
contributors
etc
to
the
united
states,
let's
see
whether
we
can
fund
it
by
budgets,
etc.
But,
in
theory,
if
everything
goes
right,
I
think
that
it
would
be
one
of
the
options
to
keep
in
mind.
A
A
Then
thank
you
and
yeah.
If
no
other
topics
we
can
just
keep
the
meeting
short,
I
will
still
publish
the
video.
Mostly
we
suggest
gsoc
talk,
because
everything
is
about
g-shock
and
just
have
a
great
summer
and
if
anything
is
needed
for
your
projects,
please
let
me
know.