fluid-work IRC Logs-2011-10-17

[08:20:34 CDT(-0500)] <jhung> justin_o: I pulled in your changes this morning and now I have a multi-headed code monster.

[08:25:54 CDT(-0500)] <jhung> justin_o: nm. I figured it out. Had to do a 'hg merge' the 'hg commit' before I can push out to my repo.

[08:26:13 CDT(-0500)] <jhung> if you want, you can pull in my changes to the Import now from my repo.

[08:28:17 CDT(-0500)] <colinclark> jhung, Justin_o: Do you guys have a link handy to our Decapod iteration plans?

[08:28:41 CDT(-0500)] <jhung> colinclark: http://wiki.fluidproject.org/display/fluid/Decapod+0.5+Planning

[08:28:53 CDT(-0500)] <colinclark> Awesome, thanks!

[08:33:00 CDT(-0500)] <colinclark> jhung: How about latest wireframes--both the long term ones and those for the 0.5 iteration?

[08:33:44 CDT(-0500)] <jhung> colinclark: see the children to this page for 1.0 and 0.5 wireframes

[08:33:45 CDT(-0500)] <jhung> http://wiki.fluidproject.org/display/fluid/Decapod+Design

[08:34:14 CDT(-0500)] <colinclark> ah, cool

[08:58:35 CDT(-0500)] <Justin_o> jhung, colinclark: i also made a change on the weekend to the decapod-server

[08:58:50 CDT(-0500)] <Justin_o> it was a change to the configuration so that the lib directory would be available as a resource

[08:59:52 CDT(-0500)] <Justin_o> anastasiac: i was looking for some info on how the uploader sends files back to the server. I've been having some trouble locating the documentation on how the uploader communicates with the server

[09:00:26 CDT(-0500)] <Justin_o> anastasiac: i was able to find the page you suggested, the faq, but had to search for it to find it

[09:00:35 CDT(-0500)] <anastasiac> Justin_o, sounds like we have a gap in our docs.

[09:00:54 CDT(-0500)] <colinclark> Justin_o: Hopefully that was an exceedingly easy thing to do

[09:01:00 CDT(-0500)] <anastasiac> Justin_o, maybe I can sit with you and you can show me where you searched i.e. where you were expecting to find it

[09:01:29 CDT(-0500)] <Justin_o> anastasiac: sure.. whenever you like

[09:23:20 CDT(-0500)] <Justin_o> colinclark: yes, that was pretty easy.. once i remembered about the config file

[09:23:46 CDT(-0500)] <colinclark>

[09:23:56 CDT(-0500)] <colinclark> Is there anything I can help with in terms of Uploader and the server?

[09:24:34 CDT(-0500)] <Justin_o> colinclark: just trying to figure out how the POST works at the moment.. do you happen to know if there are docs on this.. otherwise i'll checkout the image gallery and the code

[09:24:52 CDT(-0500)] <colinclark> I doubt there are much in the way of docs, though there should be

[09:24:59 CDT(-0500)] <colinclark> It's a standard form submit

[09:25:12 CDT(-0500)] <colinclark> So Uploader POSTs to the server...

[09:25:27 CDT(-0500)] <colinclark> using the standard multipart MIME envelope

[09:25:51 CDT(-0500)] <colinclark> Meaning, any server-side file upload documentation should explain what you need to do on the Python side of things

[09:26:04 CDT(-0500)] <Justin_o> colinclark: ah great.. i'll dig into that then

[09:26:19 CDT(-0500)] <colinclark> Uploader issues one POST per file

[09:26:28 CDT(-0500)] <colinclark> so there's no worry about having to unpack multiple files from the request or anything like that

[09:27:44 CDT(-0500)] <Justin_o> ah okay.. that will be easier then

[09:28:57 CDT(-0500)] <Justin_o> colinclark: do you know which version of cherrypy we're using?

[09:29:39 CDT(-0500)] <colinclark> Off the top of my head, no

[09:30:00 CDT(-0500)] <Justin_o> colinclark: i guess it's somewhere in the install script.. i'll check there

[09:30:23 CDT(-0500)] <colinclark> Should be, yes

[09:31:04 CDT(-0500)] <Justin_o> jhung,colinclark : wondering about what we should do with stitching and capture/calibration.. i think we were going to remove them from in this iteration.. should these be removed or just not used? if you know what i mean

