►
From YouTube: Product Group Conversation (Public Stream)
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
Hello,
everyone
and
welcome
to
the
product
group
conversation.
I'm
original,
I'm
the
director
of
a
product
management
for
the
deaf
section,
and
I
am
here
to
answer
any
questions
that
you
might
have
regarding
products
or
the
deaf
section.
A
I
see
our
agenda
is
pretty
light,
so
I'll
show
in
the
meantime,
I'll
talk
a
little
bit
about
some
exciting
things
that
we
have
coming
up
in
the
dev
section,
they're
on
the
slides
and
the
agenda.
A
A
So
we
finished
routing
and
membership
on
project
namespace,
which,
as
I
mentioned,
will
allow
us
to
port
over
functionality
from
group
to
project
already
coming
up
in
the
next
quarter.
People
can
already
start
moving
over
the
things.
A
really
another,
really
exciting
thing
that
we
accomplished
with
completing
this
phase.
Two
is
that
for
new
features
that
we
are
delivering
if
we
implement
them
with
this
new
namespace
concept,
they're
already
support
projects
and
groups
from
the
get-go.
So
I'm
really
excited
about
that
I'll
pause
to
see.
If
there's
any
questions
on
that
agenda,.
A
Do
that
it's
based
on
the
off
hand
and
their
priorities,
what
we
have
done
so
far
is
we've
found
a
way
to
move
forward
with
moving
administrative
capabilities
already
to
the
group
level.
We've
already
delivered
some
of
these
capabilities
by
creating
a
parody
view
for
group
owners
that
look
the
same
today,
if
you're
in
sas
or
in
self-managed.
So
we're
happy
about
that
accomplishment
and
we're
going
to
start
moving
over
administrative
capabilities,
but
only
for
provision
users.
A
So
what
we
want
to
make
sure
is
that
if
an
enterprise
owns
a
user,
they
can
have
control
over
their
user
and
they
can
already
start
blocking
unblocking
if
needed.
But
what
we
want
to
make
sure
is
that
if
I
have
a
free
community
user
who's
contributing
to
my
project,
they
don't
get
blocks
from
all
the
other
namespaces.
So
we're
going
to
start
this
with
provision
users
and
and
and
then
move
forward.
I
see
that
we
have
christina
on
on
the
line
christina.
A
C
Yeah
thanks
so
we're
in
the
process
at
the
moment
of
defining
some
ux
and
what
that
could
look
like
so
the
next
step
after
we've
done
it.
That
should
happen
in
the
next
one
or
two
weeks.
We
also
want
to
roll
out
the
broader
feedback
issues
so
that
everyone
can
take
a
look
at
what
this
could
potentially
look
like.
C
The
idea
right
now
is
that
it
will
look
very
similar
to
what
is
in
self-managed,
but
I
think
you'll
hear
from
me
in
the
next
couple
of
weeks
as
we
bring
this
to
the
broader
audience
that
is
captured
here.
A
D
Yeah,
this
is
definitely
something
that
we
are
going
to
start
doing.
We
actually
have
it
tied
to
an
okr
to
make
sure
it
gets
done
so
we'll
be
looking
at
starting
to
move
things
next
quarter
and,
like
gauri
said
we
are,
we
do
have
some
slightly
differing
admin
experience
based
on.
D
B
Thanks
thanks
for
that,
when,
when
are
we
at
the
point
where
all
the
kind
of
the
admin
screen
is
unbundled,
all
the
relevant
features
are
in
groups
and
available
to
sas
too.
A
What
what
the
team
has
been
working
on
right
now
is
identifying
what
can
move
to
the
group
level
and
what
makes
sense,
so
I
think
we're
currently
in
the
design
phase
of
kind
of
mapping
that
out
and
then
we're
gonna
iteratively
move
things
over
based
on
you
know
the
complexity
and
the
different
validation.
That
of
what
is
needed
first.
A
A
Yes,
so
we
have
an
epic
I'll
link
it
here
on
the
agenda
shortly
of
moving
administrative
capabilities
to
to
the
workspace
we've
already
identified,
what
should
be
in
the
mvc
for
that
which
is
mainly
around
user
management,
and-
and
we
already
have
some
plans
of
what
this
will
look
like.
It
does
not
yet
include
everything
but
I'll
link
the
epic
there
as
well.
So
you
can
take
a
look.
B
A
A
One
way
is:
let's
copy
an
admin
panel
for
the
workspace,
I'm
not
sure
that
that's
the
path
that
we're
gonna
follow,
but
it's
an
idea
and
then
it's
what
makes
sense
to
be
at
that
top
level
and
what
makes
sense
to
be
at
any
name
space,
because
we
we
can
do
user
management
on
a
project
level.
We
can
do
it
on
the
group
level.
What
does
that
mean
for
inheritance?
What
does
that
mean?
You
know
for
for
permissions,
and
so
on?
So
there's
a
few
open
questions.
A
I
don't
think
unbundling
is.
Is
that
difficult
in
terms
of
you
know
how
what
needs
to
move?
That's!
That's
the
going
to
be.
The
first
decision
point
is
here's
what
we're
going
to
move?
Here's,
what
we're
going
to
move
in
terms
of
the
mvc
and
to
give
our
our
customers
the
most
value.
Currently,
our
biggest
pain
point
is
those
enterprise
users
who
cannot
control
their
users,
so
we
want
to.
We
want
to
answer
their
needs.
B
Cool
thanks
thanks
for
that,
the
things
that
are
not
related
to
users
are
those
already
completely
moved,
or
is
that
not
a
priority,
because
the
user
stuff
is
more
important.
A
So
we
identified
the
user
things
as
the
most
important
if
you're
talking
specifically
about
the
administrative
capabilities.
So
there
are
some
other
issues
that
can
probably
features
that
can
probably
move
easier
more
easily
like
the
color
schema
or
things
like
that,
but
those
are
lower
priority.
What
we
do
want
to
do
is
identify
features
that
are
ready
to
be
moved
today
and
not
necessarily
administrative,
for
example,
work
items
in
that
matter.
A
How
do
we
make
epics
in
the
project
level
or
labels,
which
we
have
we've
heard
from
customers
that
that's
very
painful,
because
they
have
to
create
labels
duplicate
times
and
it
behaves
differently
based
on
where
they
are
so
there's
a
lot
of
different
features,
and
those
are
just
two
I
mean
any
group
can
migrate
at
this
point
from
group
to
project
level
and
and
already
be
solving
problems.
So
we're
excited
to
be
at
that
phase,
but
I'm
not
sure
if
you
were
asking
just
specifically
on
admin
or
just
in
general,
for
features.
E
All
right,
I
think
I
have
the
next
question
so
team,
a
great
presentation
congrats
on
all
the
innovations
in
value
stream
analytics
and
dora
metrics.
They
were
a
big
hit
when
we
did
the
gitlab
15
launch
as
well
so
extremely
valuable
to
the
outside
world
and
customers.
Can
you
give
us
a
flavor
of
what's
coming
next
and
it
looks
like
there's
already
some
information
in
the
doc,
but
maybe
you
can
speak
to
it.
F
Yeah,
I
can
take
it
if
you
want
hi.
This
is
product
manager
for
for
optimizing
for
the
value
stream
management
category.
So,
for
the
show
media
term,
we
are
looking
in
more
announcement
around
dora.
We
already
have
great
feedback
from
customers
that
it's
a
great
start,
some
of
the
metrics
the
apis
are
working
great,
but
especially
in
cases
that
there
are
complex
delivery
deployment,
for
example,
governments
and
others.
F
We
need
to
enhance
more
the
apis
also
in
order
to
improve
the
ability
to
have
a
quick,
deep
dive
into
the
value
stream
performance.
So
we
have
more
things
that
we
plan
to
make
it
very
easy
to
start
from
the
high
level
value
stream
from
really
kind
of
the
big
picture
and
to
help
bring
the
user
quickly
the
ability
to
quickly
drill
down
to
find
the
button
next
to
find
the
opportunities
to
improve.
So
this
is
another
things
that
we
are
working
on
the
design.
F
F
But
we
are
planning
more
and
more
validation.
There
are
topics
that
we
want
to
have
more
research,
and
we
have
also
great
collaboration
from
the
sales
team.
Here
they
have
a
lot
of
knowledge
coming
from
her
from
them,
as
well
so
kind
of
to
for
mid
long
term
is
still
something
that
we
are
working
on.
G
Yeah,
I
just
is
looking
at
the
response.
I'm
just
wanting
to
get
idea.
Are
we
talking
about
quarterly
or
we're
talking
about?
You
know
like
for
those
major
phases,
you're
aligned.
When
do
we
expect
to
see
some
results
and
what
kind
of
timeline
you're
looking
at
is
in.
A
G
D
All
right,
that
is,
the
million
dollar
question,
and
every
time
I
talk
to
a
customer
about
this,
they
ask
me
the
same
thing,
so
we
do
have
a
big
unknown
with
performance,
and
I
link
to
a
pretty
engineering
heavy
discussion
on
what
adding
custom
roles
and
permissions
will
do
to
already
sort
of.
D
I
don't
know,
there's
already
a
lot
of
performance
considerations
we
have
to
consider
now.
This
adds
a
lot
of
complexity,
but
anyway,
what
I've
been
trying
to
say
is.
I
really
hope
that
there's
something
our
customers
can
touch
and
feel
by
the
end
of
the
year,
so
you're
asking
for
like
a
high-level
ballpark.
That's
what.
A
D
Give
you,
with
the
caveat
that
again
it
is
until
we
have
this
con
constraint
sort
of
figured
out.
I
can't
be
100
confident
that
that's
my
best
guess.
As
of
now.
G
Yeah
talking
to
a
lot
of
customers
using
our
enterprise
provision
users,
some
of
the
feedback
we
got
is
we
did
a
lot
of
work
in
this
space
last
year
as
well.
I
think
some
of
our
capabilities,
definitely
the
feedback
I
got
is
better
than
what
github
and
microsoft
is
providing.
G
I
just
just
want
to
pass
back
that
the
comment
I
got
from
some
customers.
Thank
you
and
I
have
a
next
question.
So
we
have
a
lot
asking
them
in
the
in
you
know,
in
the
market
or
from
the
customers
that
our
gillab
grouping
on
namespace
and
the
grouping
tend
to
be
oriented
by
repositories,
projects
app
structure,
but
all
the
analytics,
especially
vsa
adoption
and
compliance,
or
even
our
security
posture
like
in
the
scorecard.
G
G
A
A
Workspace
is
that
top
level
namespace,
the
top
level
group,
if
you
will
so
it
would
cascade
everything
that
has
below
it.
So
again,
if
you're
thinking
of
the
top
level
group,
it
would
show
all
the
repos
beneath
it
aggregated
there
is.
There
are
some
epics
around
maybe
introducing
the
concept
of
teams
at
gitlab,
but
it's
not
currently
an
initiative,
that's
being
worked
on,
but
it
is
something
that
we're
thinking
about.
A
I
will
say
that
there
are
some
workarounds
to
kind
of
get
behind
that
and
that's
with
making
use
of
labels,
because
if
you
label
things
in
a
different
fashion,
you
can
group
them
in
a
different
way,
so
vsa
heavily
relies
on
labels.
So
if
someone
were
to
use
a
label
for
a
specific
team
or
something
like
that,
they
could
they
could
view
their
process
based
on
on
that
label,
so
they
could
use
it
that
way.
G
Yeah
that
that's
what
we
recommended
as
well
yeah,
thanks
for
that
and
some
customers
just
use
our
api
pulled
data.
Then
they
map
it
in
their
own
dashboard
in
a
way
that
mimics
their
organizational
up
so
both
options.
We
have
seen
that
being
used.
G
Well,
also,
compliance
sometimes
how
the
compliance
definition
is
also
come
down,
based
on,
let's
say
a
regulatory
requirement
applied
to
to
some
business
units.
Let's
say
there
is
an
anti-anti-money
laundry.
They
apply
to
a
set
of
applications
or
a
set
of
groups
that
that
might
not
mimic
the
application
hierarchy,
it's
more
aligned
to
to
the
business
function,
so
so
how
that
is
defined.
G
It's
still
propagate
down
and
end
the
project
level,
the
repository,
but
the
initial
setup
could
represent
a
little
bit
differently,
almost
like
an
agile.
If
you
think
about
agile
groups
that
group
hierarchy
can
be
very
different
from
the
delivery
grouping.
I
think
the
gabe
show
a
lot
of
examples
to
show
the
organizational
structure
from
agile
practice
and
the
planning
then
translate
or
map
that
to
delivery
team.
So
I
think
of
from
compliance,
it's
a
similar
type
of
ask,
but
I'm
just
thinking
workaround
could
be
how
we
do
agile
as
well.
H
Basically,
everything
in
kit
lab.
But
I
think
it's
just
the
common
thing
where
you
have
a
hierarchy
model
which
we
have
and
then
in
reality,
though,
there
are
different.
There
are
multiple
hierarchies
within
an
organization
that
are
used
for
different
things
in
terms
of
the
knowledge
architecture,
and
so
I
just
linked
to
some
of
the
fun
challenges
like
how
how
we
gitlab
ourselves
are
structured
from
an
hr
perspective
and
like
a
reporting
structure.
And
then
what
like
our
product.
H
Topology
structure
looks
like
in
our
layers
there
and
then
what
our
actual
like
group
and
subgroup
of
project
structure
look
like
they're
all
completely
different,
and
I
think
that's
what
some
of
our
customers
struggle
with
as
well.
I
Don't
comment
from
the
the
compliance
perspective.
We
definitely
hear
that
compliance
teams
are
concerned
with
a
lot
more
than
a
single
project.
They
frequently
have
responsibility
for
an
entire
business
unit
or
division,
and
so
that's
definitely
something
we
keep
top
of
mind
as
we
build
compliance
related
capabilities
as
we
work
on
our
iteration
plans
for
how
we
want
to
bring
capabilities
out.
I
Generally,
it's
going
to
be
faster
for
us
to
do
our
mvcs
at
a
project
level
understand
the
complexities,
the
edge
cases
that
we
need
to
solve
for
on
that
feature,
without
expanding
the
scope
to
all
those
edge
cases
for
groups
and
larger
units
and
then
in
subsequent
iterations,
expand
that
from
just
the
project
level
to
the
group
level
to
give
them
that
set
of
controls
over
the
entire
business
unit
or
division
like
like
you're
mentioning
so
definitely
something
we.
We
keep
in
mind.
G
I
just
want
to
thank
them
to
work
with
us
to
look
at
how
to
integrate
our
value
stream
and
others
with
the
jira
and
the
potentially
other
tools
that
that
is
one
of
the
top
us
by
a
lot
of
the
customers.
So
thank
you
for
the
effort.
Hopefully
we
we
will
come
to
a
place
where
we
have
a
clear
direction
and
what
to
implement.
F
Yeah
yeah,
we
definitely
will
make
it
and
yeah.
Thank
you
for
the
feedback,
and
so
we
are
really
looking
into
the
details,
and
this
is
as
well
great
opportunity
for
us.
You
know
to
complete
the
picture
for
customers
that
have
using
jira
pollution.
A
Great
well,
I
want
to
thank
everyone
for
joining
our
group
conversation
and
for
anyone
tuning
in
on
the
live
stream.
Thank
you
for
the
great
questions
and
the
great
feedback.