►
Description
Discussion Topics
- Welcome
- Where to find the community
- Google Group for announcements and calendar management
- Introduce yourself to us on GitHub
- Slack Channel for ongoing conversations
- Greetings from Maintainers and Intro to TCE
- Meeting time move imminent
- Tanzu Community Edition Repository Tour
- Relationship to Tanzu Framework
- Thanks and Sign Off
A
Hello,
everyone
welcome
to
our
first
community
meeting
our
first
public
community
meeting
for
tons
of
community
edition.
I'm
sure
all
of
you
are
aware.
Tanza
community
edition
launched
a
couple
of
days
ago
on
october
4th
and
we're
excited
to
bring
to
you
these
weekly
meetings
that
we
will
have
how
it's
going
to
work
is
that
we
have
meetings
on
currently
on
the
first
and
third
wednesdays,
and
then
we
have
our
office
hours
on
the
second
and
fourth
wednesdays.
A
And
what
will
happen
is
for
the
community
meetings.
We
have
more
of
an
agenda
planned
out
for
you
more
of
us,
giving
you
updates
on
what's
happening
with
the
project
and
with
development,
and
also
any
announcement
that
needs
to
happen.
Any
announcements
that
need
to
happen
and
then
on
the
office
hours
it'll
be
a
much
more
open
forum
for
you
to
bring
your
questions
or
issues
or
pull
requests
that
you'd
like
to
have
looked
at
in
a
more
synchronous
fashion.
A
So
for
those
of
you
that
are
here,
please
feel
free
to
add
your
name
and
your
company
to
this
document
and
you'll
see
the
agenda
that
we
have
here
for
today.
So
we're
starting
off
with
the
welcome,
welcome
and
then
we're
going
to
talk
a
bit
about
how
you
can
find
us
online
like
where
the
community
lives.
A
So
we've
got
the
google
group.
That's
here
for
our
announcements
and
our
calendar
management.
I
have
recently
been
informed
that
the
calendar
management
piece
is
not
working
very
well.
So
we're
going
to
be
troubleshooting
that
and
getting
those
updates
out
to
you
so
that
you
know
we'll
have
more
folks
show
up
because
they
know
the
meeting
is
happening
at
this
time.
And
then,
if
you
haven't
already,
we
have
a
discussion
thread
already
on
on
github.
A
So
if
you
want
to
introduce
yourself
in
this
introduction
thread
so
that
we
can
get
to
know
you
a
little
bit
better
and
what
you're
looking
for
the
intent
is
that
this
community
is
for
you
that
we're
speaking
to
your
needs
and
making
sure
that
you
feel
as
much
a
part
of
it
as
everyone
else
and
to
that
end,
we'd
love
to
get
to
know
you.
So
please
drop
a
little
intro
in
that
thread
for
us,
and
then
we
have
the
slack
channel
for
ongoing
conversations.
A
B
Yeah
sure
am
I
just
introduce
introducing
myself.
Nigel
are
also
introducing
what
tonzu
community
edition
is
yeah.
Let's
do
both
okay,
great,
hey
everybody.
My
name
is
josh.
I
am
the
one
of
the
maintainers
and
kind
of
technical
leads.
If
you
will
on
tons
of
communication,
I
work
for
vmware.
I've
been
doing
kubernetes
stuff
for
a
really
long
time.
I
worked
at
a
company
called
coreos
for
a
couple
years.
B
Once
we
get
those
clusters
instantiated
to
bring
higher
level
functionality
on
top
of
it,
so
this
is
functionality
like
certificate,
provisioning
or
log
forwarding
and
so
on,
and
you
know
the
whole
thing
that
we're
really
excited
about
with.
I
think
tce
is
this
idea
that,
with
a
with
an
ecosystem
and
a
community
of
users,
we
can
grow
these
packages
and
higher
order
functionality
on
top
of
our
clusters,
to
provide,
like
just
super
super,
robust
ways
to
to
spin
up
clusters
at
scale.
So
thanks
so
much
for
joining
us
and
again,
I'm
josh
thanks.
C
D
E
I
could
jump
in
in
the
meantime:
hey
everyone,
I'm
sean
mcginnis.
I
also
work
for
vmware.
I've
been
involved
in
storage
and
other
infrastructure
software
for
a
very
long
time,
part
of
the
tce
team
here
and
just
ready
to
to
help
get
anyone
connected
or
or
look
at
resources
or
find
the
right
information
you
need
to
use
tce
so
feel
free
to
ping
me
on
slack
or
let
me
know
if
there's
anything
I
can
do
to
help.
G
I'll
go
I'm
nick
c
miller.
I
also
joined
vmware
through
the
pivotal
acquisition
and,
after
my
first
experience
of
deploying
an
application
kubernetes,
I
just
wanted
to
get
more
involved
and
I
thought
that
joining
this
team
would
be
a
great
way
to
do
it.
So
here
I
am,
and
I've
been
focusing
on
packaging.
H
Anyone
else
yep,
I
guess
I'll
go.
My
name
is
david
von,
then
yeah
I've
been
primarily
my
focus
has
been
kind
of
like
not
being
focused.
It's
all
over
the
place.
I've
been
doing
some
work
with
like
john
and
stand-alone
clusters,
some
of
the
release
stuff
with
automation
and
stuff
like
that
so
yeah,
you
know
super
happy
to
be
part
of
the
community
and
yeah.
Let's
looking
forward
to
making
you
know
the
project,
even
better.
A
D
I
Maybe
I
will
go
next,
so
I'm
part
of
ibm-
and
I
have
wrote,
ibm
slash
kindle
not
sure
how
many
of
you
know,
but
one
of
the
unit
in
ibm
is,
is
spinning
out
as
a
new
company
and
becoming
kindle
so
I'm
still
part
of
one
of
it
and
from
brand
new
perspective,
actually
I'm
working
since
year
and
worked
on
different
tangie
kubernetes
grid
versions.
My
role
here
is
basically
bringing
out
the
tangie
portfolio
capability
within
ibm
and
providing
services
to
our
client.
A
Awesome,
thank
you
dinesh.
We
have
enough
time,
but
we're
we
we
are
looking
for.
We
were
introducing
the
maintainers,
it's
all
good.
If
audience,
members
also
would
like
to
introduce
themselves.
I
think
all
of
the
maintainers
have
gone
there.
A
couple
of
other
people
who
are
very
important
to
the
project.
Don't
know
if
they
want
to
introduce
themselves
amanda
chase.
J
J
A
K
Sure,
hey
folks,
clint
kittson
I've
been
at
vmware
for
the
last
four
to
five
years
and
we've
been
in
the
cloud
native
ecosystem
from
a
few
years
prior
to
that
focusing
heavily
on
on
storage.
But
behind
the
scenes
I've
been
helping
lead,
our
our
teams
have
been
building
all
these
great
kubernetes
integrations
and
helping
support
the
kubernetes
contributors.
A
Awesome,
thank
you
clint
and
we'll
wait
a
beat
now,
if
there's
anyone
else
that
would
like
to
introduce
themselves
we'd
love
to
meet
you
and
also,
if
you
don't
want
to
talk,
that's
totally
fine.
Please
feel
free
to
introduce
yourselves
as
well
on
that
discussion
post
in
the
github,
the
github
discussions,
the
intro
posts
on
github
discussions,
words.
L
I'm
amanda
I've
been
leading
the
engineering
and
engagement
efforts
here
for
tonsil
community
edition.
I
am
so
excited
that
we
are
now
public
after
about
a
year
and
a
half
of
working
on
this,
so
I
am
stoked.
I
am
also
a
little
tired,
and
so
everybody
here,
I'm
so
excited
to
have
a
community
on
this
and
to
work
out
on
the
open
this.
L
A
A
A
B
A
B
As
well
for
folks
to
know,
you
know
like
where
you
keep
the
road
maps
where
all
the
information
is
can
do,
can
do
and
I'm
being
slightly
sarcastic,
we
we're
not
terribly
unorganized,
but
we
can.
We
could
use
a
little
bit
of
improvement,
so
I'm
sure
most
people
on
this
call
have
already
been
to
the
the
repository
it's
on
github.
Someone
can
put
the
link
in
vmware
tonzu
community
edition
and
inside
of
the
repository
one
of
the
things
that
you'll
find
probably
helpful.
B
If
you're
doing
any
contributions
is,
if
you
go
down
to
the
bottom
of
our
readme,
we
have
a
repository
layout
section
that
talks
about
what
the
folders
are
and
what
is
contained
inside
of
them,
so
tons
of
community
edition
as
a
repo
kind
of
has
two
well
actually.
I
guess
it
has
a
couple,
but
two
main
things
from
a
code
perspective.
B
B
So
what
will
be
a
little
bit
confusing
about
this
tour
and
I'll
try
to
keep
it
succinct
is
that
when
it
comes
to
tonzu
plugins,
some
of
these
come
from
our
our
foundation.
If
you
will
tanzu
framework,
which
is
a
slightly
different
repo,
maybe
I
can
talk
a
bit
about
that
if
we
have
time,
but
some
of
the
plugins
are
unique
to
tonzu
community
edition.
B
So
if
you
haven't
seen
this
what's
interesting
about
our
architecture,
is
it
feels
like
you
have
a
singular
cli
here,
but
in
actuality
these
are
independent,
binaries
that
are
providing
functionality
and
it's
all
piping
through
this,
this
tanzu
command.
So
with
that
context
in
place,
let's
go
back
to
the
repo
real
quick
here.
B
Somehow
I
lost
it.
So
with
that
context
in
place
the
the
plug-ins
that
you
I
was
just
describing
with
the
cli
you're
going
to
find
all
of
these
inside
of
cli
cmd
and
then
inside
of
plug-in.
So
these
are
the
three
tons
cli
plugins
that
are
unique
to
tonzu
community
edition,
and
the
one
thing
for
contributors
to
know
about
is
that
for
better
or
for
worse,
we've
decided
to
not.
B
We've
decided
that
we
wanted
different,
go
module
dependencies
and
to
be
able
to
keep
these
plugins
and
their
source
code
really
clean
and
separate.
So
these
plugins
are
root,
go
projects
in
and
of
themselves.
What
I
mean
by
that
is,
if
you
enter
the
standalone
cluster
directory
you're
going
to
find
it
has
its
own
dedicated,
go
mod,
go
sum
and
so
on.
B
B
This
folder,
if
I
was
working
on
standalone
cluster,
would
be
my
root
directory
that
I'd
start
programming
against,
if
I
was
using
anything
from
vim
to
vs
code
to
intellij
all
right,
so
those
are
our
plugins,
our
binaries,
that
give
us
functionality.
The
second
piece
are
the
packages
that
we
deploy
on
top
of
clusters.
In
fact,
if
I
can
find
the
command
real
quick
package
list
see
if
we
can
get
them,
I
don't
even
know
if
I
have
a
cluster
running,
but
maybe
I
do
okay
cool.
B
So
this
is
coming
off
of
a
cluster
when
you
deploy
tons
of
community
edition
clusters
and
installer
repo
you'll
see
a
bunch
of
functionality
that
you
can
deploy
now
these
packages
are
all
contained,
or,
I
should
say,
the
package
source
configuration
is
all
contained
in
add-ons
packages
and
you'll
find
the
package
source
configuration
for
every
single
one
of
our
packages.
So
let's
say
that
you're
deploying
contour
and
you're,
like
I
wonder
how
the
tce
group
and
maintainers
are
working
on
the
contour
package
and
configuring
it
you
can
go
into
contour.
B
You
can
choose
the
version
that
you're
looking
at
and
then
inside
of
the
bundle
directory.
You'll
see
some
information
about
the
the
configuration
for
it.
So
we
have
these
things
called
overlays
we
have
the
upstream
manifests.
We
have
values
that
we
apply.
This
is
all
using
a
bunch
of
tools
from
a
project
called
carvel
or
karvel,
and
yeah
you'll
find
all
the
the
configuration
bundles
inside
of
that
add-ons
packages
directory
all
right.
So,
aside
from
that,
we've
got
a
couple.
B
Other
directories
that
I
will
mention
docs
is
one
of
our
probably
most
important
directories
inside
of
docs
and
site.
If
you're
familiar
with
hugo,
this
is
where
the
entire
hugo
website
lives.
So
if
I
were
to
go
into
my
local
machine
and
do
tce
if
I
went
into
docs
hugo
or
sorry
stocks
site
at
this
root
directory,
you
can
make
modifications
to
the
website,
and
you
can
also
run
hugo
server
from
here,
and
this
will
actually
pop
up.
B
You
can
make
those
changes
and,
like
I
said
you
can
go
to
our
docs
site
folder
and
run
hugo
server
and
get
a
local
preview
of
all
these
different
pieces.
So
hopefully
that
will
be
a
little
bit
helpful
and
then
what
are
the
other
directories?
I
should
just
call
out
real,
quick
hack
and
test
hack.
I
don't
even
want
to
describe
it
because,
as
you
can
probably
imagine
from
the
folder
name,
it
just
has
a
lot
of
random
stuff
in
it,
but
our
test
directory
is
what
our
awesome
release.
B
Engineering
team
and
other
teams
use
to
set
up
automation
for
end-to-end
testing.
You
know
lower
level
testing,
all
that
good
stuff.
So
there's
a
lot
of
our
test,
automation
and
things
in
the
test,
repo
and
then
maybe
the
last
thing
I'll
say,
and
then
nigel.
Let
me
know
if
there's
anything
else,
I
should
cover.
If
you
haven't
already
gone
to
the
issues
page
when
you're
ready
to
file
an
issue,
we
do
have
some
templates.
B
We
super
super
appreciate
usage
of
these
templates
because
it
automatically
labels
stuff
and
lets
us
triage
and
filter
as
we
need
to
and
if
you're
at
all
interested
in
how
we
go
about
triaging
issues
like
you
can
see
a
bunch
that
need
triage
right
here.
We've
got
a
pinned
issue
up
here
that
describes
what
our
labels
mean,
how
we
think
about
and
triage
and
prioritize
things.
This
is
more
of
like
an
internal
detail,
but
you're
super
welcome
to
read
about
it.
B
If
it
interests
you
and
then
last
but
not
least,
you'll
also
find
our
engineering
roadmap
inside
of
pinned
issues
here
and
the
engineering
roadmap
is
basically
a
collection
for
each
one
of
our
milestones
of
what
we're
working
on.
So
when
you
all
come
to
community
meetings
and
you're
like,
I
really
need
this
one
feature
really
bad
and
we
talk
about
it.
If
we
put
it
in
a
milestone,
it's
going
to
get
allocated
into
one
of
our
releases,
which
means
we're
going
to
try
to
include
it.
B
So
if
you're
interested,
for
example,
you
all
have
used
v090,
whether
you
knew
it
or
not,
and
if
you're
interested
for
our
next
release,
you
can
get
details
on
when
we're
targeting
that
release
date.
Assuming
all
things
go
well
and
you
can
get
an
idea
for
what
new
features
bugs
enhancements
to
existing
features
and
documentation
changes
we
have
slated
for
v010
and,
like
all
open
source
projects,
these
are
always
a
moving
target,
but
this
will
usually
give
you
a
really
good,
concise
way
to
see
hey
in
the
next
release.
A
M
Yeah,
I
just
want
to
add
one
thing,
which
is
that
we
normally
maintain
those
as
zero
to
three
months
three
to
six
months
and
future
you'll
notice.
The
future
is
missing
and
that's
because
over
you
know,
some
community
meetings
in
the
near
future,
like
probably
about
a
month
out
we're
going
to
start
discussing
those
high-level
things
and
talk
about
prioritizing
those.
So
the
future
bucket
is
largely
up
to
you
as
well
as
us.
B
Sounds
great
thanks,
roger
and
on
the
note
of
tonsi
framework,
I
will
give
just
like
a
quick
two
minute
overview,
so
you
know
what?
Let's,
let's
just
look
at
the
cli
again,
because
I
think
that
that
kind
of
tells
the
story
really
well
there's
a
lot
of
really
core
functionality.
That
is
just
you
know
the
the
nucleus,
if
you
will
of
tonzu
community
edition,
and
that
is
largely
found
in
something
called
tonzu
framework,
so
architecturally
without
getting
too
much
into
it.
Tanzu
framework
is
an
enabler
of
of
us
to
build
a
distribution.
B
B
You'll
also
find
our
api
definitions,
general
purpose
machinery
and
just
things
that
are
kind
of
again
at
the
core
of
everything
that
tanzu
builds
out
so
for
not
just
community
users
but
paid
users,
who
I
already
heard
there's
some
in
this
chat
or
in
the
session
that
are,
you
know,
tkg
users
tanzu
framework
builds
our
product.
It
also
builds
our
community
edition
right,
it's
kind
of
like
a
layered
cake.
So
I
wouldn't
say
I
you
know
my
caution.
Is
you
don't
have
to
worry
too
much
about
like?
B
Oh,
do
I
need
to
file
an
issue
in
tanzu
framework
or
tanzu
community
edition
we're
here
to
help
you
out.
If
you
hit
issues
in
tanzu
community
edition
you're,
more
than
welcome
to
file
an
issue
we'll
make
sure
it
gets
to
the
right
place,
but
if
you're
a
tinkerer-
and
you
want
to
kind
of
check
out
some
of
the
things
that
tonsu
framework
can
offer
you,
there
is
a
separate
repo.
Someone
can
put
the
link
to
this
in
chat
as
well
tanzu
framework,
and
this
is
gonna-
have
a
lot
of
the
tooling
here's.
B
Actually
a
great
description.
Api
machinery,
cli
machinery
and
some
of
the
package
stuff
that
we
use
to
generate
and
create
tanzu
community
edition
so
again,
framework
tce
sits
on
top
of
framework
and
then
that's
essentially
what
you're,
what
you're
downloading
under
the
under
the
guise,
if
you
will
or
banner
of
of
tanzu
community
edition,
hope
that
helps.
A
Give
a
little
bit
of
context.
It
definitely
does.
We
definitely
appreciate
you
going
over
that
with
us.
Thank
you,
josh
and
thank
you.
Everyone
for
coming
we're
going
to
have
another
one
of
these
meetings
next
week,
we'll
see
about
the
time
just
because
we
know
that
kubecon
is
happening
and
also
we
have
overlap
with
cappy,
so
stay
tuned.
We'll
get
you
all
the
updates
that
you
need.
Thank
you
so
much
for
being
here
and
we'll
see
you
next
time
take
care.
Y'all,
bye,.