►
From YouTube: NixOS Marketing Team Meeting #15, 2020-10-28
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,
so
welcome
to.
I
have
no
idea
which
which
number
of
the
meeting
it
is,
but
we'll
figure
it
out
afterwards
new
nixos
marketing
meeting
today
we're
gonna
be
in
a
small
group,
because
I
didn't
announce
it
properly.
A
I
think
we
skipped
it
so
yeah
there's
lots
of
work
that
we
need
to
kind
of
review,
whether
it's
in
a
good
position
or
not,
and
for
the
today
we
have
the
agenda
kind
of
looking
at
the
pages
and
yeah
that's.
It
sounds
good.
A
Okay,
so
we'll
go
quickly,
so
the
first
page
community.
A
Do
you
have
any
comments
regarding
it
like
in
general,
how
the
design
looks
and
the
elements
try
to
slowly.
B
C
A
Okay,
I'll,
then
open
also
the
governance
and
donate.
I
think
this
this
kind
of
this
three
kind
of
go
quite
well
kind
of
together.
I
think
these
are
quite
standard,
so
we
have
let's
look
at
the
donate
and
I'm
sure
there
is
definitely
things
to
improve
on
this
website
like
in
terms
of
content.
A
I
think
the
second
part
of
this
job,
I
guess
going
looking
forward
how
this
will
change,
is
that
we
will
most
likely
merge
if
you
agree,
of
course,
right
community
and
governance
and
maybe
even
donate
page
into
kind
of
one
community
page.
A
B
Have
no
idea
yet
my
main
worry,
with
putting
the
donate
merging
the
next
page
into
the
other
pages.
Is
that
the
donate
action?
The
call
to
action
from
the
main
menu
disappears,
but.
A
Okay,
yeah,
I
mean
that's,
we
can
bring
the
donating.
I
mean
this
is
a
valid
concern,
although
we
can
add
a
donate
next
to
the
download
page,
which
is
kind
of
the
next
thing.
We
will
actually
look
at
you
know
before,
where
you
download,
you
know,
support
the
project
in
this
way,
yeah,
so
that
might
be
there,
so
it
kind
of
exposes
it,
although
not
in
a
top
navigation,
a
possible
solution
to
this
right.
A
And
then
there
is
a
download
page.
I
think
this.
With
the
current
2009
release.
It
was
quite
nice
how
it
was
done.
It
was
almost
hands
off.
I
think
this
is
still
missing
here.
We're
still
waiting
for
evaluation
to
succeed.
A
And
then
the
regents
will
be
there,
but
yeah.
I
think
it
looks
nice
it.
There
is
one
thing
we
didn't
implement,
although
it
was
in
the
design,
was
that
you
can
actually
go
to
the
older
versions
and
kind
of
download
older
versions
which
is
here
in
the
green
thing.
There
should
be
like
a
drop
down
with
pointing
to
the
last
interesting
versions
or
archive
right.
Yes,
I
think
that
would
be
nice
or
at
least
pointing
to
the
releases
releases.nixos.org.
A
A
This
changed
a
bit
and
it's
far
from
how
we
this
is
the
I
think,
the
content,
the
page
that
is
going
to
receive
the
most
attention
going
forward
like
they're,
because
we
want
to
improve
in
this
area
right
now.
If
I
will
I'll
go
to
the
artwork
where
we
have
the
design
for
the
learn
page,
so
that
might.
A
A
No,
I
mean.
Are
they
perfect,
the
tutorials?
No,
but
we
can
improve
on
them
right,
but
it's
and
then,
at
the
current
place,
I'll
just
close
these
windows
at
the
current
place,
I
added
the
search
in
this
blueish
area
and
later
on,
we
we
can
add
the
buttons
for
language,
specific
tutorials
or
actually
like
examples.
A
Where
they
have
language
specific
tutorials,
so
most
likely
not
in
most
likely
a
person
that
comes
to
nix
wants
to
is,
like,
let's
say,
a
python
developer
and
he's
like.
Oh,
how
can
I
use
mix
with
python
right
and
there
should
be
a
easy
way
how
to
do
this
below?
There
comes
a
guide
which
we
need
to
add
much
more,
and
I
guess,
as
we
will
be
adding
them,
we
need
to
figure
it
out
how
to
organize
this,
and
the
same
goes
with
the
manual.
This
is
just
the
current
structure.
How
I
think
it's
presentable.
A
And
there
are
some
some
kind
of
pointing
to
the
other
learning
resources
and
that's
kind
of
it
comments
on
this
section.
I
hope
to
focus
just
on
the
examples
in
the
next
quarter.
In
this
quarter
I
mean
in
this
release
cycle.
A
A
I
do
have
a
question,
maybe
I'm
not
sure
this
is
the
right,
but
how
should
we
approach
the
now
that
the
markdown
rfc
is
supposedly
is
going
to
be
merged?
We
all
assume:
how
should
we
approach
converting
manuals
into
documentation.
C
A
C
B
There's
only
good
thing
with
the
fact
that
it's
marked
down,
we
probably
can
use
different
tool
chains
for
different
uses.
So
even
if
you
structure
form
md
book,
it's
still
marked
down
under
underneath
all.
So
if.
B
Yeah
and
as
as
we
described
in
the
rfc,
it's
we
prefer
features
that
can
be
implemented
easily
or
that
are
already
implemented
in
multiple,
but
not
necessarily
forced
to
be
implemented
in
multiple
implementations
but
yeah.
If
it's
a
big,
if,
if
there
is
an
issue
integrating
one
particular
tooling
into
the
website,
or
vice
versa,
we
can
probably
use
another
one
and
in
fact,
if
we
we
always
have
two
tool
chains
using
the
same
inputs.
A
I'm
actually
not
that
worried
about
the
the
mark,
the
whole
markdown,
the
specifics
of
the
markdown
syntax,
that
we'll
use
or
the
tool
chain,
regardless
of
what
it
is
a
more
into
what
interests
me
more
is
maybe
try
to
rephrase.
It
is
when
a
person
comes
to
a
website,
especially
beginner,
they
don't
understand,
while
we
kind
of
as
for
us,
I
think
it's
kind
of
intuitive
is
that
what
nick's
manuals
contains
right,
so
nick's
manual
is
so
what's
inside
is
what's
the
audience
with
target
there
right?
A
B
A
Yes,
yes,
so
I'm
just
looking
from
you
know
perspective
a
user
comes
to
the
website.
We
need
to.
They
need
to
find
information
right
so
right
now
they
need
to
kind
of
like
it
is
like
I'll
scroll
a
bit.
So
these
guides
kind
of
show
you
only
about
nics.
What
did
you
can
do?
I
think
we
can
do
even
better
with
the
titles
but
fine.
I
think
it's
good
enough,
but
even
going
further,
if
I
would
not
expose
the
kind
of
the
short
version
of
table
of
contents
for
each
manual.
A
It
would
be
a
bit
hard
to
understand
right
so
yeah.
I
think
I
would
say
this
way.
It
might
be
that
we
might
even
split
these
manuals
into
more
or
merge
them.
You
know,
like
I,
don't
know
I
I
I'm
not
really
worried
how
we
will
handle
this
in
the
back
end,
I
mean
in
the
back
end,
in
the
build
tool
and
all
of
this
I'm
more
worried
how
we
present
it.
C
B
Something
else
about
documentation
where
we
get
more
of
the
people
that
are,
I
think
there
were
people
nexon
2019,
that
worked
into
planning
something
about
documentation,
so
maybe
get
a
another
another
place
to
discuss
about
the
documentation
itself
and
its
structure,
because
otherwise,
I'm
sure
there's
many
people
that
are
not
interested
into
working
on
the
marketing
stuff,
but
are
interested
into
handling
this
documentation
problem.
A
Oh,
that's
definitely
true.
I
mean
I
mean
there
is
a
bit
of
marketing
in
documentation,
and
that's
actually
just
this
part
that
you
know
it's
about
that.
They
are
the
right
tutorials
in
the
right
places.
A
You
know
that's
the
marketing
side
of
it
that
the
user
can
find
it
and
it's
in
their
face.
So
I
mean
that
the
user
that
the
right
user
finds
the
right
manual,
that's
the
kind
of
the
marketing
behind
it
and
that's
it,
but
I
think
there
is.
A
I
would
love
if
there
would
be
a
documentation
team,
and
I
think
I
hope
that
in
the
future
we'll
in
the
near
future
we'll
have
it.
I
think
we
we
can
invite
all
the
others,
because
I
think
the
ma,
the
learn
page
will
be
the
biggest
effort
we
will
put
in
the
future
and
if
nobody
else
will,
if
nobody
else
will
work
on
the
documentation,
I
think
the
marketing
team
will-
or
you
know,
if
somebody
is
interested
in
documentation,
they
can
join
marketing.
A
A
B
Well,
I
think
so
I
just
wanted
to
preface
that
we
shouldn't
discuss.
C
B
Structure
before
we
try
getting
other
people
on
board,
just
in
case
to
make
sure
the
picture
there's
no
by
us
or
anything
that
is
perceived
into
our
efforts.
C
But
I
think
what
what
so
rock
is
a
good
point.
I
mean
you
could
say
that
the
presentation
on
the
the
learn
page
is
what
should
direct
the
structure
of
the
manual,
because
you
can
so,
if
you
think
about
it
from
yeah
what
what
is
the
the
the
nicest
structure
for
a
new
user
then
yeah
that
that
should
determine
the
structure?
C
Yeah
yeah.
So
if
you
so
currently,
the
structure
of
the
manuals
is
determined
by
the
structure
of
the
project.
So
we
have
different
repositories.
So
we
have
different
manuals.
B
C
Yeah,
so
I
I
would
guess
you
would
want
a
sort
of
a
nyx
book
for
for
well
beginners
and
and
so
it
shows
you
how
to
use
nics
and
how
to
write,
nick's
expressions
or
how
to
start
writing
x
expressions.
And
then
there
could
be
another
reference
manual,
although
it
could
be
part
of
the
same
manual.
C
Just
just
just
a
different
part
of
the
same
manual
doesn't
really
have
to
be
a
separate
document,
and
then
the
xos
would
be
a
separate
thing,
because
you,
you
don't
really
care
about
it
if
you're
a
regular,
nix
user,
but
so
the
next
packages
manual
could
probably
just
be
integrated
into
the
nyx
manual
because
yeah.
If
you
start
writing
your
first
python
package,
then
you,
you
probably
expect
to
find
that
in
the
next
manual.
B
Well,
I
think
the
first
words
you
used,
which
were
manuals
and
reference,
are
a
good
track
to
follow,
so
we
probably
probably
want
the
nix
and
next
packages
manual.
That
is
something
that
you
can
follow
like
a
story
like
a
from
the
grounds
up
where
every
chapter
builds
on
the
precedent,
instead
of
just
being
chapters
that
you
have
to
currently
the
next
manual.
If
you
want
to
know
what
the
synthetic
the
syntax
is,
I
think
it's
chapter
14
after
many
other
concepts
are
introduced,
and
then
we
also
need
a
reference.
B
C
A
Yeah
I
mean
there
is
like
I
think,
the
the
first
part
which
you
said
is
about
the
guides
or
tutorials,
which
is
usually
self-contained,
or
at
least
it
points
you
to
what
to
you
know
which
knowledge
is
required
beforehand
and
it,
and
it
has
an
objective
what
it
will
teach
you
right
and
the
second
part.
I
think
what
I
hope
that
we
will
get
out
of
this
reconstruction
is
that
the
whole
manuals
will
become
much
less
sorry,
so
strange
wording
much.
A
They
will
become
much
smaller
because
they
will
only
contain
the
kind
of
the
reference
documentation
and
then
all
the
how
to
use
things,
how
to
do
python
documentation
will
move
into
this
tutorials
guides
and
so
on.
Right
example,
and
I
think
a
nice
example
would
be.
We
need
a
tutorial
about
how
to
learn
next
language.
You
know,
and
part
of
it
might
be
in
this
next
manual.
Where
is
the
reference
documentation.
C
So
are
you,
are
you
saying
that
these
guides
they,
so
there
should
be
a
lot
of
separate
guides
rather
than
chapters
in
a
nick's
book
or
something
like
that.
A
C
A
Yeah,
which
is
fine,
you
know,
I
mean
you-
can
jump
a
bit
if
you
want,
but
it's
kind
of
expected
to
go
from
top
from
first
to
the
last
chapter,
and
I
think
this
is
fine.
There
is
also
a
reference.
A
I
will,
I
will
suggest
like
this,
because
I
want
to
keep
this
meeting
short.
Let's
discuss
this
next
time.
I
hope
that
everybody
that
you
are
listening,
I
mean,
if
it's
fine
with
you,
because
I
want
to
kind
of
have
the
input
and
maybe
there's
going
to
be
somebody
else,
interesting
interested
in
this,
and
you
know
we
can
gather
a
wider
audience
that
wants
to
fix
these
things,
and
I
think
then
we
will
have
a
better
discussion.
B
Yes,
I
believe
this
discussion
should
be
handled
in
a
more
open
avenue
than
the
marketing
meetings.
A
I
mean
we
can
do
small
changes.
You
know
adding
new
tutorial,
but
this
is
as
far
as
we'll
go.
We
want
to
restructure
anything
as
part
of
the
marketing
team,
but
we
should.
A
I
hope
that,
with
this
meeting
and
this
whole
discussion,
we
had
we
kind
of
intrigued
all
the
community
to
consider
joining
the
marketing
or
just
like,
come
to
the
marketing
team.
So
we
can
work
on
documentation
and
found
the
documentation
team.
A
Would
this
be
okay?
If
we
conclude
with
this
topic.
A
Yeah,
okay,
so
this
was
the
learn
page
and
now
the
the
last
page
that
so
this
these
are
all
the
pages
except
the
features
page,
and
I
I
started
to
work
on
on
it
already,
although
I
don't
have
any,
I
only
designed
it
because
I
think
once
we
see
it
and
I
didn't
create
a
pull
request.
I'll
just
show
the
local
development
instance
what
I
have
so
far,
so
the
first
thing
I've
renamed
it
because
features
sounded
a
bit
wrong
because
I'll
go
behind
this
reason.
A
A
A
It's
kind
of
merge
of
all
three
designs
that
we
had
it's
like
a
line.
It
has
a
the
first
line,
please
whoever
watches
this.
This
is
not
gonna,
be
the
text.
It's
just.
This
is
like
a
working
progress
and
we
we
don't
want
to
limit
ourselves
with
it's
going
to
be
much
less
marketing,
but
so
it's
going
to
be
a
title
describing
a
benefit,
make
it
explaining
it
a
bit
with
the
description
and
then
really
explaining
it
as
we
had
in
the
previous
features
page.
A
So
in
this
case
it's
a
not
some
good
example,
because
we
need
to
change
a
lot
of
these
text,
but,
let's
say
stop
looking
for
what
it
is
missing.
Let
nix
reminds
you
this
is
talking,
you
know,
make
sure
nothing
gets
left
behind
and
reduces
and
reduce
the
risk
of
incomplete
dependencies
stop.
So
all
this
is
quite
non-technical.
A
The
first
part,
and
then
the
second
part
which
can
be
also
hidden,
will
actually
explain
the
the
feature
that
we
wanna
that
we
wanna
talk
about,
which
is,
in
this
case
complete
dependencies
right,
and
here
I
actually
just
copied.
The
text
from
previous
website
like
nix,
ensures
that
the
package
dependencies
specification
is
complete
and
so
on.
A
I'm
not
sure
like
this
is
just
a
work
in
progress,
as
I
said,
but
the
the
structure,
how
I
want
why
why
are
there?
These
numbers
is
is
because
I
want
to
tell
the
story-
and
it's
like.
Oh,
if
you
don't
this,
then
this
is
the
next
step
kind
of
I'm
not
sure
this
is
what
we
want,
but
I
might
remove
the
numbers
and
just
have
them
some
other
graphic
there
or
just
no
numbers
yeah.
A
The
graphics
are
also
just
taken
from
the
design.
Yes,
I'm
samurai.
I
learned
how
to
extract
the
graphics
with
inkscape
yeah,
so
this
yeah,
so
in
the
next
days
in
the
next
day
tomorrow.
A
Actually,
I
hope
to
work
on
the
actual
content
of
this,
and
after
that,
once
we
have
the
first
I'm
going
to
be
contenting
and
talking
on
the
nexus
marketing
team,
a
marketing
channel
to
kind
of
collect
feedback,
and
once
we
are
happy
with
the
kind
of
version,
zero
I'll
create
a
pull
request,
not
to
kind
of
create
a
negative
surprise
with
all
this
here,
for
example,
this
definitely
will
go
away
and
the
sky
is
the
limit
right.
A
Yeah-
and
I
think
this
is
it
about
the
features
page
kind
of
looking
what
we
have
to
still
to
discuss
so
yeah,
so
hopefully,
tomorrow
after
tomorrow,
we'll
get
the
features.
Page
feature
features,
page
pull
requests,
and
then
we
can
work
about
the
little
details
about
how
to
the
wording,
basically
the
to
explain
it
and
important.
A
We
just
need
to
be
better
than
we
just
need
to
be
better
than
before,
still
explaining
everything
but
yeah
small
steps,
and
we
can
always
improve
it.
It's
not
the
end
product.
A
Okay
and
the
last
step
I'd
like
to
talk
about
is
actually
the
how
you
call
it
the
front
page.
So
basically,
this
text,
the
description,
I
think
with
some
with,
I
think,
with
samuel,
we
kind
of
got
an
idea
how
to
rename
it
how
to
restructure
it.
A
Two
sentences
in
the
here
we
go
so
there
are
typos.
So
please
don't
judge.
A
A
There
is
a
spot
which
we
don't
know
what
to
put
so
this,
and
then
that
takes
so
I'll
I'll
read
it.
Nyx
is
a
tool
that
takes
a
unique
approach
to
package
management
and
system
configuration,
learn
how
many
enjoy.
A
Making
reproducible
declarative
and
reliable
systems
so
kind
of
shorten
it
combine
it.
We
talk
about
nix
as
the
common
line
utility.
We
talk
about
package
management,
we
talk
about
system
and
configuration
and
we
just
invite
them,
and
we
kind
of
mentioned
this.
Three
reproducible,
declarative
and
reliable
words,
which
is
kind
of
our
top
three
features
that
we
want
to
point
out.
A
Right
yeah,
so
this
might
be
like
all.
B
Right,
if
we
and
describing
everything
like
it's
a
tool,
it's
a
language
and
it's
everything
that
it
is,
it
becomes
too
much.
So,
ideally,
we
want
one
word
that
describes
what
everything
is.
C
C
A
I
think
I
hope
that
you
know
if
somebody
know
from
the
listeners,
if
you
have
a
better
proposal,
please
write
it
in
the
comments
below
above
well,
not
in
the
discourse.
A
A
A
They
actually
we're
just
going
to
change
them
and
talk
differently
about
them
right,
so
reproducible
is
going
to
be
something
I
don't
know
be
carefree
or
something
like
this
like
we're
going
to
talk
about
the
benefit
and
not
the
not
the
feature
of
the
feature
reproducibility
because
yeah,
there
are
many
benefits
from
reproducibility,
so
we'll
just
expose
one.
A
The
whole
redesign
yeah
the
whole
redesign
effort.
A
And
hopefully,
by
the
next
meeting
we
can
get
this
under.
We
can
get
this
done
and
focus
on
other
things
already.
C
A
A
Okay,
so
small
steps
we're
moving
forward.
A
Yeah,
like
I
think,
it's
important
that
even
if
it's
okay,
that
we
are
not
happy
with
this,
but
still
going
for
it,
we
are
not
looking
for
perfect
thing.
You
know
a
perfect
description
of
nyx
right.
I
don't
think
it
exists,
yeah,
it's
good
to
just
like.
Let's
do
it
better
and
then
better
and
better
and
we'll
get
somewhere.