question about a code review for the admins here

I recently did a review of a new module applicant http://drupal.org/node/1379794#comment-5514576 and found that the linkedin module that this person's module depends on doesn't use the library api and the Oauth.php library that it includes isn't namespaced and I cannot even load up this persons module or the module that it depends on (the LinkedIn Module) -- I get lots of "can't load a class twice" type of errors. I don't know if the fact that the module this person is depending has this flaw should hold up his application?

I cannot review his module of course since I cannot even load up the linked in module. Should I just let somebody else review his module? Should this applicant take it upon himself to fix this problem, working with the maintainer of the Linkedin Module?

Actually it may be a larger mess. Perhaps the LinkedIn module should require the Oauth Module, and the Oauth module should be properly using the libraries API module.

Anyhow I didn't want to leave this candidate in "needs work" status unnecessarily, if it truly isn't their problem? It seems the Oauth.php file they require has lots of Class names that conflict across the drupal.org code base.

Thanks