3 ms·

I understand there's been drama, and someone walked away or was pushed out. I don't quite care enough to understand it all or point at guilty parties. However,

by sho_hn 8mo ago

I understand there's been drama, and someone walked away or was pushed out. I don't quite care enough to understand it all or point at guilty parties. However, my current understanding is that the project remains active, so titling this article "Post Mortem" feels a bit like it's done in bad faith as it's usually applied to projects that are over. It's certainly what I immediately assumed made it newsworthy.

Forgeties79 8mo ago
As a bazzite user who had no idea anything was up until this headline, yes that was very concerning at first glance
jovial_cavalier 8mo ago
Antheas was the #1 most active developer, and responsible for almost all low level integrations.
- sho_hn 8mo ago
  Software history is rife with projects that outlive a person like that leaving, though. Ulrich Drepper comes to mind immediately. They don't own the project.
- bee_rider 8mo ago
  Just based on this blog post it seems like he wanted the project to be more “professional” in some way that the rest of the developer group didn’t. I wonder if that difference in vision, combined with a (probably justified based on your comment) feeling that he was doing a disproportionate amount of the work lead to an unsustainable situation. Calling it a post-mortem while others are continuing the project still seems kind of petty, though.
- aprilwaters 8mo ago
  Nope, he was not, and his software will be replaced.
  - jovial_cavalier 8mo ago
    https://github.com/ublue-os/bazzite/commits/main/?after=e49f5fac49fcdd8cc66e969357537779619fc67d+384 https://github.com/ublue-os/bazzite/commits/main/?after=e49f...
- _lvbh 8mo ago
  Looking at the contributor analytics: https://github.com/ublue-os/bazzite/graphs/contributors https://github.com/ublue-os/bazzite/graphs/contributors Doesn't look like he was, but then looking at the actual commit list: https://github.com/ublue-os/bazzite/commits/main/?before=e49f5fac49fcdd8cc66e969357537779619fc67d+385 https://github.com/ublue-os/bazzite/commits/main/?before=e49... He definitely had more than the 14 commits listed. They might've lost their email due to the conflicts & lost ownership over the commits?
hiccup_socks 8mo ago
>"Post Mortem" feels a bit like it's done in bad faith as it's usually applied to projects that are over. is it? outside of autopsies, i think i have only ever seen it used as a synonym for "incident report". i dont think ive ever associated the term specifically with the end of a project. e.g. cloudflare uses the tag for all of their incident reports (https://blog.cloudflare.com/tag/post-mortem/ https://blog.cloudflare.com/tag/post-mortem/), not as a signal that they are closing shop
- sho_hn 8mo ago
  Gamasutra has a famous line of articles where game developers provide retrospectives on how the development of their titles went, maybe I'm influenced by that. I'm aware about the use in incident reports of course, but then you still don't call it "<project name> Post-Mortem" but use a more specific namespace.
- throwaway_ocr 8mo ago
  In the incident case, it's a post-mortem on the incident. The incident itself is (hopefully) resolved and can now be dissected to learn about what went wrong and how things can improve in the future. That's what a post-mortem implies to me in the tech industry. A thing happened, it's over now, here are the lessons we learned to take into the future.
  - sho_hn 8mo ago
    Yes, but Bazzite is not over.
    - snapplebobapple 8mo ago
      If you read the article, way down at the end he pulls it around. He means it's dead as a serious os that vendors can ship. It'll live on for hobbyists but you better be prepared for a bumpy ride as the YOLO crew hits send on increasingly larger amounts of stuff before its ready and continue to act unprofessionally (my paraphrase, but I believe I captured it).
- 8mo ago
0xedd 8mo ago
[dead]
ekianjo 8mo ago
"someone" is the main developer behind Bazzite. That's some context your post is missing.

by sho_hn 8mo ago

Forgeties79 8mo ago

As a bazzite user who had no idea anything was up until this headline, yes that was very concerning at first glance

jovial_cavalier 8mo ago

Antheas was the #1 most active developer, and responsible for almost all low level integrations.

sho_hn 8mo ago
Software history is rife with projects that outlive a person like that leaving, though. Ulrich Drepper comes to mind immediately. They don't own the project.
bee_rider 8mo ago
Just based on this blog post it seems like he wanted the project to be more “professional” in some way that the rest of the developer group didn’t. I wonder if that difference in vision, combined with a (probably justified based on your comment) feeling that he was doing a disproportionate amount of the work lead to an unsustainable situation. Calling it a post-mortem while others are continuing the project still seems kind of petty, though.
aprilwaters 8mo ago
Nope, he was not, and his software will be replaced.
- jovial_cavalier 8mo ago
  https://github.com/ublue-os/bazzite/commits/main/?after=e49f5fac49fcdd8cc66e969357537779619fc67d+384 https://github.com/ublue-os/bazzite/commits/main/?after=e49f...
_lvbh 8mo ago
Looking at the contributor analytics: https://github.com/ublue-os/bazzite/graphs/contributors https://github.com/ublue-os/bazzite/graphs/contributors Doesn't look like he was, but then looking at the actual commit list: https://github.com/ublue-os/bazzite/commits/main/?before=e49f5fac49fcdd8cc66e969357537779619fc67d+385 https://github.com/ublue-os/bazzite/commits/main/?before=e49... He definitely had more than the 14 commits listed. They might've lost their email due to the conflicts & lost ownership over the commits?

hiccup_socks 8mo ago

>"Post Mortem" feels a bit like it's done in bad faith as it's usually applied to projects that are over. is it? outside of autopsies, i think i have only ever seen it used as a synonym for "incident report". i dont think ive ever associated the term specifically with the end of a project. e.g. cloudflare uses the tag for all of their incident reports (https://blog.cloudflare.com/tag/post-mortem/ https://blog.cloudflare.com/tag/post-mortem/), not as a signal that they are closing shop

sho_hn 8mo ago
Gamasutra has a famous line of articles where game developers provide retrospectives on how the development of their titles went, maybe I'm influenced by that. I'm aware about the use in incident reports of course, but then you still don't call it "<project name> Post-Mortem" but use a more specific namespace.
throwaway_ocr 8mo ago
In the incident case, it's a post-mortem on the incident. The incident itself is (hopefully) resolved and can now be dissected to learn about what went wrong and how things can improve in the future. That's what a post-mortem implies to me in the tech industry. A thing happened, it's over now, here are the lessons we learned to take into the future.
- sho_hn 8mo ago
  Yes, but Bazzite is not over.
  - snapplebobapple 8mo ago
    If you read the article, way down at the end he pulls it around. He means it's dead as a serious os that vendors can ship. It'll live on for hobbyists but you better be prepared for a bumpy ride as the YOLO crew hits send on increasingly larger amounts of stuff before its ready and continue to act unprofessionally (my paraphrase, but I believe I captured it).
8mo ago

0xedd 8mo ago

[dead]

ekianjo 8mo ago

"someone" is the main developer behind Bazzite. That's some context your post is missing.