►
From YouTube: Community Committee Meeting
Description
A
Go
live
awesomely
alive
on
YouTube,
hello,
internet.
Welcome
to
another
episode
of
know
from
can't
come
so
our
meeting
issue
is
issue.
Number
497
in
you
know
Jas
slash
community
committee
for
those
following
along
at
home.
So
let's
start
out
as
usual
with
an
initiative.
Recap
we're
gonna
start
at
the
top
go
to
the
bottom.
A
Let's
see
been
on
this
call
with
I
can
n
do
not
see,
although
we
had
a
I'm,
not
sure
if
this
was
talked
about
last
time
say:
I
wasn't
present.
We
if
we've
had
some
good
interactions
with
I-10
and
it
crossed
over
from
look
sorry,
Design,
Group,
I
and
we're
working
towards
the
solution
to
get
everything
into
the
new
translation
pipeline
for
the
new
website.
I.
B
B
The
way
we're
doing
this
is
to
ensure,
like
inclusivity
and
the
cohort,
is
inclusive
enough
and
has
different
skill
levels
and
different
people
from
places
around
the
globe
and
we're
gonna
announce
it.
Probably
on
Monday
and
I'm
gonna
work
with
Rachel
to
write
a
blog
posts
about
the
mentees
and
mentors
for
its
that's
awesome.
A
A
I,
don't
see
a
mod
on
the
call,
but
I'll
give
an
outreach
update.
So
we
are
pivoting.
Leave
official
officially
cancelled
our
pro
membership
with
meetup
calm
because
they
don't
have
a
non-profit
pricing
model
anymore
and
it
would
have
been
prohibitively
expensive
to
use
them
for
tracking
meetups.
So
we're
exploring
kind
of
MVP
options
for
tracking
tracking
meetups
and
gonna
be
focusing
more
on
getting
the
community
page
on
nodejs
dev
in
a
in
a
happy
state
in
that
meeting.
A
C
C
C
Life
balance
would
totally
point
me
towards
doing
that,
but
yeah,
that's
kind
of
where
I
am
and
I
shared
the
same
with
the
user
feedback
team
and
kind
of
begun
to
walk
everyone
through.
You
know.
Alright,
you
know
what
if,
and
so
you
know
exploring
that
with
the
user
feedback
team,
you
know
what,
if
I
need
to
step
back,
how
do
we
move
forward?
The
the
biggest
thing
that
were
protective
of
in
user
feedback
is
the
great
engagement
that
we've
gotten
with
our
meetup
groups.
A
Well,
thank
you
for
putting
all
that
effort
into
succession
planning
I.
Every
single
person
in
here
would
be
very
sad
to
see
that
PR
go
up,
adding
you
to
the
emeritus
list,
but
if
there's
any
help
that
we
can
provide
to
kind
of
make
sure
that
the
transition,
if
and
when
it
does
happen,
goes
smoothly.
Let
us
let
us
know.
E
D
A
C
C
F
So,
if
you
know,
if
you
like,
you
know,
you're
sitting
at
lunch
with
someone
that
you
work
with,
or
you
know,
you're
hanging
out
and
someone
who
is
strong
in
like
community
or
marketing
may
have
a
really
good
opportunity
to
be
able
to
contribute
to
open
source
for
the
first
time.
So
this
is
a
nice
thing
to
share
for
the
node
level
or
for
the
you
know,
open
jazz
level
for
opportunities
to
pull
cool
people
into
the
fray.
Actually.
C
C
Ten
days,
so
not
this
Friday,
the
Friday
after
now
you
to
come
to
the
meeting,
then
in
terms
of
you
know,
wanting
to
officially
raise
your
hand.
You
know
an
issue
in
the
user
feedback
repo
would
be
well
placed
and
invited,
and
we
also
have
a
unknown
slackers,
a
channel
there
for
user
feedback,
where
you
can
also
sort
of
kick
off
a
more
informal
conversation.
E
G
So
that's
a
bit
of
a
change,
but
we
wanted
to
put
everything
in
one
repo,
because
I
think
people
are
actually
getting
confused.
So
we're
walking
back
in
an
earlier
decision
to
keep
administrative
stuff
and
development
stuff
in
separate
repos
to
make
it
easier
for
folks
other
updates,
we're
probably
going
to
be
integrating
I'll,
go
Leo
code
search
into
the
work
and
that's
the
that's
all
I
have
for
now.
E
A
A
G
A
Silence
is
golden
cool,
so
our
first
two
issues
are
around
the
node
collection,
mostly
a
status
update,
and
we
recap
from
co.labs
summit.
So
neither
a
mod
or
Rachel
are
here
for
an
update,
but
I
have
something
to
read
from
Rachel
on
next
steps
or
sorry
as
well
as
Waleed,
so
issues
number
four
91
and
439
both
related
to
no
collection.
A
Next
steps
we
are
reading
from
Rachel
were
essentially
waiting
for
the
okay
to
formally
updates
mission
guidance
and
do
a
push
around
collecting
new
content
from
the
collection,
so
I'm
moving
forward
with
that
fairly
soon,
I
and
Waleed
is
going
to
help
set
up
and
provide
guidance,
I
project
management,
type
tool
to
help
revamp
task
tracking
for
this,
because
a
lot
of
these
articles
kind
of
get
lost
in
email
accounts
and
we
lose
track
of
status,
so
we're
gonna
see
updates
on
that
fairly
soon.
We'll
see
updates
in
issue
number
491.
A
A
So
we
need
we
need
to
kind
of
just
officially
call
for
official
calm,
calm
review
of
the
e
blog
posts
that
Rachel
wants
to
put
out
and
then
she's
gonna
wrap
it
up
with
the
Linux,
Foundation
or
sorry
open,
Deus
side
of
things
to
finally
move
it
forward.
I'm
gonna
drop
a
link
in
the
chat
we
should
have
hopefully
seemed
Google
Doc
going
around
and
I'd
love
to
be
able
to
click
the
checkbox.
A
On
that
calm,
calm
review
at
the
top
of
the
page
there
we
had
gotten
a
chance
to
review
it
earlier
kind
of
another
I'd
love
to
give
sign-off
I'm
gonna,
give
I
think
we
have
quorum
here,
yeah
totally
so
I'm
gonna
give
another
24
hours
for
us
to
call
out
comments,
and
if
I
don't
hear
any
strong
objections
from
folks,
please
in
the
doc,
then
I'm
gonna
I
would
love
to
be
able
to
say.
We
have
completed
common
come
review
and
we
are
now
just
waiting
for
publication.
E
Are
the
changes
going
to
be
addressed
like
I,
think
I
I?
If
you
traders
are
just
or
window
just,
we
I
think
we
should
also
review
it
again
at
that
point,
because
there
is,
you
know
a
non-trivial
amount
of
comments.
I'm
not
trying
to
overburden,
but
like
yeah
I
think
we
should
probably
try
to
get
those
changes
addressed
and
then
review
again.
A
A
A
E
So
I'm
more
asking
I
I
want
to
pull
it
up
again
but
yeah.
So
this
is
something
effectively
I
think,
while
de
owns
the
I
don't
know,
I
think
they
did,
but
they
own
the
notice,
LinkedIn
I
believe
they
gave
it
to
zubi
zubi
reached
out
the
other
day,
saying
she's
still
alive,
and
she
so
she's
doing
this
work
completely
under,
since
he
did
unpaid
and
I
recognized
so
I.
E
Additionally,
and
then
you
know,
we
can
discuss
how
we
can
figure
out
the
details
on
that,
but
yeah
I
think
this
is
something
we
can
and
probably
should
take
on,
just
because
it's
well
either
us
or
the
foundation.
I
kind
of
prefer
us
but
I
also
know
that,
like
it's
a
challenge
and
it
does
align
with,
you
know
the
social
social
side
of
things
that
were
working
towards,
but
it
is
also
a
magical
amount
of
work,
and
so
it's
something
that
you
know
if
you
can
either
automate
or
help
with
or
know.
A
A
Yeah
I
was
I,
had
taken
a
look
because
I
had
been
made:
admin
a
while
back,
like
I,
remember,
approving
people
to
go
join
the
group
I
wouldn't
took
a
look
I'm,
no
longer
admin
so
get
that
resolved.
I,
don't
know
what
happened
there
I,
but
a
lot
of
the
work
is
just
approving
the
people
joining
like
it's
from
what
I
come.
What
I
saw
my
brief
time
in
there
like
there's
this
huge
backlog
of
people
requesting
to
be
added
to
the
group,
because
it
is
a
closed
group
and.
E
A
E
F
A
Was
donated
by
yld,
essentially
they
yeah
and
it
was
never
fully
integrated
into
the
Foundation's
flow
and
then
should
be
left
shortly
after
it
got
handed
off
again.
So
we
need
a
we
needed,
a
sweeping
foundation
folks
and
get
somebody
else
on
there.
I
agree
like
we
probably
want
at
least
one
calm,
calm
and
one
foundation
sure.
E
H
Mean
it's
either
me
or
Rachel.
If
in
doubt
you
can
always
add
operations
that
open
JSF
org
as
a
user
and
something
like
this
and
the
the
emails
will
always
go
to,
whoever
is
the
current
operations
person
and
so
for
something
like
this,
where
it
looks
like.
Maybe
it's
gone
stale
or
maybe
there's
a
user
who
helped
set
it
up,
and
it's
no
longer
here
that
should
help
future
proof,
and
then
we
can
figure
out
everything
everything
from
there
once
we
have
access
so.
H
A
E
A
A
Our
positives
are
so
I
yeah,
I
I.
Think
I
can
keep
poking
at
it,
though
see
the
content
group,
but
yeah
I
think
the
more
people
we
have
with
active
hands
and
on
this,
the
better
so
I'm
I'm
gonna,
amend
to
that
ticket
to
add
you
Brian,
as
well
as
Rachel
and
myself
to
the
group
and
we'll
collectively
figure
out
what
direction
you
take
it.
It
sounds.
G
E
And
so
go
ahead,
sorry
say:
I
feel
like
that
you're
like
having
a
internal
policy
around
this
is
like
yes,
any
comecon
member
can
be
honest.
Having
that
allows
gives
the
privilege
of
that
to
everyone
to
say,
like
yes,
you're
a
kumki
member.
Okay,
like
you,
know,
you're
following
the
leadership
guidelines
for
the
project,
we
can
add
you
in
that,
like
my
time
is
in
fear
and
more
even
there
again
recently
zoom,
like
it's
just
uncertainty
around
how
to
do
this.
E
There
prevent
people
who,
rather
than
necessarily
being
able
to
have
like,
have
access
like
it's,
not
it's
not
a
hard
rule
or
anything
around
like
who
can
or
can't
have
access,
and
we
generally
are
very
liberal
with
that
so
I
think
more
of
just
like
maybe
even
having
a
specific
document
of
access
policy
or
something
like
that
and
have
each
of
these
rules.
Like
you
know,
if
we
have
a
LinkedIn
item
in
that
policy,
we
can
then
say
you
know
all
comecon
members
are
welcome
to
manage
this.
If
they
want
to.
E
D
E
Yeah
yeah
I'm,
always
just
nervous
about
like
putting
passwords
in
in
something
especially
winter
like
zoom,
doesn't
really
have
our
back
in
a
way.
That's
nice
for
us,
and
especially
when
there
is
something
like
LinkedIn
where
there
is
our
back
and
you
like
someone
know.
If
someone
did
something
incorrect,
we
wouldn't
actually
know
who
it
was
if
they
committed
or
block
someone
their
appropriately,
that
we
wouldn't
have
any
kind
of
context
on
who
that
was
tied
to
user
accounts.
That's
a
different
story
and
we
can
again.
A
So
I
think
we've
successfully
transitioned
to
the
next
issue.
Just
for
folks
on
YouTube
we
kind
of
have
transition,
takes
you
number
four,
and
that
I
need
for
policy
on
access
to
the
zoom
account
and
yeah.
It's
kind
of
piling
on
to
there,
like
the
access
to
policy
document
is
great
when
our
tools
actually
have
individual
account
granularity
of
access
like
LinkedIn,
like
you,
can
get
yourself
added
to
the
to
the
group.
A
If
you
want
to
help
admin,
it
zooms
specifically,
is
rough
because
to
me,
like
you
said,
it's
just
one
login
and
if
we
give
everybody
the
password
and
then
hypothetically
in
the
future,
someone
goes
rogue
and
we
want
to
revoke
access.
We've
now
changed
the
credentials
for
everybody
who
uses
it.
Yeah.
E
Like
I
feel
like
having
a
policy
of
like
if
you're
a
member
or
if
you're
a
calm,
calm,
we
initiative
we'd,
ask
the
the
pom-pom
care
for
the
password
and
user
name
and
password.
That
is
a
fine
thing,
because
that
also
lowers
the
the
discussion
that
you,
the
chair
has
to
have
of
like
they
can
just
then
copy
and
paste
it
and
one
write
that
they
have
shared
it.
With
that
person
yeah
the.
A
A
H
A
H
I,
don't
know
that
I'm,
the
only
one
but
yeah
that
that
is
the
natural
limiting
factor
here.
I
mean
anybody
can
use
a
shared
zoom
credential,
but
you
have
to
be
authorized.
You
have
to
be
added
as
an
account
on
the
YouTube
account
in
order
to
be
able
to
actually
push
anything
live
or
upload
for
that
matter.
There's.
D
D
You
know,
usually
it's
I've
always
been
a
little
uncertain,
so
usually
what
I
do
is
I
send
like
an
email
to
the
TSC
and
admin,
as
well
as
the
like
click.
The
current
people
at
the
Foundation's
think
hey
I'm
planning
to
do
this
any
objections,
and
if
there
aren't
any
them,
you
know
go
ahead.
We
could
equally
make
it
a
foundation,
supportive
thing
that
you
send
a
request
to
somebody
there,
but
they
probably
need
somebody
saying
yeah.
We
think
that's.
Ok,
too
right
right.
G
D
G
So
so
it
seems
like
we
started
talking
about
who
has
the
power
to
like
turn
on
the
YouTube
stream,
but
I'm
wondering
like
the
original
issue
was
because
we
had
people
who
needed
to
start
a
meeting,
but
the
usual
people
started.
The
meeting
were
not
available,
so
initially
we
were
starting
to
talk
about
giving
people
access
to
the
zoom
if
they
were
in
come-come
or
I.
Suppose
the
CSC,
but
in
this
case
we're
just
talking
about
the
comic
Yeah.
D
A
This
this
becomes
somewhat
caught
up
in
our
next
issue
as
well.
We
discussed
in
the
club
summit
opening
up
the
ability
to
chair
a
to
champion
a
working
group
strategic
initiative,
sorry
allowing
those
champions
to
not
necessarily
be
on
the
column
like
have
them
be
regular
members,
not
voting
members
I'm
assuming
we
would
extend
this
privilege
to
regular
members
or
champions
of
the
group
as
well
correct.
E
So
regular
members
like
there
is
like
at
this
point:
we
can
change
this,
but
there
is
no
such
thing
as
a
regular
member
of
a
group.
There
are
members
of
the
group,
so
its
dependence
I
think
that
we've
not
totally
ratified
that
yet
or
like
will
you
address
that
and
I
think
that's
a
change
we
want
to
address
when
we
implement
it,
I
think
for
the
immediate
future.
E
This
is
like
a
decent
policy
to
implement
I'm
writing
the
file
now
just
than
if
you
are
a
strong
person,
but
you
know
I
think
we
can
at
least
accept
this
and
kind
of
have
some
policy
in
place
of
like
this
is
how
we
can
do
this
and
then
move
forward
as
we
go
and
think
about
regular
membership.
Mm-Hmm.
A
Yeah,
so
a
very
concrete
use
case
for
this
is
there:
were
there
been
a
couple
website,
redesign
meetings
where
neither
me
nor
Mineo
could
make
it
and
owner
who's
on
the
call
right
now
was
able
to
lead
and
as
a
stellar
member
of
the
website,
I'm
sorry
design,
but
it's
not
technically
a
member
of
comm
columnist
joined
as
observer
for
a
while,
but
would
be
also
to
be
able
to
get
him
credentials
to
be
able
to
start
our
meetings
into
this
stream.
It's
like
we.
We
have
cases
of
this.
D
The
node
working
like
the
TTC
side,
technical
I,
don't
know
whatever
I
want
to
call
it
like
other
working
groups
and
teams.
There's
lots
of
people
who
are
not
TSC
members
who
have
been
given
access
so
I,
don't
think
that
should
be
a
like
from
plastics
practice.
That's
another
reason
that
sort
of
says
in
my
mind
it's
like
yeah.
It
should
just
be
I.
A
Also
just
went
and
took
a
look
at
my
my
own
Google
permissions
on
the
node
account
I.
Don't
have
the
ability
to
give
other
people
permission
to
stream
I'm,
not
Lee
I'm
listed
as
a
manager,
not
an
owner
and
I.
Believe
that's
where
the
line
is
drawn.
I
yeah,
it
would
be
nice
to
have
the
chairs
of
both
TSE
and
Kham
Kham.
Have
that
dawson
you?
You
are
set
up,
yeah
I.
D
F
D
A
D
E
A
Okay,
sorry
yeah
we
can,
we
can
get
that
in
and
to
me
it
might
be
good
when
you
post,
the
kind
of
federated
access
John
in
Lowell
I
will
make
sure
it
jives
with
charter
changes
that
we
need
to
make
yeah
so
feel
free
in
the
strong
man
to
use
language
that
might
not
already
be
in
the
Charter
I
can
make
that
they
kind
of
land
in
a
similar.
This
is
what
timeline.
A
E
D
So
you
know
it's
I,
don't
know
if
there's
some
other
way
to
be
able
to
share
those
or
to
like
it's.
My
concern
is
like
okay,
we
do
have
to
change
it
for
some
reason.
Now
we're
basically
gonna
have
to
you
know,
run
around
and
tell
everybody
what
it
is
manually.
We
also
don't
necessarily
know
who
actually.
A
I
G
G
I
I
just
met
the
creator
because
I
was
visiting
Helsinki
a
couple
of
weeks
ago
and
it's
actually
gained
some
traction.
What
it
does
is
it
actually
shares
a
file.
So
a
lot
like
I
think
easily
called
key
pass.
There
was
another
open-source
password
manager
standard,
so
I
think
if
we
use
that
we
might
be
able
to
share
a
file
and
give
people
access
to
a
specific
file,
maybe
through
Google
Drive,
which
then
people.
G
H
H
D
J
A
A
Far
as
I
understand
awesome,
just
taking
notes
on
your
so
to
summarize
it's
okay
to
federate,
as
we
see
fit,
I
also
have
access
to
YouTube
for
to
show
certain
permissions.
We
can
share
that
as
we
see
fit,
Jezza
committees
have
permission
to
share
as
they
see
as
required
and
Brian
you're
gonna
have
a
shared
last
path
or
a
class
account
that
will
be
able
to
share
this
out,
and
we
should
treat
that
as
the
primary
way
to
share
credentials.
A
This
is
a
ticket
I
opened
up
for
the
distant
future,
so
we're
we're
looking
at
pulling
in
API
documentation
right
now,
we're
not
going
to
be
making
significant
changes
to
the
way
it's
currently
stored
or
the
way
it's
currently
set
up
and
we're
basically
just
going
to
be
hitting
up
the
current
JSON
files
of
all
the
markdown
stuff
in
the
denote
core
to
then
display
it
as
API
Docs
they're.
All
I
had
a
lot
of
fun,
hallway
conversations
with
assorted
folks
about
the
documentation,
needs
of
node
and
the
way
that
we
currently
store.
A
Api
Doc's
I
limits
us
a
lot
and
in
how
we're
able
to
present
the
information
and
to
what
detail.
We've
been
presented
on
the
site
itself,
just
quick
rain
to
dump.
They
are
put
on
a
single
markdown
files
per
per
module.
Essentially,
and
when
you're
updating
the
code,
you
have
to
make
sure
to
go
in
and
update
the
markdown
file.
A
A
lot
of
projects
are
now
using
encode
documentation
so
like
they
use
je
s
docx
or
some
other
standard
format
to
annotate
the
code
where
they
write
it,
and
it
allows
a
lot
of
tools
to
do
like
you
know,
jump
to
jump
to
definition
and
their
documentation
and
they'll
bring
you
to
the
source
code
where
you
can
see
where
it's
written
it'll
also
allow.
You
know,
pulling
out
a
lot
of
metadata
information
automatically.
So
you
know
it
takes
an
argument.
It
takes.
This
function,
takes
arguments
of
this
shape.
A
Here's
the
type
that's
expecting
you
know
this
is
this
is
a
method.
This
is
a
static
property.
This
is
public,
that's
private,
again,
I'm
annotated
where
the
sources
I
would
love
to
float.
The
idea
of
doing
this
not
anytime
soon
and
there's
a
major
change
and
Michael
I
see
you
laughing
over
there
I'm.
A
Know,
yeah
exactly
and
so
like
this
is.
This
is
a
non-trivial
thing
to
proposed
and
to
introduce
and
to
execute
on
and
I
wanted
to
float
it
here
in
this.
In
this
higher
level,
venue
like
outside
of
no
no
JSF
before
bringing
it
elsewhere
and
also
asked
specifically
Michael
since
you're
the
most
context
on
the
technical
side
of
things,
I
believe
how
this
can
be
best
presented,
packaged
in.
D
Like
you
know,
my
initial
reaction
is
kinda
like
well
yeah.
That
would
be
good,
it's
just
how?
How
would
we
get
there?
I
guess
the
other
concern
might
be
just
like
do
these
things
opposite
keep
the
code
when
you're
looking
at
the
code
itself
right
like
so
how
much
is
that
going
to
impact
on
the
code?
D
I
think
you
know
an
example
is
maybe
the
best
way
to
to
move
forward
is
to
say,
like
here's,
an
example
of
what
this
one
would
look
like,
both
in
what
you
end
up
generating
and
what
it
looks
in
the
code,
and
then
that
would
you
know
you
could
get
some
very
concrete
feedback
and
people
would
be
able
to
look
at
and
say
more
than
just
that
and
concept.
It
sounds
good
they'd
be
able
to
say.
Oh
that's
a.
E
E
I'd
also
need
super
curious.
If
there
there
was
a
way
to
automate
directly
15
our
current
markdown
documentation
into
jsoc
style
comments
and
and
like
not
necessarily
like
just
be
markdown
side
of
it,
and
then
you
know
having
in
something
like
whatever,
whatever
else
needed,
for
the
stock
being
able
to
just
directly
cut
through
yab
and
then
build
on
top
of
that,
rather
than
rewrite
it
right.
Yeah.
A
Yeah
I
think
both
right.
Whatever
approach
is
gonna
be
taken
like
we
have
to
make
sure
it
works
piecemeal
and
what
may
like,
we
can
get
a
proof
of
concept
of
here's,
what
it
would
look
like
up
just
to
kind
of
build
consensus
around
that
as
an
approach
and
validate
that
it's
a
it's
a
good
approach
for
the
project.
A
We
would
probably
the
website
redesign
team
can
move
forward
with
the
assumption
that
there'll
be
a
if
that
documentation
style
moves
forward,
with
the
assumption
that
there'll
be
kind
of
a
split
world
for
awhile,
where
some
documentation
will
live
in
markdown
in
a
separate
file,
some
will
be
in
like
J
a
stock
style
comments
and
can
bake
it
into
our
plan
to
to
make
sure
we
can
stitch
both
both
styles
together
and
present
it
on
the
new
site.
Well,
we
could
then
start
landing
it
assuming
it
all
goes
well
landing
it
in
earnest.
After.
D
I
wondered
like
if
one
like
how
flexible
Jess
talk
is
is,
if
you
know
the
first
integration
would
be
into
the
make
targets
where
we
generate
one
of
those,
a
markdown
files
from
the
code
right,
in
which
case
it
was
just
like
you
know,
in
the
the
actual
one
that
you
would
have
before
head
would
be
like
warning.
This
is
not
a
generative,
don't
edit
now
I,
don't
know
that
markdown
would
be
the
final
target
mm-hmm,
but
that
would
be
like
if
it
was
possible
to
say
okay,
we're
gonna
generate
you
know,
say
the
mep.
D
I
docks
as
a
first
step
and
it
so
basically
it
looks
the
same
to
everybody
else.
There's
just
an
extra
build
stuff
to
get
that
one
that
might
be
an
INT
migration
path.
We
backwards
compatible.
Okay,
then,
then
you
can
say,
oh
and
we
can
generate
some
other
format
for
the
website
or
whatever
and
eventually
maybe
get
rid
of
the
markdown.
That's
a.
A
Good
call
make
it
backwards
compatible
from
the
get-go
okay,
I'll
I
wanted
to
float
this
first
here,
just
to
kind
of
get
its
annika
check
and
make
sure
it
was
worth
up.
Leveling,
barring
any
strong
opposition
to
that
that
I'll
bring
this
back
to
website
redesign
and
we'll
take
it
as
a
task
to
get
something
written
up
and
propose
it
over
on
the
technical
side
of
the
project.
Yeah.
D
A
E
A
meeting
there's
one
in
action,
I'd
like
to
bring
up
and
kind
of
it's
not
been
discussed
with
anyone
I'm
not
but
I'd
like
to
see
what
people
think
before
I.
You
know
open
up
your
next
year,
anything
so
the
open,
D
recitation
has
an
official
slash,
yeah
I,
don't
think
all
of
us,
or
many
of
us
are
eating
it.
I
like
that.
We
have
an
official's
like
that.
The
foundation
as
a
whole.
E
It
kind
of
helps
us
have
more
of
a
communication
channel,
for
you
know
both
know
people
in
an
official
kind
of
sanshin
platform
while
also
having
a
place
for
you
know
us
to
talk
with
our
product
partners
kind
of,
or
you
know,
Co
Co
members,
the
other
members
of
honey,
I,
I'm
curious.
If
people
would
be
interested
in
or
in
a
proposal
to
standardize,
pum
pum
know
des,
they
have
suggest
that
we
use
that
specific
slap
as
our
Aflac,
where
we
can
have
discussed
event
on
Tom
and
our
image.
A
H
There
are
a
lot
of
people
on
that
account.
Well,
I'm,
sorry,
not
right!
Now
it's
it's
about
60,
some,
the
cap
for
the
open
source
discount.
So
you
can
move
up
to
the
paid
tier,
but
you
get
it
for
free.
The
cap
is
250
and
after
that
I
think
it's
something
like
10
bucks
per
user
per
year,
which
you
know
for
one
or
two
projects
is
fine,
but
if
this
eventually
ends
up
scaling,
then
we
run
into
potentially
a
fairly
sizable
expense,
particularly
if
many
people
are
idle.
H
So
it's
kind
of
at
this
point
you
know
I
think
they
really
I,
don't
know
what
the
toilet,
what
the,
what
the
stomach
is,
we're
moving
to
a
paid
account.
We
may
be
worrying
about
a
problem
that
would
never
be
a
problem.
Maybe
we
won't
get
250
people
on
the
channel,
but
I've
hesitated
on
converting
over
to
the
paid
account
her
to
the
to
the
pro
account.
Just
because
of
that.
E
F
F
I
D
B
A
F
It's
again
like
this
goes
just
goes
back
to
you
like.
Why
do
we
need
a
listed
as
official
versus
like
listing
it
as
a
partner
things
that
we
had
done
before
right?
The
informal
like
we're
chatting
in
these
places,
but
we
like
I,
don't
know
the
answer.
I,
don't
think.
We've
had
the
conversation
around
moderation,
I.
F
E
How
do
path
up
and
and
the
kind
of
the
reason
I
I'm
poking
at
this-
is
because
I
since
it
is
open,
gates,
foundation,
Brendan,
I,
assume
there
will
be
some
level
of
that,
and
so
maybe
getting
clarification
on.
That
is
good,
because
I
would
be
very
concerned
if
I.
If
there,
there
wasn't
moderation
happening
in
it,
an
official
or
seemingly
official
media
box.