►
Description
As part of https://gitlab.com/gitlab-org/gitlab-design/-/issues/2178, this is week 11 of the Tufts / GitLab Capstone project. Gina Doyle, and Ben Leduc-Mills meet with the Tufts students: Calisa, Claudia, Emmeline, Melinda, and Alex, to review student questions and deliverables.
A
A
Our
official
presenting
time
is
7
to
7
15
and
we
will
like
send
the
zoom
link
as
soon
as
we
get
it.
I
do
think
Linda's
also
going
to
send
you
an
email
with
that
information
when
it
comes
yeah,
so
just
to
go
over
like
exactly
what
we're
working
on
in
the
tasks
list.
So
we're
finishing
a
comparative
report
in
the
next
two
days.
A
That's
basically
finished,
but
we're
just
like
cleaning
it
up
and
making
sure
it's
perfect
and
that's
reviewing
the
two
usability
tests.
We
did
and
kind
of
seeing
how
we've
made
improvements
and
then
further
suggestions
for
like
how
we
can
improve
in
the
for
future
yeah,
as
mentioned
before,
we're
working
on
the
video
project.
So
we
already
have
some
progress
there
with
the
script.
We're
also
going
to
be
doing
a
poster
that
Claudia
is
leading
there,
that's
going
to
be
for
next
Friday
as
well,
and
then.
A
Finally,
we
have
like
another
prototype,
we're
working
on
which
we're
also
going
to
be
showing
you
later
today
and
then
our
presentation
and
final
report
so
we'll
be
sure
to
give
you
access
to
all
of
these
deliverables
once
they
are
finished
yeah.
So
just
like
basically
finishing
all
of
that
up
awesome
within
the
next
week
and
a
few
days
by
May,
8th
everything
will
be
done
and
then,
of
course,
we're
presenting
for
the
ux
team
on
May
9th
and
we're
really
excited
about
that
as
well.
Nice.
A
A
C
C
Yeah
we
also
changed
up
the
layouts
of
this.
Just
a
tiny
bit
removed
redundant
features
that
we
thought
weren't
unnecessary,
such
as
suggested
actually
even
changes,
wording
right
here
later
yeah
and
then
fix
up
some
of
the
Prototype
here,
because
before
the
edges
were
like
misaligned,
so
it
looked.
Weird
I
wasn't
actually
sure
how
to
execute
this
to
I
guess
like
fit
the
design
system
the
most,
because
I
feel
like
the
code.
C
Editor
isn't
meant
to
be
used
in
a
preview
like
this,
so
but
I
just
kind
of
made
it
into
the
same
like
border
that
the
code
editor
has
currently
on
other
pages
and
then
included
it
here
and
and
then
for
this
page.
We
wanted
to
label
the
this
one
right
here.
This
I
guess
it's
a
pipeline
status
thing
that
people
were
confused
with
so
I
went
ahead
and
label
this
one
and
then
I
added
a
new
I
guess
feature
here
to
expand.
C
B
C
B
C
I
think
people
I
think
it
was
a
mix
of
both
I
guess
because
we
didn't
have
any
interactive
things
prototype
within
our
prototype
like
when
they
clicked
on
it.
Nothing
happened,
but
also
people
were
saying
like
they
wish
there
was.
There
were
other
actions
other
than
just
re-running.
That's
like
step
in
the
job.
B
Okay,
yeah
I
mean
because
I'm
not
sure
if
the
feedback
that
you
got
was
they
didn't
know
that
you
could
click
on
those
and,
if
so,
adding
some
type
of
indicator,
a
better
indicator
to
see,
make
sure
that
they
know
that
they're
clickable
it's
good
feedback,
but
I,
don't
know
what
actions
they
would
be
looking
for.
Did
they
specify
yeah.
C
That's
a
great
point:
I
guess
they
didn't
because
of
the
fact
that
it
wasn't
interactive
but
yeah,
perhaps
but
I
think
it's
because
the
fact
that
there
was
only
they
could
only
see
the
the
rerun
button
so
yeah.
That's
why
they
assumed
that
there
wasn't
anything
else.
So
maybe
yeah,
maybe
that's
something
that
we
could
have
tested
a
little
bit
more
on.
But.
B
Okay,
yeah
I,
just
for
that
one,
if,
if
you're
gonna
end
like
if
you're
gonna
show
those
I
would
say
that
there
are
other
actions
when
you
click
into
them,
because
when
you
click
into
them
it's
a
job.
So
you
see
the
job
details
and
there's
other
options
on
that
page.
So,
potentially
you
could
incorporate
those
onto
those
little
pills.
B
C
B
D
B
C
C
A
I
just
had
a
quick
question
returning
back
to
the
visualize
piece
for
a
second,
if
you
don't
mind,
I,
don't
remember
like
what
it
looks
like
to
pop
up
into
like
more
information
when
I
had
like
gone
through
I
think
initially
and
looked
at
it.
I,
don't
remember
like
having
that
and
maybe
because
it
was
like
not
maybe
like
the
most
updated
version,
or
maybe
it
didn't
have
that
capability
because
of
like
this
specific
code
that
was
in
there.
E
Share
my
screen
with
that,
because
I
actually
remember
that
there
was
like
a
little
page
in
there,
so
I
just
checked
it
out
again.
It's
this
and
I
think
the
reason
why
most
of
us
didn't
quite
remember.
It
is
because
it's
like
a
little
bit
of
shoes
or
like
a
little
bit
like
complicated
for
us.
If
we
don't
have
a
lot
of
experience
with
XC.
This
is
what
happens
when
you
click
on
like
a
build
job.
If
you're
here
you're
in
your
pipeline,
you
click
on
build
job.
Takes
you
right
here:
okay,.
A
E
B
E
Yeah
I
feel
like
one
of
the
things
that
we're
like
aiming
for
when
trying
to
make
this
part
more
interactive
is.
Maybe
you
show
like
how
the
code
looks
in
the
yaml
file.
I
know.
This
is
like
right
now
here,
like
you,
do
have
like
The
Echoes
like
that
are
like
what
the
Yamaha
actually
has,
but
it
doesn't
a
little
bit
more
like
has
more
information
than
that.
E
B
B
E
B
E
B
A
A
B
The
things
I
brought
up
was
the
only
stuff
that
I
saw.
I
do
want
to
say
that
you
did
a
really
great
job
like
it's
funny.
I,
remember,
I
told
you
that
the
one
of
the
teams
is
looking
to
do
a
catalog
type
of
page
for
the
templates
and
what
they're
looking
into
is
basically
what
you
just
researched.
So
it's
it's
really
great
work
and
and
I'm
very
happy,
I'm,
happy
and
I
hope
you
guys
learn
stuff
too.
C
B
E
I
think
at
least
on
my
side,
if
I
can
I
mean
I'm
speaking
for
myself,
but
personally
I
feel
like
I
learned
so
much
in
this
project,
and
that
I
am
happy,
like
my
own
personal
goals,
of
like
figuring
out
how
cacd
works
and
how
so
getting
closer
to
like
the
UI
ux
design
process.
I
accomplish
things
like
this
project,
so
I'm
really
happy
with
that.
C
Yeah
I
definitely
really
enjoyed
using
the
design
system
and
learning
I
thought
I,
guess
something
that
I
do
Wonder
during
this
process
of
using
it
is
like
how
far
can
like
does
all
the
do.
All
the
components
that
you
currently
design
right
now
come
from
the
design
system,
or
do
you
ever
come
up
with
your
own
thing
like
that?
Is
you
know,
or
do
you
have
to
actually
add
something
to
the
design
system
in
order
to
use
it
like
from.
B
But
then
there's
also
times
where
we
create
a
brand
new
component
using
new
Styles
new
shapes
everything
like
that,
and
that
goes
through
a
whole
process
with
the
design
system
Team.
So
you
have
to
like
create
an
issue:
go
through
use
cases
why
it
should
be
a
component
and
then
usage
guidelines
like
this
is
how
you
use
it.
This
is
when
it
should
not
be
used
so
on,
and
then
you
contribute
to
the
figma
kit.
B
B
C
C
C
B
A
A
I
think
it's
interesting
because
all
of
my
professional
experiences
have
been
remote
on
zoom
and
stuff
like
that,
since,
like
like
beginning
of
college,
so
I
think
that's
something
in
the
future.
I'm
still
hoping
to
get
like
an
in-person
experience,
but
I
think
for
what
we
were
able
to
do.
Like
everything
worked
out
really
well,
we
were
able
to
communicate
super
easily.
Our
Zoom
meetings
are
like
always.
You
know
at
the
same
time,
everyone's
been
so
great
at
getting
everything
done.
B
Yeah,
but
we
and
Ben
and
I
have
both
enjoyed
all
the
meetings
with
you.
I
would
say
you
are
all
super
organized
which
makes
working
in
professional
environments
so
much
easier,
not
everyone's
like
that.
So
it's
even
unique
to
have
like
a
full
group.
That's
as
organized
as
you
all
are,
and
I
think
that
you're
gonna
do
great
job
and
I'm
like
super
excited
to
see
your
presentation
and
see
like
what
what
the
other
students
were
working
on
too
just
to
compare.
Also
because
I
don't
know
what
their
projects
were
like.
A
B
It's
up
to
you
if
you
want
I
mean
so
we
have
our
meeting
scheduled
for
the
fifth
next
week.
If
you
want
to
just
do
that
like
if
you
don't
want
to
meet
on
Zoom,
you
can
just
send
me
or
in
the
channel,
maybe
send
us
like
the
deliverables
and
and
Ben
and
I
can
review
them.
If
you
want
it's
totally
up
to
you,
though,
okay.