241–245 of 245 posts
Is it really that much effort to maintain something? I’ll admit I haven’t the foggiest, my most maintained thing having like 200 stars or something, but if I leave it alone for half a year it doesn’t suddenly combust into flame.
> Is it really that much effort to maintain something? yes see https://news.ycombinator.com/item?id=47921198 for start
Earlier quoted context omitted.
I'm not a corporate procurement specialist - I've just hit this wall before. So I might be talking out of my arse in terms of solutions. One way around it is that you get an existing consultancy, who is already on the corporate approved suppliers list and has jumped through all the hoops, to resell the product. They take a hefty cut, usually, but can also pay more punctually (in general large corp purchasing departme…
Dayuum!!! I guess then we should focus only on making that "pay something to this OSS developer" easy.. everything else still stays the same... no guarantees, no offloaded liabilities, no expedited timelines, etc.
I'm not sure making the payment part easy is going to help that much. The ideal, of course, is to get the cost under the departmental discretionary budget; most large corps allow small purchases to go through with less oversight.
Atlassian managed to do this during their initial B2D selling-to-devs stage, so it might be worth reading up how they did it.
Earlier 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.
Changing the license of already existing code? You might not be able to do that without permission from other contributors, I agree. But it's MIT license. We can open a company tomorrow, take that code, and start selling it. Further development and improvements of the code could be trivially done openly or behind closed doors. FWIW the author themselves could do that if they wanted.
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.
databasus does not do PITR.
been using databasus( https://github.com/databasus/databasus ) works pretty well so far.
I'm also using this project. Easy to configure and operate. I am feeling a slight unease using such a recent project for things as important as the database. But the polished interface combined with the easy docker deployment made me use it anyway. Restores need some permission tuning on PostgreSQL but otherwise happy. They are very proud of their github star acquisition curve [0], the "blessing" by Anthropic [1] But…
However, it's really sad that pgBackRest has been closed, because I was led by pgBackRest in some sense when started Databasus