Next Steps

It looks like the 100 Days brainstorm has reached its conclusion. The pre-agreed ideas will be discussed next Tuesday in the June sprint meeting. We might add more tasks coming from the current backlog. The ideas still under discussion should be probably moved to the 2010 Agenda for further brainstorm.--qgil 20:09, 8 June 2008 (UTC)

Scope of the 100 Days

How can I help?

How can I help in this process, as one of the people responsible of the planning at Nokia? I could help organizing the content, identifying what is out of scope or what more realistically falls in the Agenda 2010. Or I could just shut up and let you work.  :) fyi, in the meantime I'm already working on the short and mid term plans internally at Nokia. --qgil 19:05, 1 June 2008 (UTC)

I don't think a little direction will repress things too much at this point, and I definitely thing it will help stimulate and focus the brainstorm. Not only because of the clearer definition of purpose, scope and direction, but also from the interest a more visible Nokia involvement would make. The end result, of course, being a much more productive session. --generalantilles 20:15, 1 June 2008 (UTC)
I will start leaving signed comments, not to touch the original text. Then you decide what to do with it.--qgil 06:20, 2 June 2008 (UTC)

Russian language section

Is it possible to create the Russian-language section of wiki ? We would like to move here materials and translations. --dik 22:30, 30 June 2008 (UTC)

Interesting, but out of scope in the 100Days work. I recommend you to ask at Talk:Maemowiki_Action_Group.--qgil 23:01, 30 June 2008 (UTC)

Clear and useful planning pages

The 100 days page is getting longer. I think at the end what we all want to have is a list of clear actions, being most/all of them links to pages where each action is discussed and planned in detail. Proposal to get there:

  • Create pages for those topics that already got interest and meat enough. Move there all their related ideas and comments. This includes the content in this discussion lisrt, since having it hidden here or even duplicated is not going to help.
  • Put at the top the items that are pre-agreed: no-brainer stuff, items with lots of community support, items already acceopted by Nokia and/or the guys.
  • New good ideas are added in the bottom and end up either in the top after being pre-agreed, or moved to other existing pages.

--qgil 08:09, 2 June 2008 (UTC)

Proposals out of scope

Archiving here proposals that don't fit in the 100 Days exercise. Please relocate somewhere if the ideas are good.

Update developer libraries

  • gcc-4.x, glib, powervr, it's important to give developers much more time to play with newer tools than short before a major upgrade takes place (of course with disclaimer that nothing is guaranteed to be shipped in a certain way)
  • Update the vmware appliance with sb2 and python2.5 setted. And more publicity on the vmware appliance, as there is already one on garage, but many don't know it.
This is out of scope in this exercise. About giving more publicity to and - it's currently an alpha and the developers don't feel like advertising it much more. But anybody can follow the Garage project and, well, nobody is stopping you from advertise it more.  :) --qgil 07:53, 2 June 2008 (UTC)
Alpha status doesn't mean that it is unusable, I use this VM regularly and it works very well. I really think this one should be promoted on --xfade 13:55, 2 June 2008 (UTC)
Official x86_64 support will be great or at least i386 on top of x86_64. Other distributions too - some of them only need an alien. bundyo 20:47, 2 June 2008 (UTC)

A few suggestions for developers

A few more suggestions for developers - the bottom rungs of the ladder.

1. Validate and verify the tools installation for the current shipping version, particularly the HOWTO. I follow the instructions but nothing builds. At least until I do an apt-get dist-upgrade, update, upgrade or something similar, then apt-get the -dev versions of a half dozen things, none of which is mentioned. Which brings me to:

2. Insure the hello-world will actually build on a system cleanly installed following the exact instructions from step 1. (I had to edit things in mine) and form a deb which will work on a tablet - both install and remove. Also split out stand-alone versions to use as templates (I can't get a statusbar only version to come up as everything seems to be interdependent). Maemopad is a great write template, but a paint template (slightly more than trivial graphic demo) would be nice.

Hildon is not something I've dealt with, and has its own quirks along with GTK. They aren't bad, but I could spend a week just learning the ins and outs. But there aren't very many examples I can just change the icons and add in a chunk of code to do a simple task as a starting point, at least not without doing a lot of searching (e.g. some statusbar clocks are stand-alone).

3. Simplify the autogen/automake/autoconf stuff. Most of this will only be run under fixed releases, so the checking for some specific version of 20 libraries is redundant, and makes the build horribly complicated. Either in scratchbox things are there or not (and see #1 above if they are not! I also have to keep doing apt-gets since I need -dev of everything and often don't have them). Do I really need libtool for a trivial statusbar app?

Autoconf is actually quite important for code portability, not only across maemo releases (1.0, 1.1, mistral, scirocco, bora, chinook, diablo and so on) but also (and more importantly) across platforms. There is a lot of cross-pollination happening right now, and that's a very good thing IMHO. It will make your life much easier when you decide to port your application to (for example) Ubuntu Mobile, Openmoko or "desktop" GNOME, and it also makes porting stuff from other platforms to maemo simpler.
Having said that, it is a bit of a learning curve, but perhaps what's needed is more entry-level documentation/tutorials (chapter 5 is a very good start at that) and tools to simplify bootstrapping (like the anjuta plugin).
Autoconf is not necessary to write portable software, while making your makefiles unreadable. Therefore, its use has to be made optional.

The goal is that anyone should be able to do a working deb for a trivial off-the-cuff application or status bar, home, or control panel applet in 5 minutes by doing a global substitute (or perhaps changing a few lines of the form: #define APPNAME HILDON_HELLO_WORLD, #define AppName HildonHelloWorld, #define appname hildon_hello_world, etc.) and adding a few lines of code and scaled icons.

And for "garage", there should be one centralized repository, so there would be a "garage" parallel to "extras" with all betas and releases not higher up in the chain. Right now I've got dozens of archives and sources, so when I do a restore it becomes a nightmare getting all the applications back and it makes application manager slower having to go through dozens of archives. It doesn't help having a "garage page" if it is not much better than hosting offsite. But then for all these add-ons I could just do apt-get source and/or apt-get install. Maybe this is what "extras" is for, but it seems to never work or have anything. —Preceding unsigned comment added by 19:32, 29 May 2008 (UTC)