Notices

I use http://maemo.org/packages as starting point for all packages.
You see the latest builds and packages from the autobuilder
and a link to extras-testing queue

It isn't that hard to stay up to date for current packages
in extras-testing.

nicolai

Too true, I use many of the programs in extra develop, but never knew that I could vote for them. Now I know, I still don't know where to go and how to do it!

It's not that hard once you know the links. Now I know. I can remember "maemo.org/packages" - but I didn't know that existed until now. And I've looked. Most users don't think to look or know where to start.

The developer promotes from extras-devel to exras-testing when he feels the app is ready, from there it's a question of votes to get from extras-testing to extras and so on.

On the package instance page when a package is in extras-testing is a thumbs up/thumbs down link which you hit to vote, logging in via your separate maemo.org account,

Kind Regards,
D4rK

So any good ideas how to make Testing voting more sexy or appealing*, easier to approach and easier to find. Kisstester is nice but well we need this page and whole maemo.org page. IMO there should brainstorm kind of page for testing area where there is different kind of top 10-list (ordered by votes, comments, date, clicks, day etc.) of apps in testing where people can comment, vote, report bugs etc.. How about talk area strictly for apps in testing & devel?

How to market your apps more vividly here in TMO or across whole maemo.org? Any platform ideas or how to integrate marketing of testing & devel "gems" to users? Current situation is that when you have been here 3 months non-stop and scavenged all different areas the whole maemo.org the web-page tree starts to build up in your brain and you end up thinking that everything is easy and can be found just couple of mouse clicks. WRONG! For example I can still remember the first days when I tried to understand structure of this page and my head hurt quite much...(sidenote I´m M.sc by education and I know that things should´n be this hard to me and if they are hard to me then I can only imagine how hard they are to most of people :| or maybe I´m just stupid...)


*On the other hand I can understand that it should not be too easy, but current situation where devels are given free hands to use variety of different kind of communication ways is bad in big picture because of fragmentation of communication ways to users. To learn wiki, garage, TMO, brainstorm, bugzilla, package page, etc. is _way_ way_ too complicated to most of users. From the point of devel it might be fun to have variety of ways to interact with users but from point of user it´s better to have ONE hammer to all.

----sidenote---
And moreover. I still haven't seen good wiki article where app testing from point of memory leaks is shown. Just one simple CASE where it´s shown what commands and what numbers testers should look for. All what I can find across Internet is unlimited mumbling and debate about what is real memory and Linux zealots wanking on trivial semantic problems. Look for example sysinternals http://technet.microsoft.com/en-us/s...rnals/bb963890 Mark Russinovich's technical blog where he tells people how he uses these debugging apps on finding root of problems. I find these blogs very very easy to approach. Yes there is thousands of lines command line commands but to understand all of those you have to read every single manual (might be huge) and understand what every single switch does, why not just comment on side of command what all switches exactly do.

it is easy after you read this:

http://wiki.maemo.org/Help_testing_software