With all this talk here about how great and wonderful the hardware will be, it means nothing if there isn't a solid software foundation to run on it. Although I did see a few topics about software, they're mostly general "which distro" and "which apps to include" posts. As we saw with the pandora, we'll be stuck with whatever choices are made at the very start. So let's make sure that they're properly thought through this time. There isn't an entire repo of .pnd like packages that will all stop working when a major change needs to be made at this stage. Most pandora users just assume the pandora firmware magically works, and that all pnds run perfectly. Behind the scenes however, more and more ugly hacks have to be applied to keep it appearing that way. Both on the firmware itself, and the programs inside the pnd. Problem is, I don't really see a coordinated effort to avoid those issues on a successor. Just because it currently runs a debian image doesn't mean that there's nothing to be done. What's needed is: - Open, transparent, coordinated software development, right from the start. Everyone should be able to follow the design/development, and be able to complain about any problems they see there. (and maybe help avoid/fix them) Attracting as many people as possible to help develop/maintain this thing is important. (not to mention that anyone involved at this stage will probably buy one Git repo/bug trackers for everything. - A good solid existing distro to start with. Which seems to have already been decided to be debian. All distros have guidelines on how to do things, custom packages should keep to those to avoid later upgrade problems. - Package repo Rely on the existing distros packages as much as possible, any custom packages needed should be able to be automatically built and uploaded to the repo. - Firmware image builder Firmware images should also be generated automatically. Images that require any manual interference before they can be installed on the device should be avoided. - Firmware Installer A generated image usually needs additional configuration to be run on the device itself. (package installation, first run wizard ) - A well designed .pnd successor One that tried to avoid the problems .pnd currently has. Not only the way the system is implemented , but also have stricter guidelines for the software inside the .pnd itself. Once the first packaged software using it is released, you're pretty much stuck with it, so it's critical to get as much of this done right. - Custom software Device specific themes, settings, utilities, applets, etc. These things don't write themselves you know. The pandora situation where most of it is a big mess of (zenity) scripts that poke around in lots of different places isn't ideal. A standard crosscompiler development environment would also be nice. Not having to fight with crosscompilers,libraries and headers makes developing for a device a lot more fun. Since most of this doesn't depend on any final hardware, work on getting the software side set up properly should start as soon as possible. Having a hacked up debian image appear out of nowhere the day the device is delivered, and expecting everyone to just build on that isn't an option.