Move it to the community (the “Blaze Community”)
Start a patreon account (or similar) to help fund some core developers/repo managers (the “Blaze Team”)
Start some sort of system for prioritizing (voting) on the best use of time of core develoers hired by the patreon funding… preferably you can only vote if you donated to the patreon account. But you can comment, send PRs, and everything else even if you didn’t donate. The people who really value blaze and are using it in production will be happy to throw 10, 20, 50 bucks a month at the project, especially if they can have a strong say in the direction of the work. Others can contribute just like they would to any open source project and there will be the Blaze Team there to work on taking in their PRs.
Make it so Blaze can be an NPM package
Get clarity on the future of Atmosphere and Meteor… is there a need to move Atmosphere to community too? or can atmostphere packages be ported to NPM? I would be concerned investing too much in atmosphere being around in 2 years (if it were on MDG to keep it up-to-date. Not throwing shade on MDG at all. They have limited resources/time/mindshare).
Make accounts a part of “core” (blaze community should take up the PR/Issues with the core accounts-related package(s) )
The “Blaze Team” should take over the autoform package (if aldeed is okay with it). This is core to the blaze value proposition and huge number of issues and PRs should be moved forward along with the new Blaze Community
“Blaze Community” should consider forking meteor 1.2 (or making a package to add 1.2 functionality to whatever meteor x.x.x is out). I like being able to move my file structure around, rename files, and not worry about import/exports too much… especially in the early stages of development.
There are a lot of ideas up top, the core must-haves for me are:
- fund it properly with some mechanism for showing best places to invest work
- get it on npm (I suspect this may be the first thing to get out of the way)
- bring in autoform to get worked on
- bring in accounts to get worked on
- consider other stuff like view-model, etc.
I think if we tackle the majority of these points, we can save blaze/meteor/atmostphere from extinction.
Let me know what you would add; what you would take away; how you would prioritize each action.