Who hurt you!?
starshipwinepineapple
joined 2 months ago
AGPL is the most restrictive OSI approved license (of the commonly used ones), but it is still a free (libre) open source license. My understanding is just that the AGPL believes in the end-users rights to access to the open source needs to be maintained and therefore places some burden to make the source available if it it's being run on a server.
In general, companies run away from anything AGPL, however, some companies will get creative with it and make their source available but in a way that is useless without the backend. And even if they don't maliciously comply with the license, they can still charge for their services.
As far as documentation goes, you could license documentation under AGPL, and people could still charge for it. It would just need to be kept available for end-users which i don't think is really a barrier to use for documentation.
It would be much more customer and developer friendly to allow linking a service portal instead of providing a phone number. I would go insane if a user called me directly every time one of my projects had a bug or some perceived (non)issue. No, that's not how this works.
Kebab or snake for ease of parsing through them.
Either i wasn't clear or you are replying to the wrong person, but i am in support of foss projects asking for donations in a reasonable manor such as this
There is an option to disable it permanently. Otherwise it is once a year and easily dismissed
It's once per year, easily dismissed, and can be permanently disabled. Seems entirely reasonable for a piece of free software that someone would use everyday
Never. For the most part i haven't had a question that hasn't already asked or that couldn't be answered from reading the docs or some other source. For the cases i get stuck i ask the question to a more focused group
My company ones are always super obvious. One of the best ones though was on valentines day spoofing a valentines ecard from a coworker in your organization
And if you want a private repo, you can also use gitlab and point to custom domain with gitlab pages or cloudflare pages.
Yes, oracle will reclaim your server if it falls under certain thresholds for the resources you've signed up for. So it might be better to request less resources then you need but this will somewhat complicate things if you want more resources in the future since iirc you can't simply resize.
One way to get around all of this though is convert to pay as you go (PAYG). PAYG gets the same always free allocations and you only pay for use above that, and oracle won't reclaim PAYG (at least not my server for ~4 years). Just set up a budget of a $1 and then alerts to email you if you reach 1% of your budget. If you somehow go over your free resources it'll tell you.
Lastly in some cases oracle just straight up loses your data or disables your account. As always practice 3-2-1 backups (don't rely on the free rotating backups on their servers as your only backup).
It's some hoops to jump through but i was paying $5/ month for a digital ocean droplet and the oracle server has been running for 4 years now, and i also have scaled up one project and started a few others that wouldn't have all fit on my droplet. Other than the threat of reclaiming my resources before i switched to PAYG I've been pretty happy with it.
Nothing. The context of this comment thread is "fuck corporations" and then proposing AGPL to solve that. I am merely pointing out that if their goal is to have a non-commercial license then AGPL doesn't solve that, which is why i mention they can charge for their services with AGPL.