Timestamps are in GMT/BST.
[6:53] -calvino.freenode.net- *** Looking up your hostname...
[6:53] -calvino.freenode.net- *** Checking Ident
[6:53] -calvino.freenode.net- *** Found your hostname
[6:53] -calvino.freenode.net- *** No Ident response
[6:53] * DuraLogBot (~PircBot@atlas.duraspace.org) has joined #duraspace
[6:53] * Topic is '[Welcome to DuraSpace - This channel is logged - http://irclogs.duraspace.org/]'
[6:53] * Set by cwilper!ad579d86@gateway/web/freenode/ip.173.87.157.134 on Fri Oct 22 01:19:41 UTC 2010
[12:19] * mhwood (~mhwood@2001:18e8:3:10ab:7a2b:cbff:feb4:89a9) has joined #duraspace
[12:54] * GargantuaSauce (~Gargantua@142.176.125.19) has joined #duraspace
[13:06] * mhwood (~mhwood@2001:18e8:3:10ab:7a2b:cbff:feb4:89a9) Quit (Ping timeout: 240 seconds)
[13:29] * tdonohue (~tdonohue@c-98-228-58-145.hsd1.il.comcast.net) has joined #duraspace
[14:22] * tdonohue (~tdonohue@c-98-228-58-145.hsd1.il.comcast.net) Quit (Read error: Connection reset by peer)
[14:25] * tdonohue (~tdonohue@c-98-228-58-145.hsd1.il.comcast.net) has joined #duraspace
[14:46] * mhwood (~mhwood@2001:18e8:3:10ab:7a2b:cbff:feb4:89a9) has joined #duraspace
[17:18] * mhwood (~mhwood@2001:18e8:3:10ab:7a2b:cbff:feb4:89a9) Quit (Ping timeout: 244 seconds)
[18:16] * PeterDietz (~PeterDiet@peterdietz.lib.ohio-state.edu) has joined #duraspace
[18:27] * grahamtriggs (~Graham@cpc2-stev6-2-0-cust333.9-2.cable.virginmedia.com) has joined #duraspace
[19:39] * mhwood (~mhwood@2001:18e8:3:10ab:7a2b:cbff:feb4:89a9) has joined #duraspace
[19:48] * keithgilbertson (~keithgilb@207.138.47.158) has joined #duraspace
[19:50] * KevinVdV (KevinVdV@d54C15D60.access.telenet.be) has joined #duraspace
[19:50] * robint (5229fe9f@gateway/web/freenode/ip.82.41.254.159) has joined #duraspace
[19:52] <tdonohue> Hi all, just a reminder that our DSpace Developers Mtg starts at the top of the hour : https://wiki.duraspace.org/display/DSPACE/DevMtg+2011-10-12
[19:52] <kompewter> [ DevMtg 2011-10-12 - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/DevMtg+2011-10-12
[19:55] * hpottinger (80cea2c6@gateway/web/freenode/ip.128.206.162.198) has joined #duraspace
[20:01] <tdonohue> Hi all, it's DSpace Devel Mtg time! Today's agenda (if you haven't seen it already): https://wiki.duraspace.org/display/DSPACE/DevMtg+2011-10-12
[20:01] <kompewter> [ DevMtg 2011-10-12 - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/DevMtg+2011-10-12
[20:01] <tdonohue> Essentially, as normal, we are mostly talking through 1.8.0 updates in preparation for final release
[20:02] <tdonohue> A few initial updates -- we could really use some volunteers to help read through the existing 1.8.0 Documentation, just to make sure things "read well", and try and catch any misspellings, typos, etc.
[20:03] <tdonohue> We could also use a few folks to look more closely at the Upgrade & Install Docs (again, mostly for typos, but also to make sure they make sense & seem complete, etc)
[20:03] <hpottinger> I'm happy to do that
[20:03] <hpottinger> general read-through and the upgrade/install docs, too
[20:04] <KevinVdV> I could use somebody to recheck & test the documentation written for DS-599 (it was written about an hour ago)
[20:04] <kompewter> [ https://jira.duraspace.org/browse/DS-599 ] - [#DS-599] SOLR statistics file download displays all files and not only those in the Bundle Original - DuraSpace JIRA
[20:04] <tdonohue> thanks hpottinger, we'd appreciate it. If anyone else can help out, honestly this is an area of "more eyes the better"
[20:04] <robint> Thanks kevinVdv, I'll have a read
[20:04] * jose_blanco (8dd32b9d@gateway/web/freenode/ip.141.211.43.157) has joined #duraspace
[20:05] <robint> I'll join in too. I've been a bit neglectful of the docs.
[20:05] <mhwood> Will try to run an eye over them.
[20:05] <tdonohue> Again, obviously, we are reviewing the docs at: https://wiki.duraspace.org/display/DSDOCDEV/DSpace+Documentation (which will be moved in preparation for 1.8.0)
[20:05] <kompewter> [ DSpace Documentation - DSpace Unreleased Documentation - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSDOCDEV/DSpace+Documentation
[20:06] <tdonohue> Thanks all. I will also try and do a read through. If anyone notices something "amiss" or needing correction (and isn't sure how best to correct), get in touch with Robin or I and hopefully we can track down someone to rewrite it
[20:07] * aschweer (~schweer@schweer.its.waikato.ac.nz) has joined #duraspace
[20:07] <tdonohue> One specific area of Documentation that I wanted to ask about. I believe that the XML Configurable Workflow is still unable to be "uninstalled"? So, I wonder if we need a big warning about that on: https://wiki.duraspace.org/display/DSDOCDEV/Configurable+Workflow Thoughts?
[20:07] <kompewter> [ Configurable Workflow - DSpace Unreleased Documentation - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSDOCDEV/Configurable+Workflow
[20:08] <robint> Plus, we need to be clear that the jspui won't work once you make that choice
[20:09] <kshepherd> morning all
[20:09] <robint> Hi kshepherd
[20:09] <tdonohue> true...so, there's two warnings there -- essentially saying, if you want to use the XML Configurable Workflow, you need to be using *just* the XMLUI, and that you may want to backup everything beforehand (as you cannot undo the DB changes)
[20:09] <robint> Where should we put this warning ?
[20:10] <robint> Doh!
[20:10] <tdonohue> I think on this page: https://wiki.duraspace.org/display/DSDOCDEV/Configurable+Workflow :)
[20:10] <kompewter> [ Configurable Workflow - DSpace Unreleased Documentation - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSDOCDEV/Configurable+Workflow
[20:10] <kshepherd> heh
[20:10] <hpottinger> I'd suggest https://wiki.duraspace.org/display/DSDOCDEV/Configurable+Workflow#ConfigurableWorkflow-Backwardscompatibility
[20:10] <kompewter> [ Configurable Workflow - DSpace Unreleased Documentation - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSDOCDEV/Configurable+Workflow#ConfigurableWorkflow-Backwardscompatibility
[20:10] <robint> Yep, pretend I didn't ask that
[20:10] * kshepherd erases robint's memory
[20:11] <tdonohue> Actually, I'd also like to see it under the "Instructions for Enabling Configurable Reviewer Workflow in XMLUI" (Or a link from there to where ever the warning is), just so that we are up front about that
[20:11] * mdiggory (~mdiggory@72.199.216.7) has joined #duraspace
[20:12] <tdonohue> robint -- I'm also willing to help with that Configurable Workflow warning, or give a second read through...let me know
[20:12] <robint> ok
[20:12] <hpottinger> robint: I'm happy to help with the warning, too
[20:13] * hpottinger gets the big red pen ready
[20:13] <tdonohue> Ok, moving on. One area still needs documentation (i believe): The new Curation Tasks (Link Checker & MS Translator) are undocumented I believe. kshepherd did you want help in documenting these?
[20:14] <kshepherd> should be fine.. i have a README at https://github.com/kshepherd/Curation/blob/master/README which i'll base the doco on
[20:14] <kompewter> [ README at master from kshepherd/Curation - GitHub ] - https://github.com/kshepherd/Curation/blob/master/README
[20:14] <kshepherd> there's not much to say about them, they're so simple ;P
[20:15] <tdonohue> ok, cool. Just wanted to make sure we still had some docs coming :) Likely just add them to https://wiki.duraspace.org/display/DSDOCDEV/Curation+System (Under the existing list of "starter tasks")
[20:15] <kompewter> [ Curation System - DSpace Unreleased Documentation - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSDOCDEV/Curation+System
[20:15] <kshepherd> yep, will do
[20:16] <tdonohue> Ok, I think that's all I had to say about Documentation (that I can recall at least). Robint did you have other 1.8.0 updates/issues/topics you wanted to review?
[20:16] <robint> I guess we should have a quick review of the last two non-documentation issues
[20:17] <tdonohue> sounds good
[20:17] <robint> kshepherd: are you ok with doing the Maven release for the dspace-cocoon... jar ?
[20:17] <kshepherd> yeah ran out of time / got distracted last night, but i'm about to start release procedure now
[20:17] <tdonohue> (looks like we are starting with DS-768)
[20:17] <kompewter> [ https://jira.duraspace.org/browse/DS-768 ] - [#DS-768] All XMLUI Error Pages respond with 200 OK, instead of 404 Not Found - DuraSpace JIRA
[20:18] <tdonohue> cool! It tested out great (as I noted in my last comment, kshepherd).
[20:18] <robint> Thanks tdonouhue, off in my own wee world there
[20:18] <kshepherd> Tim, Stuart and I have tested latest source, works good
[20:18] <mdiggory> ok guys, I've been sitting on the sidelines for the rest of this, seems we have Kim sufficiently verse in release into sonatype now?
[20:19] <robint> kshepherd: Enjoy your maven journey !
[20:19] <kshepherd> heh
[20:19] <tdonohue> We also have some docs on how to release a single module at: https://wiki.duraspace.org/display/DSPACE/Release+Procedure#ReleaseProcedure-ReleasingaSingleModule%28e.g.amodulein%2Fsvn%2Frepo%2Fmodules%2F (they mostly just refer you to the process of releasing lang packs which is the same idea)
[20:19] <kompewter> [ Release Procedure - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/Release+Procedure#ReleaseProcedure-ReleasingaSingleModule%28e.g.amodulein%2Fsvn%2Frepo%2Fmodules%2F
[20:20] <kshepherd> yeah, i've done the maven release thing before but not since we moved to sonatype. i'm sure it'll be fine
[20:20] <tdonohue> so, I'd recommend kshepherd try out those docs (and yell if you hit issues)
[20:20] <kshepherd> tdonohue: thanks
[20:20] <robint> Yeah, the docs are really accurate and a real help
[20:20] <mdiggory> tdonohue: we realized its missing a little detail on how to get an account and rights to release to sonatype
[20:20] <mdiggory> just the JIRA request URI and a line saying to create an account and post a comment in the jira task
[20:21] <tdonohue> mdiggory -- actually, those details are on that page -- look at the Prerequisites section: https://wiki.duraspace.org/display/DSPACE/Release+Procedure#ReleaseProcedure-Prerequisites
[20:21] <kompewter> [ Release Procedure - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/Release+Procedure#ReleaseProcedure-Prerequisites
[20:21] <kshepherd> looks like DS-599 is sorted, too?
[20:21] <kompewter> [ https://jira.duraspace.org/browse/DS-599 ] - [#DS-599] SOLR statistics file download displays all files and not only those in the Bundle Original - DuraSpace JIRA
[20:21] <tdonohue> (I've been trying to document the *heck* out of the Sonatype Release process, so that it will be easier for everyone, and not as dependent on mdiggory or I)
[20:22] <mdiggory> \me applauds tdonohue
[20:22] <KevinVdV> kshepherd: the documentation needs to be checked for DS-599
[20:22] <kompewter> [ https://jira.duraspace.org/browse/DS-599 ] - [#DS-599] SOLR statistics file download displays all files and not only those in the Bundle Original - DuraSpace JIRA
[20:22] <KevinVdV> But after that all is well :)
[20:22] <robint> tdonohue: I honestly found the docs really good so don't feel the need to change too much
[20:22] <tdonohue> good to know robint :)
[20:23] <tdonohue> Ok, so it sounds like Ds-768 is moving along, and Ds-599 just needs a docs check. That leaves us with DS-135 (which is the only open issue still requiring actual *code*)
[20:23] <kompewter> [ https://jira.duraspace.org/browse/DS-135 ] - [#DS-135] Withdrawn items displayed as "restricted" rather than withdrawn - DuraSpace JIRA
[20:25] <robint> mdiggory: Just curiosity, is Ds-135 (the Tombstone) dependant on the dspace-cocoon-... release ?
[20:25] <robint> To be able to return the correct status code ?
[20:25] <kshepherd> how's the 404 response being handled for DS-135, out of interest? ;)
[20:25] <kompewter> [ https://jira.duraspace.org/browse/DS-135 ] - [#DS-135] Withdrawn items displayed as "restricted" rather than withdrawn - DuraSpace JIRA
[20:25] * mhwood (~mhwood@2001:18e8:3:10ab:7a2b:cbff:feb4:89a9) Quit (Ping timeout: 240 seconds)
[20:26] <mdiggory> yes, I've got a new patch that solves this stuff, but need to get it out to everyone
[20:26] <tdonohue> mdiggory -- how far off are you on posting it? I'd be glad to help give it a run
[20:26] <mdiggory> the solution that we settled on as an approach is much simpler than either parties options....
[20:27] * mhwood (~mhwood@2001:18e8:3:10ab:7a2b:cbff:feb4:89a9) has joined #duraspace
[20:27] <mdiggory> yes, thanks I can post before the end of the day
[20:27] <tdonohue> simple = good (I like the sound of that) ;)
[20:27] <mdiggory> It needs another set of eyes....
[20:27] <mdiggory> for the group to understand the difference... we extend the RestrictedView to support different types of restriction, including withdrawn
[20:28] <mdiggory> there is one change in user experience that needs to be discussed
[20:29] <mdiggory> instead of immediately getting redirected to the login/chooser if a restricted item is accessed, the user will first see a the page stating its restricted / withdrawn / so on
[20:29] <mdiggory> the page is configured to allow a default message for each state, otherwise, if the item has a field defined to store the withdrawn message, it is nserted
[20:30] <mdiggory> in NESCent we actully extended this to support alerting about access to items in submission and in various workflow stages
[20:31] <tdonohue> mdiggory -- so you actually implemented the new feature? (the configurable withdrawal message?) It's not just a plain old XMLUI "tombstone" (similar to the JSPUI tombstone)?
[20:31] <mdiggory> because we actually allow external users "reviewers" to see items in certain workflow stages based on a shared URL with an encrypted token
[20:31] <mdiggory> this like 3 lines of code...
[20:31] <mdiggory> this = its
[20:32] <tdonohue> right, but I'm asking if this means that the XMLUI now has a *different* tombstone functionality than the JSPUI
[20:32] <mdiggory> no, theres no UI for setting the withdraw message, you need to edit it in the ItemEdit view
[20:32] <tdonohue> right, but the JSPUI doesn't allow for a withdraw message at all right now
[20:33] <tdonohue> which would mean XMLUI would support a "withdraw message" and the JSPUI would not
[20:33] <mdiggory> I'm not a big proponent of parity
[20:34] <tdonohue> my understanding was that all we were attempting to do with DS-135 was to ensure the XMLUI has the same default tombstone functionality (no custom withdraw message) as currently exists in JSPUI. But, we can change that I guess
[20:34] <kompewter> [ https://jira.duraspace.org/browse/DS-135 ] - [#DS-135] Withdrawn items displayed as "restricted" rather than withdrawn - DuraSpace JIRA
[20:34] <mdiggory> it would be easy to add imo
[20:35] <tdonohue> yea, I'm just confused a bit (which is why I'm asking all these questions). Technically, if we wanted to be "strict", the "custom withdraw message" (even if just 3 lines of code) is a new feature. Obviously we are under a feature freeze
[20:35] <mdiggory> but all that features already in https://jira.duraspace.org/browse/DS-996
[20:35] <kompewter> [ https://jira.duraspace.org/browse/DS-996 ] - [#DS-996] Add optional reason text to tombstone page - DuraSpace JIRA
[20:35] <kompewter> [ [#DS-996] Add optional reason text to tombstone page - DuraSpace JIRA ] - https://jira.duraspace.org/browse/DS-996
[20:36] <tdonohue> right, but Ds-996 was *rescheduled* for post-1.8.0
[20:36] <mdiggory> ok... no configurable message then ;-)
[20:36] * mdiggory deletes three lines of code
[20:37] <robint> My only comment would be that it does sound like a significant'ish patch, so it would be good to get it visible as soon as possible
[20:37] * hpottinger was thinking the same thing, would like to see the patch
[20:37] <robint> I think it will need some reviewing before we can do an RC2 release
[20:37] * aschweer (~schweer@schweer.its.waikato.ac.nz) Quit (Quit: Lost terminal)
[20:38] <tdonohue> agreed -- sounds like mdiggory will hopefully have it posted by end of day?
[20:38] <mdiggory> did I not just say that?
[20:38] <mdiggory> ;-)
[20:38] <tdonohue> :)
[20:38] <robint> Its all heading in the right direction
[20:39] * aschweer (~schweer@schweer.its.waikato.ac.nz) has joined #duraspace
[20:39] <tdonohue> yep. sounds like things are moving along great
[20:39] <kshepherd> hooray, i generated sufficient entropy
[20:39] * kshepherd stops throwing his laptop across the room
[20:40] <tdonohue> ok, I didn't have any other topics for today really. Does anyone else have anything to bring up (esp. for 1.8.0)?
[20:41] <mdiggory> haha
[20:41] <robint> Not me. I should head off and start reviewing docs.
[20:41] <tdonohue> There are a few Documentation based tickets still open for 1.8.0 (listed on our mtg agenda: https://wiki.duraspace.org/display/DSPACE/DevMtg+2011-10-12), if anyone wants to claim them
[20:41] <kshepherd> i will try and review docs as well
[20:42] <mdiggory> kshepherd heads out to apple store to get laptop fixed...
[20:42] <kshepherd> i haven't really gone through and looked at the new modular config docs, docs for the new spring config xml for discovery, etc
[20:42] <PeterDietz> kshepherd: lol!1 I remember having to play video games while generating that key, a rough chore while your trying to get things done
[20:42] <tdonohue> cool. I think the more folks that can review docs the better. I feel like the docs should be *mostly* complete, but they can use more eyes (as I may have overlooked something as well in my past "quick reviews")
[20:43] <kshepherd> heh
[20:44] * hpottinger observes that DS-900 is unclaimed
[20:44] <kompewter> [ https://jira.duraspace.org/browse/DS-900 ] - [#DS-900] Create documentation for Updating a DSpace installation from source - DuraSpace JIRA
[20:44] <tdonohue> Ok, I think we can close up a bit early today then. I don't have anything else to discuss. Everyone should use the next 15 minutes to help review our documentation (there! now I'm giving you the time to do it!)
[20:45] <kshepherd> wow, i have a key on pgp.mit.edu from 1997
[20:45] <kshepherd> i would have been 14 ;)
[20:45] <mdiggory> I might get something posted then...
[20:45] <tdonohue> yes, technically I think both DS-900 & DS-901 need a volunteer. Even though DS-901 is assigned to Jeff, I don't think he's had any time to look at it (and may not have time to do so)
[20:45] <kompewter> [ https://jira.duraspace.org/browse/DS-900 ] - [#DS-900] Create documentation for Updating a DSpace installation from source - DuraSpace JIRA
[20:45] <kompewter> [ https://jira.duraspace.org/browse/DS-901 ] - [#DS-901] Add documentation about overlays - DuraSpace JIRA
[20:45] <kompewter> [ https://jira.duraspace.org/browse/DS-901 ] - [#DS-901] Add documentation about overlays - DuraSpace JIRA
[20:45] <robint> kshepherd: You were a precocious geek !
[20:45] <mdiggory> We all now know that kshepherd has always been a geek
[20:46] <tdonohue> Ok, we'll close out the meeting now. But feel free to hang around as long as you want (and tease kshepherd about his youthful geek days)
[20:47] <kshepherd> dpeending on how long this takes, the release might not happen for another 2 hours... i have a tutorial, then a lecture
[20:48] <tdonohue> ok, that's fine kshepherd. if anything goes wrong or you someone else to take over, let me know. I can always cut the release tomorrow morning when I get in.
[20:49] <kshepherd> should be all good
[20:49] <kshepherd> if i can do dspace-release, hopefully one module wont' be a big prob ;)
[20:49] <tdonohue> also note that after you "release" it to Maven Central, you may actually need to wait another 1-2 hrs or so before it will even appear (takes a while to propagate)
[20:49] <kshepherd> yep, figured as much
[20:49] <tdonohue> yep, it shouldn't be. One module is usually the easier of the two :)
[20:53] <robint> kshepherd, tdonohue : Drop me a note if you want me to pick it up tomorrow morning. Cheers
[20:53] <kshepherd> robint: cheers
[20:54] * aschweer (~schweer@schweer.its.waikato.ac.nz) Quit (Quit: leaving)
[20:55] * hpottinger waves, bye!
[20:55] * hpottinger (80cea2c6@gateway/web/freenode/ip.128.206.162.198) has left #duraspace
[20:56] * jose_blanco (8dd32b9d@gateway/web/freenode/ip.141.211.43.157) Quit (Quit: Page closed)
[20:58] * robint (5229fe9f@gateway/web/freenode/ip.82.41.254.159) Quit (Quit: Page closed)
[20:59] <KevinVdV> Needs sleep => signing off
[20:59] * KevinVdV (KevinVdV@d54C15D60.access.telenet.be) Quit ()
[21:00] <kshepherd> that was suspiciously easy!
[21:01] <kshepherd> tdonohue: done!
[21:03] <tdonohue> excellent! Yea, it's really not hard to do a single-module release, once you get the sonatype acct setup :)
[21:03] * mhwood (~mhwood@2001:18e8:3:10ab:7a2b:cbff:feb4:89a9) has left #duraspace
[22:07] * tdonohue (~tdonohue@c-98-228-58-145.hsd1.il.comcast.net) Quit (Read error: Connection reset by peer)
[22:13] * keithgilbertson (~keithgilb@207.138.47.158) Quit (Quit: keithgilbertson)
[22:16] * keithgilbertson (~keithgilb@207.138.47.158) has joined #duraspace
[22:16] * keithgilbertson (~keithgilb@207.138.47.158) has left #duraspace
[23:45] * keithgilbertson_ (~keithgilb@207.138.47.158) has joined #duraspace
[23:48] * keithgilbertson_ (~keithgilb@207.138.47.158) Quit (Client Quit)
These logs were automatically created by DuraLogBot on irc.freenode.net using the Java IRC LogBot.