Recently I've been working more with Drupal, and noticed Quickstart 1.0's post-installation fizzle: "470 days since your last update"!
I've been focused on billable time recently, but with Ubuntu 11.04 support ending 12.10, it's time to update my tools :-)
What's next for QS 3.0?
What I really wanted from QS 1.0, more than anything, was a debugger. A profiler was just icing on the cake.
Now, I really want a sensible dev/test/prod server ecosystem.
Acquai and Pantheon do a great job of this, but for many projects, I don't need all the extra features/cost. And, I'd like the rest of my tools integrated as well.
Since QS 1.0, the new Drupal installer and Drush 5 do many of the things that the Quickstart Drush commands had to do, and provide inter-server communication.
Quickstart 3.0, is about reducing the learning curve by packaging the best of these things together, with some brief howto videos.
Quickstart 2.0 beta - what happened?
Mike Stewart did an amazing job of refreshing QS 1.0 into the QS 2.0 beta, and went in a new direction towards Unity interface. Canonical’s Unity Interface wasn’t designed for me, and using it reduced my enthusiasm.
In the middle of arguing about desktop environments, I realized how destructive the Gnome/Unity/KDE wars are, and also how fundamental forks and alternatives are to the Open Source movement. Mike Stewart’s vision became the project DrupalPro.
Anyways, I'm grateful for Mike Stewart’s contributions, and if you're excited about Unity, DrupalPro is state of the art for a Unity Drupal Development Environment as I write this.
For QS 3.0, it’s important to support several desktops, and include structure for more. Luckily, Linux already does this, so it's "just" integration and configuration. Gnome 3 has made some great progress in the last year, and I've been using Cinnamon (a reimplementation of Gnome 2) that comes with Mint.
QS 3’s focus is:
- a local dev and test server
- a basic production server config (with remote debugging)
- support at least two desktop environments (Gnome 3 and Cinnamon)
- a better update and release process.
Quickstart 1.0 was a solo endeavor. It took alot of time because I had to learn and do everything myself.
Quickstart 3.0 must be a team effort for success. This time, I'm asking for help! It's time to go to the next level!
Next steps are:
- breaking up the problem,
- reviewing technologies,
- putting together a sensible schedule
We could especially use help with making a simple/sane LAMP server config that can work across dev/stage/prod
If you have time and skills you’d like to contribute, please email me: email@example.com
Thanks for your interest!
(If you've private messaged me on drupal.org or in the issue queue, I've tried to reach out, but your message may have gotten lost in the pile-o-email. Email firstname.lastname@example.org and we'll connect.)