[09:31:22 CDT(-0500)] <Justin_o> in particular for stitching we could actually remove some file dependencies and etc

[09:33:31 CDT(-0500)] <jhung> justin_o: I think stitching can be removed. Capture and Calibration will still need to exist... so perhaps present but not used? Would this mean we would still have to test it on release of 0.5?

[09:43:57 CDT(-0500)] <Justin_o> jhung: i guess so, not sure yet, but probably.. if we remove stitching though we'll have to fix up capture to work again

[09:44:38 CDT(-0500)] <Justin_o> since at the moment it's embedded in the capture workflow

[10:11:37 CDT(-0500)] <anastasiac> Justin_o, could you have a look at this? http://issues.fluidproject.org/browse/FLUID-2390 First off, should that say "maximum" instead of "minimum" and second, is this still an issue?

[10:12:36 CDT(-0500)] <Justin_o> anastasiac: so it should be minimum because UIO used to set the minimum text size or that's how it was worded before i believe

[10:12:47 CDT(-0500)] <Justin_o> so this would be the max min, if that makes sense

[10:13:03 CDT(-0500)] <Justin_o> that being said, i think we have moved in a different direction for UIO now and this could be closed

[10:13:11 CDT(-0500)] <Justin_o> jameswy: ^ can you verify that

[10:14:33 CDT(-0500)] <anastasiac> ok, great, thanks Justin_o and jameswy

[10:15:35 CDT(-0500)] <anastasiac> michelled, could you have a look at http://issues.fluidproject.org/browse/FLUID-1834? I'm not sure I understand it enough to assess whether or not it is still an issue.

[10:17:37 CDT(-0500)] <michelled> well, we've actually removed option for removing background images, haven't we?

[10:19:39 CDT(-0500)] <anastasiac> michelled, yes, we have - ok, so that's what it was about. so no longer an issue. thanks

[10:20:39 CDT(-0500)] <anastasiac> cindyli, this issue hasn't been addressed yet, has it? http://issues.fluidproject.org/browse/FLUID-4481

[10:21:07 CDT(-0500)] <cindyli> no, anastasiac

[10:21:10 CDT(-0500)] <anastasiac> thanks

[10:21:13 CDT(-0500)] <cindyli> np

[10:26:32 CDT(-0500)] <jessm> fluid-everyone: the breeze channel seems broken to me – can anyone confirm?

[10:26:51 CDT(-0500)] <colinclark> I'm just trying now myself, jessm

[10:27:06 CDT(-0500)] <colinclark> OCAD had a power outage in the new data centre last night--this might be related

[10:27:27 CDT(-0500)] <anastasiac> should we use the york fall-back?

[10:27:42 CDT(-0500)] <colinclark> I just get a white page myself

[10:27:47 CDT(-0500)] <colinclark> York sounds like a good plan

[10:31:15 CDT(-0500)] <jessm> can someone post the york url?

[10:31:22 CDT(-0500)] <heidi_> http://connect.yorku.ca/fluidwork

[10:36:50 CDT(-0500)] <jhung> Sorry I have to leave the stand-up. I'm getting major lag and overlapping voices from speakers.

[10:37:36 CDT(-0500)] <jhung> my update: continuing work on Decapod Import and styling. That's all.

[11:29:48 CDT(-0500)] <heidi_> Justin_o anastasiac http://fluidproject.org/ needs to be updated

[11:29:52 CDT(-0500)] <heidi_> front page

[11:30:06 CDT(-0500)] <anastasiac> ack! I missed that, thanks heidi_

[11:30:11 CDT(-0500)] <anastasiac> Justin_o, I'll take care of that

[11:30:11 CDT(-0500)] <heidi_> np

[11:30:19 CDT(-0500)] <Justin_o> anastasiac, heidI_: thanks

[11:31:02 CDT(-0500)] <anastasiac> done

[12:00:50 CDT(-0500)] <heidi_> Justin_o i updated http://dev.inclusivedesign.ca/wordpress/ with UIO 1.4 and it's not hiding the tabs correctly.... any guesses off the bat what's up?

[12:01:30 CDT(-0500)] <Justin_o> heidI_: what's the issue, i'm not sure i'm seeing it?

