►
From YouTube: Node.js User Feedback Initiative Meeting
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
To
you
know
really
look
at
what
what
we're
going
to
accomplish
and
what
we
can't
can
commit
to.
It's.
Probably
the
you
know
the
biggest
thing
cross
initiatives
that
you
know
we
need
to
address.
You
know
one
of
the
interesting
side
effects
about
you
know
doing
good
things.
No
just
project
is
like
it
tends
to
do
positive
things
to
your
career
and
then
you
get
busy
and
then
we,
you
know,
have
to
see
how
to
maintain
the
stuff
that
were
volunteering
and
taking
care
of
here
in
the
project.
A
A
A
You
know
I
picked
a
convenient
time
for
me
and
since
I
was
championing
this
initiative
and
that
that's
why
we
are
this
time
slot
and
you
know
I'd
love
to
hear
from
folks.
If
you
know
if
we
could
move
things
around
and
you
would
be
able
to
do
more
with
user
feedback,
I
would
like
to
you
know
at
least
consider.
C
D
A
A
You
know
some
of
the
sessions
that
we
have
on
Monday
over
the
next
few
weeks,
especially
since
I'm
gonna
be
doing
onboarding
and
stuff
like
that.
So
you
know
that
that'll
be
a
thing.
If
any
of
us
are,
you
know
community,
community
and
other
community
members,
you
know
you
know
the
set
so
cool
that
that's
great
to
hear,
and
you
know
we'll
be
able
to
sort
of
continue
continue
what
we've
been
been
accomplishing,
but
the
user
feedback,
and
do
that
and
you
know
I-
will
likely
be
able
to
lean
even
more
into
to
doing
this.
A
So
you
know
not
not
impacting
any
money.
I
do
this.
Past
week,
I
I
raised
I
said
on
initiative,
everybody
who
is
you
know
currently
you
know
a
member
and
asked
if
any
one
you
needed
wanted
to
Alexis
to
step
down.
You
know
so.
William
khaki
has
you
know,
sort
of
self-identified
that
he
needs
to
move
to
emeritus
status
and
you
know
hasn't
been
able
to
to
to
dedicate
the
time
and
energy
that
he'd
hoped
to
to
this.
A
You
know
taking
that
there's
optical
mics,
because
I
know
Mike
Mike
Hostetler,
for
example,
hasn't
been
able
to
attend
regularly
and
is
that
it's
currently
and
you
know
realistically
no
needs
to
be
the
voluntold
to
move
to
emeritus,
and
you
know
right
now,
I,
don't
believe
we
have
a
formal
process
to
to
be
doing
that.
Yeah.
E
Well,
what
we've
ended
up
doing
in
a
few
other
working
groups
is
basically
it's
a
process
where
we
we
open
an
issue.
Saying
hey,
you
know,
confirm
you,
you
still
want
to
be
active
or
you
know,
move
to
emeritus
and
usually
what
we've
done
is
it's
something
like
you
know?
People
have
two
weeks
to
respond
if
they
done
we
remind
after
another
two
weeks
and
if
there's
no,
so
basically
it's
effectively
after
four
weeks.
E
If
there's
no
response,
we
move
people
to
emeritus,
and
it's
also
been
that,
like
hey,
if
you
come
back
within
the
next
month
and
want
to
say,
hey
wait,
a
second
I
just
was
out
for
a
month.
You
just
get
added
back,
got
it.
So
it's
a
fairly,
you
know
it's
a
fairly
low
bar
in
terms
of
you
know,
if
you're
responding
or
try
or
following
what's
going
on
at
all,
you
should
I,
and
even
if
you
missed
it
for
a
month,
there's
a
way
back.
E
So
it's
not
like
we're
booting
people
out,
but
but
that
has
worked
for
you
know,
I
think
we
did
it
for
benchmarking,
Diagnostics
I'm,
trying
to
think
there's
one
other
one.
We
currently
have
that
going
for
MEP
I
as
well,
so
you
might
want
it
just
if
you
find
what,
if
you
find
the
issue
in
say
diagnostic,
which
is
like
membership
review,
but
in
there
it's
sort
of
the
first
one
basically
says
you
know:
here's
the
here's,
the
process
we're
following.
So
that
would
just
be
my
suggestion.
A
F
A
F
It's
written
to
calm
calm.
We
also
have
a
little
bit
stricter
of
a
process,
but
also
less
strict,
I
generally
reach
out
to
people
to
say
hey
like
do
you
carefully
move
you
to
emeritus,
like
you're
saying
you
know,
reach
out
via
diem
or
something
they
I,
don't
think
anyone
ever
said
no
and
then
you
know
we
also
have
the
I
think
if
you
don't
participate
for
three
months
or
six
months,
you're
just
automatically
moved.
So
it's
like
if
you're
just
totally
inactive.
That's
totally
fine.
F
A
Yeah
I
mean
you
know,
for
me,
it's
largely
it's.
You
know,
figuring
out,
grant
aligning
with
the
expectations
and
the
rules
and
want
to
make
sure
that
that
as
I'm
doing
this,
you
know-
and
you
know,
it'll
likely
be
the
model
for
any
subsequent
actions
right.
So
you
know
in
the
in
this
particular
group,
so
I
want
to
make
sure
that
I'm
sharing
that
great
I'll
I
look
at
the
at
the
docs
a
bit
and
you
know
thank
you
Michael
for
their
the
point:
nurses
in
diagnostic
for
years,
yeah.
E
F
B
E
D
E
E
A
A
Sessions,
you
know-
and
you
know
one
thing
I
noticed
this
year-
you
know
compared
to
last
year-
is
we
I
think
we
dropped
the
ball
a
bit
and
Oreo
the
various
projects
coming
from
Kotler,
so
yeah
I,
just
like
to
sort
of
you
know
note
that,
and
you
know,
as
we're
doing
this
sort
of
you
know.
Second,
second
year
work
flow.
A
You
know
what
one
of
one
of
I
think
a
lot
of
responsibilities
absolutely
are
opportunities
at
the
you
know,
collaborative
summit,
that's
connected
to
our
annual
conference
is
we
have
a
real
opportunity
to
recruit
and
onboard
new
members,
and
you
know
I
I
was
doing
the
other.
The
working
group
and
I
didn't
do
this
there
and
you
know
in
that
session
you
know
doing
mentorship,
I
really
oriented
my
you
know,
discussion
and
content
to
getting
folks
involved,
but
not
to
doing
the
orientation
stuff.
A
Yeah
I
thought
Tierney
two
years
ago
did
a
really
fantastic
job
of
sort
of
providing
an
overview
of
everything
was
going
on
with
with
within
the
community
committee.
So
one
sort
of
you
know
popping
out
popping
the
stack
a
bit
I
think
we
really
need
to
do
a
community
committee
level,
sort
of
triage
and
orientation
at
interactive,
and
then
you
know,
then
we
would
benefit,
even
if,
like
it
was
community
committee-
and
you
know
the
subcommittee's,
you
know
represented
and
initiatives.
A
E
F
F
E
F
E
You
know
it
could
be
that
well,
okay,
if
you
get
really
excited
on
the
first
day,
then
you
can
come
to
the
collaborator
summit,
but
the
club
resume.
It
really
is.
Assumes
you
have
the
context.
You
have
the
knowledge.
You
know
we're
not
going
to
do
upfront
talks
that
are
more
generic.
It's
just
like.
Okay,
let's
get
the
working
groups
together
and
go
from
there.
A
Yeah
I
mean,
as
a
baseline
I,
think
you
know
having
that
that
half-day
that's
after
code
and
learned,
be
you
know,
recruiting
or
new
member
orientation,
focused
I,
think
that's
great
and
yeah
III
think
tyranny
was
hitting
it
like
wow.
Today's
you
know
on
that
would
be
a
lot,
but
it
would
but
it's
not
right.
It's
there,
those
those
we
seem
to
really
sink
our
teeth
into
whatever
issues
we
yeah
I
had
the
opportunity
to
to
focus
on
during
collaborate
summit.
A
E
A
Now
I
think
we're
building
we're
building
that
experience
and
you
know
kind
of
the
off
the
off
session,
which
is
just
collaboration
and
so
I
think
that,
since
you
know,
you
know
Matteo
and
I
organized
the
other
one
we
were,
you
know
really
layering
back
in
a
lot
of
the
successes
of
what
we
did
in
Berlin
and
you
know
kind
of
you
know
just
applied
that
to
the
half-day
was
like
all
right.
Let's
do
fill
in
the
half-day
with
that.
A
Yeah
I've,
never
I've,
never
seen
collaborative
community
contributor
days
in
action,
but
yeah
I
mean
I,
helped
some
folks
in
the
Drupal
community
kind
of
orient
themselves
to
node
recently-
and
you
know,
one
of
the
things
that
that
community
has
done
very
effectively
is:
is
documentation
sprints
right,
something
that
we
don't
as
a
community
do,
but
we've
kind
of
been
circling
around
you
know,
doc
sprints
would
would
be
a
great
activity.
To
sort
of
you
know
collaborated
the
edges
with
folks
right
these.
A
A
F
A
B
A
A
Grumble
grumble
grumble,
so
it
was
really
nice
to
get.
You
know.
The
online
session
on
Meetup
I
got
flagged
almost
immediately
as
being
an
online
session
and
I
tried
to
you
know
to
work
around
it,
but
meetups
being
really
aggressive
right
now
about
a
meet-up.
You
know
somehow
means
that
you're
meeting
in
person
you
know
and
if
you're
not,
then
it
doesn't
apply
to
me
calm,
that's
a
new
post.
We
work
a
position
there
are
there
any
competitors.
A
The
crowd
cast
gets
a
little
bit
spendy,
you
know
once
you
get
over
a
certain
threshold.
We
are
above
that
threshold.
Yet,
but
you
know,
I
could
definitely
see
us.
You
know
tapping
eating
that
ceiling.
What's
the
threshold
I
think
it's
like
a
hundred
users
hundred
participants
that
will
get
you
into
like
a
ninety
bucks
a
month
price
points.
Okay,
so.
F
F
A
So
crowdcast
solves
a
very
different
problem.
The
reason
why
I
love
meetup
in
terms
of
its
functionality
is
it
provides
a
central
like
folks,
join
a
meet-up
and
then
meetup
does
a
great
job
of
engaging
and
notifying
everybody
about
every
meetup
that
that
you,
you
know
published.
That
is
every
meeting
that
you
ever
published
is
associated
with
that
Meetup
and
it's
it
just
snowballs
over
time.
You
know
the
folks
that
are
subscribed
and
engaged
they're,
just
no
balls
and
that
works
really
well.
A
E
B
For
what
it's
worth
dan,
like
the
the
very
thing
that
you
love
about
meetup,
is
the
thing
I
hate
about
it
so
pushy
with
the
emails,
and
it's
really
hard
to
you-
have
to
like
there's
like
50,
different
checkboxes
to
unsubscribe
or
any
given
meetup
that
you
join,
and
you
can't
just
like.
Do
a
uncheck
all
got
and
it's
it's.
So
it's
so
much!
There's
a
lot
of
pain
involved
there
and
you
know
the
thing
that
I
like
about
meetup
is
I
mean
it's
just
that
people
use
it.
B
E
A
So
what
you
know,
one
of
the
the
goals
turning
turning
them
back
to
some
of
the.
Why
of
meet
up?
One
of
our
goals
with
you
know,
engaging
general
user
is
breaking
out
of
you
know:
Twitter
our
collective
Twitter's
and
github
to
get
in
front
of
you
know
broader
user
base,
and
you
know
honestly
to
reduce
the
the
burden
of
doing
so
to
us
as
low
a
threshold
as
possible.
A
A
A
A
A
E
E
A
D
But
the
thing
I
want
to
ask
like
what
is
it
in
the
group
mechanic
that
we
want
to
surface
here
like?
Is
it
coming
back
to
the
point
like?
Is
it
just
email
being
able
to
email
people
into
the
mode,
but
there's
something
happening,
because
if
that's
really
the
mechanism,
then
it's
just
a
newsletter
at
that
point.
Well,.
E
E
You
know
that
whole
thing
about
hey,
I,
see,
there's
50
other
people
going,
oh
I,
better,
not
lose
at
my
spot,
and
you
know
those
kinds
of
things
do
give
a
little
bit
more
of
like
a
group
feeling
and
I
think
you
know,
Dan's
are
they're
coming
about
being
regular,
like
I
I
get
a
regular
email
every
month
to
my
local
JavaScript
meetup
right,
and
it
makes
me
a
little
bit
more
likely
that
I'm
actually
gonna
go.
This
is
like
I
feel
guilty
that
I
didn't
go
this
month
right.
So
the.
E
E
D
Just
trying
to
distill
down
like
the
core
things
that
we're
trying
to
surface
here
by
asking
these
questions,
given
them,
it's
not
so
much
like
a
newsletter
per
se,
but
it's
like
a
campaign.
Automation,
perhaps,
and
if
you
looked
at
streaming,
solutions
like
you
can
get
to
the
point
of
perhaps
streaming
on,
I,
don't
know
like
Twitter
if
you
want,
but
it's
the
check
in
and
RSVP
mechanism,
yeah
the
event
type
RSVP,
but
more
of
a
check-in
time.
D
D
A
E
A
E
A
D
Miss
interesting
because
they
do
have
webinars
and
webinars
are
things
that
you
schedule
and
sign
up
for
behavior
of
I'm
opting
in
it
doesn't
take
it
slowly
all
the
way,
but
then
that's
where
you
can
like
hook
in
something
like
campaign.
Mother
or
you
know,
whatever
the
other
thing
from
MailChimp
is
called
where
you
can
just
do,
triggered
based
events
for
emails
so
like
if
somebody
says
RSVP,
you
send
them
an
email,
and
then
you
send
them
a
reminder.
E
E
D
F
A
B
E
A
E
Have
a
banner-
and
we
could
use
the
banner
to
announce
things
and
stuff,
but,
like
you
can
see
the
you
know,
but
we
have
the
sign
up
for
the
noches
everywhere.
We
could
also
have
like
a
regular
here's.
You
know
sign
up
for
the
next
nodejs
user
feedback
or
you
know,
then
next
no
GS
meet
up
virtual
meet
up
or
something
that
might
be.
The
thing
is,
if
they're
already
coming
to
the
nodejs
website,
does
that
getting
us
outside
of
our
like
the
goal
was
to
get
inside
of
our
regular
areas
right.
A
F
A
F
F
E
A
I
think
that
you
know
given
the
attendance
last
time,
which
was
you
know,
middling
we
we
would
want
to
do
two
things.
First,
let's
define
whatever
content
that
we're
gonna
do
and
finalize
that
for
any
announcement
for
any
dates
like
let's
build,
you
know
what
the
next
event
is
and
then
I
would
like
to
see
in
this
next
iteration.
You
know
kind
of
how
how
big
we
can
do.
A
A
A
To
promote
it
will
will
draw
in,
but
you
know,
take
some
content
this
time.
That's
not
just
core
yeah
and
you
know
sort
of
model
having
a
user
share
some
of
their
experience,
so
we're
drawing
on
that
that
experience
we've
had
you
know
Walmart
in
the
past.
You
know,
maybe,
if
folks
have
a
proposal
of
oh.
This
is
a
really
interesting
use
case
for
a
node
that
folks
haven't
heard.
A
You
know
we'd,
like
I'd
like
to
explore
that
I
really
enjoyed
the
American
Express
presentation
at
the
American
Express
team
presentation
at
interactive
I
thought
they
did
a
wonderful
job,
sort
of
sharing
their
sack
and
their
challenges
where
you're
working
in
financial
services-
and
you
know
so
you
know
that
if
you
have
a
chance
to
poke
through
this,
all
the
videos
are
online.
Now,
if
you
have
a
chance
to
poke
through
those
videos,
I
highly
recommend
that
good
sort
of
overview
of
you
know
a
user
experience.
A
B
I
I'm
not
sure.
Well,
you
know
III
talked
about
this
with
the
group
at
the
club
summit
and
basically
we
decided
to
table
that
for
now.
We
certainly
have
plenty
of
things
to
do
for
now,
like
there's
stuff
that
needs
to
get
done.
We
have
quite
a
few
things.
Actually,
we've
you
know
come
up
with
already
from
the
feedback
we've
gathered
here.
B
So
you
know,
I
would
expect
to
want
to
do
another
one
at
some
point.
I,
don't
know
if
it's
going
to
be
like
a
regular
occurrence,
I'm
gonna
guess
not,
but
I
can't
say
quite
yet.
If,
if
you
know
we
want
to
move
that
the
whole
effort
back
into
that
group,
because
certainly
if
you
know
you're
working
with
these
meeting
sites
or
whatever
you
know,
right
is
a
resource
that
we'd
also
need
to
consume.
B
If
we
want
to
get
the
word
out
and
get
people
to
actually
join
us,
so
at
that
level,
that's
you
know
we
want
to
at
least
keep
tabs
on.
What's
going
on
and
and
hopefully
like,
that
is
something
we
can
open
up
to
other
groups
that
that
need
it
or
want
to
want
to
use
it,
but
yeah,
that's
kind
of
where
we
stand.
Okay,
cool.
A
Yeah
that
works
for
me,
I'm,
happy
to
you
know
continue.
You
know
just
asking
I
guess
you
know
on
my
end
is
important
to
consider.
That's
y'all
are
just
getting
started
and
you
know
so
you
don't
know
what
you
need
yet
right
or
what
what's
our
outreach
until
you,
you
know
continue
so
the
process
of
coalescing
that
group
and
seeing
those
needs
so
yeah.
It's
probably
you
know
too
early
to
determine
you.
B
D
Yeah
I
think
probably
still
need
to
be
a
few
more
kind
of
tweaks
before
we
can
talk
about
like
how
did
that
help
that
evolved.
I
would
like
to
keep
that
as
part
of
the
user
feedback
group.
D
So,
whatever
lessons
come
out
of,
you
know
this.
This
conversation
we
just
had
either,
though
we
can
replicate,
or
we
can
make
a
kind
of
a
little
corner
of
it-
that
we
can
add
these
people
to
without
the
without
it
becoming
a
point
of
spam
and
noise
to
them
as
those
folks
who
will
be
part
of
those
enterprises-
and
you
know-
let's
say
you
know,
a
new
companies
like
yours
in
the
future
might
be
interested
in
helping
out.
D
They
don't
want
to
be
overwhelmed
by
either,
but
I
think
that
could
be
as
simple
as
a
newsletter
in
a
call
to
action
every
once
in
a
while
when
needed,
and
we
want
to
do
like
these
kind
of
meetings.
Then
it's
a
it's
a
personal
invite
that
works
best
to
get
these
people
to
actually
give
us
their
time,
because
that
time
is
very
valuable.
D
E
A
F
Using
other
existing
art
is
probably
gonna,
be
less
work
for
us.
In
a
long
run,
it's
gonna
be
most
beneficial
because
that
already
has
like
I,
think
seven
thousand
emails
that
it
goes
up
to
addresses
that
it
goes
out
to,
and
it
would
I
mean
we
can
send
out
a
different
email.
If
we
want
to
create
our
own,
we
can
send
it
to
the
list
and
we
don't
have
to
spin
up
our
own
infrastructure
for
it,
but
I
think
it'd
be
beneficial.
A
I,
don't
think
they're
mutually
exclusive,
though
so
like.
If
we
did
commit
to
you,
know
letting
everybody
know
through
through
know
just
everywhere.
What's
going
on
and
then
spun
up
you
know
quit.
Do
you
think
that
the
the
Enterprise
Group
would
only
want
to
hear
from
their
focus
area
or
I?
Don't
think
we
could?
You
know
we
could
do
like
three,
your
general
and
tooling
and
enterprise.
It
seems
like
overkill,
but
maybe
if
we
you
just
started
with
you
know
with
Enterprise.
D
I'm
just
saying
it's
not
not
the
point
of
view
is
not
about
what
the
what
the
individuals
and
the
group
would
want,
but
more
so,
what's
more
of
a
benefit
for
the
let's
say
the
the
Technical
Committee
that
they
want
to
get
action
out
of
it's
more
for
the
benefit
to
keep
it
less
of
a
group
that
people
just
subscribe
to
and
sign
up
for
more
of
a
we
have
an
action.
Let's
say:
there's
a
conference
coming
up,
there's
a
new
release
coming
up
yeah
make
it
more
kind
of
like
event-driven.
A
D
So
my
next
action
is
I
want
to
schedule
another
kind
of
community
meeting
for
the
enterprise
group
and
but
as
a
requirement
for
that
I
think
like
having
that
email,
signup,
slash,
newsletter,
slash
method
of
communication
beyond
just
me
sending
emails
to
individuals,
so
people
can
opt
in
to
that
conversation
and
then
we
can
make
it
easier
for
follow-ups,
especially
as
we
want
to
start
asking
for
the
different
working
groups.
What
actions
they
might
want
to
surface,
whether
it's
a
survey
or
an
engagement
of
some
sort.
So
we
can
make
it
more
structured.
D
F
F
D
Doesn't
have
to
be
a
infrastructure,
it
just
has
to
be
something
separate
than
public
groups.
So
here's
a
workflow
if
it's
coming
from
enterprise
at
no
genius
that
org
or
something
similar.
That
would
like
this
thing
distinction
for
somebody
to
look
in
their
inbox.
They
know
that
this
is
something
to
look
after
and
we
can
add
people
annually
to
it.
But
as
long
as
we're
able
to
trigger
that
communication
through
a
centralized
thing
and
again
it
can
be
manual
doesn't
have
to
be
something
people
sign
up
on
a
website
or
anything
right.
B
E
F
Every
day
have
their
own
marketing
automation
stuff,
and
it's
it's
relatively
automated,
and
there
is
the
I
mean
if
you're
doing
it
manually
like
if
you're
manually,
I
think
emails.
It
shouldn't
be
a
problem,
but
if
we
want
to
move
away
from
a
neo,
we'll
have
to
also
be
careful
about
gdpr,
which
they
handle
very
carefully.
So
that's.
C
E
A
D
I'm
just
to
structure
it
better
like
to
your
point
about
gdpr
and
other
things,
I
mean
it
may
not
cover
GTR,
but
we
probably
want
to
have
a
process
in
which,
when
we,
we
announced
all
the
working
groups
that
if
you
have
something
to
ask
or
do
leverage
the
enterprise
connections
that
we
have.
What
does
the
Megane
mechanism
to
do
that?
So
we
maybe
we
can
have
a
part
of
the
github
repo
or
issues
our
label,
that
people
can
say
hey.
E
E
All
right
so
basically
I
mean
we
had
at
least
one
Twitter
conversation
where
somebody
was
saying
things
were
avast's
I'm
having
trouble
updating
to
no
ten,
and
so
we
thought
it
actually
would
be
useful
to
gather
that
kind
of
user
feedback
in
terms
of
like
hey,
it's
a
perfect
time
we're
telling
people
to
upgrade
to
ten.
So
if
you're,
having
having
problems,
you
know
and
user
feedback
when
I
talked
to
Mateo
seemed
like
a
simple
place
to
collect
that
right.
A
D
I,
just
have
a
thought
about
that.
Yes,
sorry,
just
pizza
delivery-
and
this
relates
to
our
previous
conversation
as
well,
seeing
how
the
NPM
team
shut
down
their
issues
I
could
help,
because
that
was
the
behavior.
Was
you
like
user
feedback
and
show
obviously
bug
reports,
but
a
lot
of
you
know
hey
how
do
I
do
X
or
what's
best
practice
on
why
they
shut
that
down
and
they
opened
up
a
discord,
I
think
what
it
de
or
is
it
a
discourse?
It's
a
forum
yep.
D
D
D
It's
like
NPM
dog
community,
so
that
acts
as
their
authentication
for
users,
people
sign
up
there.
It
could
act
as
a
communication
mechanism,
I'm,
not
sure
for
announcements
and
community
type
events.
So
you
can
it's
a
forum
at
the
end
of
the
day,
but
he
can
shape
it
to
behave,
however,
which
way
you
want.
I
can
have
like
events
on
there
and
notify
people
of
things.
D
It
just
occurred
to
me
right
now.
They
can
also
use
a
forum
for
the
same
topic
that
we
discussed
previously
and
as
we're
talking
about
now
for
user
feedback.
That's
probably
a
better
mechanism
for
collecting
user
feedback,
keeping
things
open
and
people
can
help
each
other,
but
then
monitor,
attend
and
collect
data
and
output.
E
Right
so
you're
suggesting
we
open
up
another
like
we've,
had
lots
and
lots
of
discussions
around
using
different.
F
E
E
G
A
D
E
A
E
A
You
know
this
this
point
specifically,
you
know
to
kick
off
this
process.
Absolutely
not!
Please,
please
feel
free
and
you
know
I
think
it's
a
great
opportunity
to
you
know
to
look
at
these
these
moments
in
time
like
the
LTS
release,
and
you
know
what
sorts
of
things
we
can
be
doing
to
support
other
things
that
are
happening.
The
project
I
deeply
appreciate
Matteo,
for
you
know,
choosing
to
do
that
with
us
and
I.
Think
that's
something
that
that
I
I
personally
love
to
see
they
see
more.
A
E
A
F
A
F
Their
problem
was
actually
not
around
no
tenon,
no
date
streams,
but
more
around.
You
know
they're
having
their
own
problems,
and
then
they
were
had
a
reaffirm,
a
information,
a
reaffirmation
that
you
know
things
work
perfectly
great,
and
so
it's
you
know,
I'm
glad.
We
kind
of
captured
that
or
I
engage
with
it
and
then
pulled
in
a
few
people,
and
you
know
I'm
happy
to
see
that
we're
having
some
user
feedback
actions
like
that
was
my
hope
for
it.
So
it
worked
great.