drupal 8

Referring to my document that tries to cover the topic on how to build a perfect multilingual / revisionnable system that allows to finally make content translation unneeded without regressions for typical advanced usecases in Drupal 8.

http://techblog.md-systems.ch/blog/2012-06-drupal-8-multilingual-and-rev...
It finally went bigger than intended, but couldn't find too much to strip.

Feedback as comments appreciated.

I have posted a discussion issue in the core queue to attempt to get some consensus around the following topics:

• How much information should be stored in each file?
• What is the naming convention for configuration files?

The issue is at http://drupal.org/node/1479492

I recently posted the following issue to remove file signing from the Drupal 8 configuration system

http://drupal.org/node/1444620

I would love for some feedback from the security-savvy members of this group as to whether this is a viable option.

Thanks!

Hey Guys,

I talked about this at the meetup last night - Dries is going to be giving a webinar this week presented as a "fireside chat" (I expect there to be some classical music, egg nog, a pipe, and at least one person dressed like Sherlock Holmes). The talk is this Friday. He has posted it on his blog:

http://buytaert.net/drupal-fireside-chat-core-development-process

Sign up and attend!

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:

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)

Last night, as I read through the conversation that is happening on the "Make core maintainable" issue (http://drupal.org/node/1255674), I couldn't help but feel that while this conversation is important, it may be the wrong conversation to be having at this time. I am glad this conversation has continued coming out of DrupalCon London, but I feel like we haven't answered the fundamental question of "what is Drupal?", which may help steer the conversation in a direction that will help us select the features that really need to be in core.