►
From YouTube: Node.js Community Committee - Jan 9 2020
Description
B
Yeah
great
thanks,
Michael,
okay,
everyone
welcome
to
another
noches
community
committee
meeting
I'm
TV
siren,
and
we
have
a
bunch
of
folks
on
today.
Does
it
really
I
think
the
largest
compound
meeting
in
a
bit
so
good
start
to
the
to
the
new
year
for
sure?
Okay?
So
we
have
a
relatively
foolish
agenda.
I
removed
a
couple
things
just
because
they
were
outdated
or
kind
of
moot
at
this
point,
but
I
did
you
know,
comment
in
those
perfectly
and
you
know
try
to
help
move
us
forward
on
that.
C
There's
a
PR
open
which
I
need
to
a
bit.
There
was
some
feedback
from
tyranny
and
some
other
people
also
from
the
process,
and
there
was
some
discussion
in
on
an
other
issue
about.
If
we
can,
we
should
maintain
the
noches
collection
anymore
or
not
as
there's
not
much
traffic,
as
we
see
so,
but
I
suggested
that
we
we
go
on
for
until
the
next
clips
are
made
with
noches
collection
of
data
processor
and
see
if
we
can.
D
C
More
blogs
and
more
submissions
from
people
after
that,
if
that's
not
possible
until
the
next
clap
summit,
after
that,
we
can
think
about
if
we
don't
want
to
maintain
it
anymore.
But
yeah
I
have
some
things
on
my
to-do
list
to
update
him
in
the
process
and
once
that
done
I'll,
let
ya
I.
Let
everyone
in
the
comm
come
know
that
we
are
following
this
new
process
and
it's
like
more
easy
and
more
open
for
everyone.
I
may
need
to
have
some
meetings
with
Rachel.
C
D
E
D
Website
redesign
/p,
no
gas,
dev
right.
Okay,
we
do.
We
don't
have
that
repo
anymore.
It's
it's
everything
is
in
no
just
out,
though,
so
that
clarity
needs
to
be
reflected,
but
until
a
person
does
step
in
who's
able
to
both
Shepherd
the
pr's
along
and
attend
the
meetings
and
also
has
privileges
to
login
to
meetings
or
start
the
meetings
for
the
the
initiative.
I'm
happy
to
just
stay
on
it.
Just
I'm.
Putting
this
out
there
frequent
fancy.
F
To
speed
again
on
the
project,
there's
a
lot
of
there's,
you
know
various
activity
and
interest
from
you
know:
disparate
parties
who
have
been
involved
in
the
past
I
think
it's
I
think
20
20
20
is
a
good
year
to
get
this
thing
off.
The
ground
should
like
really
like
I,
think
it's
definitely
something
that
I
want
to
focus.
D
F
I
am
excited
to
get
some
of
the
people
who
have
expressed
interest
working
on
it
again,
so
I
think
yeah
I
mean
there's,
there's.
Definitely
like
I'm
consistently
getting
requests
for
translations
languages,
there's
no
shortage
of
people
that
want
it
I
mean.
Obviously
it's
the
thing
that
we
need
to
be
doing
and
yeah
I
think
finally
hitting
a
point
in
2020,
where
I
can
consider
it
an
option
for
me
to
to
do
so,
I'm
happy
to
continue
to
help,
but
that
ended
up
saying
the
organizer
meetings.
F
F
H
Hello,
everyone
so
in
our
free
shave,
I
finally
completed
that
community
page.
We
were
talking
your
I'm
going
to
just
put
the
link
here
in
the
chat.
This
is
sort
of
fun
new,
you
know
start
the
new
community
page
but
notice
the
Learman
was
sort
of
us
just
a
stop
please.
So
what
we
are
going
to
do
next
is
we
are
going
to
put
this
PR
into
the
node.js
door.
Dev
repository
for
the
website.
Redesign
initiative.
Do
if
you
folks
have
any
comments,
definitely
feel
free
to
each
other.
G
Cool
turn
here
on
mute,
but
I'll
jump
in
and
say
an
update
on
user
feedback,
which
is
something
that
we
suggested.
Moving
to
the
open,
G
foundation,
I
finally
moved
the
repo
over
there.
I
still
have
a
lot
of
cleanup
to
do
and
make
it
like
open,
Jas,
focused
and
clear
out
the
things
that
are
not
feedback
related,
but
I
did
it
in
a
way.
That's
the
nodejs
repo
still
exists,
and
we
can
archive
that
repo
and
I
have
here
the
link.
G
So
yeah
I
created
a
an
issue
to
reap
to
archive
the
node.js
user
feedback
Rico,
and
then
we
can
just
kind
of
move
on
to
the
open
jess
side
of
things.
But
if
you
have
any
interest
in
user
feedback
surveys
and
and
kind
of
helping
you
flesh
out
that
framework
or
whatever,
though
or
concede
it
there,
please.
Let
me
know.
B
A
B
A
G
Yeah
I'm,
not
sure
what
exactly
to
share.
But
if
you're
interested,
especially
in
the
code
of
conduct
stuff,
we're
gonna,
we're
gonna
spin
up
something
of
a
working
group
to
really
bootstrapped
that
whole
process
being
moved
to
the
open,
J's
foundation
and
the
complexities
that
that
adds
kind
of
having
a
layer
above
and
having
multiple
projects
and
such.
If
you
have
any
interest
in
that.
Let
me
know.
G
A
Ik
on
that
front
worth
mentioning
is
the
discussion
around
whether
to
inline
or
not
inline,
the
contributor
covenant
seems
like
the
the
CPC
is
landed
on
inlining.
So
that's
what
was
landed
in
current
guidance
and
I
think
that's
in
line
with
what
the
calm
calm
ended
up
doing
for
or
what
tyranny
did
for
the
updated,
no
code
of
conduct.
So
that's
just
yeah.
B
B
There
there
is
also
one
relatively
large
thing
just
at
the
foundation
level.
Electron
joint
is
a
well
so
announced
intent
to
join
as
a
foundation
project,
and
they
are
in
going
through
the
incubation
process
presently.
So
that's
another
kind
of
thing.
If
you
weren't
at
the
events,
you
might
not
have
seen
to.
B
G
And
then
I
guess
one
other
thing:
I'll,
add
and
I
know
Rachel's
here,
but
there's
an
email
and
you're
in
boxes
for
Comic
Con
Fulke
about
the
events
in
in
the
summer
and
there's
some
renaming
discussion
happening.
I
think
the
particular
thing
is
that
node
is
no
longer
in
the
name,
and
so
we
just
wanted
to
make
sure
that
that's
there's
awareness
there
personally
I
always
felt
like
node
plus
J
s.
Interactive
was
the
funky
name.
So
I,
don't
I,
don't
mind
that
we're
moving
on
from
that.
G
B
Is
also
just
in
that
in
that
vein,
since
the
event
has
moved
to
June,
so
this
is
like
the
next
open.
J
s
interactive
the
type
event
it's
being
paired
with
open
source
summit
in
North,
America
I,
think
in
Austin
Texas,
one
of
the
Linux
Foundation
events,
so
it's
kind
of
a
sister
event
it
given
that
I
believe
the
collaboration
that
will
be
happening
there,
which
means
being
in
in
the
vacuum
of
T,
is
something
you
not
happening.
B
That
will
be
the
first
collaborative
summit
of
the
year
and
then
I
heard
suggestions
that
there
there's
another
note
specific
European
event
that
the
collaborative
summit
might
also
be
European
version
of
the
collaborator
some
it
might
be
paired
with.
So
just
if
you
have
questions
about
that
or
like
need
contacts
feel
free
to
reach
out
to
me.
I,
just
I,
don't
want
to
make
commitment.
B
A
G
Just
say
real
quickly,
Michael
to
add
some
context,
I
think
the
thinking
is
at
the
open,
Jas
level.
You
know
we
have
one
kind
of
flagship,
collaborator
summits
and
then
the
projects
themselves
may
have
one
or
two.
You
know
other
ones
as
well,
because
electron
has
one
or
two
and
has
one
or
two.
So
we
just
want
to.
The
thinking
was
that
that
might
be
a
good
patent
before
yeah.
A
That's
kind
of
what
I
heard
people
expressed
as
well
and
on
the
you
know
it's
it's
nothing's
been
like
written
down
or
agreed.
It
seems,
like
you
know,
most
likely.
The
best
thing
to
do
is
to
have
the
next
collaborator
summit
at
the
next
iteration
of
the
conference.
That
then
leaves
the
question,
as
you
said
typically
that's
around,
when
we
would
have
had
the
European
one.
So
what
do
we
do
there
and
a
few
ideas
have
been
thrown
out,
but
it's
very
much
a
you
know.
G
I'll
also
add
to
that
we
had
a
collab
summit
retrospective
earlier
this
week
and
are
already
excited
about
planning
the
next
one,
which
I
think
it's
great,
that
we
have
a
really
long
runway.
So
there
may
be
some
issues
coming
up
in
the
club
summit,
repo,
which
is
now
I
believe
in
Melbourne
jeaious
org.
G
B
B
With
that
I
think
we
can
probably
move
on
anything
else
in
open
dance
foundation
or
board
stuff
that
folks
have
questions
about,
and
it's
okay,
if
you
do
not
journey
time
box
but
yeah.
If
have
questions
on
that
cool,
that
sounds
like
a
we
can
move
on
then.
So
the
next.
The
agenda
item
is
the
first
agenda
item
is
the
issue
454
in
no
Josh
admin.
This
is
no
js'
social
media
accounts.
B
There's
a
variety
of
reasons,
the
largest
being
were
the
only
one
that
they
manage.
This
to
some
extent
made
sense
under
the
node.js
foundation.
It
makes
less
than
less
sense.
Under
the
the
open,
Geospatial
we're
like
in
yeah,
you
know
we
are
want
to
be
largest
account,
if
not
the
largest
I
believe
our
count
is
like
double
the
size
of
V
of
a
deist
foundation
account
itself
at
six
over
six
hundred
thousand
followers.
On
Twitter
and
then
a
hundred
thousand
on
LinkedIn
and
then
21k
on
Facebook
sort
of
like
relatively
high
impact.
B
But
what
I
jumped
at
this
because
I've
consistently
heard
from
folks-
and
this
isn't
a
dig
at
anyone-
who's
managed
this
account.
But
for
the
last
few
years,
I've
heard
that
you
know
I
I
followed
the
nerdiest
account
out
of
a
feeling
of
obligation,
because
it's
so
fundamental
work
on
you,
but
it
doesn't
really
tweet
things
that
are
relevant
or
doesn't
share
things
that
are
relevant
in
any
of
the
platforms
to
notice
itself
like
previously,
especially
in
really
the
node.js
foundation.
It
was
very
much
a
foundation
account
rather
than
a
project
account
and
I.
B
B
So
in
this
you
know
in
this
issue,
I
just
brought
that
up
I
kind
of
outlined
a
lot
of
those
details
and
I
also
made
a
small
proposal
for
how
this
could
be
managed.
Basically,
just
mending
it
the
exact
same
way.
We
manage
moderation,
so
any
any
member
comer
TSE
can
object
with
1-1
that
person,
you
know
so
somewhat
like
I,
go
and
submit
myself
as
someone
to
manage
this
account.
B
There
is
a
you
know,
week
or
two
week
period
where
for
objections.
If
there
is
any
minus
one
and
those
minus
ones
can
be
filtered
through
the
chair,
people
of
the
various
committees
or
the
two
committees,
but
if
there
is
a
minus
one,
if
there's
an
objection,
that
person
is
not
able
to
participate
in
this
at
this
way
in
this
way.
So
that's
the
process
we
currently
follow
for
moderation
and
it's
been
relatively
successful
and
I
think
this.
B
This
specific
thing
is
very
important.
So
like
this,
you
know
I,
don't
call
it
like
a
an
initiative,
but
this
task
that
we
have
is
like,
if
we
do
take
this
on
which
we
don't
have
to,
but
we
can,
if
we
do
take
this
on,
is
a
very
high-impact
thing.
The
nodejs
account
on
twitter
is
600,000
people
that
you're
broadcasting
to
that's
larger
than
many
stadiums
and
it's
a
verified
account.
B
The
LinkedIn
is
a
similarly
large
size
and
the
well
not
similar,
it's
1/6
of
the
size,
but
also
larger
than
most
stadiums-
and
you
know
Facebook
is
you
know
just
another
large
large
audience.
So
this
is
a
high-impact
thing
and
we
do.
We
do
want
to
make
sure
we
have.
You
know
it's
people
that
the
committees
have
trust
in
so
and
you
know,
aren't
gonna
tweet
or
post
bad
things
to
various
accounts,
so
pictures
of
cats
or
something.
F
Maybe
that's
it,
but
I
just
have
a
question,
so
it
seems
like
in
this
sort
of
scenario-
and
this
I
think
I'm
contextualizing
this
right,
but
you're,
saying
that
the
members
who
have
access
to
the
nodejs
Twitter
account
to
be
able
to
represent
that
go
through
a
similar
process,
as
we
do
with
moderation
now.
Is
there
a
limit
or
a
cap
on
the
number
of
people
that
can
do
that
and
of.
F
And,
if
not,
maybe
that,
like
this,
this
seems
it
seems
like
with
this
sort
of
thing
it
might
be
reasonable
to
to
have,
and
this
is
an
opinion
like
I'm,
just
throwing
this
out
there
I
don't
know
where
it
would
land
but
having
some
kind
of
quorum.
You
know
for
the
nodejs
Twitter
account
based
on
based
on
like
interest,
or
you
know
like
like,
like
to
calm,
calm
members,
to
confirm
the
TSC.
F
You
know
that
sort
of
thing
so
that
we're
getting
we're
not
like,
for
instance,
if
we
were
in
a
scenario
where
we
had
like
eight
people
from
Hong
Kong
using
nodejs
Twitter
and
then
like
one
person
from
the
TSC
yeah
I,
don't
think
people
who
are
looking
to
see
the
the
content
that's
relevant
to
them
about
the
runtime
are
gonna
like
get
enough.
You
know
representation
there.
B
And
so
one
thing
there
with,
like
moderation,
my
intent
there
was
to
not
limited
to
TSE
in
Hong
Kong
members,
so
anyone
in
the
org
would
be
able
to
kind
of
self
nominate
and
be
accepted
or
rejected,
but
I
definitely
definitely
understand
where
that's
coming
from
and
I
do
think
that
that
would
be
need
to
be
figured
out.
There's
also
like
other
concerns
of
like
hey,
you
know,
I,
some
I
was
gonna
use
a
generic
name,
but
then
it
was
the
name
of
a
compound.
Ever
so
I
was
like
maybe
I
should
there.
B
You
know
John
Doe
works
at
Amazon,
for
example,
and
like
it
becomes
a
mediator
of
this
and
then
like
Oh
Amazon
releases,
this
objectively
cool
thing.
For
now
there
is
a
conflict
of
interest
there
and
also
like
what
happens
when,
like
Joe
go
or
not,
Joe
John
goes
and
asks
goes
in
us
to
mean
to
post.
That
thing,
which
is
fine
like
I,
would
do
that.
But
it's
there
still
like
this,
like
underlying
conflict
of
interest
of
like
asking
someone
to
post
something
that
benefits
you
so
there's.
B
Definitely
things
like
that
and
I
think
I
believe
the
current
policy
for
that
account.
Is
they
just
don't
they
don't
post
anything?
That's
like
corporate
I
did
run
up
against
that
when
I
was
in
notes,
like
I
asked
them
to
like
between
something
or
something
like
that,
and
there
were
times
where
it
was
okay
and
times
just
when
the
answer
was
no
and
that
might
have
changed
at
this
point
because
of
the
foundation
changes,
but
that
you
know
I
I
do
think
that's
also
another
area.
We
need
to
approach.
B
F
A
Did
bring
it
up,
it
was.
You
know
you
added
to
the
agenda
the
TSC,
so
we
had
a
bit
of
a
discussion
I.
Think,
generally,
you
know
people
thought
the
the
approach
was
reasonable.
There
was
some
discussion
that
maybe
there
might
be
a
slightly
different
like
domination
process,
as
opposed
to
no
objections.
It
might
need
to
have
like
more
explicit
like
approvals
or
something
but.
D
A
B
And
I
think
that's
also
fun.
Like
I
know,
there
was
at
one
point
an
issue
with
a
moderation
team
member
where,
like
someone
was
on
vision
and
their
objection,
just
missed
by
a
day
because
they
were
on
vacation
and
they
like
got
it
in
at
the
last
second,
and
it
was
like
a
second
too
late,
so
yeah
yeah.
B
So
you
know
that
was
a
thing
and
I
think
adapting
that
approach
is
totally
fine.
I,
just
I
do
think
that
be
the
consensus
between
consensus
or
consensus,
seeking
probably
can
between
comity
SC
on
these
processes
is
like
the
approach
we
should
take
for
this.
Just
because
of
how
impactful
it
is
so
yeah.
A
A
D
A
B
A
B
B
And
that
definitely
brings
up
the
other.
The
other
elements
that
I
posted
know
that
I
did
not
talk
about
and
also
I'm
taking
up
too
much
time
on
this,
so
I
will
I
will
shorten
this
after
this,
the
other
other
element
I
brought
up.
There
was
a
former
punko
member
Gregor,
made
a
tool
called
Twitter
together,
which
is
based
on
kind
of
actions
which
basically
allows
you
to
control
a
Twitter
account
from
github
repo,
so
you
basically
merge
PRS
and
once
the
PR
is
merged,
that
is,
that
becomes
the
you
know.
B
B
Is
this
soda
a
few
people
and
then
proposing
it
in
a
few
R
would
be
a
fine
way
to
go
ahead
and
approach
that
and
then,
like
obviously,
no
merging
it
yourself,
but
yeah
yeah
I
think
that'd
be
a
fine
way
to
to
approach
that
so
yeah
I
I
think
that
there's,
like
all
of
the
problems,
have
relatively
straightforward
answers
or
solutions
in
and
for
context.
This
is
a
problem
that
we
faced
in
I.
B
Ojs
I
was
involved
with
Michael
and
trying
to
get
this
a
similar
thing
done
for
the
official
I
OJ's
account,
and
things
are
in
a
much
better
place
now
in
terms
of
tooling.
For
this,
then
they
used
to
be
so.
You
know
I'm,
relatively
confident
that
we'll
be
able
to
manage
this
successfully.
Oh
cool
yeah.
If
you
have
thoughts,
feedback
suggestions,
yes
so
Gary,
the
the
tweet
Pierre
will
be
in
a
public
repo,
I'm.
B
If
you
have
thoughts,
feedback
comments,
requests
anything
I'd,
definitely
go.
Take
a
look
at
that
issue
and
post
them.
I
think
getting
discourse
on
this
and
moving
forward
on
it
would
be
good.
It's
something
I'd
like
to
see
us.
You
can
be
able
to
succeed
in
and
you
know
take
over,
because
I
think
it
does
prevent
to
present
the
opportunity
to
add
a
lot
of
value
to
our
atarime
ecosystem
directly.
So.
F
Let's
take
a
like
more
time
on
this
topic,
but
very
quickly
very
quickly.
I
feel
like.
There
also
comes
some
kind
of
responsibility
of
discovery
with
that
to
like
make
the
messaging
relevant,
you
know,
and
so
I
don't
know
what
kind
of
systems
are
in
place
and
I
definitely
don't
have
context
on
how
that
was
how
this
is
done
in
the
past,
but
it
just
may
be
relying
on
people.
F
You
know,
from
from
the
community,
to
tweet
about
the
relevant
things
from
the
working
groups
that
are
happening
or
whatever,
but
there's
also
that
element
of
like
hey,
there's
the
audience
and
who's
the
who's,
the
champion
or
who's
the
person
who's.
A
part
of
you
know
this.
This
initiative
to
you
know,
like
figure
out
like
what's
actually
relevant
to
these
different
to
the
spectrum,
people
that
were
serving
so
just
something
to
consider
yeah
a
messaging
system.
That's
so
broad
that
also.
B
That
also
does
feed
into
this
is
not
just
about.
This
is
also
inbound
right.
People
do
tweet,
I
notice
a
lot
and
like
Rachel,
does
a
pretty
good
job
of
like
retweeting
things
that
are
relevant
like
retweeting,
when
there's
releases
are
like
retweeting
when
there's
a
meeting
like
this
one.
So
you
know
that
is
another
element
of
it
that
it
gets
a
lot
of
inbound
I
if
you've
ever
searched
at
nodejs
holy
hell,
but
yeah.
It's
not
just
outbound
like
broadcasting.
B
It
is
also
inbound
and
I
mean
even
even
small
things
like
liking,
someone's
tweet
from
the
nodejs
account
hugely
impactful
and
or
like
liking,
someone's
LinkedIn,
post
or
Facebook
post.
That
is
an
impactful
thing,
and
that's
part
of
the
responsibility
of
this,
too,
is
that
additional
kind
of
level
of
management
not
just
outbound,
so.
B
B
Okay,
the
let's
move
on
to
the
next
agenda
item.
The
next
agenda
item
is
remove
individual
membership,
director
role
and
move
on
cupcake
Emeritus
I
had
merged
this.
There
was
three
three
green
checks,
so
the
the
readme
has
been
updated
to
remove
the
reference
to
individual
membership
and
move
Liam,
who
is
a
member
not
through
election
but
through
the
individual
membership
role
to
emeritus,
since
that
rule
no
longer
exists
so
just
when
to
give
an
update
on
that
that
has
been
merged,
and
that
brings
us
closer
in
line
to
the
current
state
of
the
world.
B
Cool
the
next
agenda
item
is
at
licenses
to
come,
come
repos,
so
this
is
one
I
opened
up
issue
271
from
a
long
time
ago
brought
up
the
discussion
for
licensing
placing
licensing
repos,
since
this
was
like
relatively
undefined
and
something
we
weren't
maybe
consisted
on
totally.
This
is
from
May,
8th,
April
or
March
8th
2018.
B
We
did
eventually
get
an
answer.
It
did
take
take
a
bit,
but
we
did
get
one
and
we
should
probably
go
through
an
audit,
the
various
calm,
calm
repose
and
make
sure
that
they
are
appropriately
appropriately
licensed
and
if
they
are
not
liked
since
them
appropriately
I,
don't
know
how
that
looks
in
terms
of
like
if
there's
been
a
bunch
of
done
without
a
license,
do
we
have
to
go
through
and
get
every
every
committers
approval
to
merge
that
license.
D
B
G
D
B
So
it's
more,
it's
like,
let's
say:
okay
cool
it.
Nobody
objected
and
it's
like.
We
have
to
get
explicit
approval
if
it's
on
licence
as
far
as
I
know,
so
that's
gonna
be
tricky
and
you
know
if,
if
necessary,
we
can
go
and
delete
those
bits
like.
If
someone
has
an
issue,
we
can
work
with
them
in
good
faith,
but
yeah
it'll
be
challenging
for
sure.
So
it's
just
something
to
to
be
aware
of
in
this.
D
A
This
thing
is
like
what
you
know
if
it's,
what
would
actually
be
reused
from
some
of
these
repos
right,
like
old
issues
of
discussions
and
whatever
I'm,
not
sure,
there's
too
many
people
who
are
like
hey
I
need
to
copy
that
stuff.
I
use
that
stuff.
If
there's
specific
documents
that
people
want
to
pull
and
reuse,
you
know
those
might
be
easier
to
get
the
that.
Can
you
know,
identify
the
contributors
and
get
the
okay
to
add
to
licenses
yeah.
B
B
That's
gonna
be
straightforward
for
us
to
dance
our
on
and
yeah
I
mean
like
if
it's
just
documents,
perhaps
we
don't
need
to
go
down
the
path
of
Licensing
yeah
and
we
can
just
for
future
stuff
kind
of
go
down
the
path
of
always
including
an
MIT
license
it
rather
than
retro
actively
fixing
everything.
That's
totally
solution,
so
yeah.
A
G
A
We're
basically
using
it
to
manage
our
work,
it's
a
little
bit
less
clear
that
it's
a
problem
like
I
I.
We
should
we
want
to
get
into
the
states
so
that
anything
future
just
has
a
license.
Yep
I'm
just
wondering
how
big
a
deal
is
it
for
some
of
these,
so
it'd
be
worth
while
more
more
like,
in
my
mind,
figuring
out
the
ones
that
we
do
think
matter
and
doing
those
first,
this
kind
of
way
yeah.
A
B
That
was
part
of
it.
It's
basically
like
for
most
things,
use
MIT
for
materials,
the
materials
documentation
provided
Beach
to
be
provided
by
users
to
be
provided
to
the
users
UCC
by
4.0
and
for
internal
community
documents
Susan
my
team,
so
yeah
it's
it's
there's
a
full
and
body
dancer
there,
Wow
so
cool
any
other
kind
of
comments
on
that
one
I,
don't
know
if
there's
anything
explicitly
for
us
to
do,
except
for
perhaps
go
and
investigate
that
I.
Don't
know
if
there's
anything
explicitly
that
we
can
do
right
now.
B
B
B
Basically,
my
intent
here
is
to
start
a
new
common
ishutin
on
building
out
small
examples
that
go
beyond
hello
world.
So
like
building
a
CLI
with
no
building,
you
know
XYZ,
you
know,
building
a
web
server
with
FASTA
file
or
building
an
AWS
lambda
function
with
no
js'
right
and
like
getting
kind
of
having
examples
of
how
to
do
all
the
things
that
people
with
noches
would
do
and
you'll
notice
that
the
last
one
was
definitely
very
Bennet's
into
its
link
and
be
the
issue.
B
B
My
intent
is
to
have
a
useful
resource
for
people
that
creates
a
space
where
they
can.
You
know
learn
how
to
do
things
in
the
real
world
rather
than
the
bajillion
Express
hello
world
right,
because
there
are
a
million
of
those
and
there's
very
little
beyond
that.
You
know
in
terms
of
like
going
beyond
that
kind
of
level
of
intricacy
in
tutorials,
so
yeah,
that's!
The
intent
of
this
is
basically
to
build
out
kind
of
a
set
of
a
set
of
resources
to
do
that.
B
So
there
will
be
some
engineering
to
get
around
those
things,
but
that's
work
I'm
happy
to
spend
time
on
and
there
does
seem
to
be
interest
from
a
few
folks.
Already
Tara
and
then
you
know
Blake
and
a
few
other
folks,
a
model
so
I
have
said,
they'd
be
happy
to
help
contribute
some
example.
So
there
have
been
no
objections
and
I
kind
of
started.
B
A
Only
comment
is
there
might
be
some
some
caution
just
around
things
that
use
products
and
the
examples
like
it
like
you
mentioned
a
couple
of
those
like
AWS
and
Google,
like
it's
just
using
express
another
third-party
project
or
G
RPC
or
whatever
I.
Don't
think,
there's
there's
too
much
to
worry
about
once
you
get
into
it
uses
this
specific
offering
from
a
particular
company
mm-hm.
E
A
B
I
see
that's
actually
kind
of
what
I
want
is
I
that
helps
bolster
contributors
to
it
and
like
helps
get
more
examples
of
how
to
do
things
and
the
competitiveness
is
something
that
I
would
very
much
encourage
in
this,
because
it
gets
us
a
larger
set
of
examples
that
are
usable
to
the
ecosystem
and
like
if
it's
a
product
someone's,
probably
using
it,
and
someone
will
want
to
learn
how
to
use
it
and
I.
Don't
see.
A
A
D
F
D
F
F
D
F
You're
saying
is
creating
a
repository
with
with
examples
that
have
like
a
basic
here's,
how
you
shoot
it
up
and
use
it
or
whatever,
and
this
is
what
it
looks
like
with
code
and
all
that,
but
you
know
just
seems
like
another
great
opportunity.
If
there
are
people
willing
to
do
that,
to
write
tutorials
that
go
into
like
you
know,
JSF
dev
or
no
dev
or
whatever
you
know
to
be
able
to
make
that
more
accessible
for
like
fundamental,
you
know,
tutorials
I,
suppose
yeah.
B
Examples
have
their
own
repos
and
those
routes,
our
own
directories
and
then
directories
have
their
own
readings.
They
have
to
be
very
comprehensive
rather
than
like
cool.
Here's.
How
you
do
this
thing
run,
NPM,
start
and
you're
good.
That's
not
I,
don't
think
what
we're
looking
for
in
an
example,
so
yeah
I
also
have
to
run
into
meeting
in
a
few
minutes
but
yeah
so
yeah,
that's
like
I.
Don't
just
want
to
push
code
into
a
repo
and
hope
it
works.
G
B
This
is
an
issue
I
created
I've
created
a
lot
of
these,
so
I
apologize
this
one
specifically
implementing
okay,
ours.
This
was
an
hour
expressing
intent
to
implement
okay,
ours
for
calm
calm
for
those
who
aren't
familiar
okay,
ours,
our
objectives
he
resolved
something
to
initiate.
It
originated
at
Google
and
is
like
a
kind
of
metrics,
tracking
or
measurement
of
goals,
and
if
you
were
able
to
achieve
them
reasonably
or
not
and
yeah,
there's
a
lot
of
context
in
the
issue.
B
We
had
a
session
at
the
collaborators
summit
where
we
sat
down
and
worked
on
some
okay,
ours
and
I
put
the
hack
and
D,
which
is
the
tool
used
to
write
kind
of
collaboratively
right
this
model
into
that
into
that
issue.
So
you
can
see
that
there,
the
first
section
of
objectives
of
brainstorming
is
the
top-level
bullets.
Are
the
objectives
that
we
kind
of
ended
with
the
+1
sub
bullets?
Are
the
people
who
participated?
B
Who
kind
of
said
this
is
probably
a
good
one
for
us
to
go
after,
and
then
you
know
the
the
bullets
under
that
for
each
of
those
top
level
objectives
is
like
the
reasoning
or
thoughts
behind
why
we
wanted
to
go
for
Londyn
kind
of
d
duping
the
other
ideas
into
a
broader
category
and
then
below
that
scaffolding
out
key
results
for
objectives.
The
first
level
bullets
are
again
the
same
same
objectives
as
previous
previously
stated,
and
then
the
key
results
are
the
sub
bullets.
B
So
the
proposed
key
results
are
the
kind
of
things
below,
and
so
we
got
through
the
first
two
as
a
group,
and
then
I
went
through
and
kind
of
worked
on.
The
the
second
two,
independently
with
context
from
I,
believe
him
manok,
who
had
kind
of
added
some
as
well
so
I
kind
of
tried
to
broaden
them
and
make
them
key
results
rather
than
objectives
and
kind
of
go
ahead
and
get
something
together,
and
we
can.
We
can
still
iterate
on
this
I'm
planning
to
PR.
B
Basically,
the
scaffolding
out
key
results
for
objectives
section
as
a
document
and
then
there
you
know
there
are
some
questions
and
additional
context
in
there,
but
this
is
hopefully
something
that
we
can
agree
to.
You
can
kind
of
discuss
a
bit
more.
Like
Joe
said
we
don't
have
that
much
time,
unfortunately,
I'm
sorry,
but
yeah.
This
is
you
know,
hopefully
something
that
the
intent
here
for
this
specific
objectives
and
key
results
section
or
this.
This
document
would
be
to
have
this
income
okay,
ours
and
then
initiatives
themselves
would
align
there.
B
Okay
are
said
they
would
go
through
and
create
their
own
okay,
ours
and
I'm
more
than
happy
to
sit
through
that
process
and
help
them
kind
of
move
that
and
move
toward
doing
that,
but
they
would
create
their
own.
Ok,
ours,
that
somehow
aligned
to
these,
so
that
we
we
can
kind
of
make
sure
we're
all
moving
in
the
same
direction
and
you
know
moving
towards
success
for
the
entire
entire
organization
in
terms
of
compound.
B
D
As
far
as
the
easel
Chara's
go
for
clarity
for
the
initiatives,
is
this
something
that
we'd
like
to
tell
initiatives?
Hey
we're
doing
this
of
the
calm,
calm
level,
and
while
initiatives
typically
have
a
fair
amount
of
autonomy?
Is
this
something
we
want
to
say
hey?
You
should
definitely
do
this.
Will
you'll
give
you
all
the
help
you
want,
but
it's
preferable
to
not
having
these
at
all.
B
F
That
kind
of
thing
is
going
to
be
such
a
healthy
reminder,
moreso
over
and
over
again,
and
so
I
think
in
that
effect
and
I
wasn't
happy
at
collaborative
summit.
So
this
kind
of
stuff
might
have
already
been
all
discussed
and
whatever
I
just
think,
it's
a
really
exciting
time
to
do
this.
Now
you
know
to
have
that
visibility
on
you
know
the
commitments
that
are
you
have
and
seeing
them
through
on
the
quarterly
cycles.
That's
really
awesome.
B
Yeah
and
one
last
thing
I'll
add:
we
are
not
going
to
be
able
to
fish
this
the
agenda
today.
Unfortunately,
all
the
most
thing
I
will
add
there
is
that
this
isn't
like
you
have
to
do
this
thing.
Otherwise,
you
fail.
That's
explicitly
not
the
purpose
of
okay,
ours,
it's
more
okay,
here's
the
goals
we
set
and
then
once
we've
at
the
end
of
our
frame,
which
my
proposal
would
be
next
collaborator
summit
kind
of.
Do
it
a
collaborator
summit,
collaborator
summit
style,
so
we
came
to
find
them
at
collaborator
summits.