►
From YouTube: FIRE Collaboration Project-20220202
Description
Bringing awareness to the FIRE Collaborations project - a space for fostering inclusive InnerSourcing Collaboration at GitLab using the FIRE Method: Fast, Inexpensive, Restrained, and Elegant to generate strong value for participants and for GitLab and customers and partners.
A
Good
morning,
good
afternoon,
good
evening,
everyone
welcome
to
this
session
of
cs
skills
exchange.
So
today
we
are
on
fire,
so
you
know,
darwin
is
going
to
you
know,
talk
about.
You
know
fire
collaboration
or
by
the
way
fire
he'll
probably
explain
that
it
means
fast,
inexpensive,
restrained
and
elegant
way
to
generate
strong
value
for
participants,
for
you
know,
git
labs
and
customer
customers
and
partners.
So
without
much
further
ado
I'll.
Let
darwin
go
on
and
tell
us
more
about
the
fire
project.
B
B
I've
already
been
asked
to
promise
not
to
sing
any
of
the
many
popular
songs
with
the
word
fire
in
them.
So
you
won't
be
hearing
me
do
that
right,
but-
and
I
do
get
made
fun
of
by
my
family
by
the
way
I
say
fire,
so
what
maybe
we'll
have
to
have
at
the
end
of
the
round
up
on
exactly
the
proper
way
to
save
fire.
B
B
All
right
lots
of
interesting
ideas
so
we're
we.
We
all
know
that
edison
is
well
known
for
creating
the
light
bulb
and
he
created
the
light
bulb,
and
we
think
of
that
as
a
seminal
an
incredible
moment,
and
it
definitely
was
notably,
he
had
tried
hundreds
of
different
ways
to
create
a
light
bulb
and
failed,
and
this
was
his
final
success,
and
so
we
we
see
the
beginnings
of
the
concept
of
iteration
and
building
forward
already
in
in
innovation
innovation
culture.
At
this
time
now.
B
One
of
the
things,
though,
that
was
interesting
to
me,
was
that
edison
went
on
to
do
something
incredible
in
order
to
meet
his
own
internal
measure
of
a
successful
solution,
so
he's
holding
his
hand
there
a
successful
solution,
but
no
one's
going
to
be
able
to
use
it.
Does
anyone
know
why,
at
the
moment
of
invention,
why
no
one
is
going
to
be
able
to
use
it?
Ac.
B
Getting
closer
there,
but
the
answer
is
there
was
no
electrical
grid,
so
the
light
bulb
was
created.
Absolutely
no
electrical
grid
and
edison's
internal
meter
of
have
I
created.
A
successful
solution
was
adoption,
so
he
has
a
light
bulb.
No
one
can
adopt
it
because
there's
no
electrical
grid,
so
he
does
the
obvious
and
simple
thing
of
building
an
entire
electrical
grid
system
and
wiring
up
part
of
his
campus
and
then
parts
of
various
cities
in
the
u.s
to
start
to
get
sponsorship.
B
So
if
you
think
about
the
creation
electrical
grid
system,
that
alone
is
a
massive
undertaking,
but
it
was
what
he
needed
in
order
to
get
to
his
measure
of
solution
success.
It's
a
side
point
that
it
what
the
system
he
created
was
not
the
one
we
have
in
place
today,
but
he
did
make
this
massive
commitment
to
make
sure
this
could
be
adopted.
B
So
I
want
to
make
a
connection
here
between
what
I
feel
is
a
solid
connection
between
solutions
and
innovation.
So
solutions
are
a
unique
and
self-contained
answers
to
a
problem
or
challenge,
so
they
pose
an
answer.
It's
usually
unique,
which
would
make
it
either
net
new
or
innovative
over
a
previous
answer
and
they're
self-contained.
So
solving
generally
means
you
catch
all
the
key
attributes
in
whatever
you're
presenting
that
need
to
be
covered.
B
As
far
as
addressing
that
problem
or
challenge
now,
there's
a
book
called
they
made
america
and
in
this
book
they
have
a
very
interesting
section,
and
I'm
just
going
to
read
through
this.
Even
though
I'm
breaking
my
own
rule
about
reading
slides
innovation
is
not
simply
an
intention.
It
is
inventiveness
put
to
use.
Herbert
boyer
was
not
content
with
splicing
a
gene
in
a
university
laboratory.
He
risked
academic
odium
by
going
into
business
to
mass-produce
man-made
hormones.
B
Cirrus
mccormick
was
not
the
only
farmer
to
invent
a
reaper,
but
he
was
the
only
one
who
intimidated
imitated.
The
financing
mechanism
made
it
possible
for
hundreds
of
thousands
of
farmers
to
afford
the
invention.
The
sorely
neglected
genius
of
radio
edwin
armstrong
went
to
the
marketplace
for
himself
rather
than
see
his
invention
of
fm
radio
shelved
by
rca's
desire
to
maintain
its
income
stream
from
am
radio
ida.
B
This
book
talks
about
the
many
many
male
and
female
inventors
from
the
period
of
the
steam
engine
to
the
search
engine
and
how
they
operated
in
what
ways
they
were
similar
in
what
ways
they
were
different
but
you'll
notice
here.
The
book
that
creates
a
very
strong
correlation
to
successful
innovators
are
all
about
adoption,
so
they
have
to
create
valuable
results
that
are
new
and
awareness
to
enable
adoption.
B
There
are
examples
of
people
who
are
more
purely
theoretical
or
academic
after
alexander,
graham
bell
was
credited
with
inventing
the
telephone.
It
was
found
that
there
was
another
inventor
who
had
it
working
almost
identically
in
his
own
home,
but
had
no
real
interest
in
market
adoption,
so
he's
more
of
a
of
a
theoretical
or
what
the
book
calls
an
inventor
versus
an
innovator.
So
this
is
something
I
really
strongly
connect
with,
and
I
think
you'll
see
it
kind
of
reflected
in
the
thoughts
about
an
opinion,
an
opinionated
way
to
approach
collaboration
on
solutions.
B
B
So
if
we
had
a
model
that
could
strike
something
in
the
middle,
so
if
you
can
think
of
it
as
a
collaborative
raw
materials,
if
you
have
a
group
of
folks
who
want
to
collaborate,
if
general
collaboration
is
kind
of
this
starting
point,
we
have
some
raw
materials
that
we
can
deal
do
some
stuff
with.
Then
a
fire
collaboration.
Starting
point
might
look
like
this.
B
We
have
some
frameworking
that
kind
of
gives
some
guidelines
about
how
to
go
about
it
and,
but
also
doesn't
over
prescribe
what
the
final
result
is
going
to
look
like.
I,
I
had
a
challenge
even
picking
this
picture,
because
obviously
this
is
a
big
utility
building,
not
a
home.
I
tried
to
find
a
picture
where
you
couldn't.
C
B
So
another
way
to
just
articulate
or
define
kind
of
the
target
here
is
that
fire
collaborations
are
one
so
they're
one
collaboration
model.
This
is
not
meant
to
subsume
all
collaboration
models
or
be
the
sum
total
of
all
collaboration,
but
it's
one
just
enough
opinionated
collaboration
model
and
I
would
call
it
an
evolving
experiment.
So
kick
this
off
play
with
it
a
bit.
We
have
a
couple
successes,
but
it
can
definitely
be
morphed.
Both
the
content,
as
well
as
the
structure
as
more
folks
participate
if
they
wish
to
for
creating
solutions.
B
So
it's
targeting
solutions
since,
as
we
move
through
you'll,
see
that
I
I
mean
a
specific
concept
with
with
the
concept
of
solutions
by
leveraging
a
stewardship
oriented
working
agreement.
So
one
of
the
core
problems
with
regular
collaboration
is
it
kind
of
falls
apart,
because
no
one
keeps
the
ball
rolling.
So
we
want
to
try
to
incorporate
something
to
help
with
that
between
any
set
of
temporary
collaborators.
So
we
all
need
to
collaborate
within
our
groups
at
get
lab
around
business
requirements
and
needs.
B
But
this
is
kind
of
the
the
meta
layer,
the
the
shifty
layer,
the
3ms
steel
time,
to
do
your
own
pet
project
kind
of
collaboration.
So
the
idea
is
that
we
can.
We
can
get
together
in
groups
that
are
cross-functional
across
team
to
iterate
on
solving
a
problem,
so
we
use
our
strong
values
of
iteration
by
generating
and
radiating,
and
so
I
do
find
that
a
lot
of
collaborations.
B
This
is
the
part
where
some
challenges
come
about
either
ineffective,
radiating,
no
desire
to
radiate
or
the
inability
to
find
proper
ways
to
radiate
valuable
results
for
collaborators.
So
this
is
another
interesting
piece.
We
can
frequently
leave
out
that,
although
we're
trying
to
generate
value
for
a
certain
beneficiary
or
stakeholder
of
what
we're
trying
to
solve
for
the
collaborators
really
ought
to
have
value
coming
out
of
it
as
well.
Otherwise
they
tend
to
drop
out
if
not
and
get
lab
customers,
partners
and
communities.
B
So
all
of
our
stakeholders,
now
not
every
collaboration
and
general
collaborations-
has
to
be
driving
toward
customer
partner
and
community
value.
But
I
find
it
much
more
fulfilling
and
I
really
enjoy
that
aspect
of
being
a
solutions.
Architect
at
gitlab
that
it
does
connect
to
solid
value
for
the
gitlab
community
and
then
designed
with
executed,
designed
and
executed
with
adoption
in
mind
so
making
adoption
the
actual.
How
adoptable
are
the
results
and
how?
How
well
radiated
are
the
results
so
that
we
can
make
sure
adoption
has
a
chance
of
happening.
B
So,
as
usual,
the
ideas
for
this
did
not
come
solely
from
my
own
thinking,
but
I
stole
from
some
books.
So
we've
already
mentioned
the
one
book
fast,
inexpensive,
restrained
and
elegant
methods,
ignite
innovation,
and
this
particular
book
is
based
on
the
observation
that,
contrary
to
what
we
sometimes
think,
we
think
if
we
keep
the
specs
simple,
we
keep
the
process
simple,
that
what
we'll
result
with
is
a
simplistic
result
that
has
limited
flexibility
and
the
main
core
tenet
of
the
book
is.
B
The
opposite
is
frequently
true
that
by
keeping
things
tight,
we
frequently
end
up
with
something
that
is
much
more
flexible
than
we
actually
expected,
because
we're
not
over
articulating
it
to
a
given
purpose,
and
the
the
book
adds
some
clarity
to
what
it
means
by
these
things.
So
fast
is
not
hasty.
B
We
you've
all
heard
how
some
people
treat
agile
as
speed,
speed,
speed,
faster,
faster,
but
agility
is
actually
speed
with
high
high
coordination,
high
responsiveness,
inexpensive,
but
not
cheap,
restrained,
basically
not
keeping
things
as
short
as
possible,
but
not
shorter
in
terms
of
meetings,
time
spent
documentation
and
then
elegant,
innovative
and
fit
to
purpose
simplicity.
So
it's
simple
but
still
very
well
fitted
to
the
purpose.
B
D
B
B
This
book,
actually
at
the
in
the
last
chapters,
has
some
concepts
of
how
to
make
internal
ideas
more
executive
to
qualify
and
to
work
with
internal
ideas
to
make
them
into
valuable
results
in
a
more
light,
structured
way
than
kind
of
the
idea.
Bin
way
and
the
one
of
the
main
things
that
calls
out
is,
the
idea
of
bin
way
is
soliciting
for
solutions.
B
B
B
I
actually
end
up
attracting
others
who
have
already
recognized
that,
and
this
this
happened
very
much
in
the
one
we'll
be
talking
about
the
jwt.
I
d
c
collaboration
that
joe
and
brad
participated
in.
They
both
had
a
much
stronger
sense
of
the
demand
than
even
I
did,
and
so
it
was
really
cool
to
have
them
opt
in
with
what
they
what
they
thought
notice
here,
too.
B
Qualitative
data
is
fine,
so
again
making
this
lighter
than
the
concept
of
hey
we're
going
to
mount
up
a
new
department
or
a
new
feature
in
the
product,
or
something
really
requires
a
lot
of
commitment.
So
we
want
a
lot
of
quantitative
data
around
whether
it's
really
necessary.
So
in
this
case
we
can
be
a
little
lighter
because
we're
doing
collaborations
we
target
business
valuable
results.
B
Responsibilities
is
another
way
to
show
that
you're
moving
forward
that
you're
delivering
and
that
maybe
you
are
ready
for
for
the
next
level
in
your
role,
a
value
radiation
plan,
so
right
from
the
get-go
for
it
to
be
adopted,
we
need
to
be
able
to
radiate
that
value,
and
so
what
are
some
of
the
things?
We're
going
to
do?
You'll
see
that
in
the
issue
template
there's
a
lot
around
internal
and
external
social.
B
Some
of
the
things
I
don't
have
in
the
issue
template
is
like
there's
some
places
that
in
cs
among
solutions,
architects,
we
track
collateral,
you
can
edit
add
it
there.
I'm
part
of
something
called
aws
community
builders,
and
I
have
to
track
public
collateral
that
I
create.
That
supports
aws
community,
so
they
have
a
tracker,
so
I
have
to
go
in
there
and
enter
that.
So,
however,
the
value
radiation
plan
works
and
you
can
create
custom
things
you
might
know
of
places
to
radiate
it
that
are
not
not.
D
B
B
Sometimes
surprisingly-
and
sometimes
we
write
these
off
well,
I
didn't
intentionally
plan
those
results,
so
I
can't
count
them,
but
in
reality,
when
you
think
about
the
whole
field
of
innovation,
sometimes
that's
actually
the
seminal
piece
of
it.
It's
the
the
core
one.
So
there's
two
examples:
I
decided
those
serendipities
were
the
core
value.
B
They
don't
have
to
be
just
a
core
value,
though
very
likely,
if
you
generate
something,
that's
innovative.
You
end
up
with
several
attributes
of
it
that
you
weren't,
expecting
that
you
see
how
they're
helpful
and
because
approaching
things
with
this
fire
kind
of
concept
is
what
ends
up
causing
those
to
emerge.
It
is
really
you're
intending
to
have
these
happen,
even
though
you
can't
pre-plan
what
they'd
be.
B
B
B
It's
got
a
bit
of
an
elevator
pitch
and
some
more
additional
details
since
we're
going
through
a
lot
of
this.
I
won't
go
through
it
right
now.
It's
going
to
take
you
into
the
issue
board,
which
is
basically
they're
just
each
an
issue,
and
first
I
want
to
take
you
through
this
one.
That's
kind
of
the
intended
target
and
oh
it's
enclosed,
so
build
and
test
across
architecture
containers
with
docker
build
excellent,
get
lab
runners
on
aws
you'll,
also
notice
that,
from
my
perspective,
there's
a
bunch
of
really
cool
things.
B
They'd
like
to
do
that.
I
don't
have
time
for,
and
I
tend
to
put
those
out
as
far
collaborations
and
so
in
a
way
I'm
trying
to
rope
in
some
additional
value
for
my
specific
area
at
gitlab,
just
because
this
is
where
my
head
constantly
is.
So
a
lot
of
mine
have
to
do
with
aws
and
or
alliance's
type
motions.
B
So
within
this
particular
one,
someone
asked
a
question
on
slack.
Somebody
needs.
I
think
it
was
victor
hernandez,
that
someone
needs
power,
pc
containers,
but
we
can't
how
do
we
get
git
lab
running
on
power
pc
and
I
quickly
responded?
Oh
yeah,
you
can't
do
that
because
the
architecture
is
different
and
then
I
was
like
wait
a
second.
I
didn't
really
validate
that
answer
before
I
posted
it.
B
So
I
went
and
looked,
and
I
discovered
something
called
docker
build
x
and
build
x,
uses
a
feature
of
linux
so
that
you
can
build
a
power
pc
container
on
top
of
an
x86
machine
and
those
kind
of
things.
So
I
posted
this.
I
posted
an
initial
just
how
to
get
docker
build
x
installed
on
amazon,
linux
machines.
I
thought
now
to
make
a
great
working
example.
B
A
guy
guided
exploration
and
a
great
extension
to
an
existing
one
that
does
scaled
runners
on
amazon
already,
and
I
happen
to
be
talking
to
jefferson
and
he
mentioned
hey.
I
I've
been
playing
with
that
too,
and
so
I
asked
him
if
he'd
be
interested
in
doing
this.
We
put
this
up
here
and
in
about
four
hours
we
were
able
to
refactor
my
simple
instructions
based
guided
exploration
into
a
working
example,
and
then
we
also
took
a
dependency
on
this
other
fairly
large
working
example,
which
is
a
scaling
runner
vending
machine
for
aws.
B
Since
it
was
designed
to
be
modular,
we
were
able
to
create
a
plug-in
script
that
could
create
the
kind
of
runner
that
could
process
these.
So
the
business
value
for
this
ends.
Up
being
that,
let's
say:
you're
generating
x86
container
images
or
even
power
pc
images.
You
could
use
amazon's,
cheapest
graviton
3
arm
runner
fleet
to
build
containers
for
those
other
operating
systems.
You
can
also
build
system
390
containers,
so
you
can
not
use
a
potentially
very
specialized,
compute
or
more
expensive
compute
that
you
would
use
in
production.
B
You
can
in
develop
dev
where
you're
doing
hundreds
of
container
builds
a
day
or
a
month
or
whatever.
You
could
use
much
cheaper,
scalable
compute
to
build
the
target
architecture
that
you
need,
or
a
target
architecture
that
you
can't
even
get
as
a
gitlab
runner,
assuming
you're
running
on
containers
on
that
target
architecture.
B
So,
in
about
four
hours
we
were
able
to
get
this
running.
It
took
several
more
hours
to
finalize
the
changes
to
both
of
these
projects
and
then
jefferson
was
able
to
take
the
social
media
evangelism
training
and
to
post
about
it
on
social
media
to
to
try
to
get
it
out
to
the
word
out
so
to
speak,
and
I
think
jefferson
had
another
commitment
today,
so
he's
not
able
to
attend
with
us
today.
But
you
can
ask
him
about
his
experience
working
through
with
this.
So.
B
The
next
one
I'm
going
to
go
through.
Oh,
let's
go
down
here,
real
quick
just
for
a
few,
and
only
at
the
beginning
of
this
program,
I've
been
doing
what
I
call
tracing
an
impact
map.
How
did
the
collaboration
proceed?
Who
got
involved
what
assets
were
generated?
What
the
collaboration
issue?
What
did
it
plan
to
make
and
what
happened,
and
so
I'm
going
to
go
through
one
on
the
next
one,
but
this
part
of
it
is
not
something
you
would
have
to
do.
It's
more
just
me
experimenting
with
trying
to
qualify.
B
B
If
you,
when
you
see
these
maps,
if
you
go
in
and
take
a
look,
if
you
click
on
this
detailed
one
when
you
get
in
here,
these
links
are
clickable,
because
this
is
svg
it's
zoomed
in
so
you
got
to
zoom
around
a
bit
yourself,
and
so
this
zoomed
out
view
is
rendered
as
a
png.
So
the
links
are
not
clickable
in
it
and
let
me
just
go
into.
I
have
another
view
of
it,
which
is
in
visual
studio
so
that
I
can
get
into
more
detail.
B
So
originally
the
way
this
got
touched
off
was
amazon
announced
in
hacker
news
that
they
could
do
this
kind
of
authentication.
So
an
individual
github
action
could
authenticate
into
amazon
and
you
can
map
the
entities,
so
you
can
have
a
finer
security
mapping
so
that
one
job
only
has
the
permissions
you
intend
to
have
in
amazon.
So
it's
the
the
best
way
to
do
runner,
authentication
into
target
environments.
B
So
at
that
point
I
was
called
in
because
I
had
to
do
with
aws,
and
so
I
put
did
a
post.
That
said,
we
can't
I'm
not
sure
if
we
can
do
that
yet,
but
we
can
do
it
this
other
way
and
then
at
that
point
I
created
a
fire
collaboration.
Just
to
try
to
understand
you
know.
Is
this
something
that's
really
needed?
I
know
it's
needed
I've.
I
know
that
just
from
the
concepts
involved
it's
important
and
then
it
turned
out
that
joe
randazzo.
B
We
were
talking-
and
I
mentioned
this
to
him-
and
he
got
excited
about
it
because
he
had,
in
his
experience,
seen
a
lot
of
customers
asking
for
it
so
joe
and
I
decided
to
go
ahead
and
turn
this
collaboration
on
and
we
defined
the
things
that
we
would
try
to
generate
as
we
went
through.
A
working
example
is
a
big
theme
of
mine
in
everything,
and
so
a
working
example
was
targeted.
B
The
the
first
iteration
that
we
agreed
to
do
was
that
joe
would
try
to
figure
out.
Can
we
already
do
this,
and
actually
that
was
the
seminal?
That
was
a
seminal
idea
that
the
jwt
token
may
already
be
usable.
All
we
need
to
do
is
create
enablement,
so
create
some
blog
posts
and
working
examples
and
we're
done,
but
it
turned
out
joe
discovered
that
that's
not
all
that
we
needed.
B
We
actually
had
some
an
existing
issue
that
would
need
to
be
resolved
and
and
figured
out
and
worked
in
order
for
this
to
happen.
At
that
point
too,
I
also
reached
out
to
amazon
and
we
established
a
collaboration
and
they
got
the.
This
was
a
happy
happenstance,
but
they
got
the
exact
s
authentication
specialist
sa
who
helped
build
the
github
version
of
this.
B
B
So
brad
got
interested
and
excited
to
the
point
that
he
created
a
new
mr
and
started
playing
around
with
how
to
get
the
code
working
and
he
actually
got
an
entire
gitlab
server
running
inside
of
git
pod,
which
I
had
no
con
idea
that
you
could
do
and
he
started
working
this
and
so
then,
as
we
realized
hey,
this
would
have
to
be
accepted
by
product
victor
nagy
and
krasmir.
Who
would
have
done
some
of
the
original
production?
B
B
We
also
defined
documentation
and
enablement.
So
you
can
see
here
that
the
working,
the
guided
explorations
are
enablement
and
they're
ready
very
early
in
this
whole
process.
It
still
took
some
months
and
then
so
eventually
joe
put
in
an
mr
created
documentation
for
aws
and
some
overall
documentation,
but
then
three
on
our
incubation
engineering
team.
I
was
talking
with
the
senior
google
engineer
and
I
believe
that
atif
had
some
interaction
with
this
as
well
from
the
alliance's
team.
B
So,
basically,
the
concept
of
this
map
is
to
show
kind
of
how
it's
really
retrospective.
How
does
organic
collaboration
usually
happen,
but
how
can
we
kind
of
put
a
little
bit
of
light
structure
over
it
to
touch
the
match,
so
to
speak,
to
light
it
on
fire
and
ignite
that
this
would
get
moving
and
keep
moving?
B
In
this
case,
it
snowballed
out
of
an
effort
just
to
do
enablement,
but
it
ended
up
being
that
we
all
wanted
to
keep
moving
with
it
and
keep
keep
it
moving
and
I'd
ended
up
being
an
enhancement
to
a
product.
So
that's
a
fairly
full
example,
and
this
is
still
somewhat
underway,
and
it
is
not
quite
as
super
fast
as
the
four-hour
one,
but
at
the
same
time,
for
everything
that's
being
generated
and
how
complete
the
picture
will
be.
It
is.
D
Yeah,
it's
interesting
and
thanks
for
the
detailed
map
as
well,
so
a
couple
of
things,
I'm
not
a
coder.
I
actually
don't
even
know
anything
about
ruby,
but
I
have
a
contribution
to
gitlab
the
product
and,
I
think
that's
kind
of
cool.
At
least
my
name's
tied
to
it.
The
cool
part
is
is
like
I,
those
mrs
seem
to
be
at
most
20
code
and
80
management
like
project
management
or
feature
manager.
Whatever
you
want
to
call
it
chasing
down
people
getting
collaborators
getting
opinions.
D
I
asked
other
people
to
write
the
code
for
me
right
so
kraus
who's
on
the
back
end
team
a
lot
of
times.
They
don't
have
time
to
do
the
full
thing.
So
if
you
look
at
the
mr,
which
is
probably
linked
somewhere
in
there,
it
started
in
october
mid-october-
and
that
was
after
the
idea
was
kind
of
already
discussed
and
what
we
were
going
to
do
and
it
just
merged
into
products
last
last
month.
So
it
does
take
a
while.
D
D
It's
you
know,
potentially
a
security
review,
all
those
things
chasing
down
those
people,
that's
the
time
they
don't.
They
don't
have
the
guy
who
wrote
the
code
craz,
you
know,
or
at
least
the
majority
of
it
it
probably
he
probably
busted
it
out
in
five
or
ten
minutes
like
on
his
local
machine.
He
just
said:
hey
here's
some
code,
right,
okay,
cool!
Let
me
just
pop
that
into
a
c
into
into
git
lab
into
into
a
branch
run.
D
Ci
got
some
errors,
change
a
couple
things
until
the
errors
go
away
and
start
collaborating
with
approvers
and
and
people
that
want
to
have
an
opinion
on
it.
So
there
it
does
take
a
little
bit
of
time,
but
it
doesn't
always
take
every
skill
set.
So
I
think,
if
you're
hesitant
to
say
you
know,
I
don't
know
ruby
or
I
don't
know
the
product
or
I
don't
know
these
things.
I
think
we
we
you're
you're
underestimating
what
it
takes.
I
think
you
can
very
easily
figure
out.
D
You
know
you
start
chasing
down
and
asking
questions.
We
have
a.
We
have
a
leg
up
on
the
community
with
the
ability
to
internally
slack
people
saying
hey,
can
you
take
a
look
at
this
or
if
you've
got
a
few
minutes,
blah
blah
blah
and
then
darwin
did
a
shout
out
for
git
pod?
I
thought
that
was
so
cool
that
I
could
just
basically,
if
you
create
an
mr
which
creates
the
branch,
we
know
how
that
works,
and
you
say
open
in
git
pod
with
a
little
bit
of
tweak.
Not
too
much
you.
D
Can
you
basically
have
your
own
sandbox
version
of
gitlab
and
you
just
start
changing
code
and
gitlab
changes.
So
if
you
see
something
a
lot
of
times,
we
can
kind
of
get
to
the
spot
in
the
code
and
go.
You
know
what
it
just
but
just
said
this
or
that.
But
I
don't
know
how
to
test
it.
Gitpod
does
all
of
that
stuff.
D
You
know
without
all
the
long,
ci,
cd
pipelines
and
everything
so
really
interesting,
to
be
able
to
use
that
as
a
very
fast
way
without
having
to
download
and
do
a
bunch
of
stuff
like
get
the
gdk
running
locally
and
all
the
things
that
yeah,
you
know
takes
a
a
long
time
so
development
environments
as
a
service,
which
is
what
git
pod
does
and
since
our
project's
open
source,
we
get
a
large
amount
of
time
in
that
service
for
free,
it's
pretty
neat.
So
that's.
B
Brad,
actually
I'll
ask
we
defer
questions
till
the
end.
If,
if
we
have
time
also,
I
just
want
to
point
out
that
the
intent
this
was
an
unusual
one,
that
it
spiraled
or
snowballed
into
product
and
and
length
of
time,
and
that
kind
of
thing
is
not
an
intention,
but
we
all
wanted
to
keep
going
with
it
and
see
it
through.
For
for
the
customer
and
partner
benefits
joe.
Can
you
give
us
a
little
bit
of
perspective.
C
Yeah
and
I
was
gonna
reply
to
what
brad
was
saying
a
little
bit,
there's
a
lot
of
interesting
things
to
watch
so
brad
was
taking
a
lot
of
the
coding
there
and
his
ability
to
kind
of
pull
in
different
folks.
It
was
really
interesting
to
see
that
and
also
inspiring
to
see
kind
of
that
that
work,
because
everyone
was
so
willing
to
contribute.
C
D
B
B
B
Pac
area
has
been
working
on
this
to
get
it
to
see
to
qualify
that
answer
and
to
make
contributions
back
to
those
projects.
He's
got
an
excellent
enablement
headset
when
he
creates
detailed
how-to
instructions,
so
he's
also
able
to
very
articulately
talk
to
hey
customers
who
are
doing
this
for
the
first
time
ever
are
not
going
to
get
it
because
of
xyz,
and
so
you've
been
giving
some
of
that
feedback.
B
B
Yesterday:
who's
like
man,
we've
got
this
two
massive
mono
repos
and
when
we
were
talking-
and
we
had
someone
from
the
quality
team
on
it
sounds
like
pac
object,
cache
might
help,
but
in
amazon
instances
there's
a
specific
local
ssd
storage
capability,
which
would
then
make
that
cache
blazing
fast.
So
we're
wondering
can
that
make
this
like?
Can
we
give
numbers
to
show
it
substantially
better
and
the
scalability
team
recently
put
out
a
blog
that
talks
about
the
pack
object
cache
in
general,
but
not
necessarily
putting
on
hyper-converged
storage?
B
B
I
also
wanted
to
point
out
a
couple
here
these
templates,
so
a
couple
of
these
I'm
putting
out
here
as
if
you
want
to
a
one-time
micro
mentorship
and
I'm
actually
gonna
put
a
micro
mentorship
label
on
here
land
a
conference
speaking
opportunity.
So
you
won't
learn
how
to
do
that.
I'm
willing
to
help
you
with
that.
You
make
a
copy
of
this
template
and
create
a
new
one.
If
you
I
can
talk
about
why
I
don't
use
issue
templates
at
another
time
and
then
qualify
for
database
community
builder
program.
B
So
if
you
want
to
be
in
this
program,
this
particular
issue
outlines
the
benefits
and
all
that
you
can
make
a
copy
of
this
and
paste
it,
and
then
we
can
collaborate
on
it.
So
you
can
see
kind
of
the
a
lot
of
these
are
quite
lightweight
they're.
Not
all
you
know
really
heavy
heavyweight
kind
of
things
for
you
to
participate
in
okay
and.
B
Just
want
to
talk
a
little
bit
about
so
so.
We've
talked
about
the
positivist
model
of
what
are
some
of
the
things
we
can
do
we'll
talk
a
bit
about
what
are
some
of
the
things
that
are
potentially
avoided
by
this
approach.
There
might
be
other
ones
too,
if
you
all
have
had
any
great
thoughts
about
hey.
This
would
be
even
ten
times
better
if
you
did
acts,
I
so
totally
want
to
hear
those
so
definitely
interact
with
me
on
those,
but
some
of
the
things
that
can
be
avoided
are
valuable.
B
Results
frequently
aren't
clearly
targeted
in
the
first
place,
with
the
collaboration
they
aren't
targeted
for
participants.
So
if
participants
aren't
getting
something
out
of
it,
it's
a
voluntary
thing
so
that
results
in
drop
off.
If
there's
not
value
in
it,
for
them,
they
aren't
always
tracked,
and
although
we
don't
want
to
go
crazy
tracking
and
if
you
want
to
do
a
collaboration,
that's
not
even
this
structured
well,
then
obviously
you're
free
to
do
that.
B
One
thing
I
guess
I
didn't
show
too
well
is
here's
the
career,
valuable
goals
that
any
individual
can
grab
and
drop
into
their
profile
and
joe
is
on
the
track.
He
took
the
social
media
certification
which
is
required,
and
then
once
we
get
this
in
a
position
where
he
feels
good
about
radiating,
he
can
post
it
to
lincoln
and
to
get
lab
social,
and
so
this
little
template
here
I
have
a
whole
bunch
of
other
places
I
radiate
to,
but
it
gives
at
least
a
basic
template
of
where
you
can
radiate
value
to.
B
Also
silo
breaking
so
the
best
insights
can
come
from
any
git
lab
team
member.
It
doesn't
have
to
be
team,
bounded,
cross
group,
recognition
and
aggregation
for
need
or
demand,
including
qualitative,
potentially
lighten
the
load
on
special
kinds
of
collaboration.
So
internship
is
a,
in
my
opinion,
a
special
kind
of
collaboration,
but
it
also
tends
to
be
heavy
lift
for
both
sides,
so
this
can
accommodate
potentially
a
micro
internship.
B
B
It's
a
more
open
thing
with
less
structure
and
that's
there's
always
a
place
for
that
kind
of
thing,
but
this
could
also
be
used
for
a
micromentorship
like
I
showed
about
hey,
get
a
get
get
into
this
program
or
or
get
a
speaking
gig
and
then
continuous
skills
growth.
So
we
all
have
ways
we
want
to
grow
our
skills
or
we
don't
even
know
how
to
grow
our
skills.
So
by
perusing
through
existing
and
past
collaborations,
you
might
get
some
ideas
for
how
to
grow
your
career.
B
And
then
what
fire
collaborations
are
not.
It
does
not
attempt
to
redefine
the
nature
of
all
collaboration,
only
to
opinionate
it
in
a
valuable
way.
It's
not
a
rigid
structure,
as
we
touched
on
earlier.
So
if
there's
ways
in
which
you
get
into
that
issue
and
you're
like
wow,
we
create
a
lot
more
value
by
having
a
whole
new
different
kind
of
section
that
I've
never
conceived
before
put
it
in
and
it
is
really
valuable.
You
know
see
about
getting
it
into
the
issue.
Template
that's
not
limited
to
technical
roles
or
activities.
B
B
B
Well,
maybe
a
working
example
would
work
better.
Then
you
can
just
cite
a
one-on-one.
Send
that
out
to
the
customer
participate
in
the
collaboration.
Ask
someone
to
mentor
you
in
a
highly
defined
collaboration.
So
maybe
you
have
some
ideas
of
how
you
want
to
grow.
You
ask
them
to
mentor
you,
but
you
use
fire
collaborations
too,
to
show
that
show
the
mentor
kind
of
the
the
structure
that
you
want
to
to
use.
If
it's
useful
to
you.
B
So
that
is
basically
the
the
sum
total
of
what
I
was
going
to
talk
about
today.
I'm
hoping
that
you
can
see
that
we've
been
able
to
generate
some
valuable
results.
The
success
of
moving
this
forward
and
growing
it
is
going
to
be
organic
out
of
the
alliance's
team,
we're
we're
trying
to
say,
hey
here's
a
model
that
seems
to
be
working.
We've
done
the
initial
testing
if
you'd
like
to
participate,
we're
all
ears
in
all
arms.