[14:52] <NCommander> lamont, you around?
[14:52] <lamont> yeah
[14:52] <NCommander> lamont, question, what does it take to get a new port of Ubuntu off the ground so the speak
[14:52] <NCommander> (in an official way)
[14:53] <lamont> hardware for the DC, and a working bootstrap world, plus people working on it
[14:53] <lamont> at a minimum
[14:55] <NCommander> lamont, see PM :-)
[19:40] <jbailey> NCommander, Awww.  You're not gonna share?
[19:41] <jbailey> lamont, You forgot the critical bits of overcoming James' hatred for the port and convincing kernel + toolchain people that you're not a muppet.
[19:43] <lamont> jbailey: that was encapsulated in the "at a minimum" :-p
[19:44] <jbailey> lamont, You left out the hardest part.
[19:44] <jbailey> Otherwise we'd have m68k already, wouldn't we? =)
[19:44] <lamont> as for the kernel/toolchain, the port must provide a responsible muppet^Wporter of sufficient competence to at least get James back to neutral from hating the port for the drain that it is otherwise.
[19:45] <lamont> also, the port needs to be to a point where it reliably runs, even when building gcc and glibc (and openoffice/java??)
[19:45] <jbailey> I was more thinking that you probably want commit access to the kernel and the toolchain.
[19:45] <jbailey> Yeah, Java's pretty standard these days.
[19:45] <jbailey> You have a pile of VMs to port if they don't work: Python, Java, Mono, Guile.
[19:46] <jbailey> They're all in main these days.