►
From YouTube: NixOS Marketing Team Meeting #6, 2020-06-03
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
Okay,
welcome
everybody.
This
is
the
sixth
marketing
meeting
I
guess
we
are
fewer
than
last
time,
but-
and
there
is
also
not
much
to
discuss
on
the
roadmap
on
the
agenda,
but
neither
nevertheless
we
can
see
what
we've
done
so
far
and
what
we
will
work
on
next
I
guess
all
three
items
are
mine,
so
I'll
just
go
for
the
first
two.
These
are
just
review
items
landing
page.
The
video
was
done.
You
can
check
with
VR.
A
A
So
yeah
I'm
hoping
to
kind
of
merge
this
after
this
meeting
and
then
we
have
a
landing
page
I'll,
wait
until
if
you
still
want
to
review
it
a
bit.
So
this
is
the
landing
page
and
the
search
Nick
sighs
that
org,
it's
really
close
now
I
have
all
the
big
pieces
locally
developed
I
just
think
there
are
three
issues
more
and
I
want
to
commit,
and
then
we
are
also
ready,
so
I'm
hoping
to
kind
of
push
the
last.
A
A
B
A
A
A
And
then
the
road
map?
This
is
actually
what
I
wanted
to
talk.
It
may
be
not
a
road
map
item,
but
it's
more
like
a
kind
of
combination
of
status
updates,
where
we
are
because
I
think
we
like
merging
this
to
pull
requests
like
the
landing
page
kind
of
wraps
the
whole
thing
like
we
did
something.
You
know
it
really
feels
like
we
did
something
and
we've
discussed
many
much
more
than
what
is
present
there
and
yeah.
A
So
currently,
what
I
think
we
did-
and
please
add
to
the
to
the
agenda
in
that
done
so
far
item
I,
think
we
moved
to
notify
I
think
there
was
a
major
thing
because
we
separate
it
really.
The
website
is
about
presentation
and
it's
not
tight
with
our
infrastructure
anymore.
Well,
not
so
much
right.
There
are
still
few
redirect.
A
We
will
reorganize
the
websites
kind
of
clean
up
some
stuff,
updated
some
content,
so
it's
relevant
to
today.
I
think
this
kind
of
took
like
one
page
at
the
time
and
I
think
this
approach.
We
should
keep
not
two
big
changes
and
first
tutorials
are
there
like.
We
need
to
see
how
we
can
it
while
I
checked
with
like
few
tutorials
already's
that
are
there
on
mix
dev
and
we
need
to
see
how
do
we
bring
them
in.
But
I
think
this
is
like
four
I
would
be
completely
happy.
A
B
A
I
mean
it's,
you
know
every
to
two
times
a
week:
it's
it's
some
progress.
Could
we
do
more,
or
could
we
do
less?
Oh
definitely
but
I'm
I'm
happy
right.
We
started
it.
That's
that's
why
the
what's
most
mostly
important
for
me
and
we
are
on
a
good
way,
I
think
what
I
notice
is
that
we're
picking
paste
a
bit
in
the
last
week.
So
that
makes
me
happy
like
we
and
I
hope
with
the
state
status,
we
will
be
able
to
kind
of
show
where
we're
going
right.
A
So
this
is
what
I
wrote
down
kind
of
so
the
next
item.
It's
like
what
is
to
be
done
until
next
release.
I,
don't
want
to
do
too
much
of
the
roadmap
planning,
but
I.
Think
next
release
is
a.
It
is
far
enough
to
be
able
to
can
actually
do
the
planning
and
not
a
not
so
it's
not
too
short
and
not
too
long
that
we
will
be
lost
so
kind
of
it.
I
think
it's
90
days
roughly
depends
when
the
release
is
done.
A
A
This
is
the
one
thing
it's
gonna
take
some
time
before
we
are
all
happy
or
maybe
but
I
think
we
can
have
a
discussion
now
all
right,
because
now
we
can
somebody
can
make
a
pull
request
and
see
the
messaging
when
we
answer
how
what
is
next
or
how
do
we
talk
about
Knicks
right,
it's
gonna
be
a
bit
easier
to
discuss
and
we
can
take
it
separately.
Better
examples
as
I
will
lend
the
page.
B
A
The
more
you
will
do
the
work,
so
if
somebody
just
said,
oh,
we
need
better
examples.
That's
really
good
I
need
a
better
example.
You
know
and
pull
requests,
and
we
can
improve
one
example
at
the
time.
I
think
there
is
a
always
a
price
you
pay.
If
you
want
to
show
something
good,
it's
a
bit
too
complex.
If
it's,
if
you
show
something
too
complex,
then
it's
not
really
like
a
showcase
example:
it's
not
short
enough,
so
a
balance,
but
then
I'm
gonna
announce
it
then
blog
new
section.
A
So
this,
then
the
big
one
is
the
redesign
I
just
want
to
focus
and
till
then
on
the
redesign
and
not
really
sky,
discussing
the
tools.
Yet
it
tools
regarding
the
can
we
tools
in
regards
to
should
we
use
something
else
for
template,
think
and
so
on
that
we
need
multilingual
features.
I
don't
want
to
discuss
that
just
yet.
I
would
like
to
postpone
this
is
possible
and
rather
focus
on
redesign
I.
A
A
A
A
The
other
part
which
is
a
bit
higher,
is
the
testimonials
I'd
like
to
like
I'd
like
to
I
think
it's
makes
sense
that
others
provide
testimony
alum
clients
that
are
happy
basically,
if
they
have
something
on
the
web
sites,
that
I
and
say
hey,
we're
happy
with
you
well
make
them
say
something
nice
about
mix
as
well.
In
that
context
right,
it
can
be
done
that
you
know,
in
the
same,
if
somebody
provides
a
testimonial,
this
company
hybrid,
this
was
done.
A
I
think
that's
completely
fair,
especially
even
better
success
stories,
so
this
is
a
bit
longer,
so
one
company
implemented
some
feature.
How
do
you
call
these
like
white
white
papers
or
in
this
kind
of
a
use
cases
that
were
sold
with
Knicks?
That
would
be
nice
and
in
different
areas.
We
can
tag
them.
This
kind
of
goes
a
bit
with
the
blog
in
new
section.
A
It's
like
might
be
something
similar,
but
this
is
kind
of
to
be
discussed.
Is
this
fair
game
or
everybody
all
the
companies
in
the
can
all
the
companies
equally
contribute
right
and
be
equally
visible
in
kind
of
random
order.
I
think
that's
important
to
keep
there
I
mean
if
some
companies
do
more
work
with
mix
that
you
know
like.
That
also
needs
to
be
somehow
balance
this
and
then
the
job
section
I
think
this
could
be
an
interesting
way
of
an
income
to
a
mix
wise
foundation.
A
Again,
we
will
need
to
define
why
we
need
the
income
but
I
think
at
that
point
we
would
Italy
for
start,
we
can
at
least
have
like
going
long
term.
We
could
monetize
this
for
our
infrastructure,
but
I
think
initially
we
at
least
one
a
job
section
where
somebody
posts
a
job.
Somebody
approves
it
and
it's
posted
on
the
on
the
website
and
there
is
like
a
job
board.
You
know
with
the
link
to
apply
to
that
company
and
that's
it
I
think
these
are
like
non
controversial
topics.
C
A
Don't
know
how
to
do
a
redesign
I
think
there
is
a
lot
of
I
mean
I,
don't
want
to
do
it
right,
I!
Think
I,
think
some
oil
is
really
interested
in
how
the
technology
behind
the
redesign
will
look
like
just
speaking
of
the
redesign
it.
What
I'm
mostly
interested
is
in
the
process
like
I'm
worried
that
you
know
whatever
will
produce.
There
is
going
to
be
percentage
of
people
who
are
disagreeing
right
and
I.
Think
that's.
Well,
it's
not
okay,
but
it's
I
think
we
cannot
avoid
that
right,
yeah,
but
I,
wouldn't
so.
A
If
we
hire
somebody
we
so
first,
where
do
we
get
the
money?
That's
one
question
and
the
second
one
I
suppose.
If
we
hire
somebody,
we
need
to
be
explicit
that
they
there
might
be
few
rounds
of
redesign
right
so
because,
if
to
be
I'm,
not
sure
at
which
point
we
we
will
say
this
is
good
enough.
You
know
like
how
does
this
decision
fall
on
the
like?
This
is
good
enough
right.
C
A
C
A
A
C
B
C
C
A
Okay,
I
mean
we
are
only
three
here,
but
still
I
think
it's.
If
the
the
we
can
then
have
another
discussion
about
the
process,
but
I
think
for
now
we
can
say:
let's:
let's
have
a
process
and
discuss
the
whole.
Let's
say
three
options
like
pre,
like
you
know
those
initial
options
where
the
designer
asks
you
in
which
direction.
A
Should
it
spend
more
time
and
then
have
few
iterations
on
that
and
we
discuss
them
here
in
the
meetings,
so
everybody
will
be
able
to
see
them
and
the
kind
of
feedback
will
go
into
the
meetings
we
listen
to
it.
But
you
know
there
is
only
so
much
we
can
write
and
then,
especially
once
we
have
a
preview
of
this,
we
will
go.
B
A
B
A
Yeah
exactly
I
think
we
are
I,
guess
what
we
need
now,
I
think
when,
once
we
know
what
how
to
talk
about
mix
and
mix
os
I
think
this,
and
even
if
we
start
the
redesign
process
that
we
start
looking
for
somebody
I
think.
Once
we
figured
out
how
to
talk
about
Nix,
we
will
also
have
a
designer
that
our
design
team
that
will
do
the
design
right,
because
I
think
these
things
are
two
things
are
connected,
but
they
kind
of
need
to
know
who
are
we?
A
Who
is
our
audience?
And
what
is
next
right
and
I
think
that
that
can
kind
of
give
them
the
all
the
fuel
needed
to
come
up
with
something
I
assume.
We
are
sticking
with
the
logo
that
doesn't
change
right.
It's
like
a
like,
please
narrowing
it
down,
so
logo
doesn't
change.
The
structure
should
more
be
there.
Something
like
this
ideas
welcome
how
to
change
it,
but
I
mean
the
structure
of
the
menu
in
sense.
C
A
B
A
A
A
A
A
B
Until
the
next
release,
I
wonder
whether
we
we
should
take
in
in
the
tutorial
guide
work
include
this
in
here,
because
it's
it's
happening
anyway,
yeah
I
kind
of
market
that
is
being
done,
but
it's
actually
ongoing
right.
Yeah
I
mean
we
had
a
few
basic
tutorials,
but
I
guess
still
not
too.
A
B
A
B
A
B
C
A
A
With
the
tutorials
and
guides,
I
was
hoping
that
we
will
have
like
10
guides
tutorials,
that
are,
you
know
like
the
more
the
most
important,
especially
for
newcomers,
and
as
we
go
further,
let's
say
in
a
year
when
we
have
a
multi-language
site
that
we
will
also
translate
like
the
top
ten
tutorials
that
we,
you
know,
those
that
we
think
that
are
worth
translating.
You
know
for
especially
newcomers.
B
A
B
C
B
A
It's
you
will
have
with
different
people.
Don't
have
different
sessions
like
just
checking
the
landing
page.
Do
we
convey
the
mail?
Let's
say
after
we
do
the
how
we
call
it
change
the
messaging.
How
we
talk
about
things
then
I
think
it's
worthwhile
to
that
right.
It's
like
go
to
mixers
the
torque
and
then
answer
what
is
next.
A
B
B
B
So
yeah,
so
this
is
I
mean
the
framing
here
is
important
right,
because
you
can
I
mean
you
can't
just
let
people
like
go
on
a
website
and
have
them
narrate
their
thoughts,
but
for
this
first
round
of
sessions,
I
would
really
go
for
okay.
So
someone
sent
you
a
link
to
Nick
so
as
dot-org
now
try
to
get
started
using
Nick's
at
least
like
given
that
task
specifically.