cmi

I had several conversations around CMI at BADCamp a few weeks ago, which I have attmpted to summarize here.

First off I had a long conversation with yched about how to implement fields in the config api. There are several aspects to this that are tricky.

Field API : Config files layout

We are talking about a file layout like this:

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!

Last Wednesday I had a Skype conversation with Angie Byron (webchick), Francesco Placella (plach), Gábor Hojtsy and Jose Reyero to discuss how we are going to implement multilingual functionality in the Drupal 8 configuration system. For a little background, the configuration management system will be using XML files to store configuration. These files will be loaded into an 'active store' (the database by default, but pluggable) which will act as the source for configuration at all times.

We had a really productive IRC meeting last night, the log has been attached to this post. Highlights:

I will be attending spending a lot of time traveling to Drupal events in September and October, and I am hoping to run CMI initiative code sprints at all of them! There will be other initiative owners at the US events as well, so I would not be surprised to see coding going on around those topics as well. Our main focus here will be around the file-based config system and enhancements to the entity system. For those who are not local to these events, you can join #drupal-cmi on IRC to participate virtually.

I am going to start holding IRC meetings every other week to discuss and plan issues around the configuration management initiative. These meetings will be held every other Tuesday at 19:00 UTC. In real world terms this currently translates to

11:00 - US West coast (PST)
13:00 - US Midwest (CST)
14:00 - US East coast (EST)
20:00 - UK (BST)
21:00 - Most of Europe (CEST)

This week at DrupalCon London, all the initiative owners gave status updates on the progress they are making and where they currently stand. Unfortunately not all of them were recorded properly, but mine was so anyone who is interested can watch the video here

http://blip.tv/drupalcon/drupal8_full-5494012

The slides are also available here

http://www.slideshare.net/heyrocker/drupl-8-configuration-management-ini...

Hello everyone. When last we met we were discussing potential file formats for configuration management, and just as that argument was winding down I went on vacation for a month. Sorry about that. However I am back again and hopeful that we can wrap up this discussion and put the topic to rest. Before I dive into this I want to thank everyone for the feedback they have provided. There haa been an enormous amount of valuable information coming from the community, which is exactly what we have been looking for!

Welcome to another discussion from the configuration management initiative! So I believe that in the last thread we pretty much got everybody on board with the idea of 'We can use pure JSON as our file format if we use a hashed directory name and don't write the files by default.' This is great, however it then led to more discussion of 'Why are we using JSON anyways? Why aren't we using PHP/YAML/INI/LOLCODE etc.' Some good points were brought up in this discussion and I think it is worth hashing this out now.

First I want to thank everyone for their feedback in the last thread about the configuration management system. While it was long and hard, a lot of really good ideas came out of it. What I'd like to do here is summarize some of the points of contention and propose alternatives for further discussion. It seems there is a lot of agreement around the basic ideas behind the proposal and if we can work out the controversial pieces, then we are in pretty good shape to move forward.