| * ndushay joins | 00:07 | |
| * g8tor leaves | 01:10 | |
| * ndushay leaves | 02:49 | |
| * jaron_1 joins | 07:07 | |
| * jaron_1 leaves | 07:09 | |
| * jaron_1 joins | ||
| * jaron joins | 07:14 | |
| * jaron leaves | ||
| * jaron joins | 07:15 | |
| * jaron leaves | 07:17 | |
| * jarona joins | 07:28 | |
| * jarona leaves | 07:30 | |
| * jarona joins | ||
| * jarona leaves | 07:31 | |
| * jaron_1 leaves | 07:35 | |
| * jaron joins | ||
| * g8tor joins | 08:11 | |
| * bess joins | 08:43 | |
| * jamieorc joins | 08:49 | |
| * bess leaves | 08:50 | |
| * bess joins | 09:07 | |
| * bess leaves | 09:41 | |
| * bess joins | 09:52 | |
| g8tor: are we ready to release? | 10:13 | |
| looks like Matt fixed a bunch of things yesterday and tagged a release | ||
| <g8tor> | good AM bess | 10:15 |
| <bess> | good morning g8tor | |
| <g8tor> | is saw the messages come through the commiters list | |
| looks like it to me, let me try one more fresh install and I will let you know in a couple | ||
| <bess> | awesome | 10:16 |
| could you glance at the install instructions at http://github.com/projectblacklight/blacklight | ||
| * cbeer joins | ||
| <bess> | they seem incomplete to em | |
| me | ||
| cbeer! | ||
| cbeer: I've been talking about you all morning | 10:17 | |
| <g8tor> | ok will do | |
| <cbeer> | uh oh :P | |
| <bess> | I'm at hydra meetings this week and everyone's pretty excited about the stuff I'm telling them about WGBH | |
| <cbeer> | awesome | |
| <bess> | looks like they're interested in some kind of arrangement for working together | |
| <cbeer> | i never asked you about your relation to hydra | 10:18 |
| <bess> | but I guess your boss and my boss have to talk or whatever | |
| * bess thinks about how to say something diplomatic | ||
| people come up with ambitious ideas and then I try to figure out how to implement them | ||
| <cbeer> | guess i should tell my boss more about what i've been doing.. | |
| <bess> | :) | |
| cbeer: are you going to be at code4lib and / or PyCon this year? | 10:19 | |
| I'm just trying to figure out when we could meet up to talk in more detail about some of this stuff | ||
| <cbeer> | i'm hoping for code4lib, but it's too early to know | 10:20 |
| <bess> | ok | |
| cbeer: do you get down to DC at all? I know you were there for a workshop recently. | 10:21 | |
| <cbeer> | but i should also watch for CPB/PBS/NPR things that could get me to DC at last | |
| s/last/least | ||
| and getting to DC is much quicker than asheville | 10:22 | |
| <bess> | let me know whenever you'll be in DC and I'll drive up | |
| it's not far for me | ||
| <cbeer> | will do | 10:23 |
| oh, and i started writing stuff about workflows on my flight yesterday | 10:24 | |
| <g8tor> | bess: here are my finding (LOL) | 10:28 |
| <cbeer> | bess: http://cbeer.info/~chris/workflow.png | |
| <g8tor> | I did two install the first without downloading solr & jetty data. That went smashingly easy! So we are good if you are installing and already have a solr instance alone with an existing solr.yml file and a customized blacklight_config.rb file | 10:29 |
| <cbeer> | bess: sorry, guess it is http://cbeer.info/~chris/workflow-flow.png | 10:30 |
| <bess> | cbeer: thank you! | |
| g8tor: good to know | 10:31 | |
| <g8tor> | The second I installed as a first time user, I installed everything according to the template questions. I ran into two issues | |
| <cbeer> | bess: i have a bunch of high-level brain-dump text too, but that image is worth 634 words at this point.. at least until i write up use-cases | |
| <g8tor> | first when starting jetty, when the template installs solr/jetty there is no log directory so jetty won't start. The reason for that is that git ignores empty directories (easy enough to fix) | 10:34 |
| <bess> | g8tor: do you have time to fix that? | |
| g8tor: thank you for catching that, btw. :) | ||
| <g8tor> | yes I can fix it but I'm alittle confused about how we are doing things but let me continue | 10:35 |
| <bess> | g8tor: what are you confused about? | 10:36 |
| <g8tor> | the second : (after creating a log directory in the jetty folder) I was able to index the daya as instructed. I then firedupp the app (./script/server) nd attempt to access http://localhost:3000/ i get an error saying "A copy of ApplicationController has been removed from the module tree but is still active!" and that is where I am right now | 10:37 |
| <bess> | g8tor: oh! jaron just wrote to the list about that error | 10:38 |
| did you read his email? | ||
| * darthmolly joins | ||
| <g8tor> | no i didnt see that | |
| <bess> | hi, darthmolly | |
| <darthmolly> | hi | |
| <g8tor> | will check it in a minute | |
| <jaron> | g8tor: oh! could you try fix #2 from here: http://groups.google.com/group/blacklight-development/browse_thread/thread/6805fb7da7d93511 | 10:39 |
| <g8tor> | I'll try right now feeding the baby and he doesn't like to wait LOL | 10:40 |
| <bess> | g8tor: awww! :) | |
| <g8tor> | bess: i'm confused about the dev cycle | 10:55 |
| tags are light weight pointers ti specific points in time | ||
| so for instance if I pull down the blacklight-jetty repo and add the log directory along with a .gitignore file within should I delete the tag and recreate it after pushing the changes or is that a 2.4.1 tag? if its a 2.4.1 tag that leaves the recomended 2.4 without the fix. Am i right r am I all screwed up on this? | 10:58 | |
| * ndushay joins | 11:02 | |
| <g8tor> | hi ndushay | 11:03 |
| <bess> | g8tor: we haven't really "released" 2.4 yet | 11:05 |
| so at this point I think it's okay to make changes to 2.4 and then just commit them | ||
| <ndushay> | hi g8tor | 11:08 |
| <g8tor> | ndushay: I saw your message last night about the dev cycle what is your understanding of it? | 11:09 |
| <ndushay> | g8tor: basically, we had discussions a while back about adhering to the "apache" model | 11:11 |
| trunk - active development. code checked in passes all tests, but not ready for release. | 11:12 | |
| release - a stable snapshot that we have confidence in (beyond tests for trunk?) | 11:13 | |
| bug fixes - we don't have no stinking bug fixes | ||
| <jamieorc> | b/c we have no bugs :D | |
| <ndushay> | i just realized this window wasn't scrolled to see latest messages so I read the conversation with jamie | |
| i'm still working on the git mind set | 11:14 | |
| but it makes sense to me that we have a *branch* for each *release* | ||
| and bug fixes/improvements are added to that branch | ||
| but we do need best practices for trunk vs. branch | 11:15 | |
| that is, we develop on trunk, as we have been | ||
| <jamieorc> | trunk/master is where current development is going on | |
| <ndushay> | but if we agree that we can add a feature or a bug fix to a branch, then we do it. | |
| in addition to. | ||
| <jamieorc> | when a new version is ready for release, create a branch, then create a tag for release | 11:16 |
| right, that becomes a tag in the branch | ||
| <ndushay> | jamieorc: so we have a branch for 2.4, 2.4.1, 2.4.2? | |
| <jamieorc> | no | |
| <ndushay> | or we have a branch 2.4 | |
| <jamieorc> | we have a branch for 2.4 | |
| <ndushay> | and tags 2.4.1, 2.4.2 | |
| beat you. ;-) | ||
| <jamieorc> | and we tag 2.4.0, 2.4.1, etc | |
| yes | ||
| :D | ||
| that's what matt did last night | 11:17 | |
| made 2.4 branch and tagged 2.4.0 | ||
| <ndushay> | so the main thing to up to 2.5 is a decision to put changes xyz in a new 2.5 branch, rather than making them to 2.4 branch with 2.4.x tag. | |
| ? | ||
| <bess> | ndushay: yes that seems right to me | 11:18 |
| urgent bug fixes could go into a 2.4.1 | ||
| <ndushay> | this model makes ongoing small changes more possible | |
| <bess> | but pretty much anything else would go into 2.5 | |
| <ndushay> | we decide policy. | |
| <bess> | right | |
| <jamieorc> | right | |
| <ndushay> | bess: yes, i like the notion of sticking to our current approach of bundling up changes | |
| <jamieorc> | here's an example | 11:19 |
| let's say someone found a bug in 2.4.0 | ||
| we know it needs fixing in master and 2.4 | ||
| <ndushay> | as a release. less burden on documentation and other overhead. | |
| <jamieorc> | so we can fix it, merge to master and 2.4 because we made the changes in a local branch first and the tag a release from 2.4 branch | 11:20 |
| <ndushay> | jamieorc: got it. | 11:21 |
| jamieorc: right now, i'm trying to grasp how to set up locally | ||
| we want to have control over when we synch up with trunk | 11:22 | |
| and keep our local code working locally | ||
| <jamieorc> | ndushay: this was very illuminating to me. It completely changed how I work: http://blog.hasmanythrough.com/2008/12/18/agile-git-and-the-story-branch-pattern | |
| <ndushay> | thanks. | |
| i've been reading reading reading | ||
| i've discovered pictures help a lot. | 11:23 | |
| i feel like a little kid | ||
| i also feel like i'm reading Larry Wall's perl book, where in order to explain A, he tells you about B, C, F, Z | ||
| and to explain about F, he references A, G, Q, P | ||
| <jamieorc> | heh | 11:24 |
| <ndushay> | I *hated* that book. | |
| I also am really really disappointed in the git tools. | ||
| <jamieorc> | I loved Dave Thomas and Andy Hunt's book, Programming Ruby | 11:25 |
| <ndushay> | --graph is like a mainframe picture from the 60s. | |
| <jamieorc> | ndushay: u using Textmate? | |
| <bess> | ndushay: I found just doing it helped tremendously. I just dove into git for the NWDA project, and it was frustrating at times, but really doing it made me learn it pretty quickly | |
| <ndushay> | gitk is a little better, but same graph. | |
| <jamieorc> | if you're using TextMate, get the git bundle | |
| <ndushay> | bess: if i didn't have to come up with a decent way to do the "vendor branch" model we're using in svn, it would be easier. | |
| jamieorc: i have it. | ||
| <jamieorc> | I changed the major key binding to CTRL-SHIFT-Z so it was easier to get to | 11:26 |
| <ndushay> | basically, I'm going to jump in this week. | |
| jamieorc: is there a way to see an outline of a class in textmate? | ||
| i'm always scrolling around and I can't see an overview | ||
| <jamieorc> | well, at the bottom of the window on the bar is something that shows methods and such | 11:27 |
| <ndushay> | i really wish we were co-located so I could leverage other folks' knowledge better. | |
| jamieorc: right. i forget about that. | ||
| <jamieorc> | you can also use CMD-Shift-T to see a list of methods and then go to them | |
| <ndushay> | ah - cool. | 11:28 |
| <jamieorc> | You will want to know CMD-T and CMD-Shift-T intimately | |
| <ndushay> | jamieorc: theres some talk here about intellij and rubymine as IDEs | |
| <jamieorc> | sure | |
| there are ruby devs for all the java tools | ||
| i mean java ides | ||
| <ndushay> | yeah, i haven't done that much with ruby in eclipse | 11:29 |
| <jamieorc> | also, Anoop swears by VIM with ruby and rails plugins | |
| <ndushay> | textmate is pretty cool. | |
| <jamieorc> | but I'm not inclined to vim | |
| <ndushay> | i like vigor myself. ;-0 | |
| <jamieorc> | ndushay one of my clients/colleagues just texted me this: wow. rails.vim IS pretty cool | 11:34 |
| he just installed it on linux | ||
| <ndushay> | jamieorc: i have a mac. It's 2009. colors. graphical representations as appropriate. | 11:37 |
| i can't see screen shots of vim at their site. | ||
| what's someone who isn't an early adopter (me) doing in this biz, anyway? | 11:40 | |
| <jamieorc> | heh, we're all learning new things every day | 11:41 |
| that's part of the fun and pain! | ||
| * ndushay leaves | 11:43 | |
| * cbeer leaves | 11:45 | |
| * cbeer joins | 12:12 | |
| * ndushay joins | 12:26 | |
| * bess leaves | 12:33 | |
| * ndushay leaves | 12:37 | |
| <g8tor> | people I'm sorry if you were trying to do a fresh install of backlight-jetty a couple of minutes ago. I made a change to correct an issue with the template nstall. | 12:44 |
| oops install that is | ||
| previously if you installed solr/jetty with the template and tried to start jetty it would fail because there was no logs directory(because it was empty git ignored it) do I cloned blacklight-jetty added the logs directory with a .gitignore file (hacky I know) pushed to master, checked out branch 2.4-stable and rebased it with master (i.e. git rebase master) and finally deleted the v2.4.0 tag and recreated it. | 12:47 | |
| I just finished a fresh (new user install) using the install template, indexed the sample data, started the ./script/server and BAM BL GOODNESS! | 12:49 | |
| ok now I'm off to do work @ wor LOL | 12:50 | |
| oops work @ work that is | ||
| clear | ||
| * bess joins | 13:09 | |
| * cbeer leaves | 13:11 | |
| * Naomi joins | 13:25 | |
| * cbeer joins | 13:58 | |
| * Naomi leaves | 14:42 | |
| * ndushay joins | 15:09 | |
| * bess leaves | 16:03 | |
| * bess joins | 16:11 | |
| * darthmolly leaves | ||
| * bess leaves | 16:18 | |
| * bess joins | 16:50 | |
| * bess leaves | 16:53 | |
| * bess joins | 16:54 | |
| * jaron leaves | 17:02 | |
| * Naomi joins | ||
| * ndushay leaves | 17:04 | |
| * cbeer leaves | 17:12 | |
| * bess leaves | 17:13 | |
| * bess joins | 17:35 | |
| * jaron joins | 17:41 | |
| * jamieorc leaves | 17:55 | |
| <g8tor> | ndushay: do you thing I should change the email address for the projectblacklight account on github to the blacklight-commiters address? | 17:58 |
| * bess leaves | 17:59 | |
| * ndushay leaves | 18:09 | |
| * g8tor leaves | 18:53 | |
| * ndushay joins | 19:13 | |
| * Naomi joins | ||
| * ndushay leaves | 19:31 | |
| * g8tor joins | 19:41 | |
| * cbeer joins | 20:49 | |
| * bess joins | 21:56 | |
| * bess leaves | 22:22 | |
| * cbeer leaves | 22:38 | |
| * g8tor leaves | 23:20 | |
Generated by Sualtam
