►
From YouTube: Community meeting (February 21, 2023)
Description
A
B
You
community
manager,
at
a
single
API
initiative,
so
I'm
very
excited
to
fill
in
the
big
shoes
of
Lucas
but
anyways.
If
anyone
has
any
suggestions,
comments,
feedback
on
how
we
can
improve
the
community,
you
can
reach
out
to
me
on
slack
via
DM
I'm,
also
available
on
social
media.
You
can
reach
out
and
I'll
be
available.
B
A
A
So
you
don't
have
to
be
afraid
of
me
anymore.
If
you
were,
of
course,
so
yeah
I'm,
I'm,
super
happy,
I,
think
I
shared
it
to
you
privately
already
and
and
and
slack
but
yeah
I'm
super
happy
that
you're
here
and
you're
gonna
next
12
months
cover
asking
API
Community
Management,
which
is
awesome,
because
even
though
it
may
look
like
it's
a
big
shoes
but
I
never
had
a
chance
to
really
do
it.
A
Just
full-time
only
Community
Management,
so
I'm
happy
that
we
finally
have
someone
dedicated
and
we
can
have
someone
through
the
open,
Collective
money,
which
is
great
now
looking
on
the
agenda
items,
there's
there
was
like
five
minutes
ago.
There
was
nothing
on
the
agenda,
so
I
have
just
two
items
so
akshat
before
we
go
into
your
topics.
A
Awesome
so
so
there
are
two
topics:
I
just
wanted
to
share,
so
the
status
of
g-soc
and
awesome
API
mentorship
so
like
he
just
asked
me
to
share
feedback
as
to
share
status,
but
because
he
felt
bad,
he
wasn't.
He
wasn't
able
to
share
exactly
what
I
have
to
share.
So
just
looking
at
my
notes,
I
know
that
he
applied
on
this
for
gsoc
I,
think
API
for
G-Shock,
but
I.
A
A
If
we
get
rejected,
then
I
think
it's
irrelevant
anymore.
But
if
we
get
accepted,
that's
super
cool
but
yeah
anyway.
That's
the
news.
So
today
we
should.
We
should
like
Ace,
should
get
an
email
on
the
status
and
in
case
of
asking
the
API
mentorship
the
last
time.
I
checked
but
again
not
sure
how
he,
if
he
changed
his
mind
or
did
something
basing
on
the
slack
discussion
in
the
mentorship
channel.
A
The
plan
that
he
had
I
know
is
that
was
okay,
we're
waiting
for
G-Shock
and
once
it's
we
know
yes
or
not.
We
will
proceed
with
async,
API,
mentorship
and
I.
Don't
think
it
was
ever
a
a
condition
that
if
we
get
accepted
for
G-Shock,
we
will
not
do
as
an
API
mentorship
I
think
these
two
do
not
exclude
each
other.
It's
more
about
that.
We
submitted
few
proposals
for
gsoc
so
before
we
actually
kick
off
mentorship.
We
need
to
know
if
the
same
proposals
for
gsoc
will
be
done
under
mentorship.
A
Cool
before
we
or
actually
not
before,
okay,
so
actually
your
items.
So
there's
a
you
left
a
comment:
there
are
a
list
of
issues
I
want
to
add
to
this
meeting
regarding
the
website
to
have
a
clear
discussion
on
it
and
make
it
out
to
the
community.
So
would
you
like
me,
would
you
like
to
give
me
you?
Would
you
like
me
to
give
you
and
I
share.
C
Thank
you
when
he
was
like
I,
have
a
question
regarding
that
previous,
what
you
have
said
regarding
the
G,
so
that
do
didn't.
We
get
the
email
or
any
announcement
or
information
regarding
from
the
from
the
gsoc.
Regarding
that
we
have
got
selected
or
Not
Like
a
Prayer
information
to
the
organizations
like
previously
last
year.
I
know
that,
before
the
announcement
of
the
organizations
to
the
public,
async
API
got
the
mail
two
to
three
days
before
that
it
got
rejected.
A
A
B
A
A
C
A
D
C
D
A
D
A
C
Of
changed
the
like,
if
you
can
see
there,
is
actually
a
sample
PR,
which
is
being
initialized
by
the
issue
owner
only
that
he
made
a
slight
changes
to
make
this
change
happen,
but
it
is
not
perfectly
okay,
like
I'm,
not
I'm,
going
to
review
it
soon.
But
question
is
that
do
we
need
that
change
or
not.
A
He
also
underlines
it
I
mean
so,
like
my
opinion
would
be
like.
If
we
really
want
it
and
I,
don't
see
a
problem
having
it,
but
I
would
not
underline.
I
would
just
basically
persist
the
behavior
that
we
have
when
we
hover
over
that's
what
I
think
is
the
best
like.
So
when
you
hover
over
on
dogs
and
you
click
and
the
docs
load,
the
the
the
Hoover
color
should
stay.
You
know,
you
know
what
I
mean.
C
D
C
C
A
C
A
C
C
A
D
C
C
C
A
time
that
when
we
are
loading
the
GSL
into
the
tools
dashboard,
it
takes
a
particular
time
of
to
load
all
the
data
into
a
respective
components.
So
we
could
have
the
preloader
assigned
to
it.
But
the
only
problem
is
is
that
the
exact
component
that
has
to
be
used
is
not
available.
With
the
present
react
vessel,
we
are
using.
D
A
Well,
in
such
cases,
I
always
like
try
to
balance
what's
their
like.
What
is
the
change
if
the
change
is
worth
it
like?
So
it's
if
it's
just
for
the
preloader
and
we
have
to
upgrade
and
upgrades,
always
mean
that
we
will
probably
have
some
issues
and
it
will
take
time
and
especially
if
the
features
are
better,
then
I
would
say:
let's
let's
wait
until
it's
really
production
check,
then
we
can
use
it.
C
C
Yeah,
it
means
like
many
of
them
actually
complain
that
when
they
do
not
have
the
proper
Internet
working
on
it
and
if
we
go
to
the
tools
dashboard
for
around
one
second
or
one
and
a
half
second,
the
screen
goes
blank.
Full
blank
means
that
only
the
that
search
bar
and
the
navbar
comes
in
between
and
no
tools
are
being
showed
up
at
the
initial.
D
C
A
A
A
C
A
I
mean
we
definitely
should
have
like
that
should
be
visible
out
of
the
box,
and
pre-loading
should
be
below
right,
okay,
and
so
that
would
be
my
feedback
if
I
would
go
deeper
in
the
pull
request,
but
again
like
if
like,
if
it's
really
visible
on
in
different
networks.
This
this
delay
and
preloader
makes
really
a
lot
of
sense.
A
C
That's
it
yeah.
It's
like
the
perfect
solution.
I
think
I
actually
mentioned
it
that
if
the
next
JS
releases
and
written
next
six
months
or
in
a
year
that
is
in
the
next
next
to
13th
person,
it
will
be
a
great
one
like
they
already
making.
It
have
already
out
that
in
the
docs,
but
yeah
I
still
don't
prefer
that
we
should
upgrade
it
to
the
next
13.
C
D
D
C
Okay,
so
this
was
actually
I
pointed
out
this
one
to
the
as2
that,
as
we
discussed
before-
and
you
also
pointed
out
before
that-
we
can't
manage
feature
Branch
for
long
face
and
it
becomes
a
very
difficult
to
manage
and
merge
the
changes
from
the
mean,
because
if
it
is
a
very
big
pull
request
with
lots
of
file
changed,
we
are
sure
to
get
so
many
merge
conflicts
in
it.
So
it
was
a
time
that,
should
we
now
merge
or
should
we
now
have
Community
section
on
the
website
running.
B
C
A
D
A
C
Yeah
I
think
I.
Wasn't
you
know
in
those
three
to
the
community,
Branch
yeah?
That
was
most
even.
There
was
one
more
very
point
where
he
pointed
out
the
issues
there
didn't
relate
to
the
environments
or
the
deployment
regarding
issues
and
he
actually
recovered
all
resolved
all
of
them,
so
it
was
like
majority
of
the
UI
part
is
done,
is
done
but
yeah
still,
as
per
the
issue
that
he
made.
Regarding
that
epic
roadmap
for
the
community
section,
the
dogs
and
certain
reference
contributor
docs
are
still
missing
to
be
added
in
the
section.
A
So
yeah
I
mean,
like
my
suggestion,
I
mean
so
I'm
like,
as
you
said,
like
you
know,
my
opinion
like
long
living
branches
are
a
pain
and
that's
why
this
is
a
pain
because
of
the
match
conflicts.
Basically,
what
you
said
so
I
would
say.
Yes,
our
goal
should
be
to
merge
it
as
soon
as
possible,
but
so
we
just
basically
need
to
agree
like
because
who
was
involved
in
the
review.
Mainly
it
was
you
me
and
Alejandra,
so
we
just
need
to
check
with
with
Ace
when
he's
back.
A
This
basically
has
to
go
out
of
draft
into
the
like
a
like
I
said:
pull
request
that
is
really
ready
for
review
and
we
need
to
basically
click
through
it
and
see
what
what
happens,
because
I
think
that,
like,
for
example,
one
thing
that
is
missing
I
already
see
is
the
that
when
you
go
to
Docs
it
nicely,
like
you,
click
docs,
and
it
takes
you
to
docs
when
I
click
on
community.
It
does
not
take
me
to
the
community,
but
instead
I
see
overview.
A
So
we're
already
inconsistent
overview.
Should
not
be
here
because
we
don't
have
any
overview
docs
here
and
so
Community
should
be
like
the
same.
I
click
on
community
I
and
I
and
I
see
this
without
a
need
to
click
on
the
overview.
So
that's,
for
example,
one
thing
so
we
just
need
to
click
through
like
click
through
and
see
if
things
are
still
working.
C
Yeah,
it's
like
I
also
saw
that
Community
has
two
pages.
One
is
dashboard.
One
is
overview.
It's
like
somewhat
similar
in
the
terms
of
like
they
do
have
different
things.
A
dashboard
consists
of
all
the
issues
and
the
hot
topics
we
do
have,
but
if
we
look
into
it
we
should
have
something
naming
because
overview
and
dashboard
looks
like
it's.
Both
are
the
home
pieces
of
community.
C
D
A
So
basically
this
should
be
replaced
with
or
still
be
called
meetings,
but
take
user
to
to
this
view.
So
yeah
we
need
to
click
through
see.
The
inconsistencies
make
sure
that
I's
address
them
as
the
most
important
ones
to
have
to
fix
this
basic
stuff
and
merge,
because
the
less
the
rest
we
can
improve
like
in
case
of
tooling
you
you
see
on
your
own,
like
after
releasing
the
tools
view,
there
were
already
a
number
of
different
pull
requests
to
improve
bits
and
pieces
right
to
to
make
things
work
better.
A
D
A
A
I
I
think
we
like
I'm,
not
gonna,
point
you
to
any
specific
issues
from
the
past,
but
I
I
know
that
in
the
past
we,
since
the
introduction
of
light
and
dark
mode
in
GitHub,
we
already
were
having
more
often
discussions
about
like
yeah.
It
would
be
nice
to
have
website
as
as
dark
in
dark
mode
as
well.
So
we
did
like
I
would
like,
and
you
can
already
see.
Fran
commented
I
can
leave
my
comment.
A
C
Css,
like
we
also
also
to
the
Tailwind
version
4.,
so
it
actually
allows
us
for
to
make
our
website
both
a
light
and
dark
mode
simultaneously
by
changing
the
certain
attributes
so
like,
if
you
add
certain
attribute
with
a
dark
and
colon
just
behind
it.
It
is
automatically
suggested
at
this
particular
property
of
properties
for
the
dark
mode,
so
it
automatically
assigns
so
like
we
do
need
a
certain
color
scheme.
Yes,
we
do
need
certain
designers
that
requires
that
this
particular
color
scheme
should
be
changed
into
this
particular
color
in
a
dark
mode.
C
So
if
this
discussion
comes
into
the
end,
like
comes
to
an
final
conclusion,
with
a
set
of
colors
being
interchangeable
in
the
light
in
the
dark
mode,
we
can
essentially
add
to
the
theme
that
is
to
the
Tailwind
config
file,
and
it
can
be
added
anywhere
inside
the
all
the
properties
to
it,
but
yeah.
It
will
be
a
big
change
for
sure,
because
we
do
have
too
many
components
and
too
many
Pages
inside
it.
C
A
Then
then,
my
suggestion
is
because
it's
a
nice
to
have
future
nothing.
We
have
to
rush
with
so,
as
you
said
like,
let's
do
it
first
on
the
dogs,
add
a
toggle
where
you
can
switch
on
the
dark
mode
and
then
we
can
also
add
a
specific
Google
tag
to
track.
If
people
actually
enable
dark
mode
to
see
if
people
click
it
and
then
like
seeing
the
feedback
on
on
the
color
scheme
that
we
used,
we
can
roll
it
out
to
to
other
views
one
by
one.
A
Because,
like,
as
you
said
like
the
most
critical
is
to
choose
the
scheme
like,
let's
see
in
action,
how
it
really
works
and
and
also
like
making
sure
it's,
it's
persistent
right
in
the
in
the
local
storage.
So
whoever
choose
dark
mode,
it's
not
loading
light
mode.
Every
time
they
reload,
of
course,
right.
D
C
There
you
go
so
we
like
yeah,
so
this
was
the
whole
of
it,
but
yeah
there's
one
more
I
want
to
add
that,
regarding,
as
we
discussed
before
too,
that
we
have
to
remove
the
previous
two
speech,
I
still
see
that
two
to
three
PRS,
where
the
contributor
want
to
add
new
to
the
dashboard
and
the
pr
consists
of
adding
the
tools
both
into
that
new
tools,
dashboard
and
also
on
the
previous
two
space
that
was
under
the
slash
talks.
So
is
this
the
time
that
should
we
remove
that
page.
A
A
A
D
A
D
A
C
So
I
think
you
you
already
are
you
asked
me
in
the
month
of
December
or
in
the
first
week
of
January,
that
we
should
have
a
PR
or
all
the
tools
should
be
listed
from
that
slash,
talk,
slash
tools
to
the
new
tools
dashboard
when
I
made
a
PR
recording
so
like.
If
we
remove
that
section
completely
in
a
single
PR
that
should
be
okay.
For
that.
A
A
Exactly
so
there's
we,
like
some
note,
has
to
be
left
here
and
so
so
just
make
sure
to
to
clarify
that
and
and
take
it
forward,
and
if
it
comes
to
the
announcement
of
the
tooling.
It's
almost
done
so
you
you
did
a
blog
post,
yes,
but
I
I
did
not
do
I
didn't
do
the
you
probably
noticed
that
whenever
we
have
articles
we
use,
we
ask
in
promotion
and
marketing
people
to
share
the
blog
post.
A
I
also
make
posts
on
Twitter
and
I
LinkedIn
to
like
really
announce
a
big
change,
and
that
is
something
that
I
plan
for
this
week
later
this
week.
So
so
we
can
assume
that
the
announcement
of
the
new
tools
will
happen
this
week,
so
we
can
already
like,
if
you
have
time
to
complete
the
pr
you
can
make
it
ready
for
merge
and
then.
C
So
yeah
yeah-
it
will
be
done
most
probably
by
the
next
two
days
like
when
I
get
back
to
my
home
from
The
Institute
yeah
I
will
do
it.
So.
Regarding
this,
my
the
migration
that
you
asked
regarding
this
tools
this
to
a
nude
one.
This
is
the
pr
that
I
was
talking
about
it.
It's
in
the
chat,
waiting,
chat.
D
D
A
C
C
A
D
A
B
Yes,
so,
like
oh
I
was
right,
opened
an
issue
on
on
open
Collective,
like
in
terms
of
like
payments,
how
contributors
might
struggle
like
with
payments
like,
for
example,
like
for
us
to
get
like
open
quality
funds
right?
You
need
to
use
fiscal
hosts
like
wise,
Pioneer
and
what's
the
third
one
Swift?
Is
it
Swift
or
is
it.
B
Swift
system
right,
so
oh
no,
Stripe
Right
like
for
instance,
try
for
us
doesn't
work
like
in
southern
Africa,
then
wise
doesn't
work
in
Nigeria,
so
I'm
not
sure
about
payoneer.
How
much
does
it
restrict?
So
it
was
like
coming
up
with
the
solution
where
we
can
open.
Collective
can
use
the
Swift
method
where
they
can
just
directly
deposit.
The
money
depends
without
the
need
for
fiscal
hosts,
if
I'm
not
mistaken.
B
B
I.
Think
that's
the
last
comment.
Yes,
this
one
so
now
I'm
not
sure
how
things
will
go
in
terms
of
like
if
we
have
contributors
like
from
countries
that
have
sanctions,
how
will
they
go
forward
because
I
know
like
wise
doesn't
work
in
Nigeria
totally?
So
let's
say
we
have
a
contributor
in
Nigeria
right,
for
instance.
So
how
can
they
ask
wise
like
to
try
to
transfer
money
because
they
no
longer
provide
those
kind
of
services
to
Nigeria
or
let's
take
place
and
stripe
strive?
B
Doesn't
totally
work
in
southern
Africa,
so
there's
no
way
I
can
access
funds
unless,
if
I
use,
maybe
Pioneer
I'm,
not
sure
if
Pioneer
does
restrict,
we
have
countries
that
are
not
restricted,
I'm,
not
sure.
So
this
is
a
challenge
that
we
are
currently
facing,
or
most
people
are
currently
facing
and
in
terms
of
like
accessing
funds.
So
this
goes
hand
in
hand
in
the
open
collected
funds,
distribution
for
contributors.
A
A
The
most
important
is
for
others
to
understand
why
we
even
have
this
discussion,
and
just
please
people
join
this
discussion
that
via
chess
love
started
last
year,
because
one
of
the
goals
for
this
year
is
to
is
to
explore
and
have
kind
of
process
in
place
at
least
experimental
process,
to
see
how
we
can
share
the
money
that
we
get
on
open
Collective
with
the
with
the
maintainers
to
not
exploit
people
too
much
in
their
free
time.
So
we
can
actually
pay
something.
A
D
A
B
Okay,
all
right
so
in
terms
I,
think
AP
I
until
yeah
we
have
one
confirmation
and
we
Madrid,
that
is
towards
the
end
of
the
year,
so
it
can
be
a
then
November
or
December
so
yeah
we
still
I'm
still
discussing
with
Ivan
in
terms
of
like
the
schedule,
how
many
speakers?
How
are
we
going
to
finalize
everything
so
yeah?
We
just
have
like
one
solid
one,
solid
location
confirmed
at
this
moment.
A
A
A
Oh
yeah
yeah
and
there's
a
comment
from
akshat
about
the
issue
with
yeah
of
getting
payments
from
open
Collective,
especially
like
like
even
with
India.
There
was
a
problem
writing
Pioneer
account
was
required
for
everyone,
so
think
like
I'm,
not
sure
what
happens
with
wise,
because
last
time
like
we
were
able
to
do
many
things
with
wise
I
personally
used
wise
for
many
things,
and
now
it's
suddenly
getting
more
complex
when
it
was
Estonian
startup.
It
was
different.
Now
when
it
got
bigger,
something
is
blocking.
It.