►
Description
Reviewing a low-cost experiment aiming to drive direct feedback from users, reinforcing contribution guidelines, and possible user research recruiting
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/218369
A
Other
things
it
is
is
like,
as
we
roll
out
changes,
especially
most
recently
like
on
the
dependency
list.
While
the
changes
are
gradual
and
small
date,
they
are.
The
recent
ones
are
noticeable,
so
the
user
may
land
on
there
and
notice
them
and
have
some
thoughts,
and
what
the
idea
here
is
is
when
they
have.
A
Those
thoughts
is
to
to
open
up
a
line
of
communication
for
them
to
to
share
them
with
us,
and
since
we
have
all
our
issues
in
the
open
and
and
since
anyone
can
contribute
by
creating
an
issue
or
emerge
request,
we
we
just
want
to
kind
of
reinforce
that
to
the
user,
possibly
need
user
interface.
Like
we'll
see
here
the
downside
here
is
you
know
we
don't
get
any
responses.
The
upside
is
it's
pretty
inexpensive
as
well,
take
a
look
at
in
a
minute.
Hopefully
we
get
a
direct
line
to
active
users.
A
We
could
establish
some
jobs
to
be
done.
We
could
ask
them
questions
like
what
were
you
trying
to
do
on
this
page?
What
would
you
like
to
do
on
this
page
general
feedback?
How
could
the
page
be
improved
and
then
also
we
may
be
able
to
start
recruiting
participants,
of
course,
we'll
see
if,
if
they
were,
if
it,
it
will
have
to
see
if
it
works
or
people
respond,
but
these
would
be
that
goals
that
we
would
have.
A
Okay,
let's
just
take
a
look
at
how
that
could
look
a
rather
so
on
this
page,
we're
looking
at
the
license
compliance
page-
and
this
is
the
worst
case
scenario,
because
we
actually
do
have
a
banner
on
this
page
saying
detected
licenses
are
out
of
compliance,
but
this
banners
as
well
is
alerting
the
user
that
we'd
like
to
feedback
from
them.
We've
it's
communicating,
hey
we've
been
updating
license
compliance.
You
may
notice
some
recent
changes.
We'd
love
your
feedback
on
the
recent
ones
interested
in
contributing
to
this
page.
So
it's
it's.
A
Bringing
our
contribution,
guide
links
there
and
just
letting
them
know
that
at
this
exists
and
it's
open
to
contributions,
and
then
we
have
this
call
to
action
to
provide
feedback
which
would
come
to
this
issue.
It's
not
populated
yet,
but
this
is
where
we
would
have
those
questions
that
I
mentioned
earlier.
Like
hey.
How
would
we
improve
this?
What
were
you
trying
to
do
on
this
page?
What
would
you
like
to
do
on
this
page?
A
We
could,
of
course,
CC
like
myself,
the
product
designer
and
Nicole,
for
example,
the
product
manager,
so
they
know
who
to
reach
out
to,
and
then
we
have
a
direct
line
with
them
and
their
feedback.
Another
one
is
that
they
could
create
an
issue
directly
and
if
they
click
this,
we
could
pre
populate
it
with
the
title
saying,
for
example,
license
compliance.
We
could
have
the
the
product
manager
in
the
product
designer
on
there
as
well
and
some
a
template
that
that
outlines
it
a
little
bit
that
helps
them
guide.
A
What
the
issue
could
be
a
little
bit
more
similar
to
our
feature
template.
So
this
page
is
just
a
dependency
list.
How
it
would
look
there.
The
downside
is,
the
banner
is
a
little
bit
big
and
I.
Don't
know
I'm,
not
I'm,
not
sure
about
it,
but
I
just
wanted
to
show
to
have
all
these
different
links
and
options
here
they
could
always
just
click
out
of
out
of
it.
A
Another
one
is
a
more
subtle
one,
so
here
we're
in
the
license.
Compliance
page-
and
it
says,
have
feedback
about
this
page
sure
with
us
here
and
that's
where
it
could
go
to
that
issue.
The
pre-populated
issue
like
feedback
and
license
compliance
that
I
pointed
to
earlier
or
the
same
on
the
dependency
page
a
little
bit
more
subtle,
but
the
copy
here
says
help
us
improve
by
assuring
feedback,
and
then
it
links
to
the
feedback
issue.