Status of this fork

[wheelsandcogs]

Hi, is this fork in a usable state? Any major known issues?

[adamelso]

Hi there :) I've been revisiting this project a few times but unfortunately am mostly involved in much larger projects that don't use the library. I am currently considering looking for a new owner as my access to an Exchange server will be limited and knowledge of how EWS works is quite sketchy anyway.

Ideally I would like to start bringing in more modern coding standards to this library. I'd like to introduce behavior driven development, though it difficult to test without an actual connection to an EWS server.

I'd also like to use introduce a command line utility, split the library into different packages: php-ews/php-ews, php-ews/ntlm and php-ews/data-types and add dependencies on other packages, likely one that would handle the filesystem like symfony/filesystem and another that handles cURL messages like guzzlehttp/guzzle.

Apparently it does work for a few people, and has been download a couple of times from Packagist https://packagist.org/packages/php-ews/php-ews

[wheelsandcogs]

It seems there are quite a few forks of php-ews aimed at modernising the codebase - it's a shame that the efforts haven't been pooled towards the same fork. I'll give this one a go and see how I get on, cheers.

[adamelso]

Just to give an important update, I am currently in the process of transferring ownership of the php-ews/php-ews package on Packagist to James (see jamesiarmes#253) as any future activity on this fork from me may be unlikely and perhaps better done as a separate library entirely.

Anyone currently installing this forked version via Composer may want to change their composer.json to read:

"php-ews/php-ews": "dev-master#2ab3137bca6d8cc9690d6d4d46b53e75111457cb"

When the official library is ready to support Composer, switch back to dev-master or any other version constraint and apdat your codebase to it.

Many thanks,
Adam