@H-Hour, so, It's the worse situation cause releasing a game that run on a PC and a documentation software that runs on hosted server is really different in terms of security risks. Player computer may not access WW web, i will do...
Let say that i'm not seeing the game as the addition of several individual artwork but as consistent piece of work with at least enough unity to create a new distinct artwork that loose its meaning if only looked on the texture level. The best proof is that the textures and artwork are constantly changing (+90% of commits) but we always recognize the game. So i think this should do because i'm not trying to copy the rifle texture to remake an other rifle in an other game, but i'm trying to copy the 'feeling' of having a soldier carrying a rifle in the game, so i just need current copyrights-holder of the game authorization. Does not sound convincing? the problem is that you will have to refer to a local country law to know if it's acceptable.
What i will do, is to have a lazy approch an provide a contact form to request removal of content that is causing problems. I guess it will do a fair enough use for this form no being used.
---
t i'm not planning to do something rely extraordinary... i've almost did a browsable techtree, i will then implement a tool to compare weapons like the one on ufoai/contrib/script/generate_comprehensive_weapon_table.py with little more pragmatic approch then maybe a tool to comment base layout or something for UFO or whatever... maybe mods that were discussed on the forum ... if i'm still having the time.