15:02:47 <rebelsky> #startmeeting
15:02:47 <zodbot> Meeting started Thu Jun 27 15:02:47 2013 UTC.  The chair is rebelsky. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:47 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:02:59 <rebelsky> #chair camm
15:02:59 <zodbot> Current chairs: camm rebelsky
15:03:30 <rebelsky> #topic Greetings
15:03:41 <rebelsky> Camm and Rebelsky seem to be here.  Is anyone else?
15:04:36 <rebelsky> camm: Is it okay if we don't meet next week since it's July 4 (a holiday in the US)?
15:04:56 <camm> Sure, I think every 2 weeks is more reasonable
15:05:26 <rebelsky> I see some reasons for weekly meeting in terms of the incentive for people to get things done for each meeting, but perhaps I'm just optimistic.
15:05:54 <rebelsky> pnutzh4x0r: Are you lurking?
15:06:18 <camm> Well, I'm good either way.  I'd of course like to keep our momentum from Philadelphia going
15:06:26 <rebelsky> Me too.
15:06:45 <rebelsky> Well, it seems like it's just you and me today.  I think some folks are heading off to ITiCSE.
15:06:53 <rebelsky> Since it's just the two of us, we can try for a short meeting.
15:07:00 <rebelsky> #topic Activities
15:07:30 <rebelsky> Some of my effort this past week has been on rewriting my proposal and extending the list of exercises.
15:08:04 <rebelsky> #link http://foss2serve.org/index.php/Rebelsky_Work_Log
15:08:09 <rebelsky> Whoops.  That was my work log.
15:08:22 <rebelsky> #link http://foss2serve.org/index.php/RebelskyProposal The revised proposal
15:08:48 <rebelsky> I also looked at building the Ushahidi Andoid App.
15:09:26 <rebelsky> My students, who have experience building Android App, had difficulty with this one.
15:09:36 <rebelsky> Although I was able to follow the instructions and at least get something to compile.
15:09:51 <camm> that's a very detailed proposal, well done
15:10:15 <rebelsky> #llink https://wiki.ushahidi.com/display/WIKI/Build+The+Android+App
15:10:31 <rebelsky> These are the instructions we (mostly) followed.
15:11:04 <rebelsky> One stumbling block in the instructions: You need a Google Maps key, which requires that you have an identifier for your android app, which seems to require some other steps.
15:11:28 <rebelsky> We tried building without that step and our build of the app seems to lack maps.
15:12:35 <rebelsky> I also started a short page on building the app on the Wiki
15:12:44 <rebelsky> #link https://wiki.ushahidi.com/display/WIKI/Build+The+Android+App Preliminary notes on building the app.
15:14:13 <camm> Open Street Maps is not an option for the Android version?
15:14:15 <rebelsky> #link http://foss2serve.org/index.php/Ushahidi_Android_Application Preliminary notes on building the app for real.
15:14:33 <rebelsky> As far as we could tell, Open Street Maps isn't an obvious option.  But we haven't looked in depth.
15:14:44 <rebelsky> My research students are a bit intimidated by dealing with the App code.
15:15:07 <rebelsky> (Sam notes that he has to pay a bit more attention to the links that he copies and pastes.)
15:15:46 <rebelsky> We've started writing a small API to make it easier for students in the class to access Ushahidi data.
15:17:02 <rebelsky> But the public API is not very well documented.
15:17:12 <rebelsky> #link https://wiki.ushahidi.com/display/WIKI/Ushahidi+Public+API Ushahidi Public Web API
15:17:23 <rebelsky> Or maybe it's just not very well designed.
15:17:35 <rebelsky> For example, it doesn't seem like there's a way to specify how many incidents you want.
15:17:39 <rebelsky> Or a range of incidents.
15:18:17 <rebelsky> And the things like sinceid don't behave the way one would expect.  For example, if you start with a sinceid of 1, it doesn't return the earliest incidents.
15:18:57 <rebelsky> With some digging around in the forums (fora?) we were able to find some workarounds, but it took awhile.
15:19:30 <rebelsky> (Note: When I say "we", it is not the royal "we".  It's "My students and I".)
15:19:58 <rebelsky> Finally, we met with Susan Sanning, Grinnell's director of outreach.
15:20:10 <rebelsky> She suggested a few possibilities for the class Ushahidi app.
15:20:41 <rebelsky> She also suggested some good clients for the small-team projects at the end of the semester.
15:20:47 <rebelsky> And some possible projects for that, too.
15:21:26 <rebelsky> #link http://bit.ly/14ZG1UT Notes on Rebelsky team's meeting with Grinnell's director of community outreach.
15:21:39 <rebelsky> Boy, I'm typing a lot.
15:21:41 <camm> So we had some intense flooding here in Alberta last week
15:21:49 <rebelsky> I'm sorry.  Are you and your family okay?
15:21:54 <camm> down in Calgary, not sure if it made the news
15:22:21 <rebelsky> It didn't seem to make the NYTimes, which is my primary news source.  (Okay, it didn't make the "Top News" of the Times, which is really my primary news source.)
15:22:45 <camm> Someone setup a crowdmap for it
15:22:48 <camm> I'll try and find the link
15:23:01 <rebelsky> Cool.  I look forward to seeing it.
15:24:23 <rebelsky> #link https://crowdmap.com/map/calgaryfloodcleanup2013/ Calgary Flood Cleanup Map
15:24:25 <rebelsky> Is that it?
15:24:28 <camm> https://albertaflood.crowdmap.com/main
15:25:49 <camm> the one I linked is a map for the flood dangers, roads washed out, etc.
15:26:03 <camm> the one you posted is a response
15:26:10 <camm> cleanup map
15:27:49 <rebelsky> (Sorry ... distracted by looking at the map.)
15:27:56 <rebelsky> A nice, powerful, example.
15:28:45 <rebelsky> #link https://albertaflood.crowdmap.com/main Alberta 2013 Flood Crowdmap
15:28:55 <rebelsky> (Added the link tag so that it gets put in the summary.)
15:30:27 <camm> yes, thank you
15:30:44 <camm> does the cleanup map have any info on it?
15:31:00 <rebelsky> No.  Just a "Please post information on cleanup activities."
15:31:15 <camm> that's too bad
15:31:37 <camm> I know the albertaflood one was just using news information, I don't know if it had citizens posting
15:31:58 <rebelsky> The few reports I looked at seemed to be just news and tweets.
15:32:29 <rebelsky> But it's clear that we can find a variety of good motivational examples and potential projects.
15:34:15 <rebelsky> #topic Wrapup
15:34:35 <rebelsky> It's been good chatting quickly, but i assume you have to get back to the kids (or at least you did last time) and my students are clamoring for help.
15:34:54 <rebelsky> #action Meet in two weeks.
15:35:57 <rebelsky> #action Sam should have some sample assignments (and supporting code) ready by then.
15:36:11 <camm> sounds good Sam, I'll send an email to find out where people are at
15:36:29 <rebelsky> Great.  Have a good two weeks!
15:36:31 <camm> June 11 is it
15:36:40 <rebelsky> Probably July 11 :-)
15:36:47 <camm> or that ;)
15:37:01 <rebelsky> See you then.
15:37:02 <camm> clearly I need some breakfast too, not just my kids
15:37:08 <camm> see you then
15:37:14 <rebelsky> #endmeeting