10.1 nightlies are now officially supported for the standard definition Kindle Fires, So if you're curious about rooting and flashing ROMs to get a more stock Android experience, here are the official links for them, you'll still need to go about installing TWRP/CWR beforehand with the Kindle Utility that's over at XDA:

NOTE: Nightlies are not generally unstable. They might have a few quirks here and there, but it's mostly due to the CyanogenMod base being added onto every day. You could have something show up one day, and gone the next. Developers have to have drivers 100% ready before thy are able to get supported and listed on their repo.

"hey might have a few quirks here and there, but it's mostly due to the CyanogenMod base being added onto every day. You could have something show up one day, and gone the next

."

which is why I would never bother with such a modification/hack
to me it seems you would spend half your time tinkering about with the operating system
and chasing down the latest patch to fix what got broken by the last patch etc etc instead of consuming & enjoying your mobile content

and for what??

just to be able to go into esoteric online user forums and announce you are running CMOD7 on such & such device.

Umm no thanks I shall settle for Golauncher EX with my wall changer app sitting on top of the Stock Amazon Firmware.

which is why I would never bother with such a modification/hack
to me it seems you would spend half your time tinkering about with the operating system
and chasing down the latest patch to fix what got broken by the last patch etc etc instead of consuming & enjoying your mobile content

and for what??

just to be able to go into esoteric online user forums and announce you are running CMOD7 on such & such device.

Umm no thanks I shall settle for Golauncher EX with my wall changer app sitting on top of the Stock Amazon Firmware.

I'm a firm believer in sticking with ROMs that are based on the stock firmware (not just for the Fire, but for all devices with custom ROMs). The stock firmware has drivers that have been optimized for the hardware and I have yet to see any non-stock-based ROM perform as well or trouble-free.

Having said that, I appreciate that the Fires (1st and 2nd gen) are receiving attention from the CM development community. That's a good thing.

I rooted and installed a custom ROM on my KF1, and while it made it a much better tablet, I regretted the loss of the Amazon ecosystem that the KF is really made for.

I love my KF2 and will not be rooting it. I have a rooted Android cell phone and a Nexus 7 if I want an open Android tablet. But I find I use the KF2 a lot - in the stock configuration - and specifically for easy access to the Amazon content it was made to deliver.

IMO, if you want a non KF tablet, go buy one. There's a ton on the market, and many are quite good and inexpensive.

I'm a firm believer in sticking with ROMs that are based on the stock firmware (not just for the Fire, but for all devices with custom ROMs). The stock firmware has drivers that have been optimized for the hardware and I have yet to see any non-stock-based ROM perform as well or trouble-free.

Having said that, I appreciate that the Fires (1st and 2nd gen) are receiving attention from the CM development community. That's a good thing.

Unfortunately this is not the case for the Otter (Kindle Fire 1st Gen).

Their USB driver hobbles the transfer speeds, and their driver that handles the charging is also pretty bad.

Not to mention the completely disabled light sensor and various other items. To be honest the stock firmware for the Otter is a mess.

I'm going to look a bit more closely at 6.3.2 since it is out and see if they improved things, but I'm not all that hopeful.

Part of the work that Hashcode put into getting Otter onto CM builds was based around fixing many of those issues. It was a monumental piece of work to get it to a point where it was allowed to be officially on CM.