Carsten Munk wrote: > Hi! Hey - good post. > * What are you waiting for to happen in the MeeGo project? Code, obviously. Mainly policy though.
1st: How does meego work with real life devices? I assume Nokia will still release closed libraries like liblocation (an example - I don't care if it's actually open) that are needed on a, say, N910 So where do *I* build an app that uses that location? I'd like to build it on build.Meego.com and target the Nokia build repo. That way I could also target the Sony build repo using the same source (with #ifdefs/patches) and have 2 packages using 2 different binary location apis. As a developer my life would be much easier than having to manage packages on both build.nokia-meego.com and build.sony-meego.com 2nd: How does meego work with real life "linux" compatibility? eg: I ported this cool ruby/lighttpd application to my device.... where's meego's ruby? Does it have the ruby-ldap library? Some googling found solutions for other distros that didn't need me to take permanent responsibility for maintaining ruby or the ldap module. How will meego be handling this? http://packages.debian.org/sid/ruby/libldap-ruby1.8 http://packages.debian.org/sid/ruby/libactiveldap-ruby https://admin.fedoraproject.org/pkgdb/packages/name/ruby-ldap?_csrf_token=5bc051ac734e77ce3faefc8a83bf27c93921d3b7#Fedora13 http://software.opensuse.org/search?baseproject=openSUSE%3A11.2&p=1&q=ruby-ldap > * Do you know what is currently blocking these things to happen, if so, what? No > * What would you contribute with if these things happened? What area, > what specific things - how can you help, where's your talents in this > area and interest? I'm designing build systems and processes around them for maemo devices internal use and I'd get involved in Meego's too. Meego needs to recognise the various sub-communities that will form and needs to be prepared to prevent fragmentation. This is a technical issue as well as a social one. Part of the technical planning is to minimise the deltas. Meego must make some clear statements about the limited scope of packages available and then address this. I hear too many people talk about Meego as a "cut-down" or "phone" OS. It can't be... I need my meego device to be as powerful next year as my desktop was last year. Ubuntu's core/multiverse/universe model may be worth looking at here. My main concern is that we don't have enough resource to truly maintain all the packages in the linux ecosystems. The only economically sound way to address this is to find a way to take advantage of work done in and around other distros - and that means working collaboratively with one or more of them in some way. David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..." _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