[12:01:45 CDT(-0500)] <heidi_> Justin_o when you open the panel are you seeing all of the tabs at once? i do

[12:01:54 CDT(-0500)] <Justin_o> heidI_: they look okay

[12:02:35 CDT(-0500)] <Justin_o> heidI_: i tried for FF and Safari and both seem okay

[12:02:50 CDT(-0500)] <Justin_o> heidI_: are you sure your css and js are all running?

[12:03:25 CDT(-0500)] <heidi_> Justin_o i just cleared cache/restarted/etc and it's working now - false alarm!

[12:03:34 CDT(-0500)] <heidi_> not sure why... just old code i guess

[12:03:56 CDT(-0500)] <Justin_o> heidI_: yep.. probably.. scary when that happens though

[12:03:58 CDT(-0500)] <heidi_> Justin_o it's too bad the focus styling makes the tabs look weird

[12:05:23 CDT(-0500)] <Justin_o> heidI_: yah, a bit..

[12:05:30 CDT(-0500)] <Justin_o> we'll have to fix that up later..

[12:05:46 CDT(-0500)] <heidi_> ya

[14:39:00 CDT(-0500)] <heidi_> heya jameswy do you recall if handbook layouts are on the wiki for anastasiac?

[14:39:11 CDT(-0500)] <heidi_> not sure if there were mockups with UIO - but i think not, right?

[14:39:44 CDT(-0500)] <anastasiac> heidi_, jameswy, I did find some mockups on the wiki: http://wiki.fluidproject.org/display/fluid/User+interface+options+mocked+up+in+Inclusive+Learning+Handbook and http://wiki.fluidproject.org/display/fluid/Inclusive+learning+handbook+mockups

[14:40:44 CDT(-0500)] <heidi_> aha, yep

[14:41:19 CDT(-0500)] <jameswy> Thanks anastasiac

[14:42:38 CDT(-0500)] <heidi_> anastasiac is that what you need? i think the "text pref" link was all there was of a UIO mockup eh jameswy? i'll email you github info once i get it set up... i think the process will be you can clone the site and work on it locally, commit changes... do you have a local server set up?

[14:43:26 CDT(-0500)] <anastasiac> heidi_, those mock-ups are what I was thinking of. No, I don't have a local server set up - do you recommend that, instead of working on the server with a dev site?

[14:43:37 CDT(-0500)] <jhung> justin_o: I pushed up changes to Import. I added new selectors for Remove All and Cancel Import. It's a bit of a mess currently, but hopefully it'll get cleaner soon.

[14:44:22 CDT(-0500)] <Justin_o> jhung: thanks.. i'm going to try to get uploading to the server working, then i'll merge in your changes and hope things are still all good

[14:44:41 CDT(-0500)] <heidi_> anastasiac i think that's what colinclark and i are leaning toward... you would clone the dev site from github, run the db script, make your changes, commit and push the development branch

[14:45:07 CDT(-0500)] <Justin_o> jhung: by the way, i've started to use eclipse and pydev. it lets us do debugging also it makes it a lot easier to start and stop the server

[14:45:08 CDT(-0500)] <heidi_> it'll be a good system for tracking changes made to our sites

[14:45:31 CDT(-0500)] <heidi_> when it's time to go live, we'd merge the dev branch into the production branch, then the server would update from it

[14:45:34 CDT(-0500)] <jhung> justin_o: okay. If you can, try hooking up the selectors to the Import.js file. The prefix for the selectors have changed btw ("fl-uploader" -> "ds-import").

[14:45:46 CDT(-0500)] <jhung> justin_o: cool!

[14:52:01 CDT(-0500)] <colinclark> anastasiac, heidi_: Yep, I think it's ideal for us to start developing our websites in a local environment first

[14:52:24 CDT(-0500)] <colinclark> This might take a bit of time to transition to, but in the case of UI Options and the Inclusive Learning Design Handbook, we should go ahead and try that workflow out

[14:52:29 CDT(-0500)] <colinclark> heidi_

[14:52:42 CDT(-0500)] <colinclark> heidi's in the midst of moving the ILDH's code into Github

[14:52:48 CDT(-0500)] <colinclark> which will be located in the Fluid organizational space

[14:53:12 CDT(-0500)] <colinclark> In the meantime, greggy1 put together a prototype MediaWiki theme with UIO in it

