Policy for web framework integrations

[lambda-fairy]

Now that we're getting a handful of PRs adding these, I think it would be good to define which web frameworks should and shouldn't be integrated into Maud.

[zopieux]

This would be in constant flux as the ecosystem evolves, right? What are you looking for in this thread – objective signals to assess a framework's popularity which could help motivate accepting/refusing a PR?

Given that web framework integration are gated by non-default crate features, I'm not sure I understand the rationale for ever refusing adding one, if someone went through the trouble of creating a well-tested PR to support a new framework. Rust is not JS, I don't anticipate a high load, do you?

[lambda-fairy]

Thanks @zopieux. I think my main concern here is my workload. I don't want to spend a lot of time updating all the integrations every time I change something.

I think the only rule here we need is that support is "best effort" -- we'll try our best not to break anything, but the bulk of the maintenance work will be provided by the community. (Which is de facto the current situation anyway.)