First things first, a hyphen in a name is a bad idea (tm).
Tag this baby as: kTizen from now on.
OBS - Open Build Service
An openSUSE project, see: http://www.open-build-service.org/
A community (Corporate or otherwise, including a "community of one") Embedded Linux project, see: http://merproject.org/about.html
A system distribution for Embedded Linux platforms, see: https://www.tizen.org/
Both the Tizen distribution and the Mer Project use the OBS build system.
The Tizen distribution, being a distribution, maintains the system repositories.
The Mer Project allows the configuration of local (or community) system repositories. The Mer Project does have system repositories but expects that they will just be a starting point for any new, community (or Corporate) system repositrory. (Which is why they let you rsync them.)
Neither (currently) supports the Freescale, i.MX, SoC devices.
Neither (currently) defines any of the Amazon e-book products as a platform.
Both currently build for armel.
At this point in the post, review the first reference link above, then take a deep breath...
Tizen uses the code from Samsung (as used in the Samsung smart phones and tablets) to provide the "core platform API".
Giving a Kindle product a sub-set of the Samsung product behaviors is "good enough" as a starting point for kTizen.
Assume that kTizen re-uses the Tizen/Samsung "core platform API code".
Tizen is pulling most of their "platform sources" from Debian Wheezy/sid and some from Ubuntu.
Not a bad choice for Tizen, embedded systems need to be "conservative" in their choice of platform sources.
But, being locked into the aging, very conservative, choice of Tizen may not be suitable for kTizen.
Enter the Mer Project.
Using the Tizen/Samsung "core platform API code" snapshots (no repo access) plus defining the "platform sources" as remotes of the Debian/Ubuntu upstream sources would be a better choice for kTizen.
That would allow the choice of "very conservative" core system builds (like Tizen) or "bleeding edge" core system builds. Builder's, build-time, choice.
Every embedded Linux device needs a bootloader and a kernel.
You all know where the kernel and u-boot repositories live.
Freescale maintains a product specific set of repositories, with the upstream u-boot and kernel repositories as remotes, see: http://git.freescale.com/git/
Note: Freescale has the series three kernel sources in the "-2.6" named repository. Currently as recent as: 3.0.0 (a.k.a: 2.6.40).
Amazon does not publish access to their repositories, but they do publish their product specific changes to the kernel.
Hope to find someone who loves to merge patches and presuming such a masocist will be found...
Tizen is using ScratchBox-2 as its cross-compile engine, see: http://maemo.gitorious.org/scratchbox2
More later, once I have studied these tens of gigabytes of files I downloaded a bit more.
Comments welcomed here.