►
From YouTube: Jenkins Governance Meeting October 31, 2022
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
Welcome
everyone,
it's
Jenkins
governance
meeting.
This
is
the
31st
of
October
2022.,
thanks
for
being
here
and
topics
on
the
agenda
that
I've
got
action,
items,
elections.
A
Cdf
topics
if
olig
joins
us,
antler
2
to
antler
for
progress
report
by
Basel
and
forum
and
Community
Topics
by
Gavin
and
Gavin
I,
put
a
couple
of
items
in
there
that,
if
you're
not
comfortable
with
them,
I
can
talk
to
them
as
well.
Anything
else
that
needs
to
go
on
the
agenda.
A
A
B
C
C
B
Herb
made
changes
to
make
it
more
customizable,
so
you
could
probably
do
more
stuff,
but
essentially
yeah.
It
doesn't
actually
like
create
a
nice
card
or
anything
it
just
does.
The
link
and
the
link
has
open
graph.
B
D
D
D
It's
going
as
a
blog
post
in
jenkins.io;
okay,
oh
good,
okay,
damn
putting
the
chatter
link
to
the
document
if
you
want
to
edit
it.
Thank
you
all.
D
A
continuous
document
you
know
so
there
is
a
previous
newsletter
and
then
we
have
the
draft
for
the
one
which
is
about
to
come
I'm
supposed
to
transform
that
into
a
nesky
dog
document
and
then
make
a
pull
request
on
Jenkins.
B
For
the
sake
of
when
we
post
this,
we
should
also
get
the
actual
link
to
the
last
one,
so
that
someone
can
go
view.
The
last
one
somewhere.
A
C
E
Yeah,
probably
people
so
yeah
for
kubecon
yeah.
There
was
a
CDF
for
Summit
today.
One
of
key
highlights
that
there
was
a
major
press
release
by
The
Continuous
delivery,
Foundation.
So
key
points
of
this
really
stickton
graduation.
E
E
Maybe
I
will
be
spending
some
time
in
the
coming
commands
for
that
unexpectedly
I
got
a
bit
more
time
than
I
planned,
but
yeah
so
yeah
and
the
last
is
Pierce
adoption.
So
basically,
what
is
important
for
the
ecosystem?
So
I
can
bet
that
jfrog
will
be
updating.
Where's
the
factory
plugin
to
support
peer,
settle
and
probably
a
few
a
few
more
patches,
so
stay
tuned
for
turbulence,
but
yeah.
F
A
Okay,
next
topic,
then
action
items.
Three
we've
got
community
jenkins.io
for
the
docs
mailing
list;
no
progress
but
I'm
back
from
vacation,
so
there's
a
better
chance
of
progress
than
there
was
two
weeks
ago.
A
Great
okay,
and
then
we
had
an
open
question.
Gavin
reminded
reminded
me
that
we've
had
questions.
Several
questions
come
in
in
various
places
in
the
community
about
multiple
application
servers
like
Tomcat
or
web
sphere
or
glassfish,
or
you
you
name
it,
and
right
now
we
have,
as
far
as
we
can
tell.
No
core
developers
are
actively
using
Tomcat
or
or
other
web
containers
other
than
the
web
container
that
we
ship
on
our
own,
and
so
the
thought
was.
Should
we
create
a
support
page
similar
to
the
Windows
support,
page
and
Linux?
E
Is
some
complicated
locations
with
it,
because
if
we
talk
about
the
web,
containers
that
are
Java
based,
they
Behavior
significantly
depends
on
the
version
of
java
Uranus.
So,
for
example,
when
we
were
releasing
Java
11
support
for
Jenkins,
we
did
some
testing
for
Apache,
Tomcat,
I
believe
and
for
build
fly.
E
So
this
is
what
we've
tested,
but
just
to
be
clear.
Even
acceptance
test
harness
framework
is
not
really
a
dead
degree.
The
Vocational
tissues,
then
so,
potentially
you
can
use
a
sentence
test,
harness
framework
or
PCT
or
customer
work
package
Azure
tests,
if
any
of
them
left
launch
with
another
web
container
and
see
what's
going
on,
but
we
have
exactly
zero
test
Automation
in
our
existing
pipelines.
For
that,
so
I
would
rather
ask
hard
question
for
the
recent
Java
versions
is.
E
Do
you
want
to
support
anything
beyond
JT,
for
let's
say
Java,
17
and
above.
A
Valid
question
and
I
think
I
think
I'm
biased
toward
the
answer
being
no,
but
that's
that
seems
like
that's
the
same
class
of
of
no
as
other
other
Linux
variants
that
we
don't
test
and
validate
it's
it's
a
platform.
Where
would
we
reject
a
pull
request
that
proposed
to
fix
something
on
behalf
of
one
of
these
web
containers?
We
don't
test
I
suspect
in
the
average
case.
We
would
not
reject
it,
but
we're
not
testing
it
for
sure.
E
Yeah
so,
and
so
how
much
of
an
issue
that
could
be
well
I
would
rather
just
call
in
the
community
and
ask
if
anyone
wants
this
support
and
ready
to
step
up
and
maintain
that
there.
B
Has
been
a
lot
of
chatter,
about
tomcat
and
I,
think
Wild
Wild
play
on
the
forums
the
last
month
or
so
a
lot
of
people
having
issues
some
going
back
a
lot
longer
than
that.
So
it's
it's!
You
know
if
that's
like
a
a
slice
of
what
people
are
actually
using,
then
I
think
enough.
People
using
it
to
make
a
fuss
but
I,
don't
know
who
would
be
maintaining
it.
B
C
B
What
I'd
like
this
idea
is
where
we
say
Windstone
is
level
one
anything
we
can
set
up.
Automated
testing
support
is
level
two.
We
could
put
a
note
saying
we
have
no
automated
testing,
we
just
could
and
anything
we
won't
support
our
tests
at
all.
You
know
is
proprietary
or
spend
cost
money,
or
something
is
level
three
and
I.
Don't
think
we
need
a
giant
chart
for
that.
We
could
just
literally
say
you
know
we
only
test
with
Winstone
or
something
like
that,
and
that
could
be
good
enough
right.
E
B
E
Versions,
yeah.
So
this
is
why
I'm
very
consistent
about
supporting
that
it's
basically
a
kind
of
worms,
all
kinds
of
compatibility,
because
we
still
have
libraries
which
are
in
Jenkins
runtime
and
division
tomcatra
on
the
time
and
the
except
different.
So
for
Java
11.
It
was
kind
of
pain,
but
well
at
least
the
project
was
updating
at
the
same
time
to
stop
of
java
11,
though
a
bit
behind
Jenkins.
E
B
E
B
Risk
it.
My
vote
is
to
update
the
system
requirements
page
and
say
we
only
regularly
test
with
Windstone.
Anything
else
is
community
supported
and
is
best
effort
by
community
members
or
something
like
that.
Just
because
I
want
something
to
be
able
to
point
to
say
you
know
at
one
point,
because
at
one
point
Tomcat
was
used
quite
heavily,
maybe
not
recommended,
but
used
quite
heavily.
And
then,
when
that
changed
there
was
no
there's,
nothing
really
to
point
at
to
say:
hey,
look,
we
don't.
We
don't
have
the
people
anymore
to
test
this.
A
Yeah
so
oh
like
does
that
I
guess
we
I
think
that's
a
good
for
me.
That's
a
good
proposal
to
say
what
we
test
right.
That
may
not
be
a
that,
may
not
be
as
definitive
as
the
support
page
but
saying
what
we
test
is
a
good
way
of
being
open
about
the
reality
of
what
we
are
testing
and
what
we
aren't
well.
E
You
don't
have
to
explore
well,
Windows
browser
or
even
Java
I
believe
Java
distributions,
but
yeah.
Historically,
what
we
supported
was
what
some
of
the
vendors
used
to
distribute
RVs,
so
basically
the
vendors
which
we
Distributing
Jenkins
and
if
we're
willing
to
commit
the
resources
to
maintain
this
particular
platforms
and
support
in
the
community.
We
basically
voted
along
with
this
policy,
which
makes
total
sense
because
there
does
not
be
ready
to
support
it.
Then,
okay,.
E
So
if
we
want
to
do
the
same
for
web
containers
and
perfectly
fine,
the
biggest
problem
would
be
some
of
deployments
because
yeah,
no
it's
hard
to
run
Jenkins
and
corporate
environments.
So
if
a
particular
web
container
is
mandated,
so
let's
see.
A
B
I
do
really
like
a
like
sentence
about.
Oh
God
now
can
I.
Remember
it.
We
we
only.
We
only
maintain
the
one
web
container,
but
vendors
are
welcome
to
step
up
and
support
other
containers
if
they
use
it
for
commercial
purposes
or
something
like
that,
because
you
know
I
think
we
want
to
clear
on,
like
I
think
we
want
to
put
heavy
push
and
nudges
on
people
to
contribute.
I'd
like
to
Mark's
comments
about
like
getting
very
aggressive
with
people
like.
B
If
you
want
to
use
TFS,
your
company
should
donate
resources
because
we're
not
fixing
it.
You
know
so
same
sort
of
thing.
I
think
we
should
be
really
heavy-handed
about
saying.
We
only
support
the
one,
because
we
only
have
so
many
people
and
anything
more
than
that.
We're
expecting
vendors,
maintainers
poor.
F
Yeah
I
wanted
to
mention
about
Tomcat
the
only
specific
thing
that
I
know
that
we
once
supported
that
we
no
longer
support
is
wanting
two
different
Jenkins
controllers
in
the
same
Tomcat
process,
but
that
is
a
clear
example
of
something
that
we
used
to
support
that
we
no
longer
do.
F
However,
I
am
not
aware
of
any
other
case
where
something
used
to
work
and
no
longer
works.
There
was
you
know
an
example
where
people
were
configuring,
their
Jenkins
home
inside
of
Tomcat
a
certain
way,
and
we
dropped
support
for
that
in
favor
of
a
Java
argument.
But
once
you
use
the
job
argument,
you
can
still
do
what
you
were
doing
before.
So
you.
F
Some
of
the
links
that
I've
seen
about
people
having
trouble
with
other
web
containers
seems
to
be
user
error
in
the
sense
of
some
people
are
trying
to
use
the
Jenkins
War
file
with
a
web
container
that
is
using
the
Jakarta
Imports
rather
than
the
Java
X
Imports,
and
so
that's
that's
just
a
matter
of
using
the
wrong
version
of
the
servlet
container.
We
don't
have
any
documentation
for
this
because
it's
not
supported,
but
this
could
be
a
good
way
for
people
who
are
interested
in
contributing
to
start
by
just
documenting
okay.
F
B
C
B
F
So
I
think
documentation
would
go
a
long
way,
but
that
isn't
documentation
that
any
of
us
could
provide
if
we're
not
actively
using
that
server
container.
But
it
would
be
great
to
have
contributions
from
people
who
are
using
it
and
documentation
will
be
a
great
place
to
start
I.
Think
because
I
think
for
the
most
part
it
should
be
doable.
If
you
pick
the
right
version,
if
you
configure
the
home
directory
in
the
right
way,
should
be
possible
to
use
Jenkins
on
just
about
any
servlet
container.
F
A
Nope,
okay,
next
topic,
then,
is
elections,
so
the
blog
post
has
been
has
been
made
made
visible.
It's
available.
It
came
out
on
the
20th
talking
about
the
phases
of
the
election
Etc.
Voter
registration
has
started
and
will
continue
for
another
two
and
a
half
weeks.
Then
voting
and
Then
followed
by
results.
Announcement.
A
Gavin
and
Evelina
are
both
on
the
board
up
for
reelection
all
officers,
so
infra
doc,
security
Etc
are
all
up
for
re-election
events
and
there's
a
link
that
Gavin
you
had
included
to
Damien's
proposal.
I
assumed
that
the
blog
post
superseded
The
Proposal
that
wasn't
my
I
link.
A
B
I
was
thinking
about
it.
Do
we
want
to
I
mean
I
know
when
Mark
came
on
board
and
to
some
degree
when
I
came
on
board
there
was
some
transition
issues,
you're
trying
to
figure
out
where
and
how
and
what
to
do?
B
B
The
two
GitHub
groups,
the
infra
and
the
C,
and
the
CI
board
groups-
I,
don't
know
what
else
we
actually
do,
but
it
might
be
worth
writing
this
down.
One.
C
A
Yeah,
the
infra
officer
and
the
security
officer
in
particular,
have
access
to
lots
of
very
sensitive
stuff,
and
it's
probably
a
good
idea.
Let's
capture
that
I
hope
we
persuade
both
of
them
to
be
nominated,
the
current
officer
to
be
nominated
again,
but
but
one
way
or
the
other
it's
healthy
for
us
to
describe
what
are
the
things
that
we
need
to
be
sure
they
they
have
access.
They.
E
Well,
not
really
so
I
know
yeah
there
you'll
be
a
governing
board
meeting
in
the
middle
of
November.
It
wasn't.
C
C
E
Follow-Ups
now,
yeah
I
do
have
some
private
news,
but
I
will
share
it
with
the
team
later,
but
yeah
basically.
B
The
the
signing
thingy.
A
E
Oh
yeah,
so
for
LFX
Community,
which
is
also
a
baby
backend.
There
is
some
time
for
us
to
decide
whether
we
move
out
or
not
as
a
foundation,
so
I
guess
the
deadline
would
be
January
or
February.
A
E
Oh
baby,
oh
I'm,
sorry
right!
So
there
should
be
little
to
no
input
on
Jenkins.
Yes,
I
create
a
chapter
there.
We
try
to
host
a
few
webinars
so
basically
hit
the
wall
with
some
of
the
issues.
Because
of
the
pricing
plan
and
taking
the
limitations,
we
discovered
the
barely
makes
sense
to
press
it
there.
E
B
Right
yeah
because
I
was
going
to
say
like
the
same
thing
with
Matrix
is
they're
all
designed
to
be
self-hosted
and
one
of
the
issues
is
namespaces.
So
like
we
getting
a
mastodon
account
is
easy.
You
can
get
it
on
any
of
the
number.
Thousands
and
thousands
of
servers,
but
I'm
wondering
if
links
Foundation
has
any
intention
of
running
a
CDF
or
Linux
Foundation
Mastodon
for
their
projects.
B
It
wouldn't
be
a
SAS
per
se.
It's
like
would
be
a
Twitter
type
thing
right.
E
Yeah,
so
it's
basically
distributed
yeah,
so
everyone
hosts
their
own
location
and
there
is
just
whatever
central
registry
yeah.
B
So
something
like
you
know,
Jenkins
at
Linux
foundation.io
makes
a
lot
or
Linux
said.
I,
don't
know
what
domain
is.
It
makes
a
lot
more
sense
than
you
know,
Linux
at
Mastodon
the
chat
you
know:
okay,
yeah.
E
So,
for
us
is
basically
the
question
of
how
we
post
it.
What
is
the
price
of
this
host
link
in
principle
I'm,
not
against
the
Mastodon
for
sure.
B
It's
a
message
on
itself:
is
a
rails
app,
so
it
needs
the
database
and
the
web
server.
It's
a
pretty
tiny
little
ask,
but
it
also
brings
up
the
whole
like
Matrix
issue.
I
was
gonna,
go
make
up
a
space
which
is
a
like
a
a
collection
of
rooms
in
Matrix
and
someone's
already
claimed
Jenkins
at
matrix.io.
B
A
B
So
that's
all
I'm
bringing
up
is
this
might
be
things
like
they're,
relatively
small
things
that
I'm
sure
even
the
element
team
could
host
Matrix
one
or
you
know
Linux
Foundation
could
easily
spin
up
a
VPS
with
Macedon
on
it.
It's
pretty
easy
to
Launch,
so
just
things
that
we
should
probably
bring
up
at
some
point.
E
E
B
But
like
if
the
Macedon
one
was
only
for
Linux
Foundation
projects
and
not
users,
then
it
would
be
a
lot
smaller
scale
but
yeah.
It's
not
something
I'm
going
to
bring
up
I.
E
There
would
be
no
difference
from
community.jenkins.io,
then
I
mean
like
no
practical
difference
right.
E
C
C
F
Yeah,
so
in
the
last
two
weeks,
Alex
L
and
I
have
been
co-authoring
a
change
to
complete
this
task
and
it
was
merged
yesterday
towards
this
weekly
release.
With
that
we
can
close
the
ticket
and
declared.
F
F
E
Yeah
one
question
about
the
so:
the
threat
and
the
budgeting
request.
Taking
this
pull
request:
where
do
we
stand
there?
Do
we
want
to
proceed
with
the
budget
request
or
do
we
put
it
on
hold.
F
F
A
A
B
Yeah
so
I'm
just
looking
at
the
notes,
because
I
don't
have
any
of
the
forms
that
didn't
really
support
heavy
the
last
couple
of
months.
B
So
there's
not
really
anything
interesting
to
bring
up
so
yeah
October
5th
Fest
is
today
I,
really
like
the
the
stats
of
JM
JMM
has
been
posting,
it's
really
kind
of
cool.
How
many
people
are
doing.
You
know
the
first
PR's
ever
with
Jenkins
I,
don't
know
where
I
last
thought
I
think
I've
received
Channel
just
listed
there.
C
B
October
Channel
yeah,
but
it's
still
a
large
percentage
of
people
who
have
never
submitted
to
open
source
before
have
done
a
lot
of
work
in
Jenkins.
So
it's
really
nice
to
see.
E
So
I
guess
it's
mostly
because
of
Oktoberfest.
What
do
you
see
large-scale
contributors
joining.
B
James
that
are
really
only
about
hetoverfest
things
have
been
labeled
head,
overfest
and
things
that
happened
this
month.
So
I
don't
know
if
there's
a
technically
distinction,
I
think
any
PR
in
a
repo,
that's
labeled,
hackover
fast
is
considered
that.
B
A
Yeah
I
was
I
was
really
pleased
with
this.
This
to
oh,
like
to
your
question.
This
graph,
that's
maintained
by
the
Linux
foundation
for
us,
shows
a
nice
boost
of
from
about
640
in
at
the
end
of
September
to
over
700
at
the
end
of
October,
as
their
count
of
contributing
developers
to
the
Jenkins
repositories
in
total.
A
Now,
I
think
that
number
is
actually
quite
a
bit
lower
than
John
Mark's
number
I
think
he
sees
on
the
order
of
a
hundred
independent
developers
that
he
could
see
with
submitting
hacktoberfest
submissions,
but
their
numbers
say
at
least
60
of
those
are
are
new
and
had
never
may
have
never
contributed
before.
B
Yeah,
so
he
last
posted
on
Wednesday
I
found
it
there's
535
eligible
for
Oktoberfest
by
111
different
contributors.
B
A
A
Super
thanks,
I
had
put
this
number
in
just
because
I've
been
interested
in
pipeline
graph
view.
Gavin
and
I
have
had
conversations
about
blue
ocean
and
pleased
to
see
that
some
months
it's
gone
up
by
100
installations
per
month,
and
it's
done
that
for
the
last
several
last
two
or
three
months
done
very
nicely
so
pipeline
graph
view.
Plugin
gives
us
hope
that
blue
ocean
is
not
the
only
way
to
visualize
pipelines
in
in
Jenkins.
It's
working
great
for
me
and
it's
running
on
ci.jenkins.io
it
it's
quicker
than
blue
ocean.
B
I've
actually
been
thinking,
I
might
submit
a
PR
to
it
to
add
notifications
so
that
you
could.
You
could
like
have
a
checkbox
on
the
bottom
of
the
page.
That
says,
notify
me
when
this
build
is,
is
done
or
like
per
build
or
even
per
project,
because
that
was
one
of
the
ones
I
have
for
one
of
my
old
plugins
that
I
don't
necessarily
want
to
maintain
and
it'd
be
nice
to
add
it.
To
this
thing,.
A
D
Because
it
has
been
also
crazed
on
Twitter
these
days
with
purchase
of
Twitter
lots
of
people,
I
follow
are
going
on
masterton
and
so
I
did
that
also
today,
I'm
not
leaving
Twitter
but
I
have
masterton
can
just
in
case
and
I
also
experienced
the
cross-busting.
You
know
I
just
set
up
something
with
a
website
that
correspassed
whenever
I
tweet
something
it
goes
then
on
methadone.
B
Yeah
I've
been
doing
that
for
years.
The
same
thing:
I'm
thinking
as
action
items
for
this
someone,
either
someone
from
the
board
or
someone
from
infra
to
talk
to
one
of
the
master
and
hosts
about
maybe
getting
a
sponsored
install
for
Jenkins.
B
B
Yeah
so
I
just
did
a
quick,
Google
search
and
there
are
post
solutions
for
both
so
I
think
it's
worth
reaching
out.
I
don't
know
if
we
want
to
pay
big
money
for
them,
but
even
if
it's
a
small
monthly
cost
that
we
might
be
able
to
put
on
a
budget.
B
The
new
hosting
crew
is
doing
really
well
I
brought
it
up
last
meeting,
but
Alex
B
is
is
just
owning
this
and
answering
all
the
hosting
requests
and
both
Alex's
are
improving
the
process.
Quite
a
bit.
Updating
documentation,
upgrading
the
IRC
bot,
it's
a
lot
smoother
than
when
Tim
and
I
were
doing
it
part-time.
So.
B
The
only
other
things
I
was
going
to
point
out
were
things
I
mentioned
in
the
newsletter,
but
and
I.
Don't
remember
if
I
mentioned
last
week,
but
accounts.jenkins.io
has
gotten
not
only
a
facelift
but
a
cleanup,
so
it
should
be
a
little
bit
more
reliable,
I
think
we're
going
to
just
put
in
the
newsletter
more
about
the
facelift
itself,
but
I
think
a
short
of
email.
B
I
think
we
could
probably
make
email
more
reliable,
too,
and
that
should
probably
because
we've
been
putting
it
off,
because
we
thought
we
were
switching
to
the
other
service
that
I
can't
remember
the
name
of,
and
that
doesn't
seem
to
ever
happen.
So
it
might
be
worth
just
fixing
up
accounts
now,
so
between
Tim
Alex
and
myself,
we
got
it
deployed
by
you
know:
Docker
container
CI
Tim
did
a
lot
of
it,
but
CI
the
UI
is
fixed
yeah.
A
A
A
Right
well,
although
I
like
wiki.jenkins.io,
because
of
what
it
what
it
shows
as
the
as
the
top
level,
let's
see
if
I
can
find
one
sample
page.
Oh
the
one
that.
B
B
General,
thank
you
to
everyone.
Who's
been
stepping
up
on
the
community
pages.
B
I
know,
Alex
and
Bruno
have
been
helping
out
quite
a
bit.
I've
slowly
slowed
down
I
get
exhausted
by
answering
all
the
support,
tickets
and
I'd
love
to
see
everyone
else,
step
up
and
I
can
step
in
once
in
a
while.
Instead
of
burning
myself
out
answering
things
so
yeah.
D
By
the
way,
Kevin,
where
are
you
the
one
who
created
the
template
to
answer
the
same
question?
We
got
regularly
yeah?
Oh
thank
you.
Thank
you.
So
much.
B
I
think
I
think
I
crowdsourced
it
early
on
but
yeah.
That
being
said,
it
did
just
change,
so
it
might
be
worth
at
the
end
of
the
video
of
showing
that
off,
because
we
can
make
it
easier
for
people
to
submit
changes
and
ideas
and
posts
and.
A
B
So
I
don't
know
where
they
put
it
because
I
don't
use
this
view,
but
so
yeah
like
they
added
a
new
templates
category
and
put
all
the
templates
in
there
so,
instead
of
it
being
like
hidden
in
deep
in
menus.
B
Okay,
any
any
top
level
Post
in
this
form.
So
all
five
of
those
are
considered
Canon
responses.
You
can
reply
to
them,
so
people
can
actually
it's
opened
it
right
now.
This
category
is
open
to
anyone.
We
can
lock
it
down
or
open
it
up,
but
you
can
reply
to
them
say
hey.
Can
we
change
this?
That
kind
of
thing
we
can
actually
give
it's
all
category
management,
so
it's
now
easier
to
give
out
access
to
people
who
can
post
new
ones
or
edit
old
ones.
B
That
kind
of
thing
it
used
to
be
this
really
hacky
groupy
thing.
We
could
probably
delete
that
one.
The
last
one
yeah.
B
It
should
be
a
lot
easier
to
add
more
of
them
now
because
I
know
I,
think
Mark
made
the
Linux
transition,
one,
which
is
very
nice.
It
was
just
easy
for
us
to
just
do
it
but
yeah.
So
this
is
very
easy
for
people
to
add
more,
do
and
I
encourage
people
to
add
more
to
because
it
at
some
point,
it's
getting
frustrating
to
answer
the
exact
same
questions
over
and
over
again.
So.
D
Right,
oh
wait,
no
maybe
I
did
I
haven't
yet
used
any
one
of
them.
So
it's
just
a
copy
paste
or.
B
It's
easier
than
that
Mark.
Do
you
want
to
go
to
reply
to
something
sure.
A
A
B
Great
yeah
they're,
nice
and
easy.
It's
a
really
good
nice
feature
of
discourse.
If
you
hit
close
Market
It'll,
ask
you
yeah.
B
So
I
encourage
people
to
submit
more
of
them.
I
don't
know
currently
who
has
access
to
write
to
that
category,
but
it's
very
easy
to
change.
If
someone
has
wants
access
to
it
so.