►
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
So
I
was
asked
for
my
opinion
about
what
we
need
to
do
in
manage
group
and
I
think
we
should
restructure
it
into
axis
and
latex
and
import
access
really
important
lots
of
security
issues
there
as
well.
We,
the
group
that
was
hard
busy
analytics
I,
would
rename
it
from
measure
to
analytics
just
to
make
it
more
crisp,
like
it's
kind
of
analytics
across
the
the
whole
thing,
and
we
call
a
DevOps
core
and
value
stream
management
instead
of
analytics
this.
A
But
if
specific
categories
but
I
think
it's
kind
of
the
analytics
group
we
didn't
put
in
the
product,
so
I
think
that
makes
sense
and
then
the
FIR
group
I
think,
should
be
the
import
group.
They
do
importers
and
templates,
and
then
we
have
a
a
bunch
of
feature,
a
bunch
of
categories
which
I
think
we
should
deprecated.
So
we
have
navigation.
A
Navigation
is
not
the
task
of
any
specific
group.
Everyone
is
responsible
for
that
part
of
them
navigation.
If
you
add
a
new
feature,
you
change
the
navigation,
get
live.com
specific
functionality.
Well,
that
doesn't
make
sense
as
well.
Look
if
it's
for
buying
get
Lancome,
it
should
be
under
fulfillment.
If
it's
for
CIF
it
should
be
under
sis
CI
etcetera.
It's
always
someone
else
is
saying
there
shouldn't
be
anything
under
this
group
specifically
with
projects.
A
I
think
that
by
definition,
there's
going
to
be
an
overlapping
function
thing
so
I,
don't
think
anyone
can
do
projects
like
it.
It
depends
on
what
you
do
in
the
project,
so
I
don't
think
we
need
that
assigned
to
a
team.
In
fact,
I
think
importing
is
also
an
overlapping
function
thing.
The
reason
I
want
importing
is
because
we
see
we
haven't
done
a
good
job
at
importing
for
JIRA.
A
A
They
will
just
add
that
functionality
to
plan,
if
that,
if
it's
not
a
priority
of
the
planting-
and
they
will
do
it
because
they're
tasked
with
making
sure
things
can
import
so
it's
overlapping,
but
in
this
case
it
needs
to
overlap,
because
in
the
last
two
years
we
haven't
been
able
to
do
it
from
the
team
itself.
Maybe
the
importing
team
goes
a
bit
more
into
kind
of
synchronization
with
all
the
tools
over
time
kind
of
like
a
task
table
or
something
like
that.
A
B
A
The
admin
panel
is
again
it's
a
shared
thing
like
what
does
it
need
to
show
it?
It
needs
to
show
your
license,
uses
great
fulfillment
team.
Does
it
need
to
show
how
CI
is
running
great
CI
team?
So
it's
it's
a
shared
canvas
for
multiple
people,
abuse
I,
think
what
kind
of
abuse
is
it
creating
too
many
users
and
like
it's
the
access
team?
Is
it
using
too
much
CI,
Bitcoin
mining
or
something
like
that?
Okay,
that's
the
CIT
Oracle
app!
A
It's
our
abuse
team
would
be
nice
if
they
contribute
a
bit
more
to
the
product
core
product
itself.
So
we
can
dog
food
that
but
I
don't
think
there
should
be
a
specific
like
administration
team.
It's
it's
like
to
to
pull
it
to
its
extreme.
It's
almost
like
you're,
calling
it
the
gitlab
group.
Yes,
there's
gitlab,
but
like
that
overlaps
with
everything,
it's
not
that
extreme,
but
projects
groups,
it's
just:
it's
2-2
overlapping!
B
A
I
think
it's
important
to
get
there
a
lot
of
the
work
that
needs
to
be
done
right
now
is
from
the
individual
teams,
so
I
think
we're
it's
kind
of
a
cross
company
effort.
I
think
we
have
all
the
tools
in
place
I'm,
not
against
any
specific
team
owning
it.
There
is
a
bunch
of
tools,
so
someone
needs
to
maintain
that
we
could
call
it
the
import
and
internationalization
G.
Okay,
the
dread
I
have
a
bit.
Is
that
is
it
the
biggest
thing
to
solve
today?
A
Probably
not
okay,
yeah
import
and
internationalization,
when
why
not
it's
a
bit
of
a
weird
mix
but
I?
Think
that's:
okay,
okay,.