Pretty simple approach : bananas is a content manager, like the forum is, or github is.
If I post on the forum something that violates the forum rules or some obvious laws, my messages will be removed and I may be banned from the forum.
If I push on github something that violates the github rules or some obvious laws, my contributions will be removed and I may be banned from github.
But on the forum and on github, I perfectly can share things that are not my own.
And there are both moderators and developers that can review what I posted, validate it, refuse it, or ask me for proof of legitimity.
Bananas could beneficiate of the same approach.
All contributors don't take the time to publish their work, nor filling all the changelog, description and other qualification fields correctly.
If any user can upload/fix files, changelog, etc. they could take the time contributors don't have.
A validation of the uploaded/fixed elements may garantuate there is no law violation, no broken, rules, and some consistency in the way the newgrf are described and evolve.
Some exemples of WTF versions :
bananas1.png [ 32.55 KiB | Viewed 1232 times ]
Aus becomes Auz ? Where are part 1 & 2 of Auz ?
Why explicitely obsolete files are shown ?
Should I use the other Au? Stations files ?
bananas2.png [ 3.48 KiB | Viewed 1232 times ]
Should I take the "av8 Aviators Aircraft Sets" or the "av8 Aviators Aircraft Sets" ? Why are those two file 2 different versions ? The old version is more stable ?
If there is a grf for "extra aircraft", why it there also a 9.8 ? Is that the same newgrf but newer ? Something else ?
bananas3.png [ 6.31 KiB | Viewed 1232 times ]
In the newgrf detail, I think it should be usefulle to display the list of versions of the newgrf. We could prefer to use an old version, the last released, the lasted beta, etc.