►
From YouTube: Async Sketching Session - CI/CD Catalog
Description
Dov and Sunjung summarize the outcome of the async sketching session with the team members.
00:00 Intro
00:53 Icebreaker question - learning from others
03:37 Designs 🎉
04:45 Summary
- Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/388915
A
A
What
what
is,
what
type
of
information
was
most
important,
that
youth
that
our
team
members
think
and
there's
a
summary
on
the
right
side.
So
if
we
go
from
the
Icebreaker
question,
the
question
was
like
what
do
you
like
about
some
of
the
competitors
when
you're
using
the
cicd
catalog
or
the
CI
CD
feature
in
general,
but
it
was
mostly
focusing
on
the
catalog
and
it
seems
like
yup.
It's
just
interesting
to
see
that
it's
like
sticky
notes,
has
different
type
of
characteristic.
I
would
say
so.
A
It
seems
like
our
team
members
like
to
see
GitHub
Market,
please
it's
more
intuitive
and
the
layout
wise
is
also
easy
to
navigate
when
they
read
through
their
instructions
and
then
the
they
also
mentioned
the
well-defined
template,
which
is
grabbing
the
readme
file
from
the
repository
right,
yep,
so
yeah.
There
is
also
the
verbatims
here
that
you
can
also
see
it
later
and
then
for
the
circle.
Ci
is
mostly
the
the
common
benefit
of
like
having
orbs
it's
like.
They
hold
multiple
components
inside
so
they
can
hold
multiple
functionalities
and
then
their
side
part.
B
There
is
like
the
it's
trade-offs.
Okay,
it's
basically,
you
get
like
a
really
clean
experience
of
the
marketplace
or
the
catalog,
but
then,
if
you
want
to
go
into
the
details,
you
need
to
dive
into
the
fault
into
the
into
the
repo
or
you
get
like
more
information
in
in
some
sort
of
a,
for
instance,
the
left
navigation
side.
But
it
means
you
have
like
more
clicks
and
more
things
to
do
within
the
within
the
catalog
itself.
A
Yep
thanks
for
sharing
that,
so
this
was
kind
of
like
learnings
from
the
competitors
and
then
we
move
on
to
the
lovely
designs
here.
So
I
just
try
to
put
each
team
member's
name
and
then
their
design,
and
then
there
are
a
lot
of
things
going
on.
So
what
I
have
done,
for
example,
using
sorry,
Mark
I
use
your
example
and
then
I
just
try
to
Group
by
the
information,
for
example
like
Marcus,
the
the
name
and
then
there's
like
three
ctas
description.
A
So
what
kind
of
metadata
that
he
used
in
this
design
here
and
then
what
kind
of
like
supplement
information
that
did
he
like
to
illustrate
using
this
design?
So
I
just
try
to
analyze
everything
based
on
the
comments
and
then
also
the
design
itself.
So,
for
example,
for
the
index
page
like
what
kind
of
information
that
our
team
members
would
like
to
filter
it
by
and
then
what
kind
of
search
do
we
need
to
provide
for
the
user?
So
that's
something
like
that.
I'm
not
going
to
the
details.
A
A
Thanks
so
based
on
your
amazing
design,
we,
we
came
up
with
this
three
different
themes,
so
I.
Let's
say
this
is
the
most
of
course
important
theme
that
we
need
to
focus
on
like
Discovery,
discoverability
and
usability,
and
this
is
tangible
areas.
You
can
see
it's
more
like
what
kind
of
information
is
needed
per
user
when
they
need
to
find
the
right
components.
What
kind
of
information
is
needed
when
they'd
like
to
okay
I'm,
going
to
use
this
component
and
then
well
what
we
should
provide
for
them?
A
And
these
two
theme,
collaboration
and
trust,
is
like
less
tangible
item,
I
would
say,
but
it's
also
very
important,
just
considering
the
usage
of
this
context
for
user
so
for
the
collaboration,
they
have
two
different
parts,
one
for
the
maintainers
who
are
maintaining
these
components
and
then
the
components,
library
and
then
the
other
part
was
like.
Is
it
really
easy
for
the
first
time
user
because,
like
it's,
it's
their
collaboration,
considering
it's
a
private
catalog
and
then
there
is
a
developer
who
used
this
template,
but
there
is
also
another
team
member
who
maintained
this
like.
A
Is
it
really
easy
to
the
success
level
and
then
is
it
really
easy
for
them
to
collaborate
efficiently?
Enough
and,
of
course,
like
all
of
these,
things
should
happen
under
this
trust
Baseline.
Of
course,
this
is
more
slightly
more
relevant
to
public
catalog
concept,
but
it's
interesting
that
a
lot
of
team
members
also
mentioned
that
they
want
to
see
the
author.
They
want
to
see
if
it
if
this
components,
project
is
verified
or
not,
and
also
the
popularity
like
how
many
times
this
project
we
use
and
how
many
number
of
stars
Forks.
A
B
A
That's
true,
so
I
think
we
also
always
need
to
keep
about
that.
Keep
thinking
about
it,
because
it's
publishing
and
unpublishing.
It's
happened
by
those
author,
while
they're
another
layer
of
user
who
would
like
to
choose
interest
in
finding
the
component
and
just
try
to
use
and
adopt
this
components
to
their
project.
There
are
two
different
type
of
Target
users
that
we
need
to
think
and
yeah.
If
you
have
any
other
question
or
any
discussion
point.
A
If
this
discussion
inspired,
you
please
feel
free
to
reach
out
to
us
and
we
can
have
another
round
of
discussion
and
the
next
step.
So
maybe
I
can
share
this,
that
there
will
be
another
fun
and
lighter
version
activity,
design
activity
rule
coming
up.
We,
we
haven't
like
thought
about
the
actual
timeline
yet,
but
this
will
coming
up
fairly
soon,
so
we
like
to
hear
from
you
again
and
then
based
on
this
information
here,
that
you
amazingly
draw
using
the
tool
and
using
your
pen
and
paper
thanks
to
this
information.