Working on integrating the Features Server feature into OpenAtrium. My intention is to set it up as another Casetracker Project type.

OpenAtrium provides a solid case tracker and documentation system, and is a natural fit for the infrastructure of a Drupal.Org-style project ecosphere. Integrating them will allow me to post Features I’ve created to a place where I might actually have a means to get feedback on my work, let alone provide support.

Project Status of OA Features Server feature

• Features Project as a Casetracker Project ✓
• Features Project automatically a Notebook ✓
• Converting Projects View to a Site/Group feature. [in progress]
• Trivial Modification of Features Server code to play nice with OpenAtrium and Atrium Casetracker .✓ [will ship with patch]

Conundrums

• Features Server feature uses Context 2.0, OA uses Context 3.0
• hook_views_default_views_alter() has limited to no best practices or examples I’ve been able to find, given it’s currently documented intention as a site-specific hook. Somehow I don’t think it’s role will remain in site-customization in the world of Features.

Terms: drupalopenatriumfeatures-servers