►
From YouTube: Kubernetes SIG Usability 20220201
Description
Looking for Jobs to Be Done volunteers to finish annotating and synthesizing collected data! Present 3 month proposed project plan (Feb - April).
A
A
Okay,
so
this
is
the
jobs
to
be
done,
project
plan,
so
basically
gabby
is
going
to
be
going
on
leave
for
a
couple
months,
and
so
she
wants
to
put
up
together
a
plan
for
while
she's
on
leave
basically
the
jobs
to
be
done
project
to
continue.
So
we
are
looking
for
about
three
people
who
would
be
able
to
commit
about
four
hours
per
month
to
help
with
this
project,
and
what
we're
doing
is
we
have
we
have.
A
The
goal
is
to
have
a
synthesized
list
of
kubernetes
jobs
that
we
can
then
use
to
start
really
understanding
how
people
are
using
kubernetes
and
where
the
project
might
need
to
invest
more
to
make
their
the
jobs
that
our
users
are
trying
to
do
more
seamless.
So
the
estimated
effort
we
have
right
now
is
we
need
to
review
interns.
A
So
we
think
that
with
all
of
the
reviewers
involved,
this
would
take
about
four
hours
to
synthesize
interviews
on
top
of
that,
and
so
what
we're
looking
for
is
over
the
next
three
months
since
it's
february
today
about
three
people
who
can
commit
four
hours
per
month
to
review
and
synthesize,
and
then
that
way
we
would
be
done
with
this
period
of
work
by
the
end
of
april.
So
our
goals
here
are
in
february.
A
Gabby
is
going
to
assist
with
this
and
over
the
next
three
months,
she's
gonna
be
able
to
do
about
two
hours
per
week.
So
one
thing
to
keep
in
mind
if
you're
interested
in
participating
in
this
is
that
we
already
have
our
youtube
video
that
carl
put
together
about
how
to
do
synthesis.
So
you
can
just
watch
that
to
sort
of
learn
what
the
overall
process
is.
A
C
Awesome
yeah
that
makes
sense
yeah.
I
I
responded
to
her
message
today
and
let
her
know
that
I
could
volunteer
to
you
know
to
be
one
of
the
three
so
and
I
did
attend
a
session
with
carl.
It's
probably
the
one
on
youtube
but
I'll
double
check.
I'll
watch
that
as
well.
I
was
in
a
session
with
carl
and
josie
a
month
or
two
ago,
so
I
haven't
done
the
annotation
yet,
but
I
think
this
I
can
contribute
and
commit
to
doing
that
so
yeah.
This
sounds.
A
A
Bye
yeah,
so
we
were
just
going
over
our
jobs
to
be
done,
project
plan,
which
is
the
only
agenda
item
we
had
today.
So
basically
gabby's
put
this
together
to
try
and
help
take
us
through
synthesis
and
we're
basically
looking
for
three
people
who
can
commit
about
four
hours
per
month
and
then
and
then
so
we'll
share
this
doc
in
the
channel
and
on
the
mailing
list,
and
then
we
also
have
a
youtube
video
that
will
link
everybody
to
that.
A
Emily
was
just
talking
about
which
is
basically
how
to
do
synthesis
and
annotation
of
the
video
so
that
we're
all
using
the
same
procedure
as
we
work
together
on
this
so
yeah.
So
I'll
share
this
to
our
youtube
channel.
So
folks
can
kind
of
see
what
our
project
plan
is
and
then
hopefully
we
get
some
volunteers
and
we
can
really
start
getting
to
the
next
level
of
data
synthesis
on
the
jobs
to
be
done.
A
C
A
D
A
Oh,
where
the
data
is
being
saved
yeah,
so
everything
is
on
google
drive.
We
do
keep
it
locked
to
participants
who
have
engaged
with
the
sig
and
basically
kind
of
become
known,
known
participants
just
because
the
people
that
we've
interviewed
have
given
us
a
lot
of
sort
of
information
about
themselves
and
their
jobs
and
their
work,
and
so
we
really
want
to
be
sensitive
to
that,
so
the
data
hasn't
been
scrubbed
yet
to
make
like
completely
open
source,
so
we're
just
having
people
who
are
sort
of
consistent
contributors
and
participants.
A
A
Just
the
timeline
that
I
was
just
sharing
with
our
project
plan
right
here,
so
you
can
kind
of
see
that
what
we're
looking
for
is
to
get
three
folks
to
commit
four
hours
per
month
over
the
next
three
months
in
order
to
allow
us
to
finish
the
annotation
of
our
interviews
and
do
the
synthesis
of
the
interviews
to
get
those
jobs.
The
synthesized
list
of
kubernetes
jobs
identified
based
on
all
of
the
interviews,
and
so
with
this.
A
A
For
our
may
meeting,
okay,
yep
that's
the
goal,
but
so
far
it
has
been
a
little
hard,
getting
consistent,
consistent
participants
in
the
annotation
and
synthesis
just
because
you
know
so
many
people
are
changing.
Jobs
and
kind
of
you
know:
we've
all
had
so
much
going
on
lately.
So
this
is
like
basically
a
pretty
optimistic
view.
If
we
get
everybody
to
be
able
to
commit
four
hours
per
month,
yep-
and
so
was
there.
A
D
D
A
A
Have
the
data
be
publicly
available
and
kind
of
empower
people
to
see
what
different
users
are
doing
across
orgs,
because
you
know
often
say
you
know
you
work
at
red
hat,
you're,
talking
to
red
hat,
open
shift
users,
and
here
what
we're
really
doing
is
talking
to
the
greater
group
of
kubernetes
users,
who
may
be
using
openshift
or
tkg
or
pure
upstream,
but
just
starting
to
kind
of
try
and
get
that
cohesive.
Look
at
what
jobs
are
they
actually
trying
to
do
and
how
is
kubernetes,
meeting
or
not
meeting
those
so
yeah?
A
I
think
it's
gonna
be
fun.
I
think
a
lot
of
people
get
value
out
of
it,
but
right
now
it's
just
because
the
kubernetes
upstream
project
is
so
focused
on
kind
of
go
developers.
Back-End
developers
actually
getting
like
a
group
of
people
who
are
skilled
and
interested
in
doing
this
more
user
researchy
work
has
been
difficult,
so
that's
kind
of
where
we
are
right
now.