Comment by radimm
1 day ago
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!
Damn this sucks. Snowflake bought crunchydata right? I know they largely did that because they wanted to push crunchydata's datalake extension past some sort of proverbial finish line as they've been competing with databricks for features, but snowflakes pressers about commitment to open source and postgres in general (which are ofc something no one should take that seriously) feel even more sad when it blows out the floor underneath projects like this which are undoubtedly part of the same postgres extension ecosystem. Snowflake went after crunchydata for that _one_ extension while neglecting the broader world that crunchydata was keeping alive. They can champion support OSS and postgres all they want but they hurt the ecosystem here, kind of a slap in the face to the postgres world.
Thank you for adding this here.
That text is right there in the link, we don't need to read it twice.
>"we don't need to read it" [here]
many people here don't read the articles, and that's not going to change. (on today's internet, jumping from the site you want to be on to a site with unknown UX patterns is fraught)
but people here do read the comments, so having important details from the articles in comments here improves the quality of comments here, at least if you value staying on topic.
I think mostly the point is that it inadvertently implies that the message adds something new. A note that the same thing was posted on LinkedIn would help the ones tho did read the linked content know right away it's the same. I managed to just move on, but I did had a knee-jerk moment of "what if I'm missing something?" - I suppose for some people it's more difficult.
Why would somebody click a link to GitHub and then not read the text that very obviously pertains to the title of the submission they clicked on?
Also saying that GitHub has unknown UX patterns made me lol.
>fraught
dumb "journalists" especially have this backwards mindset.
Why did you read it twice if you didn't need to? Seems unnecessary. I only read it once and just ignored it on subsequent encounters.
Trying to find what context was on LinkedIn but not in the posted link. Spoiler alert, there was none.