ParadeDB'er here: We are really hoping this can turn into a back and forth, making both of our products better.

If you modify it for use in a commercial backend (not a hosted db service), does the AGPL-3.0 license mean you have to share the source of project it is used in or only of the forked repo? On a related note, have you changed your stance on accepting issues and pull requests like some orgs?

	▲	philippemnoel 4 hours ago \| parent \| next [-]
		As for the AGPL question, our primary goal with this license is to protect ourselves from hyperscalers and avoid fragmenting the community. You can read more about it here: https://news.ycombinator.com/item?id=41227172
	▲	philippemnoel 4 hours ago \| parent \| prev [-]
		We have many community contributors (150 and counting) who submit PRs and many users who open issues. We love them! We're well aware that our external contributors use AI (we do too!), and we fiercely guard our product against AI slop. We ask that external contributors understand the changes they are making, and we frequently close PRs unmerged if they look like slop.