►
From YouTube: Jenkins Online Meetup. A new home for Jenkins: Q&A
Description
Following on from Kohsuke's post 'A new home for Jenkins' to the dev mailing list [1], we have hosted an open forum to discuss the proposal, ask questions and plan the future of the project. Chris Aniszczyk from the Linux Foundation also joined the meeting to talk about the Linux Foundation structure and the CNCF experience.
[1]: Email thread: https://groups.google.com/forum/#!topic/jenkinsci-dev/1w57jl3K4S4
[2]: Slides: https://docs.google.com/presentation/d/1HMJptm6-hJVfaOc5sKc2X8z_1_PuTWcx2YZSSdxLmTs/edit?usp=sharing
Meetup page: https://www.meetup.com/Jenkins-online-meetup/events/258167664/
A
Proper,
so
I
guess
the
foundation
believes
him
the
guy
the
whole
idea
of
continuously
buzzing
like
at
the
benefit
it
brings
the
soft
edible,
that's
kind
of
I.
Guess
I
see
it
as
a.
If
you
don't
believe
in
the
mission
that
he
you
shouldn't
be
a
part
of
this
and
then
another
part
I
think
is
you
know
you
should
have
this.
A
The
obvious
important
mission
for
the
foundation
is.
We
should
have
the
second
system
of
open
source
projects
and
then,
in
order
to
sustain
the
growth
of
that
it
should
be
a
vendor
neutral,
face
that
facilitates
collaboration
in
purity
and
so
on
and
I
think
you
know
here,
your
the
many
of
you
have
already
been
a
part
of
some
sort
of
this
open
source
organization,
the
past
so
I
think
he
of
all
the
people
understand
like
what
this
means
in
the
practical
terms
to
the
ground
in
the
last
week.
A
I
think
I,
don't
know
if
we
talked
about
this
point
explicitly
in
the
past.
The
grounds
of
this
conversation
or
not
but
I
think
it's
also
important
that
for
us,
the
traditionalist
be
able
to
advocate
the
ideas
of
the
concerns.
Delivery
and
among
the
users
so
that
they
can
stop
nervous.
We
can
all
convince
her
boss
that
contains
a
very
important
effort
and
the
effort
that
we're
spending
on
is
worth
spending
time
on,
etc.
A
The
law
democracy
of
the
practice,
not
just
a
software
I,
think
he's
actually
for
me
a
very
exciting
part
of
the
console
advantage.
Alright,
so
and
then
you
know
so,
this
work
is
being
done
with
the
Linux,
Foundation
I.
Guess
again,
I
think
many
of
you
already
know
what
the
new
explanation
do
in
this
space,
so
they've
been
pretty
successful
in
building
a
lot,
some
foundations
creating
a
neutral
playground
between
different
vendors.
A
So
you
know
that
idea:
I,
don't
think,
needs
any
further
introduction.
Unless
you
want
to
talk
about
it
and
I
think
there
is
a
growing
rise
of
contains
delivery
or
in
fact,
I
guess,
on
the
backdrop
of
the
growing
importance
of
software
in
this
space,
so
I
think
that
time
is
right
for
this
effort
and
then
there's
you
know
lots
of
CCD
tools
in
the
space,
many
of
them
open-source,
but
like
need
not
really
like
right
now
collaborating
and
working
together.
A
So
that
part
of
the
things
we
mentioned
in
the
past
right,
so
so
yeah
so
I,
think
and
in
this
kinda
line.
Well,
is
what
we
been
working
on
in
the
Jenkins
for
the
city
is
defined.
A
good,
stable
whole
right.
I
can
move
away
from
this
halfway
house
between
this
external
perception
of
the
Travis
on
project
discipline,
people
versus
as
they
can
not
having
the
last
bit
more
community-driven
projects.
So
I
think
that,
what's
going
on
in
the
broad
industry,
I
think
it
and
I
know
is
what
we're
looking
for.
A
So
some
of
the
details
that
I
didn't
cover
I
think
in
the
documents
in
the
email
that
I
sent.
So
for
us
there's
like
in
a
Content
area
foundation,
you
have
member
members
and
they
are
generally
I,
think
assumed
to
the
companies
that
comes
in
a
different
tiers
and
they,
when
they
grant
access
to
certain
levels.
Playas
I,
guess
cloten
code
privileges
and
then
it's
in
exchange.
They
pay
in
the
money
unit.
A
So
that
forms
the
budget
that
allows
us
to
kind
of
plan
how
to
spin
those
that
we
don't
actually
run
around
like
a
20
secure.
The
next
place
for
the
intrabody
that
did
come
from
now
that
the
Microsoft
arrangement
is
going
to
expire
at
some
point,
etc,
and
then
so
the
content
area
foundation
has
some
governance
for
these,
like
the
group
of
people,
so
DC
I
think
one
the
CEO
builder
particularly
was
talking
about
with
it.
A
That's
the
base
like
a
high
level
of
commitment,
I
guess
so
the
one
is
like
a
Jenkinson
thinking
sex
is
it
still
and
then
there
is
a
Google
Baxter
pipelines
here
the
Canadians
find
the
products.
So
that's
the
another
one:
that's
I
think
we
have
a
high
confidence
zone
when
we
are
talking
to
sign
in
to
talk
to
you
know
like
tidal
chiming,
that's
read,
part
of
this
is
like
you
know.
We
need
to
start
there's
a
bit
of
a
chicken
and
egg
problem
here
in
that
packet.
A
We
need
to
build
some
shape
of
it
before
we
can
approach
more
people
and
then,
unless
we
approach
people,
we
don't
know
which
project
in
knowing
that.
So
some
of
these,
like
conversations,
are
happening.
Indeed,
he
started
happen
in
the
last
week.
I
think
so,
if
we
Asteria
to
be
out
in
the
process,
but
hope
still
came
in
more
projects
that
we
don't,
and
so
the
one
thing
I
think
is
worth
doing
calling
at
is
what
this
means
is
in
terms
of
the
changes.
A
A
Then
the
SPI-
and
we
gave
some
heads
up
to
SPI
about
this,
so
they
are
aware
that
this
conversation
happening
and
then
I
think
the
other
important,
particularly
files
like
the
like
a
role
of
the
members
other
family
companies
versus
computers,
which
you
know
who
you
are
so
the
contributors
under
this
image,
CDF
just
likes
today
may
or
may
not
be
from
members,
it's
kind
of
independent
from
that
the
earth
and
then
the
decision-making
structures
on
this
project.
You
know
these.
It's
still
remains
intact,
meaning
you
know
the
depth
sings
or
will
be
processing.
A
We
build
out
so
far
or
like
an
implicit
way
of
us
doing
things
like
in
no
change
in
that
the
power
of
entry
into
commuter,
sheep,
etc.
Si
la
mia
not
expecting
any
change
in
there
and
then
so.
Just
because
that
the
point
that
I
wanted
to
reassure
just
because,
like
we
have
all
this
member
company,
that
doesn't
mean
I,
guess
they
automatically
get
to
drive
the
direction
the
projects.
Anything
like
that.
So
that's
important
part
of
you
know
the
making
sure
that
this
open-source
projects
kind
of
functionalities
and
then,
as
contributors,
we
we
get.
A
The
elect
up
and
seats
into
this
some
of
the
aforementioned
governance
bodies
as
a
kind
of
voice
of
the
commuters
or
the
voice
of
the
contributors.
So
that's
additional,
like
a
visibility
in
the
calebrage.
We
people
in
the
community
get
toward
this
foundation
and
the
members
like
what
they
like
a
well
they
come
in
is
one
so
detained
annual
fees
in
that
forms
about
it.
I
talked
already
about
that
and
then
the
part
of
like
a
pain
in
the
money
they
get.
We
provide
some
level
of
oversight
about
how
those
money
are
used.
A
So
that's
the
governance,
dominance,
4gb,
port
and
then
generally
being
able
to
sort
of
raise
awareness
and
advocacy
of
container
surgeries
are
seeing
to
seem
beneficial
to
tenders.
Imagine
like
a
companies
like
these.
It
see
this
angle,
the
fertility.
You
know
the
part
of
the
reason
it's
excited
about
being
able
to
be
part
of
this
endeavor
and
for
in
Jesus
perspective.
A
lot
of
companies
still
use
this
multiple
tools
together
so
being
able
to
kind
of
have
them
talking
to
each
other,
and
then
the
Indies
I
have
some
like
a
forum
to
voice
their
thoughts.
A
That's
also
generally
seen
as
beneficial
for
the
Indies
or
companies.
So
that's
another
motivation
for
companies
to
show
up
as
members
and
then
there's
other
recruiting
other
interests
that
generally
encourages
people
to
join
and
then
the
another
I
think
for
me.
The
benefit
that
were
scoring
at
ease
when
the
company
joins
this
foundation
like
it
opens
up
more.
It
creates
more
air
cover.
A
It
opens
up
the
umbrella
for
people
engineers
in
the
organization
to
spend
more
time
in
the
airports
under
the
umbrella,
as
it
makes
it
easier
for
managers
to
see
that
this
Airport
it's
aligned.
It's
the
other
thing.
This
company
should
be
so
that
I
think
it's
gonna
play
some
positive
influence
on
those
and
then,
since
you
know
the
week
is
here,
it's
I
can
be
iterate.
That
I
think
things
we
can
do
in
China
gets
a
little
easier
and
I
know.
That's
something
exciting
to
you
as
well.
So
that's
kind
of
quick,
quick
overview.
A
B
A
So
I
don't
think
it's
God's
I'm
not
currently
expecting
any
changes,
so
they
the
one
thing
yeah.
So
the
almost
the
way
I
think
of
it
is
like.
So
you
have
existing
structures
in
this
product
like
the
core,
plugins
demo
course
in
there
like
a
rain,
you
know
that
it
just
kind
of
mostly
take
it
at
least
and
drag
that
into
the
structures
into
the
CBF
where
these,
like
at
the
pot
that
gets
connected,
is
what
the
CD,
of
course
at
the
technical
steering
committee
and
they're
from
the
Jenkins,
speaks.
That's
teaching,
Kingsport
and
officers.
A
B
I
was
just
wondering
if
there
would
be
any
change
to
the
the
technical
direction
of
a
plugin
for
set
per
say
if
I
have
a
plug-in
that
I
work
on
or
a
series
of
plugins,
if
the
governing
body
will
now
be
steering
the
direction
of
that
plug-in,
or
will
it
just
sort
of
become
a
much
like
how
the
kubernetes
community
is
built?
It
just
becomes
a
cig
and
you
sort
of
work
within
that
sig.
So
no.
A
It's
not
so
this
won't
be
like
there'll,
be
somebody
of
this
calling
the
shot
meter.
So
what
should
be
done
in
plugins?
So
it
is
not
like
that.
So
it's
very
much
my
expectation
is,
you
know.
Let's
say
you
main
thing
actually,
don't
know
what
talking
you
mean
payment?
Let's
say
you
really
maintain
this
series
of
dragons
in
the
circus,
totti
cano
in
space
right
so
in
a
a
skywriter
modem
IP
decide
what
features
they
do
and
what
bugs
to
work
on,
and
that
will
be
the
same.
A
What
I
hope
the
CDX
will
be
able
to
provide
is
like
more
Bennie's
in
WITSEC.
We
can
get
input
from
and
thoughts
from
more
people
and
then
starting
Fillion
seeds.
You're
thinking,
that's
great,
but
if
not
that's,
oh
no,
that's
not
so
be
it
as
well.
So
yeah
I
really
don't
expect
that
if
you're
concerned
like
somebody
else,
is
going
to
tell
you
what
needs
to
happen-
and
it's
not
gonna
be
like
that
know,.
B
A
A
A
A
So
there's
a
Linux
Foundation
as
the
event
called
the
open
source,
Leadership
Summit
I
believe
and
it's
I
in
my
backyard
practically.
So,
if
that's
the
you
know
so
that'll
be
a
perfect
place
for
us.
We
talked
about
this
in
front
of
the
most.
You
know:
companies
that's
participating
in
to
that
next
foundation,
so
that'll
be
a
great
race
day
and
I
encourage
more.
You
know
more
folks
to
join
there's
some
yeah.
So
that's
the
that's
the
timeline
so
back
into
the
Jenkins
project.
A
The
one
thing
that
I'm
trying
to
look
for
it's
mean
so
far
to
the
extent
that
we
had
a
conversation
in
the
debrief
I
saw
very
overwhelming
support.
But
given
the
magnitude
at
least
I
kind
of
wanna,
like
a
record
this
consensus
as
a
decision
that
okay,
so
we
collectively
decided
now
we
consulted
the
community.
They
supported
this
and
we
collectively
decided
that
this
is
a
move
we
wanna
make
and
here
see
like
a
decision
or
something
like
that,
so
I
want
to
make
that
happen.
I
think
sometime
in
February.
A
D
A
E
Sure,
hey
everyone,
my
name
is
Chris.
A
music
I
had
a
kind
of
the
fun
job
of
both
founding
and
running
the
CN
CF
organization,
which
is
the
home
of
kubernetes.
You
know
Prometheus
envoy,
another
kind
of
Claudia
your
project.
So
when
we
were
starting
up,
you
know
CDF,
you
know
it's
kind
of
spired
by
kind.
A
lot
of
the
you
know,
practices
and
lessons
we
learned
in
C&C
F.
So
you
know,
one
thing
to
note
is
generally
every
Linux
Foundation
initiative.
E
We
separate
both
kind
of
business,
governance
and
technical
governance
from
each
other
right.
So
there's
no,
like
you
know,
kind
of
pay-to-play
type.
You
know
actually
going
on
it's
more
members
or
paying
to
sustain
the
overall
efforts
through,
like
you
know,
events
paying
for
security
audits
and
and
so
on.
So
usually
the
way
it
works.
You
know
like
in
CN.
Cf
is
each
project
kind
of
independently
kind
of
runs
on
its
own,
so
you'll
see
the
same
pattern
here.
E
Where
both
you
know,
Jenkins,
Jenkins,
X,
K
native
you
know,
build
pipelining
will
all
have
their
own
kind
of
independent
technical
governance
right.
You
know
in
the
kerbin
Nettie's
case,
it's
a
little
bit
more
complex
since
it's
a
larger
project
so
like
there,
they
completely
independently
run,
but
they
have
their
own
SIG's.
That
kind
of
subdivide,
work
but
kind
of
you
know
run
amongst
them,
but
in
in
CN
CF,
the
TOC
or
the
kind
of
the
main
technical
board
has
no
direct.
You
know
that
they
can't
tell
the
projects
what
to
do.
E
They
can't
tell
like
kubernetes
you
need
to
like
ship
this
feature
they
could
do
like
overall,
like
hey,
you
should
maybe
have
like
a
security
audit
or
something,
but
they
can
actually
influence
like
roadmap
or
anything
like
that.
They
have
things
around
improving.
You
know
what
makes
it
open-source
project,
but
you
can't
tell
the
project
necessarily
what
to
do
if
that
makes
sense,
yeah
I'm
all
ears.
If
people
have
any,
you
know
questions
or
anything
else.
The
kind
of
ask
asked
me
about
this:
I.
F
Sorry,
hey,
it's
Andrew
I
just
wanted
to
clarify
a
little
bit
may
or
try
to
get
clarified
a
little
bit
further
on
the
plugins
vote.
My
understanding
is
that,
while
some
subset
of
plugins
may
end
up
getting
managed
by
the
the
TSC,
like
you
know,
plugins
that
are
effectively
core
that
the
overwhelming
majority
of
plugins
that
are
developed
by
individuals
or
you
know,
companies
doing
integrations
with
other
services
etc
are
not
going
to
be
at
all
controlled
by
the
TSE.
F
A
I
think
it's
the
only
right.
Basically,
it's
also
a
little
axis
indeed
I
mean
just
like
today.
Didn't
you
score
them?
Of
course
you
don't
maybe
dictate
what's
going
on
in
the
flagons,
there
are
some
collaborations
extra
distance,
etc,
but
that's
really
what
I
think
primarily
what's
gonna
like
what
we
keep
doing
in
this
new
world,
there's
like
a
awesome
of
conversations
about
whether,
like
you
know
some
of
that
should
shift
as
unreal.
As
you
said
that
you
know
there
is
some
interest
in
thought
about.
A
B
Have
one
other
question
with
regards
to
folding
the
Jenkins
into
the
CDF?
Will
we
start
working
under
their
infrastructure,
mainly
what
I
more
mean
like
we'll?
Have
a
slack
channel
things
sort
of
the
way
they
structure
a
lot
of
their
like
the
CNCs
structures,
their
sandbox
projects,
I?
Think
that's
more
of
a
question
for
Chris
yeah.
E
I
mean
it'll
depend
on
how
the
TOC
kind
of
defines
project
structure.
So
what
I
mean
here
is
I'll.
Give
you
an
example.
When
C&C
I
was
first
founded,
there
was
a
bit
of
a
bootstrapping
period
where
the
TOC
had
to
be
formed.
Then
they
kind
of
came
up
with
the
overall
process
of
sandbox
incubation
and
graduation.
I
see
a
similar
pattern
playing
out
here
once
that
initial
TOC
is
is
bootstrapped
at
least
when
I
suspected
I.
Don't
have
the
intimate
knowledge
of
how
the
Jenkins
community
is
fully.
A
A
I
think
the
key
change
would
be
the
project's
budget
think
is
projects
funded
it's
going
to
get
basically
get
subsumed
in
the
CVS,
but
that's
we
be
able
to
kind
of
make
sure
that
these
things
know
basically
be
able
to
pay
off
the
cost,
being
try,
etcetera
and
then
yeah
long,
but
in
a
long
run,
I
think.
Well.
A
A
You
know
if
a
team
then
I
think
it
makes
sense
to
avoid
that
so
I
think
those
conversation
you
hope
the
unfold
in
the
context
of
the
Ingrid
theme
in
the
coming
days,
but
I,
that's
more
like
a
like
a
longer
term
thing,
in
my
mind,
like
it's,
not
gonna,
be
a
thing
that
needs
to
happen
before
we
decide
to
join
or
not,
and
then
they'd
Chris
mentioned
about
this
lace,
unboxing
and
so
on.
So
you
know
be
looking
at
some
other
foundations
and
in
explanations
build
like
in
this.
A
They
do
create
this
monic
labels
around
projects,
the
indicator,
general
status,
so
I
think
it
does
apply
to
say
the
Jenkins
projects
to
taking
section
the
potentiality
that
I
mentioned,
but
I
believe
the
way
I
think
we
are
not
trying
to
map
every
individual
dragon
into
its
own
project.
In
the
eyes
of
the
city,
foundations
and
the
tracking
developers
perspective
doesn't
I,
don't
think
the
moniker.
It's
gonna
make
much
difference
if
anything,
I
think
it's
more
for
the
overall
Dinkins
product
and
Jenkins
X
product.
We
meet
subtle.
A
D
Yeah
I
just
like
to
just
add
2
to
that
specifically
on
where
the
conversations
happen,
whether
that's
slack
or
not,
I
think
it
will
continue
to
be
dictated
by
where
the
community
is
talking
so
Jenkins.
You
know
that
will
be
IRC
and
we're
seeing
a
lot
more
in
Gator
these
days
and
Jenkins
X.
They
have
conversations
in
the
community
slack.
So
that's
not
something
that
will
get
dictated.
That's
you
know
up
to
the
community
where
they
want
to
have
the
conversations
and
expect
in
the
short
term
that
will
that
won't
change.
E
C
A
A
So
there's
that
side
of
the
conversations
and
then
there's
this
other
side
like
what
we
do.
Thinking's
projects
should
be
at
the
next
step.
I
guess
that
that's
kind
of
like
maybe
it's
a
good
way
to
turn
the
table
around
Oviedo
I
know
what
what
should
we?
Let's
say,
the
leadership
the
committee
needs
to
be
doing,
I
mean
again
like
I
know.
A
The
only
key
milestone
for
me
is
like
basically
Institute
is
to
build
to
record
some
like
a
TV,
some
ceremony
or
formal
PT
record
this
consensus
and
decision,
but
I
wanna
make
sure
that
it
comes
across
as
a
natural
step,
not
something
forced
upon
people.
So
we
there
are
like
a
nice.
Q&Amp;A
is
a
part
of
that
the
emails
rate
was
part
of
that.
A
A
E
E
Sure
I
mean
we
actually
have
a
legal
entity
all
set
up
there.
So
you
know
I,
don't
know
if
you've
ever
gone
through
the
experience
of
getting
business
done
in
China,
but
there's
this
complicated
like
ICP
license
that
you
have
to
do
in
order
to
register
like
a
WeChat
handle
for
Jenkins
and
manage
it
properly.
We
could
do
events,
you
know
one
option
for
the
Jenkins
community
and
kind
of
the
city
of
community
in
generals.
We
have
open
source
summit,
China
or
Yukon
China
you're
more
than
happy
to
do
like
a
co-located
event
there.
E
You
know
I,
think
one
thing
I'll
be
kind
of
blunt
with
folks
is
like
there's,
there's
always
a
bit
of
kind
of
like
a
bootstrapping
period,
where
you're
just
kind
of
getting
the
thing
you
know
up
and
running
and
operational.
So
you
know
just
please
expect
that
it
takes
a
while
to
kind
of
about
this
to
get
fully
fully
operational.
A
A
F
A
In
there
and
then
the
Tyler
I
think
this
is
a
he's
he's
also
like
a
key
part
of
getting
this
yeah
cool.
All
right,
then,
we'll
keep
talking
about
this.
So
thanks
for
thanks
for
being
a
part
of
this,
especially
Rick
I
know
again,
like
you
tied
me
up,
I
know.
This
is
a
crazy
hour
so
and
I'll
talk
to
you
in
Doctrine
some
other
place
and
see
you
said
thanks
everyone.