►
From YouTube: Lecture Open Source Contributions
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
I'm
sean
carroll,
I'm
an
engineering
manager
at
gitlab
in
the
source
code
group
and
today
we're
going
to
talk
about
open
source
software
or,
as
it's
more
commonly
known,
fos.
So
we're
going
to
talk
about
what
is
fos.
What
are
the
various
fos
license
models
which
companies
for
us
and
contribute
back
to
it?
A
Why
should
I
contribute
to
open
source?
Why
should
you
contribute
to
open
source
and
how
to
contribute
to
open
source
at
gitlab?
So
what
is
foss
foss
is
free
and
open
source
software.
It's
software
where
that
is
both
free
and
open
source
software,
where
anyone
is
freely
used,
licensed
to
use
copy,
modify
and
work
with
the
software
in
any
way
you
have
access
to
the
source
code.
You
can
change
it
and
you
in
fact,
you're
encouraged
to
voluntarily
improve
the
design
of
the
software.
A
False
licence
models,
there
are
many
different
software
licenses
available
in
foss
and
they
actually
represent
different
points
of
view
or
philosophies.
Even
in
general,
there
are
two
broad
categories:
copy
left
and
permissive,
even
something
to
note
that,
even
if
the
software
is
given
away
for
free,
it
is
still
covered
by
a
license.
It
is
still
essentially
owned
by
somebody
it's
important
to
understand
what
license
you
are
working
with
and
what
are
the
rules,
particularly
if
you're
planning
to
take
that
into
some
type
of
business
environment.
A
Copy
left
licenses,
so
this
is
a
bit
of
a
joke
or
a
play
on
words
on
the
word.
Copyright
copy
left
takes
the
philosophy
that
software
should
be
free
and
it
should
not
pay
for
it,
so
it
actually
takes
such
a
strong
approach
that
any
software
that
is
derived
from
the
software
that
you
have
taken
from
a
foss
project.
A
A
There
are
no
restrictions
on
selling
services
built
on
copyleft
code
and
in
fact
this
is
a
very
common
business
model.
So,
under
this
type
of
model,
a
company
will
take
one
or
more
pieces
of
software
that
has
been
developed
by
a
copylift
project
and
sell
it
sell,
not
sell
the
software
itself
but
sell,
sell
the
services
and
sell
support,
perhaps
for
the
software-
and
this
has
been
a
very
successful
business
model
for
many
companies.
A
Some
examples
of
copyleft
licenses
are
the
most
common.
One
is
gpl,
and
it's
derivatives
like
a
ferro
gpl
mozilla,
who
make
the
firefox
browser
also
have
a
well-known
license,
called
the
mozilla
public
license
and
then
for
things
that
are
not
actually
software
so,
for
example,
photographs
or
wikipedia
pages
they
might
be
covered
by
something
called
the
create
commons.
Sharealike
license
it
works
in
the
same
way.
Anything
that's
derived
from
that
product
must
also
be
shareable
for
anyone
else
to
use.
A
So
if
that
doesn't
suit
you,
the
permissive
licenses
may
be
more
user
friendly
for
a
business.
Permissive
licenses
allow
the
user
to
use
the
foss
code
for
free
and
really
do
anything
with
it.
You
can
modify
it.
You
can
redistribute
it.
You
can
sell
the
software
you
can.
You
can
fork
the
software
and
make
a
different
product
from
that
original
software,
and
you
can
essentially
do
what
you
want
with
it.
So
this
is
sometimes
called
the
anything
goes
license.
A
A
A
Open
core,
okay,
so
git
lab,
uses
a
combination
of
both
open
and
closed
licenses.
This
approach
is
called
open,
core
and
I'll.
Just
emphasize
it's
not
a
license.
It's
it's
an
approach,
so
gitlab
essentially
have
two
products:
there's
git
lab
ce,
which
is
the
community
edition,
and
this
is
fully
open
source
and
then
on
top
of
the
ce,
is
built
gitlab,
ee
or
enterprise
edition,
which
is
closed
source.
A
So
this
is
also
becoming
a
more
common
model
for
companies
and
it's
a
way
where
companies
can
still
engage
with
the
open
source
community
and
you
can
use
the
gitlab
ce
product
and
many
projects
use
it
completely
for
free-
and
it
is,
you
know,
quite
a
powerful
product,
it's
most
of
the
gitlab
product
and
then
for
those
enterprise.
Customers
who
want
special
features
they
can,
they
can
buy.
The
enterprise
edition,
which
is
paid,
users
can
see
the
issue
tracker
and
they
can
contribute
to
to
either
stream
of
code.
A
So
let's
just
talk
about
that,
because,
if
you're
an
open
source
contributor,
of
course,
it
makes
sense
to
contribute
to
the
open
source
platform
if
you're
contributing
to
a
closed
source
product.
Why
would
you
do
that?
A
Well,
in
fact,
gitlab
has
many
customers
who
do
do
that
and
they'll
have
teams
of
people
who
are
working,
who
have
access
to
the
code
of
course,
and
then
they
will
submit
an
improvement
to
the
product
or
some
feature
that
they
would
like,
and
once
that
is
accepted
by
gitlab,
that
becomes
part
of
the
product,
it's
maintained
by
gitlab,
and
so
that
company
gets
a
feature
that
they
want,
which
is
then
maintained.
You
know
going
forward.
A
A
They
might
be
built
upon
and
improved,
in
which
case
there
might
be
a
premium
version,
but
the
original
features
will
stay
the
same
and
there's
a
whole
page
about
that
which
is
linked
here,
the
stewardship
page,
where
you
can
read
more
about
the
philosophy
behind
that:
okay,
so
which
companies
use
and
contribute
to
foss
open
source
has
really
been
fully
accepted
into
the
corporate
world.
There's
a
there's,
a
statistic:
here:
nine
out
of
ten
companies
use
foss
software.
You
could
probably
even
argue
it's
ten
out
of
10..
A
It's
really
prevalent,
as
I
mentioned
earlier,
it's
in
all
of
our
phones.
It's
in
many
of
the
pieces
of
software.
You
in
our
televisions
in
our
you
know
laptops.
You
know
it's
really
everywhere
in
our
cars,
so
some
companies
actively
make
part
or
some
of
their
product
available
under
the
open
source
licences
such
as
what
gitlab
has
done.
Other
companies
do
the
same
thing.
A
So
there
are
some
changes
happening
in
that
area
and
the
thing
about
open
source
software.
It
was
originally
thought
to
be
insecure
and
unreliable,
and
it
was
it
took
a
long
time
for
it
to
be
accepted
into
the
corporate
world.
It's
now
actually
the
reverse.
It's
now
considered
to
be
more
secure
because
it
has
so
many
people.
A
Looking
at
it-
and
it's
not
just
the
relying
on
one
company
for
for
the
durability
of
that
piece
of
software,
it's
because
basically
anyone
can
look
at
it
and
review
for
themselves
if
they
think
it's
a
good
piece
of
software
and
if
it's
secure.
A
So
why
would
I
contribute
to
open
source?
Why
should
you
contribute
to
open
source
there's
a
number
of
reasons,
especially
if
you're
a
student
now
one
of
them
is
to
build
your
programming
skills
in
a
in
a
real
world
environment.
So,
as
you
know,
you
may
attend
lectures,
you
may
read
books
and
you
may
have
some
type
of
projects
that
you
will
do
as
part
of
your
course,
but
to
actually
we'll
get
real
world
experience
generally,
you
need
to
have
a
job.
A
So.
The
next
point
I
think,
actually
is
quite
important.
If
you
make
a
you
know
a
relatively
significant
open
source
contribution,
I
would
add
that
to
your
cv
as
an
achievement,
just
because
it's
open
source
doesn't
mean
it's
low
quality.
In
fact,
it's
often
the
reverse,
to
to
get
something
accepted
by
a
serious
open
source
project
is
really
some
work
and
it
is
an
achievement,
and
I
would
definitely
put
that
on
your
cv.
A
Maybe
you
want
to
build
something
that
is
literally
used
by
millions
of
people.
So,
for
example,
if
you
worked
on
some
web
server
software,
it's
literally
used
by
hundreds
of
millions
of
people
and
finally,
you
might
decide
in
the
future
that
you
would
like
to
build
some
type
of
business
around
open
source
software,
and
so
understanding
and
contributing
to
open
source
is
a
great
way
to
get
started
in
that
area.
A
Gitlab
has
really
great
resources
to
get
started
with
contributing.
We
have
great
documentation.
There
are
hackathons
which
happen
fairly
regularly
and
you
know
there's
a
lot
of
support
during
those
hackathons.
We
have
a
gifter
channel.
So
getter
is
a
instant
messenger
channel
where
you
can
ask
for
support,
and
then
within
the
issue
tracker
itself,
we
have
two
labels.
A
The
first
one
is
good
for
first
contributors,
so
this
is
something
that
is
considered
to
be
relatively
simple
and
would
be
a
great
way
to
get
started.
Sometimes
it's
something
as
small
as
a
documentation
change,
and
so
that's
you
know
it's
worth
looking
for
those
labels
and
the
other
one
that
will
always
be
accompanied
with
good
for
first
contributors
is
accepting
merge
requests.
So
once
an
issue
has
been
validated
by
the
gitlab
team
and
it's
it's-
you
know
it's
basically
well
described
and
it's
ready
to
be
worked
on.
A
Gitlab
will
often
add
this
label
called
accepting
merge
requests,
which
means
that
anyone
can
just
go
grab
that
and
write
a
merge
request
and
submit
it
and
then
you'll
be
helped
by
the
gitlab
team
to
to
get
that.
Merch
request
merged
and
you
will
essentially
add
to
the
product.
A
So
the
main
landing
page
for
open
source
contributions
is
this
contribute
page?
So
it's
quite
a
long
page.
I've
just
taken
a
screenshot
here,
but
it's
really.
If
you
go
there,
it's
got
all
the
links
to
all
the
materials,
and
I
think
the
most
important
thing
to
think
about
when
contributing
to
any
open
source
project
is,
is
that
you're
donating
your
time
and
you're
getting
something
in
return,
which
is
in
many
cases
learning
and
a
great
experience?