The #DrupalPicchu sessions have been published, and I will be making the Drupal Lean Process presentation in Cusco. In preparation, the lit-drupal-lean project is in full swing right here on GitHub. Here’s a short-list of what has been achieved so far:
- Some of the most important docs and guides and templates have been gleaned over to the wiki. That includes material on MVP Planning, structured (hypotheses-driven) user stories, collaborative design and style and code guides, scaffolding and a host of templates to people your issue queue.
- Milestone 1 is in full swing, and the closed issues include some very interesting stuff, like an everything in code manifesto and drush generated install profile + features solution, etc.
- The codebase in branch master already includes a complete distro starter set, which will then grow via the addition of features, some of which will be base features and will be turned on by the install profile, and some of them will be optional and simply present.
Backdrop como evolución alternativa y sana para Drupal 7
Introducing Drupal Lean Process
Table of contents
[Skip to any section because you can]
I have been working in software development a long time. Early on I recognized the need for Process as a way of re-using best practices for teamwork. At that time, Process implied for most of us the Waterfall model, which divides a development project into discipline based phases, each to be visited once in turn, in a kind of cascade: Requirements; capture the requirements, do the Design, Implementation, Verification and Validation, Deploy, then shift into Maintenance mode. Most people still follow that model implicitly, it has stayed in the everyday consciousness of process, much like Newton’s laws instead of the Theory of Relativity, much like the theory of Creationism over the scientific Theory of Evolution kicked off by Charles Darwin. Yep, Waterfall often creeps in even when people say and even when people think they are using Agile. Of course, project difficulties and even failures based on the extremely high propensity (40% minimum) for requirements to change within the life-cycle of a project highlighted the dire need for at least an Iterative and Incremental model. And when that became too top-heavy, at least in its wonderful, eye-opening but hard to tailor and work with Rational Unified Process, I moved on to a kind of personal synthesis of CMMI (love that continuous improvement and organization wide adoption!) and Agile and Scrum approaches. More recently I have loved the simpler work in process and visual approach of the Kanban as a lean variety of Agile:
“Some Agile methods take a more flexible approach to time than Scrum does. (For example, Kanban does away with the notion of a two-week batch of work and places the emphasis on single-piece flow.) But you can still make time within a Scrum sprint in which creative activities can take place.” Gothelf, Jeff (2013-02-22). Lean UX: Applying Lean Principles to Improve User Experience. O’Reilly Media.
Steps I take to install Drupal 7 / Backdrop CMS dev server on an Ubuntu 12.04 LTS on say Digital Ocean Droplet
Easily redoable for a quick dev server for Drupal 7 and/or Backdrop CMS on say a Digital Ocean Droplet:
Oh Shyte! Drupal 6? Provision a new Ubuntu server! How?
If you suddenly need to provision a new web app server for Drupal 6, the main problem you have is that the furthest back you can go, in say Ubuntu releases on Digital Ocean or Linode, is Ubuntu 10.04 LTS (Lucid Lynx). Default Php there is 5.3, and even though almost all contrib modules and core for Drupal 6 play nice with Php 5.3 these days, what about those monstrous legacy Drupal 6 sites that need to be maintained for “just a little bit longer” and whose modules cannot be upgraded easily due to dependency hell, or which for some reason, just need Php 5.2? This is a short article that, based on the following references, shows the steps I took to get the job done:
Best = Free: Drupal Team Project Management tool based on latest Eclipse release (Kepler)
Second article in the Best = Free Drupal IDE series
This article follows last week’s article Best = Free: Drupal IDE based on latest Eclipse release (Kepler), in which we established Eclipse as a premier Drupal IDE. This article demonstrates Eclipse (Kepler) as a Drupal Team Project Management tool also.
Our projects consist of deliverables, and our project deliverables live in repositories. Git repositories. For AWebFactory and a good number of developers and organizations, that means GitHub.
If you followed the first article in this series, you already have a powerful Drupal IDE to work on your Drupal based projects, both locally on your laptop or at your workstation, and remotely, directly on your server. In either case, assuming the code is cloned from a repository and incremental improvements and deliverables are pushed there, the version control cammands are often carried out in a terminal (inside of Eclipse, hopefully!) or else with a GUI of some kind, again, working with either local or remote cloned codebases.
Wouldn’t it be great if these tasks could be carried out in the same IDE environment where the actual editing of the code takes place. And if that repo is on GitHub, and the IDE could integrate with GitHub issues (and even gists), our IDE would not only be capable of managing the codebase, it would be capable of managing the entire project and team also, via GitHub Issues 2 (https://github.com/blog/831-issues-2-0-the-next-generation).
That’s exactly what EGit and the GitHub Mylyn Connector can do. So we need to:
1. Install EGit
2. Install the GitHub Mylyn Connector
3. Start managing Drupal Team Projects and issue tracking right from your Kepler based Drupal IDE
Best = Free: Drupal IDE based on latest Eclipse release (Kepler)
I hate it when waves of closed source fashion hit the open source communities: Purchase such and such an IDE, “it’s awesome”. Apart from paying a lot, hey, it’s closed source! Forget that! This article is the first in a series that will show you how to get set up with a top of the line, free as in beer and truly open source Drupal IDE (and Project Management system!), complying with the following objectives:
Top of the line free software development IDE with multiple projects and a multitude of plugins, based on Eclipse Kepler.
No vendor lock in.
Support for Web development in general (HTML, CSS, JS, XML, etc.), that is syntax highlighting, autocomplete suggestions with pop-up documentation, mouse-over documentation.
Support for PHP development also.
Support for back-end languages (Java, etc.)
Support for Remote project development, including code highlighting, etc.
Support for Drupal development
Drupal coding standards,
Drupal files immediately editable as PHP code,
Spaces instead of tabs
The right encoding (Unix) so they can be committed to Drupal repositories.
Drupal 8 y la adopción de los contenidos estructurados
Working through Developing Backbone.js Applications
Before I get completely seduced by Angular.JS and others equally as sweet for use on an upcoming and very important web app project, I really need to give Backbone.js another chance, a fair chance. Nothing could provide this with better timing than the publication now of the completed Developing Backbone Applications, by Addy Osmani. The book signifies a big change, in that it is simpler to dive into Backbone.js, and you can do it with more confidence since you are being shown a path following best practices.
Here’s the rub: Backbone.js is “not opinionated, meaning you have the freedom and flexibility to build the best experience for your web application however you see fit. You can either use the prescribed architecture it offers out of the box or extend it to meet your requirements.”
Diving into Lift with updated Lift in Action project (chapter 3)
Chapter 3 of Lift in Action is interesting because it reveals the elegance and simplicity of Lift’s View-Snippet-Model and templating system, actually showing how one would approach a workflow, from View First design and designer deliverables to template nesting and menu building, and from application requirements to business object modeling. In the midst of all this, the active record-like Mapper “ORM” is presented in quite useful fashion. You can find the code (in my repo, which is fully compatible with Lift 2.5 and sbt 0.12) here (at Tag “chapter03”): https://github.com/victorkane/LiftInActionAuctionApp/tree/chapter03
For development, it is quite common to use the built in H2 database engine, and this is no exception. So while it’s very cool I don’t have to start installing “stacks” of base software just to run the code, how do I get to visualize the database, as I would with, say, Phpmyadmin for MySql? The Lift community continues to impress in this case by conveniently documenting two ways: