Real cooking issues
I see all these advices on making a ROM. But these advices and the issues they deal with are IMHO not the real issue. If you have a Nexus One phone and want to modify the Android OS there's nothing stopping you. It's "easy". It's all "there".
But what if you have a new Android phone which has proprietary driver code and made by a company that has NO interest in sharing it's code or make it easy for you to root your phone? Making ROMs for these devices is the interesting thing to talk about. Otherwise you can change the name on this forum part to: "Make ROM = *.android.com"
So these two issues are the most important ones IMHO:
1) Devices DO get rooted. So some people must know how to get there. I assume that there is no "one way" of doing this but it would be nice to discuss this and make some sort of a list on what to THINK about.
Many devices will never get rooted because the brand is despised here. That is why it would be good to have some general knowledge so others that ARE interested in these despised brands can take action.
2) You have a rooted device. You load a standard Android OS ROM. All proprietary drivers are lost and thus many features and maybe whole hardware units are unavailable to you. How do you locate and use unsupported hardware in your ROM?
I understand why many "elite" devs have a Nexus One since there are no propietary driver code in that one and rooting was easy. So the doorway to the Nexus One Kitchen is wide open. But what about the rest of the new Android phones that are out and will come. Why don't you discuss and explain the general thinking in rooting a device and finding/using hardware/features that are lost because of proprietary driver code.
Thanks for your time