Roadmap

I. Platform

1. TinyCore

GotoLinux will use TinyCore as its foundation. Using a pre-existing foundation will make it a lot easier to to get up and running quickly, in comparison to having to build and maintain a whole new system from the ground up, a la LFS. TinyCore is also petite, unlike other distributions that are commonly used as foundations (Slackware, Fedora, Gentoo, Debian and Ubuntu). Plus we gain TinyCore's "pristine core" design, so we don't have to reinvent the wheel in that regard. While significant tweaks to that system will be necessary to fit with the GotoLinux goals, those changes are a short jaunt compared to redoing it all from from scratch. And with any luck, they may also contribute back to TinyCore as well. The only challenge here is how the compile and package system taken from GoboLinux can be harmonized with TinyCore's app modules.

2. GoboLiunx

The next step is to incorporate setup GoboLinux's file heirarchy, it compile and package system and and get GoboHide working. The first two should be relatively easy. The later requires that the GoboHide kernel patch be updated. It would be nice if there were a way to do this via a kernel module though a hook of some sort, but from what I understand this in not possible. Maybe eventually a conversation with Linus can open up a path to handling this without a "hackish" patch. But until then there is no choice by vigilance. A new repo will be started for this patch.

3. New Shell

Pursing the ideal of "lingua franca", tty.js looks like a potential replacement for the more traditional Bash shell. This is not the most pressing item on the list, so if tty.js is new ready for prime time yet it can wait.

4. Window Manager

GotoLinux will use NWM as it's window manager. This is a window manager written in Javascript using Node.js. It still needs work, but works well already. (I am using it as I type this in fact). It will also likely require a separately maintained fork for enhancements suited to GotoLinux.

6. User Applications

As much as reasonably feasible, the default set of end-user applications will consist of Javascript programs. Subsequent to this programs that use another scripting language such as Ruby, Python, Lisp, etc can be considered. Only after these, where no good alternative exists, are C programs included.

5. Live CD and Installer

The last set to getting the base distro up and running is the Live CD and Installer.

II. User Experience

III. Marketing