►
From YouTube: Argo Contributor Experience Office Hour 18th Feb 2021
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
A
Obviously,
I've
been
I've
been
noting
in
slack
that
many
people
are
not
finding
what
they're
looking
for
in
our
current
dogs
and
yeah
they've
been
they've
they've
organically
grown
right,
so
we
were
just
adding
things
to
some
places,
and
some
stuff
is
not
very
concise
or
clear,
and
that
brings
up
a
lot
of
questions
in
slack.
A
So
I
I
found
myself
constantly
answering
the
same
questions
over
and
over
again
and
apologizing
for
for
the
documentation,
and
I
had
the
idea,
so
I
think
around
christmas
that
we
might
want
to
to
revisit
our
documentation
not
only
for
the
conciseness
and
and
and
stuff
like
that,
but
also
for
actually
the
the
structure
of
the
dogs
right
so
basically
giving
giving
the
user
a
better
journey
through
the
docks
is
especially
for
for
people
that
are
getting
started
with
our
cd,
because
I
felt
it's,
it
might
be
a
little
overwhelming
for
new
users
to
grasp
all
the
concepts
and
how
they
fit
together,
and
so
I
I
started
between
christmas
and
new
year
to
to
think
about
a
new
structure,
and
I
wanted
to
discuss
this
proposal.
A
I
will
share
my
screen
soon,
so
you
can,
you
can
see
it.
A
If
that's
the
way,
people
would
agree
on,
so
I
thought
about
a
user
story
like
how
would
a
new
user
approach
rocd
through
the
docs
and
just
let
me
share
my
screen.
I
hope
it
will
work
this
one.
A
Yes,
I
can
okay,
so
I've
not
filled
much
content
yet
because
that's
a
very
tedious
task-
and
I
just
wanted
to
discuss
this
with
with
other
contributors
before-
if
that's
a
good
thing
so.
A
A
Then
I
went
ahead
and
okay
getting
started.
I
divided
the
getting
started
guide
into
into
three
separate
steps,
so
I
wrote
some
new
stuff
already.
A
So
this
tl,
dr,
is
basically
what
the
current
getting
started
guide
is
with
additional
a
little
bit
of
how
to
add
your
first
application.
A
But
it
goes
also
to
tell
the
user
actually
that
if
they
are
planning
production,
great
installation,
they
should
go
a
little
further,
and
just
mentioning
that
there
are
various
insulation
types
and
also
insulation
variants,
so
standard
and
high
availability,
and
I
saw
that
there
are
other
ways
to
install
iocd,
for
example,
using
a
remote
customized
base
or
a
home
chart
then
how
to
install
the
cli,
and
then
this
shall
be
like
how
to
get
your
first
application
started
and
what
I
then
did
is
so
currently
we
have
like
a
user
guide
and
an
operations
guide,
and
I
always
felt
the
line
between
the
two
was
very
blurry
and
it
was
like
yeah
not
not
very
clear
where
to
look
for
for
a
given
topic.
A
A
A
So,
what
how
do
we?
How
do
we
see
clusters
and
what's
important,
the
user
will
always
have
one
chapter
dedicated
to
how
do
I
manage
these
resources?
Actually,
what
is
in
repository?
How
do
you,
how
do
you
create
repositories
that
need
authentication?
How
do
you
manage
the
repositories
using
the
available
methods
goes
further
over
projects?
A
What
kind
of
tools
do
we
do?
We
provide
for
the
user
and
a
little
chapter
about
thinking
and
what
I
feel
is
very
important
to
give
the
concepts
of
access
control
in
the
arbut
from
the
beginning.
So
because
I've
seen
so
many
questions,
people
asking
about
arbuck,
I
felt
that's
a
very
important
thing
that
should
belong
in
the
in
the
basics
that
you
need
to
know
to
get
started
with
our
cv
and,
as
I
thought
so,
user
guide
and
operations
guide
were
kind
of
blurry.
A
So
I
thought
it
would
be
good
to
introduce
like
advanced
topics,
so
user
got
familiar
with
argo
cd
and
he
now
has
some
very
specific
things
in
his
head
and
basically
this
is
documentation
for
the
user
on
these
advanced
topics,
and
then
we
have
operations
and
maintenance.
A
A
An
own
section
for
troubleshooting,
then
a
reference
guide,
so
this
is
basically
where
we
describe
the
crds
the
format
of
the
config
maps
and
secrets
that
we're
using
this
will
be
the
the
cli
and
server
parametrization
stuff.
A
Developers
guide
faq,
so
these
are
all
known
things,
but
it's
obviously
that
if
we
go
ahead
and
actually
change
the
structure,
many
many
bookmarks
will
break
right.
So
this
is.
This
is
one
major
issue
that
I'd
like
to
make
content
on
whether
that's
acceptable,
and
the
second
thing
is
I'm
looking
for
feedback
on
whether
this
is
good
going
forward.
A
So
my
plan
would
be
to
to
put
that
in
a
separate
it
repository
just
for
the
purpose
of
finishing
finalizing
this
documentation
before
we
can
merge
it
back
into
our
city
and,
of
course,
I'm
I'm
then
looking
also
for
contributors
yeah.
I.
B
Just
I
really
wanted
to
agree
about
blu-ray
boundary
between
user
documentation
and
operator
documentation.
I
had
the
same
kind
of
like
every
time.
I'm
looking
for
something
I
was
trying
to
mentally
decide.
Is
the
topic
operator
related
or
user
related?
So
I
think
it's
maybe
a
better
way
to
split
it.
B
I
think
it's
organically
grown.
So
it's
it's
fine.
It's
yeah
and
I
agree
it's.
You
know
iteration
on
top
of
what
we
had.
So,
if
I
read
it
correctly,
it
seems
like
we
were
kind
of
saying
that
maintenance
and
performance
issues
definitely
belong
to
operator.
So
we
and
that's
why
we
have
a
separate
section
for
maintenance
and
iterations,
but
some
of
the
kind
of
more
or
less
operator
related
stuffs
still
is
going
to
be
in
advanced
topics
for
sure.
C
Think
on
that
I
would
say
my.
I
think
I
really
love
the
new
approach
that
we
are
taking
here.
So
the
the
only
concern
I
would
have-
and
that
is
probably
something
we
can
gradually
take
care
of-
is
advanced
topics-
may
become
a
sinkhole
of
all
different
kinds
of
things,
which
means
that
means
at
one
point,
keep
growing
and
discoverability
will
again
get
impacted.
D
It's
not
only
that
I
think
it's
it
might
be
confusing,
because
it's
it
might
be
hard
for
an
average
user
to
know
you
know
when
you're
looking
for
something
I
don't
know
I
need
to
do
create
web
hooks.
I
don't
know,
is
that
advanced?
Is
that
basic
you?
You
generally
don't
know
really
to
me
that
I
would
go
towards
the
lottery
proposal
grouping
it
somehow
towards
more.
B
So
you're
saying
basically,
are
you
proposing
that,
instead
of
advanced,
we
have
a
few
more
top
level
groups
like
advanced
advanced?
Do
you
think.
D
Yeah,
like
I
mean
not
not
not
a
few
topics
like
advance,
this
advance
that
I
like,
like
operations
and
maintenance
to
me,
that's
that's
very
easy
to
figure
out
okay.
So
this
this
I
need
backups
and
that's
in
operations
like
kind
of
it's
easy
to
guess
where
that's
where
backups
are
right,
but
advanced
and
basic.
That's
very
that's
relative,
especially
for
people
who
are
not
familiar
with
it.
Might
they
might
have
trouble
finding
it
right?
D
E
F
D
D
A
A
A
D
C
B
I
I
wanted
to
talk
about
this
broken
links
I
feel
like.
Maybe
we
can
have
a
good
solution
for
that.
We
have
google
analytics
and
we
can
find
which
links
people
kind
of
bookmarked.
We
can
just
see
where
people
landed
and
if,
if
we
most
likely
getting
started,
is
a
very
popular
one
and
then
a
few
other
ones,
and
we
can
just
create
redirect
links
in
read
the
docs.
So
we
can
right
maintain
old,
most
popular
yeah.
D
Or
or
if
we
just
keep
kind
of
like,
if,
if
if
a
page
is
moved
somewhere,
we
can
still
keep
the
old
page.
Maybe
just
change
the
content
to
say
redirect
here
or
you
know,
yeah
I
mean
we
can
keep
the
page
without,
even
even
if
it's
removed
from
the
menu
right.
Yes,
yes,
this
is
it's
supported.
G
A
Okay,
yeah
and
yeah
and
then
and
then
we
look
like
you,
propose
alex
in
in
google
analytics
and
maybe
over
time
we
can.
We
can
get
rid
of
the
old
content
and
and
the
redirects
so.
D
A
D
C
What
we
could
also
do
is
probably
host
the
new
documentation
in
a
different
location
altogether
and
have
a
nice
like
a
yellow
header
on
the
old
docs
who
said
this
documentation
has
moved
there
so
that
when
people
land
up
on
the
old
pages,
they're
greeted
with
a
bright
yellow
text,
saying
that
you
need
to
start
going
somewhere
else
gradually.
Yes,
we
just
have
the
yes.
D
H
B
We
just
did
it,
we
kind
of
we
had
to
move
to
the
dogs
to
get
feature,
and
now
we
have.
You
know
the
old
talks
which
tells
hey,
go
to
read
the
dogs
and
then
so.
A
Yeah,
but
so
basically
so
read
the
docs
we'll
we'll
have
the
old
docs
anyway,
so
because
it
works
on
branches
right,
so
we
won't
backboard
this
one
to
to
the
old
branches.
So.
B
A
Awesome
final
question
from
my
side
so
going
forward.
A
So
I
want
to
put
this
in
kit
to
to
invite
people
to
collaborate
on
writing
content
for.
A
C
A
C
B
B
C
B
And
you
mentioned
issues
I
think
it's
the
best
way
to
clear
the
network.
If
we
think
of
one
issue
in
that
issue,
we
finalize
the
structure
and
I
think
we
just
need
to
go
and
do
this
exercise
and
figure
out
top
level
sections,
and
then
we
can
split
work.
We
can
just
say:
okay,
there
is
a
separate
ticket
for
thinking
separate
ticket
for
difference,
yeah.
C
I
think
we,
I
think
that
would
be
a
great
idea,
at
least
that
way,
we'll
be
able
to
ensure
that
the
tasks
tasks
are
grand
granular
enough.
They
are
visible
to
the
community.
Apart
from
the
folks,
while
you're
in
this
call-
and
I
think
jaan
if
you
could
speak
about
it
in
the
community
meeting
as
well,
the
other
one,
the
user
community
meeting
and
do
a
call
to
action
with
here's.
The
plan
here
are
the
issues
that
people
could
pick
up
and
work
on.
Yeah.
G
Sure
one
quick
question
so,
just
like
we
have
test
cases
for
the
dev
features.
Could
we
have
some
sort
of
test
case
for
the
dock
as
well?
And
what
I
mean
by
that
new
contributors
were
joining
our
ocd
project.
If
we
could
somehow
get
their
input
on
how
they're
finding
argo
cd
docs,
because
for
folks
who
have
used
it,
we
probably
know
what
is
this
advanced
topic?
G
B
I
don't
know
if
I
would,
I
feel
like
we
need
some
kind
of
feature
from
either
read
the
dogs
or
yeah.
I
think.
Maybe
the
dogs
has
some
way
to
communicate
feedback,
but,
like
someone
had
to
research,
it
yeah
and,
as
I
know,
I
think,
read
the
docs
simply
host
static
documentation,
and
maybe
they
provide
some
kind
of
services
to
collect
feedback
yeah.
I
need
to
change.
C
B
B
Kind
of
improve
to
make
life
easier,
so
there
is
a
plugin
in
in
read
sorry,
not
indeed
in
mk
docs,
where
you
can
include
files
into
files
and
it's
really
useful
because
often
we
have
you
know
there
is
possibility
to
auto
generate
documentation,
but
you
still
want
to
write
some
some
text
manually
and
then
include
generated
part,
and
I
I
tried
to
do
it
in
argus
identifications
and
it
really
helped.
So,
basically
I
have
a
let's
say:
you
mentioned
reference
in
the
reference.
B
You
can
give
you
a
possibility
to
write
some
text
and
explain
what
is
it
about,
and
you
know
provide
some
examples
that
only
human
can
right.
You
know
and
use
that
plugin
to
include
auto
generated
stuff,
which
has
you
know
so.
Basically,
it's
it's
building
blocks
or
yes,
yeah
right
yeah,
so
you
can
have
files
which,
and
these
files
are
not
part
of
menu-
you
don't
see
them
and
you
only
include
them
from
top
level.
B
B
And
I
think,
and
it's
like
one
ticket
to
agree
on
final
final
directory
structure
or
topic
structure
for
yeah.
So
exactly.
B
I
I
I
have
a
couple
of
questions
for
people
about
the
documentation
I
mean,
so
I
think
the
feedback,
one
of
the
feedback
items
we're
getting
from
the
community
in
the
survey
in
the
workflows
which
I
haven't,
come
up
with
an
action
plan
for
that.
Yet
is
that,
even
though
we've
improved
the
docs
a
great
deal,
they
want
more
than
we
currently
have,
and
I
don't
I
kind
of
don't
know
if
mk
docs
is
the
right
technology.
B
I
know
that
there
is
the
second,
I
think
at
least
another.
The
same
popular
one
is
sphinx
and
I
to
be
honest,
I
never
looked
at
it,
but
it
seems
like
read
the
dog's
favor
like
read:
the
dogs
has
better
support
with
things
for
some
reason.
Don't
know
why
maybe
it's
more
flexible
or
maybe
it
has
more
features
there,
where
you
can
programmatically
define
those.
I
Yeah,
I
guess
that's
probably
the
case
I
mean
we
did
put
the
docs
together,
do
some
kind
of
organization
into
different
areas
and
kind
of
left
it
and
it
doesn't
definitely
doesn't
each
stock
is
kind
of
piecemeal.
I
guess
it
doesn't
create
a
narrative
that
you
can
start
at
the
getting
started
guidance
slowly
ramp
up.
You
know
it
kind
of
jumps
up
and
down
in
complexity
has
like,
like
emissions.
D
That's
true:
that's
exactly
the
feeling
that
I
had
the
first
time
I
jumped
into
argo.
It
was
kind
of
getting
started
great
and
now
what?
If
I
then
you
need
to
start
exploring
all
the
different
topics
and
figuring
out
what
you
should
really
do
next,
some
kind
of
more
like
a
book
approach.
Kind
of
you
know
there
are
steps.
I
Yeah
yeah
I
mean
none
of
us
are
particularly
well.
That's
a
lie.
I
mean
alex
and
jesse
are
writing
a
book
at
the
moment
and
I've
written
a
book
in
the
past.
So
we
should.
We
should
know
how
to
do
stuff
like
this,
but
with
the
community
generator
stuff,
they
often
drop
in
a
particular
topic
and
you
just
stick
it
into
the
index
and
there
you
are
and
they've
also
asked
more
videos,
but
I
see
victor
you've
already
done
a
really
good
job.
On
that
front,
we're
already
really
impressed.
B
I
kind
of
agree
that
technology
might
help.
I
I
saw
very
like
yesterday,
we
had
exact
same
observed,
exact
same
issue
as
documentation,
so
we
typically
have
kind
of
one
place
where
all
kind
of
property
is
described.
Let's
take
as
an
example,
argo
cd
config
map
and
we
have
argo
cd,
their
cm.yaml
file,
which
has
all
kind
of
keys
and
at
the
same
time
we
have
maybe
a
whole
document
about
subset
of
those
keys,
so
basically
same
set
of
keys,
described
in
two
places
and
then
what
happens?
B
A
That's
actually
that's
valuable
for
not
only
for
maintaining
the
documentation,
but
also
for
the
users
right,
because
if
you
have
basically
the
same
information
in
two
places,
but
they
both
say
different
things,
then
that's
a
very,
very
good
reason
for
confusion.
B
The
problem
is
mk
docs,
and
this
include
file
by
plugin.
It
kind
of
makes
it
easier,
but
it
won't
solve
it
completely
it
I
in
august
identifications,
I
ended
up
writing
call
code
that
creates
documentation,
and
things
like
that.
So
maybe
it
makes
sense
to
take
a
look
at
things
and
see
how
bad
like
how
bad
transition
is,
and
if
it's
difficult,
then
just
keep
keep
working
closely
with
the
dogs.
B
Yeah,
okay,
I
think
we
should
move
on
to
the
next
topic.
I
guess-
and
we
didn't
have
a
new
topic
since
last
meeting,
but
we
had
few
carryover
items
from
ux
meeting.
E
So
let
me
just
show
you
I
did.
I
did
want
to
ask
about
so
we're
trying
to
wrap
up
the
1.9
release
and
one
of
the
the
deliverables
we
have.
I
think,
for
that
is
getting
application
sets
as
a
optional
component
in
as
part
of
the
installation.
E
H
Sure
so
that
would
be
a
question
of
how
we
want
to
integrate
it
with
argo
cd.
My
assumption
is
that
we
would,
as
previously
discussed,
we
want
to
keep
it
standalone
for
the
time
being,
so
that
would
be
putting
out
a
release
of
application
set
controller
and
then
including
the
integration
of
the
two
via
a
shared
installation
file,
a
shared
dml
installation
file
in
the
manifest
directory
of
argo
cd.
Does
that
sound
about
right.
E
E
Cool
all
right,
it
sounds
easy
enough.
So
yeah,
I
think,
we'll
just
create
a
new
kind
of
maybe
like
a
customized
component
or
directory
that
had
the
application
set
in
manifest,
and
then
that
could
be
another
online
thing
that
they
can
add
on.
If
they
choose
to
install
upsets
yeah
right
yeah,
that's
that's
all.
I
was
wondering.
B
Thanks,
I
wanted
to
just
mention
about
reusing
repository
server
and
some
somehow
we
use
code
from
argo
cd
to
communicate
with
git
in
rcd
image
updater.
We
recently
saw
that
so
people
requested.
B
So,
just
to
kind
of
remind
what
we
did.
We
copied
code
from
argo
cd
into
image,
updater
to
communicate
with
git,
and
then
someone
noticed
that
in
argo
cd
we
we
are
adding
support
for
authenticating
authenticating
using
github
application
and
image
updater
won't
get
it,
and
I
think
it's
kind
of
it's
a
good
example.
It
shows
that
my
feeling
is
that
we
should
just
try
to
use
argo
cd
as
a
library
in
image,
updater
and
maybe
the
same
thing
can
be
done
in
application
set.
B
B
H
Be
terrible,
yeah
and
that's
the
direction
that
the
application
set
controller
has
gone
in.
For
the
most
part.
We
do
have
some
integration
with
rio
post
server,
but
my
guess
is
that's
going
to
be
removed
or
lessened
in
the
in
the
short
term.
G
B
A
Yeah,
I
think
we
we've
talked
about
that
already
right
so
and
we
we
also
agreed
on
that
jonathan
and
me
sit
together
for
for
a
couple
of
minutes
to
figure
out
how
to
integrate
the
things
that
we
need
into
the
into
the
git
code
of
our
city.
But
we've
not
had
the
time
yet
to
to
sit
together.
B
All
right-
and
I
did
want
to
share
that-
I'm
very
happy
with
a
result
of
a
blog,
so
I
just
wrote
a
simple
blog
about
argustine
notifications
some
time
ago
after
release
and
published
it,
and
it
worked
extremely
well.
I
just
I
can
see
it
by
number
of
questions
and
bug
reports
and
I
really
encourage
you
to
do
the
same
for
application
set
because
it
it
helps.
It's
like
it's.
B
It's
like
a
extremely
simple
way
to
welcome
people
to
start
using
the
project
and
if
we
publish
it
on
argo
approach,
it
I
think
it
kind
of
looks
like
blessing,
we're,
saying:
hey.
There
is
new
official
feature
of
in
argo
ecosystem,
and
this
is
how
you
can
use
it,
and
you
know
just
it's
enough
to
describe
just
the
happy
path
and
the
simplest
possible
installation
instructions.
F
I
have
a
question
coming
from
the
this
github
discussion
group.
I
think
we
got
an
answer,
but
this
is
about
security
patches.
What
is
our
commitment
to
to
support
releasing
security
pressures
for
for
our
releases?
I
think
we
got
an
impression,
but
I
think
I
think
the
person
is
looking
for.
Like
a
more,
I
told
him,
there's
no
there's.
No,
no,
we
don't
have
any
policy
written
up,
I
think.
Maybe
we
maybe
we
should.
F
Maybe
we
should
post
something
that
I
think
he's
looking
for
some
some
writing.
So
we
could
confirm
that
we
stopped.
We
support
one.
You
know
the
current
critical
release
and
the
one
above
right,
so
we
we
we
we
we
need
to
release
fixes.
I
think
you
see
he's
interested
in
disconcerting
the
security
purchase
more
than
other
thing,
any
other
bug
fixing.
F
So
what
I
wonder,
maybe
we
can
we
should.
B
B
I
think
right
now
we
comfortably
can
support
1.7
1.8,
because
we
just
recently
go
for
that
exercise
and
we
had
several
security
fixes
and
it
was
easy
enough
to
report
them
into
1.7.
Yes,
and
would
it
be
comfortable.
F
For
us
to
put
it
in
the
like
an
document
somewhere-
and
this
is
what
we
commit.
E
I
think
we
should
yeah
and
I
think
we
can
commit
to
n
and
n
minus
one,
but
that
doesn't
mean
that
if
the
fix
is
easy
enough,
we
we
can
always
go
above
beyond
all
right.
I
saw
that
recently
happen.
I
think
kubernetes
that
they
already.
E
You
know
there
was
a
security
fix
that
affected
something
out
of
out
of
their
commitment,
but
they
chose
to
backport
it
anyways
just
so
I
I
think
we
can
commit
to
n
and
n
minus
one
and
if,
if
make
a
judgment
call
if
we
can
go
further
on
the
security
fix
but
no
promises,
I
wouldn't
document
that
last
part,
though
just
then.
B
We
should
note
that
it's
only
applicable
to
unknown,
you
know.
Basically,
we
should
not
commit
to
blackboard
features
and
I'm
referring
to
so
we
have
no
limitation
like
token
expiration,
and
there
was
a
debate.
Where
should
we
cherry
pick
it?
So?
Basically,
if
security
fix
looks
more
like
a
feature,
then
we
should
not
try
to
cherry
pick
it
because
it's
just
looks
too
dangerous.
B
I
mean
in
arco,
cd
kind
of
we
started
building
it
and
we
discouraged
people
to
use
users,
built-in
user
management
and
mostly
reliable
sso.
Now
we're
getting
more
of
pushback
and
people
asking
to
fix
everything
possible
all
possible
issues
in
built-in
user
management.
B
It
might
be
that
tomorrow
we
will
get
another
big
thing
which
will
be
difficult
to
cherry
pick
yeah
and
I
I'm
not
sure
how
would
we
formulate
formulated
formulated
in
the
dogs,
but
hopefully
you've
got
what
I'm
saying
so
yeah
at
least
yeah
for
now,
like
we
recently
merged
support
for
token
revocation
for
admin.
I'm
really
scared
to
cherry
pick
it
into
bundles,
1.8
and
1.7,
because
it
works,
but
it
might
break
something
and
then
it
if
we
keep
it
in
1.9,
it
would
be
just
yet
another
patch
release.
B
B
E
It
would
also
put
maybe
the
security
dot
markdown.
I
think
that
would
the
right
place
to
document
our
position.
B
So
you
think,
okay
in
this
section,
which
is
specific
to
security,
okay
yeah-
I
am,
I
will
make
this
change
and
kind
of
promise
to
use
commitment
to
support
current
version
and
the
previous
version
at
least-
and
we
do
our
best
to
support
as
many
versions
as
possible,
like
you've,
seen.
E
F
If
I
look
at
the
document
of
the
user,
I
want
to
know
like
for
sure
or
what
kind
of
picture
I
will
get
if
I,
if
something
is
iffy
yeah,
make
it
yeah
yeah.
B
C
A
Want
to
volunteer
just
let
me
let
me
share,
please
some
experience
I
had
as
a
moderator,
because
I
think
the
moderator
should
not
only
focus
on
on
answering
questions,
but
also
to
revisit
the
existing
questions.
Whether
they
are
answered
some
some
people
they
are
coming
to
discussions.
They
they
ask,
they
get
answered
and
they'll
be
gone
right,
so
they
they
won't
mark
an
answer
as
answered
and
and
stuff
like
that.
There's
just
no
feedback.
A
Sometimes
they
they
come
up
and
say:
oh
thank
you
that
worked,
but
so
they
don't
mark.
The
answer
is
answered.
Okay,
so
I
think
this
is
something
a
moderator
should
also
do
right.
Look
look
through
the
existing
questions,
look,
whether
they
are
answered
and
if
they
are
answered,
but
they
are
not
marked
by
the
people
as
answered,
so
they
should
probably
select
the
question
that
was
answered.
A
I
I
went
through
many
of
the
questions
and
and
mark
them
as
answered.
So
obviously
I
have
not
marked
those
I
answered
so,
but
so
other
people
have
answered-
and
I
thought
yes,
that's
the
right
answer
and
it
hasn't
received
any
feedback
for
like
10
days
or
14
days
or
whatever,
and
so
I
think
this
this
should
be
something
we
also
should
do.
C
Yeah
and
then
you
would
also
need
to
have
some
privileges
to
be
able
to
market
answer
right.
I
don't
think,
like
everybody
in
this
group
who
volunteers
to
be
answering,
questions
may
not
have
the
privileges
to
mark.
They
could
have
discussions
as
answers.
So,
okay,
I
wasn't
aware
of
that.
C
Yeah.
I
think
you
need
to
be
like
you
need
to
have
specific
permissions
in
the
repo
we
have
to
close
issues
or
something
like
that,
but
yeah.
We
can
check
that.
I
think
in
in
general.
I
do
agree.
It
is
important
that
we
have
a
way
to
mark
closure
of
a
discussion,
it's
easier
for
others
and
not
have
to
handle
100
unanswered
questions
which
actually
has
been
answered.
If
you
go
in
so
but
in
principle
yeah,
I
think
we
should
take
a
look
at
that.
C
I
think
whoever
is
the
next
one
who
whoever
is
the
next
moderator,
should
probably
take
a
look
at
what
you
mentioned
and
see.
If
we
can
close
those
conversations.
F
I
actually
can
go
on
another
because
I
only
started
I
I
wasn't.
I
didn't
I
missed
the
last
meeting,
so
I
wasn't
sure
if
I
only
started
like
late
anyway,
so
I
think
yeah.
I
know
if
I
did
that
I'll
put
some
of
it.
So
I
can
I'm
okay
to
go.
Go
to
the
next
week
too.