►
From YouTube: NixOS Marketing Team Meeting #11, 2020-08-19
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
This
is
going
to
be
the
11th
marketing
meeting,
I
think
even
the
last
one
in
august,
so
this
kind
of
for
the
north
part
of
the
globe
the
summer
vacation
is
slowly
ending
well
august
was
quite
kind
of
vacation
mode.
We
still
got
pretty
some
things
done
so
I'll
switch
to
the.
A
To
the
our
agenda,
I
think
samuel
you
can
start
updating
on
the
this
item.
The
first
item
there.
B
B
Things
got
lost
in
the
time
and
I
forgot
to
actually
reply
to
the
problem,
but
while
minutes
before
this
meeting
started,
I
just
remembered
because
I
was
thinking
about
what
was
I
supposed
to
do.
I
started
writing
back
and
we
wanted
to
know
what
we
needed
to
do.
A
A
B
C
Okay,
that
was
unintentional.
A
B
A
As
much
as
the
how
it's
called
the
the
funds
to
be
transferred
to
the
nixos
foundation
for
supporting
the
the
infrastructure
and
yeah,
that's
having
a
kind
of
fancy
t-shirt
is
a
good
way
to
do
this.
Another
short
announcement
which
I
have
is
so
with
it's.
We
did
some
testing
on
search.nxsis.org.
A
It's
feature
complete.
There
is
one,
not
a
blocker
issue,
but
definitely
a
high
priority
issue,
which
I
want
to
address
as
soon
as
possible,
but
I
I
don't
consider
it
a
blocker
which
is
the
ipv6,
because
the
back
end
of
of
elasticsearch,
the
provider
does
not
support
it.
Now
there
are
a
few
ideas
how
to
do
this,
but
other
than
that.
The
search
that
thinksas.org
is
in
a
in
a
equally
good
state,
as
at
least
in
an
equally
good
state.
A
It
has
current
search
and
there
are
plans
how
we
can
actually
improve
it.
But
this
is,
I
think,
one
of
the
important
steps
where
we
replace
it
right.
We
kind
of
achieved
feature
parity.
Does
anybody
has
like
some
kind
of
a
comment
upon
this,
especially
regarding
the
ipv6.
A
Okay,
there
is
a
ticket
we're
going
to
work
on
it.
So
for
the
listeners,
it's
a
it's
a
high
on
a
priority
list.
It's
just
not
a
blocker
we're
trying
to
do
a
lot
of
things
at
once
and
it's
we
need
to
move
forward.
That's
the
main
reason
behind
it.
Okay,
next
thing,
we're
going
to
talk
about
is
nixon's
redesign,
I'm
shortly
gonna
just
mention
what
is
the
current
timeline
that
we
are
okay,
the
expected
timeline
until
we
finish
so
where
we
are
in
the
process.
A
A
So
what
happened
last
week
was
that
we
finished
our
initial
work
with
the
designer
we
have
roughly
majority
of
the
design.
All
the
pages
were
designed
all
the
elements
and
everything
we
are
left
with
many
choices
that
we
need
to
test
out
and
since
quite
some
time,
samwell
is
actually
working
on
implementation.
So
the
next
step
now
is
going
to
be
the
implementation
and
testing
different
options
and
which
is
also
going
to
give
us
a
list
of
things
that
we
still
need
to
design
right.
A
So
we're
gonna
come
back
to
a
designer
and
implement
and
kind
of
ask
him
for
the
rest.
Now
kind
of
talking
about
the
dates
is
not
best
because
you
always
miss
them
the
deadline,
but
I
really
hope
that
we
will
finish
this
process
in
august,
so
that
kind
of
we're
gonna
finish.
A
A
I
think
we
already
talked
about
it,
but
just
in
case
I
wanna,
because
if
not
then
samuel,
I
think
you
started
the
implementation
and
I
suppose
you
want
to
show
us
as
well,
where
we
are
with
it
and
then
we
can
have
a
discussion.
B
B
Yeah,
just
the
resizing
the
windows,
so
it
works
just
fine,
so
this
is
the
pdf
as
designed
by
the
designer.
So
this
is
not
the
website.
It
just
wanted
to
show
it
before,
because
otherwise
you're
just
seeing
something
out
of
context.
That
won't
mean
much
just
a
reminder
also
that
we
have
different
components
that
are
configurable
according
to
the
design.
Let's
like,
let's
say
the
editor,
the
other
currently
in
this,
this
page
I
chose
to
compare
is
the
dark
header,
but
in
the
implementation.
What
currently
is
compiled
is
the
light
header.
B
B
So
most
of
the
work
currently
has
been
towards
making
the
foundation
foundation
stable
so
that
things
like
this
is
trivial
and
then
working
on
the
hard
part
like.
I
don't
think
it's
going
to
show
up
in
the
compressed
video
stream,
but
in
the
background
behind
the
text
of
this
first
part,
there's
a
really
light
gray
outline
of
the
nexos
logo
and
diagonal
lines.
B
This
is
this
also
overlaps
with
the
following
section,
which,
if
we
look
at
the
example
as
design
this
overlaps
the
same
way.
B
B
Well,
it's
the
in
the
best
way.
I
I
imagine,
because
sometimes
when
you
implement
something
that
overlaps
with
previous
elements
and
web
things
just
end
up
breaking
so
this
section
and
currently
in
the
middle,
they
chose
from
thousands
of
packages.
This
was
the
most
concerning
part
for
me.
If
you
look,
I
have
a
button
named
undetermined,
just
because
I
don't
know
either
what
other
options
should
have
been
so,
instead
of
just
saying
other
options,
I
made
it
obvious
with
clear
brackets.
B
If
you
look
under
there's
a
lime
instead
of
gray,
because
this
way
I
know
for
sure
that
it's
not
final,
it's
just
a
jarring
color.
Instead
of
curry
and
it's
as
we
spoke
in
the
meetings
with
the
designer,
we
don't
implement
it
as
the
as
a
carousel,
because
carousels.
B
Are
not
ideal
for
usability,
because,
when
you're
reading
it
is
something
it's
going
to
fly
away
when
you're
trying
to
to
interact
with
it.
Anyways
carousels
are
not
great,
and
this
is
the
way
it
would
be
exploded
if
we
wanted
to
keep
this
kind
of
setup.
But
if
you
look,
everything
is
not
exactly
right.
Right
now,
like
this
first
part
is
mostly
right,
but
if
you
compare,
the
video
player
currently
is
not
feeling
the
full
height.
These
are
details
that
are
not
things.
I
concern
myself
with
at
first
well.
B
As
I
said,
I
worked
on
the
foundations
of
the
hard
parts
first,
making
sure
this
is
the
right
height
is
finishing
touches,
and
the
examples
is
not
done
like
it
is
on
the
pdf,
because
I
realized
when
I
was
working
on
it
yesterday,
so
this
is
really
new
implementation,
so
I
didn't
have
time
to
get
questions
around
for
that.
This
currently
doesn't
map
with
our
examples.
B
So
I
just
didn't.
I
skipped
next
to
the
next
task.
Well,
in
fact,
I
stopped
working
on
that
day,
so
this
this
would
end
up
being
the
next
thing
I'm
currently
working
on
for
the
home
page
and
otherwise,
if
I
skip
to
the
end
of
the
page,
the
footer
is
mostly
done.
There's
this
part
on
the
right,
that's
not
done,
but
it's
components
that
were
made
after
I
I
did
the
initial
work
on
the
footer
and
there's
the
social
icons
that
need
the
css
replacement,
but
the
elements
are
already
there.
B
So
for
the
main
page,
it's
like,
because
even
even
though
it's
not
finished
I'd
say
80
done,
because
the
really
concerning
part
for
me
are
done.
B
A
A
I
think
there
is
a
lot
of
skilled
developers,
so
what
I
can
serve
here,
or
somebody
if
they
want
to
do
as
well,
is
take
all
these
individual
items
that
are
still
to
be
done
from
this
conversation
and
create
tickets
for
this
with
the
label
redesign
and
then
invite
everybody
to
work
on
them.
So
because
you
know
you
can
continue
working
on
the
rest
of
the
kind
of
ground
work
of
the
css.
B
Yeah
yeah,
I
don't
need
the
help,
but
it
should,
it
sure
would
be
appreciated.
Maybe
also
a
testing
and.
A
Yeah
exactly
this
is
what
my
I
can
see.
My
part
being
here
is
either
organizing
you
know
like
creating
the
small
tickets
out
of
it
that
we
have
a
clear
like
this
is
a
list
of
things
that
you
can
work
on
and
the
rest
and
then
also
providing
the
missing
content
right,
because
we
are
still
discussing
it
but
from
the
looks
of
it
like
like.
I
hope,
really
hope
that
next
meeting
will
be.
We
will
actually
be
able
to
to
kind
of
have
a
few.
A
How
do
you
call
it
a
few,
a
few
choices
that
we
can
look
at
already?
You
know
from
the
front
page,
so
it's
gonna
be
like
a
different
discussion.
Then.
D
C
Yeah
no
comments
for
me
it
looks
great,
so
that's
so
awesome.
A
I
even
think
it's
like
looking
at
it.
It
even
makes
me
like
that.
The
thing
I
said
it
actually
makes
it
even
plausible
that
we
will
finish
by
the
end
of
like
at
least
not
80.
As
you
said
right,
the
website
could
be
done.
B
Yeah
and
something
I
didn't
point
out
right
now,
the
way
I
started
it.
If,
if
I
look
at
a
page
that
no
work
has
been
done,
it
looks
passable.
So
even
if
we
this
was
done
in
the
uptick
that
I
know
already
that
there
are
pages
that
we
don't,
we
will
not
have
a
specific
design
for
them,
they're
going
to
to
be
totally
usable
and
like
if
we
were
to
to
change
the
design
today,
it
wouldn't
look
wrong
exactly
it
sure
would
be
the
final
design
and
well
this.
B
A
B
Yeah,
I
have
doing
these
kind
of
designs
with
bootstrap.
You
always
end
up
fighting
against
the
tool
instead
of
working
with
you
have
to
design
with
bootstrap
in
mind
when
you
want
to
use
bootstrap
so
and
since
I
know
I'm
not
a
boost
trap
user
already,
I
don't
have
the
experience
to
work
with
it.
Much
because
I
dislike
it
and
I
have
found
a
myriad
of
problems
and
bugs
with
it.
B
If
you
have
a
bootstrap
tree
website,
you
you
can
know,
because
if
you
resize
the
width
of
your
browser
and
you
go
through
the
responsive
with
there
will
be
some
extreme
lag.
B
I
think
the
latest
firefox
doesn't
have
that
anymore,
but
in
the
last
year,
if
you
were
going
through
a
responsive
with
the
way
the
layouting
was
recomputed
in
the
way
bootstrap
was
implemented.
It's
it's
extremely
an
implementation
detail,
but
it
shows.
B
It's
there's
no
actual
framework
because
before
stopping
what
I
was
doing
and
starting
to
work
on
mobile
next
os,
I
was
a
web
developer
with
a
specific
specialization
with
integration
work.
So
it's
been
since
2004
that
I
was
working
with
web
in
2005,
professionally
and
2004
2003,
maybe
that
I
started
just
for
fun
and
since
then,
most
of
the
time
I
had
to
work
on
something
well
at
first,
there
were
no
frameworks
and
then
it's
in
the
evolution
of
basic
runes.
B
B
I'm
sure
the
answer
is
no,
so
I
will
continue
it's
a
it's
like
a
css
reset,
but
instead
of
resetting
two
zeros,
it
resets
to
to
good
values
by
default
for
things
like
paragraph
spacing
and
header
spacing
so
most
of
the
spacing
you
see
there
and
the
how
it's
set
up.
It's
just
the
default
from
this
old
reset.
B
That's
currently
not
even
available
on
the
original
home
page
and
working
with
graceful
degradation
in
mind,
and
everything
is
built,
I'm
using
less
css,
which
is
something
that's
like
sas
to
build
and
instead
of
using
a
framework
that
gives
you.
B
Class
names
that
you
have
to
unsemantically
use
in
your
page.
You
end
up
using
mixins
with
semantic
names,
so
let's
just
show
it
instead
of
just
saying
it.
If
I
go
to
the
main
page,
I
have
customizations
specific
for
the
main
page,
but
I
have
this
mixed
in
this
mixin
is
what
creates
web.
I
don't
see
anything.
C
B
B
B
Using
simple
dom
it
creates
this
effect
where
you
have
a
in
an
element
that
is
first
on
the
left,
then
on
the
right,
then,
on
the
left,
and
you
can
customize
it
like.
Let's
see
not
every
page,
we're
going
to
are
going
to
use
the
same
exact
rules
for
the
height
of
the
graphic
elements,
because
right
now
it's
just
a
placeholder
which
is
a
rectangle
but
you're,
going
to
end
up
using
a
css
replacement
for
an
actual
graphical
element.
B
B
On
the
search
box,
this
is
yes,
it's
a
lot
of
css,
but
this
is.
This
is
going
to
end
up
being
a
mix
in
which
removes
most
of
this
from
the
main
pages,
a
css
file.
B
So
I
I
know
it's
not
exactly
obvious
necessarily
because
of
the
way
I'm
explaining
it,
but
I
have
written
documentation
and
I'm
better
at
writing.
An
explanation
than
explaining
off
the
cuff.
D
Okay,
just
for
interest,
have
you
checked
out
other
frameworks
like
semantic
ui.
B
Most
of
the
time
it's
going
to
end
up
either
too
opinionated
like
it's
made
for
making
an
app.
I
think
it
was.
I
don't
know
if
it
was
semantic
ui,
but
many
of
the
frameworks
are
good
if
you
are
making
an
app
where
there
are
basically,
if
you're,
making
a
crowd,
those
kind
of
frameworks
can
help
the
developer
work,
but
when
you're
making
a
I
j,
when
I
talk
about
this
two
people,
I
I
compare
there's
like
two
webs:
there's
the
application
web
and
there's
the
magazine-like
web.
B
The
application
web
is
where
you
have
components
like
buttons
forms,
and
this
is
like,
if
you
have
a
ui
element
for
making
an
application
these
gener,
these
solutions
generally
poorly
apply
for
what
I
call
the
magazine
web,
where
you
have
the
user,
not
the
user
interface,
but
the
graphical
elements
that
are
used
to
make
the
website
look
good.
B
D
B
Yes,
true,
markdown
files
in
the
project
like
there
are
things
like
I'm
using
something:
that's
called
hat
unit
instead
of
a
real
pixels
or
rem,
because
that's
something
I
haven't
shown
yet
the
website.
When
you
go
way
too
big,
currently
I'm
zoomed
at
30,
it
starts
scaling
in
in
a
way.
That's
how?
How
do
I
explain
if
you
have
a
way
too
wide
displays?
B
Sometimes
websites
are
just
weird
and
broken
this
side
scales,
so
everything
in
the
css
ends
up
being
set
as
a
fraction
of
the
base
font
size,
which
is
it
a
fraction?
Yes,
which
is
a
fraction
of
the
base
font
size
which,
when
you
go
above
the
large
responsive,
breakpoint
I'm
using
the
same
breakpoint
rules
as
bootstrap
as
those
are
generally
good.
As
because,
when
you
go
larger
sorry,
I
lost
my
train
of
thought.
B
Okay,
so
the
the
base
font
size
when
you
go
larger
than
the
largest
size
start
scaling
with
the
width
of
the
viewport
to
ensure
that
you
don't
have
those
weird
issues,
but
when
you
start
zooming
in
like
right
now
at
200
percent,
it's
just
as
you
would
expect
and
that's
something
I
didn't
show
either
currently
well.
B
The
menu
is
not
done,
but
it's
usable,
there's,
there's
no,
but
there's
not
much
worries
about
the
responsive
website,
the
narrow
website,
since,
if
you
see
there,
I
have
on
the
top
left
of
the
site.
A
debug
indicator
telling
me
which
rows
apply.
Currently
xs
is
smaller
than
most
android
phones.
B
If
you
use
an
android
phone
you're
you're
on
the
cusp
of
sm
and
access-
and
you
see
it's
already
been
taken
mostly
in
account
for
because
I
see
now
that
the
buttons
don't
have
the
margin
they
should
have
on
the
bottom,
to
not
the
not
be
too
too
close
to
the
video.
But
you
see
that
the
way
is
implemented
with
graceful
degradation
in
mind.
It's
already
most
of
the
way
there.
A
No,
this
looks
great
look.
I'm
just
surprised
that
there
is
documentation.
You
want
to
start
with.
That's
good,
okay,
let's
talk
after
this
meeting
for
the
more
implementation
and
how
we
can
bring
until
next
meeting
this
to
for
the
rest
of
the
community,
how
we
can
open
this
on
a
branch
and
kind
of
see
the
preview
and
so
that
we
can
yeah
so
that
others
can
create
pull
requests
against,
let's
say
a
redesign
branch.
A
So
let's
talk
this
offline,
but
I
think
we're
in
a
really
good
state-
and
it
looks
like
this
is
going
to
be
done
this
month
about
the
next
item.
I'll
just
ask:
is
this
all.
B
Yes,
I'm
done
since
15
minutes
ago.
A
Okay,
sorry,
so
the
next
thing
is
about
messaging
about
nixon
xls.
We
briefly
talked
last
time,
and
it
was
my
fault
that
I
didn't
share
the
document
properly.
Although
I
said
I
will,
and
then
I
was
on
vacation
so
I'll
make
sure.
I
think
the
only
person
that
I
need
to
share
to
is
david.
D
A
Yes,
yeah,
please
so
I
use
the
right
email
and
then
we
and
then
we'll
work
towards
it.
So
this
is
kind
of
the
item
until
next
meeting.
Let's
please
share
your
opinions
on
it.
That
would
be,
let's
tear
it
to
pieces
and
get
it
get
it
done
so
this
is,
it
have.
D
You
seen
made
with
nick's
website.
A
D
Yes,
but
I
think
as
inspiration,
it's
quite
good.
A
Yeah
yeah.
I
took
also
inspiration
from
there-
okay,
very
good,
much
more
once
we
will
so
right
now
we're
just
redesigning
the
existing
content,
but
once
we
add
kind
of
newer
content,
it's
in
terms
of
when
we'll
talk
about
use
cases
that
other
companies
have
like
experience,
reports,
white
papers
and
so
on.
I
think
then
it's
gonna
be
like
even
all
not
one
to
one,
but
it's
gonna
be,
and
even
the
improvement
over
build
with
mix
yeah,
okay.
A
But
it's
kind
of
I
want
to
postpone
this
discussion
not
in
not
because
I
don't
want
to
talk
about
it,
but
because
I
want
to
keep
our
focus
on
this
messaging
and
redesign.
I
think
this
is.
A
The
last
item,
if
because
I
think
regarding
messaging,
nothing
was
done
so
far.
At
least
I
didn't
do
much
we
and
we
need
to.
Basically
we
need
to
collaborate
more
and
come
up
with
the
explanation
and
the
text.
A
Looking
at
the
roadmap
for
looking
at
the
road
map
for
our
2009
release,
I
think
we
have
now
the
how
we
call
this
a
release
date.
A
really
you
know,
branch
branch
date
when
the
2009
is
gonna,
be
branch
off
it's
beginning
of
september,
which
I
think
it
kind
of
really
nicely
fits
into
the
also
our
work
timeline.
A
So
this
means
plus,
I
hope,
hopefully
30
days,
and
I
think
a
lot
of
these
things
can
be
done.
So
I'm
just
going
to
go
here
like
search
mixers.org
improvements
were
already
there
and
there
are
a
few
more
on
the
list.
But
let's
say
they're
gonna
be
done,
we're
gonna,
add
more
tutorials
right
after
the
redesign
I
didn't
wanna
or
with
the
redesign.
A
I
didn't
want
to
push
too
much
in
the
first
goal,
but
kind
of
during
the
september
we'll
add
all
the
tutorials
from
nick's
dev
and
design
them
with
the
new
design.
So
not
yet
done,
but
it's
being
work
fun
and
it's,
it
looks
like
it's
gonna
be
finished
change.
How
we
talk
about
next.
This
is
about
messaging,
better
example
for
landing
page.
This
is
this
is
going
to
be
an
ongoing
progress,
blog
a
new
section.
A
This
might
fall
out
to
the
to
the
next
after
the
redesign
to
the
end.
This
is
one
thing
I'm
still
hoping
to
do,
which
is
adding
the
cloud
images.
A
I
think
it's
going
to
be
really
nice
addition
on
the
website,
but
still
less,
of
a
priority,
help
with
nixos
release
and
actually
creating
a
proper
release
notes.
I
hope
to
focus
this
once
the
redesign
is
kind
of
in
the
left
stage.
So
once
the
branch
off
happens,
we
can
start
already
start
working
with
the
release,
management
and
collecting
and
creating
the
text.
A
Commercial
support
and
blog,
as
I
said,
and
jobs
were
all,
might
follow
up
to
the
next
milestone,
and
maybe
this
would
be
better
to
just
figure
it
out
that
you
can
reorder.
A
D
I
have
updated
the
goals,
you
can
provide
feedback.
If
you
have
time.
A
Okay,
can
you
remind
us
on
the
irc
channel
I.
A
So
then,
by
next
time
we
can
please
put
this
discussions
if
you
want
to
have
like
a
feedback
so
that
we
that
I
tell
to
everybody
that
gonna
put
it
on
the
agenda
for
the
next
time,
so
that
we
don't
forget
it.
So
this
is
it.
I
think
we
look
pretty
good.
There
are
a
few
things
that
might
fall
off
the
next
milestone,
but
yeah.
A
With
that,
somebody
else
has
something
that
is
not
an
agenda.
A
Okay
with
that
adjourn,
I
learned
this
word
today
at
the
meeting.
A
So
see
you
in
two
weeks
and
let's
stay
active,
especially
on
the
messaging
part
and
the
community
survey,
so
that,
because
this
is
things
that
we
can
do
kind
of
in
the
more
async
way,
so
that
we
can
just
shortly
review
them
next
time.