►
From YouTube: Lightning Talk: Cooking Open Source without Spilling the Secret Sauce - Rey Riel, Qlik
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
Hi
everybody
and
welcome
to
cooking
open-source
without
spilling
a
secret
sauce.
My
name
is
Ray
and
I'm.
A
developer
advocate
and
lead
architect
at
click.
So
this
talk
is
going
to
be
about
promoting
open
source
without
dishing
out
the
company's
secrets.
There's
a
lot
of
companies
out
there
that
probably
want
to
get
involved
in
open
source,
but
they're
really
not
sure
how
to
do
it
because
they
don't
want
to
give
away.
You
know
the
core
piece
of
their
product
that
makes
them
successful.
A
I'm
gonna
be
using
my
company
clique
as
the
main
example
and
all
the
stuff
that
we
done
to
get
involved
in
open
source.
So
the
first
thing
that
you
can
do
is
you
can
open
source
components
that
can
be
changed
by
users.
If
you
give
the
users
a
place
to
share
customizations
that
they've
made
to
your
product,
it's
a
fantastic
way
to
create
an
open
source
community.
That's
involved
directly
in
your
product,
so
I'd
click.
A
We
have
this
brilliant
data
analytics
engine
which
is
our
bread
and
butter,
but
we
also
have
a
front
end
called
clixsense.
Clixsense
is
what
allows
users
to
drag
and
drop
visualizations,
create
data
stories
and
really
find
insights
into
the
data
that
they
have
and
we
have
a
very
robust
extension
API
and
so
that
allows
users
to
create
visualizations
directly
into
the
product.
A
So
if
your
company
has
any
way
of
extending
the
product,
if
it
has
any
theming
capability
or
any
ability
to
do
a
lot
of
configuration,
settings,
customization
settings
or
maybe
script
against
the
product,
these
are
some
fantastic
things
that
you
can
help
your
community
to
open
source
and
really
get
your
company
involved
in
open
sourcing.
The
next
thing
that
you
can
do
is
you
can
open
source
your
documentation?
A
Not
only
does
it
allow
users
to
contribute
to
the
product
and
help
make
the
product
better,
but
it's
basically
built
in
review
for
your
documentation
at
a
very
low
cost.
So,
for
example,
we
have
a
product
here
at
clique,
called
clique
core
and
we've
open
sourced
the
entire
click
core
website.
So
if
users
come
in-
and
let's
say
they
come
in
to
the
website
for
your
product-
they
come
in
and
start
looking
at
the
documentation
and
they
start
trying
to
use
that
documentation
and
they
realize
that
there's,
maybe
some
issues
or
some
misspellings.
A
They
can
actually
update
that
documentation
themselves
and
that
saved
a
lot
of
time
on
your
part.
Developing
an
open
sourcing
tooling
for
you
use
is
another
fantastic
way
to
get
involved
in
open
source
when
users
get
started
with
your
product
or
when
they're
doing
some
tedious
tasks
with
your
product.
Often
they
need
tooling.
In
order
to
accomplish
that,
and
if
you
open
source
that
tooling,
you
not
only
provide
this
for
your
users
to
address
other
main
pain
points,
but
they
can
actually
fix
those
main
pain
points
themselves.
A
So,
for
example,
here
I
click
we
have
what's
called
catwalk,
which
is
basically
a
website
that
allows
them
to
connect
to
their
engine
and
view
their
data
as
they're
loading,
their
data
into
the
engines.
So
they
can
see
exactly
what
their
data
looks
like
before
they
get
started.
Visualizing
it
another
thing
about
our
engine
is
that
it's
built
on
a
WebSocket.
So
if
people
don't
know
how
to
use
WebSockets,
we
developed
an
enigma
j/s
project,
which
is
a
JavaScript
library
that
allows
users
to
easily
connect
and
talk
back
and
forth
with
the
engine.
A
And
finally,
we
also
have
a
product
called
halyard
jeaious
and
how
your
j/s
allows
our
users
to
easily
load
data
into
their
engine
using
javascript
we've
open
sourced
the
entire
thing,
so
that
if
people
are
having
issues
with
our
tooling,
then
they
can
fix
it
themselves.
Another
fantastic
way
to
get
involved
into
open
source
is
to
encourage
your
Rd
to
open
source.
Any
in-house
tooling
that
they
have
Rd
is
a
veritable
gold
mine
for
things
to
open-source.
A
When
employees
are
developing
your
product
or
working
with
your
product,
they
often
create
their
own
scripts
or
their
own
tooling.
In
order
to
accomplish
tasks
that
they
have
with
the
product
itself,
so
encouraging
your
Rd
and
your
employees
to
open
sources
code
not
only
benefits
the
users
by
allowing
the
users
to
use
this
tooling
themselves,
but
it
can
also
possibly
improve
your
internal
processes,
because
if
your
users
find
a
faster
or
a
better
way
to
accomplish
these
tasks,
they
can
update
the
things
that
you're
now
using
internally.
So,
for
example,
I
click.
A
We
have
almost
a
hundred
repositories
now
and
a
lot
of
that
has
things
that
we
were
using
internally
and
we
ended
up
open
sourcing
that
so
we
now
have
a
repository
called
gopher
size
which
is
used
for
load
testing.
We
also
have
one
called
clixsense
kubernetes
and
that's
to
help
our
multi-tenant
cloud
product
work
better
inside
of
kubernetes,
so
a
lot
of
times
with
the
product.
A
Finally,
if
you
don't
have
anything
inside
of
your
Rd
or
inside
of
your
product
to
open
source,
one
of
the
great
things
that
you
can
do
to
get
involved
in
the
open
source
community
is
open
source,
any
tutorials
or
any
product.
Examples
that
you
might
have
the
interactive
education
material
that
your
company
uses
to
get
users
up
and
running
it's
great
content
to
open
source.
A
So,
for
example,
we
have
a
workshop
called
the
click
movie
workshop,
which
allows
people
to
get
the
up
and
running
with
the
engine
API
using
a
react
app
that
shows
off
movie
data.
We
have
a
game
called
core
chopper
which
allows
you
to
connect
our
engine
to
bike
sensors
and
make
a
helicopter
move
up
and
down,
depending
on
how
hard
you're
working
on
your
bike-
and
we
also
have
a
ton
of
websites
that
really
focus
on
using
the
engine
in
a
lot
of
different
business
cases.