lsmith77

Also what is up with “These external links will take you off GitHub to pages we haven't verified, so beware.” ?

You can put links to stuff in all other places without warnings. Now ok I guess they can argue that most other places do not entail with people sending money. But why not at least keep a list of “trusted” places?

here at Liip, we usually tend to give people full access, so roles are not so relevant, except for my wish to have "billing users" so that we could create a 3rd party like cleanshelf a billing account so that they can extract only the data relevant to their service.

Beyond that I really love the usage based billing approach of Slack, where we could just give all our employees access and we get billed on how many actually use the service. Access would be managed via Google Auth or SAML.

SAML is kind of the solution that is now pretty well supported in the SaaS world. So you "just" have to setup a SAML provider with your LDAP for authentication.

no .. but we choose this different terminology because management is usually associated with decision power, where as explained in the blog post, I just help people get whatever they decide themselves.

just to clarify, Liip is not affiliated, we don't get any kick-backs and generally we do not accept kick-backs anyway (if we do get a kick-back for one of our customers, we hand that kick-back to the customer), specifically because we don't want to recommend something simply to get direct financial gain.

Docker reslly seems to gain a lot of momentum but there is still a need to mature the tooling around it, this looks like a great step in that direction.

Semi-related see also http://blog.liip.ch/archive/2014/06/01/how-i-use-docker-on-o...

indeed .. the numbers should be even better now.

I think the first step would be that the Wordpress core developers start to mingle with the PHP community. I simply have not met a single Wordpress core developer at any PHP conference and I tend to go to 6-10 a year in various countries around the world.

I have also not seen any Wordpress core dev participate on an php-src internals discussion let alone something like the Framework Interoperability Group that outs out the PSRs.

Note I guess it might actually be that I did come across a Wordpress core dev, but maybe they just didnt identify them as such.

But without communication the chances of collaboration are low and without collaboration imho its going to be hard for Wordpress to identify and assess the potential for new directions.

That being said, Wordpress is king of the hill and it at least right now there is no indication of this changing. So changing might just have a ton of risks with maybe little chance of success. Then again I guess AOL once thought quite similar about their position.

this is exactly the kind of scenario we aee trying to address with the Symfony2 CMF: cmf.symfony.com

ibm thingi was called "project zero" btw i hear facebook is also looking to move to the jvm to ease some troubles with their hiphop approach

well for Symfony2 there were two major sites running on Symfony2 pre alpha versions (2 years ago) .. and several others more in alpha. Obviously these teams had to spend a fair bit if time keeping up with all the BC breaks before the stable release, but it helped a lot in ensuring that Symfony2's stable release was ready for the real world.

Magento is non the less one of the most popular shop solutions. I also see it having lots of issues, but maybe the fact that there isnt anything better shows that it isnt so easy to do a good shop.

Well I want to make sure that nobody assumes that just because I am not aware of any major website using ZF2, that its necessarily a fact. Quite likely nobody in the ZF2 community heard that both opensky.com and exercise.com launched on Symfony2 2 years ago.

sure .. they also both use PHP .. what is your point? just because some arguments also apply to ZF2 do not make them non applicable for choosing Symfony2.

however he also mentioned a few others, like a huge list of applications migrating to Symfony2. that being said ZF1 at least at more apps based on it than Symfony 1.x. However a list of Drupal, ezPublish, phpBB etc is indeed quite a big shift that Symfony2 managed to pull off.

also Symfony2 has had 2 major websites in production for 2 years now and a stable release for over a year leading to 1600+ Bundles (of course I would assume 80% are of questionable quality). I am not aware of any major website today using ZF2 and the number of available Modules is much smaller.

the fact that Symnfony2 has a lot more contributors than ZF2 can also not be disputed.

the fact that the lead developer of ZF2 says that when creating their new Form API he didnt even look at the API already in Symfony2 also shows that they do in fact have a reinvent the wheel mentality.

that being said .. ZF2 does have some philosophical differences that might make it more viable for some users with specific preferences. f.e. ZF2 ships with autowiring and a view layer out of the box. these features require 3rd party Bundles for Symfony2.

so my point is .. if you really want to position ZF2 as an alternative to Symfony2 then please focus on what makes ZF2 unique. that would in fact be something productive. listing all the things ZF2 can also do is legitimate as well of course, but can hardly be used as criticism to someone talking about the advantages of Symfony2 unless you can illustrate that the bulk of all PHP frameworks out there provide these capabilities and characteristics.

I think its legitimate to note why someone doesn't want to go to conferences anymore. Now if organizers will act on that is their own decision.

But if nobody ever speaks up, then it implies that everyone is happy with things are going.

Its sad when someone introduces you to a new community, telling you how much they love to drink. Then when you reply that you don't drink, said person tells you .. you know actually I don't drink either.

First up, very few of these parties are advertised as a place to taste alcohol. They are advertised as get wasted as much as possible cause its cool. And its pretty much every conference I go to.

But at any rate, I think the "original" purpose was the same as why people drink when they are back at home: To reduce anxiety and to make it easier for people to get to know each other. I think that is a worthy goal since to me the main purpose of conferences are to network, the talks come second.

But I know the same deal from sports tournaments where its also play hard on saturday, get drunk on saturday evening, play hard on sunday. I just sick around as long as there is someone not drunk to talk to, or the DJ doesn't suck so that I can dance. So it goes.

I also recently wrote on my Facebook page, that this is yet another form of excluding people. Especially if the only non alcoholic drink is water and pineapple juice. But yeah the difference is that nobody has seriously (well jokingly they have) implied that I am a worse programmer because I don't drink, where as it appears to happen still way too often that women are assumed to be booth babes or n00bs.

But getting smashed also has the tendency that people do stupid things and when a bunch of guys feel like they totally own a place in numbers while being totally drunk they might also start thinking they can "own" that female geek hacker. So yeah maybe there is where we get back to the sexism debate.

Scenario: A single backend, providing content for an ever growing set of front ends (desktop, tablet, mobile in various permutations). Content editors need to ensure things look good in all output formats.

Solution: Content editors get a button to preview draft content in all front ends. This opens up a tab for each front end. Front end uses the backend session to get permission to retrieve the draft content and loads up create.js during the rendering.

Using CORS the frontend is configured to send back any changes to the backend directly. Title width optimization can be done inline, all related pages can be updated right away.

All the front ends need to be able to do is identify an admin and to be able to pull the draft content and then include create.js. That is it. Booom, the front end supports inline editing. All your front ends support inline editing this way!

btw some more info can be found here: http://pooteeweet.org/blog/2046

I am mind blown by this service. Doctrine2 is being tested against SQLite, MySQL and PostgreSQL as well as PHP 5.3 and even PHP 5.4RC1.

http://travis-ci.org/#!/doctrine/doctrine2

Was green earlier today, guess someone will hopefully fix the red tomorrow morning :)