|
Some very nice sentiments in here (and long posts!) and a great vision for where we should go. But before we can get there the base kitchen needs to be fully functional. The basic bugs all need to be fixed first (some already are). So, to get more organized on that front I suggest:
1. Take the stock AKU 3.5 kitchen (I believe this was created by Imcokeman based on helmi's AKU 3.3 kitchen).
2. Using the Wiki, compile a list of all bugs present in that kitchen. This gives a master list of the problems. For the ones that have been fixed already, provide a detailed description of the fix, cab or OEM of the fix, and credit where due). Unfixed bugs should have the names of people working on them (links to thread topics with discussion?). We don't move beyond this step until all of the known bugs are fixed or reasonably worked around (general consensus?).
3. Once all of the known issues are fixed, an OEM package for each fix is created and sufficiently tested. Then it is moved into the kitchen, but still in the OEM folder (I strongly suggest the OS and LOC folders are not ever touched). This will become the final "vanilla" kitchen for this AKU, at which point it can be plugged into that cool web page idea, and be used as the basis for everybody and their mother's own custom ROM.
As it has developed now, people are moving on to step 3 without step 2 having been completed (not that this paradigm even exists--I'm just making an observation), and that accounts for a lot of the confusion here. Whose custom ROM fixes which bugs? At this point in time we need to concentrate not on adding apps and making OEMs, but fixing all of the existing bugs! Once they are fixed, then we truly have a functional kitchen and can proceed with all the app OEMs and custom rom business.
There's my two pennies anyway. We need to walk before we can run.
|