Re: Contribution guidelines
These were good comments, thanks! Marius Vollmer wrote: Obviously, the license of the contributed code must be compatible with the project that you contribute to. It is a good idea to use the same license as the project that you contribute to. http://wiki.maemo.org/Maemo_contribution_guidelines#License edited. Copyright http://wiki.maemo.org/Maemo_contribution_guidelines#Copyright edited as well. -- Quim Gil marketing manager, open source Maemo Software @ Nokia ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Linux mainstream again (was Re: Projects Nokia should support (yours?))
Hi, Sure. However as for today there is no Ubuntu productized for ARM, so it's not as easy as it might look like for the average Ubuntu enthusiast. The Mojo project (funded by Nokia, btw) is investigating that Ubuntu ARM port. It is probably not very difficult to put a Maemo Ubuntu Hacker Edition in place, but the guys in the know think that there is a longer way before shipping commercial products on that basis. I am sure this is pretty widely known but anyway armel is now officially debootstrapable on jaunty debootstrap jaunty dest http://ports.ubuntu.com/ubuntu-ports debootstrap --variant=buildd jaunty dest http://ports.ubuntu.com/ubuntu-ports Another aspect to be analyzed are the implications of Nokia relying totally on a platform delivered (ultimately) by a private third party. This can be achieved by thinking about how *both* sides can gain in the exchange. Ubuntu is interesting to Nokia if (and only if) the community around it gets big enough to support the kind of numbers Nokia deals with and Nokia is interesting to Ubuntu if (and only if) the markets it has access to continue to be available. I'd recommend Nokia hire some people to work on Ubuntu. Dell has a couple of employees who spend all day working on Ubuntu (one recently became core-dev), and so Ubuntu works very well on Dell hardware. Those people could also register specs, argue for them at Ubuntu Developer Summits, etc., and generally ensure that Ubuntu was exactly what Nokia needed. Work on getting patches directly into Ubuntu rather than maintaining a separate flavor. Realigning around a central core would help everyone Don't get me wrong, we have good relationship with Mark and the Canonical crew. But what if one day they all go for a new mission in the outer space? Also, as more companies sponsor people (currently there are about four that have more than one employee working on Ubuntu), the easier it is for them to make sure the Ubuntu Foundation does it's job if Mark does go back to space. Assuming I was completely in charge of Nokia strategy, I'd loosely recommend looking at the internal goals, and thinking about whether you want to engage in a business alliance, or sponsor developers. Doing both is the most expensive solution, but if the volume is high enough, may be warranted. Option 1 --- Paying developers means either hiring existing Ubuntu developers, or getting Nokia devs to work through the processes to become Ubuntu developers (this usually takes about six months). The advantage is that you can completely control their targets and direction. The disadvantage is that you have to work within the framework to get the work applied initially. Option 2 Engaging in a contract with Canonical means that Canonical is responsible for the application of everything. The advantage is that it's not that much hassle, just a bunch of money. The disadvantage is working at a level removed: the basic vendor relationship. What balance of these two options provides for the best expression of Nokia's strategy would require me to have a lot more knowledge than I have at present about Nokia internal strategy etc but as a start it may be worth tracking down some of the other guys from Google, Dell or Sun who work with Ubuntu and talking with them about the costs and benefits of such a strategy however intangible each of these might be Regards, Ian -- http://ianlawrence.info ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Is Ubuntu 64 bit compatible with Scratchbox and Maemo SDK?
Hi, ext Andrea Grandi wrote: I was thinking about installing Ubuntu 64 bit instead of 32 bit, since I've an Intel Core 2 Duo that supports 64 bit OS. Is a 64 bit Linux OS supported by Scratchbox+MaemoSDK? See also: https://bugs.maemo.org/show_bug.cgi?id=3479 - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: RSS-reader issue
Hi, ext Till Harbaum / Lists wrote: Just as a side note: I recently had this problem with the osso rss reader. It took me some time to figure out that it was the rss feed reader eating my battery with a 100% cpu load even after a reboot (i was in fact already searching for a cheap replacement battery on ebay). Deleting the rss feed folder under /home/user resolved my problem. I didn't even remember that i ever used and i am not using the rss home applet. So i was pretty surprised to see it running at all ... not to mention the 100% cpu load it did ... Did you have automatic RSS updates enabled? which release you were using? I think one of the RSS feeds had something that put RSS feed reader into a loop and it would be good to identify what that was. Do you have the rss feed colder contents backed up somewhere? I also think like already suggested here that the solution is some monitoring mechanism. If one of those units has a process running at 100% cpu load for more than a few minutes there's sure something going wrong. I think Youtube and some other Flash stuff can occasionally cause more than few minutes of 100% CPU usage normally. - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Beware 'Personal launcher'
Hi, ext Niels Breet wrote: Asked for more details: 1. Only personal launcher is enabled and device is booted after enabling it 2. Use resizable layout enabled 3. Launcher has enough icons (in one column, icon size = 64) that it it's higher than screen When launcher is disabled, Desktop crashes. The leakage and crash are 100% reproducible. The author was able to reproduce your leak with these instructions. He uploaded a new version to Extras to solve the problem. Can you confirm that it is fixed now? It's not anymore refreshing/resizing itself constantly when larger than screen (which with the redraw leak caused the issue and made it easily to crash when it was disabled). I.e. the main issue is solved. The redraw leak is still there though. It can be tested easily just by running: mem-monitor-smaps -p $(pidof hildon-desktop|cut -d' ' -f1) And dragging with stylus the bottom-right resize handle back and forth. Resizing should normally happen fairly rarely though, so this isn't as critical. Btw. The setup application seems to throw some asserts when it's used: From setup startup: personal-launcher-setup[10388]: GLIB CRITICAL ** GLib - g_strcasecmp: assertion `s1 != NULL' failed From opening Settings dialog: personal-launcher-setup[10388]: GLIB CRITICAL ** Gtk - gtk_box_pack_start: assertion `child-parent == NULL' failed - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Beware Personal launcher
Till Harbaum / Lists wrote: Unfortunately there's no fan on the n8x0 becoming noisy if the device is under heavy load. So even a simple thing like a taskbar icon indicating a high cpu load and being able to present something similar to the windows task manager might help. osso-statusbar-cpu does exactly this. With memory reporting turned off it is nice statusbar clock with black background. Once the background turns solid blue you know there is a problem :-) http://inz.fi/blog/category/geeky/maemo/maemo-hackers/osso-statusbar-cpu/ Chinook build works in diablo too http://people.debian.org/~tschmidt/maemo/chinook/osso-statusbar-cpu/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Beware Personal launcher
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Frantisek Dufka wrote: osso-statusbar-cpu does exactly this. With memory reporting turned off it is nice statusbar clock with black background. Once the background turns solid blue you know there is a problem :-) Actually it should have graphs of cpu and/or memory usage, not black background; there's just a bug I haven't fixed that causes it to be black by default. If you change the settings, it should start to work. - -- Santtu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkq3l0ACgkQX9Rc0+po4p1GZwCgpyS/0IlERxAzpEUSTS+RV0HV DskAnj/9VF6ZqZP+KGFHkkS8LBqeU1A1 =9NjT -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
