I agree some organization is needed at this point, as we have different people putting fixes in their own ROMs but not documenting what the fixes are.
This can be done in the Wiki...
- Make a master list of all the bugs present with the stock AKU 3.5 kitchen
- Underneath each bug, put the threads dealing with it, the names of the people working on it, and what has been attempted thusfar.
- Once a bug has been solved and tested, the bug should be marked as such in the wiki, and the solution described (at a minimum) with a cab file and/or OEM package containing the fix posted to the FTP.
I think the idea of creating revisions to the stock kitchen should not be taken lightly, and should be avoided until "fixes" are sufficiently tested (as OEMs or cab files) such that they are deemed fit for rolling into the ROM. Because the last thing we want to do is have to backtrack and revert to old kitchen versions when it turns out JoeBlow's Smartdialer fix only works during full moons.
OEM packages offer limitless ability to customize the kitchen, even for registry changes and the like. They take up a few extra k in the final ROM, but they avoid the problem of dirtying up the kitchen.
For new users all that needs to be done is keep a list in the Wiki of what the "essential" OEMs are that contain the fixes. It may be cleaner to roll them into the ROM, but you also increase the chance that there will be interactions or additional bugs created that will then be harder to sort out.