I suspect this might not be the best place to ask this, but, I'm eager to release some gems and normally I'd just pick MIT and not even think about it. But, I did some research to see if maybe I want to try something different this time. MPL-2.0 seems like an interesting/robust/"permissive-ish" license and I'm tempted to try it. But I'm scared that I might harm adoption. Reading the text of the license and its corresponding FAQ, I feel like this shouldn't be an issue for adoption, but I'm worried regardless.

Any body happen to have advice on how I could preemptively assess the adoption risk of choosing MPL-2.0? The gem would be a software framework collection of gems (same category as Sinatra and Rails, basically)

I suppose another way I could ask it... if Rails had hypothetically originally released under MPL-2.0, would they have regretted it and relicensed under MIT later due to running into adoption snags?

Thanks!

Miles