Software evolves over time as any technology. When people invent new things, they usually launch new businesses for those inventions. They patent them. They protect their intellectual property for as long as they can.
At some point, proprietary technology becomes so prolific, that the need for agreed upon standards becomes necessary. Edison wouldn't have sold nearly as many light bulbs if they didn't standardize the size of the sockets and the shape of the two prongs, among other more important things like voltage.
In a few hours, I'll be heading to Princeton University for my fourth DrupalCamp New Jersey.
This camp holds a special place in my heart because it was the first place that I spoke about OpenDevShop in public.
DrupalCamp NJ brought me out of my lonely freelancer shell and into the larger Drupal community.
Aegir Summit & DevOps Camp at NYCcamp 2015
This Thursday starts NYCcamp, which is gearing up to be a huge event.
This year they've expanded even more beyond Drupal to all free & open source technologies.
I'm on the plane headed to my 4th DrupalCon, and this one is looking like a good time.
So much is happening this year. Drupal 8 is getting closer and closer to release, more and more Drupal businesses and services are being launched, and we continue to develop our Drupal products.
While my session on DevShop wasn't accepted, I am personally involved in a lot of BoF sessions this year.
This project is simply something I wanted to do. No one paid for it. I built it in my spare time as a way to refine the knowledge I learned over the last few years about Symfony, Vagrant, and Chef. I want to grow this tool, but it takes time and a server, which both == money.
So I'm opening up a GitTip account to raise funding for development of hubdrop.io.
But before I do that, I wanted to formally introduce HubDrop to the Drupal aocmmunity.
Just going to DrupalCon to watch is awe inspiring. The amount of people there, all sharing one common goal: to learn more and grow the power of Drupal, thereby empowering themselves... it's all really inspiring stuff. There's more than a few reasons I keep coming back.
Time and time again the debate about "what is content" and "what is configuration" comes up. I think not often enough we talk about it in words but not in the intentions of what you are building. This article is just about content, because everything else is just code.
First of all, what is "Content", really? It recently has become crystal clear to me: