5. Centralized Configuration
• Code Sprint in Denver
• Two-stage storage
• Standard format
• Replace variables
• Security
• http://groups.drupal.org/node/155559
6. Entity API
• Move entity.inc to a module
• Introduce CRUD API
• Core Conversation tomorrow at 11
• http://drupal.org/node/1018602
• http://groups.drupal.org/node/133579
7. Content Staging
• UUID + Entity API = Profit
• First patch in queue for API
• Then need to work it into Entities
• http://groups.drupal.org/node/145614
8. Problems
• Discussions are hard
• Not timeboxing enough
• Need to be quicker on the trigger
9. Next Steps
• Code is gold
• Update sandbox code from discussions
• Move into real world implementations
• Continue UUID work
• Keep talking and pushing forward
10. Next Steps
• Code is gold
• Update sandbox code from discussions
• Move into real world implementations
• Continue UUID work
• Keep talking and pushing forward
Core conversation in Chicago\nDries asked me to do this\n‘Oops’\n
\n
Did a lot of research, came up with a battle plan\nContent vs configuration\nStill evolving\n
Held a code sprint in Denver two months ago (participants)\nCame up with plan for two-stage configuration\nLots of discussion happened, most of it around .php files and file format\nFile formats - XML (I think it is rightbut it is also important to move forward)\n
Moving forward\nTalk to Peter and/or Fago and/or catch\nThis is an enabler for content staging\n
\\\n
Our tools suck\nWhile we need community buyin we also need to move forward more quickly. \nI’m new to this, and I’m a talker so online discussions are hard (thanks Angie)\n\n
Keep pushing forward - this is new and we’re all learning\n\n
Keep pushing forward - this is new and we’re all learning\n\n
