Live data from Hacker News

Pgbackrest is no longer being maintained

github.com

61–70 of 245 posts

Re: Pgbackrest is no longer being maintained

#61

> TL;DR: pgBackRest is no longer being maintained. If you fork pgBackRest, please select a new name for your project. > I imagine at some point pgBackRest will be forked, but that will be a new project with new maintainers, and they will need to build trust the same way we did. I completely understand having to back out of maintenance on an OSS project, but why also slam the door closed on someone taking over? There…

It can still be forked. There is no salting the ground here. If you maintain the project and have for a long time, and you wish to stop, you can stop.

If no one cared enough to support the project, why does anyone care enough now? It all sounds hollow. Nothing bitter about it.

When you work on a project, any project, you have a responsibility. At some point we all can stop, and become free to not have that responsibility.

Re: Pgbackrest is no longer being maintained

#62

> TL;DR: pgBackRest is no longer being maintained. If you fork pgBackRest, please select a new name for your project. > I imagine at some point pgBackRest will be forked, but that will be a new project with new maintainers, and they will need to build trust the same way we did. I completely understand having to back out of maintenance on an OSS project, but why also slam the door closed on someone taking over? There…

From the story told in the README it is clear this is a project ran by a single person. There is no wider maintenance team that can be trusted with continuing the project. So anyone who offers to take up the maintenance will be unknown to the current maintainer and cannot automatically be trusted.

The alternative to this seemingly bitter approach is handing over the trust they built to some unknown person who can do whatever they want with the data in a lot of PostgreSQL databases around the world. I think I prefer the bitterness here over blind trust.

Re: Pgbackrest is no longer being maintained

#63

> TL;DR: pgBackRest is no longer being maintained. If you fork pgBackRest, please select a new name for your project. > I imagine at some point pgBackRest will be forked, but that will be a new project with new maintainers, and they will need to build trust the same way we did. I completely understand having to back out of maintenance on an OSS project, but why also slam the door closed on someone taking over? There…

[deleted]

Re: Pgbackrest is no longer being maintained

#64
post #51
post #39

Earlier quoted context omitted.

Gatekeeping?!? Those that paid , or did any kind of contributions upstream are entitled to be sad. Others should consider this is what happens to that lego piece in Nebraska, when no one contributes, and everyone uses it.

That is exactly gatekeeping, no? You are only entitled to feel sad if you contributed effort or financially, otherwise you aren't allowed to feel. Why can't others that just used the tool feel sad? It is supposed to be used, it's the whole reason for it to exist; not everyone using it will have technical expertise or money to contribute to it, feeling sad about it when it solved issues for someone is a completely nor…

The reason for something to exist is not to be used. He was paid while doing it, and that pay stopped, and he kept doing it. Now he wishes to stop.

The reason for something to exist is someone finds joy doing it. Especially when they are unpaid.

The sadness should be focused on his inability to support himself with a tool that clearly a lot of companies, and people are using and gaining value for.

Re: Pgbackrest is no longer being maintained

#65

> TL;DR: pgBackRest is no longer being maintained. If you fork pgBackRest, please select a new name for your project. > I imagine at some point pgBackRest will be forked, but that will be a new project with new maintainers, and they will need to build trust the same way we did. I completely understand having to back out of maintenance on an OSS project, but why also slam the door closed on someone taking over? There…

I think this is overly harsh. After the guy has been working on the project for such a long period a handover would inevitably be a long process, not least to ensure whoever took over didn't abuse the existing user-base. Completely fair if the existing maintainer doesn't want to take on this work, and arguably a fork forces consumers to properly consider that someone else is in charge now.

Re: Pgbackrest is no longer being maintained

#66

Earlier quoted context omitted.

It's such a strawman to claim that you cannot be sad if something disappears where you have not financially or you work contributed. Someone can say that they are sad that the Notre Dame burned down even if they haven't personally contributed to Notre Dame.

That comparison is fallacious too, I think. Something burning down is a tragedy, beyond anyone's control. It's also possible to love something for its beauty, and be sad that a globally historic monument suffered such an act of god that the irreplaceable art and craftsmanship is gone forever. Something closing down, perhaps because there was not enough money to sustain its continued operation, when tens of thousands…

Well said, accurate framing.

Re: Pgbackrest is no longer being maintained

#67

So sad to see this happening.. I had just last year prepared a detailed guide for reliable postgre backups to local volume as well as cloud storage, using pgBackRest, for my own projects.. pgBackRest have worked so well for me https://github.com/freakynit/postgre-backup-and-restore-guid... Thanks to the author for all the time and effort he put into this project..

I really wish projects like this didn't fall through the cracks and continued to be funded. The struggles of OSS are too real.

The struggles of living in an economic system while completely rejecting that system and pretending it isn't there.

Re: Pgbackrest is no longer being maintained

#68
post #45

Earlier quoted context omitted.

True.. I truly wish wish we had better open-source license and more open-source projects adopt it.. Tiered pricing license... tiering based upon annual company revenues... should start super low for small companies (free for individuals), and jump to thousands of dollars per year for 10+ milion revenue companies. I understand that this might not fully be in the spirit of open-source, but, what's happening currently i…

Sigh. Bane of my existence is any service which does this. My org theoretically makes hundreds of millions, unfortunately none of that money is ours. So I get forced into a procurement process for anything that costs more than (ridiculously small limit), and get stuck using the worst in class because it's cheaper.

Sounds like whoever is getting that money is hamstringing your organization on purpose so they can keep more of your money.

Re: Pgbackrest is no longer being maintained

#70
post #45

Earlier quoted context omitted.

True.. I truly wish wish we had better open-source license and more open-source projects adopt it.. Tiered pricing license... tiering based upon annual company revenues... should start super low for small companies (free for individuals), and jump to thousands of dollars per year for 10+ milion revenue companies. I understand that this might not fully be in the spirit of open-source, but, what's happening currently i…

Sigh. Bane of my existence is any service which does this. My org theoretically makes hundreds of millions, unfortunately none of that money is ours. So I get forced into a procurement process for anything that costs more than (ridiculously small limit), and get stuck using the worst in class because it's cheaper.

Is there a measurement that would work better for your organizations setup?
Post reply on HN