11:00:56 #startmeeting Nemo steering group meeting 14/2/2012 11:00:57 Meeting started Tue Feb 14 11:00:56 2012 UTC. The chair is Stskeeps. Information about MeetBot at http://wiki.merproject.org/wiki/Meetings. 11:00:57 Useful Commands: #action #agreed #help #info #idea #link #topic. 11:01:41 i think we have two items today, deciding if jukkaeklund should be representative of nemo project within the Mer advisory board, and what to do with steering group/governance 11:01:48 any objections to that agenda? 11:02:09 sounds good 11:02:10 and status, of course 11:02:35 Maybe short report from FOSDEM for those who were not present? 11:02:55 too much beer :) 11:02:58 i think we can cover that under status as that's status for the project in general 11:03:02 vgrade: ;) 11:03:37 #topic jukkaeklund as representative of nemo project within the Mer advisory board 11:03:43 hi 11:04:13 we have a advisory board meeting in Mer on friday and i have nominated Jukka to be our representative -- any objections to this? 11:04:52 I second that nomination. 11:04:56 +1 11:05:17 and jukka agrees too? ;) 11:05:25 well, yes 11:05:29 alright then 11:05:38 +1 11:05:44 #agreed jukkaeklund is our representative towards Mer project in the advisory board 11:06:00 thanks for the trust, I hope I'm worth it 11:06:11 please approach him if there's any issues you want to raise on behalf of nemo project, i guess :) 11:06:30 #topic Governance 11:07:16 we haven't gotten terribly many nominations for steering group and i'd like to suggest that instead we run contributor meetings every 7/14 days for sync and when those have grown big enough, to select a steering group? 11:07:34 sounds sensible 11:07:36 as there's not terribly a lot of governing that can't be done with a proper discussion 11:07:42 +1 11:08:11 sounds sane 11:08:14 :nod: 11:09:06 +1 11:09:28 so, sync meeting every week at this time to hear what has happened since last and plan? 11:09:41 then we have bug triages and sync meetings 11:10:25 sounds good to me 11:10:41 yep 11:10:42 I'd like to re-raise the "Nemo as vendor" role too 11:11:23 most of Nemo's efforts are about making a great device platform (which is cool) 11:11:25 lbt: elaborate? (i wasn't in last meeting) 11:12:04 I just want us to check if "being a reference vendor" is still part of our goals 11:12:46 lbt: IMO it should be still one of our goals as well. 11:12:48 i think in every way we still are 11:12:56 and what deliverables we have that demonstrate or support that role 11:13:08 other than "watch what we do" :) 11:13:10 nemo helps validate mer a lot 11:13:23 I totally agree 11:13:30 as well as contributing effort, etc 11:13:42 I'm just asking if it should be more explicit in what Nemo delivers 11:14:12 lbt: well, a good place to start is defining what a vendor is optimally doing 11:14:15 #agreed Sync meetings every week at 11:00 tuesdays 11:14:20 #agreed (UTC) 11:14:37 Stskeeps: yes - is that a Nemo deliverable? 11:14:40 Stskeeps: I propose that you keep chairing these 11:14:46 veskuh: yes, that's my idea 11:15:04 great. 11:15:13 we could probably replace me with a handy written python script ;) 11:15:27 lbt: well, we show best practices 11:15:35 do we? 11:15:36 lbt: do you mind if we take this discussion after status? 11:15:40 sure 11:15:43 alright 11:15:53 #topic Status since last 11:16:48 #info my effort into Mer: SB2-OBS now running in Mer production, patches sent upstream, qtwebkit 2.2.1, soon to come to a OBS near Nemo 11:17:42 #info Great reception of open mobile linux devroom in FOSDEM, very well attended, we need a bigger devroom next year 11:18:53 #info did talk on Beyond Traditional Mobile Linux, http://fosdem.org/2012/schedule/event/mobile_beyond , slides available on page, video to come 11:19:03 (that's it from me, i think) 11:19:10 apps client is there and working, which is great 11:19:49 #info we changed from upstream Helium to own fork HeliumReborn, since upstream does not seem to be moving anymore. 11:20:43 #info Nemo Mobile FOSDEM presentation slides available at http://sage.kapsi.fi/Nemo/fosdem2012-nemo-presentation.pdf 11:20:46 #info New weekly release 0.20120120.1.NEMO.2012-02-09.1 is out http://www.mail-archive.com/mer-general@lists.merproject.org/msg00237.html 11:23:20 Since we have silence, lemme ask. Can we (at some point) open the can of worms of packaging, rpm vs deb? Since Tizen went Debian (?) 11:23:39 xruxa: nah, they didn't :) 11:23:45 xruxa: even tizen is a confusing mess 11:23:47 they're still fighting apparently 11:23:53 xruxa: intel says it's rpm, samsung says it's deb 11:24:06 meanwhile we deliver... 11:24:19 xruxa: i'd like to sync on packaging with the qtonpi project ideally, at least 11:24:37 sounds like answer to me :) 11:24:44 * Sage_ doesn't want to talk about rpm vs deb anymore. 11:24:48 i wouldn't mind supporting '.wgt' 11:24:55 ie, the html5 wac stuff 11:24:59 but that's another story :) 11:25:20 the selection is done could we just live with it? :) 11:25:31 yes <---- debian guy 11:26:06 so... shall I pipe up on vendor thing? 11:26:13 or are we too tired :) 11:26:14 any other status first? 11:26:32 I heard that new pics app is making good progress 11:26:39 also calendar apparently 11:26:44 on a sidenote, anyone interested in trying to package phonegap-qt4 in nemo? 11:26:51 it should be a slam dunk qmake project 11:27:21 I'm curious also to hear how that works 11:28:02 also ... what's happening on roadmap for MTF and Qt5 and things. Is there a page? 11:28:13 qt5 requires mer support 11:28:24 sure 11:28:32 but planning and thinking 11:28:36 and we are slowly working on rewrites but our hands are few 11:28:53 does phonegap contain demo application to test all features? 11:28:57 Sage_: it does 11:29:06 I would like to see a page saying where we are on some of these big frameworks and where we are going (and why) 11:29:09 hmmp.. 11:29:11 lbt: actually having that kind of high-level roadmap on wiki would be a good idea. 11:29:21 veskuh: yes 11:29:23 I think so far its been on our heads but not in paper 11:29:40 veskuh: we can start with our glorious nemo plan, that pretty much lists it 11:29:48 on things that happened and what didn't 11:30:03 Yes, I think I can write up something about that. 11:30:06 :nod: 11:30:38 regarding qt5 they're finally in feature freeze so maybe it will be possible to have package that works on the next morning's snapshot 11:32:20 bye bye 11:32:34 ah, netsplit 11:32:39 let's give them a second to come back 11:32:49 w 11:32:49 b 11:33:13 think we lost jukka in the turn 11:33:22 yep he said he had to go 11:33:26 ah 11:33:46 okay, anything else before we discuss the vendor relationship? 11:34:00 what was the last message you guys read? 11:34:28 Stskeeps's qt5 feature freeze 11:35:10 :O I didn't read that....did you read jukka's message about app's client? 11:35:28 [12:19] apps client is there and working, which is great 11:35:38 we can see it in meeting log afterwards 11:35:40 * Stskeeps points to merbot 11:36:12 ok good, then I said I'll push qmlgallery v0.0.0.1 before the evening comes, so that you can give some feedback and drive the development 11:36:16 cool 11:36:18 okay, i guess we can switch to reference vendor relations 11:36:25 #topic reference vendor definition 11:36:40 and jukka said 11:36:41 overall I think Nemo is looking very good now and many issues have bugs already waiting to be taken 11:36:55 as a start, we can't really commit to anything, except in how we generally work as a project 11:36:58 hehe ... so this was just meant to be a gentle reminder about that role 11:37:03 so when I said "do we" ... I was meaning "do we *show* best practice?" or do we just follow it? Where are our day-to-day tasks? The wiki page saying how do we react to a Mer release? Is the best way to learn Nemo is to hang out in irc, read backlogs or mailing list archives...? So I'm *asking* if others want to help deliver these things. I clearly think we should and I'm going to be working on it but I'd rather it was a Nemo goal/ 11:37:05 deliverable :) 11:37:18 :nod: 11:37:34 lbt: cut after goal/ 11:37:40 so basically a plea to write more stuff down 11:37:41 i think it indirectly is, we help with driving documentation as well, interaction problems/etc 11:37:44 :nod: 11:38:09 Sage_: just " ...goal/deliverable :) " 11:38:29 i guess part of the difficulty is that new mer releases get handed to us on cobs ;) 11:38:35 so it's transparent to us 11:38:42 Sage_: in particular I want to do a "day/week/cycle in the life of a vendor" 11:38:46 Stskeeps: yes indeed 11:39:37 lbt: so in the end you are after more documentation between the interaction of Nemo and Mer? 11:39:37 I think Sage's release routine for taking mer release and making nemo release would be worth documenting 11:39:42 :nod: 11:39:49 Sage_: yes 11:40:05 so ... one solution I use is to try to follow my own instructions when i do stuff - also see if others can do it for me 11:40:09 veskuh: true 11:40:42 veskuh: I can do that. 11:40:52 * Sage_ writes note about that 11:41:03 so ... what I wanted was a "yes this is still in scope" and "yes we'll try and be more explicit about having deliverables for it" 11:41:16 maybe even bugs for missing docs/processes 11:41:24 :nod: 11:41:34 yes, I'm all for task bugs. 11:41:44 thanks ... and sorry for being boring :) 11:42:09 * Sage_ thinks lbt just inspired him to do some documentation 11:42:11 i think it's a responsibility of every vendor to provide a better experience for themselves 11:43:02 * lbt offers to buy sage a cider at the next FOSDEM :D 11:43:44 * Sage_ smiles 11:44:35 cool, well, I have SDK and OBS stuff to do.... 11:44:44 alright, thank you all for coming 11:45:03 thanks. It's been good to see a lot of activity in IRC today :) 11:46:10 think most people are either on or over their fosdem flu :P 11:46:11 #endmeeting