GOgortiz·Sep 7, 2022
Yes. It is very clear. They have changed the license in the repository: https://github.com/akka/akka-http/commit/3e82a2811e853ece3b4...
In We Are Changing the License for Akkaakka
akka-http
Scala2016–2022
akka / akka-http
akka-http
The Streaming-first HTTP server/module of Akka
4Distinct people
4Mentions
0Explicit recommenders
1.4KGitHub stars
What to know before exploring
What it is
The Streaming-first HTTP server/module of Akka
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year4 dated mentions
Observed mentions: 2016-11-05 18:36:12 UTC to 2022-09-07 11:44:41 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 0 | 2 |
What Hacker News says
4 sourcesIs it clear which exact OSS components will get the license change?
For example, is akka-http [0] part of these changes?
[0] https://github.com/akka/akka-http
In We Are Changing the License for AkkaMagnet pattern is purely about making the code you write nicer to look at. (for spray it had more reasons to exist but for akka-http it is purely a usability problem)
Basically it allows you to write
def f[T](fMagnet: FMagnet[T]): X => Y
f(t) { x =>
// ...
}
instead of
def f[T](t: T)(implicit tc: TC[T]): X => Y
f(t).apply { x =>
// ...
}
so just about removing one ".apply"
(see https://github.com/akka/akka-http/issues/100 where i copy pasted the code bits from)
But yeah first time I read up on the magnet pattern it was a wtf moment.
In Plain Functional Programming by Martin Odersky [video]https://xkcd.com/386/
Disclaimer: I am an akka and akka-http community contributor. I don't know how this works for other projects.
But I don't think the process is as painful as you describe in the akka world. My experiences are quite to the contrary. The community here is warm and welcoming. But, please look at this from the other side. Would you use the software in your mission critical application if the project was accepting quickly contributions from random strangers on the internets?
Please, find an issue marked as community in https://github.com/akka/akka/issues or https://github.com/akka/akka-http/issues and give it a go. How to solve the "credentialize yourself" problem? Be known to the commiters by first working on a docs issue.
In How to contribute to an open source project on GitHub