Erik:
We had our first Austin Apps sprint last week and got quite a bit done. We had 12 people from Phase2 Technology, LevelTen, Four Kitchens, Mediacurrent and Pantheon all had people at the sprint. Thanks to Four Kitchens for helping us provide a space for the Sprint.
Chris:
There are a lot of approaches to dealing with the complexity of large software projects and a little rule I use helps me make sure that fixing one bug report doesn't result in another.
Joshua:
If scope creep at the end of a project is unavoidable, how do you prevent it from affecting killing your budget, torpedoing your launch, and making your developers hate you for dumping an eighty-hour task on them the week before launch?
Sharon:
Over the years I’ve watched my wireframes go from scribbles on the back of a napkin to architectural-looking blueprints complete with gradients and icons and detailed pagination mechanisms. And, truth be told, it saddens me. The spirit in which wireframes were intended, way back when we first realized that websites had to be planned out, was to get ideas for content down on paper before we started plodding away at development. They should inform, not dictate, the information architecture, content development, and visual design processes that follow.
Felix :
Drupal's nature of using hooks to allow functionality override by contributed modules, by the same token it is difficult to have data available between different hook implementations during the request process, specially if they are overridden. Simply we just need to have certain values available overall the system, once they are set.
David:
In September we released a new beta version of Tao for the first time in 11 months. A lot has happened in those 11 months. Tao changed hands along with several other modules and themes, and it’s taken us some time to get up to speed on all the new code that we have committed to maintain.
Karen:
This weekend at DrupalCamp Atlanta, I had the pleasure of presenting with Jay Callicott from Mediacurrent on how to build an App for a Drupal distribution. Ok, so it wasn't really 8 minutes, and it wasn't exactly live - it was more like the cooking show kind of live -- but it did cover all the steps of building an App for a Drupal distribution, start to finish.
Shawn:
These days, it's hard for us to walk across a conference lobby or leave a meeting without someone saying "I have a great idea for an App for OpenPublic." A lot of people are thinking about ideas for Apps or translating an existing Feature into an App. For those of you thinking about creating an App, we want to lay out the internal process we use at Phase2 as a suggested starting point for your own App.
Tony:
Since taking over Open Atrium we have been asked about our roadmap and pathway forward. Jeff's recent interview with Open Source CMS Pro (http://opensourcecms.pro/drupal/future-open-atrium/) lays out some key points and objectives we are looking to achieve towards this effort. We are also looking to the Atrium community for new features being developed, such as Nuvole's recent feature, Atrium Folders (http://nuvole.org/blog/2011/may/25/apps-open-atrium-atrium-folders). As Jeff notes; "One of our goals for supporting OA is to find better ways to highlight and make findable the excellent features that others are building."
Jeff:
The discussion has started. Whether you're wondering where apps fit in the Drupal ecosystem or just want to get started building one, you've got questions about apps. We're ready to get started, so let's get to the questions first.
