11–20 of 54 posts
Based on Apple's acquisition of FoundationDB, this seems like it will have negative consequences for public development of OPA. What are the counterexamples, where Apple acquiring a project results in it being more open with sustained development?
Based on Apple's acquisition of FoundationDB, this seems like it will have negative consequences for public development of OPA. What are the counterexamples, where Apple acquiring a project results in it being more open with sustained development?
This leaves me quite bummed out. After Oso[0] went from a superb open source policy evaluation solution to one that's completely closed, OPA is what I'm typically reaching for now, but now it'll likely be on life support.
Based on Apple's acquisition of FoundationDB, this seems like it will have negative consequences for public development of OPA. What are the counterexamples, where Apple acquiring a project results in it being more open with sustained development?
Was FoundationDB a CNCF project at the time of acquisition, or in some similar incubator/umbrella? Besides, seems FoundationDB was open sourced after Apple acquired it, wouldn't mean FoundationDB get more open after the acquisition? Although development stalled no matter what so maybe doesn't matter.
Based on Apple's acquisition of FoundationDB, this seems like it will have negative consequences for public development of OPA. What are the counterexamples, where Apple acquiring a project results in it being more open with sustained development?
Was FoundationDB a CNCF project at the time of acquisition, or in some similar incubator/umbrella? Besides, seems FoundationDB was open sourced after Apple acquired it, wouldn't mean FoundationDB get more open after the acquisition? Although development stalled no matter what so maybe doesn't matter.
This is a very well written announcement. It immediately defines OPA (for people like me who don’t immediately recognize it). It says what’s not changing for people, and says where things will go. Congratulations to the team.
This is a very well written announcement. It immediately defines OPA (for people like me who don’t immediately recognize it). It says what’s not changing for people, and says where things will go. Congratulations to the team.
For the people who are currently experiencing the first time a project they heavily used gets acquired by a for-profit company, it's worth remembering that everything written is "As it stands currently", which can change at any time.
It wouldn't be the first time the founders/company/project said "Nothing will change now when we got acquired" only for it to shutdown/change drastically just months after.
Isn't Styra like a company of like 50-100 people? Seems like it'd be a bummer to be an employee at the company that gets left behind.
Based on Apple's acquisition of FoundationDB, this seems like it will have negative consequences for public development of OPA. What are the counterexamples, where Apple acquiring a project results in it being more open with sustained development?
Was FoundationDB a CNCF project at the time of acquisition, or in some similar incubator/umbrella? Besides, seems FoundationDB was open sourced after Apple acquired it, wouldn't mean FoundationDB get more open after the acquisition? Although development stalled no matter what so maybe doesn't matter.
This is a very well written announcement. It immediately defines OPA (for people like me who don’t immediately recognize it). It says what’s not changing for people, and says where things will go. Congratulations to the team.
I was left with the somewhat opposite feeling. I still don’t know what OPA actually is or does. It has a nice paragraph describing it without saying anything at all.
- How do I enforce that inbound API requests come only from trusted sources?
- How do I enforce fine-grained access to user records?
- How do I enforce a set of naming conventions for a data update?
Many such policies may come from regulatory requirements, may be regional in nature, and may change in otherwise stable codebases. And it's even harder when you're applying this to a highly-scalable production internet service. As a result, defining policy at an organizational level with auditing is a challenge for large enterprises. OPA helps enterprises administer and enforce policies.
More details on what OPA does here: https://www.openpolicyagent.org/docs/philosophy
And you can see some examples of Rego (the policy language) here: https://play.openpolicyagent.org