Haha! I need dev time to port testing. And time for some money making projects to be able to survive. And time to tackle bugs for Quasar. And time for new features. And time to answer/investigate questions on GitHub/forum. And time to update documentation. And time to ensure overall Quasar quality for each release. And future time for a blog. And future time for some example apps. And time to live! You get the idea. Help me spread the word on Quasar to raise some money yo! Not trying to get rich, just to survive.

What? I thought it was time for complaining like in a support group )))

Suggestion: Start a “Trip to 1.0” issue on Github, and list off the to-dos that need to get done to get there, possibly with both “nice-to-haves” and “must haves”. Then contributors could know what to possibly help with.

Or, create a “contributor friendly” tag and create issues for all the to-dos and tag them also for 1.0.

What I am getting at is to make a workflow, which is as contributor friendly as possible.

Add an issue/ to-do to support Docker dev environments too.

Edit: and if you need help doing this, I’d be glad to help with creating the issue or issues. I just need the full list.

Hang in there! Momentum is getting closer.
I’m really impressed by the quality of this project (code AND docs, and very little bugs).
Worst case scenario, if you have to freeze quasar, you’ll have paid work in no time.
You’ve got one hell of a project on github to show off at any job interview.

@Martin Thanks! All I want is to grow Quasar. Not thinking about any job interview. I’ve quit high paying jobs so that I could write Quasar and made a hell lot of sacrifices (and still doing them). Just having a dream here which slowly becomes a reality and that’s reason enough to drive me forward.

Maybe this can help some of you, we have a running test setup with Quasar 0.9.1 and Webpack 2. Won’t be perfect for direct usage because we integrated Quasar later into an existing plain vue.js project, but it should get you in the right direction: