Live data from Hacker News

Pgbackrest is no longer being maintained

github.com

71–80 of 245 posts

Re: Pgbackrest is no longer being maintained

#71

Earlier quoted context omitted.

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…

Alright, take a park closing then. Can you be sad about that if you haven't personally raised money to finance the park?

Yes, I can't finance every park. I can feel sad about people suffering throughout the world without personally supporting them all.

I am an active open source contributor.

Re: Pgbackrest is no longer being maintained

#72
post #31

Plenty of comments of "So sad I have been using this". How many actually contributed back to keep it going?

The number of maintainers is always smaller than the number of users for any successful project. GitHub displays the number of contributors as 57, I don't know if that's small or not.

[deleted]

Re: Pgbackrest is no longer being maintained

#73
post #6

Why 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.

Why is it the responsibility of the person working for free?

Why is it never the responsibility of the people using it?

If anyone cares enough they will. People didn’t care enough to pay, so maybe no one cares enough to fork and be the new unpaid custodian

Re: Pgbackrest is no longer being maintained

#74

Earlier 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 struggles of living in an economic system while completely rejecting that system and pretending it isn't there.

There is no evidence of any of that.

He was paid to work on it. That stopped, he continued to work on it in the hopes he could find someone who would hire him to work on it.

That wasn’t true, no one has funded it.

So due to the economic system he no longer maintains it.

That’s your economic system at work. No one is pretending it isn’t there, this is the outcome of it

Re: Pgbackrest is no longer being maintained

#75
"so sad to see this"

The source is still available. Maintaining your own copy and/or paying someone to do it is an option.

While you're at it, look at all the projects you depend on that you would similarly be sad about losing, and set up those donations today.

Re: Pgbackrest is no longer being maintained

#76
This is the message the author posted on LinkedIn:

After a lot of thought, I have decided to stop working on pgBackRest. I did not come to this decision lightly. pgBackRest has been my passion project for the last thirteen years, and I was fortunate to have corporate sponsorship for much of this time, but there were also many late nights and weekends as I worked to make pgBackRest the project it is today, aided by numerous contributors. Every open-source developer knows exactly what I mean and how much of your life gets devoted to a special project.

Since Crunchy Data was sold, I have been maintaining pgBackRest and looking for a position that would allow me to continue the work, but so far I have not been successful. Likewise, my efforts to secure sponsorship have also fallen far short of what I need to make the project viable.

Like everyone else, I need to make a living, and the range of pgBackRest-related roles is very limited. I can now consider a wider variety of opportunities, but those will not leave me time to work on pgBackRest, which requires a fair amount of time for maintenance, bug fixes, PR reviews, answering issues, etc. That does not even include time to write new features, which is what I really love to do. Rather than do the work poorly and/or sporadically, I think it makes more sense to have a hard stop.

I will post a notice of obsolescence and archive the repository. 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.

Again, many thanks to all the pgBackRest contributors over the years. It was a pleasure working with you!

Re: Pgbackrest is no longer being maintained

#77

> Since Crunchy Data was sold, I have been maintaining pgBackRest and looking for a position that would allow me to continue the work, but so far I have not been successful. Likewise, my efforts to secure sponsorship have also fallen far short of what I need to make the project viable. So this was the problem, I thought Snowflake would pick up the sponsorship of this project but since it is a competing database it do…

Even with sponsorship, it's not always appreciated such as Vercel backing Svelte, Vue, etc. https://www.reddit.com/r/reactjs/comments/1g4lu5p/am_i_seein...

Re: Pgbackrest is no longer being maintained

#79
post #25

I 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.

I've used barman on somewhat large-ish DBs (30+ TB), and had no complaints with it. I am a DBRE, if that holds any weight.

barman seems to cover "Natural disaster" in their docs. Seems good.

I'll take a look. Thanks!

Re: Pgbackrest is no longer being maintained

#80

Earlier 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…

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 that than build a replacement from scratch (most likely). And more likely to attract new sponsorship by being a reliable steward of a known name (albeit with a suffix or something).
Post reply on HN