►
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,
everyone
welcome
to
the
first
day
of
open
J's
world
I'm,
so
excited
to
have
the
chance
to
meet
all
of
you
virtually
over
the
next
few
days
and
I'm
very
excited
to
be
one
of
the
folks
kicking
us
off
on
Tuesday
morning.
So
thank
you
all
for
your
time
and
for
virtually
allowing
me
and
the
other
speakers
into
your
homes.
So
my
name
is
Keeley
Hammond
I'm,
a
senior
software
engineer
at
envision
and
a
member
of
the
electron
core
governance
team.
I'm
gonna
be
speaking
today
on
behalf
of
electron.
A
So
these
are
photos
from
our
maintainer
summits
over
the
past
three
or
four
years,
and
they
represent
not
only
the
electron
core
team,
which
is
a
fairly
small
team,
but
also
the
wide
network
of
contributors
and
maintainer
x'
from
companies
all
over
the
world.
So
I
want
to
thank
that
larger
maintainer
Network,
but
I
also
want
to
give
a
special
shout
out
to
the
electron
core
team.
They've
done
a
tremendous
amount
of
work
over
the
past
year
and
I'm
very
excited
and
honored
to
be
representing
them
today.
A
So
some
of
you
may
be
familiar
with
electron
already,
and
some
of
you
may
even
develop
an
electron
already.
But
for
those
of
you
who
aren't
familiar
with,
who
we
are
electron,
is
a
JavaScript
framework
for
creating
desktop
applications
with
web
technologies
and
to
dive
a
little
bit
deeper
into
what
that
means.
Electron
is
ultimately
a
combination
of
three
major
sub
dependencies.
The
first
is
chromium
which
gives
us
everything
we
need
to
render
HTML
Javascript
and
CSS.
A
The
second
is
node
and
nodes,
VA
runtime,
which
I
suspect
many
of
you
in
the
audience
are
quite
familiar
with,
and
then
we
have
a
layer
of
C++
and
objective-c
and
that
layer
implements
the
API
is
that
you
as
a
developer,
need
to
build
a
native
application.
So,
for
example,
if
you
want
your
electron
app
to
interact
with
the
native
window
object
or
if
you
wanted
to
send
native
notifications
together,
these
three
dependencies
form
the
datian
of
electron.
A
My
own
team
at
envision
is
building
an
app
called
envision
studio
which
is
built
on
electron,
and
there
are
a
lot
of
reasons
for
a
developer
to
choose
electron
for
their
project,
but
some
of
the
primary
ones
that
we
hear
are
cross-platform
support.
So,
instead
of
having
to
support
multiple
native
teams,
you
can
just
write
one
electron
app
that
works
on
Mac,
Windows
and
Linux
out
of
the
box.
A
Some
of
the
major
changes
that
came
as
part
of
our
open
Jas
incubation
period
we're
a
formal
governance
structure.
So
in
March
of
2019,
we
established
a
governance
structure
that
covers
several
key
areas.
You
can
see
here,
as
well
as
an
administrative
working
group
that
oversees
the
project
as
a
whole.
A
We've
also
made
a
large
investment
into
automation,
as
many
of
you
who
work
in
open
source
can
probably
sympathize
with
people
are
our
most
constrained
resource,
and
so,
whenever
we
can
free
up
and
developer
by
having
a
computer
do
the
work.
Instead,
we
try
to
do
that.
We've
made
investments
specifically
into
automating,
our
nightly
and
beta
builds
and
improving
our
distributed,
build
system
so
that
developers
have
a
much
easier
time
developing
quickly.
A
We've
also
built
out
our
CI
CD
pipeline
to
include
more
coverage
for
Mac,
Windows
and
Linux
and
I
finally
want
to
give
a
shout-out
to
core
member
shelleyf
or
so
electron
now
supports
multiple
major
release.
Lines
and
Shelley
wrote
to
bots
that
help
with
maintaining
that
the
first
is
trop,
which
automates
back
porting
PRS
to
various
versions.
A
So,
for
example,
if
I'd
submitted
a
PR
for
electron,
10,
trot
pool
automatically
back,
poured
that
2,
electron,
9
and
so
on,
and
the
second
pot
is
unreleased,
which
audits
branches
that
are
targeted
for
specific
release
lines
and
it
checks
specifically
for
branches
that
either
haven't
been
merged
yet
or
need
to
be
manually
back
ported.
Both
trap
and
unreleased
have
saved
us
a
lot
of
time,
and
if
you
are
an
open-source
maintainer,
that's
running
multiple
release
lines.
I
highly
recommend
talking
to
Shelley.
She
is
an
expert
in
this
area.
A
We've
also
made
a
lot
of
improvements
to
electrons
core
api's.
This
is
by
no
means
a
comprehensive
list,
but
some
of
the
highlights
include
the
introduction
of
a
new
module
called
context
bridge,
and
this
is
something
that
we're
hoping
to
use
as
we
depreciate
our
remote
module
to
give
developers
a
safer
way
to
communicate
across
contexts.
We
also
made
improvements
to
how
we
send
complex
JavaScript
objects
across
IPC,
we're
now
using
v8,
structured,
clone,
algorithm
and
we've
been
actively
modernizing.
A
Our
ap
is
a
big
example
of
that
is
converting
our
internal
api's
to
return
promises
rather
than
using
callbacks,
but
I
would
say.
Arguably
the
largest
change
that
we
made
in
the
incubation
period
happened
in
May
of
2019,
so
we
changed
our
release
cadence
to
match
more
closely
with
chromium's
chromium
releases.
Once
every
six
weeks,
an
electron
now
releases
a
new
major
version,
roughly
every
12
weeks,
and
the
result
of
that
is
that
consumers
that
are
building
electron
apps
now
have
access
to
newer
versions
of
chromium,
faster.
A
So
as
we
were
making
these
changes,
we
were
also
continuously
moving
through
the
open,
Jas
foundations,
incubation
program
and
I'm
very
excited
to
announce
today
that
electron
has
graduated
from
the
incubation
program
and
is
now
an
open
Jas
in
Packt
project,
and
we're
very
excited
about
this
for
a
lot
of
reasons.
But
chief
among
them
is
we
wanted
to
take
a
bigger
part
in
the
larger
JavaScript
community.
The
JavaScript
ecosystem
is
so
interconnected.
Many
of
our
own
maintained
errs
contribute
to
other
projects
such
as
node
and
as
electron
continue
to
grow.
A
We
want
it
to
be
intentional
about
giving
back
to
that
rich
ecosystem
and
also
inviting
some
of
you
all
into
the
electron
community
if
you'd
like
to
join
us.
So
in
that
spirit,
if
you're
interested
in
getting
more
involved
in
electron
or
learning
a
bit
more
about
the
project,
we
would
love
to
have
you.
We've
made
a
concentrated
effort
in
the
last
year,
or
so
to
make
it
easier
for
new
contributors
to
jump
in
and
start
contributing
PRS
to
the
project.
A
We've
done
this
through
a
series
of
contributor
training
events
such
as
this
one
we
held
in
January
of
2020
and
we've
also
improved
electrons,
build
tools,
creating
an
easy
set
of
scripts
for
new
contributors
to
use
to
clone
down
electron
locally
and
start
developing
and
I
want
to
give
a
special
shout
out
here
to
four
members
of
the
core
team:
shell,
Eve
or
Sam,
a
turd
charles
kerr
and
john
Kleinschmidt.
The
four
of
them
recognize
this
as
a
considerable
hurdle
for
new
contributors.
A
Last
fall
and
work
together
to
put
these
build
tools
together
and
if
you'd
like
to
learn
more
about
electron.
But
you
don't
quite
feel
like
jumping
into
the
core
project.
Yet
electron
fiddle
is
a
great
way
to
start
exploring
what
you
can
do
an
electron.
This
is
an
easy
QuickStart
template
that
lets.
You
choose
from
various
versions
of
electron,
write
your
code,
write
in
editor
and
easily
publish
to
a
gist
with
a
click
of
a
button.
A
So
if
any
of
you
are
interested
in
electron,
I
would
love
to
talk
to
you
over
the
course
of
the
conference
and
I
also
included
some
links
and
resources
that
you
might
find
helpful
in
this
link.
So
if
you
visit
bit
dot
Li
slash
electron,
open,
J
s,
you
can
see
an
easy
list
of
resources
to
start
jumping
in.