[14:53:23 CDT(-0500)] <colinclark> https://github.com/gregrgay/mediawiki-uioptions-theme

[14:53:42 CDT(-0500)] <colinclark> As best as I can tell, it looks like it's based on the ILDH's theme, since I see some references to it in the code

[15:01:25 CDT(-0500)] <colinclark> heidi_: You mentioned about how we should handle databases in this new production workflow

[15:01:35 CDT(-0500)] <heidi_> yeah

[15:02:03 CDT(-0500)] <heidi_> i'm guessing just a dump w/o passwords that we would store as database.sql or something in the repo

[15:02:07 CDT(-0500)] <colinclark> In the long term, I still think that it will be coolest to actually have a text dump of the MySQL database (with the exception, of course, of the user table and anything else containing sensitive information) right in Git

[15:02:14 CDT(-0500)] <colinclark> And even perhaps a script that automates it all

[15:02:32 CDT(-0500)] <colinclark> But in the short term, after talking with huslage, I think we'll be okay to not worry about databases yet

[15:02:45 CDT(-0500)] <colinclark> He said he'd triple check that all the appropriate backups are being run on our servers

[15:03:01 CDT(-0500)] <colinclark> So, for example, anastasiac's workflow will be a little more complicated than we'd like

[15:03:14 CDT(-0500)] <heidi_> yeah, how would she get the db locally?

[15:03:19 CDT(-0500)] <colinclark> She'll still have to shell into the box and grab any private configuration information

[15:03:27 CDT(-0500)] <colinclark> grab the config file and a database dump

[15:03:35 CDT(-0500)] <colinclark> not ideal, but not too much of a deal

[15:03:52 CDT(-0500)] <colinclark> My vision in the long term is to completely automate the process of deployment

[15:04:01 CDT(-0500)] <colinclark> no one should even have to shell into the box under ordinary circumstances

[15:04:09 CDT(-0500)] <colinclark> We'd have a listener running on each production server

[15:04:17 CDT(-0500)] <heidi_> and she'd have to tweak the config to match her local db login/pw

[15:04:21 CDT(-0500)] <colinclark> right

[15:04:25 CDT(-0500)] <colinclark> exactly

[15:04:35 CDT(-0500)] <colinclark> Github would ping this listener each time new code was pushed into the production branch

[15:04:41 CDT(-0500)] <colinclark> and the server would automatically update itself

[15:04:47 CDT(-0500)] <colinclark> We're not quite there yet

[15:04:54 CDT(-0500)] <colinclark> but we'll get there in steps

[15:05:10 CDT(-0500)] <heidi_> will a db dump be created/accessible or is that something she'd have to create

[15:05:24 CDT(-0500)] <heidi_> or is it automated by aaron

[15:06:27 CDT(-0500)] <colinclark> Eventually we'll have a db dump-one each for the production and development branches-right in Github

[15:06:39 CDT(-0500)] <colinclark> perhaps also with a script to automatically install it

[15:06:48 CDT(-0500)] <colinclark> That's the dream, anyway

[15:06:54 CDT(-0500)] <colinclark> Does it seem sort of sane, heidi_?

[15:06:59 CDT(-0500)] <colinclark> If not quite for today?

[15:07:51 CDT(-0500)] <heidi_> colinclark yeah i think it's sane and great to have versioning/tracking. i just wonder about someone who wants to make a quick fix like anastasiac having to go through all these hoops first... what do you think anastasia?

[15:08:15 CDT(-0500)] <colinclark> I guess in many ways, it's the "quick fix" that is the biggest risk in these kinds of situations

[15:08:25 CDT(-0500)] <colinclark> Like, today, when we were talking about the IDRC web site

[15:08:39 CDT(-0500)] <colinclark> and it was unclear which version, the dev or the production site, was even newest

[15:08:40 CDT(-0500)] <heidi_> yeah, easily forgotten tweaks

[15:08:51 CDT(-0500)] <colinclark> Hopefully there will be fewer long-term hoops to jump through

[15:08:57 CDT(-0500)] <colinclark> once each site developer has a local environment set up

[15:09:01 CDT(-0500)] <anastasiac> I think in the ideal situation, we'll have the db dump and appropriate scripts that will make it easier to carry out the workflow thought github without hoops

