►
From YouTube: Jenkins Governance Meeting November 28, 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:
this
is
the
Jenkins
governance
board.
It's
November,
28
2022.,
welcome
to
new
members
of
the
board,
Julie
Hoffner
or
new
members
of
the
award
board,
beginning
December
3rd
Uli,
Hoffner
and
Alex
Brandis,
a
special
thanks
to
Gavin
and
to
Evelina
who
will
be
exiting
the
board
and
we
hope
we'll
stay
deeply
involved
in
Jenkins
in
continuing
forward
with
us
topics.
I
have
news
action
items,
elections,
governance
board,
meeting
time
and
date
and
CDF
Outreach
reboot.
A
B
And
you
skip
that
part,
but
the
governance
meeting
time
would
be
a
topic
I.
A
A
A
A
Okay.
Next
item,
then,
is
action
items
action
items
we
have
several
that
carried
over
from
last
time.
Only
to
follow
up
on
this
I
had
failed
to
do
it
last
time
we'll
do
it
this
time
create
an
empty
agenda
entry
for
the
next
meeting
after
the
end
of
each
meeting,
we're
also,
we
discussed
in
last
governance
board
switching
from
the
concept
of
sub-projects
and
special
interest
groups
to
a
single
concept.
A
Working
groups
and
I'll
submit
a
pull
request
to
www.jenkins.io
to
match
that
olegs
got
the
action
item
to
send
a
proposal
to
Rick
to
retire
the
Chinese
Jenkins
site
because
it
is
badly
out
of
date.
A
Then
Gavin
and
I
have
the
action
item
to
Archive
the
governance
meeting
notes
to
a
GitHub
repository
for
permanent
archive,
because
if
you
look
at
the
scroll
bar
on
this
Google
doc,
you'll
see
that
this
is
hundreds
of
is
over
100
pages
long.
It's
becoming
unwieldy,
so
we
want
to
switch
it
to
a
more
more
permanent
location
than
Google
Docs.
B
Can
I
ask
a
question
about
the
topic
before
because
I
think
you
are
publishing
the
agenda
after
the
meeting
in
our
community,
so
I'm
wondering
why
we
should
record
the
same
thing
in
this
document.
Additionally,.
A
C
B
A
C
A
I
I
haven't
I,
haven't
created
one
and
either
you
or
I
can
do
it.
I'm
I'm
fine,
with
either.
A
A
A
On
the
one
hand,
we've
got
quite
a
number
of
users
who
are
saying
hey
it
works
for
me
and
on
the
other
hand,
we've
got
core
developers
who
say
none
of
us
test
it.
None
of
us
verify
that
it
works
on
these
other
containers,
we're
not
willing
to
support
it
and
Jesse
Glick,
just
posted
a
note
saying-
and
there
are
some
crucial
things
like
like
websockets-
that
are
expected
to
not
work.
So
so
there's
it's
an
open
point
for
discussion.
A
C
Think
on
the
download
you
can
go
on
the
download
page
and
say
anything
other
than
the
one
that
we're
using
is
not
tested,
and
then
it
sounds
like
they're
based
on
the
previous
jab.
There
should
be
a
jab
to
fully
do
to
kill
the
old
one.
The
other
ones
right,
I,
think
those
are
two
different
problems.
A
A
That's
good,
because
I
like
that,
that's
one
that
Basel
had
guided
me
on
previously.
When
we
were
describing
operating
system
support,
his
preference
was,
let's
say
what
we
actually
test
in
Automation
and
that
way
people
know
hey.
This
is
is
covered
by
automated
tests.
If
it's
not
covered
by
automated
tests,
we
should
state
so.
A
D
A
C
C
Is
is
that
gettable?
Could
we
expand
the
Telemetry
stuff
to
report
that
information
honestly.
D
C
I
was
going
to
say
also
for
me,
so
we're
going
to
do
one
PR
that
just
make
sure
we
State
what
the
current
state
is.
It's
probably
worth
mentioning
on
there
saying
unless
we
find
a
maintainer
It's,
Gonna,
Get,
Well
I
know
it's
worse
as
bad
as
never
mind.
C
A
That
we
I
don't
think
we
need
to
State
the
current
situation.
Plus
offer
the
threat.
The
threat
will
come
as
by
virtue
of
the
separate
task
to
decide
the
future
of
web
application
server
support,
because
I
I
think
Jessie's
right
that
if
we
don't
support
websocket-
and
there
are
probably
other
things-
we
don't
support
and
Main
and
our
core
developers
don't
develop
on
it
or
or
test
it.
It's
tough
to
claim
support
for
it
right.
It's
tough
to
argue
that
it
should
be
supported
even
so.
D
Mark
for
that
list
of
support,
but
that
support
Matrix
were
you
considering
something
like
what
we
do
for
the
Linux
support
Matrix,
where
there's
three
levels
supported
patches,
considered
and
unsupported?
Was
that
the
structure
that
you
were
thinking.
A
Of
use,
that
was
the
structure
I
was
considering,
and
what
Jesse's
Jesse's
comment
back
was
hey
I.
He
thinks
that
there's
there
are
really
only
we
support
it.
We
we
test
it.
We
support
it
and
everything
else
and
that's
where
I
think
there's
some
discussion,
because
I
I
was
thinking
three
tiers
and
the
way
Jesse
described
it.
Maybe
maybe
what
I
can
do
is
show
Jesse's
description
or
we
could.
We
could
have
people
read
it
separately.
It's
a
post
to
community.js.
D
D
C
C
Okay,
three
is
unsupported,
so
oh
yeah,
but
I
think
Jesse's
point
was
that
like
Tomcat
would
be
flat
out
dropped
yeah,
but
for
now
yeah
I
think
before
that
even
happened,
I
mean
that's
part
of
the
jab
is
how
to
how
to
deal
with
it
but,
like
Administration,
monitor
to
say,
hey
you're,
on
an
unsupported
container.
You
know
in
the
future.
This
will
go
away.
C
That
kind
of
thing
you
know,
but
for
now
I
think
the
big
thing
is
we
get
form
topics
and
now
I've
identified
two
problems
with
Tomcat
alone,
and
we
have
nothing
to
point
to
and
be
like
here's
some
known
problems.
You
know
this
is
why
you
shouldn't
do
anything
like
that.
Even
if
it's
just
a
blog
post
would
be
probably
good
enough.
D
Right
so
I
think
tier
one
would
obviously
be
Jetty
in
the
form
of
Winstone
and
then
I
think
tier
two,
which
is
you
know,
patch,
is
considered
I,
think
that
would
be
that
would
be
using
Tomcat
or
wildfly,
maybe
that
third
one,
maybe
glass
fish
in
with
all
the
with
all
of
the
the
asterisks.
All
the
prerequisites
like
use,
the
right
version
of
and
set
the
Jenkins
home
the
right
way
and
by
the
way
websocket
doesn't
work
and
all
of
the
asterisks
I
think
that
would
be
tier
two.
D
In
other
words,
we
don't
test
this,
but
patches
are
welcome.
If,
if
you
want
to
document
this
or
if
you
think
it
should
be
approved
somehow,
and
that
and
and
that
kind
of
matches,
our
Linux
policy
right,
Mark.
A
It
does
those
are
the
those
are
the
three
kinds
of
layers.
It's
tier
one
is
hey,
we
test
it
with
Automation
and
we
expect
it
to
continue
working
tier
two.
We
don't
test
it
with
automation,
but
we're
willing
to
consider
other
people's
proposals
to
patch
something
in
tier
three
vendor
doesn't
support
it.
We
therefore
flatly
and
will
not
accept
any.
D
I
think
tier
three
in
this
context
is
like
using
Java
ee,
the
wrong
version
of
java
ee,
which
we
just
don't
support
at
all
right
or
any
other,
certainly
container.
Besides,
you
know
those
two
that
we
met.
Those
two
are
two
or
three
that
we
just
mentioned.
D
Does
that?
Does
that
seem
like
a
good
analog
to
the
Linux
policy?
Yes
yeah
so
Gavin
does.
That
is
having
a
clear
statement
like
that.
Do
you
think
that
would
be
sufficient
to
a
lot
to
clarify
the
situation
for
users.
C
A
A
Yeah
and
I'm
I'm
prone
to
so
I'll
I
can
I
can.
If,
if
the
this
three-tier
pattern
doesn't
doesn't
get
agreement
from
people,
I'll
certainly
submit
a
second
pull
request
with
the
stating
that
we
don't
don't
test,
because
at
least
that's
describing
it
I
like
the
three-tier,
because
we've
already
got
Windows
Linux
and
what
is
one
other.
Oh.
E
A
A
The
next
topic
is
elections,
so
welcome
Uli,
welcome,
Alex
new
board
members,
beginning
December
3rd.
Thank
you
very
much
in
advance
two
years
with
us
we're
delighted,
Uli
returning
Alex
first
time,
member
of
the
board
great
to
have
you.
Both
I've
submitted
a
proposal
to
change
the
rules
for
next
year's
elections,
and
that
proposal
has
gone
out
to
the
Jenkins
developer
list
and
is
proposed
to
jenkins.io
as
a
pull
request
any
comments
or
concerns
for
for
new
for
others
on
what's
proposed
there
or
how
to
deal
with
it.
A
So
today
the
rules
prevent
a
second
cloudbees
employee
from
serving
on
the
board,
because
we
have
the
the
overarching
rule
that
no,
we
cannot
have
any
company
have
a
majority
of
people
from
a
single
company
on
the
board
so
because
kosuke
is
considered
affiliated
with
Cloud
bees,
even
though
not
ultimately
employed
by
Cloud
bees.
He
counts
as
one
as
a
permanent
board
member
I
count
as
the
other,
and
therefore
we
couldn't
have
a
third
cloud-based
person.
What
this
proposes
to
do
is
says
the
perm.
We
don't
count
the
permanent
board
members
affiliation.
A
A
Yeah
I'd
have
to
read
the
I'd,
have
to
read
the
the
bylaws
I.
Don't
think
so.
A
B
Think
there
is
a
risk,
but
actually
yeah
I
never
have
seen
anything
bad
from
cloud
peace
right
now.
So
it's
just
a
risk.
E
Yeah
just
to
add
something
real
quick
to
that
I
mean
KK,
has
a
permanent
seat
on
the
board
and
two
Club
piece
employees,
and
you
said
two
employees
from
one
company
I
one
subject
that
necessarily
to
Cloud
peace.
Only
like
we
don't
know
what
happens
in
the
future-
and
we
know
from
the
past
that
not
only
club
with
members
were
board.
Members
see
Kevin,
CE,
Oleg
and
other
members
from
the
past,
burned.
C
So
for
context,
Mark's
Mark's
thing
is
specifically
removing
the
restriction
for
elected,
so
I
mean
the
all
of
us
on
this
call.
Oh
all
the
board
members
on
this
call
are
elected
right,
Costco
is
the
only
one,
that's
not
elected,
so
all
he's
suggesting
is
dropping
that
requirement
from
the
elected
or
from
the
non-elected
members.
So
that
means
Costco
would
not
be
included
in
the
Restriction
of
only
to
two
members
from
a
single
company,
I'm
gonna,
say
flat
out
I,
don't
think
this
should
be
decided
tonight.
C
I
think
Mark
sent
out
the
email
and
I
think
it
should
be
discussed,
but
the
other
thing
was
the
reason
it
came
up
was
we
were
having
trouble
finding
potential
board
member
candidates
a
lot
of
the
community
members
right
now
are
either
not
interested
or
from
cloud
bees,
and
that
really
restricted
it
was
considering.
You
could
only
have
one
cloudy's
member
on
the
board.
D
It's
like
another.
Another
factor
is
that
kasuke
has
been
steadily
shifting's
Focus
over
the
past
few
years,
since
these
rules
were
originally
written,
he's
gone
from
doing.
Every
single
weekly
release
and
being
an
executive
at
Cloud
B
is
into
kind
of
Shifting
his
Focus
to
his
new
company
and
we've
slowly
been
transferring
all
of
the
repositories
from
his
organization
into
the
Jenkins
organization,
and
there's
been
this
very
natural
shift
of
focus
for
him
onto
his
next
Endeavor.
D
So
I
think
we
we're
trying
to
do
two
things:
we're
trying
to
honor
his
foundational
contributions
in
the
past,
but
also
acknowledging
that
the
project
is
functioning
independently
in
this
next
phase.
That
includes
less
and
less
of
casuke's
involvement
every
as
each
year
goes
by
and
I
think
that's
a
very
natural
and
healthy
evolution
of
the
project
and
one
which
Kaskade
himself
has
written
about
many
times.
That
he's
pleased
to
see
things
graduating
from
his
nest
into
their
own.
Blossoming
self-sustaining
system
and
I.
B
I
understand,
there's
a
reasoning
and
I
think
we
can
continue
the
discussion
on
the
mailing
list.
Yes,
yeah,
yeah
and
I
was
I.
Think
it's
not
about
kosuke.
It's
about
the
50
was
50,
so
I
think
a
kosoki
did
not
yeah
yeah.
He
did
not
really
participate
in
the
last
two
or
three
years.
So
I
think
we
only
have
four
members
and
if
a
company
has
50
now
they
can
block
everything.
B
So
that's
a
thing
we
should
be
aware
of,
and
that's
for
me
a
risk
that
we
now
have
a
situation
where
we
would
like
to
decide
something
and
a
company
can
say
no
I.
No,
we
don't
want
to
have
it
and
then
we
have
a
situation
where
we
have
two
seats
from
one
company.
That
can
say
everything.
No
and
that's
a
risk
for
me
I'm.
C
B
C
B
A
Overall
and
I
think
that's
a
valid
point,
but
I'm
not
sure
actually
that
there
that
risk
is
real
in
this
case,
because
if,
let's
say
an
arbitrary
company
gets
two
seats
on
the
board,
that's
only
fifty
percent
of
the
four
active
members.
If
there's
a
conflict,
kosuke
will
step
in
as
a
board
member
and
resolve
the
conflict.
So
we
still
have.
We
still
have
a
safeguard
in
that
kosuke
is
a
safeguard
and
he
he
actually
was
expressed
his
opinion
on
this.
A
C
Okay,
that
reminds
me,
though,
do
you
do
Lily
and
and
Alex
want
to
send
me
an
email
and
I'll.
Add
you
to
the
board
mailing
list,
just
whatever
email
you
want
added
to
the
list.
I
will
add.
A
Very,
very
good,
well
and
and
I
had
an
action
item
from
our
meeting
two
weeks
ago
to
get
a
see
if
there
was
a
private
statement
that
kosoke
was
willing
to
share
in
terms
of
his
involvement
with
Cloud
bees
right
now,
I've
got
that
statement
and
I'll
send
it
to
the
board
for
all
of
you
to
read
as
board
members.
It's
not
something
I'm
ready
to
share
publicly
I
didn't
get
an
authorization
to
share
publicly,
but
I
think
it
states
in
general
terms
his
involvement.
A
Great
all
right,
so
so
that
one
anything
else
on
the
proposed
rule
changes
will
continue.
Discussions
in
the
mailing
list
allow
those
condition.
Can
those
discussions
to
reach
their
logical
conclusion,
whatever
that
may
be
hear
the
voices
of
of
community
members
and
bring
it
up
again
in
two
weeks
or
in
four
weeks
in
our
next
board
meetings.
A
Great
okay
next
item
was
that
elections
are
complete
thanks
to
Gavin
and
Evelina,
welcome,
Uli
and
Alex
and
permission
changes
so
Alex
or
Gavin.
You
said:
send
email
to
Gavin
to
become
a
board.
A
member
of
the
board
of
the
board
mailing
list.
C
The
immediate
ones
come
to
mind
are
GitHub
teams,
so
both
Jenkins
CI
and
Jenkins
infra,
mostly
to
approve
any
changes
to
jinxeo.
That
needs
board
approving
all
right
right.
Technically,
the
CL
CC
and
the
CLA
stuff.
But
that's
still
messy
I'm,
just
checking
to
make
sure
I
can
add
I,
don't
think
I
can
add
people
to
oh
I
can.
E
Yeah
I
think
we
couldn't.
We
can
neglect
the
CLA
and
icla
stuff
for
now,
at
least
until
we
fully
switch
to
the
LFX
solution,
because
if
I
remember
correctly,
only
Oleg
has
the
key
to
actually
decrypt
the
PDFs.
So
yeah.
E
C
C
So
yeah
again,
once
you
send
me
an
email
I'll,
add
you
to
the
GitHub
teams
as
well
looks
like
I
can
do
that
and
then
the
only
other
one
that
I
still
don't
have
access
to
is
the
LFX
crowdfunding
thing,
but
that's
a
bit
of
a
mess
because
crowdfunding
doesn't
support
multiple
people,
so
it's
kind
of
awkward
and
then
anyone
who
doesn't
have
it
and
wants
it.
Mark
can
help
you
set
up
for
zoom
all.
A
Right
right,
Zoom
meeting
password:
yes
exactly
so
the
zoom
account
password.
If
you
need
to
host
a
host
a
meeting
with
the
the
Jenkins
project,
Zoom
account,
we
have
a
process
to.
A
C
Good,
okay,
those
are
the
only
ones,
oh
and
then
technically
one
password,
though
we're
not
really
using
it.
C
Oh
actually
so
Community
drinks,
Io
Io,
all
black,
Olivia
and
I-
have
been
admins
forever.
I,
don't
mind
staying
as
demon,
but
do
we
want
to
make
sure
all
board
members
have
like
moderation,
access
or
anything
like
that?
That's
more
of
a
discussion
and
not
something
on
me,
but
that
is
something
I'm
thinking
about
whether
or
not
that
should
be
done.
C
I
I
think
at
the
very
least
board
members
should
be
able
to
delete
a
post
because
I
think
that's
when
you
step
in
for
any
any
wow
Community
guidelines,
whatever
that
word
is
anytime,
that
it
has
to
be
done.
I
think
the
Board
needs
to
be
able
to
step
in,
but
I,
don't
know
what
you
want
to
do
for
this.
So.
A
I
I
like
that,
okay,
so
we
we
had
an
episode.
What
was
it
six
months
ago,
maybe,
where
I
ultimately
phrased
a
posting
that
I
made
to
community.jenkins.io,
saying
I
am
acting
as
a
member
of
the
Jenkins
governing
board
and
I
am
declaring
that
what
you
did
is
contrary
to
community
our
community.
A
And,
and
that
was
me
acting
as
a
board
member,
so
I
think
I
I
would
love
to
have
Uli
and
Alex
also
have
moderator
access
just
to
to
help
with
that
in
case,
I
missed
something
Alex
Uli.
What's
your
what's
your
opinion.
B
I
think
this
is
a
really
good
idea,
so
I
think
it
would
be
really
helpful
to
yeah
to
remove
posts
or
mark
them
as
invalid.
B
C
Still
planning
on
working
on
that
project
to
move
everything
into
Matrix
because
we
have
full
control
in
Matrix.
We
don't
have
full
control
and
getter.
Okay,
I,
don't
have
even
access
together,
I,
don't
know
who
does
I
think
Mark
might
be
the
only
person
who
has
getter
access.
No.
C
E
To
get
it
actually,
the
Jenkins
namespace
is
configure
that
everyone
who
has
the
right
access
to
Jenkins
c
I
Jenkins,
can
administer
the
guitar
rooms
and
a
kind
of
weird
concept,
but
the
resulted.
E
Okay,
maybe
we
can
create
another
rule
in
the
Jenkins,
the
eye
organization,
people
to
add
and
make
sure
this
role
at
this
team
can
moderate,
guitar
or
something
I,
don't
know?
Definitely
not
something
core
maintainers
do.
C
Can
we
can
we
get
a
sponsored
small
instance
just
to
host
the
rooms,
so
we
have
like
Sig
accuracy
at
jenkins.io
instead
of
at
matrix.org,
just
because
I
think
it'll
look
a
little
bit
more
professional
and
clean,
and
then,
when
we
do
that,
then
we'll
have
admin
namespaces
and
everything
and
Gator
can
still
join,
and
everything
like
that,
but
I
just
hasn't
been
a
priority
with
all
the
other
stuff
going
on
right
now.
C
So
I
can
do
everything
on
this
list
and
I
think
Mark's,
the
only
one
that
should
do
Zoom.
So
you
want
to
assign
I
think
to
me
sure
you
bet
just
to
the
top
level
one
yeah.
A
A
A
Not
as
far
as
I
know,
all
those
things
I
think
I
think
I've
got
them
covered.
I
think
I've
got
access
to
all
of
them.
A
Okay
next
topic,
then
governance
board
meeting
time
and
date.
So
what
I
was
thinking
of
doing
is
just
sending
out
a
Mark
to
send
a.
What
do
you
call
it
a
pole?
A
A
D
A
All
right
anything
else
on
governance
board
meeting
time
and
date:
oh
oh
I,
take
it
back.
I
do
have
one
more
thing:
I
propose
to
cancel
the
governance
board
meeting
and
now
I
have
to
look
at
the
calendar
to
see
the
exact
date.
It
would
not
normally
fall
between
the
Christmas
holiday
and
the
New
Year
holiday
and
I
would
like
to
be
offline.
Let's
see
so
that
would
be
26
December.
A
C
Well,
I
was
saying
next
year.
Instead
of
having
the
new
board
start,
December
4th
have
one
meeting
and
then
not
have
any
more
meetings
so
January.
It
might
be
worth
trying
to
see
if
election
ends
earlier.
So
then
you
can
have
two
full
meetings.
B
A
D
B
A
A
Okay,
yeah
fair
enough
next
topic,
then
okay,
CDF
Outreach
reboot.
This
is
just
more
for
your
information.
December
14,
Lori
lorusso,
the
I
believe
she's,
the
Outreach
leader
at
continuous
delivery.
Foundation
is
restarting
the
CDF
Outreach
effort
and
Alyssa
Tong
has
agreed
to
be
there
and
present
for
the
Jenkins
project.
I'll
be
there
as
well.
A
It's
just
getting
started.
Lori
is
actually
with
jfrog
and
we've
been
working
with
her
as
well
on
the
jfrog
contribution
to
Cloud
to
to
Jenkins
and
how
how
we're
adapting
to
needing
to
reduce
bandwidth
requirements
there.
So
Lori's
been
a
great
help
on
that.
We're
very
grateful
to
jfrog
for
her
contribution.
C
Yeah
I
mean
it's:
it's
gonna,
it's
pretty
support
heavy
last
couple
weeks,
but
there
is
the
whole
thread
that
various
people
have
been
I
accidentally
typed,
the
last
one,
but
talking
about
how
to
get
involved.
It
does
sound
like
we
get
a
lot
of
people
asking
that
so.
A
And
actually
John
Mark
John
Mark
Mason
has
prepared
a
boilerplate
in
the
form
of
a
blog
post
that
he
and
I
were
going
to
propose.
We
also
use
as
a
canned
reply
here
on
community
with
some
suggestions
and
topics,
things
that
can
help
people.
Then
this
thing
that
I
did
here
of
hey
here
are
plugins
that
have
just
been
adopted:
dhiraj,
Jodha,
diras,
Singh,
Joda
and
I
are
trying
this
experiment
where,
let's
give
them
specific,
plugins
and
say
help
with
this
plugin
and
let's
see
what
that
happens.
That
way.
A
D
I've
got
some
experiments,
I'm
doing
that
are
in
the
pipeline.
That
could
be
part
of
this
that
basically
I
think
a
big,
a
big
suggest.
One
of
the
most
frequent
suggestions
that
I
see
being
given
for
people
who
want
to
get
involved
is
to
adopt
a
plug-in
and
bring
the
plugin
up
to
the
modern
standards
for
our
build
tool
chain
and
I.
D
Think
that
that's
a
that's
first
of
all,
something
that's
very
much
needed
to
keep
to
keep
the
plug-in
stable
and
building
properly
and
tested
properly,
and
it's
also
a
great
way
for
people
to
get
involved
if
they
are
not
involved.
But
I.
Think
one
of
the
downsides
to
that
suggestion
is
that
it's
a
fairly
specialized
and
difficult
task.
That
requires
a
lot
of
the
main
specific
knowledge
to
for
that
task
to
be
completed
by
people.
D
So
it's
just
very
High
investment
and
low
reward
scenario,
so
something
that
I
have
in
the
pipeline
is
finding
ways
to
make
that
easier.
I've
been
doing
a
lot
of
experiments
about
this
have
have
an
idea
of
building
a
mono
repo
of
the
top
250
plugins.
D
That
would
be
basically
building
against
had
all
the
time
against
the
latest
versions
of
everything,
not
even
the
latest
released
versions,
but
just
the
latest
commits
on
the
main
branch,
and
basically
with
that
idea
that
would
that
would
make
our
pitch
a
lot
more
friendly
to
these
newcomers,
because
we
could
say
hey
instead
of
figuring
out.
All
of
this
Arcane
build
knowledge
that
you
never
need
to
use
again.
D
After
this
just
go
and
find
what's
being
done
in
the
mono
repo
and
apply
that
into
the
plug-in,
so
I
think
that
that
to
me
is
a
much
more
friendly
message
that
oh
you'd
like
to
get
involved.
Okay,
great
start
fixing
build
failures
that
very
few
people
can
figure
out.
D
I
I
think
I
think
that
if
I,
if
I
I've
been
kind
of
playing
around
with
this
way,
I
think
that
would
be
a
good
step
and
then
obviously
I've
got
much
much
more
Grand
plans
like
automating
some
of
this
and
then
adding
openview
right
to
to
make
it
even
fancier,
but
just
just
getting
started
with
the
modern
repo
to
get
the
hard
stuff
out
of
the
way.
D
I
think
that
would
be
a
positive
step
in
in
the
sales
pitch,
because
that
would
transform
the
task
from
being
hey
thanks
for
thanks
for
wanting
to
get
involved.
Now
do
something
really
hard.
Now
it's
like!
D
Oh,
you
can
do
something
of
easy
to
medium
difficulty
and
then
could
do
something,
and
also
it's
I
think
it's
also
good,
because
if
we
give
them
the
fundamental
knowledge
to
get
the
build
up
to
date,
then
they
can
focus
on
something
that
they
really
want
to
do
like
add
a
new
feature
fix
a
bug,
rather
than
something
that
probably
very
few
people
are
interested
in,
which
is
working
on
builds
so
anyway,
that's
just
a
preview
of
what
I've
been
working
on.
C
There's
also
triaging
I
think
that's
that's
always
gets
under
under
suggested.
It's
just
look
at
open
bugs
and
see
if
you
can
reproduce
them
and
write
up
notes
about
it.
It
could
because
it-
and
we
could
highlight
the
fact
that
it
gets
you
comfortable
in
using
Jenkins,
which
means
that
making
future
requests
are
a
little
bit
easier.
You
actually
know
what
people
do
with
it.
A
D
D
Triaging
them
is
somewhat
laborious,
but
I
have,
in
the
past,
offered
to
help
people
or
to
teach
to
teach
people
the
process
that
I
use,
which
is
basically
to
use,
get
bisect
coupled
with
interactive
testing
to
find
find
the
commit
that
introduced
their
aggression,
so
that
that
would
be
a
great
place
for
people
to
get
involved
in
and
if
there's
questions
about
how
to
do
that,
I
could
definitely
share
the
process.
I've
been
using.
A
A
C
Yeah
I
didn't
know
what
to
title
this
one
there's
just
an
ongoing
discussion.
Everyone
has
their
opinion
on
spacing,
and
so
this
go
ahead,
keeps
going
Billy's
been
doing
a
great
job
at
managing
and
suggesting,
but
I
figured.
It
was
a
non-support
request
that
I
should
mention.
A
Yeah,
that
is
this
is
a
good
one
and
it's
a
it's.
A
good
topic
for
ongoing
discussion.
I
expect
some
more
noise
from
the
release,
this
Wednesday,
because
there's
an
accessibility
Improvement
that
makes
one
of
the
things
that
used
to
be
a
click
of
a
link,
no
longer
a
clickable
link
and
it
it
does
improve
accessibility.
It
was
intentionally
discussed,
carefully,
decided,
but
I'm
expecting
that
they're
going
to
be
some
users
who
say
Hey
where's
my
click
that
I
used
to
be
able
to
click.
C
Good
and
then
totally
honest,
selfish,
I
love.
It
then
I
included
the
newsletter
because
I'm
very
happy
that
it
exists.
So
Alyssa
has
done
a
oh
I
pinned
the
wrong
topic.
Oops
reach
request
to
anyone
who
wants
to
add
anything
to
the
November
balance.
There's
an
open
post
for
it,
and
you
know
I'll,
link
to
the
past
September
and
October
newsletters.
A
C
Nothing
comes
to
mind,
I'm,
hoping
the
newsletter
kind
of
replaces
this
whole
section.
So
yeah.