Earlier quoted context omitted.
To me it reads as being worried that someone malicious could step in and use the project's name to do harm. If you don't have someone within the project with trust built ready-to-go, establishing that trust enough to hand over the project is a big task.
I totally agree, that is a huge risk. But what if someone from the postgres team decided to step up and maintain it? I'm not saying that's likely, but it is possible for a very popular tool like this. With the way the project exited now, that would not at all be an option. Obviously if postgres themselves decided to do it, they wouldn't need the previous credibility so this isn't the best example
Pgbackrest is no longer being maintained
101–110 of 245 posts
Re: Pgbackrest is no longer being maintained
#102This 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 nu…
That text is right there in the link, we don't need to read it twice.
Re: Pgbackrest is no longer being maintained
#103This 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 nu…
Re: Pgbackrest is no longer being maintained
#104Earlier 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.
I thought a while back there were some products that had dual licenses, a fairly open license for private use, use in small companies, but requiring purchase and/or contribution back when used in something like a cloud providers SaaS.
I like open source, but I also can understand the nagging feeling when your (and your contributors work) is used for pure corporate greed.
Re: Pgbackrest is no longer being maintained
#105> 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...
I doubt that they have sponsored an OSS project or made it sustainable.
Re: Pgbackrest is no longer being maintained
#106Re: Pgbackrest is no longer being maintained
#107Open Source has worked fine here. The author doesn't find financial support for the work, so they just want to change winds and that's a perfectly fine path forward. If this is really much more than a personal project "for fun, on my leisure time", and it became an actually serious product -level project that provides good value in commercial environments for people, there's clearly an opportunity for a for-profit co…
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.
Re: Pgbackrest is no longer being maintained
#108It still works, you can just keep using it. I think that’s what the author would want. People to keep using it until it doesn’t work anymore.
Re: Pgbackrest is no longer being maintained
#109"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.
This is the right attitude. All the "this is sad" comments make me want to ask, "How sad are you? Sad enough to donate?"
Not the fact that he made the decision he made.
Re: Pgbackrest is no longer being maintained
#110Earlier quoted context omitted.
To me it reads as being worried that someone malicious could step in and use the project's name to do harm. If you don't have someone within the project with trust built ready-to-go, establishing that trust enough to hand over the project is a big task.
I totally agree, that is a huge risk. But what if someone from the postgres team decided to step up and maintain it? I'm not saying that's likely, but it is possible for a very popular tool like this. With the way the project exited now, that would not at all be an option. Obviously if postgres themselves decided to do it, they wouldn't need the previous credibility so this isn't the best example