I'm well aware of the situation as I was the one who took over handling it from Buddah. I've read every post in this thread thus far.
I have two choices; protect the people who do the work or protect the people who wrap up all the fixes in to one easy to download package. Personally I choose protecting the creative developers rather than the folks who are willing to do the gift wrapping.
If the fixes are really easy then get off your backside and do them yourself and provide them to Zen's project. If permission is needed then help Zen get in contact with the relevant people. This mod could go back up now if Zen just had a list of those files that were free-to-use and those files he had permission to use and he removed anything else until such time as he did get permission. Once I get the go-ahead from Zen that everything in the file is as it should be it can go back up.
With respect, it has actually taken quite a lot of time and effort to create the Compilation Patch. What's more, people have been actively contributing unique fixes to the patch that may otherwise not have come about, so it has catalysed as well as compiled. It has done its part to provide value to the nexus and many people appreciated it, showing so by voting it for file of the month (and if it's the case that this is against the rules, you might want to look at some of the other mods in the running for file of the month). I'm sure it wasn't your intention to denigrate my efforts, but I do I feel rather hard done by if this is your attitude towards me.
@Povolhulo - I agree that it would be preferable if a dedicated team worked on a bug fix patch, and that is exactly what I was hoping to build, albeit a loose one. A few extremely decent members had already started to emerge and be extremely helpful in terms of developing the patch. In terms of quality control, I actually do check through every fix when I compile it, and any dirty edits I remove. Where possible, I check every fix through testing myself (this is hard having not completed the game yet), where this is not possible, I request help, which so far has been readily given.
And as you say, as Bethesda/Obsidian announced a "comprehensive" patch is in the pipeline, it would make sense to stop work on the patch for the moment anyway. In the meantime, I should hopefully have gotten all the required permissions for the patch to continue on from before.
For what it's worth, I don't think there should be any 'default' option when it comes to choosing file restrictions when uploading a mod. People should be actively encouraged to determine how they wish their mod to be used by the community. What's more, allowing search criteria that can find mods by permission type would be incredibly useful, and hopefully avoid situations like this from occurring again. I admit full responsibility for not adequately acquiring proper permissions for all the files included in the patch, but I thought (wrongly) that because of the nature of the mod (a bug fix mod) and because of my effusive credits and thanks I gave in the read me, this would have been overlooked. I still maintain had it not been for the bitter actions of the commenter, it would have continued to have been overlooked. But that is by the by. We must cover our asses, otherwise ill meaning people may use the rules against us. It is a sad lesson, but that's the way it goes.
Anyway, here's a poem for everyone.
Débacle
D. H. Lawrence
The trees in trouble because of autumn,
And scarlet berries falling from the bush,
And all the myriad houseless seeds
Loosing hold in the wind’s insistent push
Moan softly with autumnal parturition,
Poor, obscure fruits extruded out of light
Into the world of shadow, carried down
Between the bitter knees of the after-night.
Bushed in an uncouth ardour, coiled at core
With a knot of life that only bliss can unravel,
Fall all the fruits most bitterly into earth
Bitterly into corrosion bitterly travel.
What is it internecine that is locked,
By very fierceness into a quiescence
Within the rage? We shall not know till it burst
Out of corrosion into new florescence.
Nay, but how tortured is the frightful seed
The spark intense within it, all without
Mordant corrosion gnashing and champing hard
For ruin on the naked small redoubt.
Bitter, to fold the issue, and make no sally;
To have the mystery, but not go forth;
To bear, but retaliate nothing, given to save
The spark in storms of corrosion, as seeds from the north.
The sharper, more horrid the pressure, the harder the heart
That saves the blue grain of eternal fire
Within its quick, committed to hold and wait
And suffer unheeding, only forbidden to expire.