Der erste Commit in das electron/electron
Repository war am 13. MĂ€rz 20131.
10 Jahre und 27.147 weitere Commits von 1192 individuellen Mitwirkenden spĂ€ter, Electron ist heute zu einem der beliebtesten Frameworks fĂŒr das Erstellen von Desktop-Anwendungen geworden. Dieser Meilenstein ist die perfekte Gelegenheit, um unsere bisherige Reise zu feiern und zu reflektieren, und mitzuteilen, was wir auf dem Weg gelernt haben.
Wir wĂ€ren heute nicht hier ohne alle, die ihre Zeit und MĂŒhe geopfert haben, um das Projekt zu unterstĂŒtzen. Obwohl Quellcode-Commits immer die sichtbarsten BeitrĂ€ge sind, mĂŒssen wir auch die Anstrengungen der Leute anerkennen, die Fehler melden, userland-Module warten, Dokumentation und Ăbersetzungen bereitstellen und an der Electron Community im gesamten Cyberspace teilnehmen. Jeder Beitrag ist fĂŒr uns als Betreiber von unschĂ€tzbarem Wert.
Bevor wir mit dem Rest des Blog-Beitrags fortfahren: Vielen Dank. â€ïž
Wie sind wir zu diesem Punkt gekommen?â
Atom Shell wurde als GerĂŒst fĂŒr GitHubs Atom-Editorgebaut, der im April 2014 in die öffentliche Beta startete. Es wurde von Grund auf als Alternative zu den webbasierten Desktop-Frameworks gebaut, die zu dieser Zeit verfĂŒgbar waren (node-webkit und Chromium Embedded Framework). Es hatte eine Killer-Funktion: Einbetten von Node.js und Chromium, um eine leistungsfĂ€hige Desktop-Laufzeit fĂŒr Web- Technologien zu bieten.
Innerhalb eines Jahres begann Atom Shell ein immenses Wachstum der FĂ€higkeiten und PopularitĂ€t zu sehen. GroĂe Firmen, Startups und einzelne Entwickler hatten gleichermaĂen damit begonnen, Apps damit zu bauen (einige frĂŒhe Anwender waren Slack, GitKraken, und WebTorrent), und das Projekt wurde treffend in Electron umbenannt.
Von da an startete Electron voll durch und hielt nie auf. Hier ist ein Blick auf unsere wöchentliche Download-Anzahl ĂŒber die Zeit, dank npmtrends.com:
Electron v1 wurde 2016 veröffentlicht und versprach eine höhere API-StabilitĂ€t und bessere Dokumentation und Werkzeuge. Electron v2 wurde 2018 veröffentlicht und fĂŒhrte semantische Versionierung ein, was es den Entwicklern von Electron einfacher macht, den Release-Zyklus zu verfolgen.
Mit Electron v6 haben wir auf eine regulĂ€re 12-wöchige groĂe Release-Kadenz umgeschaltet, um der Chromium-Kadenz zu folgen. This decision was a change in mentality for the project, bringing âhaving the most up-to-date Chromium versionâ from a nice-to-have to a priority. This has reduced the amount of tech debt between upgrades, making it easier for us to keep Electron updated and secure.
Since then, weâve been a well-oiled machine, releasing a new Electron version on the same day as every Chromium stable. By the time Chromium sped up their release schedule to 4 weeks in 2021, we were able to shrug our shoulders and increase our release cadence to 8 weeks accordingly.
Weâre now on Electron v23 (and counting), and are still dedicated to building the best runtime for building cross-platform desktop applications. Even with the boom in JavaScript developer tools in recent years, Electron has remained a stable, battle-tested stalwart of the desktop app framework landscape. Electron apps are ubiquitous nowadays: you can program with Visual Studio Code, design with Figma, communicate with Slack, and take notes with Notion (amongst many other use cases). Weâre incredibly proud of this achievement and grateful to everyone who has made it possible.
Was haben wir auf dem Weg gelernt?â
Der Weg zur Dekaden-Marke war lang und gewunden. Hier sind ein Paar der Kernelemente, die uns geholfen haben, ein solch groĂes Open-Source Projekt am Leben zu erhalten.
Skalierung verteilter Entscheidungsfindung mit einem Governance-Modellâ
Eine Herausforderung, die wir bewĂ€ltigen mussten, war, die langfristige Richtung des Projekts zu bewĂ€ltigen, nachdem Electron zum ersten Mal in der PopularitĂ€t explodierte. Wie gehen wir damit um, ein Team von ein paar Dutzend Ingenieuren zu sein, die ĂŒber Firmen, LĂ€nder und Zeitzonen verteilt arbeiten?
In the early days, Electronâs maintainer group relied on informal coordination, which is fast and lightweight for smaller projects, but doesnât scale to wider collaboration. In 2019, we shifted to a governance model where different working groups have formal areas of responsibility. This has been instrumental in streamlining processes and assigning portions of project ownership to specific maintainers. What is each Working Group (WG) responsible for nowadays?
- Electron-Versionen herausbringen (Releases WG)
- Upgrade von Chromium und Node.js (Upgrades WG)
- Ăberwachung des öffentlichen API-Designs (API WG)
- Electron sicher halten (Sicherheit WG)
- Die Webseite am Laufen halten, Dokumentation und Bereitstellung von Werkzeugen (Ecosystem WG)
- Community und Firmenreichweite (Outreach WG)
- Community-Moderation (Community & Safety WG)
- Wartung unserer Build-Infrastruktur, Maintainer-Tools und Cloud-Services (Infrastructure WG)
Around the same time we shifted to the governance model, we also moved Electron's ownership from GitHub to the OpenJS Foundation. Although the original core team still works at Microsoft today, they are only a part of a larger group of collaborators that form Electron governance.2
While this model isnât perfect, it has suited us well through a global pandemic and ongoing macroeconomic headwinds. Going forward, we plan on revamping the governance charter to guide us through the second decade of Electron.
If you want to learn more, check out the electron/governance repository!
Communityâ
The community part of open source is hard, especially when your Outreach team is a dozen engineers in a trench coat that says âcommunity managerâ. That said, being a large open source project means that we have a lot of users, and harnessing their energy for Electron to build a userland ecosystem is a crucial part of sustaining project health.
What have we been doing to develop our community presence?
Virtuelle Gemeinschaften erstellenâ
- In 2020, we launched our community Discord server. We previously had a section in Atomâs forum, but decided to have a more informal messaging platform to have a space for discussions between maintainers and Electron developers and for general debugging help.
- In 2021, we established the Electron China user group with the help of @BlackHole1. This group has been instrumental in Electron growth in users from Chinaâs booming tech scene, providing a space for them to collaborate on ideas and discuss Electron outside of our English-language spaces. Weâd also like to thank cnpm for their work in supporting Electronâs nightly releases in their Chinese mirror for npm.
Participating in high-visibility open source programsâ
- We have been celebrating Hacktoberfest every year since 2019. Hacktoberfest is yearly celebration of open source organized by DigitalOcean, and we get dozens of enthusiastic contributors every year looking to make their mark on open source software.
- In 2020, we participated in the initial iteration of Google Season of Docs, where we worked with @bandantonio to rework Electronâs new user tutorial flow.
- In 2022, we mentored a Google Summer of Code student for the first time. @aryanshridhar did some awesome work to refactor Electron Fiddle's core version loading logic and migrate its bundler to webpack.
Automatisieren Sie all die Dinge!â
Today, Electron governance has about 30 active maintainers. Less than half of us are full-time contributors, which means that thereâs a lot of work to go around. Whatâs our trick to keeping everything running smoothly? Our motto is that computers are cheap, and human time is expensive. In typical engineer fashion, weâve developed a suite of automated support tooling to make our lives easier.
Nicht Gomaâ
The core Electron codebase is a behemoth of C++ code, and build times have always been a limiting factor in how fast we can ship bug fixes and new features. In 2020, we deployed Not Goma, a custom Electron-specific backend for Googleâs Goma distributed compiler service. Not Goma processes compilation requests from authorized userâs machines and distributes the process across hundreds of cores in the backend. It also caches the compilation result so that someone else compiling the same files will only need to download the pre-compiled result.
Since launching Not Goma, compilation times for maintainers have decreased from the scale of hours to minutes. A stable internet connection became the minimum requirement for contributors to compile Electron!
If youâre an open source contributor, you can also try Not Gomaâs read-only cache, which is available by default with Electron Build Tools.
Kontinuierliche Faktor-Authentifizierungâ
Continuous Factor Authentication (CFA) is a layer of automation around npmâs two-factor authentication (2FA) system that we combine with semantic-release to manage secure and automated releases of our various @electron/
npm packages.
While semantic-release already automates the npm package publishing process, it requires turning off two-factor authentication or passing in a secret token that bypasses this restriction.
We built CFA to deliver a time-based one-time password (TOTP) for npm 2FA to arbitrary CI jobs, allowing us to harness the automation of semantic-release while keeping the additional security of two-factor authentication.
We use CFA with a Slack integration front-end, allowing maintainers to validate package publishing from any device they have Slack on, as long as they have their TOTP generator handy.
If you want to try CFA out in your own projects, check out the GitHub repository or the docs! If you use CircleCI as your CI provider, we also have a handy orb to quickly scaffold a project with CFA.
Sheriffâ
Sheriff ist ein Open-Source-Werkzeug, das wir geschrieben haben, um die Verwaltung von Berechtigungen in GitHub, Slack und Google Workspace zu automatisieren.
Sheriffâs key value proposition is that permission management should be a transparent process. It uses a single YAML config file that designates permissions across all the above listed services. With Sheriff, getting collaborator status on a repo or creating a new mailing list is as easy as getting a PR approved and merged.
Sheriff also has an audit log that posts to Slack, warning admins when suspicious activity occurs anywhere in the Electron organization.
âŠund alle unsere GitHub Botsâ
GitHub is a platform with rich API extensibility and a first-party bot application framework called Probot. To help us focus on the more creative parts of our job, we built out a suite of smaller bots that help do the dirty work for us. Here are a few examples:
- Sudowoodo automates the Electron release process from start to finish, from kicking off builds to uploading the release assets to GitHub and npm.
- Trop automates the backporting process for Electron by attempting to cherry-pick patches to previous release branches based on GitHub PR labels.
- Roller automates rolling upgrades of Electronâs Chromium and Node.js dependencies.
- Cation ist unser StatusprĂŒfbot fĂŒr electron/electron PRs.
Insgesamt hat uns unsere kleine Bot-Familie einen enormen Schub in der EntwicklungsproduktivitÀt gebracht!
Was kommt als NĂ€chstes?â
Wenn wir in unser zweites Jahrzehnt als ein Projekt kommen, könnten Sie fragen: Was ist das nĂ€chste fĂŒr Electron?
Weâre going to stay in sync with Chromium's release cadence, releasing new major versions of Electron every 8 weeks, keeping the framework updated with the latest and greatest from the web platform and Node.js while maintaining stability and security for enterprise-grade applications.
We generally announce news on upcoming initiatives when they become concrete. If you want to keep up with future releases, features, and general project updates, you can read our blog and follow our social media profiles (Twitter and Mastodon)!
- This is actually the first commit from the electron-archive/brightray project, which got absorbed into Electron in 2017 and had its git history merged. But whoâs counting? Itâs our birthday, so we get to make the rules!â©
- Contrary to popular belief, Electron is no longer owned by GitHub or Microsoft, and is part of the OpenJS Foundation nowadays.â©