11:03:12 #startmeeting Nemo steering group meeting 11:03:12 Meeting started Tue Jan 17 11:03:12 2012 UTC. The chair is stskeepsie. Information about MeetBot at http://wiki.merproject.org/wiki/Meetings. 11:03:12 Useful Commands: #action #agreed #help #info #idea #link #topic. 11:03:42 welcome to another week of nemo steering group meeting, i'm a little limited by that my server just crashed 5 minutes before the meeting, so bear with my slowness :) 11:03:45 #topic Status 11:04:49 Mer core still approaching, we decided to include qt 4.8.0 and qtwebkit 2.2.1 11:04:57 so we have (finally) a stable non-rc version 11:05:18 #info Mer core still approaching, we decided to include qt 4.8.0 and qtwebkit 2.2.1 11:05:21 (theoretically stable... ;)) 11:05:56 yesterday i put out a post about bootstrapping Mer governance, http://www.mail-archive.com/mer-general@lists.merproject.org/msg00131.html 11:06:13 and we should probably before 31st january choose a representative for the Mer advisory board from Nemo Mobile POV 11:06:21 #info Mer governance http://www.mail-archive.com/mer-general@lists.merproject.org/msg00131.html 11:06:42 any comments on the structure/governance is of course welcome on the mailing list 11:07:19 Looks fine. 11:08:13 So we have two weeks and this starts beginning of feb? 11:08:19 right 11:08:27 seat's reserved 11:10:23 so this next mer release is to be released on Thursday if nothing bad is found from prerelease? 12:05:30 .. okay 12:05:32 right on time ;) 12:05:33 :) 12:05:36 #endmeeting 12:05:50 stateful in memory ... tut tut 12:05:56 Stskeeps: Error: Can't start another meeting, one is in progress. 12:06:07 oh ffs 12:06:12 nope... just broken 12:07:11 okay, anyway, let's go through a quick status of release management and release planning 12:07:40 i'm planning a new prerelease of Mer tomorrow hopefully, which will include a bunch of changes, including speedup in symbol lookup and Qt 4.8.0 and qtwebkit 2.2.1 12:08:21 dm8tbr: could you reboot merbot? it's stuck in a meeting 12:09:17 i've been working on new ways of preparing and sharing Mer image descriptions, both the core, hardware adaptations, UX, in order to be able to have a feeling of just pulling additions to your product off a shelf 12:10:12 http://releases.merproject.org/~carsten/mer-kickstarter-configs/ is an example, mer/ contains descriptions of the core that people can derive from, includes repository information, basic settings, etc. mer-reference-images is the images that will be included with mer release, useful for hardware porting, or as examples for your product 12:10:24 and ks/ is the outputted kickstart files (still some bugs to fix) 12:10:53 i also started documenting the kickstarter format on wiki 12:10:58 .. what about the rest of you? 12:11:16 This is good - fits right alongside the work I'm doing on getting systems setup and actually starting a new product 12:11:59 I'm using the Joggler as a product (it's an Atom powered Openframe pictureframe) 12:12:03 StsKeeps: this work is very useful for me:) 12:12:31 yes, for all of us 12:12:32 this is helping get the kernel packaging setup and I'm also going through some first-mer-boot docs too 12:12:55 I'm not yet at the stage where I'm pulling in updates but it's on the plan 12:13:23 essentially I'm going to do "a day/week/month,,, in the life of a vendor" 12:13:42 to go through all the things like integrating a new Mer release 12:14:03 or managing an old internal release after Mer has been updated 12:14:24 bug submission and tracking ... whilst keeping my bug 'private' 12:14:49 so tbh a lot of this is spread out as bullet points and notes at the moment :) 12:15:08 I hope to get the first bit up this week 12:15:08 we should probably do a handbook outline or something 12:15:29 yeah ... I also have that "concept index" I'm working on too 12:15:49 but a handbook is another way to look at the "day in the life of" 12:16:04 (you could also call it process documentation :) ) 12:16:18 :nod: 12:16:50 I need to make some time to look at infra too 12:16:56 there's a fair backlog there now 12:17:04 but I think phaeron can help out there 12:17:47 ok... done until I remember something else 12:17:57 lbt: I think we all know the basic steps of building. Maybe the handbook should focus on some important points. 12:18:10 sonach: suggestions welcome 12:18:26 especially for prioritisation of docs 12:20:01 or what docs are missing :) 12:20:17 For me now, I am porting Mer to my platform. I can get sources of bootloader and linux kernel of the platform. But I don't know how to config/package/... 12:20:37 right 12:20:44 I have docs on exactly that 12:21:27 I'm doing a small tool that will check your .config and say "you need CONFIG_AUTOFS" .... because systemd needs it 12:21:44 http://wiki.merproject.org/wiki/Adaptation_Guide#Kernel 12:21:59 is that what you meant sonach ? 12:22:41 but also how to package a kernel, i presume 12:22:54 lbt: Yes! It seems good to me:) 12:23:06 Stskeeps: got that covered too 12:23:35 you need a git tree with a set of commits and a baseline tag 12:23:48 it prepares a .yaml section for the patches 12:23:54 and all the patches etc 12:24:13 lbt: just remember that that's not a typical scenario for someone getting a reference board, a tarball is 12:24:27 ... worst case you feed it a tarball 12:24:29 ok 12:25:02 I'm sure sonach has a nice kernel git tree though ... :D 12:25:51 so, my goal is that the kickstarter stuff is in next mer kernel so we can start using that 12:26:11 lbt: No git tree, but source code in a tarbar privided by the vendor. 12:26:46 sonach: *grin* .... I'm sure we'll manage 12:27:55 right, anything else to report? 12:28:48 we have a week and a bit to FOSDEM 12:29:37 err, no 2 weeks... nm 12:30:02 nothing from me 12:30:51 ok, thank you all for coming 12:30:57 Stskeeps: Where can I report my porting process? to the mailing-list? 12:31:49 yes, if you have any questions or the likes or want to share experiences, mailing list is good 12:31:56 even asking where documentation for things is 12:32:25 and if you have any issues to discuss then raising them here is fine as well 12:32:30 OK. 12:32:54 nothing from me 06:53:04 #endmeeting 06:53:15 Stskeeps: Error: Can't start another meeting, one is in progress. 06:59:17 #endmeeting