On Saturday 06 March 2010 13:02:44 Carsten Munk wrote: > * What are you waiting for to happen in the MeeGo project?
* Source code / git repositories. * Public build system, or at least docs/configs on how the build system is set up so others can implement the same environment. * Opening up of battery code (or a new implementation) for the N900. I had been doing devel using Fedora 12 ARM (which I figure is reasonably close to what MeeGo base will be), but after completely corrupting filesystem twice due to loss of battery, I've sort of lost my enthusiasm for it. I hope under MeeGo we can charge the battery of N900 with Free Software. * Upstreaming of N900 kernel drivers (e.g. tsc2005.c) so N900 device isn't stuck with 2.6.28 kernel. > * Do you know what is currently blocking these things to happen, if so, > what? I'm not sure what the code hold-up is, but Intel/Nokia have "promised" to deliver code by the end of the month (which is probably likely). That said, would be cool if we could even just watch the builder without even being able to submit to it. That way we can start to get a feel for what's coming... I hate waiting. As for the battery, perhaps we should start the request process to see if Nokia will release it this time around (ditto for flasher).[1] For the kernel, I have seen that Nokia has submitted patches for N900 drivers which haven't been accepted upstream yet (neither linus nor linux-omap git). > * What would you contribute with if these things happened? I'm interested in having a 100% Free Software telephone that is generally available. MeeGo appears to be the most likely candidate to do that and the N900 is likely to be the device. So I'll be putting the image on my N900 as soon as it is available. I will likely also be making my own images and testing yours (stskeeps). I'll also test and new kernel patches / releases that come available. > What > area, what specific things - how can you help, where's your talents in > this area and interest? I made a number of mini-HOWTOS and documented various processes with Maemo; I'll do the same with MeeGo. http://wiki.maemo.org/User:Jebba I'll make a bunch of .specs too, as soon as I know what code will be used. I made one for libdui[2], and could make more, but I'm not too stoked to be making .specs for code I'm not even sure will be in MeeGo. I've pretty much lost all enthusiasm to make .debs at this point. The larger issue is that I just feel like I just have to sit and wait. It's pretty much been like that ever since I got the N900. Before it was sit and wait for the servers to actually work[3]. Now sit and wait for the decisions that Intel/Nokia are making. It seems "the community" should be a player in these discussions. "The Technical Steering Group meets once every two weeks. These meetings are public and open to all. Minutes of the TSG meetings are also public and available on the project website meego.com." This hasn't happened, AFAIK. It would be very very good if it happened now. > Imad Sousou wrote: > "not sure whether we should do on IRC or maybe we can also try a real voice conference and see how that works." I very much hope it is a regular IRC meeting, and not some "voice experiment"...[4] Anyway, I look forward to actually being able to work on MeeGo, once the meat gets thrown on the table. :) -Jeff Moe [1] http://wiki.maemo.org/Open_development/Licensing_change_requests [2] https://bugs.maemo.org/show_bug.cgi?id=9337 [3] https://bugs.maemo.org/show_bug.cgi?id=5818 [4] See CD #4: http://lwn.net/Articles/370157/ _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
