configuration management

Hello everyone!,

As announced during the past presentation of Patterns at Drupalcamp London (http://2013.drupalcamplondon.co.uk/session/automating-drupal-development...) version 7.x-2.x of Patterns has just been marked as the recommended one.
Several sections of the documentation have been updated according to the new version and a new section offering a more detailed summary of the new features has been added as well: http://drupal.org/node/1933180

We look forward to hear your feedback, please do not hesitate to open any issues in the list.

I've updated CMI info thanks to Greg, check it out here: http://drupal.org/community-initiatives/drupal-core#cmi

He's working through some pretty big architecture options, and the community has been awesome about stepping up and supporting this initiative - so huge thanks to you all for keeping so many balls in the air!

Configuration Management

Greg Dunlap (heyrocker)

Status: Green

Headlines

• Had a meeting with Gabor, Plach, and Jose about multilingual considerations in the configuration system. This discussion has been summarized at http://groups.drupal.org/node/185609.
• Had a code sprint at the Pacific Northwest Drupal Summit with beejeebus, msonnabaum, webchick and ksenzee. We worked on some implementations for the system and ksenzee wrote tons of awesome doc blocks!

Update on this format: NEW! Props section. The Initiative leaders were excited to start saying thank you to people who are going the extra mile. We do want to thank everyone who contributes, and not just these people, we'll be singling you out occasionally for an extra big thanks.

Configuration Management

Greg Dunlap (heyrocker)

Status: Green

Headlines

What this is about:
We've been hearing a lot from the community about wanting more transparency with regard to the Drupal 8 initiatives and their advancement. Every two weeks, the Drupal 8 initiative owners, along with Dries, webchick, and a team of project managers have “scrum of scrum” calls where each person goes around and talks about what they worked on since last time, what they’re going to work on for next time, where they’re blocked, and how the community can help.

What this is about:
We've been hearing a lot from the community about wanting more transparency with regard to the Drupal 8 initiatives and their advancement. Every two weeks, the Drupal 8 initiative owners, along with Dries, webchick, and a team of project managers have “scrum of scrum” calls where each person goes around and talks about what they worked on since last time, what they’re going to work on for next time, where they’re blocked, and how the community can help.

In DrupalCon we had BoF about DOG and aspect of configuration management (later CM) came up.

What we need to do related to configuration management is to decide what are our goals.

What i mean by configuration management is that when site is being deployed to certain (or several) server (local dev, testing, live...) DOG can make needed changes in order to apply those settings. If you understand configuration management differently or have different need/use case for CM give us your opinion.

So basically there are (attleast) two open question.

Hi, I'm developing a Multisite module that has some shared tables. I have settings that I've been using system_settings_form() for, but now I want to add more configuration options. The thing is, they should be shared as well. I don't want users to have to duplicate the settings over and over, so I'd like to store these configuration settings somewhere else.

One of the key aspects of solving the configuration management conundrum is identifying how to uniquely identify data between servers. To this end I propose implementing UUIDs in core for the identification of content, and to provide an API through which UUIDs can be generated and added use by contrib modules. While we are still talking through many big picture architectural issues, I think that it is possible to get moving on this and several other tasks to get the real work started. So here is my proposed game plan for this, created after some discussion with Dave Hall (skwashd) who has put a lot of work recently into porting the UUID module to D7.

hi,

i've just created a Settings Audit Log module.

http://drupal.org/project/settings_audit_log

it uses a trigger on variable to log all changes by user.

looking for reviews, feedback, and ideas for modules to build on top of this using the audit data.

cheers
justin