A Guide To Becoming An Ubuntu Developer
Phoronix: A Guide To Becoming An Ubuntu Developer
For those interested in potentially becoming an Ubuntu developer, Emmet Hikory has written a brief guide about that very topic. Some feel that it can be challenging to become an Ubuntu developer, but in a long mailing list post he goes over all the details...
ubuntu api, haiku, tradeoffs involved portability to other distros
First, imvho mizra is absolutely right in his first post ("Ubuntu API"), and i'm afraid that he might also be right in his second post in this thread ("State of The Ubuntu").
I should point out for the record that there is an official page about the ubuntu api, namely:
However, when you actually visit that page, you discover that there's no api to be found there. It's almost as if they don't really know what an api is.
Now, Thatguy makes a good point about Haiku. And there are a lot of good things about Haiku. But, afaik, it still is lacking some very important features, such as (simultaneous) multi-user support, and i'm not sure there's a functioning emacs for it. And the linux kernel is probably the best possible foundation layer just due to the huge amount of scrutiny and debugging it has been through. So ubuntu really has some strong points that are not there yet with Haiku. Too bad that having an api is not one of them. (Similar remarks for Syllable --- they're right about the need for an api, but still lacking many things, including lots of modern hardware support.)
Regarding Veerappan's remarks --- it is true that if ubuntu actually had an api, then apps developed for ubuntu might not run on other distros (at least until they adopted the api).
But this is an engineering question, and every engineering decision there are trade-offs involved.
We would be trading portability for ease-of-development and application quality.
So i would welcome an ubuntu api very much (or, an api for any linux distro, for that matter).