oxp verfier gives annoying warning about readme.txt for development with git repo

[LW-archlinux]

The oxp verifier gives a warning like

WARNING: apparent Read Me file ("ReadMe.txt") inside OXP. This is the wrong place for a Read Me file, because it will not be read.

I understand the reason but since I'm developing in a git repository it's much more convenient to put readme and license together with manifest and similar files on top level of repo.

Please silence the warning if the readme is in a git repo toplevel folder (recognizable by the presence of a folder named .git) .

[phkb]

Workaround: add the following line to the oolite.app\Resources\Config\verifyOXP.plist file:
Look for the "logControlOverride" and add in:
verifyOXP.scanFiles.readMe = no;

So it should look like this:

	logControlOverride =
	{
		// Note: only yes and no here, no inherit or $metaclass
		dataCache.rebuild.pathsChanged = no;
		
		verifyOXP = yes;
		verifyOXP.stage = yes;
		verifyOXP.verbose = no;
		verifyOXP.scanFiles.readMe = no;
	};

[oocube]

This warning should likely be disabled in the master branch and future Oolite versions for two reasons:

1. where else would one place documentation about the expansion? Hiding it down in the folder structure is less serving the cause than staying on top level. Keeping it outside the expansion might get lost also.

2. The index actually brings readme files back to surface:
   https://ooliteproject.github.io/oolite-expansion-catalog/expansions/oolite.oxp.Thargoid.Armoury/oolite.oxp.Thargoid.Armoury.html#documentation

It works good or bad depending on the documentation format. RTF is not my favourite:
https://ooliteproject.github.io/oolite-expansion-catalog/expansions/oolite.oxp.CaptMurphy.BreakableShieldGenerators/oolite.oxp.CaptMurphy.BreakableShieldGenerators.html#documentation