►
From YouTube: NixOS Marketing Team Meeting #5, 2020-05-20
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,
hi
everybody
to
another
marketing
meeting.
This
is
the
number
five
and
yeah
I
hope
I
prepared,
I,
I,
hope
I,
organize
myself
a
bit
better,
so
that
we
will
have
a
swift
meeting
and
with
that,
as
always,
please
stay
open,
be
kind
to
all
the
ideas.
Let's
try
to
focus
come
prepared,
let's
not
start
a
discussion,
what
to
do
as
permissions,
but
rather
come
with
the
idea
already
formed
that
you
need
other
instructions
or
you
want
to
have
more
conversation
right,
so
try
to
be
better
prepared.
So
these
meetings
are
not
too
long.
A
Basically,
let's
talk
if,
but
if
there
are
discussions
that
need
to
happen
which
are
more
higher-level,
let's
then,
let's
do
have
them,
but
first
try
to
do
them
in
issues
pull
requests
and
such
and
the
most
important
thing
all
the
way
we
are
here,
because
we
want
to
make
mix
better.
We
want
to
polish
it
and
that's
the
only
goal
doesn't
matter
how
we
just
want
to
get
it
there
like
each
week
a
bit,
so
we
I
see
already
put
yourself
in
the
in
the
attending
list.
A
So
there
are
two
announcements
of
what
I
was
working,
so
I'll
just
continue
because
I
already
start
sharing.
We
can
have
a
bit
of
discussion,
but
I
would
like
to
limit
it
and
just
kind
of
as
I
announced
it
have
the
discussion
on
the
PR.
So
the
PR
was
the
landing
page
the
which
we
discuss
in
the
sky's
controversial
how
we
discussed
it
long.
A
It
was
long
but
was
good,
but
what
raised
the
question
was
that
I
needed
to
do
much
simpler,
smaller
step,
so
what
I
did
was
I
included
all
the
stuff
that
we
agreed
upon,
which
I
lighted
here,
which
is
kind
of
the
layout
of
the
front
page.
It
was
good
enough.
So,
like
a
title
description
and
the
video
on
the
right
and
the
title
we
agreed
upon
that.
It's
like
reproducible,
builds
and
deployments.
We
can
all
of
this.
A
A
The
download
button
like
there
are
few
things:
I
remove
those
three
buttons
I'll
switch
to
the
preview,
so
this
text
here
is
the
same.
It
is
on
the
current
mixes,
so
you
should
not
discuss
it.
We
can
discuss
it
afterwards,
so
kind
of
smaller
steps
right.
The
same
thing
about
mix
is
same
I
know
it's
not
the
best,
but
let's
discuss
it
in
a
separate
issue
and
then
okay
download
getting
started.
I
extracted
this
text
from
the
about
pages
and
just
highlighted
some
bolded,
some
things
so
I
didn't
wrote
the
text
it's
already
there.
A
I
just
put
it
up.
If
you
think
something
else
should
be.
Please
let
me
know,
but
if
you're
disagree
that
this
should
be
here,
I'm
completely
fine
of
removing
it
I
just
want
to
kind
of
move
this
forward.
I.
Add
that
also
this
section
of
connect
that
we
have
a
lot
of
packages
kind
of
trying
to
say
this
text
is
also
from
the
mixed
packages
about
page.
We
can
change
it,
but
I
would
rather
do
it
afterwards
kind
of
getting
merged.
A
It
also
searches
stuff,
and
there
are
examples
I
will
just
make
sure
they
are
there.
I
would
not
like
on
the
pull
request.
I
would
not
like
you
to
add
new
examples,
but
only
comment
on
the
current
and
if
they
are
not
working
properly,
we
can,
if
you
want
to
add
new
example,
let's
first
lend
this
page
I,
let
this
PR
and
then
add
new
ones,
or
we
can
always
also
change
or
remove
old
ones.
A
A
Of
course,
there
is
some
to
do
that
needs
to
be
done,
which
is
about
here
well
here
mostly,
the
video
is
missing
and
I
need
to
double
check
if
the
examples
actually
work
and
the
previously
the
built
about
pages
so
mix
and
mix
OS
annex
packages
have
about
page
or
something
of
that
sort,
and
this
is
now
the
features
flag
features
option
in
the
menu
and
it
just
side
by
side
about
six
arrests
about
about
nicks
and
it's
just
a
copy
place
or
what
was
already
there.
Is
it
good?
It's
okay
could
be
better.
A
A
B
A
A
A
A
What
else?
Let's
say
a
common
thing
is,
if
you
search
for,
if
you
search
for
g
HC,
if
you
remember
how
this
was
you
get
a
lot
of
other
haskell
packages
results.
Now,
if
I
got
correctly
this
like
the
most
relevant,
is
this
one
right?
It's
the
GAC.
So
we
did
some
ranking
and
boosting
of
the
results
just
this
week,
but
kind
of
it
works
the
same.
It
looks
the
same.
I
think
I.
Think
there's
still
a
few
things
missing.
A
A
A
And
apart
from
this,
so
this
is
replacement,
and
then
there
are
other
ideas
we
want
to
explore
with
this.
First
is:
can
I
have
a
search
for
each
evaluation
so
that
you
can?
Actually,
if
you
go
on
the
page,
you
can
actually
show
which
versions
are
in
other
evaluations,
so
you
can
maybe
use
them.
So
that's
one
of
the
options,
the
other
one
is.
You
can
see
the
progress,
how
many
packages
get
added
and
removed
over
time.
A
A
Actually
well,
the
more
and
more
important
is
between
two
versions,
so
we
can
say
since
less
so
the
release
manager
could
we
could
kind
of
also
generate
like
a
report.
This
many
packages
were
added
this
many
removed,
this
menu,
updated
and
so
on
right,
so
it
would
at
least
provide
the
list
that
they
need
to
go
through
and
create
this
report,
and
we
can
provide
many
stats
in
terms
of
once.
We
have
how
many,
how
many
packages,
one
maintainer,
is
maintaining
right
and
things
like
that
and
another
page.
A
Another
idea
is
also
to
have
a
maintainer
page,
where
you
will
see
like
oh
I'm,
a
maintainer
of
this,
and
this
many
packages
and
kind
of
have
a
better
overview,
like
maybe
even
pulling
in
the
github
data.
Somehow
that's
the
kind
of
future
work,
but
the
first
step
is
of
course,
get
search.
Working
that
was
what's
been
done.
C
Can
I
just
say
something
very
shortly:
I
think
all
of
these
are
like
nice
to
have
I
think
the
most
useful
one
for
beginners
is
just
like
eyepin
mix
packages
and
then
I
want
to
see
packages
for
that
spin.
So
something
like
by
evaluation
or
recommit
search
is
most
common.
I
mean
you
can
use
the
NYX
and
for
that,
but
it
would
be
nice
to
have
it
online.
I
think
we'll
have
the
whole
history.
C
A
C
Okay,
yes,
I
was
just
trying
to
like
I
was
writing
tutorials
and
like
it's
really
hard
right
right
now,
I,
don't
know
how
how
you
guys
search
for
packages
but
I,
look
at
source
in
mix
packages,
and
if
you
wanna
pin
stuff,
then
basically
that's
the
only
way
to
do
it
right
now.
So
yes,
and
we
wanna
like
encourage
everyone
to
pin
stuff
in
my
opinion,
because
that's
the
only
way
to
really
say
NYX
is
reproducible
and
my
dad
to
basically
use
all
the
search
on
three
packages.
B
A
A
But
like
can
you
yeah,
let's
not
go
there.
This
is
just
like
a
replacement,
so
we
can
remove
basically
the
whole
a
bit
of
the
closure
size
of
the
mixer's
homepage,
so
yeah.
If
nobody
will
object,
I
will
remove.
I
will
do
the
replacement
in
the
next
week.
That's
coming
and
yeah.
That's
it
so,
but
please
open
issues
if
you
find
that
certain
searches
are
not
as
they
should
be.
A
You
know
grouped
the
next
thing
that
we're
working
on,
which
is
coming
also
before
the
release
is
you
could
drill
down
the
search,
that's
actually
more
than
important.
So
so
doing.
Let's
say
you
have
a
request
library
or
some
package
numpy
right
and
you're,
like
oh
I,
intend
on
the
left
side
or
somewhere.
There's
going
to
be.
A
So
that's
the
next
feature,
which
is
it's
just
there.
It
just
needs
to
be
implemented
in
the
in
the
okay
just
to
go
further.
The
next
topic,
which
I
proposed
even
like
the
last
time,
was
the
that
we
should
start
doing
community
survey
survey
survey
just
to
get
the
feeling
what
the
community
is.
We
never
did
it
and
I
think
David.
Damn
it.
You
already
had
ideas
how
to
do
it?
Yes,.
D
A
I
would
suggest
so
that
we
don't
have
a
big
discussion.
What
kind
of
survey
we
want.
Let's
open
a
ticket
issue
about
this
and
discuss
what
do
we
want
to
get
from
this
survey
survey
there
and
then
bring
that
discussion
once
we
already
have
like
an
idea,
what
we
want
and
bring
that
to
the
next
meeting
and
discuss
it,
and
then
also
maybe
we'll
also
have
somebody
that
can
work
on
this,
and
we
can
also
do
the
research
there,
like
that's
for
examples,
and
we
can
like
it's
not
going
to
go
into
too
long.
A
D
A
I'll
start
I
think
the
idea
is
good.
I
just
don't
know,
I'm,
not
sure
how
important
is
it
on
the
at
least
my
area,
I
think
at
least
what
we
can
provide
for
start
is
the
will
torture,
his
name
or
actually
I,
don't
remember
it,
but
from
in
the
last
Nix
con
there
was
a
talk
about
the
Knicks
history.
I
mean
are
mine
exactly
and
I
think
that
at
least
we
can
provide
this
video
there.
You
can
embed
it
like
history
of
Knicks
in
what
was
half
an
hour.
A
D
A
Ok,
so
the
next
two
tickets
I
kind
of
want
to
skip,
but
please
love
it.
Correct
me
if
I'm
wrong,
I
just
want
to
have
a
that
there
is
some
work
being
put
so,
for
example,
the
master,
don't
think,
let's
just
talk
generally
about
social
media
or
how
do
we
want
to
do
this
and
let's
provide
an
overview,
the
current
state
and
how
we
want
to
go
and
the
same
for
the
second
one.
It's
a
bit
vague
and
I.
D
D
A
B
A
E
F
F
Because
we
are
targeting,
first
of
all,
we're
not
only
getting
statistical
data,
we're
probably
not
getting
data-
that
is
very
representative,
but
we're
getting
much
deeper
inside
and
we
can
probe
into
it
during
a
conversation.
So
this
gives
us
a
better
feeling
for
what
some
of
the
data
we
might
collect
in
other
ways
means
and
also
like
more
of
the
human
factor.
Okay,
what's
really
difficult,
and
how
is
it
difficult
for
people
to
understand
which
also
sometimes
helps
get
to
get
better
get
better
in
size
and
what
to
actually
do
about?
It.
F
I
also
think
it's
quite
cheap
to
carry
out,
because
it's
basically
just
I
mean
we
need
to
invest
time.
Obviously,
because
we
need
to
do
it
with
people,
but
it
doesn't.
We
can
just
sit
down
so
that
you
do
some
screen
sharing
and
get
some
idea
for
for
a
couple
people
what
they
are
their
experiences
and
yeah.
Whatever
we
learned
from
that
I
think
initially,
I
would
try
to
find
like
five
people,
maybe
to
get
the
feeling.
F
Of
and
then
we
can
summarize
the
results
and
get
some
points
like
if
I
don't
know.
If
everybody
has
the
same
problem,
then
it's
quite
obvious
like
if
five
random
or
pseudo-random
people
that
we
get
there
have
the
same
problem.
It's
pretty
obvious
that
we
should
do
something
about
it.
Whether
this
is
writing
better
documentation
or
change.
Some
of
the
tooling
I,
don't
know,
but
I
guess
that's
what
we
would
see
from
that.
F
Yeah
in
the
document
that's
linked
there,
and
probably
it
doesn't
make
sense
to
look
into
it
right
now,
but
I've
written
out
like
a
short
announcement
to
the
community
that
we're
looking
for
those
people
because
I
mean
maybe
we
can
find
it
even
among
people
that
we
know,
but
we
can
also
make
it
as
no
announcement
see
how
many
people
we
get
and
if,
if
there's
a
lot
of
feedback
like
find
20
people
or
something
that,
then
we
can
talk
to
them.
Maybe
in
after
some
iteration
on
the
issues,
I.
D
D
And
I
know
that
on
some
conferences,
for
example,
the
case
Communication
Congress
there's
every
year
next
install
part
where
people
from
the
community
help
new
users
install
an
Express
and
I
think
they
have
the
knowledge.
What's
what
people
struggle
with
and
we
could
ask
them
or
just
provide
or
just
say
we,
we
want
that
feedback.
A
Initiative,
especially
because
you're
willing
to
do
it,
I
think
that
says
a
lot.
No,
because
it's
you
know
like
we
have
all
ideas,
but
we
need
to
go
through
with
them.
I
think
this
usability
testing
can
be
applied
to
anything
we
do
even
the
website,
you
know,
can
you
find
something?
You
know
there
are
many
aspect
and
how
not
even
just
the
usage
of
the
Knicks
itself,
it
can
be
even
like
does
the
guide
that
we
create
tutorials.
A
Do
they
make
sense?
You
know
things
like
this,
so
it's
like
it's
a
crucial
thing:
I
think
how
it
plays.
It
is
orthogonal
to
the
other
stuff,
but
to
the
survey,
and
but
what
I
think
we
can
actually
do
is
to
use
the
survey
as
a
kind
of
announcement
for
once
we
polished
it
right
because
it
will
take
some
time
to
polish
the
whole
process.
A
A
I
use
usability
testing
and
if
you
can
record,
maybe
just
one
session
and
kind
of
try
to
have
like
10
minutes
and
showing
how
you
help
somebody
understand
and
how
and
even
then
maybe
having
like
a
talk
after
in
saying
like
oh,
this
is
what
we
learned
you
know,
or
we
confirmed.
That
would
be
my
just.
The
only
suggestion
that
to
kind
of
drive
more
people
towards
actually
go
sitting
down
with
you.
A
A
F
A
A
A
The
other
means
that
we
use
documentation
for,
to
be
honest,
I,
don't
care
I
just
want
the
whole
in,
like
the
whole
experience
of
the
new
user,
to
be
good,
the
rest
I,
don't
care
all
right
and
I
think
the
only
way
to
achieve
this
I
don't
care
about
the
format.
If
so,
first
I
don't
care
about
the
format,
but
the
format
is
being
discussed
and
until
then
I
just
want
a
nice
experience
so
that
it's
it's
on
the
website,
because
currently
the
manual
and
everything
is
on
the
website
until
we
decided
otherwise
Domon.
A
A
F
C
D
E
C
Write
that
way,
all
right,
perfect,
so
yeah
I,
don't
know
I
had
for
quite
some
time
the
backlog
of
writing
a
bunch
of
tutorials
and
I
mean
there
there's
a
lot
of
ways
to
do
it.
Obviously
everyone
would
do
it
their
own
way,
but
I
really
wanted
rights
like
10
to
15
tutorials.
That
I
think
are
the
most
common
or
way
of
people
entering
mix.
So
it's
not
about
covering
everything,
it's
more
about
covering
the
most
common
reasons
why
people
would
like
try
next,
essentially
that's
the
lingo
and.
C
Yeah
I
think
it
should
be
done
in
a
more
proper
documentation
away
so
that
things
can
be
organized
with
a
documentation
of
system
so
that
you
can
have
a
glossary
and
surge
over
the
documentation
and
all
these
things
anyway.
So
I
started
the
next
of
Death
I
bought
the
domain
just
like
a
week
ago
which
wasn't
cheap
but
yeah.
C
We
have
it
now
and
yes,
I
wrote
to
choose
Torrio's.
Actually,
while
I
was
already
done,
installing
next
I
extended
it
a
bit
and
then
I
wrote
very
basic
one
like
ad
hoc
environment
developer
environments,
and
then
there
is
like
a
bunch
of
issues
open
on
the
next
of
defillippo
story
and
yeah
I
wanna
I'm
gonna
spend
the
next
weeks,
probably
like
2
or
3
days
per
week.
C
Writing
those
and
trying
to
get
trying
to
get
some
technical
writer
to
look
at
it
as
well,
because
my
life
style
of
writing
is
not
really
technical
writing,
so
it
would
be
good
to
get
it
a
bit
more
consistent,
I
think
sorry,
I,
don't
know,
I
don't
want
to
stop
anyone's
energy.
If,
if
somebody
wants
to
join
efforts
with
that,
that's
great-
it's
not
that's
also
great
I-
think
there's
pretty
good
infrastructure
right
now.
So
when
you
open
a
pull
request,
it
will
like
generate
a
preview
page.
C
F
I,
don't
care
too
much
about
the
technology
I
mean,
of
course
it
makes
a
difference,
but
I
have
to
write
raw
HTML
or
restructure
text,
but
in
the
end,
I
agree
with
it.
It
is
important
that
we
can
guide
the
user
to
that
and
I
think
for
me,
it's
valuable
to
to
put
the
effort
that
I'm
putting
right
now
into
writing
guides
into
something
that
people
will
discover
when
they
are
on
the
NYX
website.
Right,
because
that's
that's
the
kind
of
angle
that
I
want
to
work
on.
F
C
Right
I
mean
my
opinion
is
that
if
we
have
whatever
the
play
is
with
15
tutorials,
which
are
written,
you
know
semi,
okay,
at
least
then
that
is
much
better
than
anything
else.
We
have
on
so
lots
linking.
That
would
be
a
shame
in
the
first
place
and
yeah.
That's
like
essentially,
you
know
use
what
is
the
the
currently
best
source
of
tutorials
and.
C
Although
you
know
it
will
always
be
present
to
some
degree
and
just
have
a
good
infrastructure
in
place
for
writing,
dogs
and
and
the
linking
I
don't
know,
I,
don't
see
a
problem
why
linking
15
links
of
tutorials
is
hard
or
why
it
would
be
done.
I
mean
if
it's
more
like
it
shouldn't,
be
a
separate
side
and
okay
I
wouldn't
understand
this
I
demand
a
job
in
the
first
place.
A
Can
I
propose
just
like
coming
like
as
a
intermediate
solution
for
the
time
being,
so
we
are
writing
the
time
where
the
RFC
about
documentation
is
being
done
or
being
worked
on
right.
So,
whatever
comes
out
of
that,
that
is
going
to
be
the
main
source
of
things
right
or
don't
really
care.
Just
it's
going
to
be
decided
somehow,
whatever
that
is
I.
Think
one
thing
that
you
are
showing
here
really
good
is
that
you
are
showcasing
how
restructuredtext
could
work
what's
the
workflow.
A
So
if
somebody
wants
to
give
it
a
try,
they
can
even
write
right
now
the
tutorial,
and
it
will
show
up
there
right
as
a
good
resource,
I'm,
really
I,
really
I
think
we
should
link
needy
staff
as
as
any
other
website.
We
have
with
the
resources
I
mean,
but
clearly
should
be
done,
but
if
we
are
even
the
NYX
is
manual
and
mix
mix
manual
and
expected
is
manual.
A
We
kind
of
incorporate
into
the
website
currently
right,
and
would
it
be
okay
until
the
RFC's
decided
that
we
want
some
document
so
that
we
contribute
to
Nick's
death
for
the
guides,
but
once
the
guide
is
written
or
updated,
we
copy
paste
the
HTML
and
put
it
into
into
the
mix
less
org.
And
that
way,
and
of
course,
with
the
links
where's.
The
source
of
it
is
to
kind
of
where
you
should
update
the
manual
or
fix
the
manual.
C
A
Understand
so
the
argument
became
this
is
that
it's
confusing
to
the
new
users
that
you
re
directly
between
two
pages
and
showing
those
guides.
It's
something
that
it's
really
kind
of
important,
that
everybody
will
go
there.
It's
something
that
will
confuse
people
right.
I
mean
you
know
like
you,
can
understand
this
or
you
don't
I
mean
I'm
like
right,
but
I'm,
trying
to
find
a
compromise
for
the
next
month
and
a
half
so
that
we
can
contribute
into
one
place
but
then
still
have
you
know
like
it's
a
compromise.
A
F
C
C
B
Something
like
that
but
looks
a
bit
strange
if
you
go
to
Nick's
result
or
again,
the
first
link
you
click
on,
goes
to
mix
of
death.
I
mean
they
might
wonder
that.
Well,
why
does
it
have
different
styling?
And
why
is
different
domain
and
it's
run
by
different
people,
so
it
might
make
a
rudder
unorganized
impression,
I,
like
with
the
cursor
for
some
of
the
wiki.
Is
it
had
different
side
for
my
different
people?
A
Can
I
just
add,
because
I
think
we
are
almost
nobody's
saying
that
having
a
sub-domain,
darks,
dot
or
guides
that
nick
says
that
pork
is
not
the
way
to
go?
What
I'm
proposing
in
my
this
is
that
we
find
the
middle
ground
until
this
is
decided.
You
know
like
I'm,
trying
to
find
the
what
we
can
do
now
that
we
can
start
contributing
to
the
to
one
place
right
because
it's
like,
as
you
said,
right,
like
writing.
The
content
is
the
right.
A
It's
one,
it's
important
right
and
just
having
at
the
same
time
the
consistency
that
we
want,
and
once
the
RFC
it's
confirmed
or
disproved
or
whatever
then
we
can
have
like
I
would
rather
have
this
discussion
elsewhere
in
the
RFC,
where
you
know
like
okay,
now
we
will
work
on.
This
is
our
these?
Are
our
tools?
There's
gonna,
be
dogs,
dot,
mixers,
dot
org?
What
do
we
want?
You
know
like?
E
Just
want
to
come
back
to
the
point,
just
before,
with
a
single
statement.
Having
a
separate
subdomain
in
a
separate
design
in
separate
site
for
documentation
is
leaky
abstraction
of
the
back
ends.
You
don't
need
to
separate
this
in
any
kind
of
way
to
have
a
a
working
website.
It
can
be
integrated
whatever
back
end
is
used
and
I
must
additionally
say
that
when
you
switch
back
ends,
nothing
should
change
for
the
end
users.
E
So
if
you
know
website
that
you,
like,
let's
say,
read
the
dot-com
for
their
documentation,
they
are,
they
are
putting
themselves
in
the
Imperial
of
losing
their
SEO
juice,
since,
if
they
want
to
move
their
backends,
do
something
else,
because
some
thing
doesn't
work
for
them
in
read
the
docs.
They
can't
continue
using
the
existing
URLs,
so
I'm
against
or
for
anything
it's
just
something
to
consider
that
this
is
a
leaky
abstraction.
C
C
Agree
with
that,
I
don't
agree
with
that
at
all,
but
if
you'd
like,
we
I,
think
it's
very
byte
setting
like
it's
pretty
common
to
have
this
and
for
a
month
and
a
half
I,
don't
see
why
it
matters
it's
like.
We
didn't
have
tutorials
for
ten
years,
and
now
it
certainly
matters
that
they're
on
the
same
page,
that's
weight
requirement
to
me,
but
on
the
other
hand,
I
have
nothing
against
this.
If
it's,
if
you
think
it's
important,
then
I.
B
I
mean
the
whole
purpose
is
to
improve
the
website
right.
So
if
we
then
immediately
starts
improving
next
restore
or
by
adding
another
website
that
looks
a
bit
disorganized
and
there's
also
practical
aspect.
So,
for
example,
if
I'm
going
to
make
an
improvement
through
the
homepage,
if
we've
separated
the
cross
different
websites
and
I
would
have
to
do
pool
requests
again.
Multiple
websites-
and
you
know
they
would
ask
the
dependencies
between
them.
B
So,
for
example,
if
we
have
these
examples
from
the
landing
page
and
they
link
to
some
other
page
where
they,
where
it
goes
into
more
detail
and
I,
want
to
do
a
pool
request.
That
makes
her
change
due
to
both
of
these.
And
if,
if
the
extended
page
is
in
a
separate
repository
on
separate
sites,
then
it
makes
it
much
harder
to
contribute
to
that
and.
D
A
Think
I
actually
agree
with
the
point
that
I'm
actually
really
happy
that
Nick's.
They
have
happened
that
it
showcased
the
rsd,
because
I
really
think
the
some
that
people
should
get
a
feeling
of
the
whole
process
right
and
for
that
I'm
really
happy
I
do
think
again.
Domain
is
really
important.
I,
don't
think
we'll
agree
on
this,
but
until
RC
is
done,
I
think
I.
A
Think
everybody
understands
that
once
I
receive
this
decided
how
everyda
days
this
is
going
to
be
the
way
for
official
documentation
right
whatever
that
is,
and
until
then
we'd
like
to
contribute
to
Nick's
tab
repository
and
then
later
convert
it
into
whatever
that
later
is
and
then
still
use.
You
know
like
we
wouldn't
like
to
split
this.
Is
there
is
only
few
of
us
writing
the
documentation
right,
so
I
joined
forces.
C
Yeah
I
think
the
this
is
exactly
the
real
like
I
would
like
a
lot
of
people
to
have
to
be
able
to
contribute
documentation
and
that's
probably
a
very
different
audience
than
people
who
should
have
access
to
Nick's
homepage.
So
that's
probably
another
reason
to
actually
separate
the
two
I.
Don't
see
very
I,
don't
see
a
lot
of
reasons
for
wanting
to
change
the
homepage
and
wanting
to
change
the
documentation.
F
A
B
C
Think
it
would
be
the
same
as
mixed
packages
right.
Anyone
can
write
to
the
manual
if
they
have
committed
to
annex
packages,
so
that's
like
130
people,
so
I
would
give
the
same
group
access
to
this
documentation
if
we
trust
them
with
the
manual
we
might
as
well
trust
them
with
this
and,
of
course
it
goes
all
through
poor
request
of.
B
C
Intention
is
that
you
know
people
can
easily
contribute
I
I,
don't
I,
don't
think
I
mean
that's
my
goal.
I
don't
have
a
particular
opinion.
How
that's
done,
except
that
it
should
ideally
be
done
through
some
reviews,
since
it's
a
big
community
now
so
maybe
actually
give
not
giving
at
commit
access
is
even
better,
but
then
at
some
point
somebody
should
merge.
A
I
think
here
it's
even
extending
a
bit
the
proposal
right
you
can
address
also
the
ill
cause
concerns.
Maybe
move
this
in
move
this
so
I,
don't
know
what
the
repositories
name
but
like
move
this
into
NYX
org
use
the
same,
create
a
documentation
team
put
yourself
there
as
a
and
then
you
kind
of
add
people
to
that
documentation
team,
and
this
is
where
the
commentation
team
start
is
it
starting.
Then
you
know
it's
you're.
A
A
A
Then
we
can
also
discuss
where
this
documentation
will
also
live
separately
together,
but
this
I
would
kind
of
put
into
the
hands
of
the
documentation
team,
and
but
this
will
be
just
a
start,
so
they
have
their
own
repository.
It's
like
it's
not
ideal.
I
would
actually
prefer
that
it's
in
the
home
page,
but
we
can
incorporate
it
in
the
as
part
of
the
build
process.
A
A
A
C
A
A
C
A
C
C
It's
really
one
of
those
topics
where
there
is
a
lot
of
options
to
pick
from,
and
it's
really
hard
to
say
one
is
right
and
another
one
is
wrong.
It's
more
like
that.
The
status
quo
is
is
far
from
good
and
we
can
pick
something
that
is
much
better
and
then
the
difference
between
better
and
a
bit
tiny
bit
better.
A
C
C
A
You
know
it's
marketing,
you
need
to
have
good
spirit
and
speaking
of
the
good
spirit,
it's
one
hour,
so
we
did
it.
We
really
did
it
it's
one
hour
since
we
started,
though,
and
I
will
just
assume
that
kind
of
this
I
will
write
up
and
I'll
ping
you
if
I
that
compromise
it's
what
I
understood
and
then
I'll
write
the
ten
minutes
of
the
meeting
and
post
them.
I'll
contact
you
before
posting
it
so
that
there
is
no
lost
in
translation,
sounds
good.
Okay,
yeah,
with
this
I'll
conclude
the
meeting.