Talk:Task:ITt Collaboration

(((Discussion moved from main page)))

maemo.org and ITt services should integrate much better i.e. maemo.org Downloads syndicated in ITt and ITt users getting maemo.org karma.

  • Provide a way for developers to easily add a bug at the application's Garage page for confirmed bugs reported in the discussion thread.
We have agreed with ITt on the general idea. It's something urgent and it would be definitely good to see it in the 100 Days. The specific plan to be discussed in an open page, either here or in ITt or both. In any case, it's clear that the feature is "syndication". Then ITt or whoever can benefit from that, and are the developers of each piece of software that decide if they want to direct the user feedback to ITt, their garage project, the project website, etc.--qgil 06:59, 2 June 2008 (UTC)
A solution could be to add a bugtracker field to the entry in the application catalog. This could then point to the developer's own bugtracker, the maemo bugtracker or a thread at ITt. This could be done on a short term and be a temporary solution until we implement a global bugtracker. --xfade 13:23, 2 June 2008 (UTC)
  • Today we have too many channels (ITT, maemo.org...). Maybe have some more focus like: maemo.org for developers and ITT for end users and something that links them so software releases can be announced automatically on ITT and users from ITT can easily post bugs on garage bugzilla for example.
Perhaps develop a plan, but this isn't specific enough to achieve in 3 months, IMHO --jaffa 22:10, 29 May 2008 (UTC)
I'm not convinced that two channels is too many, either. —generalantilles 20:04, 31 May 2008 (UTC)


Discussion Forums

3. Effectively replace "iTT Software Section" with #2 from this list.

About 2 and 3 - I thought we all agreed on that here: http://www.internettablettalk.com/forums/showthread.php?t=20261, just compiling a single list won't solve the dependency hell. bundyo 19:04, 30 May 2008 (UTC)
It will not but then it is not the goal of 2. The goal is to supplement the current half-baked Application Installer app with a quickly modifiable online interface for searching and selecting applications. This will help users to find more applications and in the same time it will help developers to figure out just how exactly application installer should work. Instead of waiting for the next OS release, it is really easy to modify the web interface and see which modification is better. Later, the real App Installer can be designed to have the same or similar interface.
I can see what your idea is, but i don't think the user will be happy when his/her NIT falls into a reboot loop due to some library replacement. Not good for official, but maybe will be good for the developers to see what is already ported and not doing it again. bundyo 20:49, 30 May 2008 (UTC)
Situation where a library used by some other application is being upgraded can be checked and reported to the user, as a warning. And no, of course I do not suggest that this system is associated with Nokia in any way: Nokia can't be held responsible for all the repositories out there.
Well, then it should be discussed as kind of an upgrade to Gronmayer's site, maybe with him? bundyo 21:35, 30 May 2008 (UTC)
Definitely: after all, he has all the code already. Replicating it is extra work. As to the UI, I have got a mock up already, if anybody is interested (http://fms.komkon.org/Maemo/). fms

Out of scope

1. Fix iTT's style sheets so that they work well on MicroB! It is a joke that a site dedicated to internet tablets cannot be effectively viewed with an internet tablet.

Just stylesheets may not be enough - the real problem lies elsewhere: run a Firebug Net test and look at the results - seems like right now the front page is 700k, delivered by 67 requests. Some things take seconds to load, some javascripts are with php extension, thus not using cache, taking precious bandwidth and seconds to load, I'm not sure I see the reason for that. Things that can be done to get it faster - javascript libraries can be compressed with YUI compressor for instance and not served with php so they can cache properly, replace youtube videos with handy links for mytube just for ITs, combine stylesheets and javascripts together, reducing requests, use fewer PNGs with alpha, if any - Cairo probably will have a good deal of trouble displaying them on an IT. bundyo 20:44, 30 May 2008 (UTC)
Umgh... I did notice the stylesheet but did not know it was that bad. My suggestion would be to simplify the page rather than use compressor, etc. There is absolutely no reason for this page to be this complicated and take 700kB. It is not doing anything special, just presenting a few views to the reader. Really hope Reggie sees the light at some point and changes his setup. —Preceding unsigned comment added by fms 17:19, 30 May 2008 (UTC)
Though definitely something that needs doing, it's a bit out of scope for maemo.org. ;) Somebody want to run through the areas where Reggie could optimized and open a thread in the Comment/Suggest forum over there? —generalantilles 21:22, 30 May 2008 (UTC)
another itT redesign (tablet-friendly) is planned. --Reggie 20:54, 2 June 2008 (UTC)