►
From YouTube: NixOS Marketing Team Meeting #10, 2020 08 05
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
Welcome
to
the
10th
marketing
meeting
as
always,
keep
the
open
minded,
let's
it's
okay
to
disagree,
but
it's
important
to
listen
to
each
other,
so
I'm
gonna
share.
I
should
have
shared
this
already
before,
but
I'm
gonna
start
sharing
actually
the
whole
window.
A
The
whole
screen,
if
that's
even
possible,
yeah
because
we'll
be
doing
some
more
interesting
things,
but
there
we
go
so
today
on
the
agenda
I'll
make
it
a
bit
bigger.
So
it's
readable
I
would
just
like.
So
I
think
I
added
this
from
the
previous
meeting
notes,
but
it
was
kind
of
tight
to
samuel
and
maybe
it
slipped
to
our.
B
B
A
Okay,
I
think
I
forgot
the
name,
but
we
receive
also
the
email
what's
happening
to
the
webmaster
mixers.org,
so
I'm
gonna
forward
you,
the
email
and
you
can
take
it
from
there-
sounds
good
all
right,
awesome,
okay,
so
the
next
item
is
update
on
a
redesign.
So,
as
you
know
a
week
before,
we
started
to
work
on
a
redesign,
we
hired,
we
hired
a
designer
most
of
us
on
this
call.
We
already
seen
it,
but
it's
maybe
more
important
to
just
like
quickly
go
through
it.
I
will
time
myself
to
be
below
five.
A
Minutes
so,
and
without
so
to
kind
of
explain
it
so
the
redesign,
so
we
are
halfway
through
the
redesign,
but
we
you
can
already
see
what
the
direction
that
we're
going
somewhere
already
started
on
the
implementation
part.
So
by
the
next
meeting
we
should
be
pretty
far.
A
I
will
include
all
the
links
where
help
is
needed
and
when
help
is
needed
in
the
in
the
meeting
minutes,
but
for
now,
let's
just
go
quickly
through
it,
so
this
is
kind
of
the
color
scheme
and
the
two
types
of
fun
on
the
black
and
on
the
light
and
dark
kind
of
the
sizes
in
comparison
yeah.
The
all
these
links
for
the
to
for
to
this
pdf
will
be
available
in
the
mar
in
the
minute.
A
So
we
can
see
them,
then
we
have
few
options:
how
to
do
our
top
navigation,
so
nothing
from
this
was
actually
chosen.
Yet
once
we
will
do
implementation,
we
will
simply
try
and
see
what
fits
best
and
also
in
our
as
we
work
with
the
designer.
A
We
are
just
like
testing
different
options
as
well
as
we
go,
and
so
far,
if
I'm
not
mistaken,
we
already
have
like
four
meetings
with
the
designer
every
second
day,
so
it's
progressing
pretty
fast.
So
so
this
is
the
navigation
bar
a
few
options.
I
think,
like
six,
seven,
eight
nine
options
below
that
comes
the
we
call.
This
cover
cover
box
like
where
we
have
our
video
and
our
slogan.
A
So
a
bit
darker,
I'm
not
sure
if
it's
visible
on
the
recording,
but
there
is
some
kind
of
a
logo,
is
also
visible
in
the
background
and
when
you
click
on
the
video
it
will
pop
out
and
start
playing.
A
So
this
next
one
below
the
cover
area,
we
have
like
three
boxes
where
we
explain
why
to
use
white
to
choose
nyx
or
nexia.
A
A
This
is
also
an
example
of
with
the
sliding.
Next
we
have
a
search
box,
so
the
search
area.
The
important
thing
to
note
here
we
have
this-
I
don't
know
how
to
call
this,
but
let's
say
this:
l
design,
which
this
theme
will
be
throughout
the
website,
will
be
visible.
You
will
see
some
other
examples
later
on,
but
this
kind
of
comes
from
the
mix
logo.
So
it's
kind
of
reusing
the
effort.
A
Next
comes
our
examples,
so
we
will
do
similarly
as
our
video
in
the
top.
We
will
convert
them
to
those
ascii
cinema
videos
and
when
you
click
on
them,
they
will
start
playing
in
a
bigger
format.
We
will
show
three
videos
either
in.
A
Sorry,
either
in
this
layout,
above
or
in
this
layout
above
and
below,
we
will
list
as
much
as
example,
as
we
think
is
still
needed
on
the
front
page.
So
this
is
all
about
the
landing
page.
A
It's
the
logo.
What
else
this
is
kind
of
the
example
how
one
of
the
examples
when
things
fit
together.
A
So
nothing
here
is
set
in
stone,
but
we
are
ex.
We
are
experimenting
and
we'll
experiment
with
this,
even
during
the
implementation
phase.
So
when
we
are
writing
css
and
html.
A
This
is
an
example
of
this
special
announcement,
so
when
there
is
a
new
release
coming
or
a
conference
coming-
and
things
like
this,
so
we
could
use
this
or
maybe
when
there
is
a
community
survey
survey
and
we
expect
everybody
to
answer
it.
So
this
is
one
of
the.
A
This
is
the
search
again,
the
different
format.
These
are
the
footers
different
colors,
but
layout
is
kind
of
the
same
again.
Another
selection
of
how
to
put
things
together
with
different
colors.
C
A
Let
me
just
see,
maybe
there's
something
interesting
yeah
there
is
for
the
download
page
some
items.
Maybe
this
is
the
most
how
the
top
elements
might
fit
together.
So
we
can
get
the.
A
Idea
how
things
will
look
at
the
end,
yeah,
okay,
this
was
shortly
looking
at
the
redesign.
Are
there
any
comments
from
anybody?
You
mostly
seen
this,
but
there
are
a
few
other
pages
that
we
redesigned,
but
we
will
kind
of
include
them
in
the
next
meeting.
Also
in
the
implementation.
B
Well,
the
timeline,
I
don't
have
a
timeline
ready,
but
already
the
header
and
the
footer
for
the
wide
version
of
the
site.
Not
the
narrow
version
are
mostly
done
just
choosing
the
the
theme
so
the
either
either
dark
or
light
colors
everything
is
done
in
a
way
we
can
choose
on
the
fly.
B
It's
all
configurable,
so
I
guess
coming
from
there
up
to
the
end
of
this
week,
most
graphical
elements
shown
and
produced
for
this
new
design
is
going
to
be
implemented,
so
we
have
different.
B
B
A
Okay,
so
we
will
work
with
updating
the
content
and
bringing
design
in,
but
we
will
have
more
results,
I
suppose
by
the
next
meeting,
which
is
in
two
weeks.
A
I
hope
so
yeah
yeah,
I
mean
it's
as
we
have
time.
I
mean
this
is
on
a
voluntary
basis,
but
everything
so
far
looks
good
and
I'm
really
happy
that.
I
think
it
took
us
now
a
week
or
it
was
a
bit
more
than
a
week
to
get
where
we
are
and
yeah.
A
We
need
a
few
more
days
with
the
designer
and
kind
of
designs
will
be,
or
the
idea
of
the
design
will
be
there
and
then
we'll
just
use
it
we'll
use
him
for
how
they
call
this
on
for
certain
special
cases
which
we
need
to
design
icons
and
things
like
that.
C
A
Well,
the
manual
is
also
going
to
be
designed,
but,
like
the
current
manual
like
we're,
just
gonna
make
the
spacing
correct
and
everything,
but
for
the
new
we
can
again
re-hire,
because
it's
just
going
to
be
using
the
same
elements
and
maybe
adding
and
adjusting
it
to
fit
the
current
design.
A
I
mean
I
already
talked
to
him
and
he
said
like
yeah.
Whenever
that
comes,
you
can
just
thank
him
and
he'll
be
more
than
happy
to
help
us.
I
hope
to
bring
him
on
this
call
at
least
next
time,
or
maybe
even
after
that,
when
the
the
website
is
done,
so
that
we
know
that
who
actually
did
it
right
who
helped
us.
So
this
is
about
the
redesign
kind
of
feedback.
A
Welcome,
although
it's
a
bit
too
soon,
we
have
not
yet
anything
really
to
show,
but
by
next
time
we
will
have
and
then
the
feedback
more
than
welcome,
especially
I
assume
we
will
need
a
lot
of
help
from
everybody
testing
this,
that
it
looks
proper
on
all
devices.
A
A
Going
once
twice,
okay,
so
the
the
next
topic,
which
I
hope
we
will
actually
will
be
a
bit
more
elaborate
conversation
is
so
the
the
test
I
was
working
on
is
actually
rewriting
how
we
talk
about
nics,
which
kind
of
translates
rewriting
what
we
have
on
features
page
and
so
far.
A
I
covered
most
of
the
features
that
we
kind
of
present
there
and
I
tried
to
turn
it
around.
So
instead
of
talking
about
the
features
I
wanted
to
bring
it
closer
to
our
audience
that
we
selected
I'll
repeat
what
our
audience
is
a
bit
later,
but
instead
of
talking
about
the
features,
for
example,
we
are
reproducible
right.
This
would
be
a
feature
or
nix's.
C
A
Atomic
upgrades
are
a
feature,
but
rather
than
this
we
we
should
talk
about
the
benefits
of
this
right,
because
in
this
way
the
our
audience
will
should
connect
and
understand
what
neet
is
about
and
is
it
is
nix
or
nixon
for
them
our
audience.
I
think
that
should
actually
start
with.
This
is
on
the
website.
I'm
talking
now
right.
A
Our
audience
are
newcomers
tunics
and
are
kind
of
managers
or
decision
makers
who
want
to
just
evaluate
whether
nix
is
something
they
should
they
should
introduce
to
their
team
or
it's
okay
to
use
in
in
the
team,
so
they
are
kind
of
two.
These
are
our
kind
of
the
primary
targets
that
that
we're
targeting
with
this
features
page,
how
features
page
is
currently
written
is
written
for
us
or
to
kind
of
compare
it
with
I
mean
it's.
A
A
Now
not
everything
is
going
to
be.
Like
I
skipped
a
part
of
the
comment,
but
you
can
imagine
that
there
are
sections
each
on
each
feature
or
I
think
we
want
to
say.
A
What
what
is
really
hard
to
strike
with
english
is,
I
don't
want
us
to
be
too
looking
too
fake
with
marketing.
You
know
kind
of
lying,
and
this
is
a
nice
example
what
I
don't
want
to
do,
but
I
included
it
nevertheless,
like
the
sky's
the
limit,
this
is
already
going
over
the
the
the
border,
which
I
would
call,
but
I
want
to
be
honest
right
and
a
nice
example
is
stop
looking
for
what
you're
missing.
A
Let
nick's
remind
you,
so
this
is
trying
to
talk
about
complete
dependencies
now
we
are
not
mentioning
directly
complete
dependencies,
but
we
will
so
if
you
can
imagine
in
the
design
wise,
this
still
hasn't
been
designed,
but
you
can
imagine
there
is
going
to
be
some
art
that
will
show
a
complete
dependency
graph
and
something
is
missing
or
maybe
nothing
is
missing
with
next
right.
So
this
will
be
kind
of
the
art.
Then
it
gets
a
bit
bigger
kind
of
like
a
small
2-3
sentence
area
where
we
will
still
use
this.
A
We'll
still
talk
about
benefits
and
it's
going
to
be
a
bit
bigger
text
below
that
it's
going
to
be.
This
is
still
kind
of
trying
to
lure
him
to
understand
what
this
feature
is
about,
and
only
then
we
will
kind
of
explain
the
feature
in
a
similar
fashion
that
it's
now
right
so
either
is
this
going
to
be
in
a
somehow
collapsible
way?
I'm
not
sure
we
need
to
see.
Maybe
not,
I
think,
that's
not
a
good
option
but
yeah.
A
Okay,
so
should
I
just
go
by
the
titles
and
then
I'll
read
it
once
because
it's
not
that
much
and
then
we
can
kind
of
have
a
round
so
complete
dependencies
feature.
They
are
not
in
any
particular
order.
That's
also.
We
can
then
reward
them.
What's
more
important,
stop
looking
for!
What's
missing,
let
nix
remind
you,
make
sure
nothing
gets
left
behind
and
reduce,
reduce
the
risk
of
incomplete
dependency,
stop
worrying
if
all
dependencies
are
in
order.
A
Let
nix
remind
you
about
the
missing
pieces,
and
then
you
know
why
complete
dependencies,
if
you
open
the
features
page
and
scroll
down
to
complete
dependencies,
we
will
include
a
bit
more
technical
detail
explaining
how
complete
dependencies
work
and
why
it's
important
going
further.
This
is
the
most.
A
Maybe
we
should
discuss
each
item
individually.
That
just
came
to
my
mind,
probably
yeah,
probably
okay,.
A
A
A
This
clearly
needs
to
be
changed,
but
completely
customizable
built
to
get
the
power
to
adjust
any
part
of
the
built
environment.
All
changes
are
transparent
and
nyx
keeps
it
that
way.
So
kind
of
this
is
the
worst
section,
actually
that
it's
here
and
it
doesn't
really
show
the
benefit
yet,
but
all
ideas
are
welcome.
I
will
later
share
this
document
or
actually
I
will
already
share
it
on
the
chat,
so
you
can
actually.
A
Oh,
but
then
I
need
to
add
old
emails
I'll
do
it
afterwards.
Just
so,
I
don't
disclose
any
personal
details,
okay,
so
patches,
then
it's
multiple
development
environments,
no
club,
no
conflicts
with
operating
systems.
This
is
kind
of
explaining
here
like
explaining
that
everything
is
explaining,
basically
the
next
story
and
how
the
hashing
works
and
all
of
this
so
securely
in
style
software,
with
no
risk
of
breaking
anything
down.
Nix
prevents
cufflinks
not
only
between
multiple
environments,
but
also
with
the
operating
system.
A
All
packages
remain
in
style,
installed,
side
by
side,
even
if
different
users
install
packages
with
the
same
dependencies,
so
kind
of
this
touch
is
also
the
multi-user
but
more.
The
the
feature
that
I
want
to
kind
of
get
here
is
the
can
explain
afterwards
how
the
next
door
works
and
why
there
is
no
conflicts
between
this
important
thing.
I
this
is
kind
of
between
multiple
environments,
so
this
is
because
people
will
have
multiple
development
environments
and
they
usually
the
question
asks:
how
does
this
work
with
the
operating
system?
A
A
This
way
is
the
right
word,
especially
if
you
look
at
the
the
history,
why
we
call
it
atomic
upgrades,
like
the
the
reason
behind
the
atomic
but
yeah
to
eliminate
the
risk
of
leaving
any
parts
behind
all
operations
are
atomic
nick
sets
everything
in
place
and
once
ready,
there
are
only
two
possible
outcomes:
upgrade
was
successful
or
upgrade
did
not
happen,
so
I
think
kind
of
this
statement
at
the
end
kind
of
made
it
like
either
it
happens
or
not
atomic
right,
and
then
we
explain
how
this
works.
A
I
think
there
are
two
more
three
more
three
two
more
so
kind
of
profiles:
generations,
garbage
collection.
Why
we
can
is
the
previous
version
better
question
mark
roll
back
anytime
packages
are
never
overwritten
and
the
old
versions
are
always
stored,
roll
back
to
any
previous
version
within
milliseconds.
A
Yes,
again
with
the
trustworthy
atomic
operation,
we
could
actually
here
replace
it
with
instant.
We
can
have
discussion
a
bit
later
why
this
is,
I
think,
it's
important,
but
maybe
it's
actually
not
so
we
can
just
have
atomic
here
as
well.
So
multiple
kind
of
features
here
talking
about
profile
generations,
garbage
collection,
because
we
need
to
mention
how
to
get
rid
of
the
all
generations.
A
Please
be
carefree,
develop
with
no
limits.
I
find
this.
The
this
is
our.
This
is
talking
about
reproducibility
and
the
word
carefree,
and
actually
the
sentence
or
the
phrase
be
carefree,
is
actually
a
really
catchy,
but
the
more
I
read
it,
the
more.
It
sticks
to
me
that
this
is
the
reason
for
reproducibility.
A
Yes,
there
are
other
benefits,
but,
like
I
think
this
will
speak
to
the
most
users.
Only
my
opinion
right
so
gives
you
the
power
to
build
and
deploy
software
consistently
on
different
machines.
Save
time
be
carefree
and
roll
back
any
time
to
previous
versions.
Next,
we'll
make
sure
all
dependencies
are
in
place,
as
you
can
see,
we're
talking
about
multiple,
also
multiple
features,
but
I
think
this
is
the
most
important
save
time
be
carefree,
and
then
it
explains.
Why
is
why
this
is
the
case?
A
A
Because
I'm
not
seeing
the
the
faces,
because
I'm
sharing
the
full
screen.
C
I
think
the
the
header
being
carefully
developed
with
no
limits
is
it
yeah,
it
doesn't
yeah,
I
don't
know,
and
then
it
says
reproducibility,
but
you
could
also
say
that
that's
about
the
ability
to
roll
back.
A
Yeah
yeah:
well,
it
is,
although
the
the
target
was
more
reproducibility
so
where
the
role
that
came
here
is
because
you
know
save
time
be
carefree
because
yeah
yeah
you're
right,
it's
a
bit.
A
A
Yeah,
okay,
I'll
just
give
it
this.
C
And
with
no
limits
it's
a
bit,
I
mean
you
could
say
that
about.
This
is
sort
of
a
general
thing
aspiration.
A
A
Okay,
so
this
is.
It
talks
a
bit
about
multiple
points,
so
this
language
agnostic
will,
we
will
add
it
a
bit
later
so
until
next
time
is
previous
version,
better
roll
back
anytime
and
then
the
rest.
C
Yeah,
not
not
the
reproducibility
part
with
the
experiment
safely,
part.
B
C
A
Yeah
yeah,
but
I
think
here
we
kind
of
go
the
kind
of
this
fearless
experimentation,
fearless
experimentation,
so
kind
of
saving
the
time
that
would
be
the
reproducible
part
in
nix.
That's
the
reason.
That's
the
selling
point.
At
least
this
is
the
one
I
could.
I
think.
C
A
We
might
even
have
a
like
like
from
a
strip.
You
know
where
it's
it's
a
developer.
It
works
on
my
machine,
another
developer.
Now
it
works
on
all
machines.
A
You
know,
you
know
what
I
mean
and
yeah,
so
we've
been
strikeout
exactly
yeah,
so
we
can
be
smart
about
with
the
design.
We
can
tell
also
a
lot
like
this
or
catch
phrases.
Is
it
okay?
If
we
go
further
yep,
okay,
the
next
one
is
leave
nothing
behind
instantly
upgrade
and
then
all
the
rest.
C
Yeah
that
that's
actually
I
mean,
do
even
use
a
term
like
transactionality
or
assets,
or
something
like
that.
So
basically,
we
provide
database
like
guarantees
for
the
integrity
of
the
integrity.
A
How
would
you
so
we
can
clearly
this
it's
so
we
say
are
not
instant.
Oh.
A
We're
assuming
people
have
humor,
so
that's
I
would
avoid
humor
or
at
least
potentially
dangerous
one.
I'd
love
it,
but.
A
A
We
just
need
to
find
the
second
part,
or
maybe
the
whole
thing,
but
I
I
really
like
the
descript,
it
kind
of
explains.
A
Without
the
doubt,
what
atomic
upgrades
are
yes
and
then
we
explain,
of
course,
the
linking
farm
and
the
picture
where,
where
is
gilco's
home
and
then
everything
the
firefox
gets
installed
right.
A
We
need
to
find
we
need
to
find
the
name
for
the
mascot.
We
need
the
mascot
first,
then
we
need
to
find
the
name,
and
then
we
can
use
that
as
a
as
a
user.
In
our
examples.
A
Anything
further
on
on
this,
except
that
we
need
to
work
on
it
on
the
title
but
offline
and
the
text
looks
okay.
Next,
one,
multiple
development,
environments,
no
conflicts
with
the
operating
system
and
then
again
title
I
it's
like:
okay
ish.
I
like
the
no
conflict
it's
been
mentioned.
I
think
that's
important
that
the
rest
around
I'm
not
sure,
but
description
fits
properly
as
it
I
mean
it
fits.
A
I
would
say,
if
maybe
let's
start
whoever's
thinks
about
this,
we
should
maybe
think
from
a
perspective.
What
are
the
current
problems
that
user
faces?
Let's
say
there
is
a
user
and
it
has
two
development
environments
and
they
somehow
collide
or
something,
and
what
would
that
user
be
looking
for
as
a
yeah,
so.
C
So
they're
they're
running
all
these
crazy
scripts
to
install
all
sorts
of
dependencies
and
various
places,
and
so
maybe
yeah
stop
polluting
your
system.
D
Or
something
like
messing
up
your
system
also.
C
A
Yeah
yeah
right,
I'm
not
sure
it's
the
the
best.
C
A
A
B
And
just
something
about
the
last
sentence
it
finishes
with
it
ends
with
with
the
same
dependencies,
but
the
issue
is
not
with
the
same
dependencies.
It's
with
country
think
dependencies.
B
B
A
Okay,
okay:
this
is
the
worst
one.
A
Any
suggestion
is
like
I
think
this
is
I
don't.
We
don't
want
to
discuss
it
because
it's
clearly
not
a
good
one,
but
I
would
just
ask
you
to
fix
it
or
suggest
in
after
the
the
meeting
that
makes
sense.
B
I
don't
know
how,
but
I
think
that
coherence
or
coherently
or
current
should
be
in
there,
so
I
don't
know
where,
but
I
think
the
word
is
important,
because
it's
patches
and
custom
changes
and
what's
the
issue
with
that,
there's
no
issue
except
that
generally,
when
you
start
going
with
patches
and
custom
changes,
your
system
stops
being
coherent.
It
starts
being
a
big
ball
of
mess.
A
B
And
not
necessarily
in
the
title.
I
just
think
that
it's
something
that
that
should
be
explained
that
it
keeps
everything
as
one
single
units
one,
instead
of
being
just
a
set
of
patches
that
you
have
to
deal
with
externally
or
in
a
way
that
you
we
know
how
it
how
it
works,
what
they
have
the
x
build,
but
they
don't
so.
C
Yeah
that
gets
back
to
reproducible.
So
you
have
your
coherence,
description,
which
is
because
it's
a
complete
description.
It's
reproducible,
complete.
C
A
A
This
is
so
our
so
I
think
our
main
use
case
is
not
to
change
packages,
but
these
development
environments,
and
we
need
to
speak
to
that
like.
I
know
that
you
can
do
this
for
right,
but
our
main
audience
is
development
environment
and
if
somebody
we
need
to
speak
to
the
to
these
people.
D
A
So
when
you
work
on
a
development
environment
right,
let's
say
you
are
working
on
a
project
and
usually
this
means
you
will
use
many
dependencies
and
a
lot
of
times
happens
that
you
need
this
dependency,
but
because
it's
like
there
is
a
fix
for
a
problem
that
you
have.
But
you
know
you
just
need
to
wait.
Oh
no
waiting
for
patches
there
we
go
or
no
waiting
for
upstream
releases
or
something
like
this.
A
D
D
A
A
This
is
like
a
complete
dependency,
which
we
mentioned
it
already
a
bit,
but
I
think
it's
okay,
if
it
repeats
if
the
features
kind
of
repeat
because
they
are
connected
right.
That's
why
acid
is
quite
kind
of
it's
we're
displayed
yeah.
We
could
use
asset
in
any
of
these
titles.
Almost
now
stop
looking
for
what
is
missing.
Let
mix
remind
you.
B
My
main
concern
with
this
is
the
way
it's
telling
nyx
reminds
you
about
the
missing
pieces.
Let's
say
that
you
edge
your
your
development
environment
and
it
uses
node
for
something
and
you
don't
and
kill.
Node
nix
will
not
tell
you
that
you're
missing
nodes
and
other
dependencies
from
nodes
it
will
probably
fail,
depending
on
how
you
run
the
system,
but
nix
itself
wants.
It
won't
tell
you
hey,
you
are
missing
node.
C
Yeah,
so
it's
really
the
other
way
around
mix
forces
you
to
remind
it
about
missing
the
currencies
exactly
and
and
stop
looking
for
what
is
missing.
Well
yeah,
you
still
have
to
look
for
what
is
missing,
because
mix
won't
really
tell
you
so
mix
forces
you
too
again
yeah
specify
dependencies,
but
I
mean
maybe
want
a
catchy
way
to
phrase
that
mix
forces
you
to
be
complete
about.
A
C
You
can't
be,
I
mean,
that's
right,
it's
a
bit,
it
sounds
like
work
and
in
a.
C
From
the
perspective
of
the
user,
so
the
story
you
can
tell
here
is
that
well
it
just
actually
gets
back
to
the
it
works
on
my
machine
or
it
works
on
their
machine.
So
one
developer
has
this
project
and
it
compiles
on
their
machine
and
and
then
it
fails
on
somebody
else's
machine
because
they
weren't
complete
about
the
dependencies.
C
B
D
A
I'm
sure
we're
gonna
change
it
numerous
times
and
that's
good,
that's
good,
so
that's
kind
of
it.
There
is
one
thing
so
kind
of
the
process
that
I
want
to
have
here
is.
I
want
to
expand
a
bit
more
with
the
rest
of
the
features.
So
there
are
two
features
missing
and
one
is
we
said
lang,
language,
agnostic
and
the
other
one
is
declarative
configuration.
A
A
So
yeah,
so
I
would
like
to
add
this,
and
once
we
have
roughly
the
idea,
it's
okay,
if
it's
not
perfect,
like
the
say,
like
the
words
and
everything,
but
we
could
then
already.
A
The
number
of
items,
but
I
think
it
should
be
flexible
so
that
we
can
always
add
and
remove.
I
think
what
it's
important
that
you
know
like
we
need
some
kind
of
a
structure,
and
I
think
this
is
like
a
title,
a
bigger
description
and
then
maybe
there
are
a
few
items
that
we
want
to
explain.
A
There
are
multiple
ways
how
we
can
do
this.
I
mean
how
design
can
solve
this
so
that
it's
not
cluttered,
but
still
that
you
explain
everything
so
that
nothing
is
hidden.
So
I'd
like
that,
it's
a
bit
it's
a
bit
hard,
because
we
need
to
kind
of
work
at
the
same
time
on
both
things,
but
I
think
it's
we're
gonna
come
to
a
an
satisfaction,
satisfactory
result.
So
after
that
one
of
the
things
we
need
from
this,
I
would
like
to
so
all
these
titles.
A
Might
I
would
like
to
take
three
catchphrases
three
like
be
carefree,
it's
quite
interesting
and
to
build
around
it.
If
you
remember,
we
had
on
a
design
this,
so
you
can
imagine
be
carefree,
would
be
one
of
them
and
be
secure,
be
whatever
or
just
carefully
secure
and
so
to
come
up
out
of
this
with
three
sections.
A
With
a
bit
of
the
description,
we
can
even
repeat
it
for
what's
worth
right
and
even
maybe
yeah
kind
of
it
take
the
top
three,
how
it's
called
top
three
sections
of
this
features,
page
and
kind
of
include
it
in
the
landing
page
and
out
of
that
after
this
all
is
done.
The
last
thing
that's
waiting
for
us-
and
this
is
not
gonna-
be
a
huge
debate,
but
maybe
we're
gonna
have
more
ideas
at
this
point
because
we
will
go
through
this
process
is
to
fix
this.
A
D
A
Okay,
okay
I'll
share
this
right
after
the
meeting
and
the
link
is
already
there.
I
will
give
you
the
the
permissions
are.
B
A
A
A
See
yourself-
and
I
forgot.
A
Perfect
here
we
go.
D
Yes,
content
wise,
so
we
can
discuss
if
we
want
to
ask
about
the
background
of
the
person
where
they
come
from
or
if
we
want
to
dismiss
it.
This
time.
A
A
Are
asking
for
how
old
are
you
why?
What
do
we
want
to
get
from
this
like?
I
would
like
to
see
this
connection
being
done
so
so,
like
each
question
should
come
with
the
reason
why
right
and
you
know
like
so
that,
because
otherwise,
why
are
we
asking.
A
I'm
not
sure
how
to
work
on
this,
because
it
would
be
so
first.
I
cannot
edit
this
file.
It
would
be
nice
to
have
it
in
something
that
we
can
kind
of
collaborate
on.
D
I
can
make
it
open
for
everyone.
D
A
Maybe
but
but
I
think
this
will
not
happen
like
we
can
go
through
all
the
questions.
If
we
have
specific
questions
like
is
this:
okay,
is
this
not
okay?
We
can
collect
quick
feedback,
but
the
real
work
on
this
will
happen
between
the
meetings.
I
think.
D
D
Can
discuss
now?
What
do
we
want
this
time.
A
A
Not
even
that
not
really
with
the
design,
but
can
you
find
something
you
know
like?
Can
you
find
your
things
and
then
in
correlations?
We
were
also
interesting.
What
we
would
be
also
in
because
of
this
is
the
goal
we
are
also
interesting.
What
is
your
background?
What
is
your
like?
Where
do
you
work?
Do
you
use
nicks
at
work,
because
then
this
incorrelations,
this,
this
kind
of,
tells
us
who
our
audience
is
on
the
website.
D
A
Are
you
writing
this
down?
Because
I'm
not
sure
I
can
hear
right
now.
A
Okay,
it's
recorded,
so
we
can
circle
back
to
this.
So
from
my
point,
like
from
marketing
point
of
view,
I
think
that
this
would
be
like.
We
need
to
know
whether
we
do
it.
We
did
a
good
job
and
maybe
ask
are
the
direction
like
that
we're
going
is
this?
A
Is
this
okay,
like
I
would
like
to
confirm
or
drop
the
idea
that
our
main
audience
is
or
should
be,
development
developers,
and
I
call
system
administrators
right.
D
A
A
And
I
assume,
if
this
is
done
after
the
release,
we
can
just
generally
ask
about
like
if
you
are
in
like
I
would
like
to
improve
the
well
everybody
would
like,
but
what
I
think
it's
like
all
these
issues
that
we
have.
We
could
ask
about
rfc.
So
if
you
are
a
knicks
community
member
like
if
you're
part,
if
you
contribute
to
community,
if
you
open
a
pull
request
right,
you're
already
a
member
of
nick's
community
or
your
next
contributor
in
some
sort,
so
your
like
was
the
whole
process
good.
A
And
maybe
we
can
ask,
did
you
contribute
to
the
rfc
discussion
as
well?
So
can
I
get
the
feedback
on
this?
I'm
not
telling
that
we
should
do
this
all
in
one.
D
A
A
A
Exactly
but
I
think
these
kind
of
goals
need
to
be
discussed
and
I
think
I
would
like
that
we
go
with
this
once
we
have
some
goals
and
we
write
them
down
as
part
like
as
a
marketing
team.
Yes,
maybe
go
around
and
even
like
once
we
have,
it,
maybe
collect
them
on
discord.
What
what
should
we
look
for
in
survey.
C
By
the
way,
since
this
was
mentioned
last
time,
so
I
had
to
bias
and
some
other
people
at
fleet
are
also
working
on
a
on
a
survey.
A
Yeah,
okay,
I
talked
to
tobias
and
I
think
the
goals
of
the
survey
they're
doing
is
a
bit
different
like
they're.
They
don't
want,
they
don't
want
to
their
goals,
are
not
to.
They
just
want
to
know
what
the
community
is
about.
It
is
like
basic
statistics:
that's
it
they
don't.
They
definitely
don't
want
to
include-
or
at
least
that's,
not
the
goal.
How
was
I
told
to
include
you
know
things
that
like?
How
is
the
website?
Okay?
A
You
know
like
generalizing
right,
but
there
will
be
better
questions.
Of
course,
the
website
okay,
but
they
just
want
to
know
the
general
statistic
of
the
community.
C
C
Yeah
there's
a
lot
of
yeah
statistics
like
what
sort
of
programming
language
or
platform
do
you
use,
but
yeah
also
something
like
what
are
you
using
next
for.
C
Yeah,
okay,
it
doesn't
really
ask
like
well
okay,
there
are
questions
like
if
you're,
not
using
eggs.
Why
not?
So?
What
are
your
pain
points.
A
A
A
D
A
Vacation
he
went
on
vacation.
C
D
A
Okay,
so
kind
of
just
kind
of
summarize
what
we
said
in
order
to
improve.
So
in
order
to
get
to
the
questions,
we
need
to
have
better
goals
and
each
goal
should
be
tolerated,
like
each
question
should
have
one
or
more
goals,
it
should
be
there
for
because
of
one
or
more
goals.
So.
A
Yeah,
okay,
I
think
this
is
it.