It is still hard to hook on to spritely unless you have deep technical expertise. That means most others (large group) are in wait-and-see necessarily.
Choice is perfectly valid, because its the foundation team's own initiative.
Is it the best tech introduction strategy? Best technology adoption model to use?
Your community and ecosystem have to catch up, once you say "it's time for fun".
Randy's community pattern language might serve to unlock upper-stack stakeholders now.
@cwebber @helge
Because that is highly tangential from spritely core technology, fanning out into vast scope, you might offload that to a fellowship that can facilitate multiple independent initiatives at the same time, not just spritely but also see an ecosystem of convergance and increasing alignment, rather than fragmentation as per the norm.