Features Kata for DrupalCamp NY

Events happening in the community are now at Drupal community events on www.drupal.org.
You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!

Drupalcamp NY Attendees!

Would you like to learn how to create and install site configurations with the Features module, and learn how to create a Feature for Open Atrium?

I'm going to try a "meatspace Kata" - we all move forward together through a series of "forms". For this Features Kata, here are preparatory resources and instructions for prospective attendees.

INTRODUCTION

In this Kata, we will cover the following forms:

  1. Creating a feature on a default Drupal installation
  2. Exporting and Importing the feature on Drupal
  3. Modifying that feature for Open Atrium, and
  4. Installing the feature on Open Atrium. 

As a KATA, this will involve moving through steps together. To prepare:

  1. DISTRIBUTIONS: Prepare a default Drupal 6.x installation and a default Open Atrium installation either on your laptops or on a server someplace.
  2. ACCESS: Be able to write to sites/default/modules.  It is optimal if you can run INSERT queries on this database for full benefit.
  3. MODIFICATIONS: we're going to build a feature and then export it. For your Default Drupal installation, enable:
  • FOR ADMINISTRATION
    • Administration Menu (that's how I'll navigate)
    • Admin Role (so you can use modules Features enables)
    • Demo Site (so you can take snapshots and move back in time)
    • Features (obviously)
  • FOR CCK
    • CCK Import Custom: Imports previously exported CCK data.
    • Content: Allows administrators to define new content types.
    • Content Copy: Enables ability to import/export field definitions.
    • Node Export: Export sample content
  • FOR VIEWS
    • Views: Create customized lists and queries from your database.
    • Views UI: Administrative interface to views.
  • FOR OG
    • Organic groups: Enable users to create and manage groups.
    • Organic groups Views integration: Highly recommended.
  • FOR COMMITMENTS (Our Feature)
    • Date API: A Date API that can be used by other modules.
    • Date: Defines CCK date/time fields and widgets.
    • Date Popup: Enables jquery popup calendars and time entry widgets for selecting dates and times.
    • Date Timezone: Needed when using Date API.
    • Flag: Create customized flags that users can set on content.
  • On Friday (I'm doing a walk-through test Thursday afternoon, so might change these), please download these required files

    Also download the Open Atrium distro and these additional files. See http://netsperience.org/content/blog/drupalcampnyc-7-125 for details

Begin the Kata.

=========================================

From Peter's Post:

Bring to Camp

  • Your Laptop
  • Power Strip (there are outlets, but not enough for all so power strips will be most appreciated)
  • Make sure you have the downloads described above on your computer and handy
  • Make sure to attend one of the installfest options above.

Schedule on Camp Day!

Detailed schedule will be decided barcamp style with a community discussion starting at 10 am (along with breakfast). Hands-on Intro will definitely be one of the first to start. So specifically as it relates to the hands-on intro here is the schedule on camp day:

  • 9:00 am to 10:00 am - Installfest
  • 10:00 am to 11:00 am - Community decides full day schedule
  • 11:00 am to 1:00 pm - Hands-On Intro
  • 1:00 pm to 6:00 pm - Additional sessions (many options!)

See You There!

Comments

How did this go?

gusaus's picture

Just wanted to drop a line to say thanks for picking up on the Dojo/Kata theme for DrupalCampNYC. It's exciting to see a core group of contributors coming together in the New York area. A few of us have been talking via email, but it would be good to open up the discussion on how this went and where we can go from here.

Personally, I think the format used for the camp (also described here) is a good one for both virtual and in-person collaboration. This could work for a master class where we break down each component of an entire development project into Katas (somewhat similar to this draft in progress) to specific feature development or bug fixes.

It's probably going to take a bit of trial and error to solidify a format, but one way to kick start would be to form a Kata around the current effort to fix critical bugs for D7. Could we do a virtual daily Kata to coincide with this?

Gus Austin

I see a Kata as structured, repeatable - no unknowns...

bramface's picture

So I'm not sure how you'd use one to fix bugs!

-Bram

We're taking some liberties with the terminology...

gusaus's picture

We're obviously taking some liberties with our Drupalization of Dojo and Kata terminology. Assuming there is some sort of structure to the daily virtual code sprints (irc.freenode.org #drupal-contribute from 11AM-noon PST), we could probably craft a Kata to help facilitate and get people involved?

Gus Austin