-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5 changed files
with
112 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
--- | ||
audience: | ||
- Introductory and overview | ||
title: Against the Grain | ||
speakers: | ||
- _participants/sasa-juric.md | ||
published: true | ||
|
||
--- | ||
This talk tells the story of developing a bespoke Kafka client. None of the existing libraries in the BEAM ecosystem fulfilled the needs of the team, and it was estimated that contributing new changes to those projects would be very difficult. At the same time, writing and maintaining a client from scratch would require a lot of time, much more than the team could afford. | ||
|
||
So what can we do in such situation? Join me and find out how by making some atypical choices we got ourselves out of a tricky situation. | ||
|
||
**OBJECTIVES:** | ||
* question the established practices and think about whether they make sense in your context | ||
* overcome the deficiencies in the BEAM ecosystem | ||
|
||
**AUDIENCE:** | ||
This talk is fairly technical, and assumes that the audience is familiar with some BEAM language, especially with its concurrency model. The code snippets will be given in Elixir. No knowledge of Kafka is required. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
--- | ||
audience: | ||
- Introductory and overview | ||
tags: | ||
- Growth-of-the-Ecosystem | ||
title: Contributing to the Erlang Ecosystem. My Journey from Individual Contributor to Maintainer | ||
speakers: | ||
- _participants/benjamin-philip.md | ||
published: true | ||
|
||
--- | ||
"Lately the Erlang Ecosystem has grown to address many new domains. But is its community growing enough to support it? My experience as a new contributor may shed light on this. | ||
|
||
I'm a 16 year old student who started contributing to the Livebook, Hexpm and Nx projects at 14. Since then I've grown from being a raw newbie to receiving funding from The EEF to work on packages that will support Erlang's telemetry implementation. | ||
|
||
Join me as I talk about my challenging transition and see how I: | ||
* overcame my fear of the opensource community | ||
* learned to work with other members | ||
* found more meaningful ways to contribute | ||
* learned to balance my contributions with my other priorities | ||
|
||
If you're new to the community, you'll learn how to get started and grow in the community - even if you have as little experience as i did. | ||
|
||
Maintainers will see how the community helped me to make valuable contributions, how it got in my way, and how my experiences can help their projects." | ||
|
||
**OBJECTIVES:** | ||
This talk has 2 major objectives: | ||
|
||
* Convince more people to get involved in the Erlang Community by illustrating how easy and effortless it is to make valuable contributions - no matter your background | ||
* Show maintainers and community leaders what elements of the community ethos enabled even a teenager to contribute, and what elements were a stumbling block | ||
|
||
If you are interested in growing in the community, expect to also learn: | ||
* How to find projects to help out with and contributions to make | ||
* How to build relationships with other members of the community | ||
* How to balance your opensource work with other aspects of your life | ||
|
||
**AUDIENCE:** | ||
This talk is targeted at people: | ||
|
||
* who would like to get started with contributing to the Erlang Ecosystem | ||
* looking to grow in the community while maintaining a work-life balance | ||
* maintainers who would like to grow their projects | ||
* leaders of the community interested in a unique perspective |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
--- | ||
audience: | ||
- Intermediate | ||
tags: | ||
- Edge | ||
- Cloud | ||
- Devices | ||
title: SwErl - a library for phones, watches, and headsets | ||
speakers: | ||
- _participants/lee-barney.md | ||
- _participants/sylvia-deal.md | ||
published: true | ||
|
||
--- | ||
It is estimated that there are over 1 billion current users of the iPhone. That doesn't even count the number of watch, Mac, and headset users. SwErl is an easy-to-use open source library that enables these 1 billion plus devices to be nodes in Erlang systems....and it mimics Erlang programming patterns and syntax in Swift. | ||
|
||
**OBJECTIVES:** | ||
* To show the current state of SwErl. | ||
* Show working code examples. | ||
* Show examples of message passing between an Erlang node and a SwErl node. | ||
* To begin building a community to complete and maintain SwErl (the project is too important for one person do make all important decisions). | ||
* To show examples of how Erlang-type syntax makes writing Swift apps simpler. | ||
* To demonstrate a bridge for programmers to move to Erlang/Elixer when they have Swift knowledge. | ||
|
||
**AUDIENCE:** | ||
Software Engineers and programmers wanting their product to reach broader audiences without having to use older web-style technologies. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
--- | ||
audience: | ||
- Introductory and overview | ||
tags: | ||
- Growth-of-the-Ecosystem | ||
title: Unlock the Power of OpenID Connect on the BEAM | ||
speakers: | ||
- _participants/jonatan-maennchen.md | ||
published: true | ||
|
||
--- | ||
In an increasingly interconnected digital world, ensuring robust security and seamless user experiences is paramount. OpenID Connect, a proven authentication framework, stands at the forefront of this challenge. This conference talk delves deep into the realm of OpenID Connect, shedding light on its myriad benefits and showcasing practical techniques to effortlessly integrate it into your Erlang and Elixir web applications and APIs. | ||
|
||
Discover the foundational concepts that make OpenID Connect a compelling choice for identity authentication. Explore how it simplifies the process of verifying user identities while enhancing security. We'll explore the benefits of Single Sign-On (SSO), identity federation, and secure user data exchange, all facilitated by OpenID Connect. | ||
|
||
**OBJECTIVES:** | ||
* Understands what OpenID is on the surface | ||
* Compares SSO vs. internal authentication | ||
* Knows about oidcc & its Cowboy & Phoenix Integrations | ||
|
||
**AUDIENCE:** | ||
* Software Engineers | ||
* Project Managers |