Timestamps are in GMT/BST.
[1:14] * kdweeks (~Adium@2001:468:c80:a103:8c23:a4b:fc61:2ae3) Quit (Quit: Leaving.)
[6:41] -dickson.freenode.net- *** Looking up your hostname...
[6:41] -dickson.freenode.net- *** Checking Ident
[6:41] -dickson.freenode.net- *** Found your hostname
[6:41] -dickson.freenode.net- *** No Ident response
[6:41] * DuraLogBot (~PircBot@ec2-107-22-210-74.compute-1.amazonaws.com) has joined #duraspace
[6:41] * Topic is '[Welcome to DuraSpace - This channel is logged - http://irclogs.duraspace.org/]'
[6:41] * Set by cwilper!ad579d86@gateway/web/freenode/ip.173.87.157.134 on Fri Oct 22 01:19:41 UTC 2010
[12:12] * mhwood (mwood@mhw.ulib.iupui.edu) has joined #duraspace
[12:14] * tdonohue (~tdonohue@c-50-179-112-246.hsd1.il.comcast.net) has joined #duraspace
[12:33] * tdonohue1 (~tdonohue@c-50-179-112-246.hsd1.il.comcast.net) has joined #duraspace
[12:35] * tdonohue (~tdonohue@c-50-179-112-246.hsd1.il.comcast.net) Quit (Ping timeout: 245 seconds)
[13:02] * tdonohue1 is now known as tdonohue
[13:35] * monikam_ (~Monika_Me@monika.Princeton.EDU) has joined #duraspace
[14:04] * kdweeks (~Adium@2001:468:c80:a103:42:add0:7ed2:ecf9) has joined #duraspace
[14:53] * Anja (82587893@gateway/web/freenode/ip.130.88.120.147) has joined #duraspace
[15:01] <tdonohue> Hello all, it's time for our weekly DSpace Developers Meeting (today at 15UTC). Today's agenda: https://wiki.duraspace.org/display/DSPACE/DevMtg+2014-06-18
[15:01] <kompewter> [ DevMtg 2014-06-18 - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/DevMtg+2014-06-18
[15:02] <tdonohue> Not many attendees today it seems...though I know some folks may be on vacation or traveling after OR14 last week in Helsinki
[15:03] <tdonohue> Today's agenda is pretty light. Mostly I wanted to go over some of what was discussed at OR14 last week, and check in on upcoming planned releases. We may have time for other discussions/topics as well
[15:03] <mhwood> Sounds good.
[15:04] <tdonohue> As of yesterday, I've posted the notes from the OR14 face-to-face DSpace Developers meeting: https://wiki.duraspace.org/display/DSPACE/DevMtg+2014-06-09+-+OR14+Meeting
[15:04] <kompewter> [ DevMtg 2014-06-09 - OR14 Meeting - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/DevMtg+2014-06-09+-+OR14+Meeting
[15:04] <tdonohue> (they are at the bottom of that page)
[15:04] <tdonohue> Essentially, during that meeting we covered a few primary topics:
[15:05] <tdonohue> 1) We talked through the results of the DSpace Vision Survey from earlier this year, along with an analysis of the results (performed by a small group of 6 Committers & DCAT folks)
[15:06] <tdonohue> There are some attached slides which detail those results & analysis...but the basics were that it seems like most of our "gaps" (things that are high priority to our community, but we haven't implemented yet) seem to lie on the UI layers.
[15:08] <tdonohue> The *recommendation* of that small group (to the DSpace Steering Group) is that (1) We need to standardize on a *single UI* (if a secondary third-party UI is built, that is fine..but only one should be supported centrally), preferrably against a standard "API layer" (e.g. REST or a Java business logic layer), and (2) It's about time to refactor & cleanup some of our codebase
[15:09] <tdonohue> Additionally, that group has recommended to the Steering Group that these two activities would be hard to do without some sort of *managed* or organized project. So, the first step would be to find a way to establish a process to get this work done (including resources), and come up with a plan for *what* we are going to do (e.g. what does this *single UI* look like? Will it be one of the current ones? Or something entirely new?)
[15:11] <tdonohue> The general feedback from those in attendance was that this seems like a reasonable idea. Everyone seemed to agree that we need more concentrated effort on avoiding too much duplication of effort (e.g. maintaining two UIs in parallel). Obviously though, many folks pointed out that we need resources to make this happen, and we want to *avoid* a situation like the "DSpace 2.0" project (where the work went nowhere)
[15:12] <mhwood> Communicate early, communicate often.
[15:13] <tdonohue> yep, exactly. That seemed to be the consensus. Needs more & better communication. And we need to locate dedicated resources to make it happen (as these projects in themselves are too "large" for an ad-hoc group to do in a timely manner)
[15:14] <tdonohue> And to be clear -- NONE of this will affect the upcoming DSpace 5.0 release. 5.0 will go forward as planned in our current development model (with both XMLUI and JSPUI). It'd be *after 5.0* that we may form a larger project to refactor / rework some of DSpace for 6.0
[15:15] <tdonohue> The DSpace Steering Group is hopeful to get this started for the 6.0 release...but the exact timelines still need to be worked out based on how quickly we can move things forward in the coming months.
[15:16] <tdonohue> During this OR14 developer meeting, we also talked through the proposed "Product Planning Process" and proposed "Governance" model going forward. Both of those have been documented in great detail on the wiki
[15:16] <tdonohue> Planning Process: https://wiki.duraspace.org/display/DSPACE/Product+Planning+Process
[15:16] <kompewter> [ Product Planning Process - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/Product+Planning+Process
[15:17] <tdonohue> Governance model: https://wiki.duraspace.org/display/DSPACE/Governance
[15:17] <kompewter> [ Governance - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/Governance
[15:18] <tdonohue> Both of these are drafts (from the Steering Group). We asked the Developers & DCAT members for feedback on the ideas presented...the general consensus seemed to be that "the proposals seem reasonable, but they may need tweaking as we start to put things into action and try and establish this larger refactor/rework DSpace project"
[15:19] <tdonohue> Essentially though, the purpose of the Planning Process & Governance model is to help us (1) locate resources, and also (2) hopefully improve communication at all levels & help us be more efficient in using our resources (less duplicative effort / projects)
[15:20] <tdonohue> I know this is a *ton* of info all at once. I'd encourage you all to review it when you have the chance, and feel free to provide feedback, ideas, etc. We can also revisit it next week as well (since our group is small today)
[15:21] <tdonohue> Essentially though, the first 1/2 of this OR14 Developer meeting was covering all of these topics. The second 1/2 we moved into discussion of 5.0 release (and what folks may be working on for that release)
[15:22] <tdonohue> For 5.0, a few major features have been identified:
[15:22] <tdonohue> (1) Mirage 2 (bootstrap based theme for XMLUI) will be released in 5.0
[15:22] <tdonohue> (2) ORCID support (also from @mire with U of Missouri) will also be released in 5.0
[15:24] <tdonohue> There is interest in finding ways to *enhance the REST API* as well for 5.0...but no one was identified (yet) to do that work. Many people hope to see the REST API improved though, in the hopes that it could become our primary API to build a UI against.
[15:24] <Anja> I've done some stuff for the REST API
[15:25] <tdonohue> There was also interest in seeing some form of "Streaming" Support in 5.0, e.g. DS-1942 . There's also some streaming work being performed by Open Repository / BioMed Central
[15:25] <kompewter> [ https://jira.duraspace.org/browse/DS-1942 ] - [DS-1942] DSpace admins should be able to enable streaming or pseudo streaming on a per-format basis - DuraSpace JIRA
[15:25] <tdonohue> Anja: yes, your name came up actually as someone who might be able to help us enhance the REST API, etc.
[15:25] <Anja> I've done something with search and stats is now working too
[15:26] <Anja> http://dspace.jorum.ac.uk/rest/items/stats?start=2014-06-01&end=2014-06-03&interval=day as an example
[15:27] <tdonohue> Anja: yep, I had heard you were working on that. It sounds like we still need to find a way to cleanup the REST API Pull Request though (as I know they are broken/messed up right now)
[15:27] <Anja> I don't quite understand how I created that mess
[15:27] <Anja> should I just delete the one and try again in a new branch?
[15:28] <Anja> Also stats is building on the search, so I don't know how to create a PR for that without the search being in the code first
[15:28] <tdonohue> It sounded like, from what I heard...it was mostly a matter of creating a Pull Request off of an older version (DSpace 1.8?) instead of the latest codebase. Sometimes the cleanest way to do a Pull Request is to do it against the "master" branch, rather than an old version of DSpace code
[15:29] <tdonohue> You can create dependent Pull Requests...just make it known that one depends on the other...that way to we try and review the search part earlier on, and merge it first
[15:30] <Anja> OK, so just create a branch of the branch with search
[15:30] <tdonohue> Anja: yep, I think that should work fine
[15:31] <Anja> I am changing job in a month, so I try to get this done fairly soon
[15:31] <tdonohue> And make sure to create the *search* PR against a fresh copy of the "master" branch, if possible. That should help the PR turn out "clean"
[15:32] <Anja> Yes, there are not many files changed for that
[15:32] <tdonohue> Anja: that'd be great! Thanks. Congrats also on a new job! Will you still be working on DSpace in your new job, or are you moving on to other things?
[15:33] <Anja> Thanks. No I am going to join the Uni Manchester Library and they are using Fedora
[15:34] <tdonohue> OK, good to know! In that case, we'll have to make sure to get your DSpace work analyzed quickly (or handed over to someone else), so that we aren't bugging you with DSpace REST API questions later on :)
[15:35] <Anja> I hand over my developments to the new person, so someone should continue with REST within Jorum
[15:35] <tdonohue> Oh, ok. That's also good to know. thanks!
[15:35] <mhwood> I'm sure we'd all appreciate an introduction.
[15:35] <tdonohue> yes, definitely
[15:36] <Anja> I'll do that soon
[15:36] <tdonohue> sounds good
[15:37] <tdonohue> A few other discussion points from the OR14 Developer Meeting....
[15:38] <tdonohue> (1) Several people (both Developers & DCAT) asked that we split the JIRA updates out into a separate mailing list (currently any updates in JIRA are sent to dspace-devel). We had some DCAT members say they'd like to subscribe *just* to JIRA updates...and others felt that not all folks on dspace-devel may want to see every little JIRA update
[15:39] <tdonohue> (2) Folks requested that DuraSpace find a way to re-enable self-registration in JIRA/Wiki. It's been disabled since December (after spammers attacked our wiki and crashed it). I've already brought this up with our sysadmin folks, and we're going to look at options to re-enable it (hopefully as early as next week)
[15:41] <tdonohue> (3) Finally, there was a request for some sort of "Developers Hub" (akin to a "Stack Overflow" or similar)...a place to do Q&A and vote up good answers...also a place to share what folks are working on (even tiny projects or fixes or tweaks), so that it's easier to find common interests. The concern is that the mailing list is hard to find old answers on, and some things go unanswered. A few of us (Graham Triggs, Andrea Schweer
[15:44] <tdonohue> Regarding #3 -- essentially folks are dissatisfied with the mailing lists. Too many questions are repeated, and it's hard to find answers...and too many threads are "forgotten" or unanswered. So, we're just trying to see if there's a better way to communicate between developers..with "Stack Overflow"-like idea being just one possible option.
[15:45] <mhwood> I would wish for a way to be notified of activity, so I don't have to remember to scan for new stuff all the time.
[15:45] * kdweeks (~Adium@2001:468:c80:a103:42:add0:7ed2:ecf9) Quit (Ping timeout: 260 seconds)
[15:46] <tdonohue> mhwood: yep. I agree. It'd be nice to have a way to be notified, or at least have a place you can go to see "unanswered" stuff....that's how the idea of "Stack Overflow" came up...they do a good job of letting you "subscribe" to topics, and "incentivizing" you (via badges/notoriety) to take part & help out
[15:48] <tdonohue> I've been digging around a bit already...and Stack Exchange actually does let you suggest a new "Q&A Site" (https://area51.stackexchange.com/) So, we could try to suggest one for DSpace. I also just stumbled across a plugin for Confluence wiki which lets you do Q&A similar to StackOverflow/StackExchange: https://www.atlassian.com/wac/software/confluence-questions
[15:48] <kompewter> [ Confluence Questions - Knowledge Sharing Software | Atlassian ] - https://www.atlassian.com/wac/software/confluence-questions
[15:49] <tdonohue> But, I'll be forwarding these ideas on to Graham & Andrea (and anyone else who is interested) to get their comments, etc.
[15:50] <tdonohue> So, I think that is *everything* from OR14 that I wanted to highlight. Didn't realize it would take most of the meeting ;)
[15:52] <tdonohue> Any questions on OR14 stuff...or comments? As mentioned, this was a ton of info...so questions in the future are also welcome, and we can even revisit this briefly next week as well to see if there are questions
[15:52] <Anja> sounds all good
[15:52] <tdonohue> Ok. cool.
[15:53] <mhwood> Thanks!
[15:53] <tdonohue> So, in the final few minutes here... I wanted to at least touch upon the 3.3 bug fix release. It looks like all the tickets marked for 3.3 are now completed. So, are we ready to release 3.3 this week (or early next week)?
[15:55] <mhwood> I had a question out on -devel about a problem that I had with m-release-p not updating versions properly. It depends on the version of m-release-p *and* the version of git. Would like to revive that and see what people think.
[15:56] <tdonohue> oh, I must've missed that query while I was out at OR14. Need to go back and look again
[15:56] <mhwood> Yeah, of course I posted it Friday afternoon before OR to ensure the smallest audience. :-/
[15:57] <mhwood> Date: Fri, 6 Jun 2014 14:49:10 -0400
[15:57] <mhwood> Subject: [Dspace-devel] mvn release plugin didn't update version properly for
[15:57] <mhwood> 3.3-rc1: now what?
[15:57] <tdonohue> just found it
[15:58] <tdonohue> Not sure I fully understand what happened. It sounds like you looked into this some? It's a common problem?
[15:59] <mhwood> It's a somewhat common problem, but the solution is *either* to upgrade or downgrade m-release-p, depending on your environment. So fixing it here could break it elsewhere.
[15:59] <tdonohue> do you have links to these "solutions"?
[15:59] <mhwood> I'll see if I can find some.
[16:00] <tdonohue> cause I think I need some more info...I'll try and dig around myself too
[16:01] <mhwood> Thanks. I should followup on the ML just to reawaken the thread.
[16:02] <mhwood> https://jira.codehaus.org/browse/MRELEASE-812
[16:02] <kompewter> [ [MRELEASE-812] "prepare" does not commit before tagging and therefore deploys snapshot instead of release - jira.codehaus.org ] - https://jira.codehaus.org/browse/MRELEASE-812
[16:02] <tdonohue> Also, regarding "SNAPSHOT" Releases...it looks like your snapshot release did show up in Sonatype's Maven repo: https://oss.sonatype.org/content/groups/public/org/dspace/dspace-api/3.3-SNAPSHOT/
[16:02] <kompewter> [ Index of /groups/public/org/dspace/dspace-api/3.3-SNAPSHOT ] - https://oss.sonatype.org/content/groups/public/org/dspace/dspace-api/3.3-SNAPSHOT/
[16:03] <mhwood> OK, either it was slow or I wasn't looking in the right place.
[16:06] <tdonohue> Hmm...this workaround seems to imply that all you need to do is set "LANG" to fix the "mvn release:prepare" issues: http://www.shredzone.de/cilla/page/373/maven-release-plugin-and-git-fix.html
[16:06] <kompewter> [ maven-release-plugin and git fix - shredzone ] - http://www.shredzone.de/cilla/page/373/maven-release-plugin-and-git-fix.html
[16:07] <mhwood> mwood@mhw ~ $ locale
[16:07] <mhwood> LANG=en_US.UTF-8
[16:07] <mhwood> Already got that.
[16:08] <mhwood> Just found this, though: http://stackoverflow.com/questions/20912299/using-maven-release-plugin-with-git-1-8-5
[16:08] <kompewter> [ Using maven-release-plugin with git-1.8.5 - Stack Overflow ] - http://stackoverflow.com/questions/20912299/using-maven-release-plugin-with-git-1-8-5
[16:09] <tdonohue> that one just says to upgrade to "maven-release-plugin" 2.5. That seems simple enough to try out
[16:10] <tdonohue> Honestly, if upgrading to 2.5 "works for you", mhwood...I'd say just do that. We can revisit this again at the next release (4.2) and again with 5.0....and if it pops up again, we look for a "better" fix
[16:10] <mhwood> There are things I can do to fix it *for me*. But they can break the process for people who would not have seen the problem without the "fix".
[16:10] * tdonohue notes that we're into "overtime" here. No more topics will be brought up today after this discussion of 3.3 stuff
[16:11] <mhwood> I may try downgrading my local git temporarily, just to get this release to work. That way I don't have to introduce changes to DSpace.
[16:11] <tdonohue> mhwood: Not sure I understand how it'd break for others.. especially if people claim that v.2.5 of m-release-p should fix this problem
[16:12] <mhwood> Others say that running with m-release-p:2.5 *causes* a problem and downgrading fixes it. It's dependent on the *combination* of m-release-p and git versions.
[16:13] * Anja (82587893@gateway/web/freenode/ip.130.88.120.147) Quit (Ping timeout: 246 seconds)
[16:14] <tdonohue> I'm not seeing any verified "issues" with 2.5 in the links above...there's one claim to that affect, but everything else seems to imply that it was fixed in 2.5. So, that's why I was wondering if the quick fix here is to just upgrade us to 2.5 and *see* if it works right
[16:15] <mhwood> Would it be acceptable to just make it work for git 1.8.5ff, and if someone has problems as a result, the response is "upgrade your git"?
[16:16] <tdonohue> yes...as long as we document what version of git you need to do a release. Releases are only done by a small subset of folks. We already have notes in the Release Docs about particular versions of Maven you *must* avoid. So, having notes related to Git versions is also OK
[16:16] <mhwood> I will take that approach, then.
[16:16] <tdonohue> ok, sounds fine
[16:17] <tdonohue> So, I'm not going to bring up any more topics here. Is that the last thing for the 3.3 release though? Is the release basically "ready to go"?
[16:18] <mhwood> I think so. That's why I was putting out an RC. Not the best week to be doing that, I know.
[16:19] <tdonohue> gotcha
[16:20] <mhwood> OK, I followed up the ML posting with those links above and the fix I'm going to try. Thanks for talking it over with me.
[16:21] <tdonohue> Ok, so, I guess keep in touch about how the release process goes (you may want to obviously do another RC just as a test). We can then work on getting the docs & advertising in place for 3.3 once the Release process kinks are worked out
[16:21] <mhwood> Will do.
[16:22] <tdonohue> Thanks, mhwood!
[16:22] <tdonohue> I'm going head into "lurking" now...if anything else pops up, let me know
[16:22] * monikam_ (~Monika_Me@monika.Princeton.EDU) Quit (Quit: Leaving.)
[16:22] <mhwood> Later, then.
[16:26] * kdweeks (~Adium@2001:468:c80:a103:e0a4:8bdd:4c05:dba0) has joined #duraspace
[17:19] * monikam_ (~Monika_Me@monika.Princeton.EDU) has joined #duraspace
[18:11] * hpottinger (~hpottinge@mu-161174.dhcp.missouri.edu) has joined #duraspace
[18:23] * monikam_ (~Monika_Me@monika.Princeton.EDU) has left #duraspace
[19:50] * aawoods_ (~awoods@67.165.245.76) Quit (Ping timeout: 240 seconds)
[21:01] * mhwood (mwood@mhw.ulib.iupui.edu) has left #duraspace
[21:23] * linux4u (~james@employed.library.emory.edu) has joined #duraspace
[21:30] * kdweeks (~Adium@2001:468:c80:a103:e0a4:8bdd:4c05:dba0) Quit (Quit: Leaving.)
[21:37] * kdweeks (~Adium@2001:468:c80:a103:e0a4:8bdd:4c05:dba0) has joined #duraspace
[22:07] * tdonohue (~tdonohue@c-50-179-112-246.hsd1.il.comcast.net) has left #duraspace
[22:12] * hpottinger (~hpottinge@mu-161174.dhcp.missouri.edu) Quit (Quit: Later, taterz!)
These logs were automatically created by DuraLogBot on irc.freenode.net using the Java IRC LogBot.