►
From YouTube: Kubernetes SIG Apps 20170123
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
And
so
this
is
sig
apps
for
Monday
january
twenty,
three
twenty
seventeen
and
remind
everyone.
This
is
recorded
and
will
be
posted
online.
Today
we
have
jason
here
to
help
us
worth
a
retrospective,
and
this
is
something
I
appreciate
having
somebody
come
in
from
the
outside
to
help
us
with
it,
because
that
means
it
was
Michelle
and
myself
participate,
get
feedback
and
be
able
to
hear
without
being
a
moderator
and
doing
that,
and
so
it's
great
to
be
part
of
it
in
a
different
way
by
having
that
outside
portion.
So
Jason
are
you
there.
A
B
And
thanks
for
after
the
handoff,
and
also
met
Michelle
for
inviting
me
to
help
do
this.
This
is
something
that
we
see
a
lot
of
success
thus
far
with
the
last
three
communities
releases
and
I'm,
pretty
proud
to
say,
we've
seen
a
lot
of
incremental
improvement
between
releases.
Those
people
have
taken
note
of
the
things
in
the
retrospectives
that
could
be
addressed
moving
forward.
So
for
those
who
haven't
really
done
in
retrospective,
which
probably
everybody
here
has
but
I'll
just
give
it
grinds
down.
B
Somebody
might
know
me
I'm
sorry,
so
I
just
said
just
to
go
over
this
quickly.
The
the
attendance
of
retrospective
is
to
identify
things
that
maybe
didn't
go
as
well,
some
things
that
went
well
and
then,
most
importantly,
one
of
the
things
that
we
learned
through
this
last
release
cycle
that
we
can
apply
moving
forward.
That
will
make
the
next
one
better
trust
that
a
lot
of
people
fall
into
with
retrospectives
is
that
it
turns
into
a
argument
or
everybody's
complaining
that
sort
of
thing
to
definitely
go
anywhere.
B
So
my
requests
from
people
in
bikini
is
to
simply
look
at
things
that
as
positive
light
as
possible
and
feel
like
if
you
weren't
happy
how
something,
when
let's
focus
on
how
to
change
it
and
that'll,
give
us
another
data
point
as
we
move
to
the
next
release,
to
make
it
better.
So
I
really
invite
everybody
in
the
room
to
be
as
positive
as
possible
and
disrespectful
and
to
go
into
the
document
that
is
linked
in
the
chat
channel.
B
To
add
your
items
that
you
feel
like
went
wrong,
didn't
go
up
so
in
that
regard,
one
request
is,
if
you
do
put
something
that
didn't
go
well,
I,
if
you
could
put
your
initials
at
the
end
of
that
and
then
claim
it
as
we
go
through
the
list.
That
would
be
great
because
that
way,
I
don't
have
to
speak
for
you.
B
You
can
speak
to
your
point
and-
and
we
can
have
a
more
direct
conversation
about
it,
saying
with
the
help
us
so
what
I'll
do
is
we
have
some
time
boxes
there
we're
already
at
the
time
box
for
the
interim
working
agreements.
So
let's
move
forward
to
what
went
well
and
I
would
love
for
either
people
to
put
things
in
the
document
directly
or
two-
maybe
fit
them
in
the
channel
or
in
the
video,
and
we
can
maybe
note
those
in
the
document
ourselves.
B
B
And
to
be
expand
on
that
just
to
touch
what
what
were
the
qualities
that
you
think
helps
make
the
demos
really
good.
What
was
what
was
specifically
about
them
with
a
particularly
useful
or
were
they
things
that
needed
to
community
hadn't
seen
before
or
what
can
you
extend
on
this?
The
Dutch
I
think.
C
I
just
got
to
learn
a
lot
from
the
people
who
are
creating
solicitor
tools
or
working
on
particular
features
and
I
really
enjoyed
that.
It
was
just
a
short
as
like
10
minutes
or
15
minutes,
and
it
just
was
a
nice
little
digestible
piece
of
information
and
as
always
nice
to
learn
something
new
or
how
people
are
using
particular
tools
or
two
ronnies
features.
B
C
Think
this
was
method,
risk
comment
or
Adams
comment,
but
I'll
say
to
that,
and
he
saw
lots
of
contribution
is
I,
think
Tom,
it's
a
hundred
contributors
and
home
addresses,
and
it
was
just
nice
to
get
a
lot
of
community
input
and
it
wasn't
like
peers,
were
sitting
there
for
a
long
amount
of
time.
Closing.
C
B
I've
got
20
people
on
it.
A
lot
of
silence
that
I'm
sure
everybody
had
wants
to
get
into
be
as
the
improvements
as
much
as
I
do,
but
I
definitely
would
love
to
know.
If
there's
any
more
shout
out,
were
there
any
key
players
and
the
project
this
time
around
that
stepped-up
anybody
want
to
recognize
anyone
else
that.
B
Okay,
so
pasting
the
retrospective
doc
in
chat,
one
more
time
and
because
exam
when
you
join,
you
don't
get
to
see
the
prior
chat
so
for
those
who
just
joined.
If
you
could
look
at
this
document
that
I
just
pasted
the
link
to
in
chat
I'm
going
to
shelve
it
as
well,
there
right
now
we're
at
the
one-way,
well
affection,
and
if
you
want
to
add
any
items
there,
we
can
definitely
discuss
them.
I.
E
B
Alright,
so
pretty
much
cricket
I,
sometimes
the
first
retro
is
a
little
awkward.
So
if
we
move
forward
anybody
wants
to
add
anything
in
the
wetland
wall
section,
we
can
definitely
do
that
up
retro
actively.
So
without
further
ado,
let's
get
into
the
what
might
have
gone
better
again.
We
want
to
focus
on
things
and
in
this
positive
light
as
possible.
We
know
there
are
a
lot
of
frustrations
this
release
cycle.
B
F
Sure
I'm
the
one
who
added
that
in
okay,
something
we
had
talked
about
on
the
core
team.
So
even
if
it
wasn't
me
who
added
it,
I
feel
I
taken
articulated
pretty
well
agreed.
We
just
got
started
on
our
1.5
migration,
a
little
bit
later
than
we
should
have.
We
were
not
watching
carefully
when
it
went
from
alpha
to
beta,
and
we
really
probably
should
have
started
on
it
a
little
earlier
in
alpha,
but
because
we
were
so
focused
on
getting
some
of
the
features
for
2.1
finished.
E
F
Main
takeaway
is
that
we
want
to
bump
up.
We
want
to
say
more
aware
of
wings
for
Nettie's
hits
its
alpha
cycle
and
we
feel
like
alpha
is
generally
the
stability
marker,
where
we
should
start
testing
the
library,
migrations
and
things
like
that
there
anything
else
autumn
is
here
on
I
know,
Adam
said
the
internet
trouble
all
morning,
because
it's
raining
in
California
boy.
F
B
Great,
so
there's
the
thing
here
about
the
surprise
by
the
image
full
quality
breaking
which
broke
most
charts.
Anybody
want
to
speak
to
that.
G
G
But
if
you
did
upgrade
from
1.4
2
1.5
with
the
exact
same
manifest
and
it
did
not
set
an
image
full
policy
because
in
1.4
it
was
assumed,
I
think
it
was,
if
not
present,
by
default,
and
so,
if
you
upgraded-
and
you
did
not
set
an
image
full
policy
by
default
than
a
broke
for
you,
it
was
just
a
backwards.
Incompatible
change
on
the
API
side
of
things
that
caused
a
little
bit
of
headache
on
the
Cooper
Nettie's,
charts
side
of
things.
G
B
G
Personally,
I'm
like
I'm,
not
quite
sure
on
the
cooperage,
defer
development
side
of
things
on
the
core.
On
the
communication
side,
it
was
just
a
surprising
bug
that
caught
us
all
off
and
I
think
that
was
more
of
the
fact
of
just
from
the
chart
side
of
things.
It
was
less
so
testing
the
migration
from
1.4
2
1.5,
and
it
was
just
testing
right.
11.5
was
released
and
testing
the
charts
against
those,
I'm
not
sure
if
it
was
an
intentional
bug
or
not.
So
I'm
not
sure
on
the
communication
side
of
things.
Ok,.
B
F
If
I
can
add
to
that
for
a
moment
yeah,
I
think
that
whether
it
was
a
bob
year
feature
of
Coober
Nettie's
isn't
quite
the
most
important
issue.
In
my
mind,
the
most
important
issue
was
that,
in
spite
of
the
fact
that
we
well
basically
that
we
had
dozens
and
dozens
of
charts
that
were
impacted
out
of
the
gate-
and
we
didn't
know
until
the
release
went
by
and
Michelle,
do
you
want
to
talk
about
what
what
has
been
discussed
for,
avoiding
that
problem
or
because
I'm,
a
little
behind
on
that.
C
Testing
all
charts
on
particular
versions
of
raids
earlier
see
you
and
I
talked
about
it.
D
I
think
we
envisioned
to
obviously
charge
people
has
its
own
CI
TV
and
by
the
end
of
this
quarter,
1.6
we
hope
to
have
a
mokuba
nettings
repo
see
I.
That
runs
relatively
recent
versions
of
charts
against
head
to
burnet
ease,
and
so
we
would
have
detected
that
if
we
had
that.
So
that's
that's
our
plan.
B
D
B
In
terms
of
other
things
that
might
have
taken
this
as
well,
for
example,
the
clutter
up
in
terms
of
operators
who
are
using
charts
for
all
their
deployments.
That
would
have
been
a
serious
issue
for
them,
so
maybe
some
some
collaboration
that
can
be
done
as
well.
There
so
just
kind
of
keep
that
in
mind.
B
Let's
see
what
else
could
have
gone
better,
more
discussion
around
proposals
and
in
which,
I
believe
is
Michelle.
Nothing.
C
So
me,
this
is
not
necessarily
a
negative
comment.
It's
just
a
thing
that
happened,
so
let
me
give
a
little
context
when
I
first
started
this
fake
one
of
the
things
that
we
had
discussed,
arm
or
plans
on
doing
was
discussing
proposals
and
Cooper
Nettie's.
That
related
and
you'll
see
that
there
are
several
proposals
that
get
tagged
with
the
specific
apps
tag,
and
so
we
don't.
We
haven't
necessarily
had
those
kind
of
long,
like
lengthy,
in-depth
discussions
about
proposals
in
in
this
big
I.
D
I'll
share
one
thought:
I
also
worked
in
the
sig
off
and
a
style.
There
was
that
if
we
could
resolve
it
on
the
issue
like
and
it
was
converging,
then
it
didn't
ever
get
discussed
in
the
video
chat
and
then
it
could
got
blocked
or
people
after
a
week
or
so,
and
people
felt
like
face
to
face
was
going
to
be
faster.
Then
someone
say:
let's
do
it
in
the
fig
and
it
was
usually
enough
time
on
the
sig
calendar.
There's
always
room
to
have
that
type
of
a
talk
discussion.
D
D
Maybe
just
tell
people
like
if
you
feel
like
this,
you
would
like
to
have
a
discussion
on
any
issue
in
Coober
Nettie's
that
affects
the
gaps,
feel
free
to
put
something
on
the
agenda,
and
people
should
defer
decisions.
If
someone
reasonably
wants
to
talk
about
it
here
and
that's
a
very
big
action
item,
but
what
people
know
it's
an
option
so.
B
C
B
Great
okay,
that
is
I,
believe
the
last
of
the.
What
could
have
gone
better
that
are
in
the
document?
Is
there
anybody
it
wants
to
raise
something
at
hakama,
collectorate,
uh-huh.
E
Is
it
possible
to
provide
another
hook
just
like
image
containers
just
after
reports
are
being
started,
not
for
coordination?
So
what
is
the
best
place
for
me
to
put
for
that
proposal?
Automotive
quiz,
because
I
see
a
plenty
of
issues
being
created
in
the
actual
coconut.
This
project,
so
if
I
really
issue
it
could
easily
get
lost.
D
Aware
of
Julie's
proposal-
and
I
am
very
backlogged-
and
it
has
not
come
up
to
the
top
of
my
cue
yes
in
terms
of
the
review,
if
there's
someone
outside
of
its
the
nature
of
the
review,
is
I'm
using
this
for
myself,
tell
me
if
I'm,
using
best
practices,
that
kind
of
puts
it
down
in
my
queue,
if
there's
other
people
saying
hey
I,
wish
this
thing
with
someone
else
from
a
different
org
said:
please
check
this
in
I.
Think
I
want
this
Redis,
then
we
can
expedite
and
then
it'd
be
good
to
understand.
D
Is
there
a
Redis
chart
already
and
why
is
it
going
to
contrib
or
how
does
it
differ
from?
What's
there?
That's
not
even
answering
in
the
hole
I
apologize
to
the
issue
of
if
you
want
to
feature
and
you're
not
getting
attention,
I
think
that
would
be
a
good
case
to
put
something
on
the
agenda
and
just
saying-
and
you
want
five
minutes
to
make
my
case
for
why
this
is
useful,
we'll
talk
about
it,
face
to
face
and
make
a
decision
in
a
future
sing.
Ups.
D
E
Yeah
well
in
continuation
to
that
I've
gotta
go
to
another
question.
So
what's
this
concept
directly
or
what
sort
of
things
looking
to
consider
that
clear?
What's
what
are
things
should
go
to
the
chart
because
this
I
think
it's
not
a
charging.
Just
a
simple
staple
said
implementation,
so
any
people
who
would
want
to
have
a
registered
table
set
should
be
able
to
see.
We
do
here
creative
and
nvm
sizes
I.
Don't
they
don't
want
to
the
charge?
Then
this
should
that
be
a
better
place
for
me
to
raise
the
PR
0.
D
E
D
D
G
Mean
if
it's
like
a
direct
modification
of
the
Redis
image
itself
or
if
it's
direct
location
of
what
happens
the
behavior
of
a
container,
then
that's
obviously
like
that's,
probably
just
a
fork
of
the
image
itself,
depending
on
the
use
case
of
it.
But
if
it's
like
a
modification
of
how
the
manifests
are
deployed
and
there's
probably
something
that
can
be
done
inside
of
the
chart
itself,
it.
G
Then
that's
probably
a
fork
honestly
I
wouldn't
be
too
aware
of
how
that
would
be
like
reflected
unless
we
saw
the
actual
code
itself.
So.
A
So
maybe
a
suggestion
you
know
this
is
getting
into
kind
of
best
practices
and
where
they
talking
about
how
we
should
do
things,
and
so
one
of
the
things
that
we
could
probably
do
better
in
the
future
is
actually
document
that
stuff
and
have
one
place.
We
say
come
over
here
and
if
there's
a
gap
you
can
do
a
pull
request.
We
know
whatever
the
process
is
to
fill
that
in,
but
at
least
we
have
a
place
that
that
captures
that
yeah.
G
B
Thank
you
so
much
okay
moving
along
here,
we
had
a
few
things,
come
up
in
chat,
so
there's
I
want
to
quickly
recognize
that
there
are
a
couple
of
extra.
What
went
well
that
will
at
it
and
attendant
so
the
group
went
way
up,
which
is
fantastic.
I
have
to
say
that
is
having
seen
a
cross
cut
of
several
things,
that
this
is
one
of
the
great
active
shakes
and
seems
to
be
a
huge
positive
impact,
so
congrats
to
you
all
on
that.
B
F
No
and
I
can
I
can
explain
that
last
when
I
guess
really
quickly
that
when
we
started
off
suggest
felt
like
a
lot
of
demos
from
a
lot
of
different
people,
which
is
fabulous,
I
love,
seeing
the
demos,
but
then
what
has
happened
particularly
over
this
last
little
time
window
is
I've,
noticed
a
lot
of
cross
project
collaboration
and
so
demos
have
turned
into
cooperation
when
she
turned
into
collaboration,
which
is
really
cool,
I.
Think
that's
my
understanding.
F
B
I've
seen
that
as
well
amazing,
this
is
a
community
goes
to
could
really
be
as
a
bellwether
further
states
in
terms
of
how
to
tell
you
that
process
so
going
back
to
the
what
could
have
gone
better
there's
a
couple
items
became
from
chat
so
concern
how
we
process
DSF,
based
in
1.5
time
frame.
It
should
land
what
we
did
not
well,
but
it's
starting
prevent
416
and
that
was
genuine
I.
Believe
you
want
to
speak
to
that
and
actually
as
an
exciting
as
well.
Oh.
B
B
Okay,
so
let's
get
into
what
we
can
do
differently
to
1.6
and
beyond,
so
regarding
helm,
begin
helpless,
1.6
build
as
soon
as
1.6
beta
1
is
released.
F
H
B
So
this
so
specifically
on
begin
the
1.6
belts
as
soon
as
one
place,
video's
release
just
ensuring
that
if
we
didn't
do
it
last
time-
and
we
want
to
do
it
next
time-
who
is
who's
actually
taking
responsibility
for
that,
that
actually
happens
and
more
kind
of
mechanics
around
that
okay.
G
Specifically
for
the
Cooper
Nettie's
for
the
community's
helm,
documentation
update
is
a
file.
An
issue
and
I
can
comment
on
that
and
I
can
just
tag
that
to
my
triage
as
you
personally
for
the
other
ones,
I
think
just
filing
up
a
ticket
and
then
trying
to
ping.
The
person
may
be
so
easy
ously
to
make
them
accountable.
G
B
F
I'm
keeper
of
the
helm
read
map
is
probably
my
responsibility
to
make
sure,
and
probably
the
best
metric
to
make
sure
on.
This
is
that
we
are
following
the
Cooper
Nettie's
release
estimated
time
estimated
release
time
date
on
the
Cooper
Nettie's,
where
I
mean
on
the
Helmer
that
law
all
I
really
mean
to
say,
is
that
we
have
a
relief
plan.
For
the
same
time,
the
crew
brunetti
1.6
is
planned.
Ok,
that
keeps
its
my
mind
for
us
and.
B
So,
in
terms
of
the
things
that
need
to
be
done
on
the
city
outside
of
the
home
side,
are
you
going
to
be
responsible
for
delegating
those
out
and
kind
of
making
sure
that
we're
following
the
road
map
properly
or
is
there
somebody
else
that
you
need
help
with
to
ensure
that
stuff
for
how
we
keep
accountability?
There.
F
F
It
would
be
nice
to
have
someone
from
outside
of
helm.
Keep
us
accountable
for
this
if
anybody
feels
like
jumping
in
and
taking
so
how
did
responsibility?
I'd
appreciate
it,
because
I
do
think
that
part
of
the
reason
we
skipped
out
on
at
last
time
was
because
we
were
just
not
not
keeping
close
enough
tabs
on
what
was
happening
upstream,
to
always
be
paying
attention.
G
B
B
B
B
B
G
From
my
own
personal
point
of
view,
I'm
getting
a
little
bit
confused
on
the
target
of
cig
apps
itself,
because
when
I
originally
came
to
say
gasps
I
believed
it
was
for
specifically
talking
about
applications
built
around
Cooper,
Nettie's
and
those
kind
of
things,
but
I'm
also
starting
to
see
a
little
bit
more
towards.
G
It
seems
to
be
muddling
up
a
little
bit
in
the
sense
of
it's
also
being
Cooper
Nettie's
development
side
of
things
specifically
towards
features
that
are
being
added
into
Cooper
Nettie's
and
just
talking
about
the
design
of
those
features.
So
it
seems
like
there's
some
kind
of
Cooper
Nettie's
development
discussion
happening
as
well
and
cig
apps,
which
to
me
seems
relevant.
But
at
the
same
time
that
doesn't
seem
like
it's
the
court
or
to
my
opinion,
it
doesn't
sound
like
it's.
G
B
A
A
But
that
means
we
there's
just
the
development
of
new
tools
such
as
helm
and
extensions
and
compose
and
other
things
that
help
operators
do
their
job
well,
hopefully,
and
then
there's
features
that
we
can
also
get
into
Cooper
Nettie's
to
try
to
improve
that
experience,
and
so,
as
we
learn
we'd
like
to
be
able
to
kind
of
enable
improvement
in
that
area,
so
that
does
touch
on
Cooper
Nettie's
features
as
well.
As
you
know,
best
practices
and
all
kinds
of
other
things
are
on
operating
those
applications
and
building
them
to
Ramon
Cooper
Nettie's.
A
C
A
really
good
job,
tough
on
all
of
that
yeah
I.
The
first
kind
of
organically
grew.
This
way
we
originally
intentionally
had
your
view,
mat
Fisher
on
what
it
was
going
to
be,
and
it
just
kind
of
just
kind
of
grew
into
this
and
I
think
it's
been
helpful
and
I'd
like
to
see
where
it
goes,
but
if
anybody
has
concerns
about
anybody
else
has
concerns
week.
Majority
of
the
group
has
concerns
office.
Would
really
love
to
hear
about
that.
D
It's
not
a
concern,
but
I'll
just
say
that,
like
people
comment
or
August,
the
gaps
is
one
of
the
more
big
and
active
things.
That
would
mean
that
it
might
be.
One
is
actually
ready
for
mitosis.
You
know
so
the
book
that
I
talked
to
Brian
about
that
recently
he's
very
open
to
the
ideas
they're
being
new
cigs
to
come
as
there's
demand.
D
What
I
see
is
if
things
happen
when
they're
like
it,
takes
an
entire
community,
but
also
takes
some
leaders,
a
mat
Michelle
who,
like
just
keep
it
going
and
obviously
if
the
thing
is
going
to
be
centered
around
there,
the
leaders
interest.
So
there's
someone
that
wants
to
lead
a
cig
with
a
different
topic.
As
you
mission,
you
know,
bring
that
up
well
happy
to
help
them,
but
they're
going
to
need
to
like
create
that
community
themselves,
but
I
think
it's
a
good
thing.
B
So
one
question
that
comes
to
mind
about
that,
though,
is
so,
if
you
look
at
the
so,
if
you
have
this
fear
of
concerns
that
the
gaps
is
just
primarily
focused
on,
and
there
are
things
that
the
edges
and
you
and
you
look
at
where
those
things
get
pushed
out
into
so
specifically
to
Nettie's
development
of
streams.
It
relates
to
applications.
B
It's
always
good
to
wonder.
Ok,
so
if
that's
get
pushed
out
of
the
state,
where
does
it
go
and
visit
enough
gravity
that
it
needs
to
create
anything,
will
consider
or
is
it
something
they
could
actually
should
expand
the
gravity
of
the
passaic
to
encompass
it,
because
the
thing
that
we
don't
want
to
see
is
for
the
things
to
just
disappear
or
two
to
not
be
covered
for
to
city
left
in
some
sort
of
nebulous
state.
B
A
I
one
thing
I
was
going
to
suggest
was
in
a
sense.
This
sig
is
one
of
the
few
cigs
that
actually
has
a
number
of
smaller
sub
sig
sub
groups
working
together,
the
home
team,
which
is
you
know,
in
a
sense,
a
very
self-directed
component
that
works.
Well,
you
have
the
app
controller
work
and
you
do
have
like
the
parts
that
are
covered
as
components.
D
The
way
I
think
about
this
is
when
we
did
our
2017
planning.
We
had
that
dock,
which
star
got
a
very
high
level
of
abstraction
and
I
chose
a
lot
of
those
yearly
goals
and
they
were
very
consciously
chosen
to
require
a
crossfade
collaboration
to
meet
them,
and
so
we're
gonna
have
a
mixture
of
you
know
very
focused
discussion,
but
we
also
have
to
make
sure
we
set.
We
some
gold
every
quarter
that
force
us
to
collaborate
and
I.
Think
we
do.
Okay
at
that,
but
yeah.
A
So
how
about
this?
Because
we're
talking
about
the
idea
of
maybe
some
cigs
here
too,
just
because
we've
got
naturally
got
that
and
just
bringing
in
so
folks
can
collaborate
and
work
together.
If
there's
a
few,
people
want
to
go
off
on
their
own.
But
how
do
you
meet?
How
do
you
come
back
and
share
that
if
you
want
to
throw
an
action
at
me,
I
am
happy
to
crap
together
some
doc
and
we
can
put
that
up
in
the
community
because
it
says
hey
you're.
D
Yeah
yeah
I
think
I'll.
Do
mea
culpa,
like
I've,
had
a
lot
of
common
ice
happen
to
work
with
people
who
are
on
storage,
had
a
lot
of
conversations
in
the
hallway
with
them
about
like
what
apps
people
need
from
storage.
I
expect
those
to
turn
in
proposals.
Maybe
we
people
are
saying,
though,
should
be
had
in
cigs,
so
that
even
the
collaborative
park
is,
you
know
visible
from
the
start,
I'm,
not
sure.
If
that's
the
feedback,
this
being
given.
B
Yeah,
so
this
is
interesting
because
we
have
we've
had
some
discussions
about.
We
had
a
few
cigs
leaders
in
the
room
talking
about
this
and
there
might
be
a
notion
of
maybe
there's
a
fig
as
far
as
the
machinery
around
the
interest
group
that
there
might
be
something
or
a
space
for
special
user
groups
as
well.
B
Like
some
more
informal
focused
around
a
proposal
you
get
together,
you
break
apart,
like
really
just
as
part
of
the
feature
process
and
not
necessarily
having
all
the
groups
and
all
the
things
that
a
fake
has
tied
to
it,
because
the
I
think
Matt's
comment
about
the
human
resources
part
is
is
true
for
some
people,
a
lot
of
us
have
many
irons
and
many
fires.
So
we
don't
want
to
exclude
people
because
they
don't
have
time
so
making
it
as
lightweight
as
possible
might
be
a
way
to
help
facilitate
that.
B
But
there
definitely
seems
to
be
in
this
group
a
dynamic
of
many
different.
You
know
every
application
is
its
own
ecosystem
and
then
you
have
the
crew
Nettie
ecosystem.
On
top
of
that,
so
there's
probably
is
going
to
be
some
innovation
in
terms
of
how
things
and
subgroups
work
here
that
is
going
to
be
an
interest
to
the
community
at
large.
C
I'm
really
open
to
hearing
about
what
people
take
away
from
their
weekly
sagat's
experience.
Maybe
that's
better
done
in
a
forum
or
survey,
but
I
really
want
to
know.
Why
is
it
that
people
come
because
there's
almost
40
people
that
come
sometimes
and
I
give
a
meeting
like?
What
do
you
take
away?
Is
it
just?
Are
you
just
there
for
the
first
part
or
you
just
there
for
the
end?
C
So
you
can
ask
your
questions
and
when
you
what
topics
interest
people,
because
they
think
that
my
inform,
if
there's
some
patterns
there,
that
I'm
informed,
possibly
if
we,
if
we're
covering
too
much
or
if
we
need
to
split
or
want
to
go
to
subside
rat
I,
think
that
it's
like
it's
feedback
and
data
that
I
really
haven't
got
enough.
Only
gotten
really
positive
feedback
about
every
particular
part
of
the
agenda
and
I
kind
of
want
to
know.
If
all
of
it
is
relevant
to
everyone.
B
Great
Michelle
I
just
put
a
to-do
item
in
the
actions
for
you
to
come
up
with
that
today.
Do
you
need
any
help
from
the
community
or
anybody
to
help
organize
that
or
I.
B
B
Ok,
so
this
document
we're
going
to
leave
right
access
available
for
a
period
of
time,
probably
after
a
week
or
so
it
will
get
turned
into
a
read-only
document
that
will
be
shared.
Probably
it
will
retain
means
is
obviously,
but
in
the
time
after
this,
it
would
be
great
to.
If
you
think
of
anything
else,
you
want
to
add,
add
it
in
there
and
make
sure
that
your
name
is
so
if
you
had
it
post
facto.
B
Definitely
add
that
because
we
definitely
want
to
keep
this
document
as
a
living
document,
also
just
as
a
health
keeping
thing
here
at
the
end
of
this
retrospective
I
would
love
to
have
some
feedback
from
all
of
you.
Was
this
valuable,
and
would
you
like
to
continue
doing
retrospectives.
A
Offering
if
this
is
matt
Farina,
I
guess
I
should
say
my
full
name
and
I
find
this
to
be
very
valuable,
because
I
really
want
to
hear
the
feedback,
vocab
and
well
Michelle
and
I
regularly
catch
up
on
things.
Hearing
entirely
different
perspectives
adds
to
our
ability
to
help
enable
y'all
and
so
I
I'm,
really
appreciative
of
this.
B
Cool
okay.
Well,
that
concludes
the
first
retrospective
for
sig
apps
for
1.5
I,
sincerely
appreciate
everybody's
great
participation
and
going
on
with
me
as
we
go
through
this
process.
Next,
your
perspective
as
we
go
through
this.
If
there's
anything
anybody
wants
to
change
or
make
this
week.
So
please
let
me
know
and
we'll
do
that
I'm
going
to
turn
it
back
over
to
amend
Michelle.
A
Thank
you
for
doing
this
retrospective
I
I
found
it
should
be
useful,
and
so
thanks
everyone-
and
that
is
all
that
we
had
for
this
week's
meeting.
We
just
gave
the
whole
meeting
up
for
for
doing
the
retrospective,
and
so
that's
all
we
have
did
anybody.
We've
got
12
minutes
left
for
any
last
minute
announcements
or
anything
that
anyone
wanted
to
share
for
the
week.
The
force
open.