On Sat, Mar 6, 2010 at 11:49 PM, Jeff Moe <m...@blagblagblag.org> wrote:
> * 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. > Add rtcomm-call-ui or rtcomm-call in general. oh, and also the app manager stuff , for make sure things like that never manifest in the user experience, as it does here - https://bugs.maemo.org/show_bug.cgi?id=9089 https://bugs.maemo.org/show_bug.cgi?id=8747 > > * Upstreaming of N900 kernel drivers (e.g. tsc2005.c) so N900 device isn't > stuck with 2.6.28 kernel. > +1 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] > +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). > Maybe we could start promoting those patches up and see where they are stuck ? Or is this work already being done by Nokia employees ? It would be nice to have some input from Nokia people on this. > > > * 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. > +1. > > 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). > +1. > > I'll also test and new kernel patches / releases that come available. > I would like to make sure we do provide a slick and polished user experience. If code is open, then all those potential scratches as I identify I could fix myself. I am also interested to explore the development workflow technically wise (build system, translations, packages, upstream importation etc) to see where I can integrate the QAWG processes and work flows for QA and integration. (I have a draft that I haven't published, I'd like to be able to deduce if it holds at all fro the MeeGo project, as it is now mostly based on Maemo) > 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. > What about the Deb Packaging working group? I think we should seek official acceptance of that by Nokia at least in order to make this "branch" of meego and official flavor and not just the enthusiast's dream. I'll risk jumping into conclusions but for me seems Nokia should be interested in this, if only to provide some sort of backward compatibility with Harmattan and Fremantle packages that are already there. > > 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." > I think the first ever meeting should be a mini developer summit. This may sound a bit rad , but if you think of it thoroughly that is the only way to get things ironed down and agreed upon for a future release. I'm thinking along the lines of the UDSs Canoincal holds for Ubuntu. I think there should also be a room for some sort of sponsorship for community members that have shown interest and proven the qualifications to carry on the work. Sivan
_______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