[15:09:24 CDT(-0500)] <colinclark> yep

[15:09:30 CDT(-0500)] <colinclark> Short term hoops

[15:09:35 CDT(-0500)] <colinclark> long term automation

[15:12:13 CDT(-0500)] <heidi_> anastasiac i'm doing handbook now... will send you github repo in a minute

[15:12:36 CDT(-0500)] <anastasiac> heidi_, excellent, thanks. I'm getting MAMP set up now (well, downloading...)

[15:12:57 CDT(-0500)] <heidi_> colinclark i'm wondering about putting the fresh mediawiki install in as well...

[15:13:08 CDT(-0500)] <heidi_> into a branch

[15:13:19 CDT(-0500)] <colinclark> heidi_: that would be awesome

[15:13:34 CDT(-0500)] <colinclark> I guess we could try for our original idea

[15:13:43 CDT(-0500)] <colinclark> put the fresh media wiki into master

[15:14:04 CDT(-0500)] <colinclark> then changes from the stock code are tracked in dev -> production

[15:14:28 CDT(-0500)] <colinclark> I'm just not sure, from an already-customized site, how we'd quite get that kind of an overlay

[15:14:30 CDT(-0500)] <colinclark> If you know what I mean

[15:14:49 CDT(-0500)] <heidi_> yeah... create the production branch from master... then merge in the live site

[15:16:05 CDT(-0500)] <colinclark> yeah, that part is easy

[15:16:27 CDT(-0500)] <colinclark> the problem is how you "rewind time" back to a fresh media wiki

[15:16:31 CDT(-0500)] <colinclark> and track changes from there

[15:16:35 CDT(-0500)] <colinclark> I'm just trying to think

[15:16:48 CDT(-0500)] <colinclark> Justin_o: Do you have any thoughts on the subject? (sorry to distract you from Decapod)

[15:18:15 CDT(-0500)] <heidi_> colinclark i was going to just commit a fresh install

[15:18:44 CDT(-0500)] <colinclark> heidi_: Walk me through it...

[15:19:45 CDT(-0500)] <heidi_> colinclark working through it now... unzip mw. add all the files/commit. create a new branch called production. merge in live site...

[15:19:58 CDT(-0500)] <colinclark> how would you merge in the live site?

[15:20:06 CDT(-0500)] <colinclark> That's the part I'm stuck on, perhaps stupidly

[15:20:26 CDT(-0500)] <heidi_> yeah i am too... literally paste the files into/over the mw files?

[15:20:26 CDT(-0500)] <colinclark> I guess you probably could just drop the site on top of it

[15:20:32 CDT(-0500)] <colinclark> yeah, I think it might work

[15:20:43 CDT(-0500)] <heidi_> trying now...

[15:24:36 CDT(-0500)] <colinclark> heidi_: I just chatted with Justin_o in person

[15:24:40 CDT(-0500)] <colinclark> since he was distracted in Linuxland

[15:24:54 CDT(-0500)] <colinclark> michelled thinks you should be fine to just replace everything with our modified version

[15:24:59 CDT(-0500)] <heidi_> colinclark it's just keeping things in the right dir... all the git stuff. i'd have to replace the current live site with the fresh install, then dump the stuff in

[15:25:12 CDT(-0500)] <heidi_> unless i can move .git dirs

[15:25:15 CDT(-0500)] <colinclark> yes, that's the one challenge

[15:25:20 CDT(-0500)] <colinclark> I think it's probably evil to do that

[15:25:27 CDT(-0500)] <colinclark> but it's probably not crazy

[15:25:31 CDT(-0500)] <heidi_> which one?

[15:25:32 CDT(-0500)] <colinclark> want to Skype for a second?

[15:25:33 CDT(-0500)] <heidi_> ha

[15:25:35 CDT(-0500)] <colinclark> moving .git dirs around

[15:25:40 CDT(-0500)] <colinclark> being evil

[15:25:42 CDT(-0500)] <heidi_> sure

[15:25:57 CDT(-0500)] <colinclark> the challenge being, how do we do this while not causing harm to our live website

[15:26:09 CDT(-0500)] <heidi_> ya

[15:26:21 CDT(-0500)] <heidi_> maybe i'll try dev.handbook first