►
Description
How the Tekton Community is Driving its Growth and Adoption - Adam Roberts, IBM
Adam's been a familiar figure in the Tekton community since it started, coming out of knative-build, so has been able to see it grow and develop rapidly. As a Tekton Dashboard maintainer, and someone that's involved in Tekton everyday, Adam's looking to use this platform to highlight that not only is the project itself awesome, but the community is helping to drive its growth and adoption. Adam's specifically referring to the "not just on GitHub" events that regularly occur and will be providing particular examples and insights into what makes the community project something special.
A
A
A
I
worked
on
the
tipton
dashboard
weapons
extension,
so
lots
of
go
code,
lots
of
tecton
code
running,
go
lots
of
javascript
and
react,
and
I've
got
a
decent
background
in
open
source
projects
in
general.
So
you
can
find
me
on
github,
usually,
but
also
on
linkedin
as
well.
That's
really
what
I
do
in
my
day
job
and
what
I
do
outside
of
that
day.
A
Job
is
I'm
an
ambassador
for
continuously
foundation,
and
that
means
doing
things
like
reaching
out
to
folks
getting
them
to
submit
things
how
it
talks
working
with
people
on
talks,
maybe
doing
meetups.
Eventually,
things
like
making
sure
tech
time
itself
is
developing
in
accordance
with
our
guidelines
and
bringing
the
community
into
the
foundation
and
the
opposite
way
around,
so
that
we
can
make
sure
the
project
is
growing
and
we're
succeeding.
I
guess
I'm
also
on
the
subcommittee
for
outreach
and
I'm
a
co-creator
for
twitch.tv
cd
foundation.
A
We
have
two
ibm
colleagues,
dewan
and
jj,
and
we
basically
stream
every
so
often
on
tuesdays,
usually
protect
on
jenkins,
x
and
anything.
That's
really
cdf
related
outside
of
that
so
away
from
screen
completely.
Now
I'm
a
keen
powerlifter,
I'm
into
the
green
bay
packers
and
my
football
team
and
a
lot
of
music
production
so
either
making
trance
in
ableton
or
with
my
guitars,
making
some
you
know:
metal,
music
and
some
cool
riffs.
A
That's
really
me
in
a
very
small
nutshell
who
do
I
think
you
are
then,
so
I
think
this
talk
is
real
for
people
that
have
heard
of
protect
them.
You
want
to
know
what
we're
up
to
so
how
the
community
is
set
up
and
functions
on
a
day-to-day
basis
and
someone
that
may
want
to
make
their
own
community
and
look
for
an
awesome
standard.
So
maybe
it's
a
new
open
source
project.
A
You
have
to
figure
out
how
to
grow
that
project
and
really
develop
it
or
maybe
just
water
contribute
to
tecton
for
the
very
first
time
you
want
to
know
what
it's
like.
You
know
where
the
project
repository
is
all
set.
If
we
have
meetings,
if
you're
on
slack,
that
kind
of
thing
may
be
quite
useful
for
you.
I
think
the
main
claims
I'm
making
are
threefold.
You
know
one
is
that
tecton
is
growing.
Two
is
that
it's
being
adopted
at
a
greater
rate
and
the
community
itself
is
part
of
that
growth.
A
I
think,
if
you're
going
to
go
away
from
this,
knowing
a
few
things,
it's
basically
this
side
how
our
community
works.
What
are
the
evidences
for
that
growth
and
adoption,
some
education,
so
you
can
join
our
community
and
really
get
stuck
in.
Maybe
it's
through
your
first
pull
request,
or
you
know
you
want
to
figure
out
where
our
meetings
are
held
and
if
you're,
watching
this
as
part
of
cdcon,
you
can
ask
me
anything.
A
You'd,
like
in
the
q,
a
section
I'm
going
to
try
and
make
this
20
minutes
in
one
take
and
leave
10
minutes
at
the
end
for
your
questions
so
take
some
growth.
I
think
the
main
indicators
are
those
things.
Basically,
so
do
you
get
more
people
doing
more
pull
requests
more
contributors,
more
contributions?
A
Do
you
have
releases
that
have
got
new
features
in
them
on
a
consistent
basis?
So
is
the
project
itself
getting
better
and
more
stable
as
a
community
I'll
be
seeing
more
people
using
us?
So
not
just
people?
Actually,
it's
other
projects
using
us
that
may
be
in
the
adoption
section,
but
I
think,
as
tekton
gets
more
popular,
it
would
lead
to
being
adopted
more
and
by
having
a
strong
community.
A
I
think
you
know
it
helps
if
that
on
two
fronts,
people
get
confidence
and
they
know
if
they
want
to
change
something
I'll
have
an
enhancement.
It'll
be
welcomed,
so
contribute
is
increasing.
What's
a
nice
way
to
figure
that
out?
Well,
if
I
go
to
this
link
here,
I'm
going
to
go
to
this
tab.
Actually
I
don't
know,
though,
there's
a
good
final
dashboard
for
new
contributors
to
text
on,
and
you
can
see
here
quite
a
few
in
september.
A
I'm
recording
this
for
24
for
september,
and
you
can
see
you
know
for
september,
we've
been
quite
good
and
this
is
across
all
of
texan.
It's
not
just
you
know
the
pipeline
component
that
you
install,
maybe
it's
part
of
the
cli
or
the
dashboard
or
the
website,
or
the
community
or
friends
repository
there's
plenty
of
places.
You
can
get
involved
in
that's
covered
by
this
table
here.
So
I
think
that's
quite
good
to
be
getting
new
new
folks,
so
I
think
take
that
box
off
how
about
this
new
releases
of
new
features.
A
A
You
can
see
lots
of
things
going
on
here,
lots
of
new
features
and
fixes,
and
most
importantly,
for
this
talk
contributors.
So
plenty
of
people
nearly
two
dozen
there,
I
would
say,
are
pitching
in
and
basically
adding
what
they
think
would
benefit
the
project.
Be
it
fixes.
You
know
enhancements
you
name,
it
really
need
to
see.
A
So
I
think
yes
we're
getting
new
voices.
I
can
go
to
any
of
these
places
and
see
the
same
kind
of
story.
It's
often
a
few
people
doing,
let's
say
the
bug
fix,
so
here's
triggers
and
then
quite
a
few
more
people
do
the
actual
big
milestone
releases.
The
major
well,
the
minor
voice
is
in
our
case
so
0.70
for
example.
A
So,
what's
next
github
insights,
that's
a
handy
way
to
figure
out
what
the
contribution
pattern
looks
like
over
a
period
of
time.
So
if
I
go
to,
let's
go
back
to
let's
say
pipeline,
if
I
go
to
this
insights
button
here,
I
can
see
contributions.
All
the
time-
and
you
can
see
here
is
quite
a
nice.
You
know
little
graph,
it
doesn't
go
like
it
doesn't,
go
up
and
then
drop
and
nobody
maintains
it
ever
again.
A
It's
quite
consistent,
even
though
we
know
summer
months
are
still
getting
quite
a
few
folks,
so
that's
quite
good
to
see
and
we
can
scroll
down
and
there's
no
particular
area
where
nobody
pitches
in
doesn't
you
know,
go
inactive
for
a
while,
and
people
have
got
you
know,
let's
say
eight
or
nine
commits,
which
is
really
good,
and
quite
a
few
of
these
are
substantial
things.
It's
like
you
know.
Let's
say
it's
support
for
a
platform
or
bug
fix.
A
We
then
have
the
next
section
of
this
presentation.
This
is
all
about
adoption,
so
more
products
out
there
using
tekton
or
more
internal
teams,
from
my
perspective,
at
least
using
tekton
or
more
dependent
projects,
so
you'll
burn
something
completely
new
and
you
think
you
know
what
you're
really
handy
to
use
text
on.
I'm
going
to
show
you
a
few
of
those
next
so
depends
on
open
source
projects.
A
I
think
of
a
few
immediately.
One
is
jenkins
x,
two
is
cabanero.
Three
is
the
openshift
pipelines
by
red
hat
and
four
is
an
extension
I
think
for
cube
flow,
where
you
can
basically
write
your
q
for
pipelines.
You
can
take
them
under
the
covers,
so
those
are
the
ones
that
I
personally
know
about.
If
you
look
at
some
of
these,
they
are
quite
they
are
quite
popular
jenkins
x,
for
example,
if
I
go
to
their
main
website,
you
know
it
looks
quite
slick
quite
useful,
but
how
about
502
jenkins
x
on
github?
A
I
want
to
see
how
people
have
been
starring.
This
thing,
that's
quite
a
good
usage
indicator,
in
my
view,
you're
not
going
to
get
me
a
stars.
Otherwise,
if
it's
not
very
good.
So
if
I
go
to
jenkins
x,
slash
jx,
if
I
move
myself
a
little
bit
out
of
the
way
you
can
see
here,
we
have
almost
3.7
k
stars
and
you
can
then
go
on
to
see
all
the
releases.
You
know
all
these
releases.
I
think
that's
because
whenever
there's
a
new
commitment,
that's
merged,
a
new
voice
would
also
happen.
A
So
it's
you
know
real
continuously
great
integration
and
therefore
going
on
because
things
are
basically
being
added,
they're
being
tested,
they're
being
built
and
they're
being
pushed,
and
you
go
straight
into
if
you
like
production,
which
is
the
gate
of
release
straight
away
after
it's
passed
all
those
quality
checks,
so
jenkins,
x,
the
user
of
tecton.
I
can
prove
that
if
I'll
do
a
search,
let's
say
on
texting
up
here,
you
can
see
lots
of
imports
from
both
go
for
yaml
and
there's
just
plenty
of
it,
so
definitely
a
big
user
of
tekton.
A
I
encourage
you
to
check
out
the
other
ones
for
yourself
and
just
if
there's
anything
else,
you'd
like
to
add
maybe
to
the
friends
of
the
participant
I've
mentioned
this
later.
Please
do
a
pull
request
and
let
us
know
how
you're
using
text
more
examples
then.
So
I
actually
did
a
question
under
the
text
on
slack,
saying
hello.
Anybody
like
to
share
their
adoption
examples
and
I
had
a
few
responses.
A
I
had
eddie
charlie
his
name.
I
think
charles
and
he's
now
a
dashboard
maintainer
protectom
out
of
economy.com
betsy
benfo
mentioned
30
plus
services
using
techton
in
queen
for
production
usage
as
well,
and
the
ibm
cloud
is
a
continuous
delivery
offering
or
based
on
text
on
a
long
development
team
starting
to
use
tecton
as
well
in
production.
So
this
is
where
we're
writing
our
code.
A
Please
do
so
so
cd.foundation
has
a
link
at
the
top
submitting
blog
posts
and
case
studies
and
all
sorts
webinars
podcast
entries,
and
you
can
really
start
to
share
what
you're
doing
protects
on
with
the
wider
community.
In
this
way
and
again
that
friends
of
position
were
mentioned
soon
as
well,
so
here's
eddie
charles
aka,
charles
and
he's
mentioned
here
that
they
used
text
on
pipelines
and
takedown
dashboard
hosting
their
in-house
cicd
platform.
A
They
run
jobs
and
every
single
pull
request
and
commit
it's
very
effective.
And
what
I'd
like
to
draw
your
attention
to
is
something
that
he
mentions
at
the
end,
you
managed
to
break
a
few
things
a
few
times.
The
community
was
always
there
to
help
fix
things,
and
that's
because
you
know
we're
very
welcoming
to
people,
experiments
and
trying
new
things.
There's
always
somebody
on
slack
who's,
gonna,
say
yeah,
I'd
love
to
help
out.
You
know.
Here's
me
to
try
and
we
welcome
those
contributions.
A
So
it
was
a
nice
read
for
you
to
do
there
and
basically
get
a
lot
of
guidance
from
the
project
owners
and
maintainers,
and
anything
that
you
would
like
to
have
been
added
was
basically
working
with
open
arms.
It's
not
a
case
of
where
we
say.
Oh,
we
don't
want
that.
It's
yeah!
This
looks
quite
handy,
let's
get
this
in
there
and
then
the
dashboard
is
using
their
offering.
A
So
when
they're
doing
their
pull
requests,
you
can
use
the
dashboard
and
see
what's
going
on
next
example,
bits
of
info,
so
they've
mentioned
in
their
blog
post,
which
can
all
check
out
yourself
in
more
detail.
They
mention
using
tecton
for
more
than
30
different
applications
from
various
contexts,
including
development,
qa
and
production,
and
they
mentioned
there.
You
know
we're
very
thankful
for
their
tech
time
for
folks
making
a
great
platform.
We
can
all
build
upon,
and
you
can
see
my
response
there.
A
A
A
Governance
of
the
cd
foundation
was
key
to
ensure
the
project
remained
open
with
no
one
compliment
running
in
the
show.
We
feel
tech
has
a
unique
place
in
the
students,
close
ties
to
kubernetes
and
native
communities
and
aligns
with
our
future
so
mentioned.
All
of
that,
and
simon
himself
is
a
known,
contributed,
concrete
detector.
You
can
see
pull
requests
by
him,
he's
off
on
the
weekly
meetings,
giving
updates
and
really
trying
to
get
engaged
with.
The
community,
so
we
can
make
sure
tecton
itself,
is
as
good
as
can
be
for
our
customers,
product
development
teams.
A
So
at
the
start
I
mentioned
using
tekton
to
basically
build
and
push
our
own
code
for
our
own
development
projects.
This
is
very
much
the
thing:
we're
starting
to
use
tips
on
more,
more
ibm
that
you
can
show
me
all
the
builds
for
our
entire
project
in
terms
of
pull
requests
pushes
merges
and
get
the
status
of
them.
A
It
gives
us
confidence
to
do
that,
so
our
community
itself.
How
do
we
function
and
we'll
take
you
through
github
slap,
the
weekly
events
and
by
the
way,
the
lots
of
captain
tecton?
If
you
do
a
pull
request
and
you
were
to
do
slash,
meow
on
that
pull
request
and
then
a
noun,
a
reverb
or
maybe
slash
me
out
hats,
you
would
see
a
picture
of
a
cat
with
a
pic
with
a
hat
on
ideally
from
the
cat
api,
so
we're
really
big
on
cats
so
slack.
A
This
is
where
our
sectional
lives
and
it's
our
main
source
of
q,
a
in
the
community.
We
have
dev
channels
and
user
channels
for
project
areas.
So
if
you're
a
developer
just
pipeline
dev,
if
you're,
just
a
user,
you
can
just
use
pipeline
and
the
active
folks
in
various
areas
both
for
project
areas
and
across
the
world
that
are
regularly
available.
A
What
we
also
have
is
a
github
setup
that
basically
encourages
you
to
tell
us.
What
do
you
have
tips
on?
We've
got
a
community
repository.
This
is
both
contributors
and
watchers
of
what
we're
up
to.
So.
If
you
want
to
figure
out,
you
know
how
to
join
our
meetings
or
sac.
That's
the
place
for
you,
the
friends
place
as
well.
The
friends
of
puzzle
tree
is
where
you
can
tell
us.
A
If
you're
using
tecton,
you
can
tell
us
what
you're
using
it
for
how
you're
using
it
if
it's
you're
in
production
or
not
you're
evaluating
it
or
you
just
want
to
share
a
success
story.
At
the
same
time,
I
should
expect
the
actual
project
repositories
themselves
for
the
main
coders,
as
well
as
the
docs
weekly
events.
There
are
many
of
these
so
for
every
single
project
in
tecton,
of
which
there
are
many
dashboards,
cli
triggers
website
pipeline
they're,
basically
weekly
meetings
that
go
through
what's
going
on
in
that
project,
you
know,
is
it
changing?
A
What's
been
changed,
what's
going
to
break
things
in
the
future,
there's
a
set
agenda,
there's
room
for
playbacks
and
cool
demonstrations
at
the
end.
They
are
all
recorded
and
there
are
very,
let's
see,
elaborative
notes
for
each
of
them,
so
you
can
see
people's
thoughts
and
musings
and
you
can
basically
go
back
over
a
year
and
figure
out
what's
been
going
on
for
each
project,
since
I
guess
the
beginning
of
time,
protect
them
youtube
and
twitch.
A
So
what
we
like
to
do
is
stream
text
on
every
few
weeks
at
that
link
there
as
well
jenkins
x,
recently,
there's
a
foundation
channel
on
youtube
as
well,
and
there's
lots
of
talks
already
by
the
community
and
various
companies,
so
red
hat,
ibm,
google
and
cloud
beers.
I
encourage
you
to
submit
your
own.
A
So
if
you're
using
techton
do
a
cool
video
on
it,
let
us
know
what
you're
up
to
and
then
the
concluding
thoughts
on
this
I've
told
you
how
active
it
is,
but
I
think
the
main
selling
points
are
these
community
is
giving
users
and
developers
that
confidence
they
know
if
they
find
a
bug
they
can
raise
it.
No
one
will
say:
oh
it's
a
terrible,
terrible
issue.
It
will
get.
You
know,
responded
too
quickly.
A
There'll
be
a
new
release
pretty
quickly
and
people
get
the
confidence
and
that
someone
is
available
to
help
out
people
are
encouraged
to
try
new
things
and
experiment.
In
fact,
we've
got
our
own
experimental
repository
on
tact
on
where
you
can
basically
put
your
ideas
in
and
eventually,
if
it's
not
quite
popular
and
useful,
I
can
graduate
to
being
a
real
thing.
That's
maintained
by
everybody
else.
A
Active
people
in
various
geographies
plays
a
massive
role
in
this.
It
is
what
I
mentioned
earlier.
You
could
be
in
india,
let's
say,
and
you
want
to
work
on
triggers
chances
are.
If
you
say
something
on
slap,
some
will
respond
to
you
quite
quickly,
and
then
we
have
a
good
discussion
about
making
an
issue
helping
you
out
and
going
from
there.
The
regular
events
as
well
are
really
useful,
as
you
might
step
back
from
doing
a
pure
development
role
in
something
that's
more
architectural.
A
I
would
like
you
personally
to
join
our
tech,
team
and
cdf
communities.
Add
yourself
as
a
friend
via
the
techton
cd
friends,
depository
submit
your
issues.
If
it's
a
new
feature,
if
it's
a
bug,
let
us
know
and
try
texting
out
for
yourself
get
involved
on
slack,
say:
hello,
join
the
working
groups,
give
us
a
wave,
say
hello,
and
last
year
it
was
a
really
cool
blog
post
on
tech
tom.
A
It
was
2019
detective
in
focus,
and
I
had
a
lot
of
people
from
various
companies
pick
shinkins
saying:
here's
what
takedown
is
up
to
and
what's
more
in
the
future,
if
there's
a
2020
post,
that
would
be
great
and
I'd
love
for
you
as
a
community
to
be
involved
in
that.
So
please
join
him
either
through
slack
techton
or
cdf
slack,
maybe
through
github
anything
you
like
and
please
let
us
know
what
you're
up
to
so.
This
concludes
the
main
portion
of
this
talk.
A
You
know,
as
I've
said,
this
should
be
plenty
of
time
for
q.
A
at
the
end
of
this.
So
please
ask
me
anything:
you'd,
like
I'd
love
to
stick
them
out
and
answer
your
questions.
As
I
mentioned,
though,
you
can
find
me
on
linkedin
as
well
at
this
place
here
and
yeah.
Thank
you
all
for
this
talk
and
please
enjoy
this
conference
have
a
great
day.
Everybody
bye
for
now.