web-meeting-2009-01-13

Jaffa2Hmm. Baby in one arm, likely to want feeding soon - this'll be fun.14:54
GeneralAntillesJuggling is a fine skill to learn14:56
-!- wazd [n=wazd@gwh-1-22-val21.ln.rinet.ru] has joined #maemo-meeting14:58
Jaffa2GeneralAntilles: Mrs Jaffa might get upset if I dropped the baby :)14:58
wazdI got you!14:58
wazd:)14:58
-!- etrunko [n=edulima@200.184.118.130] has joined #maemo-meeting14:59
-!- timsamoff [i=46f4f0e8@gateway/web/ajax/mibbit.com/x-9cf4e598512e5a72] has joined #maemo-meeting14:59
Jaffa2Who's chairing, btw?15:01
timsamoffI'm assuming dneary.15:01
timsamoffGood morning (from here), btw. ;)15:01
wazdHello everybody :)15:01
wazdGood evening in here already :)15:01
dnearyJeez15:01
dnearyHi all15:02
* dneary sits in the chair15:02
timsamoff:p15:02
dnearySo - do we have everyone important here?15:02
* bergie feels important now :-)15:02
dnearytimsamoff, Jaffa2, dneary, bergie, ...15:03
dnearyNo glaoliver or andrecunha for the moment?15:03
X-FadeNope..15:03
dnearyOr teko15:03
dnearyor is it tekojo?15:03
bergieI have to be out in about 1.5h15:04
andre___i can pretend to be andrecunha but i think you will find out quite soon :-P15:04
timsamoffHehe.15:04
GeneralAntillesandre___, I demand mockups with cats!15:04
andre___eeks15:05
-!- glaubertsouza [n=glaubert@192.100.104.170] has joined #maemo-meeting15:05
dnearyandre___: sprechst du Deutsch?15:05
dnearyglaubertsouza: Hi there15:05
glaubertsouzaHi Everyone15:05
andre___dneary, a bit. same with french ;-)15:05
bergieok, are we able to begin?15:06
wazdhello15:06
dnearywazd: Hi - mind me asking who lurks behind the IRC nick?15:06
dnearybergie: Waiting for Andre Cunha and Tero Kojo, hopefully they'll arrive quickly15:06
dnearyWe can start in the meantime15:07
-!- andre___ is now known as andrek__15:07
bergieok... so, the status15:07
andrek__(to avoid confusion)15:07
dnearyglaubertsouza: Can you give us a status update on what you've been working on since the holidays, please?15:07
bergiewe have layouts for the front page, and some sectional front pages15:07
wazddneary: em, Andrew Zhilin, Russia :)15:07
bergiebut not app catalog, a regular content page, social news etc15:07
wazddneary: http://tabletui.wordpress.com guy)15:07
bergieespecially a regular content page is urgent15:07
bergiewe looked at the CSS and XHTML that we got from INdT15:08
dnearybergie: Mind if I do a tour of everyone?15:08
bergieand unfortunately it doesn't follow any of the guidelines we wrote for them15:08
bergiedneary: sure, go ahead15:08
dnearybergie: Thanks15:08
dnearybergie: Could you fish out a link to the mail archives for that mail with the guidelines?15:08
timsamoffCan I ask a BIG question before Bergie gets started?15:08
dnearytimsamoff: Please.15:08
bergiedneary: http://lists.maemo.org/pipermail/maemo-community/2008-December/002782.html15:09
timsamoffWould it be feasible just to hand off the PSD designs to Neiman and have their guys do all of the html/css work (i.e., convert static designs to web)?15:09
bergiedneary: ok, it follows *some* of the guidelines ;-)15:09
timsamoffThis would remove INdT from that part of the loop... Glaubert could continue to mockup pages.15:09
dnearytimsamoff: I'll hold off on that answer for a bit too :p15:09
bergietimsamoff: yeah, that is one option15:09
bergiebut let us do the round that dneary wanted first15:10
timsamoffOk. ;)15:10
dnearytimsamoff: I would like to have a clear summary of where we're at first15:10
timsamoffRight. carry on. :)15:10
dnearyglaubertsouza: You're on!15:10
glaubertsouzayes15:10
glaubertsouzaok15:10
glaubertsouzaas we "completed" the community page15:12
glaubertsouzawe are moving to Download and planet pages15:12
dnearyglaubertsouza: Did you read my email from last Friday?15:13
dnearyglaubertsouza: http://lists.maemo.org/pipermail//maemo-community/2009-January/002877.html15:13
dnearyHow's progress on the Download and planet pages? And when do you think you might be able to get to (say) the Intro page, which is a typical Midgard page?15:14
bergiedneary: well, the typical Midgard page can as well be a typical wiki page, or typical mailing list archive page if we so decide15:15
bergieso I'd say "typical content page" :-)15:15
glaubertsouzawe`ve just started on the DOwnloads and planet pages..15:16
bergieglaubertsouza: a little remark: can we have a "person profile" widget that can be reused across planet, comments, whatever user posts?15:16
bergieyou know... photo, name, karma, online status15:17
glaubertsouzawhy not.?15:17
-!- acunha [n=acunha@200.184.118.136] has joined #maemo-meeting15:18
dnearyhi acunha15:18
Jaffa2Do we need to track work items &Y status better?15:18
glaubertsouzaI Think it works15:18
acunhahi dave15:18
timsamoffMorin' Andre.15:18
dnearyglaubertsouza: How long does it take you to mock up 1 page?15:19
glaubertsouzaIt Depends, some time it take me some days15:19
timsamoffAs an aside, I think one to three days per page (depending on complexity) should be enough.15:20
timsamoffBut, that's me. Glaubert can comment.15:20
glaubertsouzaYes , the complexity says how long it will take15:21
bergiealso, in general, the more reusable design elements we have, the easier it will be to adapt the layout to the various maemo.org services15:21
timsamoffbergie: Especially in the css stage!15:21
bergieindeed15:21
acunhayes, after having 5 or 6 design pages things get much easier15:22
bergiebut also because it doesn't make sense to design all of the 100 different screens we have across the systems15:22
glaubertsouzawe try to make a "Template" (reusable elements)15:22
dnearyOK15:22
timsamoff(Damn, my typing fingers are frozen right now -- it's 6ยบ F here!)15:22
timsamoff:p15:23
glaubertsouzawe work less on the currents page, but we think more to adapt and get it consistant15:23
wazdCan I ask a question?15:23
dnearySo - in summary, you have completed the front page, Community & Development design work & HTML, you are now working on applying the same style to two complicated pages15:23
glaubertsouzayes15:23
dnearyDownloads & planet15:23
dnearySo you're not working on a graphic, you're on HTML?15:24
bergieafter those, the big priority should be the "static page"15:24
bergieas for HTML, can we discuss that *after* we discuss the design?15:24
dnearybergie: That's what I'm trying to get at15:25
wazdCan I ask a question bout design?)15:25
timsamoffwazd: Ask away. ;)15:25
wazdHow would you add "talk" item into top menu row?15:26
bergiegood point15:26
timsamoffI think there's room for another menu item.15:26
bergietalk should be there15:26
dnearywazd: "Talk" as in ITt?15:26
timsamoffBut, we never made room for excerpts.15:26
wazddneary: yes15:26
glaubertsouzaI`m working in the graphics I plan to show you my progress by we thursday15:26
dnearyWouldn't that fit in the "Community" page?15:26
timsamoffYes.15:27
dnearyI mean, wouldn't that be most appropriate in the community page?15:27
timsamoffBut, on the front page... We could mix (mashup) News/Planet/Talk in the exerpts.15:27
dnearySure15:27
timsamoff...as one long set of conversations.15:27
timsamoffBut, yes, Community is where it should go, I think.15:28
timsamoffwad: Opinions?15:28
wazddneary: maybe, but I think it's not so good idea to hide forum in sub-pages15:28
timsamoffwazd I ean.15:28
timsamoffmean.15:28
wazdtimsamoff: well, I've asked this question because I see current design is not so scalable as it should be15:29
bergiewazd: then again, same reasoning goes for wiki, bugs and garage15:29
wazdBut since Glaubert is still working on this problem could be solved already15:29
dnearywazd: In my head, I had it going in "Community" and "Support"15:29
timsamoffWe did have quite a lengthy discussion about categorization about pages... Keeping it simple -- making launching points rather than direct links, etc.15:30
dnearybergie: And mailing list subscription pages, IRC, ...15:30
bergiedneary: yes, so grouping them under more generic headers like Community and Development makes sense15:30
wazddneary: Maybe you're right, but still, if you one day will want to add something to the main menu - you'll screw up)15:31
dnearywazd: You could be right.15:31
wazdBut still I'm considering forum as standalone item... Less newbie-confusing I think. But that's just my opinion15:32
dnearywazd: I think it's sufficiently adaptable to accommodate maybe one more top level header, if one day we find one that we really really need, based on the feedback of people using the site15:32
timsamoffwazd: Can you provide an example? I see room for more menu items...15:32
dnearyBut for this version, I'm pretty happy with the front page serving its purpose15:32
bergieok, should we move on?15:33
dnearyglaubertsouza: I am still wondering if you're working on graphics or on HTML15:33
wazdtimsamoff: I haven't got examples of future pages for now, but when they will appear it would be too late :)15:34
glaubertsouzaI`m on Graphics15:34
dnearyglaubertsouza: OK, great15:34
timsamoffwazd: True, but... I'm with dneary on this -- I think the current version serves a good purpose. If, at some point, it needs to change, we could change the front page (and it's functionality) without redesigning the entire site.15:35
dnearyBecause who works on the CSS/HTML is one of the things we need to discuss15:35
bergieagreed15:35
dnearyacunha: So - Andre, what have you been working on since Friday?15:35
timsamoffHere here. ;)15:35
bergiethe current version has some structural issues and quite a bad case of classitis (http://joshuaink2006.johnoxton.co.uk/blog/330/avoiding-classitis) that makes it a bit hard to adapt and reuse15:35
bergieso with it there are two options: hot-fix the structural things, or redo it15:36
wazdoh, and where's the "community" item then?)15:36
wazdI'm looking at http://openbossa.andrecunha.com/maemo15:36
bergiesince we need to adapt them to quite a few different systems, I'm kind of in favor of trying to get the HTML right the first time15:36
Jaffa2wazd: this had been my concern - the links to Support & Community are only off the front page, not the header.15:37
timsamoffNote: dneary, glaubertsouza: We also need rollover states for clickable graphics (links).15:38
bergietimsamoff: especially the main menu (rollover + selected status)15:38
wazdJaffa2: Well, I don't get why documentation is a standalone page, since it's a 9% developement thing :)15:38
wazd99%15:38
timsamoffDocs can also refer to user docs (in the future), though.15:39
Jaffa2wazd: I'd say 50%; half of it is developer docs, half of it is community documentation. But I can't remember the arguments about this before. I seem to remember losing :-)15:39
Jaffa2timsamoff: What's a "user" doc? Why does a visitor to the site care who the author is?15:39
dnearywazd: "Get involved" -> Community, "Get help" -> Support15:40
dnearywazd: And I specifically left Documentation off the front page, not sure when it crept back in15:40
timsamoffJaffa2: No, I mean documentation for users.15:40
dnearyBut that's another subject15:40
timsamoffBut, maybe that's Support...?15:41
wazdJaffa2: I think you should divide 2 types of documentation and place it in "development" and "community"15:41
dnearyWe've got a relatively short amount of time to find out what progress is, and decide what's happening next15:41
dnearyFor design discussions, please use the list15:41
wazddneary: ok15:41
dnearyJaffa2, wazd: This is a discussion I'll happilyu contribute to on the list15:41
bergieso... regarding HTML15:41
bergieI'm proposing we redo it15:41
bergiethis Friday we can do the "basic skeleton" of the design15:42
dnearybergie: OK - you're up :)15:42
bergieso deployment to some of the systems can start15:42
bergieessentially to those that won't be designed specifically15:42
dnearybergie: You were saying that the pages supplied by INdT didn't meet your guidelines?15:42
dnearyMind saying why?15:42
bergiedneary: "some structural issues and quite a bad case of classitis (http://joshuaink2006.johnoxton.co.uk/blog/330/avoiding-classitis)" :-)15:43
bergiethe current design forces you to create bunch of CSS for every page type15:43
bergiewhich shouldn't be necessary, and overtly complicates things15:43
bergiethe current CSS is also very long and complex, which will bite us in maintenance phase15:44
bergiewe could just accept it on the basis that it "looks OK in the browser", and just use it, but that will be trouble further on15:44
timsamoffI agree... And, the css still needs a lot of tweaking (imho) to match the design: http://lists.maemo.org/pipermail/maemo-community/2008-December/002844.html15:45
bergieso I'll rather point out the issues now than fight with them for the next two years ;-)15:45
acunhaFine. Bergie, do you need my PSDs files or you can work on the sliced images you already have15:45
dnearyBottom line - how long do you think it will take you to take the designs & have a stylesheet that meets your standards, and works well on FF >=2, IE >=6, Webkit and the tablet browsers?15:45
bergieacunha: having the PSDs would be great. Can you send them to lauri.manner@nemein.com ?15:45
bergiedneary: I think we'll have the "basic page" on Friday... then the special designs of various pages are another matter15:46
bergiedepends how much they differ from the typical page15:46
bergiein any case, those can be implemented as separate CSS files that are rendered in addition to the "main site style"15:48
dnearybergie: You'll need the graphic design for that, or you'll retro-fit CSS from the front page?15:48
bergiedneary: both is best15:48
bergieLauri (http://nemein.com/en/people/neithan/) will work on that, so best if the materials are sent to him directly15:49
timsamoffbergie: Love the Midgard error with the mangled URL! :p15:49
bergietimsamoff: you should see the default error screen of the next Midgard version ;-)15:50
timsamoffI hope it's a little more...human readable.15:51
timsamoff:)15:51
bergiethe current default tries to emulate Apache defaults15:51
dnearytimsamoff: You get something funny?N15:51
bergiebut anyway, back to the business at hand15:51
dnearyI just get "url not found on this computer"15:52
dnearyYes - bergie, what do you need from Andre and Glaubert?15:52
bergiedneary: the PSDs15:52
dnearyThe PSDs of...15:52
bergieand if they can get us a PSD of a typical content page (with submenu) by Friday, then that would be great15:52
dneary(please be explicit)15:52
bergiePSDs of the various designs that are available15:52
bergiethe more materials we have, the better15:53
X-FadeWe might also need some icons for things like no avatar etc..15:53
bergieyes... thumbs up/down, starred/unstarred, no avatar, online/offline15:53
timsamoffLet's add these things to the wiki if they're not already there.15:54
bergieI think there's a bunch of stuff that still needs to be designed15:54
timsamoffIt will help for whenever the "next" redesign is. ;)15:54
bergiebut, for now, we can start with having some basic HTML15:54
bergiethen next question: do we aim at having all systems with the new layout?15:54
bergieMidgard, mediawiki, mailman, bugzilla, gforge, ITT, ...15:55
dnearybergie: OK - so you would like the PSD corresponding to the front page, the community page and the development page (which are done) and would like to have a "standard" page get top priority this week?15:55
bergiedneary: correct.15:55
timsamoffbergie: I think so!15:55
dnearyAny preference for a "standard" page?15:55
bergieand before Friday15:55
bergiedneary: here is a pretty good standard page example: http://maemo.org/news/announcements/maemo_diablo_4-1_reference_manual_released/15:55
dnearyglaubertsouza: Is that OK with you?15:56
bergietimsamoff: ok... I hope X-Fade has some time to collaborate on that with us when we get to the phase where we deploy the layouts15:56
X-Fadeglaubertsouza: Please also include the person profile on that page :)15:56
Jaffa2bergie: Yes, definitely all pages should look the same now15:57
glaubertsouzaAndre and I , we`ll send you the 3 PSD we have15:57
X-Fadebergie: Sure, no problem.15:57
X-Fadebtw, do we have a default font that we use?15:58
bergieglaubertsouza: obrigado!15:58
dnearyglaubertsouza: And you'll work on the page that bergie indicated in priority?15:59
dnearyFor Friday, if possible?15:59
glaubertsouzaok15:59
bergiein the original old maemo2midgard feasibility study (https://garage.maemo.org/docman/view.php/106/45/Maemo_Midgard_Migration_Project_Feasibility_Study.pdf) we proposed some methods for keeping layouts in sync between the different systems15:59
bergiethat was never implemented, but maybe we could utilize some of the ideas now with X-Fade16:00
timsamoffYes! Totally!16:00
Jaffa2bergie: as in, automatically?16:01
dnearyacunha: If you're OK with that, INdT's role will be creation of graphics assets, and graphical design of pages when necessary16:01
dnearyDo we have a check-list for assets we need?16:01
Jaffa2bergie: Whatever's easiest, but since the layouts shouldn't change *too* often, I'd be wary of spending time on a technical solution which'd take longer to implement than just doing it manually16:01
bergieJaffa2: yeah, keep it simple16:02
Jaffa2dneary: this is what I meant earlier: we should have a page on the wiki with a table of required assets, which people working on them should be updating weekly16:02
dnearyStars on & off, thumbs up & down, online/offline, no avatar were noted16:02
dnearyGeneric "User" widget layout was also mentioned16:02
bergieactually, preferably two variants of "User"... inline and a small box16:03
timsamoffGraphical links with rollover states.16:03
dnearyJaffa2: I'll take care of that after the meeting16:03
dnearybergie: OK, noted16:03
dnearytimsamoff: Not sure what you mean by that16:03
bergieyes, the rollover states should be as layers in PSDs16:03
glaubertsouzaI think we should make a priority list with all changes or needed things you`ve pointed out!16:04
timsamoffMouse-over image link (changes to sugnify).16:04
dnearyYou mean when you roll over a menu item it turns orange, kind of thing?16:04
timsamoffdneary: Yes. But, text is easy (css). Images links need actual variations.16:04
Jaffa2Wherever possible, I'd like to see text elements be rendered via text elements & CSS - even if that means sacrificing pixel perfect accuracy from the original PSD.16:06
Jaffa2Otherwise translations become harder (unlikely to be an issue), but it also makes maintenance that much harder/restrictive as to who can do it. Not to mention the bandwidth overhead.16:06
timsamoffJaffa2: Why? Images can use text replacement methods via CSS so that the page will still have text links if no CSS is available...16:06
timsamoffOh, translations. Ok. ;)16:06
Jaffa2Admittedly, there're no plans to translate maemo.org :)16:07
timsamoffBut, when people do it via Google...16:07
Jaffa2Good point!16:07
Jaffa2I win :-)16:07
timsamoffHa!16:07
dnearyOK16:07
bergiethe more elements can be "just text", the better16:07
timsamoffAgreed.16:07
dnearyglaubertsouza: The first priority is the normal content page16:08
glaubertsouzano Portuguese ?  :(16:08
glaubertsouzako16:08
timsamoff;)16:08
dnearyglaubertsouza: Second priority will be the graphical assets, and individual special pages, on a case by case basis16:08
dnearyUntil then we can use the current versions as placeholders16:08
glaubertsouzaok16:09
dnearybergie: You think you'll have the front page reworked by Friday?16:11
bergienot necessarily front page, more the "basic page", from which all is derived16:11
bergiefront page is not the main priority anyway16:12
dnearyI'll have a Support page content proposal for ye by Thursday16:12
dnearyglaubertsouza: When do you think you'll deliver the basic page?16:12
dnearybergie: The thing is, you have the PSDs for the front page, development and community now, but not for the "basic page"16:13
bergiedneary: yeah, but in general everything derives from basic page, and front page just is some CSS exceptions to that :-)16:13
bergiedneary: BTW, will you summarize the decisions from this meeting to the list?16:14
dnearybergie: So you have everything you need now to attack a basic page? Or am I misunderstanding you?16:14
dnearyI will send minutes to the list soon, yes16:16
bergiedneary: we can do the basic framework now, and add more stuff if we get the "content page" designs16:17
dnearybergie: OK.16:17
dnearyglaubertsouza: What do you think is your ETA for that page Henri pointed to?16:17
glaubertsouzaThursday16:18
bergiegreat16:18
dnearyOK16:19
bergiejust send everything to Lauri then16:19
dnearyacunha: What will you be working on now?16:19
dnearyacunha: Assets for the site? Or other projects?16:19
acunhaIm working on other projects, I will help glaubert if he needs so16:20
dnearyOK16:20
dnearytimsamoff: Will you have any time this week?16:21
dneary(it's OK if you don't)16:21
dnearyBut since you have a better eye than me, if you were able to help me wireframe the Support page, that'd be great16:21
-!- acunha [n=acunha@200.184.118.136] has left #maemo-meeting []16:21
timsamoffI have _some_ time.16:21
timsamoffI will work on Support.16:21
timsamoffAnd, my eyes... They ain't so good anymore.16:22
timsamoff;)16:22
dnearyGreat16:22
glaubertsouza:)16:22
dnearyOK - I think we're done for today16:22
dnearyI'd like to meet again next week16:22
timsamoffSet it up! :)16:22
dnearyAround the same time, if it suits everyone16:22
timsamoffThis ia a GREAT time!16:23
glaubertsouzagood16:23
dnearytimsamoff: OK for you? OK for everyone else?16:23
X-FadeOk for me.16:23
dnearyThanks Niels16:23
dnearyThanks everyone for your time!16:23
dnearywazd: Looking forward to that thread on the mailing list16:23
bergiegreat16:23
timsamoffLookin' forward to it. Hopefully, it will be warmer. :)16:23
Jaffa2This time next week should be just as good for me (second week of two of paternity leave)16:23
bergieok, see you next week16:23
dnearyI'm really not sure how "Documentation" snick back into the top-level menu16:24
wazddneary: ok)16:24
timsamoffOh, yeah! Congratulations Jaffa2!16:24
-!- bergie [n=bergie@nemein.suvilahti.nemein.net] has quit []16:24
Jaffa2ta :)16:24
timsamoffLater, everyone... See you all on the List.16:24
dnearyYes - grats Jaffa2!16:25
Jaffa2Everyone's asleep at the moment. But I think there's a stinky nappy to be changed16:25
timsamoffHa ha ha!16:25
timsamoffDon't fall in, Jaffa2.16:25

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!