171–180 of 245 posts
It's funny how developer time is considered free, but tokens are not. In other words when it comes to FOSS contribution, developer time can be donated but tokens can't - so as we move into agentic code era all FOSS development carries a cost unless it is purely done by hand (which more often it isn't). Not saying this is what is going on here but it's presumably a factor if the author was looking for an employer to s…
Earlier quoted context omitted.
Why does sqlite not suffer from the same risk?
SQLite doesn’t depend on donations. They have a consortium, sell licenses (it is open source but some companies like the explicit CYA), sell support contracts, sell an aviation-grade test harness, and sell extensions. Of course there is always the risk it goes out of business like any other company, but it’s not funded like your typical small open source project and doesn’t even allow open contributions (not necessar…
Wow, this is pretty surprising, I was under the impression that this is the leading PG backup/recovery tool. Anybody know how WAL-G and Barman compare? https://github.com/wal-g/wal-g https://github.com/EnterpriseDB/barman
Sad to see competitor go, I think there's lots of room for improvement here, & C over Golang is particularly nice when postgres wants to run on system without overcommit
Earlier quoted context omitted.
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.
Earlier 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…
Some who are opposed to capitalism seem to think that anyone who wants to trade their talents and hard work for more than the minimum, are exploiting anyone who wants or needs their product.
"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?"
A fair amount of people work here at orgs on here would absolutely be able to swing couple of hundred bucks per month in sponsorship or licensing or donations for a critical tool in their infra toolkit without lot of effort.
Particularly so, with the rising frequency of AI deleted my prod posts.
Earlier quoted context omitted.
Are you using WAL archiving? As far as I understand, pgbackrest and Barman can also use direct streaming from the DB (same mechanism as replication), I didn't find any mention of this in the WAL-G documentation. With WAL archiving you need to wait for a WAL segment to finish before it's backed up. With streaming backups the deadtime is minimized. At least that's as far as I understand this, I didn't get to try this o…
WAL-G's PITR backups are insurance against data loss through erroneous data manipulations (eg: accidental DELETE/DROP/UPDATE). WAL-G's streaming approach (using pg_receivewal or similar) sends WAL records to backup storage continuously as they're generated, rather than waiting for a full segment to complete. On top of that, for availability (and minimizing deadtime), we have 2 replicas using streaming replication. If…
Earlier quoted context omitted.
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 h…
You could dual license as well, so it’s GPL or AGPL for personal, OSS, or academic use, but requires a paid for commercial license for commercial use. I suggest GPL or AGPL because their copyleft clauses make them hostile towards platform providers who might otherwise seek to profit from your work without paying.
As long as they keep releasing sources of their own modifications -if they ever do any-, the rest is fair play.