*** Dark_Rose_afk has joined #mousetrap
*** Dark_Rose_afk_ has joined #mousetrap
*** Dark_Rose_afk has quit IRC
*** Dark_Rose_afk_ is now known as Dark_Rose_afk
*** Dark_Rose_afk_ has joined #mousetrap
*** Dark_Rose_afk has quit IRC
*** Dark_Rose_afk_ is now known as Dark_Rose_afk
*** Dark_Rose_afk_ has joined #mousetrap
*** Dark_Rose_afk has quit IRC
*** Dark_Rose_afk has joined #mousetrap
*** Dark_Rose_afk_ has quit IRC
*** Dark_Rose_afk has quit IRC
*** API has joined #mousetrap
*** API has quit IRC
*** API has joined #mousetrap
*** Dark_Rose_afk has joined #mousetrap
*** Dark_Rose_afk has quit IRC
*** AndroUser has joined #mousetrap
*** AndroUser is now known as dark_rose
*** dark_rose has quit IRC
*** amber has joined #mousetrap
*** dark_rose has joined #mousetrap
*** Stoney has joined #mousetrap
*** ghislop has joined #mousetrap
*** ghislop is now known as ghislop_afk
*** john_ has joined #mousetrap
*** heidi has joined #mousetrap
*** ghislop_afk is now known as ghislop
*** burdged has joined #MouseTrap
<burdged> hey
<heidi> Hi All
<amber> hello
<dark_rose> Hello
<john_> hello
<ghislop> Hi Darci! :-)
<Stoney> Hi
<ghislop> a few sidenotes....
<burdged> Lori is going to join us a bit late
<ghislop> Darci: we need to get the food order in for SIGCSE... I'll email you about that...
<burdged> Great...I've been thinking about that
<ghislop> Stoney: I have one of my students working on installing Chiliproject... I'll keep you posted...
<ghislop> OK... that's it :-)  we can start the meeting whenever.
<Stoney> oh wow, cool
<burdged> Are we waiting for anyone else?
<ghislop> Logan?
<heidi> Logan can't make it during this time usually, si I think that we have everyone
<burdged> Ok..meeting started
<burdged> #startmeeting
<tota11y> Meeting started Fri Feb 15 18:04:28 2013 CET.  The chair is burdged. Information about MeetBot at http://wiki.debian.org/MeetBot.
<tota11y> Useful Commands: #action #agreed #help #info #idea #link #topic.
<burdged> who would like to start with updates?
<heidi> How about I start with a reprise of what we learned last time?
<burdged> great
<john_> I guess I'll go first since I have the shortest update: none. Crazy week at school.
<heidi> #topic updates
<heidi> go john
<ghislop> I think that was the update from John?
<ghislop> next?
<amber> ill go
<amber> since last weeks meeting, i found that opencv will not be compatible with python 3
<amber> the version of opencv in the yum repo is 2.3.1
<heidi> Right, that was the update I was talking about.
<Stoney> ack
<amber> version 2.5 might not include python 3 (no rumors yet)
<heidi> This has the potential to be not as much of a problem as might be.
<amber> we might be able to port it over
<heidi> After the end of last week's meeting, Amber and I talked about this issue with Joanie.
<amber> they only said that they are not sure that it can be done, most likely because they did not do significant testing
<burdged> info opencv is not compatible with python 3
<heidi> Joanie then spent some hours checking the compatibility of Mousetrap with Python 3.
<Stoney> burdged need a pound
<heidi> I've just sent you a partial patch that Joanie created to work on this issue.
<burdged> #info opencv is not compatible with python 3
<joanie> the patch gets it compiling to about 89%
<heidi> She also observed that not all applications in Gnome 3 are Python 3.
<heidi> So we should keep this in mind, but keep working on the OpenCV issue and worry about Python compatibility after we get the OpenCV issue fiexed.
<heidi> "fixed"
<dark_rose> I'm starting to document and read about OpenCV and and update the Dev Help page. Added a part about the IRC OpenCV channel
<burdged> #info We should keep working on he OpenCV issue and worry about Python compatibility after we get the OpenCV issue fiexed.
<amber> agreed
<amber> i think we should choose a version
<john_> So why not just leave Mousetrap at Python 2 until the OpenCV community moves over to Python 3?
<amber> *of opencv
<heidi> Well, let's cross that bridge when we get there.
<john_> Do we know which version of OpenCV will be in the repos with Fedora 19?
<heidi> This follows the principles of delaying decisions until they need to be made, providing more flexibility during development.
* heidi looking
<burdged> #info We will make decision about whether to move to python 3 later.
<ghislop> Fedora 19 seems to be scheduled for june 2013...
<ghislop> I suggest we might want to just worry about Fedora 18 for now
<john_> Yes, there should be an alpha out by now though
<heidi> Yes, there is an alpha out now.
<ghislop> Alpha for mid April
<amber> if anything its going to be the 2.4.3 version which is not terribly different from 2.3.1 which is in the repo now
<amber> for fedora 17
<ghislop> (I'm looking at: https://fedoraproject.org/wiki/Releases/19/Schedule
<john_> If we choose a OpenCV version to build against, I thought it'd make sense to use the upcoming one instead of making it work with a version that will get outdated in a matter of months?
*** lori has joined #mousetrap
<john_> Perfect, then
<amber> the code would be the same john (so far as i can see)
<amber> if we choose to do cv2 we would be ahead of the curve
<ghislop> so perhaps OpenCV 2.3.1 is the right target for now?
<john_> agreed
<amber> depends on how we decide to use 2.3.1
<ghislop> Or are you suggesting OpenCV 2.4.3 Amber?
<heidi> And cv2 is also not python 3 compatible, correct?
<amber> there is a cv2 and then they have cv2.cv which has the possibility to use older modules
<amber> legacy modules*
<amber> correct heidi
<heidi> Got it.
<amber> the docs for both are the same.
<john_> Someone said Python 2 is still being actively used in GNOME 3? Then I think we shouldn't bother worrying until we have to (as per Heidi)
<amber> i think i would like johns opinion on the code before we decide
<heidi> Logan is also looking into this.
<Stoney> what has been decided (can we get that into the "agreed" section)?
<burdged> #info Discussions ongoing as to whether we should target OpenCV 2.3.1 or 2.4.3
<Stoney> thanks darci
<Stoney> Fedora 18?
<burdged> oops...I didn't mean to squash the discussion, I thought we had decided to wait
<heidi> #agreed Fedora 18 is development OS
<Stoney> and python 2?
<burdged> I think the answer is yes for now?
<amber> so I should upgrade to 18 then?
<john_> Definitely
<heidi> Yes, please amber.
<amber> #action Amber upgrade to Fedora 18
<Stoney> #agreed Python 2 is development language
<amber> i can do that today
<burdged> Great!
<heidi> The latest version of OpenCV is 2.4.3 as of November 2012.
<heidi> There are about 2-4 releases of OpenCV per year for the past few years.
<ghislop> Is there any reason to consider 2.3.1 then?
<heidi> Version 2.3.1 is September 2011
<heidi> This is why I went looking.
<amber> its in the yum repo for fedora 17
<ghislop> or should we just jump to 2.4.3?
<amber> im not sure about 18 though
<amber> im fine with that
<ghislop> amber: fine with 2.4.3?
<Stoney> how significant are the changes from 2.3 to 2.4?
<heidi> Appears to be 2.4.3
<heidi> 2.4.3 appears to be in Fedora 18
<amber> yes, but i think we should get a plan for code restructuring first
<ghislop> OK
<amber> there are some large changes that would be made
<heidi> Changes to port to 2.4.3?
<amber> yes
<Stoney> so, we need to fix it first on the current version?
<john_> Simpler, more elegant I hope :)
<amber> we could just move to 2.4.3 from where we are
<amber> yes definitely simpler
<john_> Simpler code is easier to debug -- I think we should move over rather than fix it as-is -- just my opinion anyway
<Stoney> assuming we want to move to the newer version eventually... would the move be easier after getting the current version working, or just jump
<amber> yea i was hitting a wall trying to patch everything, so a move would be preferred
<Stoney> john_ beat me to it :)
<Stoney> so target opencv 2.4.3 now?
<amber> yes
<heidi> So we're agreed to jump to OpenCV 2.4.3?
<ghislop> sounds like we have consensus on 2.4.3
<Stoney> #agreed opencv 2.4.3
<heidi> :-)
<burdged> #agreed We will move to OpenCV 2.4.3
<burdged> :-)
<Stoney> sorry :)
<Stoney> I'll stop
<heidi> NO fuss, this is fine.
<dark_rose> I'll start to really look into 2.4.3 and document that as much as I can.
<burdged> No worries...
<amber> dark_rose, you can change around the stuff i put on the dev_help page, it also is documented by version
<amber> if that helps
<Stoney> Are status reports done?
<ghislop> Such progress!
<amber> :)
<ghislop> or other issues to report?
<heidi> Nice job on the Dev Help page by the way.
<Stoney> I know, I love this
<dark_rose> I'll work on organizing the dev page better starting later :)
<burdged> #action dark_rose will work on organizing the dev page
<amber> next topic?
<burdged> It sounds like we've already addressed next steps
<burdged> Are there others?
<amber> i have one more
<burdged> #topic Next Steps
*** tota11y changes topic to "Next Steps"
<amber> i think it would be beneficial for all who will start to code to come up with a plan to reorganized based on the newest version of opencv
<amber> and to have a separate meeting to talk only coding issues
<heidi> Sure, good idea.
<amber> thoughts?
<Stoney> cool
<dark_rose> I would join in but I'm working more on the history and such rather than coding lol
<burdged> Do we want to discuss a day/time or do a poll?
<heidi> Hmmm, do you want to upgrade to Fedora 18 before upgrating OpenCV amber?
<amber> i will upgrade today to fed 18
<amber> and then i can start the opencv next week
<heidi> OK, that makes sense.
<ghislop> So perhaps a student meeting around the middle of next week?
<amber> i can create a page with some issues we should look into
<ghislop> (to discuss the code issues)
<heidi> Sure, that would work well.
<amber> yes
<heidi> Wednesday at noon might work. I think that Logan has that time free.
<amber> i can do that
<dark_rose> Wednesdays work for Logan and I at noon
<burdged> #info amber suggested that a separate meeting time be set up to discuss coding issues
<john_> I have the whole week off -- if I can do anything please let me know
<amber> how versed are you in the mousetrap code john?
<john_> (after a day or two to recuperate from this week :D)
<john_> Unfortunately I don't know Python
<john_> Apparently it's easy to learn, right?
<amber> yes
<burdged> It may be helpful for John to lurk anyway?
<amber> what have you done before?
<Stoney> I think that's what you're doing on break!!
<john_> C and Java
<amber> your fine
<Stoney> :)
<dark_rose> Python is more plain language than java and C
<amber> should be cake
<dark_rose> So yea you'll be fine :D
<amber> and plus the opencv backend stuff was in C and now is in C++
<dark_rose> Lots of documents online for python as well
<burdged> So, everyone can make it Wednesday at noon?
<amber> yes
<john_> What time?
<dark_rose> Yep, I'll let Logan know to
<Stoney> noon
<john_> I'm not sure -- I work on Wednesday
<john_> I'll try to make it
<amber> i can put together some meeting notes/ describe how moustrap works
<heidi> Ah, that would be great amber.
<amber> #action amber put together notes for wednesdays code meeting
<burdged> Should we include notes from Wednesday's meeting along with our other meeting notes?
<heidi> Yes, makes sense to do so.
<amber> i was thinking it was more like part of the dev_help page eventually
<heidi> Yes, that too!
<heidi> Its easy to post the notes.
<amber> so ill just write them up to the help page first?
<ghislop> sure
<dark_rose> I would say to put the notes as a last section on the page.
<amber> surely
<ghislop> have we done enough damage for today?
<burdged> Any other 'next steps'?
<dark_rose> I think so lol
<amber> i think we all have stuff to do
<amber> :)
<dark_rose> 7 page paper coming up for me....lol
<amber> good luck
<dark_rose> Thanks!
<burdged> It sounds like we can end the meeting?
<amber> #note
<amber> #note meet in mousetrap irc for wednesday code meeting
<heidi> I think that should be a pound sign "info" amber
<burdged> Sounds great, thanks amber
<amber> #info meet in mousetrap irc for wednesday code meeting
<heidi> :-)
<burdged> Thanks everyone!
<Stoney> bye!
<dark_rose> Bye
<john_> bye
<amber> have a nice weekend!
*** Stoney has quit IRC
<burdged> Bye
<john_> see you on Wednesday
<heidi> bye
<burdged> #endmeeting
*** lori has quit IRC
<tota11y> Meeting ended Fri Feb 15 18:45:27 2013 CET.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
<tota11y> Minutes:        mousetrap/2013/mousetrap.2013-02-15-18.04.html
<tota11y> Minutes (text): mousetrap/2013/mousetrap.2013-02-15-18.04.txt
<tota11y> Log:            mousetrap/2013/mousetrap.2013-02-15-18.04.log.html
*** tota11y changes topic to "Mousetrap"
*** dark_rose has quit IRC
<burdged> Greg: would it be easier to talk about food for the workshop or use email?
<heidi> ghislop, wanna talk food?
<ghislop> burdged: email I think
<ghislop> I need to go back and look at the menu again...
<burdged> ok...sounds good
*** john_ has quit IRC
<ghislop> burdged: I'll send you something... or put together your thoughts... whoever gets to if first.
<ghislop> burdged: there's a spreadsheet in dropbox OpenFE Share with a draft of attendees...
<burdged> I saw that, if I recall we have about 10 people?
<ghislop> yes.  should be able to nail down an exact number by Tuesday...
<burdged> Are you expecting more?
<ghislop> ( Sean is undecided, but good chance he won't come... John I want to confirm as not coming...)
<ghislop> I'm not sure if Michelle's event includes dinner
<ghislop> I'll ping all of them and get answers by early next week..
<ghislop> Oh - we're still discussing with Revi whether she's coming at the beginning or end of the day.
<ghislop> I'll work on nailing all that down
<burdged> What about John Dulaney from College of Charleston?
<burdged> He posted something on TOS the other day
<ghislop> burdged: so I guess my suggestion is that we work out menu selections over the next few days and aim to order by Tuesday?
<ghislop> Hmmm I remember seeing the name on TOS... did he inquire about the workshop?
<ghislop> (and are you guys off next week?)
<burdged> Yes, we are off next week
<ghislop> will you be on email some? or is this plan going to be a problem for you?
<burdged> I plan to work almost every day...so, no problem, I will be available
<ghislop> OK.  My inclination is to say: "do take some break!"  but I understand how this happens :-)
<burdged> :-)
<ghislop> so that seems like a workable plan.. OK?
<burdged> Yes
<burdged> Ok...I'm gonna run.
<burdged> I'll be in touch.
<ghislop> take care... have a good weekend ....
<burdged> Thanks, you too!
<burdged> Bye heidi
*** burdged has left #MouseTrap
*** amber has quit IRC
*** API has quit IRC
*** Stoney has joined #mousetrap
*** dark_rose has joined #mousetrap
<dark_rose> heidi, i just reorganized the Dev Help page and added a section for the code meeting notes
<heidi> Ah, good!
<heidi> I'm guessing that you'll likely want to just summarize what you learned and post on the actual page.
<dark_rose> yea, im assuming Amber will take care of that unless she asks me to, i provided the section to start us off
<dark_rose> mostly cuze im still behind everyone when it comes to straight coding lol
<dark_rose> but anyways i'm doing a little more reading then leaving for the day, i'm going to try to work a little more tomorrow depending on how far i get on my essay and homework, have a good weekend and see you monday!
*** dark_rose has quit IRC
*** Stoney has quit IRC
*** ghislop has quit IRC
*** heidi has quit IRC