►
From YouTube: Community Meeting - August 23rd 2022
Description
A
C
B
I'm
trying
to
enable
closed
caption
it's
too
late.
It's
too
late.
A
A
B
Hello,
everyone
hi
I'm
hayes
and
I
will
be
your
host
for
today's
community
meeting
and,
as
you
can
see,
rokash
is
back,
but
I'm
not
giving
up
like
I'm,
not
I'm
not
handling
over
I'm
not
humbling
about
lucas,
because
you
would
have
to
kill
me
to
get
it
so.
B
B
B
So
before
before
we
start
the
meeting,
does
anyone
does
anybody
have
anything
to
share.
B
Okay,
if
not
so
so
I
guess
we
have
to
like
get
started
and
for
some
reason
I
I
feel
more
confident
than
the
last
time
I
don't
know
so
so
before
we
we
have
a
couple
of
things
here.
I
have
a
couple
of
things
here
in
my
agenda,
so
first,
firstly,
I
would
love
to
go.
B
You
know
over
the
first
thing
on
my
agenda,
which
is
the
snkpi
mentorship
program,
so
I
hope
we
had
quite
some
issues
during
the
last
mentorship
and
meeting
we
had
where
a
lot
of
folks,
a
lot
of
the
folks
didn't
turn
up.
Just
one
mentee
attended
the
meeting,
which
was
quite
sad.
I
wasn't
you
know,
I
wasn't
happy
with
that
and
for
some
reason,
a
lot
of
them
didn't.
B
You
know,
share
with
me
before
the
meeting
that
they
won't
be
attending,
even
though
a
few
of
them
did
and
as
you
can
see,
some
of
some
men,
some
mentors
also
haven't
had
from
their
mentee
in
quite
some
time
now,
and
so
some
of
the
mentors
actually
reached
out
to
me
saying
ace.
I've
not
heard
from
my
mentee
for
some,
while
which
I
had
to
like
reach
out
to
them,
and
some
particular
mentee
actually
said
he's
down
with
kovid,
and
I
was
like.
B
Oh
that's,
that's
sad,
but
you
should
have
reached
out
to
your
mentor
first
and
let
your
mentor
know
I'm
currently
down
with
kovid,
not
just
you
know,
ghost
or
mental.
That
is
quite
not
good,
so
I
I
was
thinking
okay,
this
this
meeting
would
be
the
right
time
to
like
discuss,
share
ideas
on
how
I
think
we
should.
B
You
know,
approach
that,
should
we
start
should
I
start
holding
a
one-on-one
meeting
with
individual
mentors
or
keep
on
doing
the
garden
meetings
with
all
mentors
at
once,
even
though
most
of
them
are
not
attending
and
we've
had,
I
think
three
to
four
meetings.
No
three
meetings,
if
I'm
right
and
some
of
the
mentees
haven't
even
joined
for
once-
and
you
know
I
reached
out
to
them-
I
got
no
response
now
I
was
worried
because
why
why
are
they
not
joining?
I
had
no
idea
what
their
progress
is
for
some
reason.
B
A
A
Just
two
okay,
so
it
doesn't
seem
like
a
huge
problem.
Luckily
I
think
one
thing
to
remember
is
that
the
mentorship
that
we,
because
we
tried
the
mentorship
for
the
first
time
this
year
and
we
didn't
set
a
very
strong
deadline.
A
So
the
deadline
is
the
end
of
the
year,
so
there's
still
a
lot
of
time.
So
if
somebody's
sick
of
covet,
like
definitely
what
you
said,
I
agree
with
you.
100
percent,
like
the
person,
should
communicate
it
with
the
mentor
but
also
like
we
have
plenty
of
time
unless,
unless
in
case
of
these
two
mentors
mentees
already
agreed
some
timeline
and
they
they
and
they
do
not
fulfill
it.
Then
it's
a
different
problem.
A
Then
we
have
to
react,
but
I
can
give
you
my
example
like
so,
for
example,
I
I
am
a
mentor
for
two
projects.
One
is
super
advanced
and
your
one
is
not
even
started
yet,
but
I
do
not
did
not
report
it
to
you.
I
don't
see
it
as
a
problem
because
it's
it's
holidays,
and
I
know
that
in
case
of
my
my
mentee,
she
lives
in
france
which,
for
her
it's
also
holidays.
So
I
don't
see
a
problem
with
it,
but
but
yeah
it's
individual.
A
We
left
it
in
the
mentorship
program
individual
for
for
mentors
and
mentees
to
agree
on
the
schedule.
So
definitely
that
should
be
handled
individually.
I
mean,
like
that's
my
proposal
like
some
basically
connects
mentor
and
mentee
like
push
the
mentee
to
to
contact
with
mentor
and
agree
the
schedule.
B
Okay,
that's.
That
seems
like
a
very
good
insight,
because
and
also
I
I
was
worried
because
in
doing
the
last,
the
last
meetings
we
hi
and
the
only
person
that
attended
the
meeting,
we're
having
discussion
around
you
know
mentees
not
having
any
idea
what
the
evaluation
phase
is
like.
B
Yeah,
so
I
I
like,
based
on
my
thoughts
so
far,
I
believe
we
have
to
like
you
know,
like
I
said
earlier,
the
complexity
of
each
project
is
different
right
and
we
we
have
this
initial
deadline
of
the
end
of
the
year
right
and
we
also
need
to
like
have
an
evaluation
phase.
Even
even
if
we
have
those
two
evaluation
fees
and
for
different
projects,
it's
gonna
be
different
right.
B
A
A
I
remember
like
akshat
asking
me
like
one
of
my
mentees
asking
me
like:
what's
the
evaluation
period,
how
it
looks
like,
etc,
etc
so
like
when
we
were
defining
the
mentorship
at
the
very
beginning,
my
I
I
was
always
thinking
about
like
again,
it's
individual
because,
as
you
said,
like
complexity
is
super
different,
some
projects,
it's
just
a
lot
of
discussions
and
not
much
implementation
and
your
ones.
It's
not
not
much
discussion,
but
a
lot
of
coding.
A
A
But
yeah
something
to
check
anyway,
I
lost
the
truck
so.
A
I
mean
like
I
I
personally
as
a
mentor.
I
don't
I
don't
need
any,
let's
say
fixed
evaluation
unless
my
mentee
wants
to
have
it
and
my
regular
checking
or
whatever
like.
So.
I
think
it's
in
the
end
it's
up
to
us,
but
I
don't
have
a
strong
opinion,
how
we
should,
if
we
should
do
this
semi-evaluation
or
middle
evaluation
or
whatever
I
don't
recall,
having
them
with
google
summer
of
code.
Do
you
remember
ace
if
we
were
doing
this.
B
So
that
that
makes
that
makes
so
much
sense,
because,
even
even
though
we
don't
have
it
at
this
particular
time,
I
feel
it
is
something
we
should
implement
in
the
next
mentorship
program,
because
I
can
say
like
I
have
like
it.
Is
this
this
mentees
and
they're
like
so
there's
this
particular
there's
this
particular
mentee.
That
is
having
difficulty.
You
know,
understanding
what
and
what
the
project
does.
I'm
pretty
sure.
B
B
I
need
to
like
dedicate
this
amount
of
weeks
to
learning,
but
I
have
no
idea
when
the
first
evaluation
period
would
be
or
when
my
mentor,
my
mentor,
would
actually
reach
out
to
me
and
say
hey
what
have
you
done
so
far
and
she
would
probably
tell
a
mentor
she's
still
learning
about
the
projects
like
I
was
like.
I'm
pretty
sure
your
mentor
wants
to
won't
be
happy
to
hear
that
because
I'm
like.
So
I
think,
because
we
don't
have
this
evaluation
phase,
so
I
think
the
mentees
are
like
worried
about
how
how
it
works.
B
So
I
I
guess
I
just
have
to
like
you
know,
communicate
back
to
them
like
we
don't
have
an
evaluation
period
right
now,
but
we
do
know
you
are
only
allowed
to
like
run
the
program
till
the
end
of
this
year.
That's
like
the
the
maximum,
the
last
deadline,
so
you
have
all
the
months
you
have
40
days
until
the
end
of
the
year
so
and
another
discussion
that
we
had.
A
But
wait
just
to
sorry
for
just
to
continue
on
this
like,
but
just
just
I
mean
so
we
don't
have
any
evaluation
period
like
we
don't
have
any
fixed
date,
but
it's
again
like
it's
also
because
we
we
left
it
super
flexible
to
people
up
to
mendy
and
mentor
so
so
again
like
it
should
be
like
menti.
If
menti
is
confused,
menti
should
go
to
the
mentor
and
basically
talk
about
it,
because
it's
like
menti
commits
to
some
work
through
the
discussion
with
mentor.
They
should
agree.
A
What's
the
timeline
in
their
case.
What's
the
if
there
needs
to
be,
if
there
have
to
be
some
evaluation
periods,
if
they
agree
something
on,
then
that
should
be
done
between
mentee
and
mentor.
A
So
I'm
I'm
just
like
letting
you
know
like
how
it
was
designed
for
this
year,
like
because,
with
google
summer
of
code,
it
was
easy
like
the
same
timeline
for
everyone,
fixed
deadlines
and
that's
how
google
season
of
docs
works
as
well,
but
in
case
of
this
mentorship
we
left
it
like.
We
wanted
to
have
it
as
flexible
as
possible.
So
it's
all
up
to
many
inventor.
A
B
C
B
We
should
we
should
we
should
fix
it
for
next
year,
okay,
yeah,
so
there's
there's
also
this
debate
with,
like
going
on
with
the
mentees
that
I
feel
I
have
to
communicate
with
you
guys
doing
this
community
meeting.
So
I
think
a
particular
category
of
the
mentees
are
saying
the
program
isn't
paid
that
they
probably
heard
from
from
lucas
or
something
during
a
particular
community
meeting
that
the
program
isn't
paid.
B
Why
another
category
of
interns
are
saying
this
is
a
paid
program,
so
I
was
like
in
the
middle
of
I
don't
know
which
one
to
like,
because,
as
far
as
I
know,
it
is
paid-
and
I
was
like
they
said-
oh,
they
had
from
a
particular
community
meeting
where
they
said
it
is
free
and
I
was
like
well,
I
feel
like
I'm
lost,
so
I
was
thinking
I
have
to
like
bring
it
up
here.
A
It's
paid,
we
have
15k
dollars,
secured
1.5
k
per
project
that
was
submitted
for
voting
to
technical
steering
committee
and
the
budget
was
approved
so
not
sure
where
it's
coming
from.
A
I
hope
I
did
not
miscommunicate
something
but
yeah.
If
I
did
I'm
I'm
sorry
like,
but
yeah
it's
it's
definitely
paid
unpaid.
A
So
there
can
be
like
I
was
recently
contacted
by
one
of
the
by
one
of
the
contributors
that
his
project,
where
he
volunteered
was
not
accepted
by
tsc,
because
we
had
like
20
something
and
we
accepted
only
10
and
he
wrote
to
me
like
if
he
can
still
work
on
it,
just
without
any
payment
on
his
schedule
etc.
And
I
said
like
yeah
definitely
I
can
still
support
you
as
a
mentor.
It's
just
going
to
be
outside
the
async
api
mentorship.
A
B
Okay
cool,
so
since
it
is
paid
so
I'm
putting
myself
in
the
shoe
of
every
mentee
participating
in
this
program,
so
if
it
is
paid,
so
how
do
I
get
paid
like?
How
do
I
know
oh
this
is
I
have
to
like
get
paid?
Is
it
do
I
get
paid
partially
or
do
I
get
paid
just
a
single
a
single
time
after
the
project
is
done.
A
So
we
we
didn't,
have
we
didn't
wrote
down
any
rule
that
we
pay
in
rates?
Is
it
rates
like
trench,
no
like
like?
Basically
it's
one
payment
at
the
end,
that's
as
far
as
I
remember
what
was
written
in
the
whole
proposal
that
we
pay
out
once
the
job
is
done.
A
Basically
because
we
said
like
we
follow
google's
google
summer
of
docs
and
that's
how
it
works
with
google
summer
of
codes
again.
Yes,.
B
B
B
You
are
getting
paid
after
the
program
after
you've
completed
the
project
so
and
I
hope
maybe
in
the
next
mentorship
program,
we
would,
you
know,
tweak
and
do
some
updates
to
make
it
more
flexible
and
much
more
fun,
so
bear
with
us
for
now.
B
So
that's
that's
all
the
questions
I
have
I've
gotten
like
I
got
from
the
mentees,
so
I
think
that's
everything
concerning
the
mentorship
program
and
and
and
also
like
one
more
time
from
the
mentorship
program
which
I
actually
like
discussed
on
during
the
last
community
meeting.
Where
you
know
some,
some
mentees
were
actually
finding
it
difficult
to
understand.
B
You
know
some
projects
they
were
like,
it
doesn't
have
enough
documentation
or
or
they
don't
like-
really
understand
the
project,
maybe
because
it
is
much
more
complex
and
an
example
of
the
project
is
actually
glee
and
yeah.
They
were
saying.
B
Oh,
I
have
no
idea,
what's
the
what's:
what's
the
meaning
of
spec
fest
or
the
time
api
first,
they
don't
understand
like
what
is
about
and
just
want
to
like
contribute,
and
they
feel
they
haven't
seen
enough
examples
to
to
make
them
understand
how
the
project
works
or
less
documentations
and
stuff,
and
I
was
like
this-
this
could
be
an
interesting
conversation
and
I'm
glad
fran
is
here.
C
Yeah,
actually
to
my
mentees.
What
I'm
doing
is
that
please
ask
me
whatever
you
need
to
ask
I'm
happy
to
provide
any
guidance
on
what
glee
is,
how
to
set
up
glee.
What's
the
purpose
of
glee,
as
opposed
to
code
generator,
for
instance,
it's
not
a
code
generator
right,
it's
similar,
but
it's
not
and
and
yeah
like
what
can
I
say
like
we.
Actually,
I
think
we're
running
these
mentorship
programs
as
well
to
improve
all
this
stuff
right.
So
it's
like
a
chicken
and
neck
problem
right,
but
it's
like
yeah.
C
It
is
not
in
a
it
is
not
in
a
good
state,
but
that's
why
we
are
investing
in
in
glee
right
like
so
so
it
becomes
better
right,
better,
documented
and
and
also
it
becomes
better
in
general
right
so
yeah.
Well,
the
only
thing
that
I
think
we
can
do
here,
not
just
with
glee
but
with
any
project,
is
that
mentors
are
there
to
provide
any
any
guidance
they
need.
So
the
the
only
thing
I
can
say
is
is
that
is
that
the
mentors
mentors
know
how
things
work?
C
B
Of
course
yeah
yeah
and
I'm
I'm
pretty
sure,
I'm
pretty
sure
why
I
think
some
of
those
mentees
are
like
quite
nervous
that
reach
out
to
the
mentors
about.
I
don't
understand
what
this
product
does,
because
I
know
maybe
they
don't
want
to
feel
like
the
mentor
saying
what.
B
C
I
get
it
I
understand.
I
I
repeated
it
many
times
in
the
beginning,
like
hey.
No
question
is
a
stupid
question,
like
you
know,
like
don't
feel
bad
for
asking
seemingly
stupid
questions
because
they're
not
I
mean
it
might
seem
stupid
to
me,
but
not
to
you,
because
you
don't
have
the
context
or
yeah.
You
know
many
things
so
yeah
and
also
this
also
allows
us
to
provide
better
documentation
as
well
like
if
you
have
to.
C
If
we
think
if
we
see
that
many
people
are
asking
the
same
questions,
then
probably
this
will
be
documented
in
the
docs
right,
because
that's
a
that's
a
sign
of
as
a
call
like.
C
You
know
that
we
probably
are
taking
things
for
granted
ourselves
because
we
we've
now
been
doing
this
for
a
long
time,
and
we
think
everybody
knows
everything
we
know
and-
and
that's
not
usually
the
case
so
yeah
but
yeah
like
that's
yeah
I'll,
try
to
make
more
effort
on
my
side
and
saying
like
hey.
If
you
have
questions
like
really,
if
you're
struggling
with
something
ask
the
questions,
but
if
the
person
feels
that
they
don't
want
to
look
stupid
and
they
don't
want
to
ask
the
questions
other
than
myself
repeating
this
many
times
like.
C
A
B
Yeah
thanks
thanks
so
much
for
the
explanation
front.
So
no
question
is
stupid,
so
yeah.
B
A
I
would
add
something
to
it
like,
so
I
can
show
you
like,
so
I'm
at
the
moment
also
a
mentor
for
google
season
of
dogs
folks.
So
I
can
like,
like
especially
say
to
fran,
like
I
had
to
write
many
many
multiple
times
directly
to
them
or
also
on
calls
repeat
to
them.
A
Like
really
don't
be
afraid
of
me,
I'm
not
biting,
even
though
I
look
like
and
and
now
it's
it's
smooth,
it's
smooth
and
I
encourage
you
especially
mentors
to
whenever
mentees
won't
like
finally
go
through
this
barrier
of
not
asking
questions
and
they
start
asking
questions
and
they
want
to
have
a
call.
A
So
what
I
do
with
my
mentees,
we
have,
I
have
with
them
like
kind
of
an
office
hour
every
week,
so
we
meet
for
one
hour
with
both
because
they
both
work
on
generator
documentation
and
I
record
these
sessions.
But
I
don't
put
them
public
because.
A
Like
because
to
make
them
feel
that
they're
in
a
safe
place
and
they
once
they
cross
the
barrier
of
asking
questions
but
they're
still
afraid
of
asking
it,
they
don't
ask
it
in
public.
So
I
I
record
these
and
I
publish
them
to
my
my
private
youtube
and
I
publish
it
as
unlisted
video,
so
only
they
can
access
it
through
the
link.
A
So
they
can
so
they
kind
of
have
resource
that
they
can
go
back
to
when
they
have
like
when
they're
missing
some
info
and
they
can
just
re-watch
the
recording.
That's.
A
And
that's
what
I
do
with
them
and
I
I
I
I
so
far
I'm
getting
feedback
that
it
works
with
them.
So
you
can
ace
like
on
this
mentor
mentees
meetings,
like
also
mention
that
that
they
they
could
propose
it
to
mentors
and
it's
it's
a
good
solution,
but
yeah
definitely
remember
like
remind
them
again.
It's
they're,
like
interns
and
like
who
expects
like,
of
course,
they're
hardcore
yeah,
and
I
I
bet
there
are
companies
that
expect
interns
to
implement
the
whole
systems
but
like,
but
not
here.
B
Yeah
thanks
so
much
lukas
for
the
explanation
like
that
was.
That
was
a
very,
very
nice
suggestion
and
I
would
definitely
you
know,
communicate
this
in
the
next
community
meeting.
I'm
sorry
in
the
next
mentorship
meeting
with
the
folks.
You
know
we,
the
mentors
are
always
there
for
them.
So
so
I
think
that
that's
that's
everything
around.
You
know
the
mentorship
area,
so
I
the
next
thing
on
my
agenda,
is
actually
to
like
discuss
around
the
community.
B
So
for
most
of
you
that
didn't
attend
the
last
community
meeting,
so
we
started
building
or
let
me
say,
implementing
a
new
feature
or
a
new
addition
to
the
community
website,
which
we
call
snkpi
slash
community
so
which
will
be
a
place
to
house
everything
community
related.
So
I'm
gonna
share
my
screen,
which
I
did
the
last
time
to
share.
You
know
what
we
currently
have
so
peace.
B
Okay,
so
we
have
this
new
addition
to
the
skpi
website,
so
under
the
community
drop
down,
we
have
sorry.
We
have
the
overview
section
when
you
click
on
the
overview.
B
B
B
So
we
have
we
have
this
section
different
sections.
We
have
the
section
that
would
act
that
would
be
later
renamed
to
ambassador
programs.
We
have
events
and
meetups.
We
have
community
members,
we
have
a
session
to
start
contributing,
so
we
have
another
section.
That
explains
what
most
of
the
importance
section
does.
We
have
community
platforms,
we
have
the
event
and
meetup
sections.
B
We
have
the
advocate
programs
who
would
be
called
ambassador
programs.
Then
we
have
different
sections,
also
sections.
B
So
this
is
just
a
simple
design
or
implementation
of
what
we
have
so
far
and
I
think
we
got
to
put
a
question
made
into
a
new
branch
called
community
in
the
essence
website
rebel.
So
if
you're
interested
you
can
you
know
it
from
there.
B
So
this
is
what
we
have
so
far
and
we
have
a
particular
link,
I'm
going
to
share
with
you
guys
for
the
roadmap.
B
B
B
So
that's
what
we
have
so
far
on
the
new
community
section
we
are
putting
in
place
and
we
have
like,
so
we
also
have
a
list
of
documentation
issues
that
we
need
help
with,
and
I
think
lucas
this
actually
is
like
related
to
you,
because
I've
seen
a
lot
of
people
who
are
interested.
B
You
know
nebulous
documents,
all
this
stuff,
like
configuring,
release,
pipelines
from
js
how
we
post
on
official
linkedin,
accounts
and
stuff,
like
that-
and
you
know
a
lot
of
these
folks
like
I
I'm
pretty
sure
I
have
like
six
people
that
are
interested
that
reach
out
to
me
privately,
that
are
interested
in
documenting
all
this
stuff
that
we
have
here
and
they
were
like
they
didn't
know
how
to
get
started.
They
didn't
know,
even
though
they
say
some
of
them
have
experience.
You
know,
writing
documentations.
B
A
Yes,
what
so
so?
Yes,
there's
a
lot
of
docs
to
provide
we're
missing
a
lot
of
documentation
for
the
community
as
like,
contributor
guides,
etc.
There
is
a
lot
of
content
on
videos,
so
there
were.
There
was
my
presentation
about
how
to
become
contributor
and
tsc
member
from
last
conference.
There's
a
video
where
I
was
sharing
and
explaining
the
whole
cicd
setup.
I
think
it's
shared
in
this
in
comments
in
this
issue,
but
kick
me
in
my
butt.
If
I
didn't
do
it
I'll,
do
it.
A
And
so
there
are
two
two
videos
and
I
already
actually
had
a
call
with
tabach
one
of
the
guys
that
wants
to
contribute
dogs-
and
I
actually
had
a
call
with
him
today
and
I
did
what
I
just
told
in
the
cons
in
the
context
of
mentorship
program.
So
I
basically
had
a
call
with
him
and
I
was
explaining
him
everything
how
we
create
repositories,
nothing
api,
how
they,
how
people
have
to
actually
give
pro
example
of
missy
and
design
system
repo
like
how
the
whole
process
of
getting
approval
works.
A
How
me
and
fran
we
create
repo
what
configuration
has
to
be
applied,
what
cicd
et
cetera?
Sorry.
So
that's
how
I
address
it,
because
I
feel
that
that
that's
the
best
way
that
I
provide
documentation,
input
through
the
verbal
communication
and
explanation,
a
recorded
video
that
someone
can
go
back
to
and
and
transform
it
into
documentation.
A
So
if
you
have
someone
that
is
writing
to
you
directly,
not
in
how
to
contribute
or
docs
such
channels,
then
let
them
know
that
I'm
open
like
whenever
they
ask
me.
I
can
set
up
a
call
with
them
or
asynchronously
record
a
video
and
share
with
them,
or
if
it's
not
the
best
way
for
them,
I
can
do
a
documentation
input.
It's
like
like
a
written
documentation.
A
It
puts
whatever
works
for
for
people,
so
they
just
need
to
pick
the
title
of
the
document
and
I
can
share
what
I
what
I
know
and
then
they
can
write
it
see
the
plan.
B
Oh,
that's,
that
seems
pretty
cool
rakesh,
so
I'm
do
do
you
have
any
do
I
have
to
you
know
refer
them
to
you
or
you
already
have
a
particular
stream.
I
can
send
a
link
to
them
for
them
to
like
preview.
A
So
I
can
let
me
let
me
quickly
check
this
epic
issue
just
to
double
check
quickly.
If
I,
if
this
links,
are
there
already.
A
Like
this
issue
that
you
have
for
the
community
section,
there's
already
like
I
made
one
comment
actually
to
it-
was
also
directed
to
tabach
that-
and
I
linked
to
this
youtube
video,
where
I
make
a
full
explanation
of
the
whole
cicd
setup
that
we
have
adjusting
api,
all
the
workflows
that
we
have
and
we
have
to
document
it.
A
So
that's
a
like
over
one
hour,
long,
huge
video
that
provides
a
lot
of
input
for
documentation,
the
other
one
I
can
share,
also
in
the
issue
about
the
how
to
become
a
tsc
member
and
how
to
contribute.
But
with
this
case,
actually
there
is
already
one
volunteer.
A
A
A
B
A
A
B
Of
course,
like
what
so
I'm
gonna,
I'm
gonna
refer,
I'm
gonna
redirect
anybody.
That's
like
reach
out
to
me
to
help
to
you,
because
I
need
documentation.
So
I
think
that's
that
and
we
actually
need
help.
You
know
designing
these
teams
like
to
help
doing
improve
what
we
currently
have
on
the
community
section,
how
we
can
improve
it,
and
also.
We
also
need
insights
on
you
know
which
content
should
be
changed.
What
should
be
where
and
and
stuff
like
that,
I'm
pretty
not
smart
enough
to
know
what
should
be
there
and
what
shouldn't
be
dead.
B
So
that's
that's
it
and
I
also
have
like
we
also
started
discussion
about.
You
know
office
hours
with
technical
journey
committee.
You
know
a
few
people
would
like
saying
it
was
a
good
idea
and
yeah
I
was
thinking.
Could
we
could
we
like?
So
I
think
I
had
jonas
on
the
last
community
call
and
he
was
actually
saying
what,
if,
how
do
we
have
calls
with
skbi
users
that
are
like
using
snk
api
like
private
companies
or
something
do
they
have
to
like?
A
It's
up
to
us
how
we
define
it,
so
I
we
I
mean
depends,
I'm
not
sure
how
front,
but
I
was
usually
when
somebody
in
private-
and
I
know
that
person
was
from
some
company-
was
asking
me
that,
like
if
I
could
present
maybe
on
some
internal
event
or
just
have
a
meeting
to
explain
something.
A
Then
it's
very,
very
individual.
So
once
I
said
like
you,
first
have
to
become
a
sponsor,
like
your
company
have
to
become
a
sponsor
of
the
initiative,
but
for
one
guy
I
made
an
exception
because
it
was
not
about
presenting
in
the
company,
but
he
he
was
from
a
company
from
oracle
actually,
but
he
he
actually
is
writing
a
generator
code
generator
that
they
want
to
contribute
further
in
the
future
to
asking
api
so
yeah.
It's.
A
I
think
it's
already
a
huge
thing
to
help
them
and
get
them
on
board
actually
and
join
the
project.
So
I
didn't
tell
him
like:
first,
you
have
to
donate
and
then
I'm
gonna
help
you
so
it's
it's.
It's
gonna
be
hard
to
define
what
we
can
do.
What
not
so
that's
my
opinion.
C
I've
done
both
so
like
in
the
beginning.
I
used
to
do
this,
like
in
internal
company
meetings
I
got
invited
to
so
I've
been
pitching
async
api
and
explaining
how
it
works
and
how
to
contribute
in
many
internal
company
meetings
and
then
at
some
point
I
realized
that
that
is
a
lot
of
work,
and
that
is
not
really
scalable.
C
Like
imagine
I
mean
you
will
need
a
a
a
team
of
people
doing
that
with
many
companies
per
week
right
just
to
to
be
able
to
actually
spread
the
word
around
the
world
and
and
even
like
this
will
be
complicated.
So
what
I
do
is
I
often
do
that
as
well,
like
I'm
now
doing
this
that
that
luca
said
like,
if
you
want
me
to
do
this
in
your
internal
meeting,
you
got
to
be
an
a
sponsor,
actually
not
any
kind
of
sponsor.
I'm
asking
for
platinum
sponsor
specifically.
C
So
yes,
like
I'm,
not
gonna,
spend
my
time
on
on
a
company
that
is
not
willing
to
to
give
back
to
the
community
so
and-
and
I
always
like-
I
always
ask
them
to
to
understand
it
right
like
it's,
I'm
giving
you
this
work
for
free.
The
last
that
I
can
ask
you
is
something
to
give
back.
Like
luca
said.
If
they
are
contributors
like
solas,
for
instance,
I
mean
solas
doesn't
need
any
introduction
to
the
spec
they
already
know,
but
solas
is
contributing
a
lot
of
codes,
so
so
yeah.
C
If
they
were
asking
me
to
do
this
for
zola's
internal
event,
I
will
do
it.
I
will
not
ask
anything,
but
but
because
they're
contributing
a
lot
of
their
time
right
so
and
but,
if
you're
not
going
to
contribute
any
anything,
no
engineering,
no
time
not.
No,
no
pitching,
no
death
rail.
No
talks
about
this
in
kpi
in
conferences.
C
Anything
then
I'm
gonna
ask
you
for
money
that
is
like.
Then
you
gotta
become
a
sponsor.
If
you
don't
have
time
or
you
don't
want
to
be
doing
that
and
yeah
nobody
yet
accepted
this
deal,
I
thought
it
was
going
to
work
well.
B
A
C
Yeah
yeah,
but
it's
at
least
it's
not
still
in
time
for
mass,
which
is
cool
and-
and
that
is
something
good,
but
that's
what
we
do
if
someone
is
in
the
community
is
happy
to
do
this
in
their
spare
time
because
they
want
to
practice
talking
or
pitching
at
companies.
That's
that's
also
fine,
I'm
not
we're
not
saying
that
people
should
not
be
doing
this.
C
We're
saying
that
we're
not
doing
this
because
we
got
tired
of
this,
but
but
I
must
say
that
it
was
useful
so
so
yeah
it
was
useful
for
learning
how
to
teach
and
how
to
give
internal
meetings
and
and
get.
B
Out
yeah,
so
I
I
I
typically
tagged
every
tsa
member
in
the
discussion.
I
guess
yeah,
I
think
I've
gotten
few
replies
say
they're
interested,
so
I'm
also
interested,
and
I
would
love
to
do
you
know
I'd
love
to
do
it
more
often.
B
You
know
just
specify
oh
I'm
available
during
this
hour
of
the
week
for
the
discourse
and
the
thing,
because
I
because
I
I
actually
have
that
idea
based
on
you,
know,
people
that
are
using
kpi
for
the
first
time
that
you
know
would
typically
have
questions
and
and
you're
not
saying
you
know,
some
people
would
actually
want
to
take
advantage
of
that
and
they're
using
this
thing
privately
and
they're
not
giving
back
to
the
community.
So
I
was
like
we
have
like
fixed
stats
right.
A
It's
it's
all
about
how
we
describe
it
and
defining
rules,
but
in
the
end,
what
fran
said
it's
it's
time
of
the
tsc
member
like
they
can
spend
it
as
they
want.
So,
if
some
like,
if
jonas,
do
not
want
to.
A
Be
I
don't
know
what
the
term
did
you
use
like
exploit,
no
like
if
like
like,
if
it's
for
jonas,
it's
a
problem
that
some
company
would
use
this
time
in
a
wrong
way
and
ask
him
to
explain
what
dashing
api
is.
Then
he
can
just
decline,
but
some
tsc
member
might
be
okay
doing
it.
A
So
we
just
can
write
down
a
rules
in
this
office
hours
like
recommendations
not
like
that.
It
has
to
be
like
this
but
recommendations
like
if
somebody
wants
to
contribute
and
it's
a
meeting
about
how
modelina
works.
A
How
kind
can
I
contribute
to
it,
then
it's
it's
fine
and
then
have
a
rule
like,
but
please,
whenever
somebody
is
coming
from
some
company
and
they
need
a
meeting
just
where
you
explain
what
asking
api
is
then
please
first
ask
them
to
become
platinum
sponsors,
because
that's
also
what
is
in
the
platinum
sponsorship
description
that
when
you
become
a
platinum
sponsor,
you
have
one
hour
or
something
consulting
three
one
month,
one
hour,
something
like
we
would
have
to
check
with
open
collective.
C
I
think
it's
two
hours
per
month
or
something
two
hours
yeah
or
four
hours
per
month,
or
something
like
that
and
nobody
ever
used
it
so
yeah
just
find.
The
funny
thing
is
that
people
who
are
becoming
platinum
sponsors
are
the
ones
who
are
more
aware
of
what
async
api
is,
and
they
are
the
ones
that
need
less
help.
C
So
yeah,
so
they
don't.
They
don't
actually
need
this.
This
time,
usually
usually-
and
also,
I
want
to
mention
that
we're
talking
about
tse
members,
but
also
ambassadors
right
so,
for
instance,
and
actually
any
kind
any
member
of
the
community,
but
but
ambassadors,
especially
as
well,
will
be
having
this
kind
of
role
as
well
right
like
like
they
will
be
preaching
about.
C
I
think
it
is
a
same
thing
like
if
they
want
to
be
preaching
to
companies
in
the
internal
meetups
and
that's
fine,
but
that's
up
to
them
like
we
can
give
them
some
guidelines
that
they.
So
these
companies
don't
abuse
their
time.
Basically,
because
many
people
who
try
to
abuse
your
time
and
and
and
your
kinder
so
so
yeah
just
we
can
give
some
advices
of
what
we
learn
from
the
last
years.
C
B
C
To
manage
my
my
invitations
from
companies
and
so
on
to
to
to
have
a
meeting
quick
meeting
30
minutes,
it
was
never
30
minutes
and
I
had
to
disable
it.
So
I
instead
made
it
manually
now
because
it
was
insane.
It
was
too
much.
B
B
So
I
think
that's
that's.
Basically
everything
I
have
yeah.
I
I
remember
I
I
I
remember
something
I
wanted
to
like
say
and
I've
forgotten
why
you
say
something
run
yeah
I
remembered
so
I
was
open
to
have
a
contributor
called
ismail
on
this
call,
but
I
think
for
some
reason
he
couldn't
join.
B
B
B
You
need
to
you
know,
you
need
to
tell
us
how
you
know,
because
this
guy
wrote
amazing
stuff,
and
I
was
saying
you
need
to
tell
us
how
essential
is
actually
helping.
Save
the
planet.
C
I
think
you
have
to
ask
ismail
velasco.
C
A
It
was,
it
was
a
good
article
eye
opening,
but
the
thing
is
that
I'm
ignorant
in
this
topic.
So
that's
why
it
was
eye-opening.
For
me,
I
I
know
I
know
more
from
the
article,
but
how
this
can
be
done
through
the
spec.
A
I
have
no
idea,
but
what
I
can
tell
you
like
after
reading
this
article,
so
one
of
the
topics
that
I
have
for
the
mentorship
program
is
actually
the
mvp
implementation
of
the
extension
catalog
that
we
we
have
this
concept
long
time
in
the
asking
api
initiative
that
we
maintain
a
public
extension
catalog
through
which
we
can,
with
the
community
add
some
extensions
to
the
spec,
see
how
they
work,
how
they
are
adopted,
and
then
it's
easier
to
push
things
to
the
to
the
spec.
A
And
that's
what
I
was
thinking
like
when
I
was
reading
this
article
and
this
open
question
like
how
we
could
do
it
with
using
api.
A
That
was
my
first
thing
like
it's
a
like
perfect
candidate
for
the
for
this
mvp
and
this
extension
catalog
like
to
first
design
this
items
through
the
extensions
and
then
it's
like.
It's
shared
like
a
package
like
like.
If
somebody
wants
to
have
a
system
that
is
responsible.
A
If
it
comes
to
the
emissions,
then
that
would
be
like
advertised
like
a
set
of
extensions,
that
they
could
use
and
they're
supported
in
our
tools
and
then
somehow
pushed
maybe
into
main
spec.
But
the
thing
is
that,
like
first,
we
need
to
see
some
like
some
specific
proposal
like
how
these
things
could
be
really
done,
because
I'm
not
sure
like
from
the
article.
A
I
was
I
liked
the
article
because
it
was
not
very
supportive
for
http
polling,
and
I
also
don't
like
it,
but
but
with
the
spec
like
this
pack
itself
helps
already,
but
it's
just
that
some.
The
company
anyway,
has
to
go
like
move
from
http
polling
to
to
even
driven
architectures
like
web
sockets
or
something
different,
and
it's
not
spec
that
supports
it.
Specs
spec
supports
the
protocol,
but
there's
no
specific
setting
in
the
in
the
spec
that
is
making
an
impact.
C
That
will
be
really
cool,
so
I
think,
without
having
to
read
the
article
so
take
my
comment
with
the
green
results
cause.
It's
really.
I
don't
know
what
it
is
about,
but
by
the
arctic,
by
the
title
of
the
article
and
the
one,
the
first
or
two,
two
paragraphs
that
I've
read.
C
I
think
it
is
more
about
the
very
nature
of
event-driven,
architectures
and
and
persistent
connections
right.
So,
if
you
have
a
persistent
connection,
it
is
always
cheaper
in
terms
of
research.
It
depends
on
the
resources,
but
it
is
always
cheaper
than
having
request
response.
I
I
see
sergio
is
doing
like,
of
course.
C
That's
why
I
said
like
depends
on
the
resources
if,
like
for
instance,
ram
memory
will
run
quickly,
you
will
run
out
of
memory
quickly
in
the
server.
If
you
have
many
many
open
connections
at
the
same
time.
So
that
is
that,
because
it's
usually
not
just
a
ram,
but
it's
usually
mapped
to
the
file
system
as
well,
so
these
connections
are
mapped
to
the
file
system,
so
so
these
are
resources
this.
C
This
is
consuming
resources,
but
if
you're
transferring,
for
instance,
I
think
you
need
to
keep
a
balance
there
right
like
if
you're
transferring
too
much
data
too
fast
in,
like
very
often
not
too
fast,
but
very
often,
then
a
persistent
connection
will
be
ideal
there,
because
yeah.
The
only
thing
you
have
to
do
is
just
to
exchange
stuff
and
you
you
avoid
having
to
send
again
the
http
headers
and
repeating
yourself
in
an
http
request.
C
For
instance,
most
of
the
requests
is
not
about
your
data,
the
data
that
you
want
to
send,
but
about
the
http
protocol
and
then
these
again
and
again
and
again
being
the
same
if
they
are
the
same
of
course
it's
redundant
right
and
it's
very
much
redundant.
But
if
it's
the
same,
if
it's
the
same
call
over
and
over
and
over
and
over
and
very
frequently
like
a
few
times
per
second
something
like
that,
then,
if
you
have
a
person
connection,
you
only
pass
these
headers
or
this
information
in
the
beginning.
C
When
you
open
the
connection
and
then
you
start
exchanging
messages
very
often
like
few
times
per
second
or
something
like
that,
then
it's
cheaper.
Of
course
it's
cheaper
because
you
have
to
transfer
less
bytes
over
the
network
right.
But
if
you
are
using
this
persistent
connection
to
transfer
just
one
message
a
day.
C
Cheaper
at
all,
that's
it's
cheaper
to
make
a
request
right
because
to
to
make
to
keep
the
connection
open,
you
need
to
to
still
send
a
message
from
time
to
time,
which
is
called
the
heartbeat
and
it's
to
tell
the
server
hey
I'm
here,
I'm
still
here,
I'm
connected
right,
don't
close!
My
connection,
I'm
still
here
so
this
is
consuming.
This
is
this:
is
data
that
you're
sending
these
are
bytes
bytes
that
you're
sending?
C
So
if
you're,
not
if,
if
most
of
your
messages
are
heartbeat
messages,
then
then
you're
not
taking
advantage
of
an
of
a
persistent
connection
right
so,
but
that's
the
very
nature
of
eda's,
of
or
or
even
driven,
architectures
and
and
and
messaging
protocols,
and
so
on,
not
so
much
about
this
in
kpi.
C
What
I
agree
that
asm
kpi
is
promoting
and
making
it
easier
to
work
with
this
kind
of
apis
or
this
kind
of
protocols,
messaging
protocols,
even
different
architectures,
and
so
on
so
indirectly.
In
my
opinion,
I
think
we
are.
We
can
help
like
lower
the
emissions.
Of
course,
if
you
want,
if
you're
really
worried
about
it
right,
but
I
think
it
isn't
itself
by
itself,
I
don't
think
it
will
lower
anything,
because
it's
just
a
an
offline
spec
and
it's
not
running
anywhere
or
it's
not
doing
anything
right
so
so
yeah.
C
But
I
think
that,
because
we're
doing
this,
then
it
will
become
easier
in
these
scenarios
where
people
are
like
polling
very
frequently
for
messages
and
getting
always
the
same
result
like
no,
no
there's,
no
new
information
for
you.
They
could
be
using
a
persistent
connection
and
we
could
make
it
easier.
Yeah.
That's
now
I'll
read
the
article
to
see
if
it
really
makes
sense,
but
that's
what
I
suspect
is
coming
it's
coming
from
or
it's
it
is
going
or
it's
somehow
related
right
to
consumption
to
to
this
kind
of
consumption.
Yeah.
C
B
Planet
yeah
that
was
that
was
that
was
that
was
amazing,
and
I
think
that's
that's
everything,
because
I
couldn't
forget
about
that
and
I'm
willing
to
like
bring
ismael
into
the
next
community
meeting.
If
I
can,
because
he
wrote
an
amazing
article,
so
that
was
that
was
that's
everything
on
my
agenda
like
if
you
have
anything
you
might
want
to
discuss.
I
believe
right
now
is
the
time.
A
A
So
just
just
remember
like
in
the
end,
we
always
talk
that
meetings
are
not
not
mandatory,
so
just
give
them
like
if
they
cannot
come
to
the
meeting
or
and
share
their
opinion
or
or
actually
some
status
if
you're
doing
the
status
checks.
I
don't
know
just
give
them
this
opportunity
that
if
they
don't
join,
then
they
should
at
least
give
you
a
written
information
on
slack.
A
So
just
yeah
don't
require
meetings,
because
it's
okay,
yeah.
B
Of
course,
thanks,
yeah,
okay,
thanks
gosh,
I'm
I'm
going
to
do
just
that.
I
think
that's
even
better
because
yeah,
why
not?
We
don't
require
meetings
yeah,
maybe.
A
C
A
note
here,
it's
amazing
from
my
side
from
my
perspective,
that
I
started
running
these
meetings
in
the
beginning,
because
I
was
probably
the
only
one
in
the
project
yeah,
so
I
started
in
and
when
and
when
lucas
joined.
I
think
the
first
week
I
already
told
him
like
now
from
now
on.
You
do
this.
You
figure
out.
C
C
B
C
Yeah-
and
this
is-
and
I
think
this
is
a
call-
I
mean-
forgive
me
if
I'm
probably
going
to
fart,
but
this
is
a
call
to
the
whole
community
like
we
don't
have
to
be
always
the
same
host.
C
B
Yeah,
so
I
think
that's.
B
So
we
we
already
run,
we've
already
run
out
of
time
because
just
an
hour,
so
I
think
I'm
gonna,
just
you
know
summarize
everything
we've
spoken
about.
We
talked
about
the
challenges
of
the
mentorship
programs
and
how
we're
going
to
address
most
of
these
and
how
we
are
you
know
using
this
current
mentorship
program
to
collect
data
and
feedback
for
the
next
one
to
make
it
better,
and
we
also
discussed
a
discussion
around
the
community
section
we're
implementing
and
we
need
help
we
need
help.
B
We
need
help
especially
designs
if
you're
a
designer
watching
this
live
stream,
or
would
it
help
me
see
we
need
help.
So
if
you
we
once
again,
we
need
help
so
and
also
we
discussed.
We
have
a
discussion
around
one
of
the
main
one
of
the
contributors
that
did
an
amazing,
direct
and
amazing
article
concerning
how
ckpi
could
help
produce
global
emission
in
a
significant
way
and
yeah
and
how
http
pollution
should
be
dead
by
now.
B
Yeah
man.
Yes,
so
that's
that's
everything
we
discussed.
Thank
you
folks
for
joining
this.
My
team,
I'm
looking
forward
to
seeing
you
in
the
next
one
and
I
will
still
be
your
host.