►
Description
We talk about AsyncAPI participating in GSoC and other initiatives.
Slides: https://docs.google.com/presentation/d/1tJUDE7lo00LrB97IF7_oYNgKG0RDg3kt-d1MzwkzTdw/edit#slide=id.p
A
A
It's
we're
doing
a
small
experiment
here
today,
so
usually,
when
I
was
doing
the
live
stream,
it
was
live
streamed
from
zoom
from
red
stream
to
all
our
social
media,
but
there
are
so
limits
some
limits
with
restream.
So
now
we
are
using
zoom
where
we
meet
and
can
talk
to
people
and
thanks
to
it
we
have
also
live
transcripts.
As
you
can
see,.
A
A
A
So
it's
a
time
where
we
can
chat
a
bit,
have
a
small
talk
and
let
people
like
latecomers
join
later
so
definitely
first
welcome
folks
on
youtube
chat,
which
I'm
watching
now
at
the
moment.
So
definitely
folks,
let
us
know,
what's
your
opinion
on
the
live
transcript,
especially
with
my
polish
accent
and
and
yeah
folks,
on
the
call
like
before
we
jump
into
the
presentation
and
discussion
about
about
g-shock.
B
B
A
A
And
yes,
I'm
happy
you're,
happy
alejandra,
please
let
us
know
like
please
like
look
on
those
live
streams
and
share
your
opinion.
If
that's,
if
that's
enough,
because
so
far,
when
I'm
looking
at
the
live
transcripts,
it's
it
looks
pretty
decent,
but
if
that
has
to
be
improved,
then
we
can
zoom
enables
us
to
integrate
with
some
third-party
tools.
So
if,
if
there
is
some
improvement
needed,
we
can
definitely
explore
further
but
yeah.
That's
the
advantage
of
not
using
restream
directly
but
zoom,
because
zoom
by
default
enables
that.
A
Okay,
so
yeah
we
have
six
minutes
passed.
I
think
we
can
start
so
I
will
start
this
live
stream
unusual
because
I
usually
just
I
don't-
have
any
presentation-
it's
always
unorganized
discussion
or
like
we're
not
preparing
beforehand,
but
this
time
I
wanted
to
prepare
myself
better,
because
there
are
many
different
aspects
that
need
to
be
mentioned
and
and
cleared
out,
and
I
just
don't
want
to
forget
about
anything.
A
So
first,
let
me
know
what
you
think
if
you
prefer
differently,
but
I
just
have
few
slides
with
some
bullet
points
like
the
most
important
things
that
people
need
to
know
about
google
summer
of
code
and
other
initiatives,
and
then
we
can
have
a
discussion
after,
but
also
I'm
I'll.
I
actually
like
when
people
interrupt
by
saying
like
to
like
ask
questions
during
the
presentation.
A
A
And
I
will
also
send
you
a
link
to
the
slides,
because
in
the
slides
you
will
find
a
lot
of
useful
links
so
yeah
I
just
send
a
a
link
to
youtube
youtube,
live
chat,
link
to
the
slides
and
and
yeah.
So,
as
you
can
see,
it's
not
really
professional
presentation.
It's
just
for
me
to
remember
about
every
item
that
I
want
to
want
to
cover.
A
So,
first
of
all,
this
call
is
mainly
designed
for
for
people
that
will
join
as
mentees
want
to
participate
actively
as
coders
and
and
sometimes
make
a
first
step
in
open
source
or
just
make
first
step
at
async
api
and
we'll
cover
also
some
some
topics
for
mentors.
So
we've
got
a
lot
of
maintainers
here
at
asking
api,
and
I
know
already
like
seven
or
eight
folks
that
want
to
actively
help
out
folks
to
be
mentors.
A
But
I'm
gonna
make
sure
that
you
notice,
which
topic
I'm
covering
at
at
given
moment
and
now
the
most
difficult
slide,
because
the
the
events
calendar
that
I
created,
I
created
it
in
the
in
google
sheet
and
it's.
I
bet
it's
way
too
small
for
folks
watching
three,
the
live
stream.
Let
me
let
me
first
try
to
make
it
bigger
or
just
open
it
separately.
A
So
something
that
I
already
covered
during
our
community
meeting
yesterday
but
yeah
the
most
important
is
that
we
want
assassin
api
to
participate
in
different,
even
different
events,
not
only
google's
summer
of
code,
because,
like
we
like
every
year,
we
we
do
something
different
at
using
epa.
So
first
year
we
just
did
oktoberfest,
then
we
noticed
we
were
able
to
do
something
more
sophisticated.
A
So
last
year
we
participated
in
google
summer
of
code,
and
this
year
we
basically
want
to
participate
wherever
possible,
because
yeah
a
lot
of
people
that
join
us
as
mentees
bring
a
lot
of
fresh
view
and
and
energy
into
the
project.
I
guess
that's
one
of
the
motivations
behind
us,
so
you
can
see
in
this
timeline
and
most
important
to
remember
from
this
live
stream.
It's
just
a
proposal
of
the
timeline.
A
So,
if
you
later
on
would
like
to
prepare,
not
preparable
actually
propose
something
different
then
definitely
please
do
so.
Yeah
first
is
oktoberfest,
then
open
force,
outreachy,
google
season
of
docs
and
google
summer
of
code.
I'm
not
gonna
go
much
into
details
now
about
these,
because
that's
on
next
slides,
so
yeah.
A
A
A
No
so
so
appear
asked
a
question
in
zoom.
Like
sorry,
I
just
joined
a
bit
confused.
Is
it
for
only
g-shock
applicants,
and
now
we,
I
will
cover
every
event
from
the
list
separately
today.
So
it's
and
it's
not
only
for
mentees,
but
it's
also.
There
will
be
some
information
for
mentors,
because
I
also
want
to
use
this
live
stream
and
recording
essay
material
for
for
our
maintainers.
A
So
they
can
learn
what
actually
we're
asking
them
for
if
we
would
like
them
to
participate
as
mentors
and
anyway,
we
have
some
mentors
on
the
call
action,
not
in
the
on
the
call
but
yeah
watching
this
stream
on
youtube.
So
they
will
definitely
also
have
some
questions.
I
guess
I
hope
appear
that
answers
your
question.
A
Okay,
awesome
thanks
for
asking.
It
was
good
question,
so
yeah
the
first
one,
the
simplest
one,
I'm
actually
I'm
wondering
if
it's
still
something
that
has
to
be
explained
to
people,
the
oktoberfest
it's
pretty
known
and
because
it's
pretty
known
it
also
has
a
lot
of
haters
but
yeah.
We
want
to
participate
as
every
year.
It's
good
for
easy
tasks,
easy
issues,
but
it's
in
october.
So
not
much
to
talk
about
now,
really
about
the
event.
A
What's
important
and
I'd
like
to
highlight
just
you
can
join
this
issue
where
cuda
one
of
our
technical
stream
committee
members
works
on
a
dashboard
for
for
our
website,
where
you
can
see
all
the
good
good
first
issues
like
easy
issues
to
start
with
the
with
coding
and
and
other
aspects
of
open
source
at
asking
api,
and
we
will
use
this
dashboard
for
hacktoberfest
so
yeah.
That's!
That's
it
about
octoberfest,
now
open
force,
that's
something
I
didn't
know
before.
A
A
So
it's
for
this
open
force
initiative
is
just
one
taking
one
month.
So
it's
for
issues
that
are
let's
say
moderate
that
it's
just
a
few
days
of
implementation
included.
So
we
definitely
and
it's
a
message
to
mentors
and
and
like
maintainers.
That
would
like
to
provide
some
issues
for
this
event.
So
we
need
a
a
kind
of
like
moderate,
moderate
issues,
which
means
like,
and
I
have
an
example
so.
A
So
it's
about
adding
a
new
command
in
the
cli
and
and
yeah
integrate
an
existing
library
in
the
cli.
So
it's
just
a
few
days
of
work.
If
you
want,
if
you're,
if
you
need
two
two
weeks,
that's
also
fine,
but
it's
it's
not
super
complicated
issue.
It's
well
defined!
So
you
you,
basically
just
focus
on
coding,
so
you
don't
really
have
time
to
learn
all
the
aspects
of
working
in
open
source,
important
names
to
remember.
A
A
So
I
will
make
this
official
application
from
massing
api
site
to
to
open
a
force,
and
I
will
write
a
blog
post
where
we
will
list
all
the
issues
that
we
want
to
provide
for
the
event.
So
we
need
to
write
this
blog
post.
Obviously,
before
before
march,
then
yeah
we
offer
swags
for
folks
that
completed
issues
from
open
force
and
yeah.
There's
a
link
to
the
website
and
there's
already
a
question
I
see
in
the
comment:
do
we
need
to
participate
open
first
to
work
on
the
mentioned
issues
so
yeah?
A
The
question
is:
do
you
have
to
participate
in
open
source
to
actually
complete
these
issues
from
open
source
yeah?
So
I
know
that
we
have
a
lot
at
least
I'm
I
and
I
bet,
I'm
not
the
only
one
that
noticed.
We've
got
a
lot
of
super
cool
contributors
that
are
looking
for
google
summer
of
code
you're
like,
for
example,
yo
ritki,
like
you
contribute
a
lot,
but
my
request
would
be
like.
A
But
if
there
are
some
issues
that
will
not
be
completed
in
march,
then
definitely
you
can
pick
them
up
or
you
can
just
join
for
open
for.
So
I'm
not
I'm
not
sure.
If
hargon
is
watching
the
the
live
stream
who
can
apply,
I
I
was
not
really
checking
on
on
the
process
of
how
people
should
apply
as
mentees
to
open
force,
but
yeah,
maybe
just
joined
through
through
open
force,
but
but
also
yeah.
I
mean
it's
it's
hard
to
answer
to
this
question,
but
yeah.
A
Okay,
so
that's
it
if
it
comes
to
open
for
us,
so
it's
short
one
month,
just
like
oktoberfest,
but
it's
good
to
it's
still
good,
even
at
least
I
think
so.
We
participate
in
it
for
the
first
time,
but
I
think
it's
a
good
event
to
to
work
with
people
from
outside
asking
api
on
some
on
some
issues
that
we
also
don't
have
time
to
to
work
on.
A
Okay,
so
next
on
the
list,
google
season
of
dogs-
so
that's
something
that
we
did
not
participate
in
last
year,
mainly
because
there
was
no
technical
writer
working
full
time
in
the
project.
Now
we
have
alejandra.
So
it's
a
it's.
I
think
the
best
moment
to
also
make
a
stand
in
events
different
than
just
coding,
because
yeah
open
source-
I
hope
you
all
folks
know
about
it.
Already.
It's
not
only
about
coding.
A
A
Where
is
the
wait?
Wait?
Okay.
Anyway,
sorry,
I
was
I'm
just
confused
because
I'm
pretty
sure
I
provided
some
examples.
No
okay!
It's
here!
Okay!
So
again,
like
let's
focus
on
this
bullet
point,
don't
read
further
for
mentors
it's
important
to
provide
tasks
that
are
non-trivial
but
also
non-trivial
that
it's
like
don't
focus
only
on
coding
on
docs
aspects.
Sorry
in
case
of
google
season
of
docs,
like
google
season
of
docs
and
google
summer
of
code,
they're
they're
both
meant
for
people
and
especially
you
can
see
it.
A
If
it
comes
to
the
timeline,
how
much
people
have
time
to
work
on
these
issues?
It's
it's
for
people
to
learn
about
something
more
than
just
code
and
docs.
It's
about
really
learning
how
the
work
looks
like
in
in
open
source,
and
so
they
can
also
learn
as
many
aspects
of
a
given
profession
as
possible.
A
So
if
it
comes
to
documentation
related
issues
and
one
of
examples
that
I
would
like
to
submit
as
a
as
a
proposal
that
I
could
mentor
because
I
have
some
background
in
technical
writing,
so
it's
a
generator,
docs,
rework
and
it's
it
sounds
like
it's.
Okay,
we
have
existing
documentation,
it's
just
like
restructuring
and
should
be
trivial,
but
it's
it's
non-trivial,
because,
first
of
all,
it
requires
a
lot
of
discussions
with
existing
and
subject.
A
Subject
matter:
experts,
the
the
maintainers
of
generator,
that
the
person
that
will
do
the
tasks
will
have
to
talk
with
with
the
code
owners
will
have
to
make
sure
that
existing
docs
are
still
up
to
date.
Maybe
something
is
missing,
so
do
a
interviews
with
the
with
smes
and
to
learn
what
really
has
to
be
done,
then
the
person
will
have
to
really
coordinate
closely
with
with
alejandra.
That
is
leading
the
docs
aspect.
A
We
will
have
to
cover
discussions
about
how
to
then
present
this
documentation
in
the
ui.
If
the
ui
already
exists,
that's
easy!
If
it's
not
yet
there,
we
will
have
to
have
these
discussions
across
the
whole
community,
so
the
person
that
will
work
on
this
issue
between
may
and
october
will
be
really
able
to
touch
all
the
aspects
of
working
in
open
source.
So
not
just
writing
docs
because,
like
again
writing
a
specific
talk
or
writing
a
specific
class
or
or
function.
A
A
Definitely
we
will
have
swags
for
people
that
completed
google
season
of
docs
and
and
for
now
please,
if
you're
already
interested,
remember,
we
have
docs
related
slack
channel
and
then
just
go
there.
Alejandra
is
there,
but
we
not
only
alejandra
other
community
members
and
ask
there.
You
can
already
clearly
state
there
in
the
channel
that
you
would
like
to
apply
for
google's
season
of
talks.
So
please
please
do
it
and
then
yeah,
it's
alejandra
is
coordinating
here.
A
So
she'll,
let
you
know
if
she
will
create
a
dedicated
channel
for
it
like
temporary
channel
to
just
coordinate
the
google
season
of
dogs,
or
maybe
it's
not
needed,
because
in
comparing
to
google
summer
of
code,
definitely
google
season
of
talks.
It's
it's
smaller.
I
would
say
if
it
comes
to
the
amount
of
mentors
and
mentees
and
yeah
definitely
links
to
more
information.
A
So
next
one
the
most
important
one,
google
summer
of
code
summer
of
code
yeah,
it's
confusing,
isn't
it
confusing
for
you,
like
google,
summer
of
code
and
google
season
of
docs
anyway,
this
is
at
the
moment
I
would
say
the
most
important
event
because
deadline
to
apply
it's
it's
pretty
soon
and
we
like
yeah.
I
think
you
already
heard
what
I
was
saying
like.
We
noticed
that
there's
a
lot
of
folks
there
in
the
in
the
slack
and
in
github
contributing
which
is
amazing
and
and
yeah.
A
We
need
definitely
to
have
a
lot
of
mentors
involved
to
be
able
to
onboard
as
many
people
as
possible
to
to
google
summer
of
code,
so
so
yeah
the
most
important
for
mentors.
If
you
want
to
join
us
mentor-
and
you
would
like
to
promote
some
idea
here-
it's
like
in
case
of
google
season
of
dogs
like
remember
it's
not,
it
shouldn't
be
a
trivial
issue
that
can
be
really
easily
fixed,
and
it's
just
about
some
coding
and
it's
like
everything
is
defined.
It's
just
about
writing
the
code.
A
A
The
the
work
is
pretty
pretty
long
so,
and
so
there
are
two
sizes
of
projects:
that's
a
change
comparing
to
last
year.
Last
year
it
was
just
one
size
of
the
project
that
should
be
proposed
as
as
an
idea
for
for
gsoc
and
this
year,
basing
on
the
feedback
they
allow
two
different
sizes
like
medium
and
large
work
hours.
A
It's
all
defined
here.
So
that's
why
this
work
schedule
is
a
bit
different.
So
it
starts
in
june
like
last
year,
but
then
it's
it
can
end
in
september,
like
it
was
last
year
but
yeah.
It's
definitely
okay,
if,
if
like
mendy
and
even
mentor,
agree
that
time
can
be
extended
in
until
november,
so
so
take
these
factors
into
account
when
working
on
an
idea.
A
A
So
as
an
api,
you
can
define
many
different
things.
It's
all
described
in
using
api
specification,
but
there
might
be
some
features
missing
and
you,
as
an
api
user,
would
like
to
specify
more
things
in
asking
api
document,
and
you
don't
have
time
to
go
through
the
contribution
process
to
add
some
feature
into
asking
api.
A
What
people
do
then?
They
use
extensions
like
asympto
allows
you
to
specify
special
fields
x
and
then
the
name
of
the
field.
So
you
can
add
these
fields,
you're
asking
api
documents.
Validator
will
not
complain
on
those
we'll
just
ignore
them,
and
this
way
you
can
yeah
extend
your
asking
api
documents
with
some
custom
fields
and
then,
of
course,
you
code,
your
own
tools
for
it
idea
behind
extension.
Catalog
is
also
that
we
have
a
one
single
place
where
we
can
actually
like
community
can
exchange
extensions.
A
So
there's
something
missing
in
the
spec.
I
want
to
write
my
extension
but
yeah.
What's
the
point
of
inventing
new
extension,
maybe
there
is
already
something
that
community
proposed
this
mvp
extension
catalog
is
about
like
providing
minimal
value
of
the
catalog.
So
because
now
it's
just
a
repo
and
we're
not
really
supporting
it
in
even
enhancing
api
tools.
A
So
the
idea
is
that,
like
we
do
the
person
that
will
pick
up
this
issue
as
mentee
will
of
course
have
to
do
some
coding
in
the
parser,
probably
separate
library,
just
for
extensions
for
parsing
extensions.
Then
there
will
be.
There
will
have
to
be
some
work
on
the
website
and
there
will
have
to
be
some
discussion,
probably
a
presentation
to
the
community.
A
What's
the
proposed
solution
so
so,
basically
to
even
get
the
mvp
for,
for
extension,
catalog,
the
the
mentee
will
really
have
to
touch
different
aspects
of
working
in
open
source
like
discussing
being
patient
with
answers,
getting
answers
from
people
like
interacting
with
the
community
contributing
to
different
repositories,
knowing
different
contributors,
different
flows,
so
yeah
you,
basically
by
after
completing
this
task.
You
touched
all
the
different
areas
of
working
in
open
source
and
asking
api.
A
I
am
the
one
that
is
coordinating
the
efforts,
so
I
will
write
the
official
application
and
I
also
cover
the
backdoor
solution
we
have
with
with
postman
like
in
case
we
are
not
accepted.
We
will
push
the
ideas
through
through
postman,
so
it
should
be
fine
and
we
should
be
able
to
yeah
to
push
all
the
all
the
all
the
projects-
yeah
swags
as
usual-
important
information
for
folks
that
up
participated
in
g-shock
as
mentees
last
year,
so
yeah
just
to
make
it
clear.
A
A
At
the
moment
we
coordinate
all
the
discussions
in
temporary
gsoc
channel
like
we
did
last
year,
then
we
will
just
close
it
because,
like
later
all
the
discussions
should
be
in
the
official
lasting
api
channels,
but
all
the
discussions,
like
all
the
details
like
how
you
can
find
the
g-shock
issues-
that's
that
all
can
be
tracked
in
this
in
this
channel.
We
already
together
with
the
group
that
is
there
already
in
the
channel.
We
we
decided
that
all
the
discussions
on
the
ideas
should
happen
on
github.
A
A
You
can
label
issues
in
discussions.
You
can
label
discussions
and
issues,
so
we
just
have
a
g-shock
label
to
label
all
these
issues
and
then
you
can
easily
list
them
and
pick
the
the
ones
that
are
the
most
interesting
for
you,
then,
of
course,
some
links
so
that
you
can
pick
up
from
the
presentation
and
before
I
continue
further.
There
are
some
questions
I
see
so
one
is
from
ritiki
in
zoom.
Can
someone
be
a
mentor
if
he
she
isn't
a
mendy
previously
like?
No?
A
No,
no
so
like
what
I
meant
that
be
a
meant
or
if
you
were
a
mentee,
it's
it's
just
for
folks
that
I
just
wanted
to
make
a
clear
statement
to
folks
that
participated
as
mentees
in
g-shock
last
year.
So,
like
basically,
g-shock
prohibits
person
to
be
on
g-soc
in
given
organization
twice,
so
you
can
be
a
mentee
only
once
but
mentor
no
like
in
case
of
mentor.
Anybody
can
be
a
mentor.
You
just
need
to
dedicate
your
time
and
and
like.
A
A
A
Sorry,
but
we'll
have
it
we'll
have
it
tomorrow,
because
next
week
I'm
I
taking
a
week
off
so
I
have
to
have
answers
by
tomorrow
and
and
yeah
and
something
super
important
and
it's
about
google
summer
of
code
and
google
season
of
docs-
and
I
hope
I
make
myself
clear
so
the
thing
is:
maybe
I
will
drunk
a
bit
of
a
drunk
drink,
a
bit
of
water.
It's
water.
A
Some
of
the
discussions
were
on
on
google
docs
and
we
had
a
situation
that
sometimes
there
were
like
two
or
three
applications
for
for
the
same
for
the
same
idea,
and
we
could
pick
just
just
one
person,
so
it
was
usually
a
person
that
we
already
knew
from
slack
from
the
contribution.
So
we
knew
that
the
person
is
really
into
a
single
api
because
they
contributed
before
applying.
A
So
we
were
just
like
rejecting
those
that,
like
they
did
not
interact
with
us
at
all,
but
they
just
applied
through
the
online
form
and
that's
how
it
looked
like
last
year
and
this
year
we
want
like
full
transparency
on
discussion,
so
no
google
docs
it's
just
terrible
to
manage.
So
so
there's
everything
on
github,
one
very
important
aspect
of
having
it
on
github
and
and
transparent-
is
that
we
know
and
like
other
mentees
know,
who
already
wants
to
work
on
an
issue
we
can
figure
out.
A
A
So
we
basically
don't
want
to
push
away
folks
that
we
know,
especially
that
we
know
they
are
active
in
the
community
and
they
want
to
really
participate
as
google
summer
of
code.
So
yeah
just
take
it
as
an
advantage.
This
public
discussions
like
when
you
apply
for
something
just
make
it
clear
what
you
want
to
work
on
and
then
and
then,
let's
together
with
a
given
mentor
given
leader
of
the
idea.
A
Also,
regarding
the
question
about
mentors
something
I
forgot
to
tell
you
about
it,
there
can
be
mentors
that
don't
have
ideas.
So
that's
also
something
important
like
you.
Don't
have
to
have
an
idea
to
be
a
mentor.
You
can
be
a
mentor
for
idea
that
somebody
else
provides
like
I
already
have
a
list
or
like
four
or
five
different
ideas,
and
I
would
be
super
happy
if
somebody
wants
to
mentor
the
ideas
that
I
provide.
A
I
don't
have
to
mentor
all
all
of
them
now
yeah
before
I
finish
the
sentence,
there's
a
question
from
akshat
on
on
zoom
question
regarding
the
work
days
and
work
hours,
will
we
have
to
work
in
accordance
with
our
time
zone
or
with
the
other
specified
time
zone
which
we
have
to
manage
with
our
time
since
folks
are
living
in
different
time
zones?
Here.
A
B
A
Yeah,
so
definitely
on
the
working
hours,
something
important
to
to
remember
it's
not
like,
especially
in
open
source,
there's
no
office,
it's
it
doesn't
mean
you
have
to
work
eight
hours
a
day.
It's
your
own
schedule
and
and
you're
gonna
work
in
asking
api
and
at
asking
api.
We
all
are
like
in
different
time
zones
and
we
already
learned
to
work
asynchronously
because
we're
asking
api
work
asynchronously,
so
you
basically
communicate
through
github
or
just
slack,
but
then
wait
for
the
answer
for
the
next
day.
A
We
were
pushing
as
much
transparency
through
the
through
through
github
issues,
but
I
know
that
there
were
other
participants
that
had
calls
with,
with
with
mentors
like
discussing
some
coding
aspects,
some
some
different
things
like
like
a
weekly
checkpoint
like
to
check.
If
everything
is
fine,
maybe
maybe
mentee
needs
some
support
so
yeah.
I,
for
example,
had
one
mentor
that
we,
I
don't
think
we
had
one
call,
I
think,
and
then
we
were
able
to
handle
everything
asynchronously
and
the
other
one.
A
We
just
had
a
few
checkpoints
and
that's
how
it
worked
so
so
yeah,
even
if
like
you're
from
india
and
and
somebody
is
from
from
us,
then
there's
always
some
overlap
of
time
and
if
you
really
need
to
have
checkpoint
like
weekly
checkpoint,
just
you
just
need
to
figure
out.
What's
the
best
time
to
to
satisfy
you
both
but
yeah.
When
you
work
on
these
issues,
it's
your
it's.
A
Your
schedule,
like
it's
you're,
gonna,
learn
that
definitely
it's
it's
not
eight
hours
a
day
work
because
you
like
sometimes
it's
it's
not
really.
A
mentor
decision,
sometimes
like
mentor,
is
really
just
to
mentor.
You
like
give
ideas
guide
you
through
the
process
of
contributing
a
mentor,
will
not
be
a
decision
maker.
In
most
of
the
cases,
a
mentor
will
just
tell
you.
A
A
A
A
A
We
will
join
more
mentors
over
time,
so
you
will
know
already
like
okay,
there's,
jonas
and
he's
like
he's
a
mentor,
and
I
really
love
modelina
so
and
I
have
some
ideas
for
modelina,
but
he
did
not
provide
my
idea
as
official
idea
and
then
you
can
talk
to
the
mentor.
It's
okay
to
to
talk
to
the
mentors
and
say
like
hey.
I
actually
have
a
great
idea.
Would
you
like
to
mentor
it?
I
hope
you
know
what
I'm
saying
so.
A
Basically,
you
can
also
come
up
with
with
good
ideas,
feel
free
to
to
talk
to
mentors
on
slack
and
and
like
check
like,
if
that
would,
if
something
that
you
think
about
could
be
a
good
idea
and
and
the
mentor
would
like
would
be
happy
to
to
mentor
you
because
in
the
end,
it's
just
a
matter
of
of
the
of
the
time
of
the
mentor
like.
If
you
find
somebody
who
can
mentor
you
and
dedicate
time
for
you,
then
then
just
go
for
it
and
come
up
with
your
ideas.
A
A
B
A
A
A
A
We
started
some
time
ago
how
we
assassinate
api
could
on
board
more
women
into
the
project
so
yeah.
I
think
it
would
be
nice
to
try
without
richie.
We
have
some
good
proofs
from
the
community
that
we,
we
are
a
a
welcoming
community.
I
at
least
I
think
so
and
and
women
might
feel
comfortable
here
in
the
project,
I'm
not
sure
if
alejandra
feels
comfortable
but
yeah.
A
That's.
I
have
a
swag
from
the
kubecon
conference
and
I
just
love
it
and
I'm
proud
to
wear
it
on
live
streams,
and
sometimes
when
I'm
meeting
my
friends,
I
wear
my
swag,
but
there
are
also
swags
that
yeah,
you
usually
use
to
clean
your
garden
or
other
stuff.
Where
people
don't
see
you
and
definitely
the
plan
is
that
we
by
that
time,
when
g-shock
and
g-sod
ends,
we
will
have
some
really
awesome
swags
to
share
that
with
you,
but
yeah.
No
specifics!
No,
but
it's
it's
really
gonna
be
badass,
I'm
pretty
sure.
A
A
A
And
no
so
it's
regarding
swag,
so
there's
a
comment
from
akshat
about
like
making
surprise
for
for
you
folks
about
swags
like
so.
It's
not
a
surprise
because
we're
doing
everything
in
public
on
github.
So
you
will
definitely
know
upfront
what
is
in
the
swag
pack
and
and
how
it's
gonna
look
like.
So
sorry,
there's
like
a
dusting
api.
There's
no
surprises!
If
you
know
which
issue
and
discussion
follow
on
github,
you
know
everything.
A
A
That's
a
good
number.
I
think,
although
I'm
not
an
expert
yeah,
but
I
think
the
most
interesting
is
that
we
managed
to
do
a
asking
api
meeting
where
we
live
stream,
but
we
still
have
zoom
and
it's
going
to
be
directly
uploaded
to
to
youtube,
which
is
awesome.
We
just
only
have
to
take
access
to
restream
from
fran,
so
he
doesn't
break
the
titles
of
the
streams
again
and
greetings
to
front
that
is
on
holidays
this
week,.