11:46:49 RRSAgent has joined #mw4d 11:46:49 logging to http://www.w3.org/2009/06/15-mw4d-irc 11:46:57 zakim, this will be dweu 11:46:57 I do not see a conference matching that name scheduled within the next hour, steph 11:47:02 zakim, this will be mw4d 11:47:02 ok, steph; I see UW_MW4D IG()8:00AM scheduled to start in 13 minutes 11:47:20 MEETING: Mw4d bi-monthly meeting 11:47:52 Agenda: http://lists.w3.org/Archives/Public/public-mw4d/2009Jun/0023.html 11:47:57 Present:Stephane 11:48:03 Chair: stephane 11:48:07 make log public 11:48:12 zakim, make log public 11:48:12 I don't understand 'make log public', steph 11:48:18 rrsagent, make log public 11:48:23 rrsagent, make minutes 11:48:23 I have made the request to generate http://www.w3.org/2009/06/15-mw4d-minutes.html steph 11:48:58 MEETING: MW4D IG bi-monthly meeting 11:52:43 zakim, code ? 11:52:43 the conference code is 6493 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), steph 11:53:09 UW_MW4D IG()8:00AM has now started 11:53:16 +steph 12:00:40 kiwanja has joined #mw4d 12:00:42 Arun has joined #mw4d 12:00:57 +Arun 12:01:01 Present+Arun 12:01:56 +??P2 12:02:04 Present+kiwanja 12:02:19 zakim, ??p2 is Kiwanja 12:02:19 +Kiwanja; got it 12:02:23 Raphael has joined #mw4d 12:02:37 + +31.62.247.aaaa 12:02:44 nicolas has joined #mw4d 12:03:10 zakim, aaaa is Nicholas 12:03:10 +Nicholas; got it 12:03:20 Present+Nicholas 12:03:21 +raphael 12:03:27 Present+Raphael 12:03:31 + +0750070aabb 12:03:39 zakim, aabb is betty 12:03:39 +betty; got it 12:03:46 Present+betty 12:04:14 http://lists.w3.org/Archives/Public/public-mw4d/2009Jun/0023.html 12:04:26 Today: collective note taking. 12:04:34 Topic: approval of last meeting minutes 12:04:44 http://www.w3.org/2009/06/08-mw4d-minutes.html 12:04:46 +1 12:04:46 Minutes OK for me 12:04:54 approved 12:05:02 Topic: action item reviews 12:05:26 Lauri to review tools on the wiki and add extra note from .mobi 12:05:29 [postponed] 12:05:42 stephane to send maputo exec summary 12:05:44 [done] 12:05:53 Steph to put maputo executive summary discussion on the agenda for 12:05:53 next mw4d meeting 12:06:22 +Lauri 12:06:33 Present+Lauri 12:06:53 Renjish has joined #mw4d 12:06:59 The report seems self-explanatory for me. And I appreciated it. Thanks to the writer(s) 12:07:30 (last workshop report, I'm refering to) 12:07:42 betty has joined #mw4d 12:08:36 Ken to link with people at georgia tech and present wha t we are 12:08:36 doing and see if they are interested to join 12:09:02 [ongoing] 12:09:13 Steph to draft illiteracy section 12:09:14 + +1.312.799.aacc 12:09:23 Present+Renjish 12:09:28 zakim, aacc is renjish 12:09:28 +renjish; got it 12:09:41 [done] 12:09:52 Stephane add a section background draft some bullet points 12:09:58 [done] 12:10:06 Stephane to create a discussion page attached to the roadmap 12:10:09 [done] 12:10:24 http://www.w3.org/2008/MW4D/wiki/roadmapv2-discussion 12:10:38 Topic: Roadmap discussion 12:10:50 q+ on the discussion page 12:11:30 raphael: idea from mediawiki 12:11:59 the way they workis that everybody can put things in 12:12:06 same here ? 12:12:22 i suggest yes 12:14:10 consensus making process 12:15:28 I agree about the mailing list 12:15:43 stephane: i would suggest we keep links with the email 12:15:45 agree 12:15:49 greater audience 12:15:55 so edition+email 12:16:05 i agree to maintain both due to different audiences, re: bulletin board and mailing list 12:16:52 Steph: People are welcome to add substance on both channels. 12:17:06 OK. 12:17:07 +1 12:17:10 Ok 12:17:45 Lauri is OK. 12:18:21 Adesina has joined #mw4d 12:18:27 q+ 12:18:28 issue: government on audience 12:18:32 lauri: ok 12:18:37 Sure, but do we have specific things in mind for them ? 12:18:43 ack raphael 12:18:43 Raphael, you wanted to comment on the discussion page and to 12:19:12 I am here. I will not beable to audio-join. I am actually in a conference now 12:19:16 q+ 12:20:00 arun: anything we want to explicitly do for them ? 12:20:03 and how to reach them ? 12:20:20 q- 12:21:05 I think we should have an ecosystem description in the audience section which will mention all stakeholders, but the scope should specify the focus of the issues addressed 12:21:23 -Nicholas 12:22:09 no more battery for my cell. I'll follow on IRC. 12:22:36 Audience, add the government & decision makers to assure them about plus/minus, challenges, risks of MW4D. 12:23:07 In addition, government & NGOs should collaborate. 12:23:10 stephane: ecosystem ? 12:23:17 Audience meant stakeholders? 12:23:24 renjish: role of each, and their relationship with others 12:23:36 Lauri has joined #mw4d 12:24:06 Now Lauri managed to join the IRC channel :-) 12:24:11 great ! 12:24:51 Arun: do you mean that the document won't fit all audiences we aim at? 12:25:07 renjish: one way classify stakeholders: enablers, users, providers 12:25:27 I just meant to understand how we would address govt as an audience 12:25:54 It would be ideal if we can influence decision makers but this doc is probably meant to be too technical 12:25:59 I personnally think the doc might be too technical for most Gov people 12:26:05 Govt are major service provider and financier in many developing countries 12:26:20 Agree with Adesina. 12:26:26 As you can see, I agree with you Raphael :-) 12:26:31 indeed ;) 12:26:43 In government, there are also technical staffs. 12:26:49 true 12:27:34 raphael: how to reach this technical staff 12:28:01 making a document at donors and govt, it needs to be simplified 12:28:17 Gov and NGO related issues are mainly policy oriented which we can handle in the future directions section 12:28:25 however, the audience may be wide 12:28:32 better 12:28:32 It's OK to make technical roadmap. 12:29:09 Maybe a section of the docuemnt should specify buy-in or value for each stakeholder in MW4D 12:29:21 could you please repeat, Steph? 12:29:59 Example in Kenia we found IT-director in Governement. Not all governements have them. 12:30:15 Steph: example of the Maputo event with the summary, having few clear key messages. 12:30:21 thanks 12:30:28 q+ 12:31:01 arun: government: decision makers or technical staff ? 12:31:05 q+ 12:31:09 In government: the decision makers could read the executive summary. Then they could consult technical experts to study the technical documents. 12:31:10 q- 12:31:19 ack renjish 12:31:58 It is important not to focus narrowly on technical officers, but policy makers are important as well 12:32:17 Even with IT-manager they don't understand all the possibilites available by mobile services. That is a purpose of our report. 12:32:23 Depending how long the doc is, could we have document segments targeting different segments? 12:32:24 renjish: policies is important 12:32:27 Yes, I agree with recommendation and policy guideline kind of inputs but then we need to decide if this document is the right place 12:32:45 different audiences, I meant 12:33:10 I agree with you Stephane 12:33:30 We don't need to write for each stakeholder but making it clear what are the different values for diff. skateholders is important 12:33:34 stephane: policy guideline is more an output that part of this document 12:33:46 +1 to adesina 12:34:34 should a policy guideline be an output of our group? 12:34:51 A good book is: Mobile Internet for Dummies. But it is too wide. We could make references to good topics in the book. 12:34:59 not really, but identifying value for them in the document 12:36:13 -betty 12:36:31 As I know all the authors of the book, I can negotiate rights to copy some parts of it into our report if needed. 12:37:13 +betty 12:38:03 Luari, what is the link for Mobile Internet for Dummies 12:38:29 it is in paper format, I believe 12:38:58 http://www.wiley.com/WileyCDA/WileyTitle/productCd-0470239530.html 12:39:21 I think we sould write our arguments on the discussion page 12:39:35 since it is a bit complex 12:39:40 this item 12:40:37 action: renjish to summarize policy guideliens discussion on the discsuion page 12:40:41 Agree with Raphael. 12:41:22 http://www.w3.org/2008/MW4D/wiki/roadmapv2#background 12:41:26 issue: background sectoin 12:41:36 you mean context? 12:41:58 thanks 12:42:15 numbered issues, great idea 12:42:27 action: steph to put an issue number in front of each issue 12:43:15 Do you think existing working solutions and their drawbacks shud go here ? 12:44:39 Ok It is fine then 12:44:58 It is more of motivation 12:45:03 The background section can be used to specify value for each stakeholders 12:45:46 Motivation addition seems a good idea 12:45:58 Resolution: background should be transformed in Motivation 12:45:58 to me :) 12:46:02 Yup. Motivation sounds better than background. 12:46:28 issue: context 12:47:02 raphael: identifying context 12:47:07 we cannot list all context 12:47:10 too numerous 12:47:24 but we could characterize some typical context 12:47:42 context is just specifying rationale for the document and while it is important 12:47:45 example: literate rate+connectivty rate 12:48:24 ten to 20 characteristics 12:48:39 We could have pre-requisites listed for every tech. solution. 12:48:43 to define technology possibilities in some context 12:49:21 Writing context for every geo would be too time consuming and dynamic 12:49:52 so we mention the parameters/ characteristics required as pre-requisite by the solution. 12:50:41 q+ 12:51:07 we should leverage existing literature for summarizing the contexts 12:51:27 raphael: a matrix 12:51:36 might be a solution 12:52:07 a summarized way 12:52:10 might be good 12:52:41 raphael: better if i make a proposal 12:53:11 q- 12:53:42 action: raphael to summarize how to deal with context in the discussion page 12:54:08 issue: accessibility issues 12:54:24 Using existing literature is a good is=dea 12:56:42 I tend to agree with Steph. Accessibility is studied quite widely in other places 12:56:57 steph: mention accessibility specificities but out of the scope of this document 12:57:05 the "traditional" issues 12:57:10 Accessibility for developing countries is complicates enough. I suggest wen concentrate on this. 12:57:16 I am fine with Steph's proposal to mention that accessibility issues for developing countries are different than developed countries. 12:57:28 Yup. 12:57:31 +1 12:57:35 agree with everyone re: accessibility 12:57:36 steph: in the scope of the document ? 12:57:37 yes 12:57:53 resolution: accessibility aspect should go to the scope of the document 12:57:54 As time is short, I like to add one technology missing from report now: Web-server in the mobile phone. This means, the mobile web-service don't need a PC at all. 12:58:18 ACTION: steph to write accessiblity aspect in the scope fo the doc section 12:58:28 Interesting point from Lauri - agree we should look at this 12:58:41 sounds interesting indeed 12:59:08 A few NGO/devs are looking at mobile servers to replace laptops/netbooks 12:59:24 Mobiles are increasingly the LDCs PCs 12:59:37 I use this often ;) 12:59:54 can we map that to any existing challenge in the doc? or if missing, we add a new challenge and include this as a potential solution? 13:00:04 action: Lauri to send a mail about Web-server in the mobile phone. 13:00:13 Lauri, any example you could share? 13:00:19 Topic: next meeting 13:00:27 Frontline SMS 13:00:56 ok 13:00:58 stephane: propose an extra one on june 29 13:01:02 ok 13:01:03 June 29 fine with me 13:01:05 ok 13:01:09 agreed 13:01:32 thank you 13:01:46 emails can lead to the discussion page ;) 13:01:48 Raphael, please sen e-mail to me to talk more 13:01:49 bye 13:01:53 thank you all 13:01:53 bye 13:01:54 -Kiwanja 13:01:54 -steph 13:01:54 -renjish 13:01:55 -Arun 13:01:57 -betty 13:02:00 OK, Lauri, thanks 13:02:01 Bye 13:02:04 rrsagent, make minutes 13:02:04 I have made the request to generate http://www.w3.org/2009/06/15-mw4d-minutes.html steph 13:02:16 -raphael 13:02:22 BYE 13:02:52 -Lauri 13:02:53 UW_MW4D IG()8:00AM has ended 13:02:55 Attendees were steph, Arun, Kiwanja, +31.62.247.aaaa, Nicholas, raphael, +0750070aabb, betty, Lauri, +1.312.799.aacc, renjish 14:14:22 steph has left #mw4d 15:01:40 Zakim has left #mw4d