Promote Docvert module to full project

I'm really happy with the architecture I've reviewed on it last night.
A bunch of Drupal style issues have been introduced (recently?) but that's trivial.
I've got patches ready for that already.
Also, the object throws a number of exceptions that the Drupal side doesn't catch properly, I have patches for those of those that I've encountered also.

The code can work as promised, and is going to be a valuable module.

I DO have to look at it with an eye to security (have not focussed on that yet) but I have no great concerns about that.

I'll do a fresh once-over it today, pulling from d.o git now ...

.dan.

Very happy to see this, as I had looked into creating a docvert module about 2 years ago, but the project itself was in a little disarray at the time, have been wondering since the conversion to Python how this might work. Will definitely help you guys review, not sure if I'll get anytime for patches though. Keep up the good work.

This weekend:
+ Full coder.module style and layout review. All whitespace and boring stuff like that, no significant code changes
+ Minor additions to help text, form field descriptions, API docblocks
+ Some form validation additions to help test the target docvert server is valid
+ Huge amount of help and install instructions, now in the /help folder for use with advanced_help
Overview
Setting up the server, and troubleshooting notes I made
And for fun:
How to set up a stand-alone EC2 virtual web appliance to do docvert for you

I didn't find any security or general code issues worth worrying about in my per-line review of the code (though I didn't test everything either).
I'll let the dust settle on this, then maybe we can talk about some adjustments to the process I see as being helpful - specifically making the documents get processed on request (and batch API) rather than on every save.

Shall we promote?

Promoted to full project at http://drupal.org/project/docvert
... mostly so the new documentations and HOWTOs I'm writing can refer to a good URL.
Also because .. it's working for me now, and I'm actively getting this going.

Note, this MAY put anyones git repo out of date - according to the notification I got anyhoo.

You are all best to get a fresh checkout from the info on the project page it seems...

Did you go ahead and create a development snapshot/release? If not that would be great, if so then I'll just look for it to show up.

Not yet. There's still a few things I want to pack into it.
I've found a difference in the API between docvert server versions 4 and 5, so I want to work around that.
And I have a Feature that can be deployed as a usage example and test case, I'll get that tidied up and then bundle release v.1.0