1 17:06:55 <heidi> #startmeeting
   2 17:06:55 <tota11y> Meeting started Fri Sep 27 17:06:55 2013 CET.  The chair is heidi. Information about MeetBot at http://wiki.debian.org/MeetBot.
   3 17:06:55 <tota11y> Useful Commands: #action #agreed #help #info #idea #link #topic.
   4 17:07:11 <heidi> #topic Updates
   5 17:07:46 <heidi> So my SE teams, why don't you give one update per team?
   6 17:08:19 <heidi> Briefly state your progress and use the #info at the beginning of the line so that the items get in the notes.
   7 17:08:33 <heidi> ScottC and MikeS?
   8 17:08:35 <heidi> Want to start?
   9 17:08:41 <stoney> hi
  10 17:09:09 <heidi> Hi folks,
  11 17:09:17 <MikeS> Currently putting together the SRS, started it last night
  12 17:09:23 <heidi> Ah, good!
  13 17:09:30 <LoganH> #info We are working on the SRS as well
  14 17:09:38 <Amber> Where is this srs?
  15 17:09:47 <heidi> Now put the #info before the line. Something like: #info 3Gnomies have started the Software Requirements Specification
  16 17:09:53 <ScottC_> #info We're currently working on getting the SRS together, should be done by tomorrow night.
  17 17:10:05 <MikeS> thanks scott
  18 17:10:27 <stoney> #info put in a patch for whitespace issues, and start script
  19 17:11:00 <heidi> Amber: SRS = Software Requirements Specification
  20 17:11:17 <Amber> Yes but where are we storing them?
  21 17:11:21 <SeanV> # Everyone on our team has mousetrap installed, but we are currently working on an issue with one user's computers camera
  22 17:11:25 <heidi> Amber: Students in the Software Engineering class are working on creating documentation for MouseTrap
  23 17:11:44 <SeanV> #info Everyone on our team has mousetrap installed, but we are currently working on an issue with one user's computers camera
  24 17:11:58 <Amber> Hmm I worked as a systems analyst and can probably help a lot with srs docs
  25 17:12:23 <heidi> Seanv what is your team? If you include that in your #info that makes it clearer.
  26 17:12:35 <heidi> Ah, great! We'll need folks to review the docs when we publish.
  27 17:13:17 <heidi> #info Heidi is working on applying the patches to fix the white space.
  28 17:13:37 <stoney> where will these docs be published? gnome wiki?
  29 17:13:45 <SeanV> heidi, do you want member names?
  30 17:14:20 <heidi> Don't need that level of detail unless one of you is working on something inddividually.
  31 17:14:26 <heidi> But helpful to be able to differentiate between the teams.
  32 17:14:42 <LoganH> heidi, so jus tthe team name?
  33 17:14:54 <heidi> stoney: The idea is that we'll do an inclass review and make the appropriate changes and then post to gnome wiki.
  34 17:15:10 <stoney> cool
  35 17:15:17 <heidi> LoganH: sure, ad include individuals as you see fit. For instance, if someone is working on something specific.
  36 17:15:53 <heidi> Amber: Are you back yet?
  37 17:16:11 <Amber> Yes just finished my first week
  38 17:16:14 <heidi> Ah, OK>
  39 17:16:24 <heidi> Amber: and could you make sense of the email that Peter Bui sent?
  40 17:16:52 <heidi> Oh, wait. I don't think he sent anything!
  41 17:17:40 <heidi> I'll ping him in the foss2serve channel and see if I can get a response.
  42 17:18:51 <heidi> OK, he said that he will write it up and send "soon". HOpefully todya.
  43 17:19:14 <Amber> Yea I didn't get his comments on the status of the bindings issue
  44 17:19:19 <stoney> I think he's coming over
  45 17:19:20 <heidi> Amber: Right.
  46 17:19:23 <heidi> Ah, OK
  47 17:19:24 <Amber> Ok
  48 17:19:32 <heidi> Ah, good!
  49 17:19:32 <pnutzh4x0r> hey everyone
  50 17:19:34 <heidi> :-)
  51 17:19:36 <stoney> hi !
  52 17:19:42 <heidi> Welcomee pnutzh4x0r !
  53 17:20:03 * heidi thinks that Stoney and I have about equivalent typing skills...
  54 17:20:15 <stoney> :)
  55 17:20:29 <pnutzh4x0r> so here is a summary of opencv + python (i apologize for not doing this sooner)
  56 17:20:54 <pnutzh4x0r> opencv has an in-house python script that parses their header files and generates bindings
  57 17:21:06 <pnutzh4x0r> so it is automated, but they do not use stock tools like swig
  58 17:21:27 <pnutzh4x0r> recently, according to their faq page, they have implemented some support for python3
  59 17:21:28 <heidi> SE folks, the issue here is that we're migrating from Python 2 to Python 3 and OpenCV is not compatible with Python 3 (and GTK 3 I think). So Amber is looking into solutionss.
  60 17:21:34 <pnutzh4x0r> they currently support python2
  61 17:22:11 <pnutzh4x0r> here is the faq page for reference: http://answers.opencv.org/question/15670/status-of-python-3-bindings-for-opencv/
  62 17:22:29 <ScottC_> Is there something 'wrong' with mousetrap on python2?  or features we can't implement in python 2?
  63 17:22:35 <pnutzh4x0r> the opencv github repo w/ this modifications is here: https://github.com/Itseez/opencv
  64 17:22:49 <stoney> #link http://answers.opencv.org/question/15670/status-of-python-3-bindings-for-opencv/
  65 17:22:56 <stoney> #link https://github.com/Itseez/opencv
  66 17:23:08 <pnutzh4x0r> ScottC_: there is nothing 'wrong' except that most linux distros are moving to python 3 and i believe gnome is also making this transition
  67 17:23:20 <heidi> ScottC: Good question. We're trying to update MouseTrap to Gnome 3 which uses python 3.
  68 17:23:42 <heidi> #link http://answers.opencv.org/question/15670/status-of-python-3-bindings-for-opencv/
  69 17:23:54 <ScottC_> Ahh, thanks for the clarification
  70 17:24:08 <pnutzh4x0r> so, where i left off is i managed to clone the github repo and poke around the code
  71 17:24:26 <pnutzh4x0r> but i haven't figured out the right CMAKE invocation to get it to use python3 instead of python2
  72 17:24:41 <pnutzh4x0r> so whoever picks this up will have to figure out CMAKE
  73 17:24:44 <heidi> Amber: Are you familiar with cmake?
  74 17:25:01 <Amber> I can look into it
  75 17:25:09 <Amber> But no
  76 17:25:38 <pnutzh4x0r> so it is now more of a build problem than a programming problem
  77 17:25:47 <heidi> It is a variant of make that works cross-platform.
  78 17:25:49 <pnutzh4x0r> so more system adminstration than developer
  79 17:25:50 <heidi> Ah, OK.
  80 17:26:06 <heidi> Amber: Are you comfortable with that?
  81 17:26:07 <stoney> ScottC: FYI, ubuntu is moving to python3, I think fedora is too
  82 17:26:50 <Amber> I might want a go-to person, but I think its manageable
  83 17:28:13 <pnutzh4x0r> heidi: stoney im still looking for an independent study student, but no luck thus far
  84 17:29:09 <heidi> Amber: OK, good. Let us know how you fare
  85 17:29:22 <heidi> pnutzh4x0r:  :-( Sorry.
  86 17:29:23 <Amber> Okays :)
  87 17:29:35 <heidi> :-)
  88 17:30:05 <heidi> Amber: you can also check with Greg is you'd like on this.
  89 17:30:32 <pnutzh4x0r> alright, i have to run, but feel free to contact me if you need anything else
  90 17:31:06 <Amber> Ok
  91 17:31:17 <heidi> I think then that the status of Mousetrap is that we're almost done cleaning up the formatting/whitespace issues.
  92 17:31:36 <stoney> hopefully
  93 17:31:55 <heidi> Right! :-)0
  94 17:32:02 <heidi> And we're ready to dig into code.
  95 17:32:22 <stoney> need a page on coding standards and tips to help prevent those issues in the future
  96 17:32:30 <heidi> Ah, yes, right!
  97 17:32:31 <stoney> gnome has to have something like that
  98 17:32:42 <stoney> but there are some git tricks that could help too
  99 17:32:51 <heidi> #action Create a page on coding standards and tips for MouseTrap
 100 17:33:05 <stoney> yup yup
 101 17:33:07 <Amber> What was the issue exactly?
 102 17:33:37 <stoney> there were trailing whitespace  (including CR) at the end of lines
 103 17:33:42 <heidi> LoganH:  Right now, MT draws a rectangle around the face, but doesn't track. Do we need the OpenCV issue fixed before we can track? (I'm assuming yes.)
 104 17:33:48 <stoney> these can make applying patches difficult
 105 17:34:02 <stoney> also, indentation had a mix of spaces and tabs
 106 17:34:02 <Amber> There's pep8 checkers for that
 107 17:34:36 <stoney> yes... we should also be using pylint
 108 17:34:42 <heidi> Ummm, "pep8"?
 109 17:34:57 <LoganH> Currently we are drawing a rectangle around the face. I have also added a green dot to specify where mousetrap is currently tracking. The issue is that this point doesn't get updated after the initial call.
 110 17:34:57 <stoney> those are the types of things that we need on this page
 111 17:35:09 <Amber> Python attle checker heidi
 112 17:35:14 <Amber> Style*
 113 17:35:17 <heidi> Ah, thanks.
 114 17:35:23 <heidi> :-) clearly I'm not a python expert.
 115 17:35:40 <LoganH> So no tracking happens. I think we need to fix the tracking issue, so that the point will update as the user moves, and from that we can determine if issues exist with the interface to the cursor
 116 17:37:01 <heidi> Do we need the OpenCV fix before we can do that?
 117 17:37:25 <stoney> by OpenCV fix... you mean python3 bindings for OpenCV?
 118 17:37:50 <heidi> yes. And I'm assuming that the answer is yes. but just verifying
 119 17:37:54 <stoney> no
 120 17:37:56 <LoganH> I don't believe so
 121 17:38:02 <stoney> we are in python2.7 right now
 122 17:38:08 <stoney> and opencv works there
 123 17:38:20 <LoganH> We are still currently running on 2.7. So we can maintain that and regain functionality. And then apply the port when it is fixed
 124 17:38:29 <heidi> Ah, OK.
 125 17:38:38 <stoney> we should be able to make mousetrap work in 2.7 while we wait for python3 bindings for opnecv
 126 17:38:44 <stoney> right
 127 17:38:49 <stoney> what LoganH said :)
 128 17:38:52 <heidi> So the SE class can start digging into tracking.
 129 17:38:54 <LoganH> :)
 130 17:38:58 <stoney> yup yup
 131 17:39:14 <heidi> #info SE students can start looking at figuring out how to implement feature tracking.
 132 17:39:36 <heidi> #info In python 2.7 and we'll port to python 3 when bindings are figured out.
 133 17:40:22 <LoganH> Yes
 134 17:40:39 <heidi> :-) Yippee!
 135 17:41:07 <stoney> you know..
 136 17:41:16 <heidi> OK, we'll get started in class next week.
 137 17:41:19 <heidi> Yes?? :-)
 138 17:41:20 <stoney> I need to write up something on the way mousetrap starts up
 139 17:41:36 <stoney> I posted a patch to blow away the startup bash script
 140 17:41:39 <stoney> but ...
 141 17:41:47 <stoney> that's going to make development a little harder
 142 17:41:57 <stoney> developers are going to need to set ...
 143 17:42:06 <stoney> PYTHONPATH variable so...
 144 17:42:19 <stoney> that python is looking at their code and not the installed version
 145 17:42:28 <stoney> i'll put that in a blog
 146 17:43:07 <heidi> Ah, OK.
 147 17:43:13 <stoney> #action stoney will blog about MouseTrap startup and what developers need to do
 148 17:43:28 <heidi> I need to check with j*oanie about that patch as she had mentioned something last week about how it should work.
 149 17:43:48 <stoney> "how it should work" ?
 150 17:43:56 <stoney> you mean the work flow?
 151 17:44:12 <stoney> oh
 152 17:44:15 <stoney> the script
 153 17:44:16 <stoney> right
 154 17:44:39 <heidi> Right.
 155 17:44:49 <heidi> It should "run from anywhere" which is what i think you did.
 156 17:44:53 <heidi> Just want to check.
 157 17:44:55 <stoney> I'll still write the blog and describe the current startup process
 158 17:44:58 <stoney> right
 159 17:45:03 <heidi> oh, yes! Please do.
 160 17:45:22 <LoganH> :)
 161 17:45:44 <Amber> Do we have a link to the blog?
 162 17:45:56 * stoney getting it
 163 17:46:08 <stoney> #link http://stoney-jackson.blogspot.com/
 164 17:46:47 <stoney> Usually, after I make a fix, I try to blog about what I learned... or how I did it... etc
 165 17:47:02 <heidi> That's really, really good.
 166 17:47:12 <heidi> I've got it on my list to blog this weekend as well.
 167 17:47:15 <Amber> Thank you
 168 17:47:48 <stoney> sure
 169 17:47:57 <heidi> Does anyone have anything else?
 170 17:48:07 <Amber> This is cool btw stoney
 171 17:48:12 <stoney> ty
 172 17:48:55 <stoney> heidi: I've got nothing else
 173 17:49:05 <heidi> OK, so let's call this meeting.
 174 17:49:25 <stoney> OK, next week same time, same place?
 175 17:49:26 <heidi> Thank you all for being here, especially ScottC, SeanV , LoganH and MikeS !
 176 17:49:28 <heidi> Yup!
 177 17:49:33 <heidi> #endmeeting