Hi, I'm trying to identify slow Ecto queries in Pleroma. Scout looks like a good fit, except for the fact that this client library is incompatible with Pleroma's AGPL license, so it can't be used.
Using a restrictive license for a client library is unusual in this space. Take Sentry's Elixir client license, for example (MIT). Even though the Sentry backend has a more restrictive license, the client library is flexible enough to be used in a variety of projects.
It doesn't make a lot of sense to restrict the client libraries when the backend is where the core functionality lives. I would like to suggest reconsidering the license, in favor of something more permissive like MIT. This would make it compatible with AGPL software, and allow it to be used with Pleroma.
Hi, I'm trying to identify slow Ecto queries in Pleroma. Scout looks like a good fit, except for the fact that this client library is incompatible with Pleroma's AGPL license, so it can't be used.
Using a restrictive license for a client library is unusual in this space. Take Sentry's Elixir client license, for example (MIT). Even though the Sentry backend has a more restrictive license, the client library is flexible enough to be used in a variety of projects.
It doesn't make a lot of sense to restrict the client libraries when the backend is where the core functionality lives. I would like to suggest reconsidering the license, in favor of something more permissive like MIT. This would make it compatible with AGPL software, and allow it to be used with Pleroma.