Joomla! and Beyond 2013

El estado actual de Joomla!

Andy Tarr  · 




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

let's see if I can trip over some of these balls oops okay um hi my name is Andy tar and I'm going to be giving the the first keynote here on the state of joomla I've actually relatively new to joomla compared to a lot of other people I started

in the fall of OA twenty Allah was actually joomla and I got to start on 1.5 rather than Mambo or 1.0 so I didn't go through some of the pain that some of the others did but I've been in the IT industry for about thirty three years now and I've

been doing web development since the since the 90s so I've been in the field for a while I first got into very involved in joomla itself as part of the google summer of code in 09 and i had done a few sites before that had written an extension or two and

then really got into it and started working on the project itself in the summer of 09 when I wrote the accessibility template for 1.6 Hathor which was great in 2.5 and is still around in 3.0 though it's not you could use a little help now okay and currently

I'm working for meta scale in Sears Holdings as a joomla / PHP architect so I get to do joomla in my mine or mille life so we're going to go over a few things today on on where joomla is and what's happening with it will be going over the code

and the people since the people are a huge part of what joomla is and where it's going we're going to go over the adoption of joomla how are we doing in the marketplace and then finally we're going to go over the roadmap I should have mentioned

my introduction that I'm on the production leadership team for joomla which is the group that's responsible for the code of joomla and we published a roadmap last fall that showed where we want to go with the actual code on joomla so what I'm going

to be doing here is sort of a status report on going over those 12 items and where we are and what's happening with them so we'll start with the code it's always the fun part for me and how many people here are developers of some sort or another

yeah that's what I like to see you go to a joomla day and it's like two people raised their hand oh okay so just a little tiny bit of history it started with the CMS and that gave us just about everything we wanted and the big part of it kind of the

heart of joomla was the joomla library and so a couple of years ago sorry get this working and so a couple of years ago we decided to pull out to that library as a platform so that additional things could be done that so wouldn't be limited to just the

CMS and we had the platform project come out and that was a really cool experiment and one of the reasons we did it was that we wanted to be able to add additional things in the platform that the CMS didn't really need so that we could kind of expand the

use of that and make it easier to do additional things with web development that weren't necessarily content management now though we've found that there it probably wasn't the ideal solution it got us further along but we found that the CMS had

problems because we needed to make some changes but those things were in the platform but the platform didn't really want to change it necessarily because oh that's just the CMS but it's not necessarily what they want for everything and then they

found that they wanted to make some changes to make it more widely adaptable and they were held back by what they needed for the CMS so what has been decided recently is that we're going to be reabsorbing the platform back into the CMS so that if we have

bugs or changes that affect the joomla library itself we can just make them directly when we need it and then we are creating the framework which is taking what was the platform pulling it out taking out any of just the CMS eccentric things in it and releasing

that separately that's going should be released this summer sometime it's nearly there and ready to go and by doing that the framework will be able to add additional things that you really wouldn't be able to do when you've got the CMS on there

just because of the rate of adoption that we don't want to keep making major changes to the CMS too quickly for everybody so this way they can go ahead and do that in the framework it'll also be set up so that we can grab pieces of it back rather than

having to grab the entire thing we'd be able to just say oh that's a nice little feature that they have there and everything will be independent so we'll be able to just grab little bits and pieces of it back in and use it within the CMS now our

code is architectural e strong that's one of the really nice things about it if you would go and you compare it to say WordPress or Drupal there's some really good things about it and it's getting stronger we've got our issue tracker had a

lot of old issues in it that had been there from you know 1.5 and just kind of kept hanging on and we've recently gone through and we've cleaned up a lot of those so there aren't as many of those hanging or we're also doing a little bit more

in how we're going to be doing the the releasing currently as most of you probably know we've got the repository on github and we've got a master branch there and we've always had a stable branch policy so that at any point in time if we have

two we've got a stable branch that we can release it so you know if a security issue comes up or something that we need to just put something in quickly and do a quick release it were at a point where we can do that however we're wanting to get into

more of doing testing and some automated things and so it makes it a lot easier if we add an additional step and we have a staging branch where we're putting our commit sin and the staging branch will will also be stable but we can then run a number of

automated testing tests on that and when it passes everything we can go ahead and merge it into the master branch and that'll make things even more stable so in the next couple of weeks we'll end up starting to do pull requests against the staging

branch as opposed to the master branch and there'll be more information out on this as well so we just had release 3.1 come out and one of the nice things about really 3.1 is we managed to get in there a new feature that people have been asking for for

a long time which is tags so how many people were glad that tags got in okay okay good it was just one we didn't get a lot of different things in but what we got in was good we're also looking at making another change coming up in a minor release and

that should make it easier to do your upgrades that right now if you go and you install let's say you're going from 2.5 and you want to go to 3 or you're wanting to update some extension there are a number of pre checks that happen in if you're

installing a new version say of joomla but if you go through the one click update you don't necessarily see those pre checks so it's not checking to see our you know magic quotes off or on and you can get into some trouble that way so one of the things

that we're doing is we're putting all of those pre checks right into the one click install and the way we're doing it we're going to be adding in and this is partly going to be staged in in but the ability that you would be able to do dependencies

[ ... ]

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