I find it shocking (not really) that among the many BILLION dollar companies built on the back of Postgres there isn't enough sense to pay the salary of one dude to keep a project like this going forever.
Pgbackrest is no longer being maintained
151–160 of 245 posts
Re: Pgbackrest is no longer being maintained
#152Earlier quoted context omitted.
I wonder whether the author has considered taking the product to a paid level and what would be necessary for it. Obviously, all contributors have some form of copyright, which may or may not have been waived depending on whether there was an ACL in place and jurisdiction. So he would need to get permission from the copyright holders, maybe in exchange for a percentage of the profit.
ANd that gets rather looked on here as the authors being deceitful and not really Open Source doing a bait and switch.
I've been working on a software package I'm hoping to release in a few months... I'm really torn on either split FLOSS with commercial extensions, or just going fully private... I was planning on a pretty generous free tier, but hoping to make a bit on the side from commercial customers.
It's a bit of a niche as it is, so that's going to be rough in any kind of pricing model, as a large part of that niche is either homebrew types and the other commercial industry that will likely require some more integrations and customization.
Re: Pgbackrest is no longer being maintained
#153[flagged]
It didn't go dark, and doesn't seem that critical in general.
General idea still stands, but it is not like this just disappeared and backups will stop working.
Re: Pgbackrest is no longer being maintained
#154Earlier quoted context omitted.
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 project is being abandoned because the maintainer is tired of working for free. They said that they hoped someone would fork it, change the name, and pick up where it was left off. Why would anyone do that? If the person who was most passionate about it for over a dozen years has given up because it was never worth the trouble; what fool would think things will be different going forward? This is the curse of OSS…
An alternative reading is that after 13 years dedicated to a single project, the original author is simply burnt out on it, but a new maintainer can start with fresh passion that will last a number of years.
Just because someone gets tired of working on something eventually doesn't mean everyone else will immediately feel the same way.
Re: Pgbackrest is no longer being maintained
#155[flagged]
Why does sqlite not suffer from the same risk?
Re: Pgbackrest is no longer being maintained
#156I find it shocking (not really) that among the many BILLION dollar companies built on the back of Postgres there isn't enough sense to pay the salary of one dude to keep a project like this going forever.
wild isn't it
Re: Pgbackrest is no longer being maintained
#157This is scary as a solo dev who builts on postgresql. You pick a tool trust it, build around it, one day it stops. Oss sustainability is a real problem
I would say "unpaid tool use" is a real problem. Or perhaps "contractless" is actually touching the core issue?
True but as a solo dev, you cant afford to pay for every tool you depend on. That's the trap.
Re: Pgbackrest is no longer being maintained
#158Why not try to find a successor instead of archiving the repo and forbidding the use of the name? I'm sure with a 3.8k stars repo you'll find competent people willing to continue the work.
> I'm sure with a 3.8k stars repo you'll find competent people willing to continue the work.
Oh yeah, I'm sure you will find lots of competent people. Like Jia Tan, for example. I've heard he is very competent.
Re: Pgbackrest is no longer being maintained
#159Earlier quoted context omitted.
While I tend to agree with the line of thinking in this thread that the ethos of open source (and the web writ large) have been taken advantage of by capitalism, I can't quite see this: things belong to a time and place in one's life. The creator feels like his time with this project is at an end, but why would that be an impediment to someone who needs a package like this stepping up and maintaining it? Better to do…
> have been taken advantage of by capitalism “And many programmers, they say to me, “The people who hire programmers demand this, this and this. If I don't do those things, I'll starve.” It's literally the word they use. Well, you know, as a waiter, you're not going to starve. So, really, they're in no danger.” - Richard Stallman in 2001 admitting his ideology can’t explain how a programmer can eat In my opinion, tho…
> and clueless about how power works, from day 1
September 26th, 1983:
"Dear Mr. Stallman, it is I, gjsman-1000, a time-traveler sent back to tell you to rethink your upcoming GNU project because you are currently clueless about how power works. Yes, you may be able to code up an impressive prototype compiler and revise it until your fingers bleed. Yes, a decade later some zealous followers may follow your lead and maintain it on the bleeding edge. Yes, two decades later others will perhaps start an open source compiler project to wrest control from your successful compiler that is largely maintained without your direct input. And yes, three decades later your compiler team may even merge in new features and improvements that came from the other compiler. But heed my ominous warning: four decades later I will not be able to remember my original point, for time travel is dangerous business and has adverse effects on short and long term memory."
Re: Pgbackrest is no longer being maintained
#160I have a moderately sized 2TB production database I have enjoyed using pgBackRest on, and was—this week—going to set it up on another 8TB database we have. What's the next-closest thing? wal-g? barman? databasus? I only get to cosplay as a DBA.
The "closest" would be using Barman with hook scripts (https://docs.pgbarman.org/release/3.18.0/user_guide/hook_scr...) if you rely on cloud storage for storing backups.
https://github.com/aiven-open/pghoard seems like a good option too, but I haven’t tested it yet to have a solid opinion.