SRL Archive - Senior Scripts and Snippets

Hey all, I've just got an idea about something that really used to piss me off (and I lost a lot of mad procedures/functions to it). I always despised the way that the svn worked, because it allowed multiple editing of the same file, which meant that multiple people could be making different things at the same time but not all of them check whether the original file has been modified since they started editing (or if they do, once they inject their code into the new script they fail to check if the script had been changed again (some slow coders :/)). This was a problem I really experienced a lot of when there was a random developing boom back in the day of wildy pking.. I also remember the entire srl repos was once sent back to the stone-age by some un-knowing person who uploaded a really old version in place of the new one.
So instead of one file which many people edit, why not create a file which loads scripts from a folder? (I mean it loads procs from the file and includes them, or have a template include file or something) Then no-one's work is ever at risk of being over-written by older procs.. Each file is it's own include. I don't know about you guys but I would have the script load scripts based on a name, something like "SrlScript_X" basically it would look for files with "SrlScript_X", include the procs and add a debug line that says "Credits to X, X, and X for the includes and to the Srl Dev Team" or something. But it would require somewhat of an index as well so maybe leave variables to be filled out like

ProcGenre[0] = "Fishing" //woodcutting, prayer, smithing, etc.

Then get the script to output an index file or something like that to help scripters find the procedures/functions they need but also allow devs privacy/space/peace of mind/etc. 'cause I remember how it was, too many devs crammed into one folder all scripting different things at once. Headache..
If there is no use for this in the dev community, release it for public use.. Surely that would create a large procedure/function database..
Sorry if you just read all of that, took a long time to write though, Suggestions? (no insults please)

Good idea although with the rate srl is being worked on these days its not really a problem lol. (Not that I would know since I havent worked on it for……nearly a year?)