►
From YouTube: [Online Meetup] Kong Community Programs
Description
In this call, we talk about Kong Community programs, where we’re at and where we’re headed, including an open forum for feedback and discussion from the community.
Join our next Online Meetup: https://konghq.com/online-meetups/
A
All
right
so
welcome
to
today's
July
community
call
and
thank
you
all
for
joining
us,
so
I
know.
I'm
gonna
do
face
to
many
of
you.
I'm
Caitlin
I
just
recently
joined
comm
to
lead
the
developer
and
community
marketing
function.
So
I'm
super
excited
because
today,
I'm
going
to
talk
a
little
bit
about
some
of
the
work,
Kevin
and
I
are
doing
I
know
many
of
you
are
familiar
with
our
community
programs,
but
I.
A
B
C
E
A
Let's
see
I
think
my
introduction
slides
next,
so
leaving
into
that
so,
like
I
said,
I
just
joined
Kong
about
four
weeks
ago
now
to
work
on
developer
and
community
marketing.
So
what
that
means
is
really
making
sure
that
the
community
around
the
open
source
project
has
the
support
the
resources
that
they
need
to
make
it
a
really
positive
journey
for
them.
So
with
that
I'll
be
working
really
closely
with
Kevin
he's
in
China
right
now,
so
he's
not
able
to
join.
A
So,
like
I
said
today,
I
want
to
just
take
a
little
bit
of
time
to
go
over
what
our
community
programs
are
some
ways
for
you
to
get
involved
and
then
open.
This
up
to
a
discussion,
you
know
we're
really
taking
this
into
high
gear
for
over
the
next
year,
so
I
want
to
make
sure
that,
like
whatever
your
wish
list
is
we're
helping
to
make
that
happen
as
well.
So
the
first
program
that
we
have
here,
we
have
our
5
Kong
champions
right
now.
A
You
know
Jeremy
mentioned
that
he's
one
of
them
they're,
really
frequent
contributors
to
the
Kong
project
and
the
community
around
it.
So
this
is
a
list
of
champions
that
we
have
here
on
this
slide
and
I
have
a
link
here
to
the
application
for
anybody.
That's
interested
in
applying
to
the
program
as
well,
and
then
all
of
us
will
be
out
long
summit
in
San
Francisco
this
year,
so
I
think
we'll
get
a
chance
to
meet
face
to
face
which
will
be
great.
A
A
So
we
are
getting
ready
to
launch
the
schedule
with
a
and
hopefully
the
next
two
weeks
or
so.
I'm
really
excited
we're.
Gonna
have
a
lot
of
great
sessions
expert
panels,
some
workshops
and
I
kind
of
have
just
a
high-level.
What
topics
we're
going
to
be
covering
here
and
then,
like
I,
said
we're
a
hard
at
work
finishing
out
the
schedule
so
we'll
be
announcing
that
in
the
coming
weeks,.
E
Just
to
jump
in
there
really
quickly,
Kaitlyn.
The
Kong
summit
is
a
pretty
wide
range
of
folks
this
year,
it's
community
members
and
users,
it's
some
customers
and
partners,
and
we
really
value
that.
There's
a
lot
of
you
here
who
take
the
time
every
month
to
join
our
community
participate
as
well
as
all
the
other
work
that
you're
doing
related
to
your
jobs
and
Kong
outside.
So
this,
this
discount
ticket
code
won't
expire,
but
it's
kind
of
our
gesture
that
you
know
we
really
want
our
community
members
here
and
those
of
you.
E
A
Then
we
also
I
just
wanted
to
briefly
cover
our
contributor
t-shirts.
So
if
you
are
a
contributor
to
the
kong
project
and
you're
eligible
to
get
a
contributor
t-shirt,
we
have
a
new
t-shirt
design
that
we're
pretty
excited
about,
and
so,
if
your
pull
request
was
accepted,
fixes
a
bug
has
a
significant
contribution,
definitely
fill
out
the
form
to
get
your
t-shirt.
A
Great,
so
these
next
few
slides
I'm
going
to
start
opening
about
to
discussion
again,
and
so
we
are
one
of
the
things
we're
really
focused
on
right
now
is
building
out
our
meetup
schedule
for
the
remainder
of
the
year
and
then,
where
we're
going
to
be
out
next
year.
So
we
just
recently
got
done
with
some
meetups
and
Beijing
Shanghai
and
Su
Su
Kevin's
on
he
is
out
in
Asia
for
the
next
few
weeks.
A
B
E
E
C
It
we
talk
to
or
rewrite
or
already
about,
the
media
possibilities
in
Germany,
so
maybe
there's
something
we
can
pin
it
up
so
I'm
still
in
talk
with
some
of
our
branch
managers,
that's
called
centric,
so
maybe
there
is
some
more
possibilities
and
more
cities
around
Germany.
So
this
is
something
we
can
yeah
develop.
The
next
year
is.
F
A
A
E
Yeah
on
the
community
call
or
the
community
page.
Currently,
if
you
scroll
down
about
half
way
through
there's
a
scrolling,
runabout
section
events,
so
we
list
upcoming
meetups
there.
We
also
tend
to
post
them
on
I,
want
to
say
cog,
nation
and
possibly
even
get
her
as
well
as,
if
there's
one
local
to
the
area
we
send
out
in
an
email
and
advanced
anyone
who
kind
of
fits
our
regional
criteria
there
in
the
database,
like
your
location,
is
Germany
will
send
you
something
in
Germany.
A
And
then
one
other
thing
I
wanted
to
mention
in
this
call
is
that
we
are
looking
at
releasing
multi-language
support
for
plug-in
development.
So
basically,
this
would
mean
that
you
could
interact
with
the
plugins
in
your.
You
know,
programming
language
of
choice,
so
we're
aiming
to
release
the
first
one.
It
comes
from
it,
we're
going
to
start
with,
go
but
curious
what
languages
y'all
are
using
that
you
would
like
to
see
this
available
in.
F
A
We
have
there
some,
you
know
anything.
We
didn't
cover
here
that
you
think
of
further
down
the
line.
Let
us
know,
as
we
start
building
this
out,
but
definitely
look
forward
to
that
coming
out
consummate
so,
like
I
said
I
just
you
know,
I
want
to
talk
a
little
bit
about.
You
know
what
we're
doing
going
forward.
A
B
Personally,
I've
always
thought
y'all
have
done
a
really
good
dog
you're,
a
really
good
job,
with
your
documentation
every
now
and
then
obviously
you
know,
as
you
create
new
features
and
new
things
come
out.
It
gets
out
of
date,
but
you
know
y'all
do
a
pretty
good
job
catching
that
up
and
keeping
it
up.
Today.
One
thing
I
would
say
there
probably
isn't
a
whole
lot
on
as
like
links
out
to
interactive.
You
know
applications
to
kind
of
just
stuff
in
a
sandbox,
or
maybe
some
video
demonstrations
as
well
on
the
main
website.
C
B
Yeah
plus
it's
Docs
is
code
right,
so
people
can
go
in
and
you
know
make
the
changes
and
then
y'all
review
them
to
bring
them
in
which
is
really
nice,
because
so
you
can
get
that
community
engagement
around
your
documentation
as
well,
which
is
really
slick.
We've
kind
of
adopted
that
sort
of
stuff
internally
too,
with
Docs,
is
code.
A
B
So
yeah
right
now
you
all
do
like
a
Kong
forum
post,
at
least
for
the
community
edition
I
know
for
enterprise.
I'll,
do
kind
of
the
email
distribution
list
format
I
mean
the
the
current
approach.
Isn't
too
bad?
Usually
you
know
a
github
stamp
and
a
change
log
and
the
the
calling
forum
post
I
guess
you
could
start
interchanging.
If
you
wanted
to
you,
could
you
know
post
as
part
of
the
an
email
group
as
well
to
the
community,
that
there's
been
an
update
to
the
Kong
Community
Edition?
B
A
B
B
A
B
Well
well,
my
perspective.
Y'all
are
probably
the
first
application
that
I've
worked
with
from
like
an
open
source
community
perspective,
so
I
don't
really
have
a
whole
lot
of
visibility
into
how
other
companies
are
driving
that
and
what
approaches
they
take
that
are
positive,
I
think
I'll
do
a
good
job
with
it,
I'm,
not
sure.
If
air
Heron
has
any
community
engagements
he's
worked
with
with
other
companies
before
or
other
applications
before
that
he
knows
how
they
drive
things.
I.
F
Don't
think
I'd
I
don't
know
if
it's
from
a
community
perspective
is
a
road
map
of
the
plans,
it's
somewhere
in
the
community
Docs
somewhere,
that
you
can
take
a
look
and
say
not
just
the
immediate,
like
release
candidates,
but
in
three
six
a
year.
These
are
what
we
want
to
build
out,
or
these
are
the
things
we're
thinking
of,
and
maybe
those
exist
and
I
haven't
I
just
don't
know
where
they
are
located.
B
Yeah,
that's
true
publicizing.
The
future
roadmap,
probably
is
a
really
good.
Positive.
I
know
I
seen
a
t-bo's
a
slide
deck
that
he
has
presented
on
I,
think
in
Japan,
where
he
talks
about
kind
of
the
future
of
some
of
the
stuff
Kong's
working
on,
but
I
haven't
actually
seen
it
publicized
on,
like
Kong
HQ
or
in
the
github
repo
itself
for
the
future
roadmaps.
Maybe
that
would
be
a
good
idea.
Yeah.
A
F
I
guess
from
our
perspective,
as
a
user
of
it,
where
it
comes
into
play,
not
just
to
see
it,
but
if
there
are
things
on
our
internal
wishlist
or
things
that
we
want
to
do
as
well,
and
if
we
see
that
you
working
on
it,
then
we
can
pitch
in,
or
you
know
have
some
conversations
around
it
too.
So
that's
my
ask
of
why
I
was
like
would
like
to
love
to
see
that
information
where
you
guys
are
thinking
to
take
things.
A
B
I
was
just
gonna
get
the
shout
out.
I
really
wanted
to
thank
y'all
for
some
of
the
efforts
we
had
recently
with
you
around
a
keepalive
issue.
We
had
your
principal
engineer:
Tebow
had
a
nice
little
patch
fix
for
how
to
do
a
key
blog
differently
at
the
nginx
layer,
so
at
the
webserver
layer,
which
was
kind
of
some
deep
stuff
and
that
really
helped
us
out
and
really
gave
us
a
lot
of
performance
and
platform
benefits
within
our
enterprise.
G
G
Select
we
say
in
the
previews
community
goes:
another
tree
comes
with
the
gr
pieces,
you've
all
right.
So
that's
the
main
women
addition
to
E
Plus
open
receive
one
15.8
as
well
as
header
by
a
rotting
by
arbitrary
request.
Headers
to
those
are
topics
we
covered
I.
Think
in
a
couple
committee
calls
ago,
maybe
maybe.
G
And
the
EE
version
yeah
so
for
Enterprise
to
be
based
on
the
comm
1.3
Community
Edition,
which
is
not
even
released
yet
I-
think
we're
looking
at
a
late
summer-
probably
maybe
even
closer
to
September
I
would
say,
but
I
mean
we
don't
have
his
teammates
for
that,
yet
so
I'm
really
playing
a
guessing
game
here.
So
don't
quote
me
on
that.
Currently
the
team
is
working
on
supporting
Kong
number
two
and
the
courage
configuration
in
enterprise
and
then
after
one
of
the
three
is
released.
G
F
G
That
it
is
also
a
protocol
that
we
are
planning
on
supporting
a
venturi
I
think
we
haven't
quite
yet
decided
the
path
forward
for
it,
but
I
can
also
that
he
can
speak
to
that
as
well,
because
if
I
remember
correctly,
one
of
these
company
hakonsen
projects
was
actually
supporting
graphically
instead
of
calm
but
I.
Think
what's
more
on
the
admin
API
side,
if
I
remember
correctly,.
D
So
at
the
time
that
was
like
two
years
ago,
at
the
stage
of
renewal
I'm
erase
for
that
was
not
quite
there
yet,
but
ya
won't
have
to
see
how
the
things
are
going
right
now
with,
but
even
then
we
could
could
always
bridge
libraries
with
another
language,
excellent
yeah.
It's
definitely
something.
That's
that's
doable,
there's
nothing
fundamental!
That
will
prevent
us
from
supporting
it.
G
Yeah,
it's
it's
definitely
a
a
something
like
an
item
that
we've
been
looking
at
and
we
we
have
an
online
for
the
road,
not
exported
long
term,
maybe
because
we
haven't
prioritized
it
quite
yet,
but
Kong
is
moving
more
and
more
to
so,
probably
not
for
cars
right.
So
we
started
with
layer.
Four
like
just
you
know:
TCP
we
move
into
UDP.
Eventually
we
have
charity
scene
number
three
and
then
graphic
is
another
ones
that
is
unorganized
for
sure,
but
we
don't
have
a
timeline.
Yet
we
we
are.
G
Maybe
we
can
talk
a
little
bit
about
upcoming
releases,
so
after
one,
two
three
with
no
the
new
features
that
we
talked
about,
we're
looking
at
1.4
earlier
this
summer
as
well,
where
we're
planning
on
sort
of
doing
a
consolidation
release
with
you
know,
bug
fixes
improvements,
any
sort
of
usability
and
performance
improvements
we
can
make.
So
we
we
have
a
few
of
those.
G
From
the
perspective
of
you
know,
maybe
I've
been
able
to
support
a
be
testing.
Our
request
shadowing
or
some
versioning
not
like
in
the
car
right,
so
being
able
to
specify
a
multiple
upstream
spare
service
and
being
able
to
have
say
a
service
center
request
to
I
want
three
more,
the
other
based
on
different
parameters
to
do
like
wording
upgrades
or
to
do
versioning
or
request
shadowing
and
that
sort
of
but
being
able
to
configure
motor
products
through
the
same
service
means
that
you
were
able
to
use
it
as
you
wish
right.
G
So
it
could
be
each
other
ability
from
the
version
of
the
service
or
it
shops.
You
could
be
different
data
center
for
the
service,
so
you
try
to
look
or
data
center
a
copy
of
the
service
first,
so
that'sthat's.
The
sort
of
improvements
working
out
from
under
that
again
on
cannon
would
be
at.
This
point
would
be
like
some
September.
D
Yeah,
just
so
just
I,
don't
know
that
one
thing
that
kind
of
some
swear
that
sounds
like
more
future
happy
like
one
cup
one
was
about
today
and
my
dreams
coming
up
with
Jeremy
seeing
and
some
of
them
are
more
really
about
solidifying
the
platform
performance
improvements
in
the
first
controller
and
what
we
want
to
do
that
same
kind
of
work
as
a
41.2
41.4.
So
it's
kinda
healthy
for
the
project,
because
features
are
flashy
and
features,
but
at
same
time
as
the
project
moves
forward.
G
So
those
are
improvements
that
we're
looking
at
shipping
in
income
1.3,
especially
get
to
the
epson
part,
which
is
coming
soon
in
to
the
shape
of
a
PR
and
will
also
eventually
be
looking
at,
which
were
continuous
against
authorizing
cassandra
and
other
forms
of
our
connections.
That
count
opens
yeah,
so
maturities
is
a
big
year
for
us
as
well,
and
the
other
second
thing
that
I
wanted
to
talk
about
was
the
improvements
we're
planning
on
making.
So
for
this,
probably
looking
at
wonder
for
being
like
a
consolidation
with
these
occasional
said.
G
Like
less
feature,
heavy
based,
so
nginx
configuration
informants
in
the
sense
that
we
want
to,
you,
know,
hide
and
avoid
the
pattern
of
creating
custom
nginx
templates
over
and
over
again,
which
we
think
is
sort
of
a
heavy
task
for
users
to
to
do
and
to
have
to
upgrade
this
template
as
their
quick
conversion
etc.
So
we're
looking
at
in
like
new
ways
of
configuring
nginx.
The
other
configurations
are
that
injects
directive,
which
is
something
that
Harry
has
been
working
on.
G
Harry
who's
in
the
car
right
now,
since
1.1
I
believe
and
we've
sort
of
moved
towards
a
pattern
where
we
want
to
to
rely
on
defaulted,
nginx
injective
directives,
instead
of
having
to
say
copy
the
whole
region,
X
template
and
configure
as
a
certain
protocol
that
you
want
to
enable
you
can
just
edit
one
property
in
the
config
file,
which
is
which
maps
to
nginx
and
another
alternative
and
we'll
have
components
into
the
nginx
configuration
file
as
we're
back
with
include
directives,
and
you
just
be
able
to
turn
the
whole
engine.
X
sub.
G
Configuration
of
that.
If
you
want
to.
If
you
have
like
say
like
more
servers
that
you
want
to
run
some
more
nginx
server
box,
or
things
like
that,
so
so
there's
our
other
infamous
that
we're
looking
at
making,
which
you
know
for
everyday
users
of
Kong.
It
could
be
different.
We
believe
not
quite
as
shiny
as
char
pieces
for
yeah.
G
G
F
We
have
a
really
really
heavy
cough
baby
face,
but
nobody
at
least
in
our
enterprise,
drives
it
through
a
single
gateway.
Like
that
it's
it's
is
never
even
father
request
of
us
as
the
owners
of
the
Gateway
to
like
a
Kafka
topic.
I
did
it's
just
more
been
like
the
a-team,
the
Kafka
admin
team
has
set
up
the
Kafka
REST
API
is
right
there
if
the
team
wants
to
do
it
easy
now,
if
it's
provided
by
confluence
already,
it's
interesting
this
to
hear
that
other
people.
F
F
No
I
told
you
see
now
that's
what
you
guys
are
going
and
while
you
getting
into
that
market
and
that's
a
it's,
definitely
a
wild
wild
west
at
the
moment
with
the
players
that
it
will
add
service
less
market.
So
it's
wide
open
for
a
lot
of
things
which
I
assume
is
kind
of.
Why
you're
doing
the
geography
as
well,
because
we
don't
really
have
interest
in?
Do
you
every
seen
the
edge,
but
we
have
more
interested
in
G
or
PC
instead
of
a
service
benefit,
yeah.
G
F
G
G
F
Yeah
and
that's
fine-
and
this
is
where
having
a
road
map
in
our
road
and
looking
at
it
and
seeing
what's
on
my
roadmap,
for
what
I
want
to
do
internally
would
be
great,
because
it's
something
that,
since
we're
driving
so
much
internally
with
it-
and
we
have
a
lot
of
api's
in
our
enterprise
being
able
to
use
that
spec
to
drive
and
help
our
customers
just
provide
that
at
specification
to
configure
things
is
something
that
I
want
to
start
doing
internally
anyway.
Right.
F
G
Not
necessary
because
in
enterprise
were
talking
about
your
having
the
opencast
peg,
create
the
whole
like
integrate
with
our
report
card
or
in
the
documentation
that
is
provided
yet
afford
or
etc.
So
there's
I
mean
if
you
want
to
write
a
note,
as
this
wagon,
like
you
know,
prevent
you
from
doing
that.
So
I,
don't
like
I,
think
right
leg
in
the
open
source
or
free
to
do
so,
but
I
don't
think
I.
Don't
you
would
quite
match
what
we're
gonna
do
in
the
Enterprise
Edition,
but
you
can
certainly
have
community
users.
G
I
know
I
can't
guarantee
that
it
will
be
published
on
the
official
hub,
for
example,
because
maybe
it
would
I
mean
we're
not
gonna
prevent
anybody
in
writing.
You
know
exactly
how
open
educating
from
no
calcium,
that's
open
source
right
I
was
I
was
we
said
that
it's
certainly
not
as
completely
tested
as
the
one
that
we
offer
as
part
of
the
enterprise
offering
you
know
like
we,
we've
looked
at
both
ends
with
comparables
and
there's
clearly
difference,
but
I
know
that
has
been
useful
to
some
to
each
users.
So
thanks.
A
Right
then,
I
will
wrap
us
up
for
day,
like
I'll
hang
out
for
a
few
more
minutes
in
case
anybody
has
any
questions,
but
thank
you
all
for
joining
us
today.
Our
next
call
is
on
August
13th,
we'll
be
looking
for
presenters
for
that.
So
if
you
have
a
topic
in
mind
or
you'd
like
to
present,
feel
free
to
drop
that
in
the
agenda
doc
and
we
will
be
in
touch
so.
Thank
you
all.