►
From YouTube: Team Pitch Office Hours
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
If
you
are
here
to
pitch
a
team
kind
of
tell
people
about
it,
then
they're
in
the
agenda.
They
put
your
name
next
to
that
item,
I'll
try
to
kind
of
ask
people
as
we
go
through
them,
but
if
there's
one
you
know
you
want
to
talk
about
it's
better.
If
it's
someone
on
the
team
and
not
just
certainly
me
just
just
reading
it
it'll,
you
know
that
excitement
will
come
through
I'm,
sure
more
so
I
think
we're
going
to
start
with
enablement.
B
Yeah,
what
I
wrote
there,
but
that's
the
very
high-level
introduction
of
the
enablement
team.
What
I
wanted
to
highlight
is
the
enablement
team.
All
the
subjects
are,
the
team
is
pretty
low
in
application
stack,
so
it's
very
low
low
level
system
details
how
to
keep
our
you
know
application
running
smoothly
and
make
it
a
scaleable
and
performant
everything
about
that.
Is
it's
a
little
bit
far
away
from
the
high
end.
You
know
top
of
the
stack
and
then
like
the
features,
the
UI.
B
A
B
C
There
I'm
Steven
Wilson
on
the
e/m
for
the
distribution
team.
We
have
two
major
projects
that
we
work
on
on
every
release,
both
Omnibus,
which
is
sort
of
our
tried
and
trued
mature
method
for
deploying
get
lab
into
VM
and
and
hardware.
Typically,
then,
we
also
have
our
container
based
solution,
which
is
all
cloud
native
using
helm.
That's
we've
got
a
lot
of
emphasis
to
bring
our
helm
deployment
up
to
the
same
level
of
maturity
as
omnibus
right
now,
omnibus
is
lovable,
but
our
home
deployment
is
viable.
C
So
we're
looking
for
folks
that
have
again
kind
of
a
combination
of
talent,
Shaun
kind
of
mentioned.
It's
mostly
lower
level
work,
but
we
span
both
kind
of
the
cloud
native
model
containers
sort
of
the
the
new
school,
and
then
we
also
have
a
lot
of
dependencies
that
we
that
we
managed
through
the
omnibus
package
as
well,
so
we're
looking
for
folks
that
are
that
are
jazzed
about
packaging
right.
However,
however,
that
and
deployment
how
whatever
tooling
that
they're
most.
A
A
E
E
We
have
three
open
headcount
in
the
next
year
and
on
top
of
that,
there's
all
the
maintainer
duties
so
anytime
we
get
database
or
a
migration
that
happens
as
part
of
the.
Mr
then
the
database
maintained
we'll
be
king
right
now,
within
the
last
couple
months,
we've
moved
from
just
ondrea's
being
the
only
database
maintained
or
now
we're
up
to
four.
So
thank
you
for
those
that
can
contribute
it,
but
definitely
you'll
be
able
to
get
your
hands
on
Ruby
on
Rails
code.
Postgres
sequel
code
contribute
to
partitioning
charting
and
investigating
other
tools
out
there.
E
B
F
Perhaps
I
can
give
some
perspective
because
I'm
pretty
excited
to
be
joining
geo
geo,
focuses
on
geo
replication,
a
couple
categories
to
your
application
disaster,
recovery,
backup
and
restore
one
of
the
reasons
why
I'm
really
excited
to
move
to.
You
is
because
there's
a
wealth
of
knowledge
and
experience
with
get
land
on
that
team.
It's
I
believe
currently,
seven
back-end
engineers
and
one
front-end
and
I
think
four
of
those
back-end
engineers
are
maintainer
that
have
been
with
the
company
for
at
least
a
couple
of
years.
F
B
A
B
B
F
A
B
H
I
was
on
mute,
yeah
and
people
also
call
me
CD
I'm,
the
manager
of
the
search
team
right
now
recently
we'll
rename
it
to
a
global
search
and
voice.
My
conclusion,
so
for
the
team,
the
team
is
focused
on
the
advanced
search
which
is
powered
by
elastic
search.
The
feature
has
been
done
for
a
while
by
other
team
members
from
other
teams
right
now.
This
is
a
new
team
with
ten
all
the
features
together
and
now
we
are
loading
it
out
on
the
comm
and
to
our
pace
customers.
H
First,
hopefully
we
can
get
in
a
boat
for
all
the
cosmic
evac,
oh
I,
know.
Well,
we
are
doing
all
this
feature
headers
on
my
new.
If
can
talk
to
I
know
the
team
Spock
song
solving
the
stability
of
the
pipeline
and
also
the
zero
downtime.
We
indexing,
reducing
the
index
size
and
also
improved
the
search
performance
there.
A
lot
of
like
scaling
and
performance
challenges
that
that
we
need
to
solve
and
also
I,
want
to
mention
that
the
search
is
a
involving
pipeline.
So
I
think
there
will
be
like
multiple
stages.
H
H
I
Hello,
everybody,
my
name
is
Sean
I'm
the
aim
for
the
static
site,
editor
team.
Our
team
is
so
new
that
between
when
I
wrote
this
down
and
and
like
five
minutes
ago,
it's
already
outdated
because
we
just
came
out
of
and
think
big
session,
and
you
know
so
we're
we're
at
the
point
where
we're
defining
our
vision.
With
that.
I
We
we're
currently
in
the
plant
maturity
stage
and
we
have
a
goal
of
meaning
to
to
minimal
by
the
end
of
12.10,
so
we're
rapidly
moving
towards
something
we
are
focused
primarily
on
improving
the
editing
experience
for
static
sites,
so
think
the
handbook
you
know,
one
of
one
of
our
objectives
is
to
be
able
to
make
it
as
easy
for
a
non-technical
person.
They
don't.
I
They
wouldn't
need
to
know
anything
about
gate,
wouldn't
need
to
know
about
setting
up
a
site
locally,
to
run
it
and
wouldn't
need
to
know
anything
about
markdown
and
still
be
able
to
contribute,
create
a
page
edit
content-
and
you
know,
publish
that.
So
you
know
we,
if
you
think
of
the
web
IDE
you
think
of
that,
as
as
more
like
a
co-editor
for
advanced
technical
users
will
be
creating
a
editing
experience
for
non-technical
users
and
we're
we
kind
of
like
trying
to
position
ourselves.
I
You
know
like
on
the
way
on
the
left,
end,
you've
kind
of
got,
got
code,
editors
and
CMAs,
and
then
you've
got
kind
of
like
these
live
side.
Editors
and
and
then
you've
got
these
site
builders
and
we
some
way
in
the
middle
and
we
busy
framing
ourselves
in
terms
of
what
exactly
our
definition
is
and
and
how
are
we
going
to
go
about
it?
So,
if
you're,
one
of
those
people
that
really
don't
like
to
be
part
of
defining
what
the
team
does
you
know,
this
isn't
a
great
opportunity
to
be
part
of
that.
I
We're
we're
looking
for
people
that
are
interested
in
great
user
experience.
You
know
and
can
have
empathy
with
non-technical
users
from
a
positions
point
of
view.
I've
got
three
fronting
positions
open,
as
well
as
a
back
in
engineering
position
and
from
a
breaking
point
of
view,
like
I've
mentioned
in
the
notes.
Here.
It's
not
a
hard
requirement,
but
some
understanding
of
JavaScript
will
be
beneficial.
I
There
will
be
a
lot
of
JavaScript
in
in
in
the
features
we
build,
and
so
it's
that
experience
pretty
good,
we'll
be
looking
to
integrate
with
lots
of
different
static
site
generators.
We're
not
looking
to
create
a
new
generator.
As
such,
we've
focused
on
the
editing,
experience
and
I've
put
a
link
to
think
big
document
where
you
can
see
some
of
our
thoughts
that
we've
just
kind
of
like
we're
putting
down.
If
you
have
any
further
questions,
feel
free
to
reach
out
to
me,
awesome.
A
G
Be
jumping
in
as
Lucas
is
not
around
he's
in
another
call
house
I'm
jumping
in
of
both
the
ecosystem
and
the
minister
ecosystem
contribute.
The
experience
is
definitely
the
team,
most
probably
the
widest
technically
impact
or
technically
work
that
they
will
be
doing
so.
This
is
currently
a
complete
new
team
or
combining
an
existing
team
with
a
new
team.
So
because
system
is
already
something
that
we
have,
the
target
is
of
the
ecosystem.
G
Team
is
really
to
build
integrations
in
other
products
for
kid
lab,
so
building
a
JIRA
integration
building
integrations
with
some
other
products,
rather
basically
I
able
to
then
access
get
lab
data.
So
this
is
a
very
diverse
technical
background,
so,
depending
on
a
product
that
we
are
implementing
and
on
the
other
hand,
we
have
the
contribute
experience,
which
is
the
current
name
for
it.
We
will
try
to
find
the
name,
perhaps
that
combines
all
that
stuff
but
contribute.
G
G
So
we
have,
we
will
have
a
couple
of
engineers
that
will
100%
focused
on
improving
the
GDK,
making
it
faster,
making
more
stable,
making
it
more
useful
in
the
sense
of
building
stuff
like
mocking
and
simulations
and
faster
connecting
for
both
all
our
internal
engineers,
but
also
all
other
roles
like
UX
designers,
product
managers,
so
that
it's
also
much
easier
for
them
to
use
the
GDK
in,
on
top
of
that,
also
for
all
our
outside
contributors
to
have
a
really
easy
path
to
infinity
at
some
point.
Hopefully,
I.
G
Won't
click
thing
that
you're,
basically
in
relative,
put
something
in
the
command
line,
and
you
have
a
couple
of
minutes
later
are
locally
running
development
kit
that
is
stable.
That
is
fast
so
that
we
can
increase
contributions
and
simply
make
all
our
lives
easier
in
that
daily
development.
That
is
one
of
the
topics
of
the
country.
Experience
team
and
the
other
one,
which
is
a
really
interesting
field,
is
the
whole
key,
flip
UI
and
front-end
foundation.
So
this
is
really
targeting
on
improving
environment
for
front-end
engineers
by
a
lot.
G
So
this
means
that
we
will
have
dedicated
engineers
who
are
working
with
their
time
totally
focused
on
keep
your
eye
on
components,
improving
the
whole
frozen
architecture.
So
this
is
has
a
really
wide
span
and
yeah
I
said
those
are
a
lot
of
topics
feel
free
to
reach
out
to
Lucas
I.
But
if
you
have
more
questions-
and
you
will
find
also
all
the
other
InfoSphere-
they
are
a
big
thing
that
I
can
promote
you
today
and
I
have
combined
all
the
other
topics.
Just
in
a
small
paragraph
is
manage.
G
The
manage
stage
is
looking
for
a
lot
of
back-end
developers
if
I'm,
correct,
9
I
believe
is
the
current
headcount
that
we
are
looking
for
and
is
a
very
wide
field.
Again,
we
have
in
the
managed
stage
that's
taking
care
of
all
the
authentication
stuff
authorization
stuff.
So
it's
always
quite
interesting
of
the
work
with
a
lot
of
standards
with
all
the
stuff
around
users
and
managing
users
and
groups.
G
Looking
at
what
we
are
trying
to
build
in
the
in
the
near
future
is
really
also
not
only
the
point
of
managing
those
users,
but
also
giving
groups
and
teams
more
of
like
a
field
very
basically
get
started
and
collaborator.
So
that's
also
part
of
that
area.
Specialist
spaces
and
important
huge
topic
importing
from
ourselves,
so
from
self
manage
to
calm
and
perhaps
also
the
other
way
around
and,
of
course,
also
our
competitors
or
that
team
has
a
real
focus
on
just
that.
G
And
then,
on
top
of
that
we
have
the
enterprise
the
most
enterprises
worth
ever.
Compliance
which
is
really
all
around
audit
and
compliance
tools
and
following
those
tasks
to
really
an
a
with
a
lot
of
huge
customers
that
have
a
lot
of
requirements
in
those
areas
to
get
them
on
board
as
soon
as
possible
and
I.
A
A
Maybe
not
so
I'll
give
just
a
quick
feel
on
it
from
what's
in
the
agenda,
so
this
is
in
the
growth
group.
The
Kalama
tree
group
is
responsible
for
collecting
information
about
get
lab,
calm
and
self
manage
instances
to
improve
our
product,
so
big
role
to
play
there
and
the
feedback
cycle
and
I'm
not
quite
sure
who
the
manager
is
on
that
team,
but
you
can
find
it
in
the
org
chart
and
reach
out
to
them
if
you're
interested
in
that
moving
on
Darby,
you
want
to
talk
about
the
verify
group.
J
Thanks
Sam
yeah
I'll,
just
kind
of
touch
on
these
quickly.
Most
of
our
growth
in
CSC
D
this
year
is
going
to
be
in
the
verify
stage.
So
this
is
the
the
CI
testing
things
like
that.
So
we've
got
two
teams
over
here:
the
CI
group
and
then
the
runner
group
CI
group
is
going
to
be
focused
on
sort
of
a
couple
things.
One
one
is
kind
of
getting
people
into
a
lab
CIA
more
easily.
J
So
one
of
those
features
we
we
just
started
working
on
is
a
jenkins
importer,
so
you're
using
Jenkins
now,
and
you
want
to
just
huge
someone
move
over
to
get
lab
I'm
going
to
make
that
that's
super
easy.
So
so
that's
that's
kind
of
one
of
the
features
and
then
the
other
other
side
of
it
is
like
doing
some
powerful
things
that
are
that
are
big
customers
are
asking
for.
J
So
child-parent
pipelines
is
a
feature
that
that
rolled
out
recently
directed
acyclic
graphs
is
another
one
and
so
will
will
be
kind
of
enhancing
those
features
and
building
more
sort
of
you
know
deeper,
tooling
there
as
well,
so
that
team
right
now
is
for
back.
In
engineers
and
there's
just
one
one
front
end
engineer
so
we're
looking
for
some
more
back-end
folks
and
then
another
front
end
person
as
well
and
then
on
the
runner
side.
That's
all
go
it's
all
going
and
that's
going
to
be
the
the
the
runner
so
get
lab
runner.
J
It's
an
open
source
product
that
is
separate
from
from
get
lab,
but
obviously
bundled,
and
we
use
it
for
everything
that
team
right
now
is
I.
Think
of
five
back
in
engineers,
we're
looking
to
add
three
more
over
there.
The
stuff
we're
adding
into
runner
is,
is
going
to
be.
We've
been
working
on
Windows
and
Mac,
shared
runners,
the
ability
for
self-managed
users
to
somehow
have
a
shared
runner
or
make
make
setting
up
runners
really
easy
for
them.
J
A
A
I'm
gonna
try
to
capture
that
in
the
agenda
too,
but
it'll
be
hard
for
me
to
talk
if
I'm
typing
so
I
think
the
answer
is,
you
know
there
is
a
sequence
in
terms
of
when
you
know
these
positions
are
intended
to
be
filled
that
particularly
in
cases
where
we're
filling
them
from
external
candidates.
However,
though,
in
the
case
of
someone
transferring
you
know
that
is
budget
neutral,
so
there's
probably
some
flexibility
there
so
I
would
you
know
consider
that
yeah
it
would
be.