►
From YouTube: GitLab Hackathon - Migrating GitLab Pajamas components
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
Time
not
yet
good
morning
afternoon
already
evening,
everyone,
I'm
christopher
haracki
senior
code,
contributor
program
manager
and
with
us
we
have
some
george
and
jeremy,
which
I'm
gonna
introduce
you
them
in
briefly
before
that.
Welcome
to
another
session
hackathon
session
we
are.
This
is
the
last
session
of
the
day.
There
is
another
one
tomorrow
which
is
the
wrap
up
of
the
hackathon.
A
Let
me
quickly
share
my
screen
for
some
reminders
regarding
the
hackathon,
so
you
can
find
all
the
necessary
information
about
the
hackathon
on
the
hackathon
website
there
you
can
find
the
sessions
that
happened
earlier
today.
A
You
can
find
if
you're
new
to
gitlab,
you
can
find
a
link
to
the
contribute
page
where
you
can
find
ways
to
contribute
code
to
gitlab,
or
you
can
also
as
well
find
something
that
we
added
today,
which
is
about
kit
board,
how
you
can
set
up
your
development
environment
with
jitbot,
so
you
don't
have
to
spend
a
lot
of
time,
setting
up
your
development
environment,
locally
gitbox
offers
a
lot
of
nice
features
saves
a
lot
of
your
time.
A
You
can
also
find
on
the
hackathon
page
as
well
links
with
suggested
issues
for
this
hackathon
to
work
on
and
the
counter
we
have
44
merch
requests
so
far
submitted
in
the
past
10
hours,
which
is
exciting.
Thank
you
all
the
prizes,
as
well
as
the
sessions
with
the
links
to
participate
and
the
recordings
of
the
sessions
that
already
have
happened.
Every
time
the
session
is
complete.
We
update
the
the
website
so
feel
free
to
join
them
and
an
important
reminder,
because
here
at
gitlab
we
want
to
have
safe
and
inclusive
events.
A
Please
keep
in
mind
that
we
enforce
the
community
kind
of
code
of
conduct
so
in
case
that
you
see
or
have,
and
you
know
or
be
face,
an
inappropriate
behavior.
Please
feel
free
to
reach
out
to
us
at
contact
gitlab.com
we're
keeping
an
eye
on
all
our
comments,
merge,
requests
and
also
guitar
in
case
some.
We
notice
inappropriate,
behaviors
but
pills.
Please
feel
free
to
reach
out
in
case
that
you
don't
feel
safe.
Speaking
of
reaching
out.
There
is
also
the
contributor's
guitar
room
in
case.
A
You
have
any
questions
you
want
to
reach
out
to
mentors
to
the
core
team.
Anyone
feel
free
to
join
the
tech
discussion
there
we're
keeping
an
eye
on
there
and
we're
more
than
happy
to
to
help
you
and
with
no
further
ado.
I
will
stop
my
screen
and
I
will
hand
it
over
to
you
folks.
B
Okay,
this
looks
promising.
Have
we
seen
the
slides,
hey,
good,
I've
done
it
right,
cool,
so
yeah
welcome
to
the
the
component
migration
session.
So
my
name
is
sam
beckham,
I'm
a
front-end
engineering
manager
here
at
gitlab.
You
can
find
me
at
sandy
beckham
on
gitlab
or
on
twitter.
If
you
ever
want
to
contribute
to
gitlab,
do
you
have
any
issues
with
some
of
the
the
things
we're
going
to
talk
about
today
or
you
just
want?
You
know
some
general
help
getting
started
contributing
please
reach
out
to
me
at
either.
B
One
of
these
I'm
always
happy
to
help.
I'm
joined
today
as
well
by
jeremy
elder
so
I'll.
Let
jeremy
introduce
himself
quickly.
C
Yeah
thanks
sam,
so
jeremy
elder
senior
product
designer
I'm
working
primarily
on
the
foundations
team,
so
focusing
on
the
design
system,
pajamas
and
helping
with
this
migration
effort.
And
then
we
also
have
george
on
the
call
too
he's
not
on
the
slide.
But
I
don't
know
if
george,
if
you
wanted
to
introduce
yourself
because
you're
a
big
time
contributor
too.
D
A
B
A
little
bit
the
pod
hoodie
as
well
by
the
way
that's
gonna
gonna,
tie
in
nicely
what
we
talk
about
a
little
later,
so
yeah
a
little
bit
about
what
we're
here
to
talk
about
we're
here
to
talk
about
our
migration
effort.
For
basically,
we
want
to
increase
our
reduction
of
our
design
system
here
at
git
lab.
B
B
There's
a
nice
sort
of
side
effect
of
this
as
well.
We
get
to
remove
bootstrap
from
gitlab,
so
bootstrap
is
great
at
exactly
what
the
name
suggests,
and
that
is
bootstrapping
things,
but
now
that
we
have
our
own
component
library
and
our
own
design
system,
we
can
start
to
replace
some
of
those.
B
D
B
So
doing
this,
it
allows
us
to
have
a
lot
more
code,
reuse
and
a
dried
code
base,
so
using
our
component
library
just
means
that
we're
using
these
components
all
over
the
place,
rather
than
rewriting
them
and
copy
pasting
them
and
things
for
all
of
our
different
views,
and
this
allows
us
to
have
faster,
updates
and
easier
bug,
fixing
so
they're
kind
of
the
idea
being
we
fix
it
in
in
the
component,
and
it
fixes
it
for
all
of
the
places
that
we
use
this
component
or
we
have
a
slight
update
to
one
of
the
components
and
we
just
you,
send
it
out
to
everywhere
that
uses
that
component.
B
Another
thing
that
this
helps
with
for
us
on
the
engineering
side
at
least,
is
less
than
party
dependencies
right.
So
we
already
said
we
want
to
remove
bootstrap
if
we
can
remove
bootstrap,
there's
also
still
jquery
in
gitlab
judges
too
harshly,
there's
other
drop-down
libraries
and
things
in
there.
B
So
we're
not
shipping
all
of
these
different
libraries
and
plugins
and
things
we're
just
shipping.
It
live
ui.
You
know
down
down
the
wire
to
your
browser
which
results
in
in
performance
games,
because
you
know
we
ship
less
send
list
code.
We
should
should
be
a
bit
quicker
right.
That's
a
theory
at
least
there's.
There's
design
benefits
to
this
as
well,
so
I'll
pass
it
over
to
jeremy
to
talk
about
them.
C
Yeah,
so
just
a
few
highlights,
with
with
the
component
migration,
we're
able
to
have
more
of
a
single
source
of
truth
rather
than
what
the
component
behaves
or
looks
like
in
the
product
versus
the
design
system
and
that
traverses
over
to
overarching
design
philosophy,
so
that
we
can
have
a
more
of
a
singular
mindset
when
we
apply
components
and
use
them
in
in
a
different
place.
C
We
can
document
it
in
one
place,
have
that
philosophy
defined
and
then
make
sure
we're
applying
it
correctly
to
the
product
and
other
use
cases,
robots
component
library
just
again
on
the
documentation
side
and
the
philosophy
kind
of
packaging
that
all
up
in
one
place
and
making
that
library
a
go-to
source
accessibility
is
huge.
That's
by
by
having
those
components
migrated.
C
We
know
that
when
we're
building
them
and
testing
them
in
one
place
and
building
the
the
correct
parameters
and
features
and
attributes
to
use
aria
and
other
accessibility
features,
when
we
do
that
in
one
place
and
we're
able
to
propagate
those
into
the
product,
we
know
that
we're
doing
our
best
to
make
sure
that
our
accessibility
is
robust
through
the
product
and
those
components
as
they're
used
are
accessible
and
then,
lastly,
just
to
help
avoid
visual
regression,
so
that
we
we
can
prevent
testing
a
product
in
one
play
or
a
component
in
one
place,
and
then
we
go
elsewhere
and
it's
it's
impacted
by
other
styles
and
and
looks
different
or
behaves
different,
causing
that
regression
we're
able
to
have
it
singularly
implemented,
used
and
styled
across
the
board.
C
So
that
is
why
we're
doing
this
from
a
design
standpoint.
C
B
This
this
is,
this
is
gitlab
ui.
This
is
a
screenshot
of
kit
lab
ui.
This
is
the
the
component
library
side
of
things.
There's
there's
all
sorts
of
components
in
here.
We've
got,
you
know:
accordions
badges,
dip,
pickers
carousels,
all
sorts
of
things
and
again
they're
all
built
on
the
design,
well
design
system,
but
the
ones
that
we
want
to
focus
on
for
this.
So
we're
saying
we
want
to
remove
bootstrap
right,
so
we're
just
focusing
on
alerts,
pagination,
pop-overs
tool,
tips,
buttons,
drop-downs,
tabs
and
models.
B
We
focus
on
these.
We
can
in
theory,
remove
bootstrap
and,
and
you
know,
get
them,
then
performance
gains
from
not
having
to
ship.
Bootstrap
is
the
idea.
So
you
know
the
the
component,
library
and
design
systems
are
pretty
big
and
they're
growing
all
the
time.
If
we
had
a
thing
where
we
said,
replace
everything
we'd
be
here
forever
right,
so
we've
scoped
it
down
to
the
bootstrap
side
of
things.
B
B
What's
our
800
900
issues
like
that's
a
lot
of
issues
to
go
through
and
you
know
we
we've
done
really
well
again
through
most
of
them,
like
oversight,
no
almost
600
there,
there's
maths
on
the
fly
like
I'm
really
struggling
with
that,
but
yeah
thanks
for
your
contributions
right
for
the
for
the
hammer,
migration,
epic.
So
this
is
this
is
the
part
that
I've
been
looking
at.
You
know
special
calls
to
china
kopo
and
gary
like
there's.
B
There's
all
sorts
of
people
who've
contributed
to
this,
but
these
these
were,
you
know
some
some
notable
ones.
You
know
we
couldn't
get
it
done
without
you
right,
which
is,
which
is
why
we're
back
here
asking
for
for
more
help
to
get
it
through
and
over
the
finish
line.
B
There's
there's
there's
links
to
both
the
epics
here,
we've
kind
of
done
a
hammer
one
and
a
view
on,
but
yeah
I'll
go
over
the
handle
one
a
little
bit
more
later
on.
But
if
jeremy
wants
to
talk
about
the
view
one
and
how
we're
doing
with
the
view
migration
so
far,
yeah.
C
Really
quick,
as
you
can
see,
getting
really
close
to
completion
here
so
want
to
emphasize.
C
You
know,
just
could
use
help
getting
across
the
line
and
then
really
emphasize
the
help
for
the
the
hamilt
piece
of
this
as
well,
because
we
won't
be
able
to
fully
reach
our
performance
goals
and
gains
until
until
everything
is
complete.
So
but
again,
we've
had
some
some
great
community
contributions
and
really
really
thankful
for
that.
C
B
C
Yeah,
I
can
go
through
this
quickly.
Just
some
highlights
you
could
show
kind
of
our
burn
down
for
the
effort
here
and
and
this
one
is
getting
really
really
tiny.
So
there's
there's
not
much
left,
as
you
can
see.
Out
of
this
one,
I
believe
looks
like
six
issues
remaining
specifically
for
buttons
and
alerts.
You
go
to
the
next
slide
here,
we're
taking
a
look
at
dropdowns,
modals
tabs.
You
can
see
it's
five
left,
so
we're
getting
extremely
close
x
side
and
finally,
popover's
tooltips
three
left
here.
B
You
can
probably
see
from
these
chats
that
the
view
migration
is
going
incredibly
well.
We
we
don't
have
chats
like
that
for
the
humble
migration,
but
we
do
have
this
nice
table.
It's
not
we're
not
doing
quite
as
well
with
the
hamilt
stuff.
We
need
a
bit
more
help
here,
the
the
handle
stuff.
It's
yeah,
it's
been
a
little
more
slow
going,
but
it's
the
things
like
the
alerts
and
the
buttons
they're,
quite
small
they're,
pretty
simple
to
pick
up
I'll.
B
Show
you
a
little
bit
more
on
that
later
on,
there's
also
a
video
from
the
last
one.
Where
I
took
you
through
how
to
do.
B
I
would
do
an
alert
and
then
how
to
tackle
that
the
if
you
look
at
like
the
alerts
and
the
buttons
we're
really
close
with
them
ones,
the
alerts
is
actually
we've
done.
Two
more
since
I
took
this
screenshot
so
we're
about
90
something
percent.
Now
with
them
and
buttons.
You
know
we're
just
under
half,
but
there's
a
lot
there
right,
we've
still
done
77,
that's
pretty
good
and.
B
Of
pages
not
77
individual
buttons
right,
it's
quite
misleading,
there's
a
lot
of
buttons
that
we
need
things
like
the
the
models,
the
drop
downs
and
the
tabs.
There's
not
a
lot
of
work
done
on
these,
and
the
majority
of
that
reason
is
because
to
to
use
gitlab
ui
for
these
they're
a
bit
more
interactive.
We
have
to
realistically
turn
it
into
a
view
app
as
well,
which
has
a
lot
more
overhead
and
a
lot
more
thinking
about.
So
we
need
to.
B
We
need
to
figure
out
good
ways
to
do
that,
but
what
I
really
want
to
drive
today
is
these
buttons
right.
So
if
we.
D
B
Attainable
we
can
absolutely
get
there
and
simply
because
our
old
model
right
of
everyone
can
contribute.
So
that's
that's
everyone
within
the
wider
community.
That's
everyone
who
works
at
kit
lab.
That's
just
everyone
right.
Anyone
who's
not
contributed
before
you
could
contribute
a
lot
of
times.
Let's
just
you
know,
the
barrier
entry
is
pretty
low
here.
B
So,
if
you
want
to
contribute
to
these,
there
is
the
view
migration,
epic.
So
this
there's
still
some
potentially
some
issues
left
on
there.
If
you
want
to
pick
up
some
of
the
view
migration
and
help
out
about
that
effort,
there's
also
the
hammer
migration
ethic,
which
has
all
of
the
hammer
ones
that
we
need
to
move
over
and
both
of
these
have
sub
issues
or
somewhere
picks
with
more
issues
and
things
to
pick
up
in
there
and
most.
B
Issues
they
do
just
contain
small
chunks
of
work
right,
so
it's
just
lots
of
small
chunks,
so
they
they're
great
for
first-time
contributors
they're
great,
for
you
know
getting
them
contributions
in
kind
of
thing.
C
Yeah
sam
sam,
do
you
mind
if
I
jump
in
really
quick
and
share
and
show
how
you
might
navigate
the
epic
to
find
available
issues
to
contribute
to.
C
C
All
right,
can
you
see
the
the
slide
once
again
how
to
contribute
awesome
so
I'll
just
per
for
the
slide
here,
let's
say
you
know,
I
went
to
this
epic
link
and
get
epic
is
kind
of
a
high
level
collection
of
issues
you
can
see
in
this
instance.
This
is
for
view,
and
here
you'll
see
this
epochs
and
issues
list.
So
we
have
issues
listed
in
here
and
the
way
this
one
is
broken
down.
C
In
particular,
you
can
ignore
the
percentages
by
for
right
now,
they're
not
updated,
but
you
would
just
choose
one
of
these.
Let's
just
say:
dropdowns
modals
tabs
navigate
into
that
specific
issue
and
you'll
find
it
broken
up
into
other
items,
and
I
believe
these
all
link
to
epics
for
those.
So
if
we
we
saw
okay,
three
of
eight,
let's
click
into
that
epic,
each
epic
should
have
instructions
on
how
to
actually
go
through
the
the
work.
C
So,
as
sam
mentioned,
it's,
it's
really
really
easy
to
to
have
a
like
a
first-time
contribution
or
really
easy
to
just
jump
in
and
do
a
few
of
these
at
a
time
and
and
knock
them
out
pretty
quick.
But
there's
there's
kind
of
instructions,
troubleshooting,
etc
and
then
you'll
see
epics
and
issues.
You'll
see
this
other
list
where
you
can
find
open
issues
and
ones
that
have
been
closed.
C
The
closed
ones
are
great
to
go
through
if
you
know
first
time
as
examples
of
maybe
some
of
the
threads
or
conversation
of
how
somebody
made
the
change
or
just
to
kind
of
look
at
how
some
of
that
was
done
as
an
example
and
then
finally,
you
would
just
click
into
one
of
the
open
ones:
go
ahead
and
and
feel
free
to
assign
yourself
and
and
work
through
it
and
you
know,
create
a
merge
request
off
of
that.
So
I
think
that's
a
quick
overview,
I'll
stop,
sharing
and
back
to
you,
sam.
B
D
B
Too
many
desktops
I'll
share
the
wrong
one.
Yeah
we're
back
on
the
slides
right,
oh
spoiler,
yeah
so
get
pod
is,
is
the
last
thing
I
wanna
talk
about
today,
right
so
gitpods
fantastic.
It
makes
contributing
even
easier
right.
So
a
lot
of
the
the
issues
that
I
heard
from
people
on
on
contributions
in
the
first
place.
B
So
with
git
pod
like
this,
it's
like
a
two-click
install
thing.
It's
it's
really
easy,
I'm
not
going
to
show
you
how
we
do
that
exactly
because,
while
it
is
two
clicks,
the
time
between
click,
one
and
click,
two
is
about
15
minutes,
while
it
loads
all
of
the
things
in
the
background.
B
But
there's
there's
a
video
on
youtube.
I
think
christos
is
gonna
link
the
slides
later
on,
so
you
can
find
that
on
there,
but
what
I
will
show
you
is
if
I've
got
time
the
10
minute
demo
I
showed
last
time-
is
no
five
minute
demo,
thanks
to
thanks
to
github
right
so
I'll
see
if
I
can
get
it
even
lower
than
this.
So
this
is
git
pod
right.
It
looks
very.
D
B
To
vs
code,
if
you've
ever
used
vs
code
and
this
little
window
here-
is
your
local
ish
in
the
cloud,
whatever
you
want
to
say:
dev,
environment
of
gitlab
and
any
changes
we
make
to
these
this
file
here
or
any
of
the
files
over
here
in
our
file
tree
they'll
they'll
get
it'll
get
made
over
here.
So
I
need
to
log
back
in
because
I've
been
logged
out.
B
There
we
go
so
these
are
just
using
the
normal
default
username
and
password
that
you
would
for
any
gitlab
instance
right
it's
root
and
then
five
life.
But
it's
it's.
B
And
things
and,
of
course,
there's
an
error.
This
is
what
I
get
for
live
coding.
B
Will
it
play
nice
way
we
got
away
with
it
so
yeah,
I'm
just
going
to
go
through
this
issue
here
and
we've
got
some
buttons
that
need
migration.
There's
the
majority
of
these.
B
But
this
last
one
still
left
outstanding,
so
we
we
can
just
quickly
do
this
one
right!
I've
prepared
the
file
already.
So
it's
this
file.
We
need
to
look
at
and
it's
one
of
the
wiki
forms.
So
if
I
go
up
to,
if
I
want
to
open
this
in
a
new
window,
so
you
can
see
it
a
bit
better.
B
A
B
It's
a
little
slow
because
it
is
a
local
dev
environment
right,
but
it's
local
in
the
cloud,
so
you
have
to
bear
with
it
a
little
create
first
page
so
yeah
here
we
are,
these
are
the
buttons
we
want
to
change.
So
we
want
to
make
these
the
new
get
my
ui
versions
of
the
buttons,
and
in
this
case
all
we
need
to
do.
Is
these
ones
down
here.
B
This
cancel
button.
Now
we've
got
gl
button
on
it
already,
but
it
actually
needs
to
be
not
button
grouped
and
using
the
button
default,
and
that's
the
same
with
this
one
here.
So
this
one
is
default
and
then
these
success
buttons
yeah
they
are
missing
the
gl
button
class.
Is
this
one
too.
B
B
Like
obviously,
do
a
little
bit
more
inspecting
to
make
sure
it's
right,
but
I'm
trying
to
get
this
done
quickly,
so
I'm
rushing
through
well
yeah,
you
see,
we've
got
them
thick
borders,
you're
doing
it
it's
hard
to
see
on
that
one,
but
it
is
there.
B
So
you
get
your
screenshots
from
here,
create
your
merge
request,
make
sure
you
do
it
in
actual
gitlab,
not
your
local,
dead,
environment
and
normal
see
it
and
you've
got
your
terminal
here.
So
you
can
just
use
the
normal
git
commands.
B
Create
a
branch
add
them
to
it.
I've
got
database
changes
in
there,
so
I
don't
let
them,
but
you
get
the
point:
it's
it's
a
bit
quicker
to
do
it
through
git
put
git
pod.
Then
it
just
do
everything
and
this
it
just
takes
a
couple
of
seconds
to
get
this
to
get
this
started.
We
do
look
at
that
video.
I
have
on
youtube
as
well,
because
a
little
bit
more
in
depth
and
it
doesn't
skim
over
things
as
much
as
I've
done
there.
B
B
Some
tips
for
contributing
again,
we've
just
been
over
it,
but
you
can
use
github
to
set
up
a
local
environment
really
easily
as
I've.
Hopefully
just
shown
you
there.
B
B
You
can
follow
discussions
and
solutions
in
issues
and
merge
requests
again,
as
as
jeremy
mentioned,
look
at
some
of
the
closed
ones
to
see
how
they've
gone
and
and
being
the
right
people
right
so
reach
out
to
someone
on
the
front
end
or
ux
foundations,
team
reach
out
to
myself,
reach
out
to
jeremy,
I'm
gonna,
say
george
as
well,
but
apologies
if
I
shouldn't
have
said
that
george
he's
afraid
he's
very
friendly
he'll
at
least
send
you
to
the
right
person
if
he's
busy,
right
but
yeah
and
and
I'm
happy
contributing
right
like
thank
you
for
listening
and
and
preemptively.
B
Thank
you
for
for
contributing
again,
because
your
contributions
were
super
helpful
last
time,
and
you
know
it's
part
of
what
makes
it
what
makes
gillaf
great
for
me.
So
it's
good
to
see.
Thank
you.
A
A
Thank
you
for
your
time
and
for
people
watching
you
can
find
all
the
information
on
the
hackathon
page.
I've
uploaded
the
recording
and
the
slidex
as
well
as
so
yeah
feel
free
to
check
it
out.
If
you
have
any
questions,
you
can
find
us
on
github
or
you
can
tag
the
appropriate
people
on
the
merge
requests.
A
Yes,
I
will
share
them
on
the
guitar
on
slack,
there
is
a
bridge
between
guitar
and
slack.
So,
if
you
guys
like
guitar
dash
contributors,
that's
a
room,
you
can
throw
them
in
there.
A
Thank
you
folks
wishes
for
a
great
evening
or
rest
of
your
day
in
case
that
you're
in
a
earlier
time
zone.
So
thanks
for
coming
thanks
for
sharing
and
I'll
see
you
all
online.