►
From YouTube: NixOS Office Hours, 2019-10-18
Description
Today, Samuel Leathers is joining us to talk about being the release manager for NixOS 19.09 (Loris).
A
Hello
and
welcome
to
the
seventh
Knicks
OS
office
hours,
these
office
hours
happen
every
other
Friday
at
3:00
p.m.
American
New
York
time,
which
is
1900,
UTC
I
think
the
next
one
will
be
a
slightly
different
time,
depending
on
where
you
are
due
to
daylight
savings
time.
At
any
rate,
they
are
recorded
and
live
streamed
on
YouTube.
So
if
you
miss
it
for
the
time
change,
you
can
catch
it
up
later.
If.
B
You
have
a
question
at
least
be
sure
to
use
the
zoom
hang
feature,
so
they
can
give
you
voice
to
raise
your
hand,
talk
and
if
you're
not
sure
how
to
use
the
zoom
hand
feature.
It
is
in
the
dark
that
we've
linked
into
the
call
and
grandma
also
post
a
link
to
this
in
IRC
and
the
zoom
chat,
then
I
think
Graham
will
be
looking
in
our
C
on
the
Nick
Service
office
hours
channel
for
questions
as
well.
A
A
B
Samuel
I
know
it's
quite
a
difficult
decision.
You
know
for,
like
especially
the
time
management
pieces,
to
be
release
manager
for
necks
of
us,
especially
when
it's
such
like
a
big
project
like
this.
That's
so
active,
and
so
many
issues,
and
you
know,
pull
across
to
sort
through
to
decide,
was
going
to
be
part
of
the
lease.
So
how
did
that
feel
for
you
to
make
that
decision?
What
inspired
you
to
actually
choose
use?
Well,.
C
B
B
It
would
be
nice
if
we
could
sort
of
like
organize
in
such
a
way
that
it's
easier
for
the
time
management
pieces,
because
it's
not
exactly
like
it
needs
to
be
like
extremely
sort
of
intensive
on
activity
to
pay
attention
to.
If
we
sort
of
made
together,
it
might
even
it
be
a
bit
easier
like
regularly
every
week,
release
managers
with
Elco
just
to
discuss
how
the
release
is
going.
What
do
you
think
about
that?.
C
Yeah
I,
agree,
I,
think
I
think
it
definitely
would
be
good
to
have
a
little
bit
more
structure
and
a
little
bit
more
documentation
on
what
needs
done,
because
a
lot
of
it
was
looking
at
get
histories
of
what
previous
release
managers
had
done
and
trying
to
mimic
it
and
there's
the
release
documentation
in
the
Nexo
s
manual.
But
some
of
that
stuff
is
outdated.
C
And
then,
when
the
release
comes
about
there's
a
hundred.
Some
open
milestones,
milestone
issues
that
haven't
been
addressed
yet,
and
it's
like
oh
well,
I
guess
we're
just
not
doing
those
as
freely
so
I
mean
it
would
be
good
to
have
the
process
of
how
we
require
something
to
be
for
a
milestone.
And
at
what
point
do
we
just
start
moving
issues
to
the
next
milestone
or
removing
them
completely
from
the
milestone
during
the
release
process?
Exactly.
B
C
B
B
A
A
C
A
C
Well
took
a
huge
chunk
of
it,
and
part
of
that
was
because
I
had
a
new
baby
around
and
so
I
didn't
have
nearly
as
much
time
to
dedicate
to
it
as
I
wanted
to,
but
yeah
I
mean
it
felt
like.
There
was
a
significant
amount
of
work
and
there's
probably
a
lot
more
work.
We
could
have
done
that
didn't
get
done
too.
C
A
One
thing
that
spooks
me
about
release
management
is
the
zero
hydro
failures
and
you
get
pretty
close
to
the
end
and
there's
this
huge
list
of
failing
builds.
What
what
do
you
do
from
there
I
mean?
What's
it
feel
like
to
have
that
huge
list
in
front
of
you
and
just
trying
to
take
it,
get
it
and
work
through.
B
Meanwhile,
I
did
want
to
shift
I'm
sure
something
short
they
did
put
in
next
to
us
office
hours
is
that
that
Fedora
actually
has
like
a
basic
release
criteria
like
sort
of
like
a
criterion
and
what
needs
to
be
I.
Think
working
for
at
least
to
be
on
made
so
like
they'll
make
an
extension
to
the
release.
A
Yeah
I
agree
when
one
of
the
things
I
would
like
to
work
on
is
exactly
this.
What
does
it
mean
to
have
a
stable
release
right
now?
It
means
the
test
of
jobs
that
passes
but
I
think
as
we
mature
and
as
we
grow
as
a
community.
We
have
some
real
opportunity
to
to
do
better
to
push
to
be
better
in
to
come
off
as
a
more
professional
project.
Each
time.
B
Exactly
so,
I
think
like
having
a
almost
a
checklist
like
that
to
help
the
release
manager
know
so
when
they
can
look
around
and
do
their
rounds
to
figure
out
when
the
release
is
ready,
it
would
be
this
sort
of
criteria
and
then
they
can
look
up.
So
that's
a
basically
a
documentation
idea
that
possibly
a
future
release
matter.
I
could
produce.
A
A
A
C
Had
anticipated,
it
was
going
to
be
around
eight
hours
a
week.
I
was
not
able
to
put
in
quite
that
eight
hours
a
week
and
I
probably
put
in
closer
to
like
four
to
six
and
whatnot,
but
I
definitely
is
without
lioness.
Taking
off
the
the
bulk
of
the
workload
and
whatnot
I
definitely
wouldn't
need
at
least
eight
hours
a
week,
I
think
for
it.
B
F
B
A
A
C
Was
able
to
do
some
of
it?
I
was
able
to
do
some
of
it
during
work
hours,
but
it
was
not
like
I
couldn't
dedicate
a
whole
lot
of
time
to
it.
I
had
too
many
other
work
responsibilities,
even
if
they
would
have
given
me
more
hours.
I
could
have
done
at
work.
I
just
had
too
much
stuff
going
on
at
work
to
really
not
just
have
it
be
outside
of
work
hours.
Sure.
A
B
C
A
C
A
C
C
I
think
it
could
definitely
broken
up
a
little
bit
more.
The
biggest
problem
we
have,
though,
is
getting
to
is
hard
enough.
If
we
increase
that
to
a
team
of
like
six,
even
if
there's
less
work
for
each
of
the
members,
it
might
be
still
harder
to
get
people
to
actually
volunteer
to
get
the.
Although
spots
filled
to
break
it
into
a
team,
I
would
say.
Maybe
you
could
have
one
or
two
people
that
are
basically
just
responsible
for
keeping
an
eye
and
on
the
issues
and
pull
requests
and
triaging
them.
C
One
person
responsible
for
making
sure
things
get
back
ported
when
a
backboard
is
needed
during
the
freeze
to
the
release
point,
and
also
with
Mac
porting
the
stuff
to
stable
going
after
that,
and
then
a
third
person
that
might
be
well
a
third
role,
I
should
say
not
person,
because
some
of
these
you'd
probably
want
to
people
are
so
doing.
But
the
third
one
would
be
more
of
like
an
architecture
position
that
basically
someone
that
does
planning
of
like
big
things.
B
E
A
Cool
I
think
that
would
be
really
interesting,
especially
as
I
was
saying
earlier
about.
These
basic
release
criteria
is
trying
to
make
Nix
OS
better
and
better
and
and
keep
things
of
very
high
quality,
I
think
having
I
think
some
communities
call
them
working
groups
who
focus
on
specific
use
cases
or
specific
parts
of
the
operating
system.
I
think
that'd
be
an
interesting
collaboration
with
the
release
manager.
C
A
C
C
So
I
went
on
vacation
like
last
week
of
August
and
whatnot
and
was
trying
to
get
a
hold
of
me
to
announce
the
freeze
date
and
then,
when
I
got
back
on,
vacation
I
was
like
okay,
let's
announce
the
freeze
date
and
we
talked
to
some
people,
and
some
people
were
saying
that
basically
well,
if
we
announce
the
freeze
date
that
soon
it's
not
going
to
be
enough
time
for
people
to
get
stuff
in.
So
we
pushed
the
freeze
date
out
a
little
bit
and
I
was
like:
oh,
we
can.
C
C
There
was
going
through.
There
was
still
about
500
failures,
or
so
we
had
to
go
through
after
we
were
like
okay,
that's
enough
DHS
to
tackle
this
one
around,
and
then
we
had
to
go
through
a
mark.
A
number
of
those
broken
so
and
it
took
a
little
longer
than
we
wanted.
Hydro
took
a
long
time
to
build
something
so
I
mean
just
a
whole
bunch
of
different
things
coming
together,
but
it
all
kicked
off
with
me
just
not
being
available
when
I
was
on
vacation.
C
A
C
Again,
the
documentation
process
of
like
what
pieces
actually
need
to
be
done
ahead
of
time
and
like
marking
like
this,
has
to
be
done
by
this
date.
This
has
to
be
done
by
this
state
leading
up
to.
It
would
definitely
help
with
locking
that
down
to
maybe
actually
getting
a
release
in
the
month
that
it's
supposed
to
be
in
sure.
A
C
Yeah
I
think
for
something
like
that.
You
would
actually
have
to
nominate,
probably
a
core
of
at
least
three
people
to
tackle
that
architecture
of
that,
and
basically
tracking
of
the
implementation
of
that,
so
we'd
have
to
have
some
processes.
We'd
have
to
have
some
people
volunteer
to
actually
pick
that
up.
There's
no
way
the
release
manager
would
be
able
to
do
that
by
themselves
and
whatnot.
That
would
have
to
be
a
huge
community
effort
and
we'd
probably
need
to
put
a
lot
more
structure
into
the
release
to
actually
make
that
happen.
B
C
And
yeah
I
I,
don't
know
how
a
lot
of
people
would
feel
about
like
completely
getting
rid
of
x11,
because
a
lot
of
people
still
use
window
managers
that
haven't
been
ported
this
way
or
haven't
been
ported
to
Weiland
and
whatnot
I
know
like
I
three
us
way:
that's
the
one
I'm
using
and
whatnot,
but
like
people
using
like
PWM
the
next
monad
I
mean
there's
still
a
lot
of
people
out
there,
like
that
and
I.
Don't
think
there's
any
equivalence
of
that
on
the
Whelan
side.
A
That's
true
and
I
can
tell
you
from
experience,
sway
works
generally
much
better
than
x11
in
every
way
in
which
it
does
and,
and
there
are
many
ways
in
which
it
doesn't.
For
example,
zoom
has
surprising
support
screen
share.
Enos
has
surprising
levels
of
support,
it's
definitely
still
a
growing
platform.
Oh.
A
B
Particularly
in
that
regard,
I
will
say
in
the
previous
thing
that
we
were
talking
about
when
it
came
to
having
certain
maintained
errs
of
a
subsystem
step-up
so
like,
for
example,
for
1903.
We
needed
to
update
I
think
it
was
xfce
to
his
latest
revision
and
the
particular
maintainer
of
packages.
Subset
was
unresponsive
and
I
think
it
was
Volvo.
B
Bring
that
brought
that
to
my
attention,
so
I
did
actually
have
to
pick
up,
maintaining
that
provisionally
maintaining
that
package
set,
which
is
a
bit
of
a
something
I,
can't
really
do
completely,
because
I
already
maintain
it.
Several
too
many
package
sets
in
Nick's
packages,
so
in
a
situation
like
that,
I'm
not
sure
what
to
in
the
future.
C
Yeah,
but
that's
typical
of
Nick's,
OS
and
XP
kgs
I
mean
you
have
people
come
in.
You
have
people
going
some
people
more
active
in
some
parts
of
their
lives
and
getting
less
active
in
other
parts
of
their
lives.
I
mean
I
think
we
just
need
to
encourage
people
when
they,
when
they
start
giving
some
interest
into
like
how
can
I
get
more
involved
than
what
not
well
you're
interested
in
desktop
management.
Maybe,
yes,.
C
It
is
is
having,
rather
than
just
having
a
list
of
main
painters
in
the
package,
maybe
having
some
sort
of
like
monthly
or
quarterly
meaning
of
people
that
are
interested
in
this,
especially
for
the
bigger
packages
for
the
smaller
packages.
It
wouldn't
make
sense,
but
for
something
like
X
s,
de
and
whatnot
have
a
quarterly
meeting
where
anyone
that's
interested
in
the
xfce.
C
That's
what
I'm
looking
for
the
ecosystem?
That's
it!
It
could
basically
join
a
quarterly
Nexo
s
meeting
on
ok.
What
do
we
want
to
do
with
it
with
these
upcoming
releases?
Where
do
we
want
to
go
with
this
and
kind
of
encourage
more
community
input
instead
of
people
just
getting
notified
when
they're
packaged
they're,
maintaining
is
broken
and
fixing
it
and
whatnot
maybe
be
in
a
more
little
more
proactive
and
it
might
get
people
much
more
excited
about
maintaining
it
exactly.
A
C
A
B
C
A
B
C
And
then,
if
you
don't
have
anything
else,
some
closing
comments,
as
was
mentioned
earlier,
we
are
looking
for
people
to
volunteer
for
the
position
of
the
second
release
manager
for
2003.
If
that's
something
you're
interested
in,
please
hang
me
on
IRC
I
know
a
few
people
in
the
meeting
that
they
might
be
interested
in
it.
C
So
hang
me,
let
me
know
why
you
want
to
do
it
and
what
kind
of
time
commitment
you
can
give
to
it
and
we'll
take
that
under
consideration
and
I'll
be
floored
if
I
get
like
20
people,
pinging
me
and
I
have
to
choose
someone,
but
that's
not
typically
how
it
works.
So
we'll
see
we'll
get
what
happens
here.
A
C
B
B
A
I,
don't
have
a
pull
request
for
you
to
do
a
review
on
exactly
I.
Do
have
a
pleura
quest
here,
I
believe
Anders
brought
it
up
and
talking
about
teaching
the
Knicks
west
module
options
to
do
user
management,
more
user
management
and
more
database
management,
and
then
so
that's
something
we
could
talk
about
or
or
we
could
find
just
any
old
PR
off
the
top
and
do
a
quick
review
did.
B
A
G
A
G
B
G
F
B
F
B
F
F
F
G
So
I
have
a
question
here
related
to
pinning
these
packages,
though,
because
the
the
package
it
was
causing
an
issue
I
dug
into
it,
and
found
out
that
in
the
latest
release
it
had
some
breaking
change.
So
then
I
pinned
it
to
its
current
version
so
that
it
would
not
be
automatically
bumped
when
I
ran
that
generate
script,
but
it
doesn't
seem
like
many
other
note.
Packages
are
using
this
like
pinning
mechanism
so
I'm
wondering
like
is
this,
but
has
the
other
note
packages
needed
to
be
pinned
to
older
versions
in
the
past
I.
F
G
F
B
G
F
C
F
F
B
B
A
B
A
A
B
A
B
Pull
request
like
this,
it's
helpful
for
his
my
comments
actually
lights
there
so
I
do
see
she
linked
the
pull
request
that
she
has
it's
a
downstream
patch,
apparently
so
I
just
requested.
She
could
just
put
this
in
the
comment.
Just
so
I
can
understand
why
it's
downstream
patches,
even
here
and
I,
do
prefer
if
each
comment
is
per
block
on
the
level
of
the
patch
instead
of
externally
out
here.
So
in
case
it
expands,
you
have
to
like
waste
your
time
and
reorganize
that.
E
B
B
C
A
B
B
B
B
B
E
B
A
E
B
A
Well,
this
has
been
the
seventh
mix
Wes
office
hours.
Nic's
Khan
is
coming
up
next
week,
October
25th
and
26th
in
Brno
Czech
Republic.
Now
is
your
last
chance
to
get
tickets
to
the
conference.
If
you
haven't
already
I
will
be
there
a
lot
of
other
good
people
will
be
there
and
unfortunately,
the
hack
day
is
already
sold
out
if
you're
interested
in
being
the
2.20
point.
Sorry,
twenty
point:
oh
three
coat
release
manager
reach
out
as
Samuel
leathers
on
IRC
or
github
or
Twitter
I
have
posted
some
links
into
the
zoom
group
chat.
A
You
know
if
I'll
post
some
information
and
IRC
just
after
this
tweet
Gallo
is
hiring
full-time,
remote
engineers
to
work
on
Nick's
and
related
ecosystem
tools.
If
you're
interested,
please
reach
out
to
me,
our
next
edition
of
office
hours
is
November.
1St
will
again
be
3
p.m.
American
New
York
time.
However,
there
might
be
some
timezone
confusion
and
I
will
also
be
in
Paris
at
the
time.