►
From YouTube: Thinking Out Loud #10 — with Lukasz Gornicki
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
Hello
folks,
once
again,
one
more
week,
I
hope,
you're
following
us
closely
this
time.
I
have
the
pleasure
this
this
today.
The
pleasure
to
invite
someone
who
is
already
known
by
the
async
is
in
kpi
community.
A
I
mean
lucas
right,
lukas
kurnicki,
but
before
I
let
him
get
into
stage,
let's,
let's
leave
him
there
waiting
in
the
in
the
in
the
left
side
of
restream.
I
think
it's
cool.
You
cannot
see
him
but
he's
there
like,
and
so
I
would
love
to
give
a
few
give
you
a
few
messages
before
we
start.
So,
first
of
all
is
so
there's
no
script,
so
we're
gonna
have
a
live
chat
here
and
just
think
about
it
think
about
think
out
loud
about
a
topic
today.
A
The
topic
is
going
to
be
about
building
communities
and
growing
communities
and
improving
the
the
health
of
the
community
and
especially
the
the
async
api
one,
as
you
can
imagine,
but
some
things
may
apply
to
the
community
as
well.
Also,
I
don't
want
you
to
forget,
so
we
have
in
youtube.
You
can
find
an
option
to
enable
closed
captions,
so
we
made
sure
that
you
can
enable
them.
A
I
hope
with
it
right
this
time
we
had
lots
of
troubles
today
with
time
zones
and
then
so
on,
so
so
yeah.
So
I
hope
it's
working.
If
not,
let
me
know
and
yeah
that's
it
and
also
would
love
to
reinforce
that
point
like
during
the
conversation.
So
this
is
not
just
lucas
and
I
to
keep
things
simple.
A
Let's
say
only
lucas
and
I
are
on
stage
will
be
on
stage
today,
but
please
participate
and
chat
and
we
always
read
the
questions
or
the
comments
or
the
thoughts
that
you
leave
there
and
we
make
sure
they're
heard
and
also
they're
visible
on
on
screen
all
the
time,
so
so
yeah
so
feel
free
to
to
leave
your
thoughts
there
yeah,
I
said
jonas,
is
telling
me
that
subtitles
are
not
available.
A
Of
course
not
jenna's
like
we
always
have
two
days,
it's
it's
a
wrong
day
for
for
us,
so
I'm
sorry
for
that.
I
don't
think
we
can
change.
It
live
once
the
live
stream
has
started
so
so
yeah
thanks
jesse
for
the
nice
hat
compliment.
A
Let
me
let
me
invite
lucas
into
stage
here
we
go
hey,
say:
hi:
how?
How
do
we
do
it?
Is
it
like
not
like
this?
We
get.
We
have
to
talk
like
this
right,
make
it
more
real,
maybe
yeah
something
hi
fran.
A
That
would
be
too
much,
no,
no,
no
so
yeah!
I
always
tell
the
guests
to
introduce
themselves.
A
I
guess
you
don't
need
introduction,
but
there
may
be
a
case
that
someone
who's
watching
still
doesn't
know
you.
So
please.
B
I
live
in
poland
in
a
village,
so
my
internet
sucks,
I'm
a
village
man
and
I
work
for
postman,
but
basically
to
work
on
asking
api,
and
before
that
I
was
working
with
different
roles
like
technical
writer,
developer,
product
owner
community
manager,
part-time
and
so
many
different
roles
in
sap,
so
a
big
giant
and
and
then
I
I
got
sucked
into
open
source
and
got
in
love
with
fasting
api
and
decided
to
to
work
here
full
time
since
two
years
trying
to
scale
the
community
build
the
community
around
using
api
using
different
ways
of
building
the
community
and
yeah,
and
I'm
a
I
guess.
B
If
you,
if
you
have
to
have
some
name
for
my
position
but
yeah,
I
do
have
a
name
and
you
do
have
a
name
for
that
position.
Yeah.
It
was
changing
over
time.
But
now
I
think
it's
I'm.
In
the
blog
post,
I'm
saying
I'm
community
guardian
yeah
yeah,
because
at
the
beginning
I
think
I
had
dev
sword
to
have
come
guard
or
something
like
or
whatever.
B
But
yeah,
who
cares
about
these
names?
It's
all
about
what
you
do
not
how
you're
called
I
agree.
A
So
well
for
those
who
don't
know,
he
didn't
say
anything
because
he
is,
you
know
humble
and
will
not
ever
say
that.
But
yeah
people
know
me
because
I'm
the
creator
of
facing
kpi
but
lucas
is
actually
the
creator
of
this
big
community.
Let's
say
so
so
once
I
started
the
the
the
project,
I
created
a
community
around
it,
but
it
was
not
like
an
active
community.
So
it
wasn't
like
very.
B
A
Active
there
wasn't
many
many
people
interacting
with
each
other
and
and
then
I
hired
lucas
to
to
join
me
and
and
and
at
some
point
because
of
the
things
he
started
doing
in
this
community.
A
A
I'm
not
I'm,
I'm
not
doing
any
community
work
at
all
or
almost
the
community
works
since
then.
It's
all
it's
all
what
you're
doing
you're
too
humble
so
now,
mandatory
question
since
I
was
mentioning
this
is.
A
B
A
different
question:
how
did
you
grow
the
community?
I
love
this
kind
of
questions.
You
could
ask
it
like
two
weeks
ago
so
so
I
have
time
to
prepare
the
answer.
That's
the
thing.
B
So
like
so
before,
before
joining
using
api,
I
was
doing
some
community
work
for
one
of
the
open
source
projects
we
were
building
at
sap
and
during
that
period
I
think
it
was
one
one
and
a
half
or
one
year
or
maybe
more
but
yeah
anyway,
I
was,
I
was
pretty
fresh
with
the
topic
and
I
was
basing
a
lot
of
assumptions
from
what
I've
learned
from
cncf
foundation
and
basically
kubernetes
community,
because
we
were
building
products
that
was
close
to
kubernetes.
B
So
for
us
yeah
we
even
wanted
to
join
cncf.
So
for
us
it
was
like
easy,
like
mimic
everything
they
do
and
it
should
be
fine
and
then
a
dusting
api.
I
knew
it's
not
gonna,
be
the
same
like
because
it's
it's
it's
different,
so
I
think
that
my
like
I'm
not
not
sure
how
others
usually
approach,
something
that
they
don't
do
they
didn't
do
before
and
they
have
to
start
something
from
scratch.
So
I
basically
I
took
it
from
my
perspective.
B
I
was
I
came
in
from
a
corporation
with
multi-level,
not
marketing,
multi-level
structure,
with
many
product
managers
on
the
way
and
different
roles,
different
politics,
etc,
etc.
B
So
I
was
always
looking
on
open
source
as
a
like
a
holy
like
when
you
take
a
holidays
from
work
like
you,
you
go
into
a
safe
place
where
you
basically
don't
have
anything
that
you
could
say,
damn
it
it's
like
in
my
company,
so
I
I
think
that
unconsciously,
that's
what
I
was
doing
first,
so
like
making
sure
that
whatever
I
don't
like
in
my
in
my
daily
job,
I'm
gonna
fix
it
here
so
yeah.
That's
why
everything.
A
B
B
A
B
No
such
things
and
basically
like
the
biggest
pain
with
with
work
for
on
a
product
in
a
big
company,
but
I
guess
in
startup
the
same
is
like
time
pressure
so
yeah.
I
wanted
to
make
sure
that
we
can,
as
a
community,
take
advantage
of
this
like
just
no
pressure
like
it's
better.
If
we
do
something
longer
and
then
discuss,
and
so
that's
why
I
was
always
pushing
for
these
different
ways
how
we
can
make
things
as
open
as
possible
as
as
friendly
as
possible.
As
welcoming
as
possible.
B
A
A
You
know
this
crazy
speed
that
you
have
to
always
have
like
you
delivering
quickly
as
quick
as
possible.
You
have
to
deliver
value
as
quick
as
possible
and
and
it's
yeah
it's
it's.
It's
chaotic.
It's
it's
somehow
like
at
some
point
you
get
you
get
like.
A
Can
I
say
like
immersed
into
this
fast
fast
fast,
fast
mood
right,
like
everything
should
be
fast,
and
you
don't
have
time
to
think
things
well
and
and
yeah
like
it's.
It's
really
counterproductive
for
a
long-term
project
or
for
a
research.
A
If
you
want,
if
you,
because
in
the
end,
what
we're
doing
here
is
research,
it's
a
research
and
development,
of
course
as
well,
but
so
so
yeah,
it's
not
cannot
be
treated
as
a
product,
at
least
not
entirely
right.
So
yeah-
and
I
remember
when,
when
he
joined
by
the
way
one
of
the
first
things
that
I
started
doing
is
there's
a
lot
of
things
to
do.
There
are
lots
of
things
to
do.
We
need
to
get
somehow
this
thing
sorted
out.
A
Do
we
really
need
to
do
this
like
really
it's
too
much?
It's
and
I
was
like
yeah.
It's
true
like
this
is
exactly
what
I
hated
about
my
previous
job
and
and
I'm
now
I'm
here.
I
have
the
the
the
the
power
to
decide
how
we
can
do
this
and
I'm
mimicking
something
that
I
don't
like
and
and
that's
going
to
affect
others
not
just
the
ass,
but
it's
going
to
affect
the
result
and
and
how
we
treat
community
contributions
and
and
how
fast
we
we
tell
people.
A
They
will
miss
the
opportunity
to
contribute
and
that's
what
happens
when
you
live
in
a
village
in
poland.
Basically,
you
get
you
lose
your
connectivity
and
yeah.
Basically,
you
get
you
get
out
of
the
call,
but
what
I
was
saying
is
in
the
meantime
he
comes.
He
comes
back.
What
I
was
saying
is
that
precisely
this,
this
kind
of
rash
right,
it's
is
sometimes
counterproductive
like
for
products,
it
might
not
make
sense.
Who
knows?
A
I
was.
I
was
actually
mentioning
that
this
is
what
happens
when
you
live
in
a
village
in
a
village
in
poland,
I
warned
you
at
the
beginning,
yeah
exactly
and
and
was
saying
that
that
scram
is
often
or
it's
often
seen
as
the
default
or
go-to
way
to
to
manage
product
development
in
companies.
A
But
in
this
case
we
we
had
something
clear.
Let's
say
which
is
we
didn't
want
to
build
only
a
product
or
tools
or
a
spec
right.
It
was
more
about
the
community
right,
so
so
something
that
I
that
before
before
I
I'm
having
too
many
thoughts
right
now.
In
my
head
and
before
I
I
go
too
far
with
these
thoughts
and
I
derail
right,
that's
something
that
I
mentioned
before,
and
it's
the
speed
right,
the
speed
of
contributions
and
the
speed
of
our
contributions
as
well.
A
So
that's
something
that
we
we
realize
after
some
time
like
in
the
beginning,
we
were
like
still
influenced
by
this
mood,
let's
say
or
way
of
working
which
is
like
deliver
the
liver,
deliver
the
liver
as
quick
as
possible,
because
the
best
we
are
the
best,
the
I
mean
the
best
the
product
is
the
more
people
we
want.
A
A
The
more
people
will
want
to
use
it
right,
but
it
has
a
problem
and-
and-
and
I
I'm
I'm
telling
you
lucas-
but
I'm
telling
actually
the
people
listen
to
us
and
the
problem
which
was
pointed
out
by
lucas
at
the
time,
was
that
if
we
rash
that
match
we're
leaving
people
out-
and
it's
like
people
are
not
working
full
time
in
this
api
like
we
are.
A
So
if
you
don't,
if
you
only
have
a
few
spare
hours
per
week
to
work
on
and
not
every
week
to
organizing
api,
you,
you
can't
be
contributing
super
fast
or
you
don't
want
to
be
developing
things
super
fast,
because
then
they
will
be
whenever
they
connect
again,
they
will
be
like
damn
it
like
what
happened
here
right,
they
get
lost
and
they
get
they.
Basically,
it
basically
sends
the
message
to
these
people
like
that.
B
B
We
didn't
know
how
it's
gonna
work,
but
now,
after
months
several
months
we
like
see
like
especially
this
year,
we're
getting
so
many
people
contributing
to
tools
and
and
like
I,
we
would
never
do
it
with
the
core
maintainers.
Only
with
I
mean
core
maintainers
people
that
work
full-time
yeah
on
the
project,
but
yeah
like
basically
by
slowing
down
enabling
others
to
to
also
come
to
the
project
and
contribute
that
was
super
important.
B
But
still
we
can
rush
like
if
they're
like
rush
and
depends
how
you
define
rush.
But
I
mean
still,
if
there's
some
super
important
change
that
has
to
be
done
in
some
library
like,
let's
say
parser,
we
have
this
javascript
parser,
where
we
want
to
refactor
everything
and
wait
for
very
long
and
in
some
particular
cases.
I
still
think
it's
okay.
B
If
we,
if
we
rush
in
the
way
that
we
just
don't
wait
too
long
but
just
exchange
pr
reviews
between
maintainers
and
we
basically
merge
faster
and
release
faster
because
at
the
end
it's
for
the
goods
of
the
community
to
do
it,
especially
in
case
of
big
refactoring
or
rewrite
of
the
api.
B
A
contributor
that
just
contributes
from
time
to
time
will
anyway
not
jump
in
and
not
help
much
so
yeah
again,
it's
not
like
a
white.
It's
not
just
be
always
slow,
but
but
mainly
like
in
majority
of
cases
like
just
don't
rush
like
it's.
It's
like
in
in
real
life
like
you
do
something
you
you
think
it's
important,
but
then
you
go
for
holidays
and
for
two
weeks,
and
you
do
it
two
weeks
later
and
all
suddenly,
you
notice
like,
if
I
would
do
it
two
weeks
earlier,
nothing
would
change.
B
So
it
could
wait
two
weeks
right.
So
sometimes
pr
can
wait
for
like
if
you
can
wait
for
20
days
like
it's
completely
fine,
if
you're
not
in
rush-
and
you
want
to
have
as
many
people
as
possible
sharing
opinion.
B
I
mean
there
was
this
case
with
react
component
right
when,
when
machia
joined
the
project-
and
he
started
the
yeah,
the
whole
preparation
of
the
component
to
have
it
ready
for
the
studio
and
yeah,
he
also
like
rushed.
It
was
his
main
focus.
B
So
basically
he
he
wanted
to
have
pr,
sometimes
like
merged
in
two
days.
So
quick
review
like
you.
Basically,
if
you
jump
into
the
project
once
a
week,
you
don't
have
time
to
actually
see
dpr
and
I
no
particularly
one
contributor
that
was
contributing
contributing
to
react
component
from
time
to
time
and-
and
he
even
wrote
to
me
like,
like
I
can't
catch
up
with
with
mache
like
speed.
B
Yeah
but
again
like
there
was
an
in
like
super
important
goal
like
and,
and
the
component
had
to
be
really
refactored
a
lot.
So.
A
B
Like
case
with
parser
like
if
you
really
have
a
lot
of
reworking-
and
you
need
to
have
in-depth
knowledge
of
the
of
the
component,
then
then
sometimes
it's
just
it's
just
a
work
for
the
for
the
maintainer
and
contributors
can
just
learn
from
it
like
go
into
pr
help
with
the
review.
If
they
have
time,
because,
especially
if
you're
in
rush,
then
it's
not
just
one
pr,
it's
several
pr's
yeah
so
like
you,
basically,
instead
of
being
an
active
contributor,
you're
just
learning
from
the
prs
to
contribute
later
so.
B
A
I
was
actually
thinking
I
was
asking
this
because
I
was
thinking
that
I
myself
like
sometimes
feel
like
we're
slow,
we're
too
slow
in
some,
but
on
purpose
I
know
it's
on
purpose,
but
we're
too
slow
in
some
areas
that
might
not
always,
which
will
probably
not
be
so
slow
like,
for
instance,
the
cli.
So
I
think
the
cli,
so
the
fact
that
it's
taking
more
time
to
migrate
everything
to
a
single
cli
where
you
can
rule
them
all
right.
A
It's
actually
making
us
work
more
as
a
community
right,
because
we,
the
more
time
we
have
to
maintain
multiple
clis,
the
the
worst
right.
The
same
happened
with
html
template
and
react
component.
We
had
the
two
and
they
were
almost
similar,
but
they
were
two
code
bases,
so
so
yeah.
So
here
is
it's
even
it's
even
worse,
because
there
are
multiple
clies
spread
across
many
tools.
A
Right
and-
and
so
I
was
like-
I
think-
maybe
the
cli,
like
we
shouldn't-
be
waiting
so
much
for
to
to
develop
it
further
right
like
we
should
probably
put
more
effort
into
releasing
version-
one,
let's
say
whatever
it
means
of
the
of
the
cli,
so
as
so
as
soon
as
possible,
users
can
have
a
single
entry
point
to
the
to
the
spec
and
to
the
tools
right
so
to
the
to
the
initiative
like
so
now
I
have
my
cli
here.
I
can
do
everything
from
here
and
then
from
there
on.
A
Okay,
things
might
have
to
wait.
Like
I
don't
know,
the
code
generator
is
not
good
enough
here
in
there
like,
for
instance,
it's
not
implementing
the
kafka
protocol,
for
instance,
is
not
supporting
the
kafka
protocol.
A
People
will
have
to
contribute
that
to
you
to
the
code
generator
to
this
specific
code,
generator
or
glee
doesn't
support
this
or
that
or
studio
doesn't
support
this
or
that
cool.
But
but
specifically,
the
cli
to
me
is
one
of
the
one
of
the
strategic
tools
for
us,
like
cli
and
and
in
studio,
actually,
probably
more
than
cli,
but
but
or
both
together.
Right,
like
the
use
of
both
cli
in
studio.
A
To
me
are
like
strategic
investments
for
for
the
for
the
initiative
in
order
to
to
make
life
a
life
of
our
community
easier,
and
I
feel
not
sure
if,
if
you
agree
with
me
here
like
that,
was
slow
there,
sometimes
in
studio
as
well
like
for
on
purpose
like
we,
we
delay
things
or
we
leave
issues
there
and
and
leave
the
issues
there
open
just
in
case.
Someone
want
to
want
to
take
it,
but
we
know
these
issues
are
important
right.
B
I
think
it's
like
it's
all
about
the
needs
right
so
in
case
of
cli,
the
the
current
generator
cli
it's
stable.
It
has
hasn't
changed
in
a
in
a
year.
Converter
cli,
it's
just
used
like
it's
invest.
We
invest
time
there
only
from
time
to
time
and
at
the
end
it's
we're
not
investing
really
in
the
cli
we're
just
investing
in
the
library.
B
So
that's
why
there's
no
rash
on
the
cl,
because
maybe
let's
say
differently
so
basically,
if
we
would
notice
that
there's
a
lot
of
contributions
to
these
clies
and
they're
changing
like
people
have
ideas,
people
want
to
invest,
then
it
would
tell
us
okay
like
instead
of
doing
double
work,
let's
finally
migrate.
B
Yes,
but
if
there's
no
pressure
like
we
don't
see
double
work,
I
think
it's
okay
to
wait
a
bit
like
because,
like
the
cli,
this
it
was
started.
I
think
last
year,
around
march
april,
probably
by
jorge
and
then.
B
And
I
remember
when
I
was
thinking
about
cli,
so
sometimes
when
you
think
about
some
tool
like
you
have
an
idea
for
the
app
for
a
tool
and
when
I
was
thinking
first,
my
my
first
time
about
cli
that
can
integrate
all
the
tools
I
was
thinking
like
that's
the
most
important
like
we
need
to
have
it
now
like.
Let's
do
it,
let's
do
it,
let's
do
it
after
a
few
months.
I
just
see
like
it's
nothing
but
will
happen
if
we're
going
to
have
it
in
in
in
few
months.
Oh.
B
And
and
the
side
effect
like
look
on
the
look
on
the
current
cli
like
if
we
would,
if
we
would
push
it
like
push
it
like,
we
pushed
it
with
with
react
component.
B
Then
of
course
we
would
have
all
the
all
the
commands
faster
like
six
months
ago.
Let's
say,
but
in
exchange
we
have
maybe
less
but
cli
it's
one
of
my
favorites
projects
because,
like
almost
every
comment,
has
a
different
contributor,
yeah,
it's
of
course
we
have
to
wait
for
for
some
new
comment
even
few
months,
because
it's
contributed
by
someone
that
hasn't
doesn't
have
time
to
work
full-time.
We
also
don't
review
daily
but
still
like.
I
know
we're
slow
there,
but
it's
like
for
me.
B
It's
one
of
the
role
models.
I
would
always
say
like
yeah,
if
you,
if
you
are
patient,
you
just
invested
in
the
in
the
like,
let's
say
framework,
so
you
you
prepared
it
for
contributions.
B
B
A
I
I
I
I
have
another
perspective
that
I
was
thinking
as
you
were
speaking
there.
Could
it
be
that
so
one
of
the
things
that
you
were
mentioning
is
like.
A
So
I
explain
myself,
for
instance,
so
if
I'm,
if
I'm
new
to
async
api-
and
I
know
about
the
code
generator,
for
instance-
and
I've
been
using
the
cli
of
the
code-
generator
that's
cool,
but
I
don't
get
to
use.
I
don't
get
to
know
any
other
tool,
just
generator.
That's
all
I
get
right
and
I'm
happy
I'm
I'm
happy
with
this,
but
I
don't
get
to
know
what
else
I
can
do
with
async
api
file
and
therefore,
without
thinking
so
much
about
it.
A
I
start
assuming
that
async
api
is
just
for
generating
code
or
for
generating
dogs,
and
that's
it.
That's
all.
Async
api
allows
you
to
do
right,
but
if
this
same
user
starts
from
the
cli
from
the
one
cli
right,
one
of
and
and
they
start
using
the
generate
command
to
generate
dogs
or
or
code
one
day
even
the
first
day,
they
can
just
probably
type
async
api
desktops
help
and
find.
A
There
are
lots
of
commands
and
lots
of
things
you
can
do
and
driven
by
curiosity,
you
probably
will
just
see
what
what
else
is
there
like
what
you
what
you
can
do
with
this,
and
and
because
you
see
that
you
can
not
just
generate
code,
but
you
can,
you
can
create
a
a.
I
don't
know
a
glee
project
right.
So
suddenly
you
find
you
find
glee
and
it's
like.
Oh
damn
it.
A
This
is
exactly
what
I
needed,
but
I
didn't
know
it
existed
so
so
the
cli
can
serve
as
a
discovery
tool
as
well
right.
So
so
what
I
mean
here
is
that
the
cli's
of
the
other
tools
are
stable
and
we
don't
get
too
many
pr's
because
they're
fine
as
they
are,
but
that
doesn't
mean
that
we
don't
get
a
lot
of
users
in
this
in
this
cli
and
so.
A
All
those
users
that
we're
getting
in
these
other
clies
are
not
being
introduced
to
the
to
the
wider
menu
of
tools
that
they
have
right
a
siloed
and
to
introduce
into
this
cli
so,
which
makes
me
think
at
the
same
time
it's
just
like
yeah.
If
we
invest
more
in
the
cli,
it
will
get
less
contributors
to
the
cli,
but
maybe
because
we're
driving
everyone
to
the
same
single
point
of
source
of
truth.
A
Let's
say
the
the
the
cli,
they
will
discover
more
tools
and
they
will
end
up
eventually
contributing
to
more
of
this
other
tools.
You
know
what
I
mean
so
so
I
was
I'm
thinking
that,
maybe
it's
not
just
so
probably
I
could
be
that
we're
just
thinking
that.
A
We're
just
counting
the
cli
contribution
and
and
we're
missing
what
could
be
contributed
to
other
tools.
Just
because
people
landed
on
the
cli
on
a
on
a
strong
cli
and
they
knew
more
about
the
rest
of
the
tools.
A
Could
it
be
that
that
we
are
just
stopping
at
people
contributing
to
the
cli
and
counting
them
as
the
community
right
like?
Oh,
we
like
measuring
we're
getting
a
lot
of
different
people
in
the
cli.
That's
cool
right,
but
could
it
be
that
we're
missing
a
more
powerful
community
base
if
we
had
a
a
strong
cli
and
therefore,
through
the
cli,
these
people
will
land
into
generators
glee
different
code
generators?
A
I
don't
know
other
other
tools
right
and
therefore
contributing
to
those.
You
know
what
I
mean
yeah.
B
Yeah
so
like
so
basically
it
could
be.
B
So
so
what
I'm?
What
I
meant
by
cli
and
what
I
like
in
the
cli-
I
I
I
still
like
it,
but
the
thing
is
like,
but
you
still
have
maintainers
like
right,
so
I
don't
mean
that,
like
maintainers
should
just
basically
jump
into
pr
reviewers
only
and
don't
do
implementation,
but
that's
what
you
have
as
a
milestones,
whatever
planning
goals.
One
zero
like
soviet,
creates
this
issue
like
one
zero
planning
yeah.
So
that's
so
that's
this
speed
topic.
So
in
parser
speed
topic
is
typescript
and
and
and.
B
Parser
api
in
react,
speed
topic
was
was
a
studio
and
it
was
completely
fine
to
speed
up
and
in
an
ncli.
We
also
have
to
define
this
speed
topic
so
in
case
of
this
issue
that
we
discussed
one
zero
like
so
you
basically
should
we
like
must
have
for
one.
Zero
is
generator
cli,
because
then
it's
gonna
automatically
enable
people
that
go
into
generator
repo
and
they
find
an
instruction
asking
api
cli.
B
Then
they
start
using
asking
api
cli
and
do
what
you
just
said
like
the
discover
the
tool
so
yeah
with
these
topics,
we
should
well
it's
it's
completely
fine
to
rush
like
define
the
goals
if
anyone
from
the
like
and
define
them
openly
like
if
anyone
from
the
community
wants
to
jump
in,
do
it.
But
but
we
clearly
say
like
that's
the
like:
we
want
to
have
essay
maintainers.
We
want
to
have
one
zero.
B
We
should
rush
we're
gonna
review,
quicker,
etc.
But
but
the
other
comments
I
mean
like
some
copied,
for
example,.
B
It
would
be
nice
to
have
it
enabled
quickly,
but
yeah
it's
it's
again.
It's
all
about
like
what
community
wants
like.
If
community
thinks
it's,
it
would
be
super
nice
to
have
more
comments
faster.
A
So
that
takes
me
to
another
thought
so
something
that
I
that
I've
seen.
I
don't
know
if
it's
been
this
morning
or
yesterday
afternoon,
taylor
otwell,
the
maintainer,
the
creator
of
the
latable
framework,
php
frame,
a
very
famous
php
framework
posted
the
tweet,
which
made
me
think
and
and
love
at
the
same
time,
which
was
something
like
like
imagine
giving
access
to
your
to-do
list
to
the
entire
world
and
and
then
you
feeling
bad
because
you're
not
able
to
finish
everything
that
is
in
the
to-do
list.
A
That's
github
issues
and,
and
he
was
and
then
he
continued
after
that
saying
like
that.
If
he
were
to
start,
if,
if
he
were
starting
a
new
project
or
he
was
if
he
were
starting
again,
he
will
just
disable
github
issues
completely
and
accept
only
pr's
and
and
and
he's
just.
He
was
just
saying
this,
like
you
have
other
channels
for
for
issues.
You
have
other
channels.
A
You
have
things
like,
like
slack,
like
stack
overflow
people
asking
questions
on
stack
overflow
right,
but
on
github
you
only
accept
prs
because
that
filters
out
every
non-important
issue,
because
if
the
person
is
not
willing
to
contribute
the
fix
or
the
feature,
then
it's
not
really
important.
A
And
and
that
fear
that,
and
that
fear
that
you
will
be
losing
important
feedback,
it's
like
not
really.
You
eventually
find
it
out
like
on
slack
on
stack,
overflow
or
because
someone
if
it's
important,
someone
will
create
a
pr
eventually,
and
that
made
me
think
like
maybe
not
for
async
api.
I
don't
think
it's
it's
not.
Maybe
I
mean
not
for
async
api,
but
that
made
me
think
right
like
what
do
you
think
about
it?
It's
just
before
I
I
share.
B
Yeah,
it
was
a
tweet
first
of
all,
yeah
yeah
yeah.
I
know
I
mean
the
concept,
not
the
tweet
itself
yeah
and
the
con
like
the
concept.
B
I
I
don't
have
any
I'm
not
a
kind
of
good
person
for
twitter
because
for
twitter
I
would
just
say
no,
it's
a
it's
bad
whatever
you
do
it
wrong
and
but
yeah
again
it's
it
really
depends.
So
I
know
that
this
is
the
hugely
popular
project
for
php,
but
I
don't
know
like.
Maybe
you
can
tell
me,
maybe
you
know
more.
I
refuse
to
learn
anything
about
php.
B
But
like
there
are
different
open
source
projects
that
are
called
open
source
projects
like
like,
for
example,
menio.
You
have
this
project
like
like
mino,
where
they
in
open
build.
B
This
amazing
s3
alternative
that
you
can
host
on
premise,
but
it's
there's
a
basically
a
company
behind
it
right
like
with
or
nuts,
for
example,
there's
a
company
behind
it
with
their
product
roadmap
and
it's
different
way
of
building
community
and-
and
then
I
guess,
like
maybe
in
case
of
la
la
la
vel
laravel,
maybe
in
their
case
it's
also
the
same
like
I'm,
not
sure.
If
they're
are
they
part
of
some
foundation
or
something
like?
Are
they
really
community
driven
because,
like
in
case.
A
B
B
I
would
never
be
happy
to
work
in
such
project,
but
but
at
the
end
like,
if
you
have
such
strat
strategy,
like
that
you,
you
basically
do
only
stuff
that
you
think
are
important
for
the
project
and
if
somebody
wants
to
fix
something,
yeah
just
create
a
pr.
We
might
accept
it
or
not,
but
again,
but
again
like
starting
with
pr
where's
the
place
for
discussion,
then
like
yeah,
but
yeah,
maybe
slack,
maybe
somewhere
else
yeah,
so
yeah,
it's.
It
really
depends
like
in
case
of
asking
api.
B
I
can't
imagine
like
it's,
there's
no
agenda
on
your
side
on
my
side
like
we,
we
know
what
we
like
to
improve
in
asking
api,
but
it's
like.
If,
if
we're
blocked
somewhere
in
in
some
repo,
where
there
are
different
maintainers
or
something
like,
we
can't
push,
we
won't
push
so
no
and
also
we're,
in
our
case,
we're
even
more
complicated
because
we
accept
donations
like
we
have
maintainers
that
are
not
related
with
me
with
you
and
like.
We
can't
even
tell
them
like
now.
You
have
to
disable
issues
and
integrate
gyra
or
whatever.
A
B
So
no
so
basically
I
can't
fully
say:
don't
do
such
approach,
but
yeah.
Definitely
don't
do
it
if
you,
if
you
have
a
community
driven
product
project,
that's
exactly.
A
That's
the
point
so
there
you
mentioned
like
there
are
many
open
source
projects
which
called
themselves
open
source
and
that's
fine,
because
in
the
end
the
source
is
open
but
and
the
license
is
probably
something
compatible,
but
there's
something
often
forgotten
here,
which
is
the
open
governance
model
right.
So
so
it's
something
just
because
something
is
open.
Source
doesn't
mean
it
has
to
be
open
governance
and-
and
I
guess
it
has
to
do
with
this.
A
I
have
no
idea
to
be
honest,
probably
it
is,
and
and
and
well
in
any
case
he
was
saying,
like
he's
not
doing
it
for
latville
by
the
way,
like
he's
paying
some
people
to
triage
issues,
so
so
they
don't
accumulate
there
and
so
they're
they're
listened
and
they're.
Actually,
I
think
the
latable
repo
only
has
three
issues
open,
something
like
that.
It's
just
insane,
if
you
think
about
it,
just
three
uses
something
like
that.
I
read
this
on
on
twitter.
A
I
didn't
check,
but
it's
because
yeah,
like
you,
have
people
just
trading
issues
and
and
and
not
just
changing.
You
also
have
people
implementing
them
right,
so
yeah,
and
maybe
I
don't
know-
maybe
some
approach
is
that's
cool,
it's
great
feedback,
but
if
you're
not
going
to
implement
it
or
if,
after
some
time,
nobody
wants
to
implement
it.
This
is
closed
right
because
we
understand
that
it's
a
cool
idea,
but
it's
just
that
it's
a
cool
idea
right,
it's
not
important,
so
so
yeah,
I
don't
know
like.
A
A
Yeah
true,
it
was
the
native
yeah,
true
yeah.
So
then
you
have
other
projects
like
I
don't
know
like
what
was
this
search
engine
or
this
thing
use
plastic.
A
Yeah,
so
elasticsearch
searches
mike
well,
they
recently
changed
the
license.
So
it's
not
really
open
source
anymore,
but
not
not
strictly
open
source,
but
the
source
the
source
is
public.
It's
there
it's
open,
but
as
you
cannot
decide
on
the
future
or
you
cannot
influence
the
future
of
the
of
the
of
the
tool
right,
it's
the
company
behind
it
who
decides
what's
next
and
you're,
just
a
mayor,
so
gita
business
in
this
case
is
just
for
reporting
backs
or
asking
questions.
Maybe,
and
that's
it's
a
support
system,
india,
just
that
so
so,
yeah.
B
B
So
yeah
I
mean
but
yeah
like
jonas.
I
guess
that
if
there's
a
company
behind,
they
probably
use
some
different
tool
to
manage
work
that
you
can't
see.
Really
that's
the
thing
like
gyra
or
whatever
boards
and
but
probably
closed.
So
nobody
can
see
the
progress,
especially
if
you
again
like,
especially
if
you
want
to
do
open
source,
but
with
scrum
and
etc,
yeah
so
yeah,
but
yeah.
That's
how
that's
how
it
looks.
It
really
all
depends.
There's
this
nest.
B
Js-
and
I
was
recently
discussing
with
with
mache
like
because
we
were
like
checking
out
on
sjs,
because
there
was
a
community
member
writing
a
plugin
for
asking
api
from
sjs
the
one
with
s.
You
mean
nest
nest.
Yes,
yes,
n-e-s-t
yeah
and
they
have
pretty
efficient
triage
of
the
issues,
but
it's
yeah.
I
guess
that
they
have
company
to
run
the
projects
to
get
money
from
the
project,
so
they
are
pretty
like
direct
in
the
triage
like
we're
not
going
to
implement
it
close
or
no.
B
It's
not
on
the
roadmap
like
close
et
cetera,
et
cetera
and
again
like
if
you
run
a
business
on
it
you
you
want
to
close
those
quickly
because
that's
a
noise,
you
don't
want
to
have
this
noise,
but
if
you
really
want
to
have
an
open
project-
and
you
don't
do
it
like,
keep
it
longer
open,
maybe
somebody
else
will
jump
in
or
at
least
make
and
make
a
suggestion
like
or
have
a
open
discussion
have
a
meeting
where
people
can
jump
in
and
explain
why
they
want
to
have
it
and
not
just
close
discussion
by
saying
no,
instead
of
maybe
having
a
longer
discussion
but
again,
like
it's
very
popular.
B
So
it's
this
does
not
affect
popularity.
It
just
affects
the
the
community
aspect
but
yeah
again
like
to
what
I've
learned
over
the
past
few
years.
Looking
on
different
projects
like
you,
don't
have
to
be
community
driven
and
open
to
the
community
to
have
a
successful,
open
source
project.
B
But
it
was
also
the
again
another
projection
from
the
past,
like
I
sometimes
when
I'm
thinking
about
the
all
this
past
two
years
at
the
project,
I
sometimes
have
a
feeling
that
whenever
I'm
trying
to
do
some
change,
it's
not
because
only
for
asking
api
community,
but
because
I'm
thinking
like
no,
we
should
we
have
to
do
it
better.
Here,
like
we
have
to
do
better
than
than
other
open
source
projects
like
I'm.
B
Sometimes
thinking
that
many
things
that
we
do
at
using
api
is
because
we
want
to
show
that
it's
actually
doable
and
others
don't
do
it,
but
we,
but
we
should
be
the
first
ones
that
do
it
so,
and
maybe
these
things
take
effect
like
later,
but
looking
at
the
list
of
the
technical
steering
committee
members
that
is
growing
regularly,
I
think
it's
we're
making
pretty
good
decisions
here.
A
And
that's
another
thing:
that's
another
aspect
of
this
like
in
in
other
projects,
so,
for
instance,
I
I
was
before
asking
kpi.
I
was
mainly
involved.
It's
not
the
word
but
yeah
like
in
sync,
let's
say
with
open
api
right
and
in
open
api.
A
The
approach
was
exactly
the
opposite.
I
would
say
it's
almost
the
opposite
as
we're
doing
here,
but
but
with
regards
to
the
tse,
is
it
becomes?
It
is
like
a
select
group
of
people
who
are
like
how
can
I
say,
like
it's
difficult
to
become
a
tse
member
right?
It's
it
is
highly
difficult.
You
probably
have
to
be
contributing
there
for
years
to
to
get
there
to
become
a
a
technical
steering
committee
member
but-
and
that's
I
mean
that's
another
approach,
but
what
we're
doing
here
is
completely
the
opposite.
A
It's
like
no,
you
contribute
you're
a
code
owner
because
you've
been
you
donated
the
tool,
you're
being
maintaining
a
tool
for
some
time
already.
That's
it
you're
you're
part
of
the
tse.
Now
right,
like
you,
don't
have
to
you,
don't
have
to
be
super.
Like
I
don't
know
it's
not
any
lightest
club.
That's
what
I
mean
right:
it
doesn't
become
the
lightest
club,
it's
the
opposite.
It's
like
it's
a
welcoming
club.
A
A
Maintain
basically
show
that
you
want
you,
you
wonder
you
can
maintain
your
tool
and
that's
it.
You
get
automatically
invited
right,
so
so
the
the
the
aspect
of
this
is
completely
that
I
have
to
have
to
admit
that
that
this
was
new.
To
me.
To
be
honest,
I
don't
you
follow
more
open
source
project
out
there
than
that
I
do,
but
I
have
the
feeling
that
we're
the
only
ones
doing
this
like
like
making
it
so
easy
to
become
a
tsa
member,
and
I
actually
like
it.
B
Yeah,
I
remember
when
we
were
thinking
about
this
model
and
proposing
it
to
the
community
before
joining
linux
foundation
and
yeah
we're
the
first
ones
doing
it
that
open,
at
least
to
that
we
know
at
least
that
we
know,
and
again
it's
one
of
the
things
that
I
wanted
to
fix,
because
I
remember
like
watching
other
projects
like
no
it's.
It
looks
like
some
special
club,
yeah
and
and
and
one
one
issue
with
this
kind
of
special
club.
It's
not
just
it's
not
just
about
special
club.
B
It's
again
about
not
regular
contributors.
A
B
Because
other
projects
really
invite
only
few
people,
they
have
meetings
where
they
make
decisions
and
they.
So
basically
the
group
cannot
be
large
plus
it
really.
You
really
have
to
be
involved
in
the
project,
a
lot
to
be
there
and
and
it's
leaving
away
people
that
just
want
to
contribute
from
time
to
time.
A
Yeah
or
there
are
or
people
who
are
in
the
in
other
time,
zones
or
yeah
are
not
able
to
to
meet
in
a
in
a
call
with
you
every
week,
right
so
yeah
or
just
not
just
time
zones.
They
have
other
live
stuff
happening
at
this
time
and
they
cannot
join
the
meetings
for
whatever
reason
like
taking
kids
to
school
or
whatever
or
going
out
for
whatever
reason.
So.
B
And
that
was
one
of
the
motivations
for
the
approach
that
we
don't
make.
Decisions
on
the
course
like
give
people
time
to
watch
the
recording
and
share
an
opinion
and
then
have
everything
in
the
issue
at
the
beginning.
I
was
afraid
that
it's
gonna
affect
the
audience
of
the
meetings
like
less
people
will
come,
but
that
didn't.
A
A
B
I
signed
up
for
this,
something
that
like
will
evolve
regularly,
yeah
but
yeah
and
regarding
the
guardian
ideas
from
the
yeah
community,
gardener
gardener.
So
interesting
fact,
so
I
live
in
the
village.
So
obviously
one
of
my
neighbors
he
has
a
tractor
he's
a
I
don't
know
how
you
call
it
so
by
by
night
he's
a
miner.
He
works
in
a
mine
in
a
coal
mine
but
by
day
he's
a
I'm,
not
sure.
What's
the
english
word
like
the
guy,
that
has
a
field,
has
a
tractor
and
does
stuff
in
the
field.
B
I
wish
somebody
can
tell
me
well
this
single
word
in
english,
but
I
guess
you
get
you
get
it
so.
Basically
he
has
a
tractor,
so
it's
somehow
related
to
gardening,
and
I
love
gardening
and
the
fun
fact
about
using
api
and
gardening.
So
a
farmer
yeah,
exactly
farmer
he's
so
he's
kind
of
farmer
and
he
is,
he
loves
tractors
like
he's
his
tractor
is
like
40,
50
years
old,
he's
repairing
it
all
the
time
and
he
is
in
some
foundation,
local
foundation
for
tractor
owners.
B
They're
doing
some
events
where
there's
some
community
events.
They
come
with.
The
tractors
they
give
people
a
ride,
so
they
promote
that.
It's
not
something
to
be
ashamed
of,
like
it's
actually
cool.
I
remember
I
had
like
super
huge
sticker
on
my
laptop
with
their
with
the
name
of
their
foundation
and,
again,
like
finish
my
long
sentence,
so
I
I
sent
them
some
money
to
support
the
foundation
and
in
exchange
they
they
have.
B
A
B
They
have
a
flag
and
they
also
have
a
tent
like
not
like
a
tent
that
you
sleep
in,
but
it's
a
tent
with
just
a
roof
without
without
walls,
and
it
also
has
like
async
api
logo.
B
A
B
A
A
A
I
take
your
comment
before
so
we
should
be
doing
this
more
often,
probably
once
a
month
or
something
like
that
or
less
or
less
just
while
you're
on
holidays
I'll
ping,
you
every
time
you're
on
holidays,
just
yeah
just
so
so
I
can
disturb
you
for
no
reason
so
yeah
thanks
a
lot.
As
always
people
are
now
commenting.
A
Like
you
know,
sir
here
is.
We
should
build
up
an
example
of
facing
api
based
on
the
foreign.
B
But
actually
there's
there's
really
do
we
want
to
keep
people
longer,
because
there's
actually
really
super
interesting
topic
in
in
regards
to
even
driven
and
farms,
because
it's
it's
getting
very
popular
recently
when
you
have
like
huge
farms
and
you
want
to
harvest
them
when
it's
needed,
etc,
etc.
Then
you
actually
have
your
equipment
out
automated
like
in
in
advanced
farms.
You
don't
have
even
drivers,
you
just
have
machines
there
and
they
are
connected
with
with
some
kind
of
central
application
that
is
connected
with
the
with
satellites.
A
B
A
B
A
B
A
B
The
other
ones
at
least
are
cheap
right.
It's
cheap
and
it's
I
mean
actually
actually
me
as
a
community
manager.
I
should
think
like.
I
should
make
a
photo
tweet
about
it.
It
would
have
a
I
mean.
I
bet
that
tweet
like
twitter
ad,
that
pay
is
super
expensive,
would
not
generate
a
traffic,
that's
the
tweet
with
tractor
and
and
the
and
the
flag
would
generate.
B
B
Yeah
and
then
I
guess,
I
can't
use
asking
api
open
collective
money.