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.
Your point 4 has quite a problem with incentives alignment. You expect the SaaS vendor to spend resources in order to minimize your payment to them - their revenues. I can see why that would be somewhere among the lowest priorities.
Also, point 6. I understand where you come from, but you should also understand, that you are using release shared by several/many customers. If everyone had a veto power over rollout, nothing would get rolled out, at all. Therefore, if something gets broken, use your SLA, it is much easier to fix a specific bug, than delay the release.
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.
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.
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?