SymfonyLive London 2015

Analizando el proceso de integración de Symfony en Drupal 8

Richard Jones  · 


Extracto de la transcripción automática del vídeo realizada por YouTube.

good morning thanks very much for coming today so this is the first time I've spoken a non Drupal event so it's a you know quiet ma not terrifying I that space i think i think the symphony community is quite nice and friendly as well and but what I

wanted to talk to you about today was where we how we got to where we are right now with Drupal so this is the story of symphony how Symphony became to be in Drupal a and I think more importantly this isn't going to be a a talk with loads of code in it

this is more about what the effect has been how we've managed to integrate the communities and what we actually need as the Drupal community from the symphony community so we're going to talk a little bit about what the effects on our community has

been and then a little bit on what does it really mean for you guys if if your are you know working in the symphony world at the moment so why did I decide to put myself forward to speak to this particular crowd well the first thing I want to talk about is

drupal's reputation problem I've worked with many many PHP developers many symphony developers outside of Drupal and and every single one is very very reluctant to come anywhere near what we do my aim today is to change one person's mind on that

maybe all of you but let's try for one let's start there and then I want to tell you a little bit about where we are with Drupal 8 Andrew plates been in development for quite a long time but it's very very close to being ready and then hopefully

we'll have some time at the end for some questions if you have any so the first part really is how did we end up with symphony in Drupal 8 so this goes way way back in history Drupal has been around since about two thousand and it's been working through

different versions and Drupal 7 is the one we're working with at the moment and in 2011 with Drupal 7 was already out at this point juries who's the founder of Drupal started to talk at the Drupal drupalcon Chicago about a different way of approaching

in Drupal 8 because the historic problem that we'd had was in Drupal 7 everything was committed by one or two people there was this massive bottleneck everything was patched driven it's a patch driven development so they patches had to be reviewed

and committed by one or two key people juries being one of them Angie Byron being one of the others so there was this massive bottleneck and development was really constrained by this so what was decided was that for Drupal 8 there was a lot when you needed

to do and what we were going to do is going to break the different challenges that we faced with Drupal into these key initiatives and they were going to be put together by different initiative leads so spreading out the load a little bit now I don't know

whether any of these types of problems will will come to pass in the sort of the symphony community as well but it was certainly one where we found that just having that central point was really slowing things down so we're looking at the configuration

management initiative and what that was about was that Drupal historically and right now in Drupal 7 very hard to you've got a bit of a mix of features and content a lot of the settings are in the database and it's very hard to move between environments

we also needed to modernize for html5 there was a that layouts needed improvement in Drupal as well in terms of how you build pages mobile obviously it you know certainly more now but in 2011 it was very obvious that mobile was where things were going and

that we needed to be well aware of that and of course that's exactly where we are today multilingual was always possible in Drupal but was actually quite painful to do so that was an initiative as well views was a particular module that allows you to do

lists of data and everyone used at every Drupal site used this particular module pretty much all the time and so it was it was decided that we would move that into core and then a focus on on web services in general so what I've done throughout here is

I've put some my new links at the bottom I don't expect you to read them but if you want to get the slides afterwards you can see a lot of the history because the interesting thing about open source of course is that you can see where these decisions

came from you can see the discussion that led up to them and when I've been working on on this particular talk it's been about digging back through history funnier when when was that decision taken how did how did that come about so the particular

initiative in my interpretation that really made the symphony thing happen was this one called whiskey which was the web services and context core initiative this was led by Larry Garfield oh I think he may knows and known as Krell on Twitter so he's very

well known in the Drupal community but I think also in a PHP community as a whole he took on this initiative and the goal of the the goal of the initiative was to make sure that Drupal was already for the mobile web so it was basically saying the web isn't

about delivering pages anymore which is traditionally where drupal that come from for us all previous versions so we needed to move to something that was about delivering data and it didn't necessarily care about what format that data needed to be in so

this is where the web services initiative was based so we needed to understand things like partial page layouts ESI these sort of things that are important for enterprise scale applications where drupal 7 was and is of course it's very much a largely procedural

language oh sorry larger procedural framework or CMS and we can't even decide what it is some people think group was the CMS some people think it's a framework there's real note there's no real answer than that but the code inside was very

much procedural a very little object-oriented code in there certainly no namespaces the whole autoloading was done by something called the registry in Drupal and it's very very hard to work with other frameworks so historically historically you know Drupal

spin around long time and there's very much been the not invented here syndrome in the community other definitely would say that now but going back five five or six years and then of course we've got ten years of legacy but although there's no

the there's the way Drupal major versions work we don't have to go to heat backwards compatibility between Drupal 6 and 7 for example but however lots of the code is brought over from one version to the next so there's no PS i'll 0 support

and i've got public honest with you i bet most drupal developers don't even know what that means so when larry was looking and the team that with Larry's working with we're looking at this it was clear that Symphony already had a lot of this

functionality available straightaway so this concept of symphonic Drupal didn't really stick but it was referred to at some point and Men introducing all of these different Symphony components into Drupal so the idea was that we would we would replace

[ ... ]

Nota: se han omitido las otras 3.571 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.