►
From YouTube: Jenkins Governance Meeting, Jun 03, 2020
Description
Regular Jenkins Governance meeting.
* Recent news and updates
* Windows support policy, final approval
* Promoting AWS sponsorship post
* Aligning Jenkins with CDF project graduation criteria
* Jenkins project funding updates
Full agenda and meeting notes: https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit?ts=5ed8016f#heading=h.ele42cjexh55
A
B
A
A
A
So
let's
start
from
update,
so
the
first
update
is
about
York's
hot
rest.
So
if
you
yeah,
we
had
one
last
week
during
this
hot
fest,
we
had
actually
54
contributors
and
we
needed
a
major
progress
with
user
documentation
and
with
some
stories
related
to
changes,
user
interface,
so
particularly
achievements
that
we
have
released
preview
for
Jenkins
on
the
system
configuration.
So
you
can
find
the
information
in
this
blog
post,
so
it
announces.
A
They
feature
premiere
availability
and
usually
the
hot
fest
was
a
lot
of
user
experience,
testing
bug
fixes,
and
that
is
still
a
lot
of
follow
ups,
but
the
future
looks
fitting
boot
and
hopefully
we
will
be
able
to
release
it
SG
in
the
next
LCS
cycle,
so
with
September
as
et.
So,
thanks
to
everyone
who
contributed
to
this
story,
there
was
a
lot
of
progress
there.
A
The
second
related
topic
is
Jenkins,
dark
theme.
So
again
we
have
created
a
review
basically
from
stretch
which
offers
a
new
theme
for
Jenkins
and,
moreover,
we
defined
foundation
for
both
teams
extensibility.
So
the
most
of
the
code.
Isn't
this
theme
itself
but
rank
score
changes
which
are
yet
to
be
released
in
the
weekly
release,
which
is
getting
delayed?
A
We
had
a
good
progress
with
configurations
tables
to
dissemination,
test
and
testers
for
the
dishes,
and
in
addition
to
that,
we
had
improvements
in
different
stories,
for
example,
new
user
interface
and
scripts
security
plug-in,
which
is
currently
pending
review,
say
my
in
folder
authorization
strategy,
that
is
new
user
interface,
and
they
were
a
lot
of
small
stories
he
and
their
example
by
the
credentials,
navigation,
some
plug-in
management,
UI,
etc,
etc.
We
will
be
posting
a
blog
about
that
soon
and
if
you
interest,
you
can
find
their
major
stories
here.
A
C
So
we
had
40
plus
pages,
contributed
a
bunch
of
wiki
migration
changes
that
were
made
wonderful
outcome
from
those
wiki
migration
changes,
plugins
migrated
from
using
wiki
based
Docs
to
documentation
as
code
good
step.
This
was
also
our
first
experience
with
using
github
issues
instead
of
using
our
own
JIRA
site
and
github
issues
have
been
a
smashing
success.
It's
been
absolutely
wonderful,
working
with
them.
A
A
Okay,
we
also
had
some
highlights
regarding
spread
the
word,
so
we
had
a
number
of
knowledge
transfer
sessions
which
also
recorded
and
published
very
well
a
lot
of
nice
to
meet
Bike
Fest
participants
and
we'll
keep
doing
so
same
for
Jenkins.
It's
the
way
we
DC
number
of
stories,
and
also
we
launched
Jenkins
comics
thanks
to
comic
strip
and
contributors
at
the
box
and
l3c
who
helped
with
initial
reviews.
So
yep
we've
got
beautiful
good
results
from
the
hog
fest.
We
still
need
to
publish
a
blog
posts,
etc
bothered.
A
Let's
see
yes,
speak
on
the
hog
test
bills,
then
a
poll
among
participants
asked
what
would
be
the
top
three
things
which
could
improve
user
experience.
We
got
a
nice
feedback,
there,
I
didn't
treat
pipeline
visualization
and
a
few
other
bits,
so
we
will
be
processing
this
feedback
and
publishing.
So
definitely
there
is
good
opportunities
for
few
other
events.
A
So
why
I
bring
it
up
there
because
there
is
still
some
consequences.
We
need
to
figure
out.
So
you
can
find
the
summary
from
olivier
in
this
list
and
yeah
thanks
a
lot
olivier
to
team
gherkin
to
marquee
to
Danielle
back
and
other
contributors
who
were
troubleshooting
that
and
getting
back
to
the
stable
state.
A
So
we
have
the
infrastructure
mostly
restored,
although
there
are
some
issues
which
we
will
need
to
figure
out,
for
example,
where
we
lost
history
of
Jenkins
accounts
database
for
something
like
three
months,
so
we
follow
up
on
that,
but
in
general
the
instances,
but
no,
no
so
far.
So
there
are
some
issues
because
some
contributors
may
have
lost
access.
We
will
need
to
restore
that.
We
will
need
to
figure
out
how
to
notify
them,
etc,
etc,
but
yeah
for
the
information
of
the
governance
port.
This
topic
is.
A
Kevin
Hill,
let's
move
on
so
the
next
one
is
quick,
jae-seok
update,
so
we
have
started
becoming
their
coding
phase
right
now
or
the
lists
nothing
really
surprising
cone
expected.
So
all
projects
are
ready
to
coding
all
projects
have
enough
information,
students,
knowledge
transfers.
They
go
to
the
required
permissions
and
they're
ready
to
iterate.
Can
we
have
six
projects
which
are
focused
on
Jenkins
one
project
which
is
focused
on
Jenkins
X,
and
we
have
already
had
a
number
of
prototypes
being
presented
so,
for
example,
github
checks,
a
PRA
and
external
and
projects
distribution
build
service.
A
They
have
been
presented
during
the
Yerkes
hot
fest.
Again,
you
can
find
the
recordings
here
so
recorded
sessions.
You
can
just
find
them
on
the
website
or
on
the
Jenkins
online
Meetup.
We
also
have
prototypes
for
a
few
other
projects,
so
they
going
pretty
well,
let's
see
what
the
first
coding
face
brings.
So
as
always
in
the
engine,
we
will
have
them
as
hopefully,
all
projects
will
present
them.
C
A
A
From
newcomers,
some
of
these
contributors
have
already
submitted
pull
requests
as
a
part
of
population.
Some
beavers
participated
in
the
URLs
hard
first,
so
it's
going
pretty
well,
let's
see
what
it
will
be:
the
results,
but
okay,
I'm,
pretty
confident
that
you
have
maintained
its
program
and
let's
see
what
you
could
get
more.
A
A
A
A
C
I
believe
the
weekly
is
in
process
of
execution
right
now
and
it's
in
my
hands
to
pick
it
up,
and
so
so
so
we're
doing
creature.
That's
that's
my
understanding.
I
haven't
checked
through
the
VPN
to
see
its
current
status.
That's
I
just
wrote
myself
a
card
that
reminds
me
to
check
for
2.2
39
s,
progress
in
the
in
the
job
right
now
and
I'll
have
to
do
that
after
this
meeting.
Oh.
A
A
D
A
A
The
only
notable
development
except
edits
in
wording
etc
is
support
for
Windows
10.
So
originally
it
was
suggested
to
be.
Did
one
full
support,
but
yeah
we're
legit
I
made
comments
from
James,
not
that
we
actually
have
no
testing
for
that
at
the
moment
and
that
our
level
one
was
about
definition,
explicitly
states
that
we
run
automated
testing.
So
after
this
discussion,
windows
10
was
pushed
to
a
level
10
and
Alex
was
talking
about
setting
up
something
so
to
make
it
testing
yeah.
C
B
A
A
A
B
C
B
A
Would
definitely
make
sense
so
if
we
have
an
opportunity,
at
least
for
functional
tests
for
stable
branches?
Yes,
of
course,
we
don't
have
to
make
it
as
a
part
of
any
pull
request
run
because
I
don't
actually
expect
any
practical
difference
for
99
percent
of
tests
we
have,
but
if
you
could
enable
it
as
a
part
of
LCS
check,
I'm
close
one.
C
Yeah
I,
like
that,
I
I
I,
agree
with
you
wholeheartedly
that
I
don't
want
it
being
included
in
pull
request
evaluation,
increasing
the
load
on
on
pull
requests.
The
other
is
with
the
licensing
concern.
If
it's
sounds
like
it's
as
your
specific
and
if
we
need
to
host
infrastructure
agents
on
AWS
more
strongly,
the
adjure,
as
your
specific
licensing
limitation,
be
a
difficulty
to
overcome.
B
We
could
pretty
much
migrate
any
of
the
windows,
2019
or
Linux
agents
to
completely
be
on
AWS
in
terms
of
the
VM
based
agents.
We
slow
the
CIA
agents
on
Azure,
but
we
can
eventually,
hopefully
move
those
over
to
ECS,
and
then
that
would
significantly
we
can
reduce
our
costs
on
edge
or
even
more
by
just
running
things
that
can
only
run
on
Azure
manager
got
it.
C
A
A
B
Say
for
Windows
10
is
that
what
you're
asking
for
specifically
yes
I
would
say
is
tier
2
because
we
don't
have
a
tested
agent
right
now,
it's
available,
but
it's
not
like
fully
tested
and
stuff
like
that.
So
if
we
do
decide
to
keep
you
know
to
use
that
agent,
we
could
move
it
to
tier
one
saying
we're
running
tests
on
it
and-
and
things
like
that,
but
I
think
leaving
it
at
tier
2
is
perfectly
fine.
C
A
Okay,
then
I
will
just
measure
the
poor
request
after
the
meeting
okay,
the
next
topic,
so
the
next
topic
is
promoting
EWS
sponsorship
post
as
Jumbotron,
so
just
provide
you
context.
There
was
recently
blog
post
by
AWS
about
white
drinking
still
contains
the
surfs
developers
so
yeah.
It
includes
some
statistics
about
Jenkins
those
etc.
A
Matters
with
Ebola
slander
is
free
and
other
components,
and
also
a
reference
to
Jenks
project
running
infrastructure
named
WS,
so
I
wonder
what
if
we
would
be
interested
to
take
this
part
highlight
it
is
Jumbotron
and
referenced.
This
blog
post.
A
D
E
F
A
A
A
A
So
I
think
it's
slightly
unrelated
to
this
particular
blog
post,
but
the
amounts
are
here
would
be
that
if
you
want
to
apply
this
feel
free
to
apply
the
program
added
for
this.
So
we
you
can
apply
on
behalf
of
the
project
or
you
can
apply
individually,
so
I
guess
supplying
individually
as
Genki
sort
of
immunization
violetta
get
sponsorship.
It
was
handled
in
a
slightly
different
way,
but
we
have
a
confirmed
sponsorship
by
a
double
years
and
it's
$5,000
per
month
on
sixty
GPA.
So
we
already
have
this
sponsorship
and
yeah.
A
C
D
D
C
F
A
For
google
season
of
dogs
sing
for
google
season
of
code
Summer
of
Code,
we
handled
that
well,
so
what
that
means?
So,
if
you
need
specific
and
research
to
work
on
your
project,
please
contact
orchid
means
and
what
they
will
help
you
vote
for,
google
season
of
dogs.
The
project
starts
in
September,
so
before
September.
If
you
need
special
infrastructure
yeah,
it
would
be
good
to
ask
for
credits.
For
example,
we
had
such
cases.
A
This
is
some
of
g-shock
projects.
If
you
ask
for
credits,
you
know
what
to
get
them
for
variation.
If
you
are
working
on
a
bigger
project
which
needs
something
as
a
Jenkins
contributor.
Yes,
we
can
discuss
that
and
wait.
We
will
be
talking
about
funding,
which
is
mostly
related
to
the
topic,
because
a
if
you
want
to
spend
money,
you
need
to
get
money
first
and
we'll
talk
about
that
for
a
time.
Thank.
G
While
we
came
up
with
criteria
and
process
for
moving
things
along
on
the
different
stages.
So
at
this
point
we're
pretty
happy
with
the
graduated
stage
criteria
and
we're
hoping
to
move
the
Jenkins
project,
since
it's
clearly
mature
and
ready
to
be
graduated
through
this
as
kind
of
a
test
of
the
process
and
then
we'll
start
on
the
rest
of
the
projects.
So
we've
been
working
with
Oleg
to
kind
of
find
any
clear
things
in
the
documentation
and
I'm,
not
sure
that
it
all
makes
sense
for
a
successful
project
like
Jenkins.
G
A
So
if
you
follow
the
DFT
remaining
list,
there
would
be
some
topics
discussed,
for
example,
compliance.
So
this
is
what
we
are
already
working
now
on
in
the
Jenkins
project.
You
can
find
some
references
in
the
mailing
list
next
right
now,
James
project
was
at
88%
compliance
we,
but
this
will
be
addressed.
There
are
some
process
issues
here,
for
example,
related
to
governance,
references
to
public
list
of
adopters,
which
we
will
need
to
figure
out,
but
all
of
them
may
seem
to
be
of
other
processes
than
technical
blockers.
G
Awesome
and
they
I
see
traces
on
the
car
too,
but
you
know
the
goal
here
is
to
just
help
out
the
Jenkins
project
with
and
if
marketing
and
other
types
of
resources,
as
we
announced
this
graduation
I'm,
ensure
like
Jenkins,
is
an
examples
of
don't
really
well
run
open
source
projects
that
we're
using
as
a
model
for
others.
E
Yet
thinks
and
I
think
it
would
be
good
if
we
can
kind
of
pencil
in
a
target
date
for
this
just
I
think
there's
a
lot
of
different
folks.
We
can
get
focused
on
this
if
it's,
if
we
sort
of
pencil
out
when
it
would
happen
and
I'd
be
inclined
to
suggest
sort
of
end
of
July
or
early
August,
as
as
when
this
would
happen,
knowing
what
CDF
wants
to
do
and
knowing
that
this
is
within
sight
for
Jenkins.
G
Yeah
on
that
one
I
think
fifty
intent
is
that
just
has
already
met
here.
I
think
you've,
I,
don't
think
anybody
is
really
in
100%
compliance
with
CII,
so
I
think.
The
way
it's
worded
is
just
that
you
have
a
badge
and
I
think
P.
Eighty
percent
compliance
is
definitely
enough
for
I.
Don't
remember
the
name
the
nomenclature
now
at
this
point,
but
for
one
of
the
CIA
badges,
so
I
think
you're
fine.
There
already.
D
G
Yeah
great
question:
so
we
decided
not
to
require
a
security
audit
for
projects,
but
we
are
making
them
available
so
and
recommending
them
so
yeah.
If
the
chinese
community
or
in
word,
is
interested
in
a
security
audit,
then
yeah
we
can
definitely
start
getting.
You
know
estimates
and
reaching
out
to
the
different
security
audit
firms
to
figure
out.
Why
would
cost
and
then
make
sure
we
fit
it
into
the
budget?
Yeah.
A
A
So
much
initiative
assumes
that
there
are
some
additional
funding
available
from
through
Linux
Foundation
and
through
vendors,
which
would
help
with
security
audit,
because
security
audit
for
the
Jenkins
project
yeah.
First
of
all,
it's
just
expensive,
the
project,
size,
etc.
So
the
easiest
way
to
do
that
is
actually
to
facilitated
through
core
infrastructure
initiative,
so
yeah
the
drug
companies
funding
that
and
there
is
a
history
of
some
programs
like
census,
etc,
which
were
funded
by
foreign
research
initiative
members.
So
if
you
want
to
secure
it,
it
would
be
definitely
useful
for
the
project.
G
Yeah
I'm
sure,
there's
tons
of
sources
for
funding
we
can
reach
out
to
through
the
LF,
especially
in
the
security
scope.
I
think
the
yeah.
The
first
step
would
be.
It
I
mean
correct
me
if
I'm
wrong,
Tracy,
but
I
think
the
first
step
would
probably
be
just
for
the
board
to
ask
the
LF
to
get
us
some
kind
of
quote
for
a
security
audit
and
then,
if
it's
too
much
for
the
CDF
budget,
we
can
explore
other
sources.
G
A
F
E
That's
the
whole
like
the
point
of
CDF.
Is
it
wants
the
projects
that
are
part
of
it
to
succeed
and
to
continuously
keep
evolving
and
I?
Think
there's
ever
increase
like
one
of
the
key
things
at
the
board
level
is
security
and
giving
the
industry
confidence
for
the
projects
and
platforms
they
use
so
I
think
I'm,
confident
to
say
this.
We
can
figure
this
out
because
it's
a
key
importance.
D
Have
one
last
question
and
I
do
thank
you
for
being
here
Dan
as
everybody
else
in
terms
of
the
Jenkins
code
of
conduct
to
me
at
some
point
need
to
have
that?
Has
that
been
reviewed
by
the
CDF
to
make
sure
it's
following
specific
guidelines
and
I'm
also
wondering
but
want
to
add
on
to
that?
Does
it
even
the
cedia
or
does
it
make
sense
for
the
Jenkins
product
to
have
a
sort
of
code
of
conduct
committee
I
just
want
to
make
sure
those
are
aligned.
G
Sure
yeah
so
I'll,
just
repeat
the
two
questions:
does
the
CDF
need
to
review
the
Jenkins
code
of
conduct
to
make
sure
it
makes
sense?
Slash?
Has
that
already
happened
and
then
does
it
make
sense
for
the
Jenkins
project
to
have
a
code
of
conduct
committee
and
so
for
the
first
one
Oleg
raised
this
question
about
there's
a
couple
weeks
ago:
Henry
discussed
it
and
then
last
toc
meeting.
But
yes,
so
the
CDF
does
specify
that
you
have
to
have
a
code
of
conduct.
G
We
have
one
that
we
recommend
for
the
CDF
which
I'm
going
to
mess
up
the
exact
version
numbers
here,
but
you
know
the
default
to
cdf
recommends
a
version
of
the
contributor
covenant
which
jenkins
also
uses
a
Jenkins
just
happens
to
use
a
different
version
of
it
and
then,
since
the
CDF
picked,
that
recommended
one
there's
been
a
few
new
versions
with
contributor
code
of
conduct,
contributor
covenant
code
of
conduct,
so
we're
falling
behind
a
little
bit
there
too.
So
there
were
no
concerns
raised
with
the
one
the
champions
uses.
G
We
are
gonna,
do
a
little
bit
of
digging
and
to
figure
out
how
frequently
things
should
be
updated,
slash
how
to
keep
up
with
the
new
versions
of
this
as
they
come,
while
still
making
sure
we're
reviewing
the
changes,
making
sure
that
they
make
sense
but
yeah
so
they're,
not
no
issues
with
the
Jenkins
one
has
exist.
C
A
1.3,
so
this
version
was
published
around
2015
and
when
put
of
conduct
in
Jenkins,
this
fish
has
been
taken
as
a
baseline,
CDF
uses
version
1.4,
which
is
a
big
new
one,
and
this
version
covers
some
needs
which
are
not
covered
by
the
Russian.
We
use
right
now,
for
example,
it's
most
pissed
about
social
media
resources,
etc,
and,
personally
I
think
that
we
issued
update
gingka
code
of
conduct
to
a
new
version
at
the
same
time.
A
I
think
that
having
a
discussion
about
a
baking
code
of
conduct
would
be
useful
and
it
basically
brings
us
to
the
question
by
market
where
they
need
contact
time
again
and
therefore
this
question
my
personal
opinion
a
bit
developer,
man
at
least,
and
that
Jenkins
governance
meeting
is
probably
enough,
but
the
marquee
it
would
be
better
to
know.
What's
your
opinion
about
that?
Do
we
need
to
introduce
new.
D
Entities
etc,
I
think
as
long
as
the
as
long
as
we're
transparent
in
what
we're
doing
so.
Yes,
the
developer
mailing
list
should
be
good.
The
using
this
meeting
venue
to
do
that
would
be
great
and
then
for
any
decisions
that
are
made
or
something
that's
forwarded
from
these
two
venues
to
the
board
and
then
ultimately
on
to
the
sea
would
be
good.
I
just
would
would
ask
that
we
just
somewhere
it
if
possible
document
what
we
do.
So
that
way,
it's
clear
to
everybody
and
everybody
you
know
which
transplant!
G
Yeah
I
think
you
know,
an
update
here
probably
makes
sense,
exactly
which
version
I
think
we'll
leave
up
to
you
and
the
Jenkins
committee
I
think
yeah
spelled
out
in
all
of
these.
A
code
of
conduct
committee
does
make
sense
for
the
CDF.
At
that
level.
We
just
have
an
email
list
that
goes
to
a
bunch
of
responsible
people.
G
A
We
just
found
that
the
foundation
or
whatever
Jacobs
project
uses
governance
board
as
a
de-escalation
stage
and
if
you
could
agree,
for
example,
to
have
a
two-level
escalation
like
first
think
Jenkins
board,
then
second
level
is
a
foundation.
I
think
that
it
will
be
just
the
best
of
both
because
Jenkins
board
members
can
reach
out
to
all
sides,
try
to
mitigate
it.
On
the
project
side,
the
other
contributors
involved
mitigation
and
if
it's
not
possible,
if
content
senses
cannot
be
found,
then
it
can
be
escalated
to
the
CDF
I.
D
A
D
A
A
A
So
yeah
the
next
topic
is
about
community
bridge
funding,
so
I'm
just
bringing
it
up
again.
So
there
was
all
discussion,
but
after
that
everybody
was
ve
and
it
just
was
false
for
a
while.
So
it
was
discussed
in
December
and
in
December
the
governance
meeting.
We
agreed
that
it
would
be
great
to
do
something
about
our
funding
because
it
just
me
status
summary.
A
So
we
have
two
ways
of
the
age
of
the
nation
which
are
officially
documented,
so
one
is
SPI
and
for
SBA
there
was
agreement
that
base-pair
governs
both
meeting
on
llego
that
wouldn't
be
in
the
nation's
to
the
Jenkins
project.
So
the
fact
that
they
keep
accepting
them
I
guess
it's
subject
to
change
once
the
transition
from
SPI
to
CDF
is
completed
for
the
jingus
project,
but
yeah
this
way
is
marked,
as
I
would
say,
unstable
another
way
for
the
commentation
is
through
ffs,
yes
ad
side,
so
well.
A
A
The
site
why
mail
etc,
it
didn't
work,
he
also
sent
official
email
through
German
post
and
again
we
is
to
have
no
answer.
So
this
is
a
safe
assumption
that
even
if
this
way
is
technically
feasible,
it's
not
working,
so
we
probably
get
rid
of
that
and
it
leaves
us
with
basically
no
ways
to
the
name
to
the
jinguk's
project.
At
the
same
time,
we
have
a
good
experience
of
from
community
bridge
last
year.
A
Definitely
we
could
use
some
money
for
sh
work
and
other
stuff,
so
that
was
a
proposal
to
actually
go
in
this
community
bridge
and
there
is
a
prototype
set
up
for
the
project,
so
you
can
find
it
here.
It
was
basically
set
up
for
community
pitch
mentorship,
but
it's
fully
operational
right
now.
It
has
some
funding
goals
which
I
completely
just
once,
but
we've
received
a
few
contributions
there,
but
this
way
is
not
documented
anywhere,
so
I've
started
working
on
a
job
draft
and
I
submitted
it
basically
right
before
the
meeting
would
I
have
so.
A
This
job
is
not
in
a
complete
for
being
published.
The
opening
is
a
draft,
but
the
main
idea
of
this
job
would
be
that
let's
publish
community
bridge
funding
as
experimental
process-
that's
a
bit
jinx,
a
the
name.
Documentation
to
suggest
is
a
way
of
institution
and
what's
updated,
metadata
for
gingka
score
and
for
infrastructure
that
it
would
be
pointing
to
community
bridge.
So
I
set
up
what
we
prototype
here
in
my
personal
repository.
But
how
look
like
so?
There
is
a
sponsor
button
which
is
enabled
by
finding
camel
and
this
fun.
A
A
So
basically,
it
would
document
how
we
spent
the
nation's,
etc.
So
that,
and
once
this
file
is
in
place,
everybody
would
see
a
sponsored
button
which
would
be
pointing
right
directly
to
the
community
bridge
and
also
to
the
donation
policy.
So
you
click
here
and
you
better
way
to
donate
and
putting
target
in
donations,
for
example,
to
documentation
or
to
meetups,
and
also
you
would
be
able
to
predict
donations
to
do
company
in
the
nation's
etcetera,
etcetera,
powered
by
a
community
bridge
and
the
community
page
is
basically
mimics
foundation.
A
G
C
A
C
A
Say
basically,
if
you
are
plug
in
the
maintainer,
you
have
multiple
ways.
Firstly,
you
can
just
join
Jenkins
funding
and
then
you
can
ask
for
donations
for
some
money.
Basically,
you
can
ask
it
right
now,
so
you
know
fish
you
to
plug
in
as
I
can
see
that
as
a
part
of
the
Jenkins
ecosystem.
So
you
reach
out
to
the
developer
mailing
list.
If
you
want
to
get
some
expenses
or
you
can
participate
in
G,
so
G
sold
out
Ricci
we've
been
proposed
projects,
so
you
have
access
to
Jamie's
funding
right
now.
A
A
D
A
For
example,
we
can
see
that
there
are
already
some
more
plugins
depending
funding
PMO.
For
example,
we
can
take
a
look,
localization
changes
plugins,
you
point
somewhere,
okay,
but
he
is
basically
fine
and
for
the
Jenkins
Chinese
community.
Why
not
pretty
much
the
same,
for
example,
for
what's
a
minute
or
in
plugin
I
Bislett
yeah
right
now.
Basically,
it's
a
github
sponsors
for
plug-in
maintenance.
Again,
why
not?
So
we
you
can
sponsor.
A
For
Jenkinson,
one
of
the
issues
with
community
be
sure
that,
right
now
there
is
no
destination
for
infrastructure.
Specifically,
we
had
a
meeting
with
community
bridge
last
autumn
when
we
will
discuss
on
communication,
mentorship
on
name
etc,
and
they
said
that
there
is
request
for
enhancements
for
that
which
would
be
delivered
soon.
A
So
definitely
some
hasn't
come
yet,
but
eventually
it
would
be
there
and
once
it's
today,
of
course,
we
should
enable
it,
but
even
now
what
I
put
in
the
jet
development
infrastructure
so,
for
example,
development
we
can
use
it
for
finding
the
attraction
needs
if
needed.
Well,
it's
pretty
much
the
same
for
documentation,
because
Jenkins
I
offer
has
to
be
hosted
somewhere
if
you
want
to
shoot
the
fermentation
for
run.
A
Firstly,
if
we
go
beyond
the
sponsorship
by
first
again,
we
could
use
this
money
to
pay
the
difference
and
so
on
so
on
so
even
without
infrastructure
category
we
can
spend
money
on
infrastructure.
Moreover,
the
current
community
bridge
limitation
basically
says
that
whatever
you
submit
money
to
it
still
and
decision
of
the
recognization
how
they
spend
this
money,
so
we
are
not
forced
to
use
that
Aziz
and
right
now
there
is
a
opportunity
to
submit
money,
a
result,
specific
indication
so
that
everybody
can
use
them.
But
the
other
thing.
A
Right
so
well,
this
website
isn't
promoted
anywhere
and
I
would
say
that
unless
you
search
for
Jenkins
funding
directly
on
this
website,
so
right
now
there
is
a
search
button.
It
wasn't
in
case
three
months
ago,
but
even
with
this
search
button
you
have
to
search
for
Jing
is
specifically
to
find
it.
So
it's
not
exactly
visible
until
be
bigger,
added
to
github
sponsors
or
whatever,
but
yeah.
You
can
see
that
some
organizations
actually
raise
money
quite
efficiently,
so
there
are
different
use
cases,
of
example,
keycard,
etc.
They
crowd
fund
that
Ranger.
A
A
So
yeah
I
think
that
in
our
case
we
can
do
a
combined
thing,
so
we
can
did
use
some
money.
For
example,
we
you
can
see
that
right
now
we
have
a
$3,000
transfer,
but
basically
you
just
putting
money
from
one
pocket
to
another
one,
but
to
find
a
community
bridge,
but
it
technically
we
are
musicians
etc.
Can
also
do
big,
targeted
the
nations.
C
A
So
maybe
one
topic
worth
mentioning
that
basically
Jenkins
mentorship
page
is
also
public.
Again
they
have
changed.
The
website
recently
saw
something
some
bits
broke,
but
in
principle
Jenkins
mentorship
a
she's
there.
So
if
anybody
wants
to
run
mentorship
program,
we
can
use
that
we
have
some
money.
Now
is
Pierre
pounds
not
that
much
for
the
record.
But
if
you
want
to
run
unpaid
mentorship
programs,
we
definitely
can
do
that
for
paid
mentorship
programs.
We
can
shake
some
trees,
etcetera
and
again
we
can
probably
do
that.
A
A
And
yeah
three
men,
three
sound
the
call
okay,
so
that's
it
from
me
for
today
there
was
topic
about
first
thing
begins
with
proprietary
libraries
I'm,
not
sure
that
we
want
to
discuss
it
now,
since
we
are
already
over
time
or
should
we
postpone
it
till
the
next
meeting.
There's
a
point
to
the
next
meeting
was
one.
C
A
Yeah
but
this
throat,
you
know
the
detective.
So
then
next
meeting
is
June,
17th
I
guess
there
was
nothing
which
needs
change
in
this
date.
So
if
anybody
has
been
Dwyers
about
this
topic,
I
get
please
take
a
look
at
that
is,
there
might
increase
discussion
but
again
I.
Don't
anticipate
any
specific
actions
from
the
board
right
now,
because
our
governance
policy
speak
explicit
what
would
be
host
and
what
we
don't.